Connecting to different versions of Siebel

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

About this task

You can connect to different versions of Siebel by configuring integration servers to use different library files. You can then connect to different versions of a Siebel server from two different integration servers.
The integration server configuration file (server.conf.yaml) contains a section for connector providers, which defines the location of the required JAR files and native libraries, as you can see in the following example:
ConnectorProviders:
  SiebelConnectorProvider:
    jarsURL: default_Path      # Set to the absolute path containing the Siebel JAR files
    siebelPropertiesURL: ''    # Set to the absolute path containing the Siebel properties file
    nativeLibs: default_Path   # Set to the absolute path containing the Siebel libraries
By default, the location is set to default_Path, which indicates that the JAR files and libraries can be found in the integration server's shared-classes directory.

Procedure

To configure integration servers with the locations of required JAR files and libraries, complete the following steps:

  1. Use a YAML editor to open the server.conf.yaml file, then find the ConnectorProviders section.

    You can edit the file by using the built-in YAML editor that is provided in the IBM® App Connect Enterprise Toolkit, either by double-clicking the file in the Application Development view or by right-clicking the file and selecting Open with > YAML editor. If you choose to edit the file by using a plain text editor, ensure that you do not include any tab characters (which are not valid in YAML) and use a YAML validation tool to validate the contents of your file.

    For more information, see Configuring an integration server by modifying the server.conf.yaml file.
  2. For the Siebel connector provider, set the jarsURL property to the absolute path where the JAR files are stored.
  3. Set the nativeLibs property to the absolute path where the native libraries are stored.
  4. Save the server.conf.yaml file.
  5. Repeat these steps to specify the file locations for an alternative version of the Siebel server on a second integration server.
  6. Restart the integration servers.
  7. Deploy the message flows that contain Siebel nodes to the appropriate integration server.