4
Frequently Asked Questions

This chapter provides answers to frequently asked questions about the Hypertext Transfer Protocol (HTTP) adapter.

This chapter contains this topic:

• Troubleshooting Questions

Troubleshooting Questions

The following questions address troubleshooting issues for the HTTP adapter.

How do I know the HTTP adapter started properly?

View the oailog.txt file located in the appropriate timestamped subdirectory of the HTTP adapter logs directory.

On...	Go to...
UNIX	$ORACLE_HOME/oai/9.0.2/adapters/Application/logs/timestamp_in_milliseconds
Windows	%ORACLE_HOME%\oai\9.0.2\adapters\Application\logs\timestamp_in_milliseconds

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

The HTTP adapter did not start properly - what is wrong?

View the exceptions in the adapter log file (oailog.txt). 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.

See Also: Oracle9iAS InterConnect User's Guide for instructions on starting the repository on UNIX and Windows

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

The HTTP adapter caches the information from iStudio (the information that is stored in the repository) locally for better performance in a production environment. If you change something in iStudio and want to see the change in the runtime environment, you need to perform the following procedures:

To see iStudio changes in the runtime environment:

1. Stop the affected adapters.

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, edit the parameters in the following file:

On...	Go to...
UNIX	$ORACLE_HOME/oai/9.0.2/adapters/Application/adapter.ini
Windows	%ORACLE_HOME%\oai\9.0.2\adapters\Application\adapter.ini

Note: All configuration parameters with the exception of bridge_class can be edited more than once.

See Also: "adapter.ini Initialization Parameter File" for parameter information

Can I install multiple HTTP adapters on the same computer?

The installer overwrites previous installations of the HTTP adapter if you try to install it a second time in the same Oracle home. However, you can have multiple Oracle homes on a computer and have one HTTP adapter in each Oracle home. When you install the HTTP adapter a second time, choose a different Oracle home from the first HTTP adapter.

How do I make the adapter.ini file password parameters secure?

In order to encrypt password values specified in the adapter.ini file, perform the following steps:

To encrypt password values:

1. Locate the password value to encrypt.

2. Run the encrypt utility to encrypt the password value. The encrypt utility is located in the $ORACLE_HOME/oai/9.0.2/bin directory for UNIX and the %ORACLE_HOME%\oai\9.0.2\bin directory for Windows. For example, to encrypt the http.sender.password parameter, enter the following:

   encrypt password
   

3. Prefix the name of the parameter in the adapter.ini file with encrypted_:

   encrypted_http.sender.password
   

4. Replace the value with the new encrypted value created in Step 2. For example, if you want to encrypt the password for the parameter http.sender.password, replace the line:

   http.sender.password=HTTPuser
   

   with the value you received from running the encrypt tool in Step 2:

   encrypted_http.sender.password=112411071071106510801094108410731070107110811069
   

   Note: You can also encrypt the http.sender.wallet_password parameter by performing these instructions.