Indicate whether to enable (Yes) or disable (No) this HTTP listener.

The number you want to use for the port. Select a number that is not already in use on this host machine.

An alias for the port that is unique for this Integration Server. An alias must be between 1 and 255 characters in length and include one or more of the following: letters (a -z, A-Z), numbers (0-9), underscore (_), period (.), and hyphen (-).

A description of the port.

The package associated with this port. When you enable the package, the server enables the port. When you disable the package, the server disables the port.

If you replicate this package, the Integration Server creates a port with this number and the same settings on the target server. If a port with this number already exists on the target server, its settings remain intact. This feature is useful if you create an application that expects input on a specific port. The application will continue to work after it is replicated to another server.

IP address to which to bind this port. Specify a bind address if your machine has multiple IP addresses and you want the port to use this specific address. If you do not specify a bind address, the server picks one for you.

The number of requests that can remain in the queue for an enabled port before Integration Server begins rejecting requests. The default is 200. The maximum value is 65535.

When to close the connection if the server has not received a request from the client within this timeout value (in milliseconds); or when to close the connection if the client has explicitly placed a close request with the server.

Whether the listener will use this pool exclusively for dispatching requests. The existing Integration Server thread pool is a global thread pool. If there is a very high load on this resource, the user may have to wait for the global thread pool to process his request. However, with the private thread pool option enabled, requests coming into this port will not have to compete with other server functions for threads.

To set up a private thread pool for requests coming to this port, click Enable. You can change or accept the default settings given below:

Threadpool Min refers to the minimum number of threads for this private threadpool. The default is 1.

Threadpool Max refers to the maximum number of threads for this private thread pool. The default is 5.

Threadpool Priority refers to the Java thread priority. The default is 5.

If you do not need to use the Threadpool feature, click Disable.

When you view the port’s details, the server reports the total number of private threadpool threads currently in use for the port.

The type of client authentication you want Integration Server to perform for requests that arrive on this HTTP port. Select one of the following:

Integration Server prompts the client for a user ID and password.

Integration Server uses password digest to authenticate all requests. If the client does not provide the authentication information, Integration Server returns an HTTP WWW-Authenticate header with digest scheme to the client requesting for authentication information. If the client provides the required authentication information, Integration Server verifies and validates the request.

A port that is configured to use password digest for authentication of client requests will process a request from a user only if the user is configured to allow password digest for authentication. For more information about configuring a user for digest authentication, see Adding User Accounts.

Integration Server looks for a Kerberos ticket in the HTTP Authorization header using the Negotiate authentication scheme. If it does not find the ticket, Integration Server uses user name and password for basic authentication. If the client does not provide any authentication information, Integration Server returns an HTTP WWW-Authenticate header with negotiate scheme to the client requesting for authentication information. If the client provides the required authentication information, Integration Server verifies and validates the request.

Integration Server looks for a Kerberos ticket in the HTTP Authorization header using the Negotiate authentication scheme. If it does not find the ticket, Integration Server fails the authentication. If the client does not provide any authentication information, Integration Server returns an HTTP WWW-Authenticate header with negotiate scheme to the client requesting for authentication information. If the client provides the required authentication information, Integration Server verifies and validates the request.

Kerberos properties are used to enable Kerberos authentication by providing Kerberos-related details that will be used for handling service requests that come with a Kerberos ticket. For information on configuring Kerberos authentication, see Kerberos Authentication.

Specify the custom JAAS context used for Kerberos authentication.

In the following example, JAAS Context is KerberosClient:

The is_jaas.cnf file distributed with Integration Server includes a JAAS context named IS_KERBEROS_INBOUND that can be used with inbound requests.

Specify the name of the principal to use for Kerberos authentication.

Specify the password for the principal that is used to authenticate the principal to the KDC. Specify the principal password if you do not want to use the keytab file that contains the principals and their passwords for authorization. The passwords may be encrypted using different encryption algorithms.

If the JAAS login context contains useKeyTab=false, you must specify the principal password.

Re-enter the principal password.

Displays username, which indicates that the principal name of the service is represented as a named user defined in the LDAP or central user directory used for authentication to the KDC.

Specify the name of the principal used with the service that the Kerberos client wants to access. Specify the Service Principal Name in the following format: