Follow the instructions in one of the following sections to install an adapter if indicated by the procedural overview in Overview of installation:
Note that on UNIX platforms, filenames are case-sensitive. If you change the case of any filename, the adapter will fail during start-up and log an error. If you receive an error when you attempt to start the adapter, check the filenames of the XSD files in the Connector Configurator repository. The XSD files must have a lower-case .xsd extension. For example, a filename of Customer.XSD will cause the adapter to fail. In this case, you must change the name of the file to Customer.xsd.
Do the following to install an adapter using the graphical installer:
You may specify another directory, but it must contain an installation of a compatible version of the Adapter Framework.
For information on installing the Adapter Framework, see Installing the adapter framework. For more information on installing WebSphere InterChange Server, see the
At the product directory screen, perform one of the following tasks:
Do the following to perform a silent installation of an adapter on Windows systems:
Option name | Option values |
---|---|
-W destination.path |
Set this option to the directory path in which the WebSphere Business Integration Adapters product is to be installed. For example, -W destination.path="C:\IBM\WebSphereAdapters" The install path cannot contain any spaces. The install location must contain a compatible version of the adapter framework. |
-W inputServer.name |
If your broker is IBM WebSphere InterChange Server, specify a valid InterChange server name. This name must meet the following criteria: 1. Less than 80 characters. 2. Must not contain space. 3. Must begin with an English alphabetical character (a-z, A-Z). 4. Must contain only English alphabetical and numeric characters. If you are not using WebSphere Interchange Server as the broker, comment out this option. |
-W inputShortcuts.folder |
Set this option to the name of the program group created for the WBIA product, for example IBM WebSphere Business Integration Adapters. |
-W inputServer.adapterService |
Set this option to yes if you want the adapter to be registered as a Windows service. Set this option to no if you do not want the adapter to be registered as a Windows service. |
-G createDirectoryResponse= | Set this option (yes or no) to specify whether to create the destination directory if it does not already exist. |
-G replaceExistingResponse |
Set this option to yesToAll or yes to replace all files found on the system that have the same name as those being copied by the installer. Set this option to noToAll or no to not replace any files found on the system that have the same name as those being copied by the installer. |
-G replaceNewerResponses |
Set this option to yesToAll or yes to replace all files found on the system that are newer than those being copied by the installer. Set this option to noToAll or no to not replace any files found on the system that are newer than those being copied by the installer. |
-G removeExistingResponse |
This option specifies whether to remove a response file that exists on the system. Note that this option is for uninstall only. Set this option to yestoall or yes to remove existing response files. Set it to notoall or no to leave existing files on the system. |
-G removeModifiedResponse |
This option specifies whether to remove a response file that has been modified since it was last installed. Note that this option is for uninstall only. Set this option to yestoall or yes to remove response files that have been modified. Set it to notoall or no to leave modified files on the system. |
Do the following to perform a silent installation of an adapter on Windows systems:
Option name | Option values |
---|---|
-W destination.path |
Set this option to the directory path in which the WebSphere Business Integration Adapters product is to be installed. For example, -W destination.path="C:\IBM\WebSphereAdapters" The install path cannot contain any spaces. The install location must contain a compatible version of the adapter framework. |
-W inputServer.name |
If your broker is IBM WebSphere InterChange Server, specify a valid InterChange server name. This name must meet the following criteria: 1. Less than 80 characters. 2. Must not contain space. 3. Must begin with an English alphabetical character (a-z, A-Z). 4. Must contain only English alphabetical and numeric characters. If you are not using WebSphere Interchange Server as the broker, comment out this option. |
-G createDirectoryResponse= | Set this option (yes or no) to specify whether to create the destination directory if it does not already exist. |
-G replaceExistingResponse |
Set this option to yesToAll or yes to replace all files found on the system that have the same name as those being copied by the installer. Set this option to noToAll or no to not replace any files found on the system that have the same name as those being copied by the installer. |
-G replaceNewerResponses |
Set this option to yesToAll or yes to replace all files found on the system that are newer than those being copied by the installer. Set this option to noToAll or no to not replace any files found on the system that are newer than those being copied by the installer. |
-G removeExistingResponse |
This option specifies whether to remove a response file that exists on the system. Note that this option is for uninstall only. Set this option to yestoall or yes to remove existing response files. Set it to notoall or no to leave existing files on the system. |
-G removeModifiedResponse |
This option specifies whether to remove a response file that has been modified since it was last installed. Note that this option is for uninstall only. Set this option to yestoall or yes to remove response files that have been modified. Set it to notoall or no to leave modified files on the system. |
You can record your installation selections to a file by using a special option when invoking the installation program from the command line. At the completion of the install, your installation selections are recorded to the file you specified on the command line. You can use the recorded installation information in this file as a record of your installation settings and as a response file for silent installations on other machines.
To create this file, type the following command from the command line:
<installation launcher executable> -options-record <filename>
For example, type the following command in a command window to record the installation selections of your adapter installation on a Windows computer:
setupwin32.exe -options-record C:\data\settings.txt