Whether a
MPX Cache Agent operates as a root
MPX Cache Agent or a remote
MPX Cache Agent is determined solely by its configuration. The installation of the
MPX Cache Agent is similar in both cases except for consideration of the computer on which to install it:
- The root
MPX Cache Agent requires access to the vault for the server configuration that it services. Consequently, it is usually installed on the
same computer as the Server. Alternatively, if it can be installed on a network-near computer to prevent the Root
MPX Cache Agent from competing for CPU or network I/O with the corresponding server configuration. However, this requires it to access the
vault files and the
CacheJournal.dat file by way of a shared network drive, so use this option only when a high-speed network is in place .
- Remote
MPX Cache Agents should be installed in each geographic location that can benefit from local data access. One approach is to install a
MPX Cache Agent in each network environment that local users can access over a highspeed LAN. (For example: Install two remote
MPX Cache Agents at headquarters, one each for engineering and QA; install one at each regional office.) Another beneficial use of the
MPX Cache Agent is to install an instance on a computer dedicated to a check-out intensive application such as a build utility. There is
no limit on the number of
MPX Cache Agents that can be installed throughout an enterprise. However, keep in mind that each
MPX Cache Agent requires access to a
Message Broker. For more information about clouds, see “Understanding Clouds” in the appropriate
MPX Administrator’s Guide.
To install a root
MPX Cache Agent or remote
MPX Cache Agent on
Microsoft Windows: