This is a text description of Figure 5-4, "Defining the Oracle Server to Oracle Access Manager".

This illustration of Oracle Access Manager architecture is adequately described in the "Defining the Oracle Server to Access Manager" section of the chapter, which is presented near the figure.

The figure has the same five boxes and labels as figure 5-3. In addition, the first three boxes have downward pointing arrows that point to examples of code that these components are sending or receiving.

The first box (starting from the left side) is labeled "Oracle Access Manager for AS/400 SQL application". Its downward arrow points to the following message code:

...
...
EXEC SQL CONNECT TO ORA2
...
...
or
CRTSQLxxx RDB (ORA2)

The second box is labeled "RDBDIRE lookup". Its downward arrow points to the following message code:

RDB(ORA2)
RMTLOCNAME (*ARDPGM)

The third box is labeled "TNSNAMES lookup". Its downward arrow points to the following message code:

ORA2=(DESCRIPTION=
(ADDRESS=(PROTOCOL=TCP)
...
...
...
))

The purpose of this figure is to show how an AS/400 application can use Oracle Access Manager, an IBM networking connection, and Oracle Net (running on the AS/400) to have access to one or more Oracle Database servers. In this example, the remote database name (on the Oracle server) is "ORA2", and it is used as the key for both the (IBM) RDBDIRE lookup and the (Oracle) TNSNAMES lookup. The connection to the Oracle Database through Oracle Net must use an Oracle Net TNSNAMES entry with a name that matches the AS/400 RDBDIRE entry. The figure illustrates how these matching entries can interact to complete the data connection.