Running Business Processes and Composite Applications 10.5 | Running Business Processes and Composite Applications | Universal Messaging Administration Guide | Using Command Central to Manage Universal Messaging | Configuring Universal Messaging | Ports Configuration | Configuring an NSPS Port
 
Configuring an NSPS Port
* To configure an NSPS port (interface) for a Universal Messaging server instance
1. In Command Central, navigate to Environments > Instances > All > Universal-Messaging-instanceName > Configuration > Ports.
2. Click and select NSPS.
3. Specify values for the following fields:
Connection Basics
Field
Description
Enabled
Enable or disable this NSPS port.
Adapter alias
Provide an alias for the port. Each Universal Messaging server instance can have an associated alias in the form of host:port. This alias is used to tell other servers how to contact this server if this server is behind a NAT or a Proxy Server. This alias is not the same as the Universal Messaging assigned interface alias.
Number
Required. Set port number. The port number must be unique and cannot be used again in a Universal Messaging server instance.
Backlog
Set 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
Automatically start this port when starting 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 this port.
Enable NIO
Enable NIO (Network Input/Output) on this port.
Enable policy server
Allow the ports to respond to policy requests. You can run a policy file server on a socket interface that will automatically handle these requests. Once this is set up, you will also need to set up a client access policy in the clientaccesspolicy.xml file in the /install/server/name/plugins/htdocs directory of the server.
Auth time
Provide the time in milliseconds (ms) that the Universal Messaging server instance waits for the client to complete the authentication process. Default is 10000 milliseconds.
Accept threads
Provide the number of threads processing the accepted sockets.
Select threads
Provide the number of threads allocated for selection.
Send buffer size
Provide the size of the socket send buffer.
Receive buffer size
Provide the size of the socket receive buffer.
Security Configuration
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 only the JKS file type.
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 only the JKS file type.
Truststore server location
Location of the truststore file.
Truststore password
Password required to access the SSL certificate in the truststore file.
4. Optionally, click Test to validate the configuration.
5. Click Save.
Copyright © 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.