ENC Gateway Server Policy Group
The ENC Gateway Server policy group contains the following policies for the ENC Gateway Server. The policy settings are copied to the server configuration file, server.properties, during installation. They get updated when a policy is delivered by the ENC client service or when encUtilCmd is used to refresh server properties.
Note: For detailed information about encUtilCmd, see the encUtilCmd Command Reference.
You can modify policy parameter values by double-clicking a policy to display the Setting Properties dialog.
Specifies the IP address or fully qualified domain name (FQDN) of the parent gateway server.
For an ENC Gateway Manager, this parameter is empty. A manager does not register with anything.
For ENC Gateway Servers, this is the address of the ENC Gateway Manager. A server registers with a manager to make itself and all of the ENC Clients that register with it known to the ENC infrastructure.
For an ENC Gateway Router, this is the address of an ENC Gateway Server. A router registers with a server to make itself known to ENC and available for connections.
If this parameter is left blank for a server or router, that server or router will be unable to register and will be invisible to the ENC infrastructure. Any clients registered with the server will also be invisible.
Default: empty, <locally managed>
Specifies the maximum time period in seconds allowed for virtual client connections, or end point connections—client to router to client. This value is used by the router to ensure that both ends of the connection respond to the server within this timeout period and that they are ready for data transfer. If for some reason one peer is late to respond, then the other peer would be informed about this timeout and virtual connection would be destroyed in the router server.
Default: 90, <locally managed>
Indicates whether the ENC Gateway Server has taken on the role of manager. There is only one manager in an ENC network, and all gateway servers register with it. The ENC Gateway Manager knows about all clients and routers. A client tells this server that it wants to make a connection to another client. The ENC Gateway Manager determines which ENC Gateway Router to use and tells each client to connect to it. This server is visible to all clients and routers. Note that there can be only one manager.
Default: False, <locally managed>
Indicates whether non-blocking socket support or blocking socket support is enabled. If True, non-blocking socket support is enabled, providing maximum scalability but support only for IPv4. If False, blocking socket support is enabled instead, providing less scalability but providing support for IPv6 as well. Note that a restriction in the Java Development Kit (JDK) 1.5 means that IPv6 support does not work on a machine which does not have IPv4 installed as well. This will be fixed in a future release of JDK.
Default: True, <locally managed>
Indicates whether the ENC Gateway Server has taken on the role of a router. The ENC Gateway Router connects two clients and provides a virtual connection between two applications. Clients that want to connect to each other connect to a router, which then relays data between the two thus making a virtual connection.
Default: False, <locally managed>
Indicates whether the ENC Gateway Server has taken on the role of a registration server. The server accepts registrations from clients and reports them to the ENC Gateway Manager. This server is visible to all clients. The server's purpose is to concentrate a large number of connections from clients into one connection to the manager and thus provide scalability to large numbers of computers.
Default: False, <locally managed>
If True, enables TCP_NODELAY and disables Nagle's algorithm. Typically, this value is changed only for troubleshooting purposes.
Default: True, <locally managed>
Specifies the port number used by the ENC Gateway Server to listen for HTTP connections from clients. Note that an ENC Gateway never connects to another ENC Gateway using HTTP.
Default: 80, <locally managed>
Specifies the maximum time in seconds allowed for each ENC Client to return their pinged results. When one ENC Client wants to connect to another, each client is asked to ping the list of available routers and return the results to the ENC Gateway Manager.
Default: 60, <locally managed>
Specifies the TCP port number used by an ENC Gateway to listen for client connections.
Default: 443, <locally managed>
Specifies the TCP port used to connect with other ENC Gateway Servers.
Default: 443, <locally managed>
|
Copyright © 2014 CA Technologies.
All rights reserved.
|
|
