2 Installation and Configuration

This chapter describes how to install and configure the Database adapter. It contains the following topics:

Installing the Database Adapter
Installing Multiple Database Adapters in the Same Oracle Home
Configuring the Database Adapter
Uninstalling the Database Adapter

Installing the Database Adapter

The Database adapter must be installed in an existing Oracle home Middle Tier for OracleAS Integration InterConnect 10g Release 2 (10.1.2).

This section describes the following topics:

Preinstallation Tasks
Installation Tasks
Verification Test

Preinstallation Tasks

Refer to the following guides before installing the Database adapter:

Oracle Application Server Installation Guide for information about Oracle Universal Installer startup.
Oracle Application Server InterConnect Installation Guide for information about software, hardware, and system requirements for OracleAS Integration InterConnect.

Installation Tasks

To install the Database adapter, start the installer and complete the following steps:

In the Available Product Components screen of the OracleAS Integration InterConnect installation, select OracleAS Integration InterConnect Adapter For Database 10.1.2.0.2, and click Next.
The Set Oracle Wallet Password screen is displayed. Enter and confirm the password on the screen, which will be used to administer OracleAS Integration InterConnect installation. Click Next.
- Go to step 3, if installing the Database adapter in an OracleAS Middle Tier Oracle home that does not have an InterConnect component already installed. Ensure that the OracleAS Integration InterConnect hub has been installed.
- Go to step 4, if installing the Database adapter in an OracleAS Middle Tier Oracle home that has an existing InterConnect component. Ensure that it is a home directory to an OracleAS Integration InterConnect component.
The Specify Hub Database Connection screen is displayed. Enter information in the following fields:
- Host Name: The host name of the computer where the hub database is installed.
- Port Number: The TNS listener port for the hub database.
- Database SID: The System Identifier (SID) for the hub database.
- Password: The password for the hub database user.
Click Next. The Specify Database Adapter Name screen is displayed.

Enter the application name. Blank spaces are not permitted. The default value is myDBApp.

Note:

You can change the application name in iStudio after installation. In such a case, you need to specify the password corresponding to new application name in the Oracle Wallet.

For more informtion, refer to the following sections in Appendix A, "Frequently Asked Questions":

Click Next. The Specify Spoke Database Connection Information screen is displayed. Enter information in the following fields:
- Host Name: The name of the computer where the application database is installed.
- Port Number: The database TNS listener port.
- Database SID: The SID for the application database.
- Sys Password: The password of the sys user in the spoke database.
The information on this page is for the database on the application side from which the adapter will deliver or receive messages. This is not the information for the hub database.
Click Next. The Spoke Application Database Username page is displayed. Enter information in the following fields:
- Schema Name: The user name of the user in the Spoke Database.
- Password: The password for the user name.
Click Next. The Set Bridge Schema Password screen is displayed.
Enter and confirm the password for the bridge schema on the screen.
Click Next. The Summary screen is displayed.
Click Install to install the Database adapter and other selected components. The Database adapter is installed in the following directory:

Platform Directory

UNIX ORACLE_HOME/integration/interconnect/adapters/Application

Windows ORACLE_HOME\integration\interconnect\adapters\Application

Application is the value you specified in Step 5.

Verification Test

When completing the post installation steps, no errors should occur. If there are errors, then verify that in the specified database, the application using the oai schema is the only occurrence. Errors can occur if a Database adapter from previous version installation is talking to this same database.

Installing Multiple Database Adapters in the Same Oracle Home

To install multiple instances of the Database adapter in same Oracle home, use the copyAdapter script located in the ORACLE_HOME/integration/interconnect/bin directory.

Usage: copyAdapter app1 app2

For example, you have one instance of Database adapter with name myDBApp installed on a computer. To install another instance of the Database adapter with name myDBApp1 in the same Oracle home, use the following command:

copyAdapter myDBApp myDBApp1

The copyAdapter script is copied to the following bin directory only during Hub installation:

UNIX: ORACLE_HOME/integration/interconnect/bin
Windows: ORACLE_HOME\integration\interconnect\bin

If you need to use this script to create multiple adapters on a spoke computer, then copy the script to the bin directory on the spoke computer, and edit the script to reflect the new Oracle home.

After running the copyAdapter script, If you want to manage or monitor the newly installed adapter through Oracle Enterprise Manager 10g Application Server Control Console, then you need to modify the opmn.xml file by adding information about the new instance. For example, you have created a new instance of the Database adapter myDBApp1 by using the copyAdapter script. To manage the myDBApp1 adapter through Enterprise Manager, perform the following:

Navigate to the MiddleTier\bin directory and run the following command to stop the Enterprise Manager:
```
emctl stop iasconsole
```

Next, specify the information about this new instance in the opmn.xml file located in the ORACLEMIDDLETIER_HOME/opmn/conf directory as follows:

<process-type id="myDBApp1" module-id="adapter" working-dir="$ORACLE_
HOME/integration/interconnect/adapters/myDBApp1" status="enabled">
       <start timeout="600" retry="2"/>
       <stop timeout="120"/>
       <port id="icadapter_dmsport_range" range="15701-15800"/>
       <process-set id="myDBApp1" restart-on-death="true" numprocs="1">
            <module-data>
                <category id="start-parameters">
                    <data id="java-parameters" value="-Xms8M"/>
                    <data id="class-name"
                     value="oracle.oai.agent.service.AgentService"/>
                </category>
                <category id="stop-parameters">
                    <data id="java-parameters" value="-mx64m"/>
                    <data id="class-name"
                     value="oracle.oai.agent.proxy.ShutdownAgent"/>
                    <data id="application-parameters"
                     value="persistence/Agent.ior"/>
                </category>
            </module-data>
       </process-set>
</process-type>

The opmn.xml file would appear like this:

<process-type id="myDBApp" module-id="adapter" working-dir="$ORACLE
_HOME/integration/interconnect/adapters/myDBApp" status="enabled">
       <start timeout="600" retry="2"/>
       <stop timeout="120"/>
       <port id="icadapter_dmsport_range" range="15701-15800"/>
       <process-set id="myDBApp" restart-on-death="true" numprocs="1">
            <module-data>
                <category id="start-parameters">
                    <data id="java-parameters" value="-Xms8M"/>
                    <data id="class-name"
                     value="oracle.oai.agent.service.AgentService"/>
                </category>
                <category id="stop-parameters">
                    <data id="java-parameters" value="-mx64m"/>
                    <data id="class-name"
             value="oracle.oai.agent.proxy.ShutdownAgent"/>
             <data id="application-parameters"
              value="persistence/Agent.ior"/>
         </category>
     </module-data>
  </process-set>
</process-type>
            
<process-type id="myDBApp1" module-id="adapter" working-dir="$ORACLE
_HOME/integration/interconnect/adapters/myDBApp1" status="enabled">
       <start timeout="600" retry="2"/>
       <stop timeout="120"/>
       <port id="icadapter_dmsport_range" range="15701-15800"/>
       <process-set id="myDBApp1" restart-on-death="true" numprocs="1">
        <module-data>
          <category id="start-parameters">
              <data id="java-parameters" value="-Xms8M"/>
              <data id="class-name"
               value="oracle.oai.agent.service.AgentService"/>
          </category>
          <category id="stop-parameters">
               <data id="java-parameters" value="-mx64m"/>
               <data id="class-name"
                value="oracle.oai.agent.proxy.ShutdownAgent"/>
               <data id="application-parameters"
                value="persistence/Agent.ior"/>
          </category>
        </module-data>
       </process-set>
</process-type>

Save the opmn.xml file.
Navigate to the MiddleTier\opmn\bin directory and run the following command to reload the OPMN:
```
opmnctl reload
```

You can start the myDBApp1 adapter by using the following command

opmnctl startproc ias-component="InterConnect" process-type="myDBApp1"

Navigate to the MiddleTier\bin directory and run the following command to start the Enterprise Manager:
```
emctl start iasconsole
```
Login to the Oracle Enterprise Manager 10g Application Server Control Console to view and manage the newly installed or copied adapter. For information about how to use Oracle Enterprise Manager 10g Application Server Control Console , refer to the Oracle Application Server Integration InterConnect User's Guide

Note:

While installing multiple adapters in the same computer, the copyadapter script does not create entries for the new adapter's password in the Oracle Wallet. You need to manually create a password for this new adapter using the Oracle Wallet Manager. To store the password in Oracle Wallet, use the following format:

ApplicationName/password

The number of entries is dependent on the type of adapter. For example, Database adapter needs two entries whereas AQ Adapter needs only one entry. For more information about how to manage your passwords in Oracle Wallet, refer to AppendixA, "How do I secure my passwords?" in Appendix A, "Frequently Asked Questions"

Configuring the Database Adapter

After an Database adapter installation, you can configure it according to your requirements. The following tables describe the location and details of the configuration files.

Table 2-1 describes the location where the adapter is installed.

Table 2-1 Oracle9i Database Server Adapter Directory

Platform	Directory
UNIX	`ORACLE_HOME/integration/interconnect/adapters/Application`
Windows	`ORACLE_HOME\integration\interconnect\adapters\Application`

Table 2-2 describes the various executable files available for the Database adapter.

Table 2-2 Executable Files

File	Description
`start` (UNIX)	Does not use parameters; starts the adapter.
`start.bat` (Windows)	Does not use parameters; starts the adapter.
`stop` (UNIX)	Does not use parameters; stops the adapter.
`stop.bat` (Windows)	Does not use parameters; stops the adapter.

Table 2-3 describes the Database adapter configuration files.

Table 2-3 Configuration Files

File	Description
`adapter.ini` (UNIX	Consists of all the initialization parameters, which the adapter reads at startup.
`adapter.ini` (Windows)	Consists of all the initialization parameters, which the adapter reads at startup.

Table 2-4 describes the directories used by the Database adapter.

Table 2-4 Directories

File	Description
`logs`	The adapter activity is logged in subdirectories of the `logs` directory. Each time the adapter is run, a new subdirectory is created for the `log.xml` log file.
`persistence`	The messages are persisted in this directory. Do not edit this directory or its files.

Using the Application Parameter

Adapters do not have integration logic. The Database adapter has a generic transformation engine that uses metadata from the repository as run-time instructions to perform transformations. The application parameter defines the capabilities of an adapter, such as the messages to be published and subscribed, and the transformations to be performed. The application parameter allows the adapter to retrieve only the relevant metadata from the repository. The application parameter must match the corresponding application name that will be defined in iStudio under the Applications folder.

If you use prepackaged metadata, then import it into the repository and start iStudio to find the corresponding application under the Applications folder. You can use this as the application name for the adapter you are installing.

Database Adapter Ini File Settings

The following .ini files are used to configure the Database adapter:

hub.ini Parameters
adapter.ini Parameters

hub.ini Parameters

The Database adapter connects to the hub database by using parameters in the hub.ini file located in the hub directory. Table 2-5 gives a descriptions and an example of each parameter.

Table 2-5 hub.ini Parameters

Parameters	Description	Example
`hub_host`	The name of the computer hosting the hub database. There is no default value. The value is set during installation.	`hub_host=mpscottpc`
`hub_instance`	The SID of the hub database. There is no default value. The value is set during installation.	`hub_instance=orcl`
`hub_port`	The TNS listener port number for the hub database instance. There is no default value. The value is set during installation.	`hub_port=1521`
`hub_username`	The name of the hub database schema (or user name). There default value is ichub.	`hub_username=ichub`
`repository_name`	The name of the repository that communicates with the adapter. The default value is `InterConnectRepository`.	`repository_name=InterConnectRepository`

Oracle Real Application Clusters hub.ini Parameters

When a hub is installed on an Oracle Real Application Clusters database, the parameters listed in Table 2-6 represent information on additional nodes used for connection and configuration. These parameters are in addition to the default parameters for the primary node. In Table 2-6, x represents the node number. The number is between 2 and the number of nodes. For example, if the cluster contains 4 nodes, then x can be a value between 2 and 4.

Table 2-6 Oracle Real Application Clusters hub.ini Parameters

Parameter	Description	Example
`hub_hostx`	The host where the Real Application Clusters database is installed.	`hub_host2=dscott13`
`hub_instancex`	The instance on the respective node	`hub_instance2=orcl2`
`hub_num_nodes`	The number of nodes in a cluster.	`hub_num_nodes=4`
`hub_portx`	The port where the TNS listener is listening..	`hub_port2=1521`

adapter.ini Parameters

The Database adapter connects to the spoke application using parameters in the adapter.ini file. Table 2-7 gives a descriptions and an example of each parameter.

Table 2-7 adapter.ini Parameters

Parameter	Description	Example
`agent_admin_port`	Specifies the port through which the adapter can be accessed through firewalls. Possible value: A valid port number Default value: None	`agent_admin_port=1059`
`agent_delete_file_cache_at_startup`	Specifies whether to delete the cached metadata during startup. If any agent caching method is enabled, then metadata from the repository is cached locally on the file system. Set the parameter to `true` to delete all cached metadata on startup. Possible values: `true` or `false` Default value: `false` Note: After changing metadata or DVM tables for the adapter in iStudio, you must delete the cache to guarantee access to new metadata or table information.	`agent_delete_file_cache_at_startup=false`
`agent_dvm_table_caching`	Specifies the Domain Value Mapping (DVM) table caching algorithm. Possible values: `startup`: Cache all DVM tables at startup. This may be time-consuming if there are many tables in the repository `demand`: Cache tables as they are used `none`: No caching. This slows down performance. Default value: `demand`	`agent_dvm_table_caching=demand`
`agent_log_level`	Specifies the amount of logging necessary. Possible values: `0`=errors only `1`=status and errors `2`=trace, status, and errors Default value: 1	`agent_log_level=2`
`agent_lookup_table_caching`	Specifies the lookup table caching algorithm. Possible values: `startup`: Cache all lookup tables at startup. This may be time-consuming if there are many tables in the repository. `demand`: Cache tables as they are used `none`: No caching. This slows down performance. Default value: `demand`	`agent_lookup_table_caching=demand`
`agent_max_ao_cache_size`	Specifies the maximum number of application object metadata to cache. Possible value: An integer greater than or equal to `1` Default value: `200`	`agent_max_ao_cache_size=200`
`agent_max_co_cache_size`	Specifies the maximum number of common object metadata to cache. Possible value: An integer greater than or equal to `1` Default value: `100`	`agent_max_co_cache_size=100`
`agent_max_dvm_table_cache_size`	Specifies the maximum number of DVM tables to cache. Possible value: An integer greater than or equal to `1` Default value: `200`	`agent_max_dvm_table_cache_size=200`
`agent_max_lookup_table_cache_size`	Specifies the maximum number of lookup tables to cache. Possible value: Any integer greater than or equal to `1` Default value: `200`	`agent_max_lookup_table_cache_size=200`
`agent_max_message_metadata_cache_size`	Specifies the maximum number of message metadata (publish/subscribe and invoke/implement) to cache. Possible value: An integer greater than or equal to `1` Default value: `200`	`agent_max_message_metadata_cache_size=200`
`agent_max_queue_size`	Specifies the maximum size to which internal OracleAS Integration InterConnect message queues can grow. Possible value: An integer greater than or equal to `1`. Default value: `1000`	`agent_max_queue_size=1000`
`agent_message_selector`	Specifies conditions for message selection when the adapter registers its subscription with the hub. Possible value: A valid Oracle Advanced Queue message selector string (such as `'%,aqapp,%'`) Default value: None	`agent_message_selector=%,aqapp`,`%`
`agent_metadata_caching`	Specifies the metadata caching algorithm. Possible values: `startup`: Cache everything at startup. This may be time-consuming if there are many tables in the repository. `demand`: Cache metadata as it is used. `none`: No caching. This slows down performance. Default value: `demand`	`agent_metadata_caching=demand`
`agent_persistence_cleanup_interval`	Specifies how often to run the persistence cleaner thread in milliseconds. Possible value: An integer greater than or equal to `30000` milliseconds Default value: `60000`	`agent_persistence_cleanup_interval=60000`
`agent_persistence_queue_size`	Specifies the maximum size of internal OracleAS Integration InterConnect persistence queues. Possible value: An integer greater than or equal to `1` Default value: `1000`	`agent_persistence_queue_size=1000`
`agent_persistence_retry_interval`	Specifies how often the persistence thread retries when it fails to send an OracleAS Integration InterConnect message. Possible value: An integer greater than or equal to `5000` milliseconds Default value: `60000`	`agent_persistence_retry_interval=60000`
`agent_pipeline_from_hub`	Specifies whether to activate the pipeline for messages from the hub to the bridge. If you set the pipeline to `false`, then the file persistence is not used in that direction. Possible value: `true`, `false` Default value: `false`	`agent_pipeline_from_hub=false`
`agent_pipeline_to_hub`	Specifies whether to activate the pipeline for messages from the bridge to the hub. If you set the pipeline to `false`, then the file persistence is not used in that direction. Possible value: `true`, `false` Default value: `false`	`agent_pipeline_to_hub=false`
`agent_reply_message_selector`	Specifies the application instance to which the reply must be sent. This parameter is used if multiple adapter instances exist for the given application and given partition. Possible value: A string built using the application name (`parameter:application`) concatenated with the instance number (`parameter:instance_number`). Default value: None	If `application=aqapp, instance_number=2`, then `agent_reply_message_selector=`recipient_list `like` '`%,aqapp2,%`'
`agent_reply_subscriber_name`	Specifies the subscriber name used when multiple adapter instances are used for the given application and given partition. This parameter is optional if only one instance is running. Possible value: The application name (`parameter:application`) concatenated with the instance number (`parameter:instance_number`). Default value: None	If `application=dbapp` and `instance_number=2`, then `agent_reply_subscriber_name=dbapp2`
`agent_subscriber_name`	Specifies the subscriber name used when this adapter registers its subscription. Possible value: A valid Oracle Advanced Queue subscriber name Default value: None	`agent_subscriber_name=dbapp`
`agent_throughput_measurement_enabled`	Specifies if the throughput measurement is enabled. Set this parameter to `true` to activate throughput measurements. Default value: `true`	`agent_throughput_measurement_enabled=true`
`agent_tracking_enabled`	Specifies if message tracking is enabled. Set this parameter to `false` to turn off tracking of messages. Set this parameter to `true` to track messages with tracking fields set in iStudio. Default value: `true`	`agent_tracking_enabled=true`
`agent_use_custom_hub_dtd`	Specifies whether to use a custom DTD for the common view message when handing it to the hub. By default, adapters use a specific OracleAS Integration InterConnect DTD for all messages sent to the hub. Set this parameter to `true` to have the adapter use the DTD imported for the message of the common view instead of the OracleAS Integration InterConnect DTD. Default value: None	`agent_use_custom_hub_dtd=false`
`application`	Specifies the name of the application to which this adapter connects. This must match the name specified in iStudio while creating metadata. Possible value: An alphanumeric string Default value: None	`application=dbapp`
`encoding`	Specifies the character encoding for published messages. The adapter uses this parameter to generate encoding information for the encoding tag of transformed OracleAS Integration InterConnect messages. OracleAS Integration InterConnect represents messages internally as XML documents. Possible value: A valid character encoding Default value: `UTF-8` When there is no existing encoding in the subscribed message, this parameter will be used to explicitly specify the encoding of the published message. This parameter will be ignored when the encoding already exists in the subscribed message.	`encoding=Shift_JIS`
`external_dtd_base_url`	Specify the base URL for loading external enitites and DTDs.This specifies to the XML parser to resolve the external entities in the instance document using the given URL. Possible value: A URL Default value: The URL of the current user directory	`external_dtd_base_url=file://C:\ORACLEHOME\Integration\InterConnect\adapters\AQApp\`
`instance_number`	Specifies the instance number to which this adapter corresponds. Specify a value only if you have multiple adapter instances for the given application with the given partition. Possible value: An integer greater than or equal to `1` Default value: None	`instance_number=1`
`nls_country`	Specifies the ISO country code. The codes are defined by ISO-3166. Possible value: A valid code. A full list of the codes is available at `http://www.chemie.fu-berlin.de/diverse/doc/ISO_3166.html` Default value: `US` Note: This parameter specifies date format and is applicable only for the date format.	`nls_country=US`
`nls_date_format`	Specifies the format for a date field expressed as a string. Possible value: A valid date format pattern as shown in Table 2-8 for the definitions of the format characters. Default value: `EEE MMM dd HHmmss zzz yyyy`	Date format pattern `dd/MMM/yyyy` can represent 01/01/2003. `nls_date_format=dd-MMM-yy` Multiple date formats can be specified as `num_nls_formats=2` `nls_date_format1=dd-MMM-yy` `nls_date_format2=dd/MMM/yy`
`nls_language`	Specifies the ISO language code. The codes are defined by ISO-639. Possible value: A valid code. A full list of these codes is available at `http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt` Default value: `en` Note: This parameter specifies date format and is applicable only for the date format.	`nls_language=en`
`partition`	Specifies the partition this adapter handles as specified in iStudio. Possible value: An alphanumeric string Default value: None	`partition=germany`
`service_class`	Specifies the entry class for the Windows service. Possible value: `oracle/oai/agent/service/AgentService`. Default value: None	`service_class=oracle/oai/agent/service/AgentService`
`service_classpath`	Specifies the class path used by the adapter Java Virtual Machine(JVM). If a custom adapter is developed and the adapter is to pick up any additional jar files, then add the files to the existing set of jar files. Possible value: A valid `PATH` setting Default value: None This parameter is only for Microsoft Windows.	`service_classpath=D:\oracle\oraic\integration\interconnect\lib\oai.jar; D:\oracle\oraic\jdbc\classes12.zip`
`service_jdk_dll`	Specifies the Dynamic Link Library (DLL) that the adapter JVM should use. Possible value: A valid `jvm.dll` Default value: `jvm.dll` This parameter is only for Microsoft Windows.	`service_jdk_dll=jvm.dll`
`service_jdk_version`	Specifies the JDK version that the adapter JVM should use. Possible value: A valid JDK version number Default value: 1.4 This parameter is only for Microsoft Windows.	`service_jdk_version=1.4`
`service_max_heap_size`	Specifies the maximum heap size for the adapter JVM. Possible value: A valid JVM heap size. Default value: `536870912`. This parameter is only for Microsoft Windows.	`service_max_heap_size=536870912`
`service_max_java_stack_size`	Specifies the maximum size to which the JVM stack can grow. Possible value: A valid JVM maximum stack size. Default value: Default value for the JVM. This parameter is only for Microsoft Windows.	`service_max_java_stack_size=409600`
`service_max_native_stack_size`	Specifies the maximum size to which the JVM native stack can grow. Possible value: A valid JVM maximum native stack size. Default value: Default value for the JVM. This parameter is only for Microsoft Windows.	`service_max_native_size=131072`
`service_min_heap_size`	Specifies the minimum heap size for the adapter JVM. Possible value: A valid JVM heap size. Default value: `536870912` This parameter is only for Microsoft Windows	`service_min_heap_size=536870912`
`service_num_vm_args`	Specifies the number of `service_vm_argnumber` parameters specified in JVM. Possible value: The number of `service_vm_argnumber` parameters. Default value: None This parameter is only for Microsoft Windows.	`service_num_vm_args=1`
`service_path`	Specifies the environment variable `PATH`. The `PATH` variable is set before starting the JVM. Typically, list all directories that contain necessary DLLs. Possible value: The valid `PATH` environment variable setting. Default value: None This parameter is only for Microsoft Windows.	`service_path=%JREHOME%\bin;D:\oracle\oraic\bin`
`service_vm_argnumber`	Specifies any additional arguments to the JVM. For example, to retrieve line numbers in any stack traces, set `service_vm_arg1=java.compiler=NONE`. If a list of arguments exists, then use multiple parameters as shown in the example, by incrementing the last digit by `1`. Possible value: Valid JVM arguments Default value: None This parameter is only for Microsoft Windows.	`service_vm_arg1=java.compiler= NONE` `service_vm_arg2=oai.adapter=.aq`

Table 2-8 shows the reserved characters used to specify the value of the nls_date_format parameter. Use the characters to define date formats.

Table 2-8 Reserved Characters for the value of the nls_date_format Parameter

Letter	Description	Example
`G`	Era designator	`AD`
`y`	Year	`1996` or `96`
`M`	Month in year	`July` or `Jul` or `07`
`w`	Week in year	`27`
`W`	Week in month	`2`
`D`	Day in year	`189`
`d`	Day in month	`10`
`F`	Day of week in month	`Number 2`
`E`	Day in week	`Tuesday` or `Tue`
`a`	a.m./p.m. marker	`P.M.`
`H`	Hour in day (0-23)	`0`
`k`	Hour in day (1-24)	`24`
`K`	Hour in a.m./p.m. (0-11)	`0`
`h`	Hour in a.m./p.m. (1-12)	`12`
`m`	Minute in hour	`30`
`s`	Second in minute	`55`
`S`	Millisecond	`978`

Database Adapter-Specific Parameters

Table 2-9 lists parameters specific to the Database adapter.

Table 2-9 Database Adapter-specific Parameters

Parameter	Description	Example
`bridge_class`	Indicates the entry class for the Database adapter. Do not modify this value. Default value: `oracle.oai.agent.adapter.db.DBBridge`	`bridge_class=oracle.oai.agent.adapter.db. DBBridge`
`db_bridge_instance`	The SID of the database instance. Default value: None	`db_bridge_instance=orcl`
`db_bridge_num_schemas`	The number of alternate schemas that this database adapter will fail over to. Possible values: An integer greater than 0 Default value: `1`	`db_bridge_num_schemas =1`
`db_bridge_schema#_host`	The name of the computer hosting the database instance specified by the `db_bridge_schema#_instance`. Default value: None	`db_bridge_schema1_host=ssuravar-sun`
`db_bridge_schema#_instance`	The SID of the database instance. Possible value: A valid SID Default value: None	`db_bridge_schema1_instance=oiddb1`
`db_bridge_schema#_num_readers`	The number of database readers corresponding to the schema number. This is the same as the number of reader threads; each thread has its own database session. Possible value: An integer greater than 0 Default value: None	`db_bridge_schema1_num_readers=1`
`db_bridge_schema#_num_writers`	The number of database writers corresponding to the schema number. This is same as the number of writer threads; each thread has its own database session. Possible values: An integer greater than 0 Default value: None	`db_bridge_schema1_num_writers=1`
`db_bridge_schema#_password`	The password for the user specified in the `db_bridge_schemaschema#_username`. Possible value: The password for the corresponding database user Default value: None	`db_bridge_schema1_password=oai` `encrypted_db_bridge_schema1_password=112511011064109110871093`
`db_bridge_schema#_port`	The port where the TNS listener is running for the database instance specified by `db_bridge_schema#_instance` parameter. Possible value: A valid TNS listener port number Default value: None	`db_bridge_schema1_port=1521`
`db_bridge_schema#_username`	The user name for the schema number schema#. The possible values for the schema number are 1 through db_bridge_num_schemas. This value should not be modified. Possible value: A valid database user name Default value: None	`db_bridge_schema1_username=oai`
`db_bridge_schema#_writer_password`	The password corresponding to the database user specified in Oracle Wallet by the `db_bridge_schema`#`_writer_username` parameter. Possible values: A valid password. Default value: None. Note: All passwords are stored in Oracle Wallet. Refer to AppendixA, "How do I secure my passwords?" in Appendix A, "Frequently Asked Questions" for more details on how to modify and retrieve the password using Oracle Wallet.	`db_bridge_schema1_writer_password=welcome`
`db_bridge_schema#_writer_use_oracle_objects`	Specifies whether to use Oracle Objects, available in Oracle database version 8.x and later releases. Set this to true unless using an Oracle database version 7.x. Possible values: `true` or `false` Default value: `false`	`db_bridge_schema1_writer_use_oracle_objects=true`
`db_bridge_schema#_writer_username`	The user name to be used by this writer to log on to the database as specified by the `db_bridge_schema#_instance` parameter. Possible values: A valid database user. Default value: None	`db_bridge_schema1_writer_username=mydbapp`
`db_bridge_sql_ trace`	Used to enable or disable the SQL trace facility for all reader and writer database sessions. Setting this to true results in the SQL query `ALTER SESSION SET SQL_TRACE = TRUE` being run in the session, thus enabling the SQL trace facility. For more information on the SQL trace facility, including how to format and interpret the output, refer to the Oracle Tuning Guide. Possible values: `true` or `false` Default value: `false`	`db_bridge_sql_trace= true`
`db_bridge_use_thin_jdbc`	Indicates whether to use a thin JDBC driver when talking to the database. Possible values: `true` or `false` Default value: `true`	`db_bridge_thin_jdbc=true`

Real Application Clusters adapter.ini Parameters for the Database Adapter

When the Database adapter is servicing a Real Application Clusters database as the spoke database, parameters listed in Table 2-10 represent information on connection and configuration.

Table 2-10 Real Application Clusters adapter.ini Parameters

Parameter	Description	Example
`db_bridge_num_nodes`	Indicates the number of nodes in RAC cluster.	`db_bridge_num_nodes=4`
`db_bridge_schema_hostx`	Indicates host for the node x.	`db_bridge_schema_host2=` `mypc.us.oracle.com`
`db_bridge_schema_instancex`	Indicates instance on node x.	`db_bridge_schema_instance2=` `inst1`
`db_bridge_schema_portx`	Indicates port for node x.	`db_bridge_schema_port2=1521`

Uninstalling the Database Adapter

To uninstall the Database adapter, perform the following:

Navigate to the MiddleTier\opmn\bin directory.
Run the following command to check the adapter status.
```
opmnctl status
```
If the Database adapter instance that you want to remove is running, stop it by using the the following command:
```
opmnctl stopproc ias-component="InterConnect" process-type="DBApp"
```
where HTTPApp is the name of the Database adapter instance.
Navigate to the MiddleTier\bin directory and run the following command to stop the Enterprise Manager:
```
emctl stop iasconsole
```

Carefully, remove the adapter process-type entry from the opmn.xml file located in the MiddleTier\opmn\conf directory. For example, to remove an Database adapter instance DBApp1, delete the following information specific to the adapter instance:

<process-type id="DBApp1" module-id="adapter" working-dir="$ORACLE_HOME/integration/interconnect/adapters/DBApp1" status="enabled">
       <start timeout="600" retry="2"/>
       <stop timeout="120"/>
       <port id="icadapter_dmsport_range" range="15701-15800"/>
       <process-set id="DBApp1" restart-on-death="true" numprocs="1">
            <module-data>
                <category id="start-parameters">
                    <data id="java-parameters" value="-Xms8M"/>
                    <data id="class-name"
                     value="oracle.oai.agent.service.AgentService"/>
                </category>
                <category id="stop-parameters">
                    <data id="java-parameters" value="-mx64m"/>
                    <data id="class-name"
                     value="oracle.oai.agent.proxy.ShutdownAgent"/>
                    <data id="application-parameters"
                     value="persistence/Agent.ior"/>
                </category>
            </module-data>
       </process-set>
</process-type>

Save the opmn.xml file.
Navigate to the MiddleTier\opmn\bin directory and run the following command to reload the OPMN:
```
opmnctl reload
```
Navigate to the ORACLE_HOME\integration\interconnect\adapters directory and delete the folder that was created for the removed adapter instance.
Navigate to the MiddleTier\bin directory and run the following command to start the Enterprise Manager:
```
emctl start iasconsole
```