5
Frequently Asked Questions

This chapter provides answers to frequently asked questions about the Advanced Queuing adapter. This chapter discusses the following topics:

Installation Questions

The following questions address the installation of the Advanced Queuing adapter.

How do I know the Advanced Queuing adapter is started properly?

View the oai.txt file located in the appropriate timestamped subdirectory of the Advanced Queuing adapter log directory:

Platform	Directory
UNIX	`ORACLE_HOME``/oai/9.0.4/adapters/``Application``/log/``timestamp_in_milliseconds`
Windows	`ORACLE_HOME``\oai\9.0.4\adapters\``Application``\log\``timestamp_in_milliseconds`

If there are no exceptions, the Advanced Queuing adapter has started properly.

The Advanced Queuing adapter did not start properly--what went wrong?

View the exceptions in the Advanced Queuing adapter log file (oailog.txt). The exceptions should provide some idea about what went wrong. It is possible that the Advanced Queuing adapter is unable to connect to the repository. Make sure the repository is started properly. The Advanced Queuing adapter will connect to the Repository once it is started properly. You do not need to restart the Adapter.

See Also:

Oracle Application Server InterConnect User's Guide for instructions on starting the repository on UNIX and Windows

Why is the Advanced Queuing adapter using old information after I changed information in iStudio?

The Advanced Queuing adapter caches the information from iStudio (the information which is stored in the Repository) locally for better performance in a production environment.

If you change something in iStudio and want to see it in the runtime environment, stop the Advanced Queuing adapter, delete the cache files, and restart the adapter.

Each adapter has a persistence directory located in the adapter's directory. Deleting this directory when adapter has been stopped should allow the adapter to obtain the new metadata from the repository when started.

Which databases are referred to during installation?

The database the questions are referring to is the database on the application side from which the adapter will either put or get messages from Advanced Queuing.

What is the consumer name?

If all the queues the Advanced Queuing adapter connects to on the application database side are single consumer queues, leave this blank. However, if any one of the queues is a multiconsumer queue, then specify a consumer name.

The application that writes to the Advanced Queuing adapter uses a consumer name to indicate to OracleAS InterConnect to pick up this message. The following two options help you to find out the consumer name to use:

If the piece of code that writes the message to the Advanced Queuing adapter is already written, look at that code or the documentation that comes with it to find the consumer name.
If the piece of code that writes the message to the Advanced Queuing adapter is not written, type in any string as the consumer name. When that piece of code is built, ensure that the consumer names match.

Can I edit configuration settings after installation?

Yes, edit the parameters in the following file:

Platform	Directory
UNIX	`ORACLE_HOME``/oai/9.0.4/adapters/``Application``/adapter.ini`
Windows	`ORACLE_HOME``\oai\9.0.4\adapters\``Application``\adapter.ini`

The following table lists the parameters and their corresponding questions in the installation:

Parameter	Parameter Information
`aq_bridge_username`	username
`aq_bridge_password`	Password
`aq_bridge_host`	Host
`aq_bridge_port`	The TNS listener port.
`aq_bridge_instance`	The database SID.
`aq_bridge_owner`	The Advanced Queuing owner. Enter the value if your Advanced Queuing adapter is installed under a different user than `aq_bridge_username`.
`aq_bridge_consumer_name`	The consumer name.
`aq_bridge_thinjdbc`	Use a THIN JDBC driver if true, otherwise use OCI8 JDBC driver.

Design Time Questions

The following questions address design time concepts for the Advanced Queuing adapter.

Can I install multiple Advanced Queuing adapters on the same machine?

The installer overwrites previous installations of the Advanced Queuing 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 Advanced Queuing adapter in each Oracle home. When you install the Advanced Queuing adapter a second time, choose a different Oracle home from the first Advanced Queuing adapter.

How do I handle `ANY` tags in DTDs imported into iStudio?

ANY tags in an XML DTD allow unstructured data in XML to be used. OracleAS InterConnect, however, must know about the structure of that data (using a DTD) if that data is to be used in mappings.

There are two methods for OracleAS InterConnect to know about the structure:

The simplest method is to modify the DTD being importing into iStudio and replace the ANY tag with structured data. When modifying the DTD, only a copy of the DTD being importing into iStudio is modified, not the published version of the DTD. For example, if the USERAREA ANY tag is edited before importing the DTD into iStudio, only a copy is changed and the published OAG definition which other people who download the OAG DTDs would use is not changed.

This approach also supports using a PCDATA for an ANY tag.

For example, consider the following customer.dtd:
```
<!ELEMENT customer (name, phone, address)>
<!ELEMENT name (#PCDATA)>
<!ELEMENT phone (#PCDATA)>
<!ELEMENT address ANY)>
```
This customer.dtd can be changed to the following:
```
<!ELEMENT customer (name, phone, address)>
<!ELEMENT name (#PCDATA)>
<!ELEMENT phone (#PCDATA)>
<!ELEMENT customer (name, phone, address)>
<!ELEMENT name (#PCDATA)>
<!ELEMENT phone (#PCDATA)>
<!ELEMENT address (#PCDATA)>
<!ELEMENT street (#PCDATA)>
<!ELEMENT city (#PCDATA)>
<!ELEMENT zip (#PCDATA)>
```
This is dependent on what the XML will conform to at runtime. If the XML will use the ANY tag in different ways at runtime, a union can be used. For example, if address has street, city, and state only for some instances and for other instances only has zip, a standard DTD union mechanism for doing this can be used.
The following steps describe a second approach which involves creating a separate DTD which defines the structure used at runtime for the ANY tag.
1. Import the DTD for the event, either while creating an ADT or while creating the published or subscribed event or the invoked or implemented procedure. iStudio warns about the ANY tag and points out the type that needs to be modified.
2. Reload the iStudio project.
3. Under the list of ADTs, find the type corresponding to the ANY element and right click to display the context menu. This is the ADT mentioned in step a
4. Import a DTD which defines the structure planned to use for the ANY tag.
This method does not support using a PCDATA tag for the ANY element. The ANY element must have a sub-element in this case.

For example, consider the following customer.dtd:
```
<!ELEMENT customer (name, phone, address)>
<!ELEMENT name (#PCDATA)>
<!ELEMENT phone (#PCDATA)>
<!ELEMENT address ANY)>
```
When this DTD is imported, iStudio warns that the address tag is an ANY tag and it corresponds to the address ADT in iStudio.

The address_any.dtd could look like the following:
```
<!ELEMENT address_any (street, city, zip)>
<!ELEMENT street (#PCDATA)>
<!ELEMENT city (#PCDATA)>
<!ELEMENT zip ANY)>
```
Then import the address_any.dtd by right-clicking on the address ADT in iStudio. This assumes the XML has an address_any element under the address element as follows:
```
<address>
  <address_any>
    <street>
    <city>
    <zip>
  </address_any>
</address>
```
If the address_any element is not needed, then instead of editing the address ADT, edit customer ADT and change the type of address attribute from address to address_any, after importing address_any elsewhere. The following is now true:
```
<address>
  <street>
  <city>
  <zip>
</address>
```

5 Frequently Asked Questions