2
Installation and Configuration

This chapter describes the installation and configuration of the HTTP adapter in the following topics:

• Installing HTTP Adapter

• HTTP Adapter Configuration Parameters

Installing HTTP Adapter

This section contains these topics:

• Preinstallation Tasks

• Installation Tasks

• Postinstallation Tasks

Preinstallation Tasks

The HTTP adapter must be installed in one of the following Oracle homes:

• An existing OracleAS InterConnect Oracle home for 10g (9.0.4)

• A new Oracle home (Oracle Universal Installer creates this Oracle home for you)

Consult the following guides before proceeding with HTTP adapter installation:

• Oracle Application Server Installation Guide, which includes information on:
  • Oracle Universal Installer startup

• Oracle Application Server InterConnect Installation Guide, which includes information on:
  • CD-ROM mounting

  • OracleAS InterConnect software, hardware, and system requirements

  • OracleAS InterConnect installation

    Note: OracleAS InterConnect Hub is installable through the OracleAS InterConnect Hub installation type. You must install the OracleAS InterConnect Hub before proceeding with the HTTP adapter installation.

Installation Tasks

To install the HTTP adapter:

1. On the Available Product Components page of the OracleAS InterConnect installation, select HTTP adapter, then select Next.

   Consider the following scenarios:

   • If installing the HTTP adapter in an independent Oracle home, make sure that the OracleAS InterConnect Hub has been installed, not necessarily in the same Oracle home. Continue to step 2.

   • If installing the HTTP adapter in an existing Oracle home, make sure that it is a home directory to one of the OracleAS InterConnect component. Continue to step 3.

     Note: The hub database information, such as the SID, host, port, and username/password from the Hub installation, is needed for step 2.

2. If installing OracleAS InterConnect for the first time on this machine, complete the following steps to enter the hub database information:
   1. On the Welcome page, select Next. The Database Configuration page displays. Enter information in the following fields:
      • Host Name--The host name of the machine where the hub database is installed.

      • Port Number--The TNS listener port for the hub database.

      • Database SID--The SID for the hub database.

   2. Click Next. The Database User Configuration page displays. Enter information in the following fields:
      • User Name--The hub database user name. Make sure the OracleAS InterConnect Hub is installed. If the Hub is not installed, complete the installation and note the user name and password.

      • Password--The password for the hub database user.

3. Click Next. The Adapter Configuration page displays. Enter the application to be defined or already defined in iStudio in the Application Name field. White spaces or blank spaces are not permitted. The default value is myHTTPApp.

4. Click Next.

   The OracleAS InterConnect HTTP Adapter usage screen appears.

5. Select one of the following options and go to the step specified to enable the sending and receiving of messages, the sending of messages only, or the receiving of messages only from an external data source, such as an HTTP server. You can change the values for these selections later by editing parameter settings in the adapter.ini file.

   If You Select...	Then Click Next and Go to Step...
   Configure for both sending and receiving messages	6
   Configure for sending messages ONLY	6
   Configure for receiving messages ONLY	8

6. Enter the following information in the OracleAS InterConnect HTTP Adapter Configuration - Configure sending endpoint information screen:
   • URL--The URL of the outgoing HTTP server to which OracleAS InterConnect sends messages. Enter the URL as follows:

     http://hostname:port/path
     
     

7. Click Next.

   The installation screen that appears next is based on the selection you made in Step 5:

   If You Selected...	Then Go to Step...
   Configure for both sending and receiving messages	8
   Configure for sending messages ONLY	10

8. Enter the following information in the OracleAS InterConnect HTTP Adapter Configuration - Configure receiving endpoint information screen:
   • Hostname--The hostname of the HTTP server from which OracleAS InterConnect receives messages.

   • Port Number--The port number of the HTTP server.

9. Click Next.

10. Complete any other fields for other components selected for installation, such as other adapters.

    When finished, the Summary screen appears.

11. Select Install to install the HTTP adapter. The adapter is installed in the following directory:

    Platform	Directory
    Windows	ORACLE_HOME\oai\9.0.4\adapters\Application
    UNIX	ORACLE_HOME/oai/9.0.4/adapters/Application

    Application is the value you specified in Step 3. A webapps subdirectory is created in the Application directory identified in Step 11. webapps includes the following files created for the HTTP application:

    • An EAR file (oai.ear)

    • A web.xml file located in the WEB-INF directory

    • An application.xml file located in the META-INF directory

Postinstallation Tasks

HTTP adapter installation creates an adapter.ini file that consists of configuration parameters read by the HTTP adapter at startup. The configuration parameter settings are appropriate for most HTTP application environments. If you want to customize some adapter.ini file parameter settings for the HTTP application, see the following sections:

• Customizing the Payload Datatype

• Customizing the Sending Endpoints

• Customizing the Authentication Scheme

• Customizing a Proxy Host

• Customizing a Secure Socket Layer Environment

• Customizing the Receiving Endpoints

• Manually Deploying an EAR File

  See Also: Table 2-1 for the location of the adapter.ini file Table 2-7 for adapter.ini file parameter setting information specific to the HTTP adapter

Customizing the Payload Datatype

Payload data is the data sent between applications. If you want to change the payload datatype from the default of XML to the data definition description language (D3L), edit the following parameters in the adapter.ini file.

To customize the payload datatype:

1. Set the ota.type parameter to the payload type D3L. For example:

   ota.type=D3L
   
   

2. Copy the D3L XML files associated with the HTTP application to the directory in which the adapter.ini file is located.

3. Set the ota.d3ls parameter to specify the D3L files associated with the HTTP application. For example:

   ota.d3ls=person1.xml,person2.xml
   

   See Also: ota.type and ota.d3ls parameter descriptions for additional information

Customizing the Sending Endpoints

If you want to customize the behavior of the sending endpoints (destinations) for messages, edit the following parameter in the adapter.ini file.

To customize the sending endpoints:

1. Set the http.sender.timeout parameter to the timeout interval in milliseconds for HTTP connections. This parameter automatically defaults to a value of 60000 during installation. For example:

   http.sender.timeout=10000
   

   See Also: http.sender.timeout parameter description for additional information

Customizing the Authentication Scheme

If you want to use an authentication scheme, edit the following parameters in the adapter.ini file. These parameters are not automatically set to default values during installation.

To customize the authentication scheme:

1. Set the http.sender.authtype parameter to the authentication type to use. For example:

   http.sender.authtype=basic
   
   

2. Set the http.sender.realm parameter to the realm for the authentication scheme. For example:

   http.sender.realm=ipt
   
   

3. Set the http.sender.username parameter to the authentication username. For example:

   http.sender.username=joe
   
   

4. Set the http.sender.password parameter to the authentication password. For example:

   http.sender.password=100100101
   

   See Also: The following parameter descriptions for additional information: http.sender.authtype http.sender.realm http.sender.username http.sender.password "How do I make the adapter.ini file password parameters secure?" for instructions on encrypting the http.sender.password parameter password

Customizing a Proxy Host

If you want to use a proxy host, edit the following parameters in the adapter.ini file. These parameters are not automatically set to default values during installation.

To customize a proxy host:

1. Set the http.sender.proxy_host parameter to the hostname of the proxy server. For example:

   http.sender.proxy_host=www-proxy.foo.com
   
   

2. Set the http.sender.proxy_port parameter to the port number of the proxy server. For example:

   http.sender.proxy_port=80
   

   See Also: The following parameter descriptions for additional information: http.sender.proxy_host http.sender.proxy_port

Customizing a Secure Socket Layer Environment

If you want to use the secure socket layer (SSL) environment for sending messages, edit the following parameters in the adapter.ini file. These parameters are not automatically set to default values during installation.

To customize a secure socket layer environment:

1. Set the http.sender.wallet_location parameter to the directory path and name of the wallet file. For example:

   http.sender.wallet_location=/private/foo/certdb.txt
   
   

   certdb.txt is the name of the flat file exported from the Oracle Wallet manager. In some cases, you may need to use Oracle Wallet manager to add additional trusted certificates from the HTTP server into your wallet to avoid incomplete certificate chain error.

2. Set the http.sender.wallet_password parameter to the Oracle Wallet Manager password. For example:

   http.sender.wallet_password=4341193845566
   
   

3. Set the http.sender.cipher_suites parameter to the cipher suites used in the secure connection. For example:

   http.sender.cipher_suites=SSL_RSA_WITH_NULL_SHA,SSL_RSA_WITH_3DES_EDE_CBC_
   SHA
   

   See Also: The following parameter descriptions for additional information: http.sender.wallet_location http.sender.wallet_password http.sender.cipher_suites "How do I make the adapter.ini file password parameters secure?" for instructions on encrypting the http.sender.wallet_password parameter password

Customizing the Receiving Endpoints

If you want to customize the behavior of receiving endpoint messages, edit the following parameter in the adapter.ini file.

To customize the receiving endpoints:

1. Set the http.receiver.registry_port parameter to the remote method invocation (RMI) registry port for communicating with the servlet. This parameter automatically defaults to a value of 9901 during installation. For example:

   http.receiver.registry_port=3500
   

   See Also: http.receiver.registry_port parameter description for additional information

Manually Deploying an EAR File

If the Oracle Application Server Containers for J2EE (OC4J) is installed on a separate computer from the HTTP adapter, you must manually:

• Edit the web.xml file

• Deploy the EAR file (oai.ear) located in the directory of the HTTP adapter

To manually deploy an EAR file:

1. Go to the following directory:

   cd myHTTPapphome
   
   

   where myHTTPapphome is the directory in which the HTTP application is installed and the value you defined in Step 3.

2. Extract all files from the oai.ear file:

   jar xvf oai.ear 
   

3. Extract all files from the oai.war file:

   jar xvf oai.war
   
   

4. Go to the following directory:

   cd WEB-INF
   
   

5. Use a text editor to open the web.xml file:

   web.xml specifies the RMI information that must match with the setting in the adapter.ini file. For example, rmiHost must match the hostname of the computer on which the HTTP adapter is installed. The HTTP adapter serves as the RMI server. The transport servlet makes an RMI call to submit the requests sent by the external application. You can also edit the logging options that are turned off by default.

   The following web.xml file shows the rmiHost parameter with a computer hostname setting of prodserver10:

   <init-param>
     <param-name>rmiHost</param-name>
     <param-value>prodserver10</param-value>
   </init-param>
   <init-param>
     <param-name>rmiPort</param-name>
     <param-value>9901</param-value>
   </init-param>
   <init-param>
     <param-name>instanceName</param-name>
     <param-value>oai</param-value>
   </init-param>
   <!-- set the following parameters if logging is needed. -->
   <init-param>
     <param-name>isLogOn</param-name>
     <!-- enter true/false -->
     <param-value>false</param-value>
   </init-param>
   <init-param>
     <param-name>logDir</param-name>
     <!-- directory where log file is placed. -->
     <param-value></param-value>
   </init-param>
   <init-param>
     <param-name>logLevel</param-name>
     <!-- choose one of the levels: debug, status, or  error -->
     <param-value></param-value>
    </init-param>
   
   

6. Save the changes and exit the file.

7. Return to the following directory:

   cd myHttpApphome
   
   

8. Restore the oai.war and oai.ear files:

   jar cvf oai.war WEB-INF
   jar cvf oai.ear META-INF/ oai.war
   
   

9. See the Oracle Application Server Administrator's Guide for instructions on using the Distributed Configuration Management (DCM) command line utility to deploy the EAR file.

HTTP Adapter Configuration Parameters

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 HTTP Adapter Directory

Platform	Directory
UNIX	ORACLE_HOME/oai/9.0.4/adapters/Application
Windows	ORACLE_HOME\oai\9.0.4\adapters\Application

Table 2-2 HTTP Executable Files

File	Description
start.bat (Windows) start (UNIX)	Takes no parameters, starts the adapter
stop.bat (Windows) stop (UNIX)	Takes no parameters; stops the adapter
ignoreerrors.bat (Windows) ignoreErrors (UNIX)	If an argument is specified, then the given error code is ignored: ignoreerrors errorCodeToBeIgnored If no argument is specified, then all error codes specified in the ErrorCodes.ini file are ignored: ignoreerrors

See Also: "HTTP Adapter Error Codes"

Table 2-3 HTTP Configuration Files

File	Description
ErrorCodes.ini (Windows and UNIX)	Contains one error code per line
adapter.ini (Windows and UNIX)	Consists of all the initialization parameters that the adapter reads at startup

See Also: Appendix A, "adapter.ini Example File"

Table 2-4 HTTP Directories

Directory	Description
persistence	The messages are persisted (made available) in this directory. Do not edit this directory or its files.
logs	The logging of adapter activity is done in subdirectories of the logs directory. Subdirectory names take the following form: timestamp_in_milliseconds Each time the adapter is run, a new subdirectory is created in which logging is done in an oailog.txt file.

Hub.ini Parameter File

The HTTP 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

Table 2-5 Hub.ini Parameters

Parameter	Description	Example
hub_username	The name of the hub database schema (or username). The default value is oaihub904.	hub_username=oaihub904
hub_password	The password for the hub database user. There is no default value. You input the hub_password value during installation.	hub_password=manager
hub_host	The name of the machine hosting the hub database. There is no default value. You input the hub_host value during installation.	hub_host=mpjoshipc
hub_instance	The valid SID of the hub database. There is no default value. You input the hub_instances value during installation.	hub_instance=orcl
hub_port	The TNS listener port number for the HUB database instance. There is no default value. You input the hub_port value during installation.	hub_port=1521
repository_name	The valid name of the repository this adapter talks to. The default value is InterConnectRepository.	repository_name=InterConnectRepository

RAC-specific Hub.ini Parameters

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.

Table 2-6 RAC-specific Hub.ini Parameters

Parameter	Description	Example
hub_num_nodes	Number of nodes in Real Application Clusters.	hub_num_nodes=4
hub_hostx	The host where the Real Application Clusters database is installed.	hub_host2=dsunram13
hub_instancex	The instance on the respective node.	hub_instance2=orcl2
hub_portx	The port on which the listener is listening.	hub_port2=1521

Agent Connection Parameters

The agent component of the HTTP adapter reads the adapter.ini file at runtime to access HTTP adapter parameter configuration information. Table 2-7 lists the parameter name, a description for each parameter, the possible and default values, and an example.

Table 2-7 Agent Connection Parameters

Parameter	Description	Example
application	Specifies the name of the application to which this adapter connects. This must match with the name specified in iStudio during creation of metadata. Use any alphanumeric string. There is no default value.	application=aqapp
partition	Specifies the partition this adapter handles as specified in iStudio. Any alphanumeric string is a possible value. There is no default value.	partition=germany
instance_number	Specifies the instance number to which this adapter corresponds. Specify a value only if you want to have multiple adapter instances for the given application with the given partition. Possible values are any integer greater than or equal to 1. There is no default value.	instance_number=1
agent_log_level	Specifies the amount of logging necessary. Possible values are: 0=errors only 1=status and errors 2=trace, status, and errors The default value is 1.	agent_log_level=2
agent_subscriber_name	Specifies the subscriber name used when this adapter registers its subscription. The possible value is a valid Oracle Advanced Queue subscriber name. There is no default value.	agent_subscriber_name=httpapp
agent_message_selector	Specifies conditions for message selection when registering its subscription with the hub. The possible value is a valid Oracle Advanced Queue message selector string. There is no default value.	agent_message_selector=recipient_list, like '%,aqapp,%'
agent_reply_subscriber_name	Specifies the subscriber name used when multiple adapter instances for the given application with the given partition are used. This parameter is optional if only one instance is running. The possible value is the application name (parameter:application) concatenated with the instance number (parameter:instance_number). There is no default value.	If application=httpapp and instance_number=2, then agent_reply_subscriber_name=httpapp2
agent_reply_message_selector	Used only if multiple adapter instances exist for the given application with the given partition. The possible value is a string built using the concatenated application name (parameter:application) with the instance number (parameter:instance_number). There is no default value.	If application=httpapp and instance_number=2, then agent_reply_message_selector=recipient_list, like '%,httpapp2,%'
agent_tracking_enabled	Specifies if message tracking is enabled. Set this parameter to false to turn off all tracking of messages. Set this parameter to true to track messages with tracking fields set in iStudio. Possible values are true or false. The default value is true.	agent_tracking_enabled=true
agent_throughput_measurement_enabled	Specifies if the throughput measurement is enabled. Set this parameter to true to turn on all throughput measurements. Possible values are true or false. The default value is true.	agent_throughput_measurement_enabled=true
agent_use_custom_hub_dtd	Specifies whether to use a custom document type definition (DTD) for the common view message when handing it to the hub (the repository in which metadata is stored). By default, adapters use an OracleAS InterConnect-specific DTD for all messages sent to the hub, as other OracleAS InterConnect adapters retrieve the messages from the hub and know how to interpret them. Set this parameter to true if for every message, the DTD imported for the message of the common view is used instead of the OracleAS InterConnect DTD. Only set this parameter to true if an OracleAS InterConnect adapter is not receiving the messages from the hub. Possible values are true or false. There is no default value.	agent_use_custom_hub_dtd=false
agent_metadata_caching	Specifies the metadata caching algorithm. Possible values are: startup--Cache everything at startup. This may take a while if there are a lot of tables in the repository. demand--Cache metadata as it is used. none--No caching. This slows down performance. The default value is demand.	agent_metadata_caching=demand
agent_dvm_table_caching	Specifies the domain value mapping (DVM) table caching algorithm. Possible values are: startup--Cache all DVM tables at startup. This may take a while if many tables are in the repository. demand--Cache tables as they are used. none--No caching. This slows down performance. The default value is demand.	agent_dvm_table_caching=demand
agent_lookup_table_caching	Specifies the lookup table caching algorithm. Possible values are: startup--Cache all lookup tables at startup. This may take a while if many tables are in the repository. demand--Cache tables as they are used. none--No caching. This slows down performance. The default value is demand.	agent_lookup_table_caching=demand
agent_delete_file_cache_at_startup	With any of the agent caching methods enabled, metadata from the repository is cached locally on the file system. Set this parameter to true to delete all cached metadata on startup. Possible values are true or false. The default value is false. Note: After changing metadata or DVM tables for this 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_max_ao_cache_size	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.	agent_max_ao_cache_size=200
agent_max_co_cache_size	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.	agent_max_co_cache_size=100
agent_max_message_metadata_cache_size	Specifies the maximum number of messages' metadata (publish/subscribe and invoke/implement) to cache. Possible values are any integer greater than or equal to 1. The default value is 200.	agent_max_message_metadata_cache_size=200
agent_max_dvm_table_cache_size	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.	agent_max_dvm_table_cache_size=200
agent_max_lookup_table_cache_size	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.	agent_max_lookup_table_cache_size=200
agent_max_queue_size	Specifies the maximum size to which internal OracleAS InterConnect message queues can grow. Possible values are any integer greater than or equal to 1. The default value is 1000.	agent_max_queue_size=1000
agent_persistence_queue_size	Specifies the maximum size to which internal OracleAS InterConnect persistence queues can grow. Possible values are any integer greater than or equal to 1. The default value is 1000.	agent_persistence_queue_size=1000
agent_persistence_cleanup_interval	Specifies how often to run the persistence cleaner thread (in milliseconds). Possible values are any integer greater than or equal to 30000 milliseconds. The default value is 60000.	agent_persistence_cleanup_interval=60000
agent_persistence_retry_interval	Specifies how often the persistence thread retries when it fails to send an OracleAS InterConnect message. Possible values are any integer greater than or equal to 5000 milliseconds. The default value is 60000.	agent_persistence_retry_interval=60000
agent_pipeline_to_hub	Specifies how to turn on or off the pipeline for messages from the Bridge towards the hub. If you set the pipeline to false, the file persistence is not used in that direction.	agent_pipeline_to_hub=false
agent_pipeline_from_hub	Specifies how to turn on or off the pipeline for messages from the hub towards the Bridge. If you set the pipeline to false, the file persistence is not used in that direction.	agent_pipeline_from_hub=false
service_path	Windows only. Specifies the value to which to set the environment variable PATH. The PATH variable is set to the specified value before forking the Java VM. Typically, list all directories here that contain all necessary DLLs. Possible values are the valid PATH environment variable setting. There is no default value.	service_path=%JREHOME%\bin;D:\oracle\ora904\bin
service_classpath	Windows only. Specifies the class path used by the adapter Java VM. If a custom adapter is developed and, as a result, the adapter is to pick up any additional jars, add the jars to the existing set of jars being picked up. Possible values are the valid class path. There is no default value.	service_classpath=D:\oracle\ ora904\oai\904\lib\ oai.jar;%JREHOME%\lib\rt.jar;D:\oracle\ora904\jdbc\classes12.zip
service_class	Specifies the entry class for the Windows service. A possible value is oracle/oai/agent/service/AgentService. There is no default value.	service_class=oracle/oai/agent/ service/AgentService
service_max_java_stack_size	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.	service_max_java_stack_size=409600
service_max_native_stack_size	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.	service_max_native_stack_size=131072
service_min_heap_size	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 536870912.	service_min_heap_size=536870912
service_max_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.	service_max_heap_size=536870912
service_num_vm_args	Windows only. Specifies the number of service_vm_argnumber parameters specified. Possible values are the number of service_vm_argnumber parameters. There is no default value.	service_num_vm_args=1
service_vm_argnumber	Windows only. Specifies any additional arguments to the Java VM. For example, to retrieve line numbers in any of the stack traces, set service_vm_arg1=java.compiler=NONE. If a list of arguments to specify exists, use multiple parameters as shown in the example by incrementing the last digit starting with 1. Be sure to set service_num_vm_args correctly. Possible values are any valid Java VM arguments. There is no default value.	service_vm_arg1=java.compiler=NONE service_vm_arg2=oai.adapter=database
corba_port_number	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.	corba_port_number=14000
encoding	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 UTF-8. However, this encoding can be configured using this parameter, which is typically used when the OracleAS InterConnect message consists of characters not supported by UTF-8 and when the XMLParser is unable to handle them.	encoding=JA16SJIS
nls_date_format	Format for date fields expressed as string. The default date format is EEE MMM dd HH:mm:ss zzz yyyy. For the meaning of this string, see the list of reserved characters in Table 2-8.	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_country	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, http://www.chemie.fu-berlin.de/diverse/doc/ISO_3166.html The default Country code is US. Note: This parameter specifies date format. It is applicable for the date format only.	US
nls_language	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, http://www.ics.uci.edu/pub/ietf/http/related/iso639.txt The default language code is en. Note: This parameter specifies date format. It is applicable for the date format only.	nls_language=en

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-8 Reserved Characters for the Value of the nls_date_format Parameter

Letter	Description	Example
G	Era designator	AD
y	Year	1996; 96
M	Month in year	July; Jul; 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; 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
G	Era designator	AD

HTTP Adapter-Specific Parameters

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

Table 2-9 HTTP Adapter-Specific Parameters

Parameter	Description	Example
bridge_class	Specifies the entry class for the HTTP adapter. A value must be specified and cannot be modified later. A possible value is oracle.oai.agent.adapter.technology.TechBridge. There is no default value.	bridge_class=oracle.oai.agent.adapter.technology.TechBridge
ota.send.endpoint	Defines the sending endpoint URL for the HTTP adapter. There is no default value. The URL is of the form: http(s)://hostname:port/path	ota.send.endpoint=http://site.com:8888/servlet/inbound
ota.receive. endpoint	Defines the receiving endpoint URL for the HTTP adapter. There is no default value. The URL is of the form: http(s)://hostname:port/path	ota.receive.endpoint= http://site.com:8888/ servlet/inbound
ota.type	Defines the message payload type the HTTP adapter handles for both incoming and outgoing messages. The options are XML, XML_NVP, or D3L. The default value is XML.	ota.type=XML
ota.d3ls	Specifies the list of D3L XML files used by this bridge. Each business event handled by the bridge must have its own D3L XML file. When a new D3L XML file is imported in iStudio for use by an application using the HTTP adapter, the parameter must be updated and the HTTP adapter restarted.	ota.d3ls=person.xml, person1.xml
http.sender.timeout	Times out an HTTP connection. The unit is in milliseconds. The default is set to 60000 milliseconds (60 seconds).	http.sender.timeout= 10000 (Sets timeout to 10 seconds)
http.sender.authtype	Set if authentication is needed. The valid options are basic or digest. There is no default value.	http.sender.authtype= basic
http.sender.realm	Specifies the realm for the authentication scheme. There is no default value.	http.sender.realm=ipt
http.sender.username	Specifies the authentication username. There is no default value.	http.sender.username= joe
http.sender.password	Specifies the password used in the sender.password authentication. There is no default value. This password can also be encrypted by running the encrypt tool and renaming this parameter to encrypted_http.sender.password. See Also: "How do I make the adapter.ini file password parameters secure?" for instructions on encrypting the user password	http.sender.password= httpuser
http.sender.proxy_host	Specifies the proxy hostname. There is no default value.	http.sender.proxy_host=www-proxy.foo.com
http.sender.proxy_port	Specifies the port number for the proxy host. This is needed if the proxy host is set. There is no default value.	http.sender.proxy_port=80
http.sender.wallet_location	Needed if SSL is used. This specifies the path and name of the exported wallet file (not .p12 file). There is no default value.	http.sender.wallet_location=/private/foo/ certdb.txt
http.sender.wallet_password	Needed if SSL is used. This specifies the password for the Oracle Wallet Manager. There is no default value. This password can also be encrypted by running the encrypt tool and renaming this parameter to encrypted_http.sender.wallet_password. See Also: "How do I make the adapter.ini file password parameters secure?" for instructions on encrypting the wallet password	http.sender.wallet_password=walletuser
http.sender.cipher_suites	Optional parameter for choosing the cipher suites. The selections are: SSL_RSA_WITH_3DES_EDE_CBC_SHA SSL_RSA_WITH_RC4_128_SHA SSL_RSA_WITH_RC4_128_MD5 SSL_DH_anon_WITH_3DES_EDE_CBC_SHA SSL_DH_anon_WITH_RC4_128_MD5 SSL_DH_anon_WITH_DES_CBC_SHA SSL_RSA_WITH_DES_CBC_SHA SSL_RSA_EXPORT_WITH_RC4_40_MD5 SSL_RSA_EXPORT_WITH_DES40_CBC_SHA SSL_DH_anon_EXPORT_WITH_RC4_40_MD5 SSL_DH_anon_EXPORT_WITH_DES40_CBC_SHA SSL_RSA_WITH_NULL_SHA SSL_RSA_WITH_NULL_MD5	http.sender.cipher_suites=SSL_RSA_WITH_NULL_SHA,SSL_RSA_WITH_3DES_EDE_CBC_SHA
http.sender.customizer_class	Specifies the class name for customizing by the HTTP sender. The default value is: oracle.oai.agent.adapter.technology.HTTPDefaultSenderCustomizer	http.sender.customizer_class=MyHTTPSenderCustomizer
http.receiver.registry_port	Specifies the RMI port used by the HTTP receiver. The default is 9901.	http.receiver.registry_port=9901
http.receiver. instance_name	Specifies the instance name of the HTTP receiver. The default is oai. If the default value is not used, the instanceName of the initial parameter of the transport servlet must be modified to match this instance name.	http.receiver.instance_name=oai
http.receiver. customized_class	Specifies the class name for customizing the HTTP response.	http.receiver. customized_class=MyBanner
http.receiver.customizer_class	Specifies the class name for customizing by the HTTP sender. The default value is: oracle.oai.agent.adapter.technology.HTTPDefaultSenderCustomizer	http.receiver.customizer_class=MyHTTPReceiverCustomizer