Connection Manager Architecture
Connection Manager’s architecture seems a bit odd when compared with other Net8 components such as Oracle Names and the Net8 listener. Connection Manager runs as two processes—one to manage administrative details and the other to act as a relay between clients and servers. Table 9.1 lists the responsibilities of each process.
Table 9-1. Connection Manager Processes
|
Process |
Responsibilities |
|---|---|
|
Connection Manager Gateway Process (CMGW) |
Listens for incoming connection requests from clients. Relays connection requests from clients to listeners. Relays data between clients and database services. |
|
Connection Manager Administrative Process (CMADMIN) |
Identifies listeners that are serving databases. Locates Oracle Names servers. Registers information with CMGW and the listeners. Registers address information with Oracle Names servers. |
The commands to start and stop Connection Manager start and stop both processes by default. It is possible, however, to run just the Connection Manager Gateway Process (CMGW) without a corresponding Connection Manager Administrative Process (CMADMIN), and the START and STOP commands support that.
Get Oracle Net8 Configuration and Troubleshooting now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
