|slave>
A configuration server can run in a cluster which can handle fail-over. A cluster conmprises of a master server and a set of slave servers.
The master configuration server, which normally is the same machine which is host for the management GUI console, propagates changes in the configuration to all connected slave configuration servers. Similarly all slave configuration servers will propagate their changes on to the master configuration server.
If a change is made in the master configuration server, this will be propagated to the connected slave servers. Each slave configuration server works locally as a standalone configurations server with its own configurations file. A slave configuration server can just like a master, operate alone and be host for all PortalProtect servers in the system.
If a change is made in a slave configuration server, this will propagate the change to the master server who will propagate the change out to the other slave servers. The slave configuration server will receive an event about the change. The single configuration server can react on these events, for example, if it already knows the event the configurations server will ignore this.
There will normally be just one master server in an installation and there can be 0 or more slave configurations.
Example: <master> In this example the server will be the master server.
<slave> In this example the server will be the slave server. |
cluster.server.master | <host:port> or <protocol:host:port> where protocol is tcp, nio, nios or local
This property defines the connection to the master configurations server. This property must correspond to the master configurations servers host name and server.port.
This property has no effect if the configuration server is defined as <master>.
Example: cluster.server.master=configserver1:21233 - In this example the configurations server will connect to the master configurations server on port 21233. cluster.server.master=nio://configserver1:21233 – Same as above, but connects using NIO sockets which are nonblocking IO using fewer server threads. cluster.server.master=local://21233 - Same as above, but does not use tcp/ip and instead local JVM connections – the master then has to exist in the same JVM and be loaded by the same classloader. |
peer.server.address | <ip address> - DEPRECATED – use statistics.server.listenurls instead
This IP address is the network interface which the program must listen for connections from the statistics server on. This parameter is interesting in configurations where the server has more than one network interfaces.
The IP address 0.0.0.0 implies that the server must listen for all interfaces.
Example: 0.0.0.0 Here the server will listen on all available network interfaces. Security for attacks from the outside is low when when all network interfaces are being listened to.
Example: 10.23.13.110. Here the server will listen for the specified interface. It will therefore not be possible to access the server from other network interfaces. Security for attacks from the outside with this configuration will be higher.
Example: 127.0.0.1 Here the server will listen on the loopback interface. No external machines can connect to the server. Security for attacks from the outside with this configuration is high. |
peer.server.port | <port> - - DEPRECATED – use statistics.server.listenurls instead
This property specifies the port which among others the statistics server connects on. At this point in time it is only the statistics server which uses this connection. The statistics server must XXXestableXXX be configured to connect to this port.
Example: 21111 In this example the configurations server listens on port 21111. |
statistics.server.listenurls | <List of URLs>
List of URLs to listen for connections from statistics servers from – The URLs have the following format:
local://port – Local queue-based connection, requires 1 thread per connection, only works in the same JVM, but much faster than using sockets. tcp://[hostname:]port – TCP/IP blocking sockets – requires 2 java threads per connection. nio://[hostname:]port – TCP/IP nonblocking (java nio) sockets – does not require any extra threads. nios://[hostname]:port[?params] – Like NIO, but with SSL encryption
For nios connections, the following parameters can be specified; keystore – Filename of keystore – default is /ptskeystore keystorepassword - Password for keystore keystoretype – Type of keystore, default is JKS enabledciphersuites – List of enabled cipher suites, if not specified, the Java default ones are used.
Examples: statistics.server.listenurls=tcp://21111 – Listens on port 21111, using TCP blocking sockets statistics.server.listenurls=nio://10.0.0.1:21111;local://21111 – Listen on the specified IP address and port, using nonblocking sockets, and also listens for local connections from other servers in the same JVM on port 21111. |
server.address | <IP or hostname> - DEPRECATED – use server.listenurls instead.
The IP address is the network interface which the program must listen on. Interesting for configurations where the server has many network interfaces.
IP address 0.0.0.0 implies that the server listens for all network interfaces.
Example 0.0.0.0 Here the server will listen on all available network interfaces. Security for attacks from the outside is low when when all network interfaces are being listened to.
Example: 10.23.13.110. Here the server will listen for the specified interface. It will therefore not be possible to access the server from other network interfaces. Security for attacks from the outside with this configuration will be higher.
Example: 127.0.0.1
Here the server will listen on the loopback interface. No external machines can connect to the server. Security for attacks from the outside with this configuration is high. |
server.port | <port> - DEPRECATED – use server.listenurls instead.
This property contains the port which the configurations server listens on. This corresponds to the port in config.servers or in ptserver.properties which the PortalProtect agent uses.
Example: 21233 |
server.listenurls | <URL list> - defaults to tcp://{server.port} where {server.port} is the value of the server.port property.
List of URLs to listen for connections from configuration clients – The URLs have the following format:
tcp://[hostname:]port – TCP/IP blocking sockets – requires 2 java threads per connection. nio://[hostname:]port – TCP/IP nonblocking (java nio) sockets – does not require any extra threads. local://port – Local queue-based connection, requires 1 thread per connection, only works in the same JVM, but much faster than using sockets. nios://[hostname]:port[?params] – Like NIO, but with SSL encryption
For nios connections, the following parameters can be specified; keystore – Filename of keystore – default is /ptskeystore keystorepassword - Password for keystore keystoretype – Type of keystore, default is JKS enabledciphersuites – List of enabled cipher suites, if not specified, the Java default ones are used.
Note that this list of URLs replaces the older server.port and server.address properties – this provides a more flexible way to support multiple communication protocols, and listen on multiple interfaces simultaneously. If this property is not specified, it will default to tcp:// protocol and the port number from the server.port setting to remain backward compatible.
Examples: server.listenurls=tcp://21233 – Listens on port 21233, using TCP blocking sockets server.listenurls=nio://10.0.0.1:21233;local://21233 – Listen on the specified IP address and port, using nonblocking sockets, and also listens for local connections from components in the same JVM on port 21233. |
statistics.server | <name of statistics server>
This property gives the name of the statistic server. This is used by the configuration server to collect information from the statistic server and show the information in the PortalProtect management GUI.
The name must correspond to the name in the statistic server physical name in the configuration.
Example: statisticsserver1 |
telnetd | <enable |