Oracle Application Server InterConnect Adapter for Siebel 7 Installation and User's Guide 10g (9.0.4) Part Number B10448-01 |
|
This chapter describes installation and configuration of the Siebel 7 adapter. This chapter discusses the following topics:
This section contains these topics:
The Siebel 7 adapter must be installed in one of the following Oracle homes:
Consult the following guides before proceeding with Siebel 7 adapter installation:
To install the Siebel 7 adapter:
Consider the following scenarios:
The hub database information, such as the SID, host, port, and username/password from the Hub installation is needed for step 2.
Note:
mySiebel7App
.
Platform | Directory |
---|---|
Windows |
|
UNIX |
|
Application
is the value you specified in Step 3 .
Table 2-2, Table 2-3, and Table 2-4 describe executable files, configuration files, and directories. These files and directories are accessible from the directory shown in Table 2-1:
Table 2-1 Siebel 7 Adapter Directory
On... | Go to... |
---|---|
UNIX |
|
Windows |
|
Adapters do not have integration logic. The Siebel 7 adapter has a generic transformation engine that processes metadata from the repository as runtime instructions to do transformations. The application defines for an adapter what its capabilities are. For example, it can define what messages it can publish, what messages it can subscribe to, and what are the transformations to perform. The application parameter allows the adapter to become smart in the context of the application to which it is connected. It allows the adapter to retrieve from the repository only that metadata that is relevant to the application. The application parameter must match the corresponding application that will be defined in iStudio under the Applications folder.
If you are using pre-packaged metadata, after importing the pre-packaged metadata into the repository, start up iStudio to find the corresponding application (under the Applications folder in iStudio) to use as the application for the adapter you are installing (unless the package you are using provides directions for what the application should be).
This section contains these topics:
The Siebel 7 adapter connects to the hub database using parameters from the hub.ini
file located in the hub directory. The following table lists the parameter name, a description for each parameter, the possible and default values, and an example.
When a hub is installed on a Real Application Clusters (RAC) database, parameters listed in Table 2-5 represent information on additional nodes used for connection and configuration. These parameters are added on top of the default parameters which represent the primary node. In Table 2-5, x
represent the node number, which varies between 2 and the number of nodes. For example, if the Real Application Clusters setup contains 4 nodes, x
can take a value between 2
and 4
.
The Siebel 7 adapter connects to the spoke application using parameters from the adapter.ini
file. Table 2-6 lists the parameter name, description, the possible and default values, and example of each parameter.
Parameter | Description | Example |
---|---|---|
|
The name of the application this adapter connects to. This must match with the name specified in iStudio during creating of metadata. Any alphanumeric string can be used. There is no default value. |
|
|
The partition this adapter handles as specified in iStudio. Any alphanumeric string is a possible value. There is no default value. |
|
|
To have multiple adapter instances for the given application with the given partition, each adapter should have a unique instance number. Possible values are any integer greater than 1. There is no default value. |
|
|
The amount of logging. Possible values are:
The default value is |
|
|
The subscriber name used when this adapter registers its subscription. The possible value is a valid Oracle Advanced Queuing subscriber name. There is no default value. |
|
|
Specifies conditions for message selection when registering its subscription with the hub. The possible value is a valid Oracle Advanced Queuing message selector string. There is no default value. |
|
|
The subscriber name used when multiple adapter instances for the given application with the given partition are used. Optional if there is only one instance running. The possible value is application name ( |
|
|
Used only if multiple adapter instances for the given application with the given partition. The possible value is a string built using concatenating application name ( |
|
|
Specifies if message tracking is enabled. Set to |
|
|
Specifies if throughput measurement is enabled. Set to |
|
|
Specifies if a custom data type definition (DTD) should be used for the common view message when handing it to the hub. By default, adapters use an OracleAS InterConnect-specific DTD for all messages sent to the hub as other OracleAS InterConnect adapters will be retrieving the messages from the hub and know how to interpret them. Set to |
|
|
Specifies the metadata caching algorithm. Possible values are:
The default value is |
|
|
Specifies the domain value mapping (DVM) caching algorithm. Possible values are:
The default value is |
|
|
Specifies the lookup table caching algorithm. Possible values are:
The default value is |
|
|
With any of the agent caching methods enabled, metadata from the repository is cached locally on the file system.
Set this parameter to Note: After changing metadata or DVM tables for this adapter in iStudio, you must delete the cache to guarantee access to the new metadata or table information.
The default value is |
|
|
Specifies the maximum number of application objects' metadata to cache. Possible values are any integer greater than 1. The default value is |
|
|
Specifies the maximum number of common objects' metadata to cache. Possible values are any integer greater than 1. The default value is |
|
|
Specifies the maximum number of messages' metadata to cache (publish/subscribe and invoke/implement). Possible values are any integer greater than 1. The default value is |
|
|
Specifies the maximum number of DVM tables to cache. Possible values are any integer greater than 1. The default value is |
|
|
Specifies the maximum number of lookup tables to cache. Possible values are any integer greater than 1. The default value is |
|
|
Specifies the maximum size that internal OracleAS InterConnect message queues can grow. Possible values are any integer greater than 1. The default value is |
|
|
Specifies the maximum size that internal OracleAS InterConnect persistence queues can grow. Possible values are any integer greater than 1. The default value is |
|
|
Specifies how often the persistence cleaner thread should run. Possible values are any integer greater than 30000 milliseconds. The default value is |
|
|
Specifies how often the persistence thread should retry when it fails to push a OracleAS InterConnect message. Possible values are any integer greater than 5000 milliseconds. The default value is |
|
|
Specifies how to turn on or off the pipeline for messages from the Bridge towards the hub. If set to |
|
|
Specifies how to turn on or off the pipeline for messages from the hub towards the Bridge. If you set the pipeline to |
|
|
Windows only. The value that the environment variable PATH should be set to. Path is set to the specified value before forking the Java VM. Typically, all directories containing all necessary DLLs should be listed here. Possible values are the valid path environment variable setting. There is no default value. |
|
|
The classpath used by the adapter Java VM. If a custom adapter is developed and as a result, the adapter is to be used to pick up any additional jars, add the jars to the existing set of jars being picked up. Possible values are the valid classpath. There is no default value. |
|
|
The entry class for the Windows service. The possible value is |
|
|
Windows only. The maximum size to which the Java VM's stack can grow. Possible values are the valid Java VM maximum native stack size. The default value is the default for the Java VM. |
|
|
Windows only. The maximum size to which the Java VM's native stack can grow. Possible values are the valid Java VM maximum native stack size. The default value is the default for the Java VM. |
|
|
Windows only. Specifies the minimum heap size for the adapter Java VM. Possible values are the valid Java VM heap sizes. The default value is the default Java VM heap size. |
|
|
Windows only. Specifies the maximum heap size for the adapter Java VM. Possible values are any valid Java VM heap sizes. The default value is |
|
|
Windows only. The number of |
|
|
Windows only. Specifies any additional arguments to the Java VM. For example, to get line numbers in any of the stack traces, set |
|
|
Windows only. The JDK version the adapter Java VM should use. The default value is |
|
|
Windows only. The dll the adapter Java VM should use. The default value is |
|
|
Format for date fields expressed as string. The following pattern letters are defined. All other characters from A to Z and from a to z are reserved.
The default date format is Note: This parameter specifies date format. It is applicable for the date format only. |
Date format pattern
Multiple date format can be specified as
|
|
This parameter is a valid ISO Country Code. These upper-case and two-letter codes are defined by ISO-3166. You can find a full list of these codes at a Web site, such as,
The default Country code is Note: This parameter specifies date format. It is applicable for the date format only. |
|
|
This parameter is a valid ISO Language Code. These lower-case and two-letter codes are defined by ISO-639. You can find a full list of these codes at a Web site, such as,
The default language code is Note: This parameter specifies date format. It is applicable for the date format only. |
|
|
Character encoding for published messages. The adapter uses this parameter to generate encoding information in encoding tag of transformed OracleAS InterConnect message. OracleAS InterConnect represents messages internally as an XML document. The default encoding of the XML document is |
|
|
The CORBA port number on which the adapter CORBA service listens. Generally, this port is allocated dynamically. However, it can be configured to enable access across firewall. |
|
The following table lists the parameters specific to the Siebel 7 adapter.
Parameter | Description | Example |
---|---|---|
|
This indicates the entry class for the Siebel 7 adapter. Do not modify this value. There is no default value. |
|
On UNIX, start the Siebel 7 adapter using the start
script in the following directory:
$ORACLE_HOME/oai/9.0.4/adapters/Application
Type start, then press Enter.
On Windows, start the Siebel 7 adapter from the Services window available from the Start menu.
On... | Choose... |
---|---|
Windows NT |
Start > Settings > Control Panel > Services |
Windows 2000 |
Start > Settings > Control Panel > Administrative Tools > Services |
The Services window appears.
On... | Choose... |
---|---|
Windows NT |
Choose Start. |
Windows 2000 |
Right click the service and choose Start from the menu. |
On UNIX, stop the Siebel 7 adapter using the stop
script in the following directory:
$ORACLE_HOME/oai/9.0.4/adapters/Application
Type stop, then press Enter.
On Windows, stop the adapter from the Services window available from the Start menu.
On... | Choose... |
---|---|
Windows NT |
Start > Settings > Control Panel > Services |
Windows 2000 |
Start > Settings > Control Panel > Administrative Tools > Services |
The Services window appears.
On... | Choose... |
---|---|
Windows NT |
Choose Stop. |
Windows 2000 |
Right click the service and choose Stop from the menu. |
You may verify the stop status by viewing the oailog.txt
files in the appropriate time stamped subdirectory of the log
directory within the adapter directory.
|
![]() Copyright © 2002, 2003 Oracle Corporation. All Rights Reserved. |
|