WebSphere Message Broker, Version 8.0.0.7 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 execution group so that all Siebel nodes use this custom configurable service. Therefore, you can connect to different versions of a Siebel server from two different execution groups in the same broker.

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

  1. 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 MB8BROKER -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.
  2. Configure your execution group to use the custom EISProviders configurable service by using the mqsichangeproperties command, as shown in the following example.
    mqsichangeproperties MB8BROKER –e  ExecutionGroupLabel –o ComIbmSiebelManager  –n EISProviders –v EISProvidersName
  3. Restart the execution group by using the mqsistartmsgflow command, or in the WebSphere Message Broker Toolkit by right-clicking the execution group and clicking Start.
  4. Deploy message flows to the appropriate execution group.
Notices | Trademarks | Downloads | Library | Support | Feedback

Copyright IBM Corporation 1999, 2016Copyright IBM Corporation 1999, 2016.

        
        Last updated:
        
        Last updated: 2016-05-23 14:47:50


Task topicTask topic | Version 8.0.0.7 | bc22840_