Admin Console Tasks for Listeners and JMX Connectors

• To configure security for HTTP listeners

• To configure security for IIOP listeners

• To configure security for the Admin Service’s JMX connector

• To set listener security properties

To configure security for HTTP listeners

Each virtual server in the HTTP service provides network connections through one or more HTTP listeners. With the Admin Console, create new HTTP listeners and edit the security settings of existing HTTP listeners.

1. In the Admin Console tree component, expand the Configurations node.

2. Select the instance to configure:

   • To configure a particular instance, expand the instance’s config node. For example, the default instance, server, expand the server-config node.

   • To configure the default settings for all instances, expand the default-config node.

3. Expand the HTTP Service node.

4. Select the HTTP Listeners node.

5. Select an HTTP listener to edit an existing listener or click New and follow the procedure in To create an HTTP listener to create a new listener.

6. Follow the procedure in To set listener security properties to set security properties.

7. Click Save to save the changes, or click the browser’s Back button to cancel without saving.

Equivalent asadmin command

create-http-listener

To configure security for IIOP listeners

The Application Server supports CORBA (Common Object Request Broker Architecture) objects, which use the Internet Inter-Orb Protocol (IIOP) to communicate across the network. An IIOP listener accepts incoming connections from remote clients of EJB components and from other CORBA-based clients. With the Admin Console, create new IIOP listeners and edit the settings of existing IIOP listeners.

1. In the Admin Console tree component, expand the Configurations node.

2. Select the instance to configure:

   • To configure a particular instance, expand the instance’s config node. For example, the default instance, server, expand the server-config node.

   • To configure the default settings for all instances, expand the default-config node.

3. Expand the ORB node.

4. Select the IIOP Listeners node.

5. Select an IIOP listener to edit that listener or click New and follow the procedure in To create an IIOP listener to create a new listener.

6. Follow the procedure in To set listener security properties to set security properties.

7. Click Save to save the changes, or click Load Defaults to restore the properties to their default values.

   If a new listener was created, it will now be listed in the Current Listeners table on the IIOP Listeners page.

Equivalent asadmin command

create-iiop-listener

To configure security for the Admin Service’s JMX connector

1. In the Admin Console tree component, expand the Configurations node.

2. Select the instance to configure:

   • To configure a particular instance, expand the instance’s config node. For example, the default instance, server, expand the server-config node.

   • To configure the default settings for all instances, expand the default-config node.

3. Expand the Admin Service node.

4. Select the admin service to be modified.

5. Follow the procedure in To set listener security properties to set security properties.

6. Click Save to save the changes, or click Load Defaults to restore the properties to their default values.

To set listener security properties

This procedure applies to HTTP listener, IIOP listener, and JMX Connector security properties.

1. In the Edit HTTP Listener, Edit IIOP Listener, or Edit JMX Connector page, go to the section labeled SSL.

2. Check the Enabled box in the Security field to enable security for this listener. When this option is selected, you must select SSL3 or TLS to specify which type of security is enabled, and you must enter a certificate nickname.

3. Check the Enabled box in the Client Authentication field if clients are to authenticate themselves to the Application Server when using this listener.

4. Enter the keystore alias in the Certificate Nickname field if the Enabled box is checked. The keystore alias is a single value that identifies an existing server key pair and certificate. The certificate nickname for the default keystore is s1as.

   To find the Certificate Nickname, use the certutil utility, as described in Using Network Security Services (NSS) Tools.

5. Select SSL3 and/or TLS if the Enabled box is checked. By default, both SSL3 and TLS are enabled.

6. Enable individual cipher suites, if needed. By default, all supported cipher suites are enabled. Ciphers are discusses in About Ciphers.

7. Select Save to save the changes or Load Defaults to cancel.