B2Bi 2.3.1 Installation Guide Silent mode installation A B2Bi installation requires the manual input of many configuration details, including details of data base access, B2Bi shared location, and so on. To ease the task of installation, once you have installed an instance of B2Bi, you can use the silent mode installation method to install additional instances. Install B2Bi in Silent Mode To install B2Bi in silent mode: Using the B2Bi Server installer, install B2Bi on a machine. From <B2Bi_install_directory>/.install4j copy the file response.varfile . This is a property file that completely describes the initial installation. Launch the B2Bi installer on the same machine or install on a different machine, with the following options: Unix/Linux:<B2Bi_installer_name>.sh –q -varfile <path to response file> Windows:start /wait <B2Bi_installer_name>.exe -c –q -varfile <path to response file>Note For Windows, the user account credentials for the silent install must be the same as for the original installation. Examples Unix/Linux: ./b2bi-installer-server-linux-x86-64-2.3.1.sh -c -q -varfile /home/axway/scripts/response.varfile Windows: start /wait b2bi-installer-server-linux-x86-64-2.3.1.exe -c -q -varfile D:\Axway\scripts\response.varfile Results After a successful installation, you can start B2Bi and use the product. Content of silent file The content of the silent file contains key/value pairs from the original installation. Some of these can be modified in the silent file (for example, password are encoded in the silent file) and some are generated during the installation. Generate silent file values The silent file values can be generated as follows: Start the installer with the -encode_password argument. Enter a value to be encoded. Select Exit. Locate the encoded value in the EncodedPassword.txt file (in the same directory as the installer file). Note This functionality is useful if you need to change a password field in the silent file. The following table describes the keys used for the installation. They are in the same order as they occur in the installation dialogs and grouped per dialog: Note The keys that start with Windows are used for Windows installations only. Key Description Default value sys.installationDir Main installation directory to be used %HOMEDRIVE%\Axway on Windows and {HOME}/Axway on Unix UpgradeInterchange$Boolean Set to true if Interchange should be upgraded from previous version false InterchangeUpgradeLocation Path to Interchange installation that should be upgraded, only used if UpgradeInterchange$Boolean is set to true None, must be set if used B2BiSharedDirectory Main shared directory None, must be set UseNonDefaultdirectories$Boolean Set to true if non-default directories should be used, the directories are set by the section below false IntegratorRootDir Path to where Integrator root files should be installed <sys.installationDir>/Integrator IntegratorLocalDir Path to where Integrator local files should be installed <sys.installationDir>/Integrator/local IntegratorDataDir Path to where Integrator data files should be installed <sys.installationDir>/Integrator/data B2BiSolutionDir Path to where B2Bi core should be installed <sys.installationDir>/Integrator/solutions B2BiTmpDir Path to B2Bi temporary directory to be used <sys.installationDir>/Integrator/data/tmp B2BiSharedRootDir Path to B2Bi shared root directory <B2BiSharedDirectory>/root B2BiSharedDataDir Path to B2Bi shared data directory <B2BiSharedDirectory>/data B2BiSharedLocalDir Path to B2Bi shared local directory <B2BiSharedDirectory>/local InterchangeSharedDir Path to Interchange shared directory <B2BiSharedDirectory>/common InterchangeLicenseFile Full path to license file for Interchange None, must be set InterchangeDatabaseType$Integer Database type for Interchange, 0=MySQL, 1=Oracle, 2=Microsoft SQL Server, 3=DB2 2 (Microsoft SQL Server) InterchangeDBName Name of database to be used None, must be set InterchangeDBServerName Host name of database server localhost InterchangeDBPort$Long Port number to database Default port for database type selected InterchangeDBUserName Name of database user None, must be set InterchangeDBPassword.encoded Encoded database password None, must be set InterchangeDBPasswordConfirm.encoded Confirmation of encoded database password, should be same as above None, must be set InterchangeSkipDBVerification$Boolean Set to true if no check should be made of the database connection false UsePassport$Boolean Set to true if PassPort should be used, otherwise false. The keys below are only needed if PassPort should be used. false PP_HOST Name of PassPort host Current hostname PP_PORT$Long Port used by PassPort 6453 PP_SHARED_SECRET Shared secret key used when connecting to PassPort admin PP_SHARED_SECRET_CONFIRM Confirmation of the above admin PortRangeMin$Long Start value for port range, 371 free ports are needed 8832 PortRangeMax$Long End value for port range 10000 WindowsServiceNamePrefix Prefix to be used for Windows Service name Axway WindowsServiceDisplayNamePrefix Prefix to be used for Windows Service description Axway WindowsServiceUserName User name for the Windows Service account Must be current user (%USERNAME%) WindowsServiceDomain Domain name for the above user Must be domain for current user (%USERDOMAIN%) WindowsServicePassword.encoded Password for the user None, must be set EnableFarmServer$Boolean Set to true if this installation is connecting to a Farm server false FarmServerHostName Host name where the Farm server are installed Dummy value <HOST>, must be changed FarmServerPort Port used to connect to the Farm server 8852 NumberOfCPUs$Integer Number of CPU's, 0=2, 1=4, 2=8, 3=16 0 MessageSizeLimit Message size limit for caching message content in memory 16384 UseSentinel$Boolean Set to true if Sentinel should be used false EnableOnlineArchive$Boolean Set to true if online archive should be used false UseMQ$Boolean Set to true if MQ Connector should be used false MQMode$Integer Mode for MQ Connector if enabled, 0=server, 1=client 0 UseWebEdi$Boolean Set to true if WebEdi should be used false UseSAP$Boolean Set to true if SAP Connector should be used false UseUnicode$Boolean Use if SAP Connector have been enabled, set to true to use Unicode false UseFTP$Boolean Set to true if FTP Connector should be used false UseFile$Boolean Set to true if File Connector should be used false UseHTTP$Boolean Set to true if HTTP Connector should be used false UseEmail$Boolean Set to true if Email Connector should be used false UseSecureTransport$Boolean Set to true if Secure Transport connector should be used false UseMigrationConnectors$Boolean Set to true if Migration Connectors should be used false UseJMS$Boolean Set to true if JMS Connector should be used false UseMapAsAService$Boolean Set to true if Map as a service should be used false MapAsAServicePort Set port number for Map as a service if it's enabled 8869 JMSProviderName Only used if JMS Connector is enabled: Provider name for JMS Empty, must be set JMSInitialContextFactoryName Only used if JMS Connector is enabled: Initial context factory name Empty, must be set JMSConnectionFactoryName Only used if JMS Connector is enabled: Connection factory name Empty, must be set JMSProviderURL Only used if JMS Connector is enabled: Provider url Empty, must be set SAPSelectPath$Boolean Only used if SAP Connector is enabled: Set to true if SAP libraries should be copied from below the path false SAPpath Only used if SAP Connector is enabled: Path to SAP libraries Empty, must be set The following keys are used in configure mode only: Note The default values are set by the installation. Key Description Default value UseFailSafeMode$Boolean Set to true if fail safe mode should be used true UseEdifactBatchFiles$Boolean Set to true to enable EDIFACT batch file splitter true UseX12BatchFiles$Boolean Set to true to enable X12 batch file splitter true UseDmlMaps$Boolean Set to true to use DML maps true GenerateUndefinedX12Acks$Boolean Set to true to generate acknowledgements for undefined X12 transaction sets false StopDuplicateProcessing$Boolean Set to true to stop possible duplicates from being reprocessed flag false The following keys are for internal use only and should not be changed from the default; they are not required in the response file for the installation: Key B2BiCoreBuild B2BiCoreReleaseNumber B2BiDir B2BiInstallScript BuildNumber IntegratorBuild IntegratorInstallScript IntegratorPortPrefix IntegratorReleaseNumber IntegratorTargetAlias IntegratorTargetName InterchangeBuild InterchangeDBConfigCmd InterchangeDirectory InterchangeIsB2Bi InterchangeIsCsos InterchangeIsFips InterchangeReleaseNumber InterchangeUiProduct InterchangeUpgradeDbPropFile IsFarmServer LongHostName MQModeString NumberOfCPUsString PreviousVersion ProductLongName ProductShortName ProductVersion ProjectVersion ShortHostName sys.adminRights$Boolean sys.component.971$Boolean sys.component.972$Boolean sys.component.974$Boolean sys.component.976$Boolean sys.languageId sys.programGroupDisabled$Boolean sys.adminRights$Boolean Windows only B2BiWindowsServiceDisplayName B2BiWindowsServiceName InterchangeWindowsServiceDisplayName InterchangeWindowsServiceName IntegratorWindowsServiceDisplayName IntegratorWindowsServiceName sys.programGroupName sys.programGroupDisabled$Boolean Related Links
Silent mode installation A B2Bi installation requires the manual input of many configuration details, including details of data base access, B2Bi shared location, and so on. To ease the task of installation, once you have installed an instance of B2Bi, you can use the silent mode installation method to install additional instances. Install B2Bi in Silent Mode To install B2Bi in silent mode: Using the B2Bi Server installer, install B2Bi on a machine. From <B2Bi_install_directory>/.install4j copy the file response.varfile . This is a property file that completely describes the initial installation. Launch the B2Bi installer on the same machine or install on a different machine, with the following options: Unix/Linux:<B2Bi_installer_name>.sh –q -varfile <path to response file> Windows:start /wait <B2Bi_installer_name>.exe -c –q -varfile <path to response file>Note For Windows, the user account credentials for the silent install must be the same as for the original installation. Examples Unix/Linux: ./b2bi-installer-server-linux-x86-64-2.3.1.sh -c -q -varfile /home/axway/scripts/response.varfile Windows: start /wait b2bi-installer-server-linux-x86-64-2.3.1.exe -c -q -varfile D:\Axway\scripts\response.varfile Results After a successful installation, you can start B2Bi and use the product. Content of silent file The content of the silent file contains key/value pairs from the original installation. Some of these can be modified in the silent file (for example, password are encoded in the silent file) and some are generated during the installation. Generate silent file values The silent file values can be generated as follows: Start the installer with the -encode_password argument. Enter a value to be encoded. Select Exit. Locate the encoded value in the EncodedPassword.txt file (in the same directory as the installer file). Note This functionality is useful if you need to change a password field in the silent file. The following table describes the keys used for the installation. They are in the same order as they occur in the installation dialogs and grouped per dialog: Note The keys that start with Windows are used for Windows installations only. Key Description Default value sys.installationDir Main installation directory to be used %HOMEDRIVE%\Axway on Windows and {HOME}/Axway on Unix UpgradeInterchange$Boolean Set to true if Interchange should be upgraded from previous version false InterchangeUpgradeLocation Path to Interchange installation that should be upgraded, only used if UpgradeInterchange$Boolean is set to true None, must be set if used B2BiSharedDirectory Main shared directory None, must be set UseNonDefaultdirectories$Boolean Set to true if non-default directories should be used, the directories are set by the section below false IntegratorRootDir Path to where Integrator root files should be installed <sys.installationDir>/Integrator IntegratorLocalDir Path to where Integrator local files should be installed <sys.installationDir>/Integrator/local IntegratorDataDir Path to where Integrator data files should be installed <sys.installationDir>/Integrator/data B2BiSolutionDir Path to where B2Bi core should be installed <sys.installationDir>/Integrator/solutions B2BiTmpDir Path to B2Bi temporary directory to be used <sys.installationDir>/Integrator/data/tmp B2BiSharedRootDir Path to B2Bi shared root directory <B2BiSharedDirectory>/root B2BiSharedDataDir Path to B2Bi shared data directory <B2BiSharedDirectory>/data B2BiSharedLocalDir Path to B2Bi shared local directory <B2BiSharedDirectory>/local InterchangeSharedDir Path to Interchange shared directory <B2BiSharedDirectory>/common InterchangeLicenseFile Full path to license file for Interchange None, must be set InterchangeDatabaseType$Integer Database type for Interchange, 0=MySQL, 1=Oracle, 2=Microsoft SQL Server, 3=DB2 2 (Microsoft SQL Server) InterchangeDBName Name of database to be used None, must be set InterchangeDBServerName Host name of database server localhost InterchangeDBPort$Long Port number to database Default port for database type selected InterchangeDBUserName Name of database user None, must be set InterchangeDBPassword.encoded Encoded database password None, must be set InterchangeDBPasswordConfirm.encoded Confirmation of encoded database password, should be same as above None, must be set InterchangeSkipDBVerification$Boolean Set to true if no check should be made of the database connection false UsePassport$Boolean Set to true if PassPort should be used, otherwise false. The keys below are only needed if PassPort should be used. false PP_HOST Name of PassPort host Current hostname PP_PORT$Long Port used by PassPort 6453 PP_SHARED_SECRET Shared secret key used when connecting to PassPort admin PP_SHARED_SECRET_CONFIRM Confirmation of the above admin PortRangeMin$Long Start value for port range, 371 free ports are needed 8832 PortRangeMax$Long End value for port range 10000 WindowsServiceNamePrefix Prefix to be used for Windows Service name Axway WindowsServiceDisplayNamePrefix Prefix to be used for Windows Service description Axway WindowsServiceUserName User name for the Windows Service account Must be current user (%USERNAME%) WindowsServiceDomain Domain name for the above user Must be domain for current user (%USERDOMAIN%) WindowsServicePassword.encoded Password for the user None, must be set EnableFarmServer$Boolean Set to true if this installation is connecting to a Farm server false FarmServerHostName Host name where the Farm server are installed Dummy value <HOST>, must be changed FarmServerPort Port used to connect to the Farm server 8852 NumberOfCPUs$Integer Number of CPU's, 0=2, 1=4, 2=8, 3=16 0 MessageSizeLimit Message size limit for caching message content in memory 16384 UseSentinel$Boolean Set to true if Sentinel should be used false EnableOnlineArchive$Boolean Set to true if online archive should be used false UseMQ$Boolean Set to true if MQ Connector should be used false MQMode$Integer Mode for MQ Connector if enabled, 0=server, 1=client 0 UseWebEdi$Boolean Set to true if WebEdi should be used false UseSAP$Boolean Set to true if SAP Connector should be used false UseUnicode$Boolean Use if SAP Connector have been enabled, set to true to use Unicode false UseFTP$Boolean Set to true if FTP Connector should be used false UseFile$Boolean Set to true if File Connector should be used false UseHTTP$Boolean Set to true if HTTP Connector should be used false UseEmail$Boolean Set to true if Email Connector should be used false UseSecureTransport$Boolean Set to true if Secure Transport connector should be used false UseMigrationConnectors$Boolean Set to true if Migration Connectors should be used false UseJMS$Boolean Set to true if JMS Connector should be used false UseMapAsAService$Boolean Set to true if Map as a service should be used false MapAsAServicePort Set port number for Map as a service if it's enabled 8869 JMSProviderName Only used if JMS Connector is enabled: Provider name for JMS Empty, must be set JMSInitialContextFactoryName Only used if JMS Connector is enabled: Initial context factory name Empty, must be set JMSConnectionFactoryName Only used if JMS Connector is enabled: Connection factory name Empty, must be set JMSProviderURL Only used if JMS Connector is enabled: Provider url Empty, must be set SAPSelectPath$Boolean Only used if SAP Connector is enabled: Set to true if SAP libraries should be copied from below the path false SAPpath Only used if SAP Connector is enabled: Path to SAP libraries Empty, must be set The following keys are used in configure mode only: Note The default values are set by the installation. Key Description Default value UseFailSafeMode$Boolean Set to true if fail safe mode should be used true UseEdifactBatchFiles$Boolean Set to true to enable EDIFACT batch file splitter true UseX12BatchFiles$Boolean Set to true to enable X12 batch file splitter true UseDmlMaps$Boolean Set to true to use DML maps true GenerateUndefinedX12Acks$Boolean Set to true to generate acknowledgements for undefined X12 transaction sets false StopDuplicateProcessing$Boolean Set to true to stop possible duplicates from being reprocessed flag false The following keys are for internal use only and should not be changed from the default; they are not required in the response file for the installation: Key B2BiCoreBuild B2BiCoreReleaseNumber B2BiDir B2BiInstallScript BuildNumber IntegratorBuild IntegratorInstallScript IntegratorPortPrefix IntegratorReleaseNumber IntegratorTargetAlias IntegratorTargetName InterchangeBuild InterchangeDBConfigCmd InterchangeDirectory InterchangeIsB2Bi InterchangeIsCsos InterchangeIsFips InterchangeReleaseNumber InterchangeUiProduct InterchangeUpgradeDbPropFile IsFarmServer LongHostName MQModeString NumberOfCPUsString PreviousVersion ProductLongName ProductShortName ProductVersion ProjectVersion ShortHostName sys.adminRights$Boolean sys.component.971$Boolean sys.component.972$Boolean sys.component.974$Boolean sys.component.976$Boolean sys.languageId sys.programGroupDisabled$Boolean sys.adminRights$Boolean Windows only B2BiWindowsServiceDisplayName B2BiWindowsServiceName InterchangeWindowsServiceDisplayName InterchangeWindowsServiceName IntegratorWindowsServiceDisplayName IntegratorWindowsServiceName sys.programGroupName sys.programGroupDisabled$Boolean