A Frequently Asked Questions

This chapter provides answers to frequently asked questions about the HTTP adapter.

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

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

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

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

• Can I install multiple HTTP adapters on the same computer?

• How do I install a second HTTP adapter in the same Oracle home?

• How do I secure my passwords?

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

View the oailog.txt file located in the timestamped 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 (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.

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:

Can I install multiple HTTP adapters on the same computer?

You can install multiple HTTP adapters on the same computer by specifying a different Oracle home for each adapter during the installation process. If you try to install a second adapter in the same Oracle home, then the installer overwrites previous installations of the HTTP adapter. However, you can still install multiple adapters in the same Oracle home, by using the copyAdapter utility and manually editing some configuration files.

How do I install a second HTTP adapter in the same Oracle home?

To install a second HTTP adapter in the same Oracle home, perform the following steps:

1. Use the copyAdapter utility to make a copy of the existing HTTP adapter:

   On UNIX:

   % cd ORACLE_HOME/integration/interconnect/bin
   % copyAdapter oldAdapterName newAdapterName
   
   

   On Windows:

   c:\> cd ORACLE_HOME\integration\interconnect\bin
   c:\> copyAdapter oldAdapterName newAdapterName
   
   

2. Change the parameters in the adapter.ini file for the new adapter. Ensure the parameters in the new adapter.ini file are different from the adapter.ini file for the existing HTTP adapter, as follows:

   1. Change the send endpoint (ota.send.endpoint) parameter.

   2. Change the receive endpoint (ota.receive.endpoint) parameter.

      The default receive endpoint set by the installer is:

      http://machine name:port number/oai/servlet/transportServlet
      
      

      You can change the receive endpoint to the following:

      http://machine name:portnumber/oai1/servlet/transportServlet
      
      

   3. Change the payload type parameter (ota.type), if necessary.

   4. Change the RMI registry port parameter (http.receiver.registry_port) to a port not used on this computer.

3. Change the content of the web.xml file to match that of the adapter.ini file. The web.xml file is in the following directory:

   On UNIX:

   ORACLE_HOME/integration/interconnect/adapters/newAdapterName/webapps/WEB-INF
   
   

   On Windows:

   ORACLE_HOME\integration\interconnect\adapters\newAdapterName\webapps\WEB-INF
   
   

4. Change the RMI port to match the value entered in Step 2d.

5. Change the following entry in the web.xml file from:

   <param-value>9901</param-value>
   
   

   to:

   <param-value> port-number-you-used-step-2d </param-value>
   
   

6. Change the following entry in the application.xml file in the ORACLE_HOME\integration\interconnect\adapters\<your new http app name>\webapps\META-INF directory:

   <context-root>oai/servlet</context-root>
   
   

   to:

   <context-root>oai1/servlet</context-root>
   
   

7. Create the Java archive parameter (oai1.ear):

   On UNIX:

   % cd ORACLE_HOME/integration/interconnect/adapters/<your http app name>/webapps
   % jar cvf oai.war WEB-INF
   % jar cvf oai1.ear oai.war META-INF
   
   

   On Windows:

   c:\> ORACLE_HOME\integration\interconnect\adapters\<your new http app name>\webapps
   c:\> jar cvf oai.war WEB-INF
   c:\> jar cvf oai1.ear oai.war META-INF
   
   

   An .ear file called oai1.ear has been created, which is ready for deployment.

8. Deploy the oai1.ear file in the OracleAS environment:

   On UNIX:

   % cd ORACLE_HOME/dcm/bin
   % dcmctl shell
   dcmctl> deployApplication -f oai1.ear  -a oaiservlet1 -co oc4j_oai
   dcmctl> exit
   
   

   On Windows:

   c:\> ORACLE_HOME\dcm\bin\dcmctl shell
   dcmctl> deployApplication -f oai1.ear  -a oaiservlet1 -co oc4J_OAI
   dcmctl> exit
   
   

   
   

   Note: oaiservlet1 is a unique application name that you assign to your servlet. If this name is already used in the current environment, then select a different name.

   
   

9. Restart the HTTP server. Verify whether the new receiving endpoint is functioning by entering the URL used in Step 2b. If the servlet is deployed correctly, then a diagnostic page is displayed.

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

For example,

AQAPP/aq_bridge_schema_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.

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