A Frequently Asked Questions

How do I know whether the HTTP adapter has started properly?

View the log.xml file located in the time-stamped subdirectory of the HTTP adapter logs directory.

where Application is the value you defined in Step 4, and timestamp_in_milliseconds is the directory. If no exceptions are listed, then the adapter has started properly.

The HTTP adapter did not start properly. What is wrong?

View the exceptions in the adapter log file (log.xml). The exceptions provide information about inconsistencies. One possible reason is that the HTTP adapter did not connect to the repository. Ensure that the repository is started properly and the HTTP adapter connects to the repository once it is started properly. You do not need to restart the adapter.

The HTTP adapter is not starting. What could be the reason?

If you are starting the adapter for the first time or if you have set the agent_metadata_cache parameter to none or demand, then check if the repository is up and running. In addition, check if the hub database is up and running.

One reason can be that Oracle Wallet does not contain the password information corresponding to your application name. For example, during installation you defined the application name as myHTTPApp. Later, you changed the application name in iStudio to HTTPApp. In such case, you need to specify the password corresponding to the new application name HTTPApp in the Oracle Wallet. You can create password by using the oraclewallet command.

I changed an element in iStudio, but the HTTP adapter uses old information. What is happening?

The HTTP adapter caches information from iStudio. The information is stored locally in the repository. If you change something in iStudio and want to view the change in the runtime environment, then you need to perform the following procedure:

1. Stop the adapter.

2. Delete the adapter cache files.

3. Restart the adapter.

Each adapter has a persistence directory located in the directory named after the HTTP application. Deleting this directory when the adapter has been stopped makes the adapter obtain the new metadata from the repository when started.

If I cannot answer some HTTP configuration questions or I make a mistake during installation, can I edit these settings later?

Yes, you can edit the parameters in the following file:

HTTP adapter does not publish or subscribe to messages

The HTTP adapter is not publishing or subscribing to the messages.

Problem 1

The Transport properties of the HTTP adapter might not be correct.

Solution 1

Specify 2 as the value of the log level parameter agent_log_level in the adapter.ini file of the HTTP adapter. Restart the adapter and try to publish a message or subscribe to a message. You can see a log starting with TransportProperties.TransportProperties(). This log contains all the transport properties of the HTTP adapter in the form of name value pairs. Ensure that the values of these properties are correct.

Problem 2

You might not have created a publish or subscribe event in iStudio for the HTTP adapter that corresponds to the message structure. The HTTP adapter is not able to match the message data to any of the events defined during design time and therefore cannot publish or subscribe the message.

Solution 2

Create a publish or subscribe event for the HTTP adapter in iStudio corresponding to the message structure.

Problem 3

The transport servlet is not deployed properly.

Solution 3

Ensure that the transport servlet that receives the messages over HTTP and directs these messages to the HTTP receiver through RMI is deployed properly. In addition, you should never change the http.receiver.instance_name parameter in the adapter.ini file after the adapter installation.

Problem 4

The send endpoint defined by the ota.send.endpoint parameter in the adapter.ini file or in iStudio is incorrect.

Solution 4

Ensure that the send endpoint defined in the adapter.ini file or iStudio is correct. If the send endpoint expects the message in some particular form, then you can customize the outgoing messages using the SenderCustomizer parameter.

How do I secure my passwords?

OracleAS Integration InterConnect uses Oracle Wallet Manager to maintain system passwords. When you install OracleAS Integration InterConnect, Oracle Wallet Manager is also installed and a password store is created. All passwords used by OracleAS Integration InterConnect components are stored in the password store. The password is stored in the Oracle Wallet in the following format:

ApplicationName/password

The ApplicationName is the name of the application, which is extracted from the adapter.ini file of the corresponding adapter. In the adapter.ini file, the application parameter specifies the ApplicationName to which this adapter connects. The password for the application is also retrieved from the adapter.ini file.

The number of entries is dependent on the type of adapter. For example, DB Adapter needs two entries whereas AQ Adapter needs only one entry. The following table lists the entries that will be created for each adapter:

You can create, update, and delete passwords using the oraclewallet command. When you run the command, it prompts you for the admin password.

You can use the following commands to manage your passwords:

• List all passwords in the store

  oraclewallet -listsecrets
  
  

• Create a password

  oraclewallet -createsecret passwordname
  
  

  For example, to create a password for the hub schema:

  oraclewallet -createsecret hub_password
  
  

• View a password

  oraclewallet -viewsecret passwordname
  
  

  For example, to view the password for the hub schema:

  oraclewallet -viewsecret hub_password
  
  

• Update a password

  oraclewallet -updatesecret passwordname
  
  

  For example, to update the password for the hub schema:

  oraclewallet -updatesecret hub_password
  
  

• Delete a password

  oraclewallet -deletesecret passwordname
  
  

  For example, to delete the password for the hub schema:

  oraclewallet -deletesecret hub_password
  
  

How can I deliver a message to a specific partition of the publishing adapter?

Scenario: HTTP adapter has two partitions PAR1 and PAR2. You want to deliver event create_customer to partition PAR1 and add_customer event to partition PAR2.

Perform the following tasks:

1. Assign event create_customer to partition PAR1 and event add_customer to partition PAR2.

2. Deploy two transportServlets in the OC4j container. For example TRANSPORTSERVELET1 and TRANSPORTSERVELET2.

3. Configure the adapter with partition name PAR1 to receive messages from TRANSPORTSERVLET1 and adapter with partition name PAR2 to to receive messages from TRANSPORTSERVLET2.

4. Publish the message for event create_customer to TRANSPORTSERVLET1 and the event add_customer to TRANSPORTSERVLET2.