Skip Headers
Oracle® Application Server Integration InterConnect Adapter for HTTP Installation and User's Guide
10g Release 2 (10.1.2)
B14074-02
  Go To Documentation Library
Home
Go To Product List
Solution Area
Go To Table Of Contents
Contents
Go To Index
Index

Previous
Previous
Next
Next
 

B Example of the adapter.ini File

This appendix shows an adapter.ini example file for the HTTP adapter.


See Also:

"Configuring the HTTP Adapter" for additional information on adapter.ini configuration parameters

This section shows an adapter.ini example file for the HTTP adapter.

#include <../../hub/hub.ini> 
// ************* 
// ** Adapter ** 
// ************* 
// Application (as created in iStudio) corresponding to this Adapter. 
application=HTTPapp1 
// Partition (as created in iStudio) corresponding to this Adapter. 
partition= 
// If you want to have multiple adapter instances for a given application with the
// given partition, each Adapter should have an instance number. 
// instance_number=2 
// Bridge class 
bridge_class=oracle.oai.agent.adapter.technology.TechBridge 

//------------------------------------------ 
// HTTP Adapter Endpoint information 
//------------------------------------------- 
// time out in milli seconds (default should be set to 60000 milli seconds) 
// This is used to time out a http connection. Use default. 
// http.sender.timeout= 

// set the following if authentication is needed. 
// authentication type (Valid options: basic or digest) 
http.sender.authtype= basic 
http.sender.realm=ipt 
http.sender.username=scott 
encrypt_http.sender.password=112411071071106510801094108410731070107110811069 

// set the proxy parameters if proxy is needed. 
http.sender.proxy_host=www-proxy.test.com 
http.sender.proxy_port=80 
  

// set the security parameters if SSL is used. 
http.sender.wallet_location=certdb.txt 
encrpyt_http.sender.wallet_password=112411071071106510801094108410731070107110811070 
// 
//   If this is not set, we will use the 
//   default ciphers suites provided by 
//   SSLSocketFactory. 
//   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 
// Use "," as delimiter. An example cipher suites  is: 
//  SSL_RSA_WITH_3DES_EDE_CBC_SHA,SSL_RSA_WITH_NULL_SHA 
// 
//http.sender.cipher_suites= 
  
  

//----------------------------------------- 
// HTTP Receiver initialization variables 
//----------------------------------------- 

// rmi port used by http receiver (default is 1099) 
http.receiver.registry_port = 1099 

// instance name to distinguish other instances of receiver
http.receiver.instance_name =oai 
  

// A list of the D3L XML files used by this Bridge. Each business event handled 
// by the Bridge must have it's own D3L XML file. 
// Whenever a new D3L XML file has been imported in iStudio to be used by 
// an application using the HTTP adapter, the following parameter must 
// be updated and the adapter restarted. 
ota.d3ls=person.xml, person1.xml 
  

// ************* 
// ** Agent  *** 
// ************* 

// Log level (0 = errors only, 1 = status and errors, 2 = trace, status and errors). 
agent_log_level=2 

// Hub message selection information 
agent_subscriber_name=HTTPapp1 
agent_message_selector=recipient_list like '%,HTTPapp1,%' 
// Only provide values for the next two parameters if you have multiple Adapter
// instances for the given application with the given partition. 
//agent_reply_subscriber_name= 
//agent_reply_message_selector= 

// Set this to false if you want to turn off all tracking of messages (if true,
// messages which have tracking fields set in iStudio will be tracked)
agent_tracking_enabled=true 

// Set this to false if you want to turn off all throughput measurements 
agent_throughput_measurement_enabled=true 

// By default, adapters use an OAI specific DTD for all messages sent to the Hub
// because other OAI adapters will be picking up the messages from the Hub 
// and know how to interpret them. This should be set to true if for every
// message,you would like to use the DTD imported for that message's Common View
// instead of the OAI DTD.  This should only be set to true if an OAI Adapter is
// *NOT* receiving the messages from the Hub.
agent_use_custom_hub_dtd=false 

// Sets the metadata caching algorithm. The possible choices are startup (cache
// everything at startup: this may take a while if there is a lot of metadata
// in your Repository), demand (cache metadata as it is used) or none (no caching
//: this will slow down performance.) 
agent_metadata_caching=demand 

// Sets the DVM table caching algorithm.  The possible choices are startup (cache
// all DVM tables at startup: this may take a while if there are a lot of tables
// in your Repository), demand (cache tables as they are used) or none (no caching
//: this will slow down performance.) 
agent_dvm_table_caching=demand 

// Sets the lookup table caching algorithm.  The possible choices are startup
// (cache all lookup tables at startup: this may take a while if there are
// a lot of tables in your Repository), demand (cache tables as they are used) or
// none (no caching: this will slow down performance.) 
agent_lookup_table_caching=demand 

// If metadata caching, DVM table caching, or lookup table caching are turned on
// (startup or demand) then the Adapter caches metadata or DVM tables it retrieves
// from the Repository in a file cache.  When you restart the Adapter, it will not
// have to get that metadata or DVM table from the Repository again because it is
// in the cache files.  However, if you change some metadata or DVM table
// using iStudio and you want the Adapter to use those changes the next time it is
// started, you can either delete the cache files or set this parameter to true
// before restarting.
agent_delete_file_cache_at_startup=false 

// Max number of application data type information to cache 
agent_max_ao_cache_size=200 

// Max number of common data type information to cache 
agent_max_co_cache_size=100 

// Max number of message metadata to cache 
agent_max_message_metadata_cache_size=200 

// Max number of DVM tables to cache 
agent_max_dvm_table_cache_size=200 

// Max number of lookup tables to cache 
agent_max_lookup_table_cache_size=200 

// Internal Agent queue sizes 
agent_max_queue_size=1000 
agent_Persistence_queue_size=1000 

// Persistence 
agent_persistence_cleanup_interval=60000 
agent_persistence_retry_interval=60000