Oracle Application Server InterConnect Adapter for DB Installation and User's Guide 10g (9.0.4) Part Number B10415-01 |
|
This chapter describes installation and configuration of the Database adapter. The following topics are discussed:
This section contains these topics:
The Database adapter must be installed in one of the following Oracle homes:
Consult the following guides before proceeding with Database adapter installation:
To install the Database adapter, start the installer and complete the following steps:
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:
myDBApp
.
The information on this page is for the database on the application side from which the adapter will put or receive messages. This is not the information for the hub database.
Platform | Directory |
---|---|
Windows |
|
UNIX |
|
Application
is the value you specified in Step 3 .
After installation a set of post-installation steps displays. These steps are also copied to the post-installation.txt
file in the Database adapter directory.
To create the schema used by the Database adapter, complete the following tasks:
where:
When completing the post-installation steps, no errors should occur. If there are errors, verify that the application using the oai
schema in the specified database is the only occurrence. Errors can occur if a Database adapter from previous version installation is talking to this same database.
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:
Platform | Directory |
---|---|
UNIX |
|
Windows |
|
File | Description |
---|---|
|
Contains one error code per line. |
|
Consists of all the initialization parameters which the adapter reads at startup. |
Adapters do not have integration logic. The Database 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).
The following .ini
files are used in configuring the Database adapter.
The Database adapter connects to the hub database using parameters from the hub.ini
file located in the hub directory. Table 2-5 lists the parameter name, description, the possible and default values, and example for each parameter
When a hub is installed on a Real Application Cluster (RAC) database, parameters listed in Table 2-6 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-6, x
represent the node number, which varies between 2 and the number of nodes. For example, if the RAC setup contains 4 nodes, x
can take a value between 2 and 4.
The Database adapter connects to the spoke application using parameters from the adapter.ini
file. Table 2-7 lists the parameter name, description, the possible and default values, and example for 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. |
|
|
Specifies the amount of logging necessary. Possible values are: The default value is 1. |
|
|
The subscriber name used when this adapter registers its subscription. The possible value is a valid Oracle Advanced Queuing subscriber name and 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 false to turn off all tracking of messages. Set to true to track messages with tracking fields set in iStudio. Possible values are |
|
|
Specifies if throughput measurement is enabled. Set to true to turn on all throughput measurements. Possible values are |
|
|
Specifies if a custom 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 true if for every message, the DTD imported for the message of the common view is to be used instead of the OracleAS InterConnect DTD. Only set to true if a OracleAS InterConnect adapter is not receiving the messages from the hub. Possible values are |
|
|
Specifies the metadata caching algorithm. Possible values are:
The default value is |
|
|
Specifies the domain value mapping (DVM) table 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.
Possible values are |
|
|
Specifies the maximum number of application objects' metadata to cache. Possible values are any integer greater than or equal to 1. The default value is 200. |
|
|
Specifies the maximum number of common objects' metadata to cache. Possible values are any integer greater than or equal to 1. The default value is 100. |
|
|
Specifies the maximum number of messages' metadata to cache (publish/subscribe and invoke/implement). Possible values are any integer greater than or equal to 1. The default value is 200. |
|
|
Specifies the maximum number of DVM tables to cache. Possible values are any integer greater than or equal to 1. The default value is 200. |
|
|
Specifies the maximum number of lookup tables to cache. Possible values are any integer greater than or equal to 1. The default value is 200. |
|
|
Specifies the maximum size that internal OracleAS InterConnect message queues can grow. Possible values are any integer greater than or equal to 1. The default value is 1000. |
|
|
Specifies the maximum size that internal OracleAS InterConnect persistence queues can grow. Possible values are any integer greater than or equal to 1. The default value is 1000. |
|
|
Specifies how often the persistence cleaner thread should run. Possible values are any integer greater than or equal to 30000 milliseconds. The default value is 60000. |
|
|
Specifies how often the persistence thread should retry when it fails to push a OracleAS InterConnect message. Possible values are any integer greater than or equal to 60000 milliseconds. The default value is 60000. |
|
|
Specifies how to turn on or off the pipeline for messages from the Bridge towards the hub. If you set the pipeline 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. Specifies the value that the environment variable |
|
|
Specifies 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. |
|
|
Specifies the entry class for the Windows service. Possible values are |
|
|
Windows only. Specifies 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. Specifies 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 536870912. |
|
|
Windows only. Specifies 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. Specifies the JDK version the adapter Java VM should use. The default value is 1.4.1. |
|
|
Windows only. Specifies the dll the adapter Java VM should use. The default value is |
|
|
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 |
|
|
Specifies 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. |
|
|
Format for date fields expressed as string. The default date format is |
Date format pattern
Multiple date formats 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. |
|
Table 2-8 shows the reserved characters used to specify the value of the nls_date_format
parameter. Using these characters, you can construct a pattern to define date formats.
Table 2-9 lists parameters specific to the Database adapter.
When the Database adapter is servicing a RAC database as the spoke database, the parameters listed in Table 2-10 represent information on connection and configuration.
|
![]() Copyright © 2002, 2003 Oracle Corporation. All Rights Reserved. |
|