The WBI Siebel connectivity DLL is installed as part of the Siebel suite of products. When you are running the WBI CD installation program, choose Siebel for your installation. The installation puts the Siebel connectivity DLL in the following folders, depending on which version of Siebel you are using:
Siebel 7.0.x
ProductDir\connectors\Siebel\SiebelEAIAdapter\Siebel7.0.x
Siebel 7.5.x
ProductDir\connectors\Siebel\SiebelEAIAdapter\Siebel7.5.x
The other components are installed under the following folder:
ProductDir\connectors\Siebel\SiebelEAIAdapter
This section describes how to configure and set up the WBI Siebel connectivity DLL.
To add the [collabdetails] section (the Collaboration Name, Generic BO Name, PortName etc.), you must edit IBMCrossWorlds.cfg file. You can find a copy of the file in the %ProductDir%connectors\Siebel\SiebelEAIAdapter\Samples directory. The file should contain the items listed in Table 11.
Table 11. IBMCrossWorlds.cfg file contents
Item | Description |
---|---|
SERVERNAME | Name of your interchange server. |
USERNAME | Siebel application user name. |
PASSWORD | Siebel application password. |
[CollabDetails] | Details for each collaboration that is being used. For example, an
account object would include:
[CollabDetails]
IntObjName=Account
BOName=NewSiebel_Account
CollabName=SiebelConnectivityObject
PortName=From
[EndCollabDetails] |
Copy the following files from the install folder to the %Siebel%/Client/bin directory:
When the InterChange Server is started, it generates an .ior file, the persistent object reference to the interchange server access engine object. The name of the file is [Server Name] InterChangeServer.ior and can be found in %WBIA%. Copy this file to the %Siebel%/Client/bin directory. Each time the ICS starts, it generates a new .ior file. To keep the contents of this .ior file the same for every boot of interchange server, a persistent .ior file is generated. To have the server generate a persistent .ior file, edit the InterchangeSystem.cfg file, and add a subsection for CORBA, if one does not already exist.
The CORBA subsection contains the port number in the format: OAport=portnumber. For example, if the port number is 15000, add the following lines to the InterchangeSystem.cfg file:
[CORBA]USERNAME=Siebel Application user name OAport=15000
If the access client is in the DMZ and InterChange Server is on a different subnet, make sure that the port number for the OAport is open.
Generate a IBM business object definition for every integration object using XMLborgen or XMLODA. The object generated will be used by the workflow process. The business objects generated are automatically loaded into the interchange server repository.
The XML DataHandler is a data-conversion module whose primary role is to convert business objects to and from XML documents. An XML document is serialized data with the text/xml MIME type. This XML document is called from within the server access interface. To configure the XML DataHandler, the configuration information must be provided in the XML child meta-object. For the XML DataHandler, WebSphere business integration system delivers the default meta-object MO_DataHandler_DefaultXMLConfig. Table 12 shows attributes contained in the meta-objects that must be configured.
Table 12. Attributes contained in the meta-object
Attribute | Description |
---|---|
BOPrefix | The WBIA Business Object Name with the appropriate prefix is given in the configuration file. Hence, this attribute should be left blank. |
ClassName | The ClassName attribute, by default, will point to XML DataHandler class that is invoked by the server access interface. The default value is com.crossworlds.DataHandlers.text.xml. |
Define a collaboration template and create a collaboration object for the business process. For more details on defining collaboration templates and creating collaboration objects, refer to the "Collaboration development Guide".
To import the business service:
Follow the workflow process set up described in the Siebel documentation and add the business service trigger. This trigger will call the IBMsiebelConnectivityService into action. The method name needs to be set by the workflow according to the process that needs to be performed.