Field | Description |
Enabled | Whether to enable or disable the port. |
Adapter alias | An alias for the port. Each Universal Messaging server instance can have an associated alias in the form of host:port. The alias is used to tell other servers how to contact the server if the server is behind a NAT or a Proxy Server. This alias is not the same as the Universal Messaging assigned interface alias. |
Number | Required. A unique port number. |
Backlog | The size of the Internet Protocol (IP) socket queue. |
Bind address | The IP address to which to bind this port, if your machine has multiple IP addresses and you want the port to use this specific address. You cannot change this attribute after you create the port. |
Autostart interface | Whether to automatically start the port when you start the Universal Messaging server instance. |
Advertise interface | Allow the Universal Messaging server instance to send information about this port to the client. |
Allow for inter-realm | Allow port communication between two or more Universal Messaging server instances. For example, allow communication between clusters or joins. |
Allow client connections | Allow clients to connect to the port. |
Enable NIO | Enable NIO (Network Input/Output) on the port. |
Enable policy server | Enable the port to respond to policy requests. You can run a policy file server on a socket interface that will automatically handle these requests. Then you must set up a client access policy in the clientaccesspolicy.xml file in the /install/server/name/plugins/htdocs directory of the server. |
Auth time | The time in milliseconds (ms) that the Universal Messaging server instance waits for the client to complete the authentication process. The default value is 10000. |
Accept threads | The number of threads that process the accepted sockets. |
Select threads | The number of threads allocated for selection. |
Send buffer size | The size of the socket send buffer. |
Receive buffer size | The size of the socket receive buffer. |
Field | Description |
Client authentication | Whether or not Universal Messaging requires client certificates for all requests. Select: None if Universal Messaging does not require client certificates for all requests. REQUIRE_CERTIFICATE if you want Universal Messaging to require client certificates for all requests. |
Keystore type | File type of the keystore file. Universal Messaging supports the JKS and PKCS12 file types. |
Keystore server location | Location of the keystore file. |
Keystore password | Password required to access the SSL certificate in the keystore file. |
Keystore key password | Password required to access a specific private key in the keystore file. |
Truststore type | File type of the truststore file. Universal Messaging supports the JKS and PKCS12 file types. |
Truststore server location | Location of the truststore file. |
Truststore password | Password required to access the SSL certificate in the truststore file. |