This chapter describes how to install the Enterprise Data Quality (EDQ) Siebel Connector with an existing Siebel server.
This chapter includes the following sections:
Section 2.1, "Installing the EDQ Siebel Connector With a Windows Siebel Server"
Section 2.2, "Installing the Connector With AIX, Linux, and Solaris Siebel Servers"
Use the following steps to install the connector with a Windows Siebel server.
Copy the dnd.dll file to the Siebel_Server_root\bin\ directory.
Create a file in the Siebel_Server_root\SDQConnector\ directory with the name dnd.parms. This file will be used to point to the installation directory on the same server where the Siebel connector will run. The file must contain the following lines:
javalib: [location of the JRE]/bin/client/jvm.dll directory: [the installation directory for the connector]
For example:
javalib: C:/Program Files/Java/jre1.6/bin/client/jvm.dll directory: C:/SiebelConnector
Note:
The Siebel connector is not language specific so is not installed in a specific language directory.
(Optional) If detailed trace information on connector requests is required (for example, for temporary debugging purposes) add the following lines to the dnd.parms file to enable logging:
logfile: sdq%05d.log jlogfile: jsdq%05d.log
Extract the siebelconnector-11_1_N(N).zip file into the installation directory specified in the dnd.parms file (the default being Siebel_Server_root\dnd\install .)
This installs the following files:
Jar files for the connector.
Library jar files needed by the connector.
The EDQ Siebel Connector requires the dnd.properties configuration properties file to be the same location. This file configures the EDQ Siebel Connector connection details to EDQ. In most cases, the connector is configured to connect to an EDQ server with EDQ-CDS installed. EDQ-CDS provides an example dnd.properties file, which only requires simple edits to configure the Connector to use the provided services. To use this file, extract it from the edq-cds-11_1_N(N).zip file into the installation directory.
Use the following steps to integrate the connector with an AIX, Linux, or Solaris Siebel server.
Copy the libdnd.so driver file to the Siebel_Server_root/lib directory. The driver files for each OS are held in the native sub-directory of the siebelconnector-11_1_N(N).zip file in the EDQ distribution, as follows:
/native/aix/ppc/ or /native/ppc64, depending on whether a 32-bit or 64-bit version of Siebel is in use.
/native/linux
/native/sparcv9
Create a file in the Siebel_Server_root/SDQConnector directory with the name dnd.parms. This file is used to point to the installation directory on the same server where the EDQ Siebel Connector will run. The file must contain the following lines:
javalib: [location of the JRE]/lib/i386/client/libjvm.so directory: [the installation directory for the connector]
For example:
javalib: /usr/java/jre1.6/lib/i386/client/libjvm.so directory: /opt/siebel/dnd/install
If detailed trace information on connector requests is required, for example for temporary debugging purposes, add the following lines to the dnd.parms file to enable logging:
logfile: sdq%05d.log jlogfile: jsdq%05d.log
Extract the siebelconnector-11_1_N(N).zip file into the installation directory specified in the dnd.parms file (the default being /opt/siebel/dnd/install).
This installs the following files:
Jar files for the connector
Library jar files needed by the connector
The EDQ Siebel Connector also requires a configuration properties file called dnd.properties in the same location. This file configures the EDQ Siebel Connector's connection details to EDQ. In most cases, the connector is configured to connect to an EDQ server with the EDQ-CDS Pack installed. EDQ-CDS provides an example dnd.properties file, which only requires simple edits to configure the Connector to use the provided services. To use this file, extract it from the edq-cds-11_1_N(N).zip file into the installation directory.
In scenarios where Siebel Java Business Services (like the Siebel Java Message Service) are deployed, the EDQ Siebel Connector may conflict with them causing it to fail.
To avoid this conflict, the connector must be configured post-installation to connect to a separate Java process using the following steps:
Extract the siebelconnector-11_1_N(N).zip file into the installation directory specified in the dnd.parms file (by default, /opt/siebel/dnd/install).
This installs the following files:
Jar files for the connector.
Library jar files needed by the connector.
Ensure that the libdnd.so or dnd.dll files used are up-to-date with the current release.
Edit the dnd.properties file as required for the environment.
Open the dnd.parms file, and add the following line to turn on remote mode:
remote: true
The directory and javalib lines are no longer used, although they can be left in the file.
In the Siebel Connector installation directory, run the following command to start the Java code as a server:
java -jar connector.jar [-p portnum] [directory_path]
Where:
-p portnum should be used only if the connector must listen on a port other than the default port of 8642. Specify an available TCP/IP port number to use. If using this argument, also add the same port number to the dnd.params file, as follows:
port: portnum
directory_path should be used only if the dnd.properties file is located somewhere other than in the same directory as the connector.jar file (the default). Specify the path to the directory where dnd.properties is stored.
Note:
The version of the JRE can be version 1.6 or later, 32- or 64-bit. The JRE must be either the Oracle (Sun) JRE, or the IBM JRE.
In some instances, the install directory (containing the .jar files and dnd.properties) is not on the same system as the Siebel instance. If this is the case, add a host line to dnd.parms to specify the host running the Siebel Java code (for example, host: HOSTNAME).