[Laskey99] Section 5.3. MultiProtocol Interchange

Modern networks can be extremely complex, supporting multiple network protocols in a large, geographically dispersed network. In order to truly support network independence, SQL*Net must be able to communicate using more than one protocol. For example, a truly independent and open system would allow a workstation running IPX/SPX in a Novell environment to access an Oracle server running TCP/IP in a Unix environment. To provide this capability, Oracle developed the MultiProtocol Interchange (MPI).

The MultiProtocol Interchange performs protocol conversions to allow SQL*Net data originating on a network utilizing one protocol to flow to a network utilizing a different protocol. Figure 5.4 shows a node on a network running IPX with the MPI in the center connecting to a network and server running TCP.

Figure 5.4. Using MultiProtocol Interchange

As can be seen from this figure, the MultiProtocol Interchange requires:

• A host machine (which may be a PC)

• The MPI software

• Two or more network interface cards (NICs), one for each supported protocol

• Appropriate software to implement the supported network protocols

Because the MPI utilizes multiple NICs, it is able to convert data not only from one protocol to another, but also from one physical network implementation to another. For example, a MultiProtocol Interchange may convert SQL*Net data from token ring to 10BaseT.

The MPI runs as a process on a host machine, which may be as simple as a PC workstation. The MPI is configured using the Oracle Network Manager, which specifies the location in the network of any MultiProtocol Interchanges in use, as well as routing information (including cost data) and the protocols supported.

The MPI consists of a listener and a data pump. These components function in a manner similar to the SQL*Net Multi-Threaded Server, which provides a listener and a server process. When the MPI listener detects a connection request, it allocates a data pump to handle the connection. One or more data pumps may be available, and each data pump is able to handle a single protocol.

The MPI is controlled using the program intctl. This program is similar to the SQL*Net lsnrctl and Oracle Names namesctl programs, and provides the ability to start, stop, and obtain status information on the MultiProtocol Interchange.