Port aliases-simple example - assure_mimix - 10.0

Assure MIMIX Administrator Reference

Product type
Software
Portfolio
Integrate
Product family
Assure
Product
Assure MIMIX™ Software
Version
10.0
Language
English
Product name
Assure MIMIX
Title
Assure MIMIX Administrator Reference
Copyright
2023
First publish date
1999
ft:lastEdition
2024-05-07
ft:lastPublication
2024-05-07T13:36:02.962500

Before using the MIMIX TCP/IP support, you must first configure the system to recognize the feature. This involves identifying the ports that will be used by MIMIX to communicate with other systems. The port identifiers used depend on the configuration of the MIMIX installations. MIMIX installations vary according to the needs of each enterprise. At a minimum, a MIMIX installation consists of one management system and one network system. A more complex MIMIX installation may consist of one management system and multiple network systems. A large enterprise may even have multiple MIMIX installations that are interconnected.

Figure 5 shows a simple MIMIX installation in which the management system (LONDON) and a network system (HONGKONG) use the TCP communications protocol through the port number 50410. Figure 6 shows a MIMIX installation with two network systems.

Figure 5.Creating Ports. In this example, the MIMIX installation consists of two systems.

Figure 6.Creating Ports. In this example, the MIMIX installation consists of three systems, two of which are network systems.

In both Figure 5 and Figure 6, if you need to use port aliases for port 50410, you need to have a service table entry on each system that equates the port number to the port alias. For example, you might have a service table entry on system LONDON that defines an alias of MXMGT for port number 50410. Similarly, you might have service table entries on systems HONGKONG and CHICAGO that define an alias of MXNET for port 50410. You would use these aliases in the PORT1 and PORT2 parameters in the transfer definition.