Installing an NFM-P client delegate server
Description
This section describes client delegate server installation in a standalone or redundant NFM-P system. You must comply with the general requirements in NFM-P deployment configuration and the specific requirements in this section before you attempt to deploy a client delegate server.
Platform requirements
Client delegate server deployment is supported on the following platforms:
General
If the NFM-P system uses a firewall, you must ensure that the firewall allows traffic to pass between the remote client stations and the client delegate servers. See the NSP Planning Guide for a list of the ports that must be open on each component.
Note: Adding a client delegate server to an existing NFM-P system requires root and nsp user privileges on each main server station.
Note: Client delegate server deployment requires a supported web browser on the client delegate server station. See the NSP Planning Guide for browser support information.
Microsoft Windows
See the NSP Planning Guide for the supported Microsoft Windows versions for client delegate server deployment.
Note: Client delegate server deployment on Windows requires local Administrator privileges.
RHEL
A RHEL client delegate server station must have:
-
a supported OS release and patch level, as described in the NSP Planning Guide
-
the required RHEL OS configuration and packages, as described in Chapter 3, RHEL OS deployment for the NSP
-
the required Oracle JRE version; see the NSP Planning Guide for information
Optionally, for greater system security, you can remove the world permissions from RHEL compiler executable files; see Resetting GCC-compiler file permissions for information.
Note: A remote station that connects to a RHEL client delegate server requires X.11 or native X display redirection;. X-window emulation software is not supported.
Note: Client delegate server deployment on RHEL requires root user privileges.
Note: The Bash shell is the supported command shell for RHEL CLI operations.