Figure 18-1 Sample PMDF-XGS site ACME.COM
Figure 18-2 through Figure 18-4 show an example of configuring a
PMDF-XGS gateway at ACME.COM on node roadrnnr, and
Example 18-1 shows a corresponding checklist file. The sample site
ACME.COM, shown in Figure 18-1 , has a PMDF mailhub system,
roadrnnr, as well as an additional PMDF-ACCESS system
beepbeep, and has PC-LAN based cc:Mail users and
WordPerfect Office users connected through PMDF-LAN and considered to
be in the domains ccmail.acme.com and wpo.acme.com, respectively.
ACME.COM also has connections to the Internet over TCP/IP. ACME.COM has
an OS/2 system, with TCP/IP name bridge.acme.com and SNADS name PMDF,
that will act as the transport bridge between the SNADS side and the
PMDF side. ACME.COM's SNADS nodes are BLUE, INDIGO, AZURE, and LAPIS,
which will be knows as blue.acme.com, indigo.acme.com, azure.acme.com,
and lapis.acme.com, respectively, to the non-SNADS (e.g.,
Internet) world.
For this example, PMDF-MTA, PMDF-LAN, and PMDF-XGS have been installed
on roadrnnr. PMDF-MTA and PMDF-LAN have been configured
previously, during a separate configuration session on
roadrnnr. The SNADS nodes have been configured to know
about the PMDF-XGS transport bridge and the roadrnnr
system. The PMDF-XGS transport bridge component has been installed and
configured on the transport bridge system, and is using the default
TCP/IP ports for communicating with the PMDF system
roadrnnr.
Remember that the values entered in this sample are for purposes of example only. Be sure to use the values appropriate for your system when you perform the actual configuration.