Before you begin
Ensure that you have the relevant prerequisite files for
your Siebel system.
Siebel Business Applications Versions 7.5 and earlier
- SiebelJI_language code.jar (for
example, SiebelJI_enu.jar)
- SiebelJI_Common.jar
- Siebel Business Applications Versions 7.7x, 7.8x, and 8.0
- Siebel.jar
- SiebelJI_language code.jar (for
example, SiebelJI_enu.jar)
Download these files from the Siebel application, and
save them to a directory, such as C:\Siebel_LIB. (On Windows, the directory
cannot be a mapped network drive on a remote Windows computer; the directory
must be local or on a Storage Area Network (SAN) disk.)
The sample resources that you need to set up the Siebel
system so that it can communicate with the integration node are
in the following directory: install_dir\tools\ResourceAdapters\Siebel_version.
About this task
Locating the Siebel support files in the runtime environment
on Windows
To add
the Siebel prerequisite files to the runtime environment, take the
following steps.
Procedure
- Ensure that the integration node has started.
- Either open the Command Console, or open a Windows command prompt and enter mqsiprofile to initialize the
environment.
- Enter the following command to display the locations of
the prerequisite JAR files and native libraries:
mqsireportproperties IBNODE -c AllTypes -o AllReportableEntityNames -r
The
following example shows what typically is displayed when you
run this command:ReportableEntityName=''
EISProviders
JDEdwards=''
jarsURL='default_Path'
nativeLibs='default_Path'
PeopleSoft=''
jarsURL='default_Path'
nativeLibs='default_Path'
SAP=''
jarsURL='default_Path'
nativeLibs='default_Path'
Siebel=''
jarsURL='default_Path'
nativeLibs='default_Path'
siebelPropertiesURL=''
- Set the location of the Siebel prerequisite files by using
the mqsichangeproperties command;
for example:
mqsichangeproperties IBNODE -c EISProviders -o Siebel -n jarsURL -v C:\Siebel_LIB
mqsichangeproperties IBNODE -c EISProviders -o Siebel -n nativeLibs -v C:\Siebel_LIB
- Optional: To connect to a server in a clustered
environment, complete the following steps.
- If you do not already have a siebel.properties file,
create one with a siebel.conmgr.virtualhosts property
that lists the Siebel servers in the cluster. The siebel.conmgr.virtualhosts property
is the only property in the siebel.properties file
that IBM® Integration Bus supports. The server
names are represented by a comma separated list in the format hostname:port.
- Set the location of the siebel.properties file
by using the mqsichangeproperties command;
for example:
mqsichangeproperties IBNODE -c EISProviders -o Siebel -n siebelPropertiesURL
-v C:\siebel.properties
Information message BIP3427 indicates
if a siebel.properties file is being used, and
error message BIP3428 indicates if a problem occurs
when attempting to access the siebel.properties file.
- Optional: To connect to different versions of
Siebel, follow the instructions in Connecting to different versions of Siebel.
- To check that the values have been set correctly, run the
following command:
mqsireportproperties IBNODE -c EISProviders -o Siebel -r
The
following example shows what is displayed by the mqsireportproperties command.ReportableEntityName=' '
EISProviders
Siebel=' '
jarsURL='C:\Siebel_LIB'
nativeLibs='C:\Siebel_LIB'
siebelPropertiesURL=''
BIP8071I: Successful command completion.
- Restart the integration node.