IBM Integration Bus, Version 9.0.0.8 Operating Systems: AIX, HP-Itanium, Linux, Solaris, Windows, z/OS

See information about the latest product version

Connecting to different versions of Siebel

You can access multiple versions of Siebel from a single broker by using different versions of the client libraries.

You can connect to different versions of Siebel by creating a custom EISProviders configurable service and setting the location of the appropriate library files. You can then configure an integration server so that all Siebel nodes use this custom configurable service. Therefore, you can connect to different versions of a Siebel server from two different integration servers in the same broker.

You can complete this task by using the command line, the IBM® Integration Explorer, or the IBM Integration API (CMP). For more information about using the IBM Integration Explorer, see Using the IBM Integration Explorer to work with configurable services. For more information about using the CMP, see Developing applications that use the IBM Integration API. This topic describes how to connect to different versions of Siebel by using the command line.

For each version of Siebel to which you want to connect, create a custom EISProviders configurable service by using the mqsicreateconfigurableservice command, as shown in the following example.
```
mqsicreateconfigurableservice IB9NODE -c EISProviders -o EISProvidersName -n jarsURL -v "c:\siebelclient\"
```
The -o parameter specifies the name of the EIS provider, and the -n and -v parameters are used to specify the file location of the EIS provider JAR files.
Configure your integration server to use the custom EISProviders configurable service by using the mqsichangeproperties command, as shown in the following example.
```
mqsichangeproperties IB9NODE –e  IntegrationServerLabel –o ComIbmSiebelManager  –n EISProviders –v EISProvidersName
```
Restart the integration server by using the mqsistartmsgflow command, or in the IBM Integration Toolkit by right-clicking the integration server and clicking Start.
Deploy message flows to the appropriate integration server.

bc22840_.htm |

Last updated Friday, 21 July 2017