This chapter describes how to integrate the Enterprise Data Quality (EDQ) Siebel Connector with an existing Siebel server.
This chapter includes the following sections:
Section 2.1, "Integrating the EDQ Siebel Connector With a Windows Siebel Server"
Section 2.2, "Integrating the Connector With AIX, Linux, and Solaris Siebel Servers"
Use the following steps to integrate the connector with a Windows Siebel server. The siebelconnector.zip
is automatically installed into the EDQ Oracle Home when you run the EDQ installer.
Copy the siebelconnector.zip
file from the EDQ Oracle Home to the installation directory on the Siebel server.
Extract the siebelconnector.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.
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.7/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
The dnd.properties
file in the Siebel Connector installation directory configures how the connector communicates with EDQ. In most cases, the connector is configured to connect to an EDQ server with EDQ-CDS installed. Some settings in this file will need editing to reflect your particular environment; for more information, see Section 3.1, "Configuring the EDQ Siebel Connector".
Use the following steps to integrate the connector with an AIX, Linux, or Solaris Siebel server. The siebelconnector.zip
is automatically installed into the EDQ Oracle Home when you run the EDQ installer.
Copy the siebelconnector.zip
file from the EDQ Oracle Home to the installation directory on the Siebel server.
Extract the siebelconnector.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
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.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.7/lib/i386/client/libjvm.so directory: /opt/siebel/dnd/install
Note:
The Siebel Connector requires the Oracle JRE/JDK version 1.7 or later.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
The dnd.properties
file in the Siebel Connector installation directory configures how the connector communicates with EDQ. In most cases, the connector is configured to connect to an EDQ server with EDQ-CDS installed. Some settings in this file will need editing to reflect your particular environment; for more information, see Section 3.1, "Configuring the EDQ Siebel Connector".
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:
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.7 or later, 32- or 64-bit. The JRE must be either the Oracle (Sun) JRE, or the IBM JRE.Restart Siebel and perform further tests.
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
).