Configuring a Client

Configuring a client to use Connection Manager involves making some changes to the definitions of the net service names used by that client. If you’re using Oracle Names (or some other central repository for service names) then you can make the changes centrally. Otherwise, you’ll need to make changes to your client’s tnsnames.ora file.

Connection Concentration

Connection concentration is attained by routing Net8 connections from the client, through Connection Manager, and then on to the server. To accomplish that, you need to configure your net service names with two addresses instead of just one. The first address points to the Connection Manager instance, and the second address points to the Net8 listener on the database server. The addresses should be embedded within an address list. For example:

PROD.GENNICK.ORG =
  (DESCRIPTION =
    (ADDRESS_LIST =
      (ADDRESS = (PROTOCOL = TCP)(HOST = cman01.gennick.org)(PORT = 1630))
      (ADDRESS = (PROTOCOL = TCP)(HOST = donna.gennick.org)(PORT = 1523))
    )
    (SOURCE_ROUTE = YES)
    (CONNECT_DATA =
      (SERVICE_NAME = donna.gennick.org)
    )
  )

If you read Chapter 8, you’re probably thinking that this looks a lot like the setup you would use to implement either of those features. It is. The key difference is the use of the SOURCE_ROUTE parameter. Setting (SOURCE_ROUTE = YES) tells Net8 that Connection Manager is being used and that the connection should be routed through each address in sequence. Here is what happens when you connect using this ...

Get Oracle Net8 Configuration and Troubleshooting now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.