Configuration Changes

• Changing Application Server Configuration

• Ports in the Application Server

• To view port numbers

• To change the Administrative Server port

• To change an HTTP port

• To change an IIOP port

• To configure a JMX connector using the Admin Service

• To edit the JMX connector configuration

• Changing the J2SE Software

Changing Application Server Configuration

When making any of these configuration changes, restart the server for the changes to take effect:

• Changing JVM options

• Changing port numbers

• Managing HTTP, IIOP, and JMS services

• Managing thread pools

For instructions, see Restarting the Server or Domain.

With dynamic configuration, most changes take effect while the server is running. To make the following configuration changes, do NOT restart the server:

• Deploying and undeploying applications

• Adding or removing JDBC, JMS, and Connector resources and pools

• Changing logging levels

• Adding file realm users

• Changing monitoring levels

• Enabling and disabling resources and applications

Note that the asadmin reconfig command has been deprecated and is no longer necessary. Configuration changes are applied to the server dynamically.

Ports in the Application Server

The following table describes the port listeners of the Application Server.

Table 1–2 Application Server Listeners that Use Ports

Listener	Default Port Number	Description
Administrative server	4848	A domain’s administrative server is accessed by the Admin Console and the asadmin utility. For the Admin Console, specify the port number in the URL of the browser. When executing an asadmin command remotely, specify the port number with the --port option.
HTTP	8080	The Web server listens for HTTP requests on a port. To access deployed Web applications and services, clients connect to this port.
HTTPS	8181	Web applications configured for secure communications listen on a separate port.
IIOP		Remote clients of enterprise beans (EJB components) access the beans through the IIOP listener.
IIOP, SSL		Another port is used by the IIOP listener configured for secure communications.
IIOP, SSL and mutual authentication		Another port is used by the IIOP listener configured for mutual (client and server) authentication.

To view port numbers

1. In the tree component, select an instance under the Standalone Instances node.

2. Select the Properties tab.

3. On the Instance Specific page, the default port numbers are identified. It is possible to set the configuration to override these values.

To change the Administrative Server port

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

2. Expand the server-config (Admin Config) node.

3. Expand the HTTP Service node.

4. Expand the HTTP Listeners node.

5. Select the admin-listener node.

6. On the Edit HTTP Listener page, change the value of the Listener Port field.

7. Restart the server.

To change an HTTP port

1. In the tree component, expand the HTTP Service node.

2. Expand the HTTP Listeners node.

3. Select the HTTP listener whose port number you want to change.

4. On the Edit HTTP Listener page, change the value of the Listener Port field.

5. Click Save.

6. Restart the server.

To change an IIOP port

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

2. Expand the server-config (Admin Config) node.

3. Expand the ORB node.

4. Expand the IIOP Listeners node.

5. Select the listener whose port number you want to change.

6. On the Edit IIOP Listener page, change the value of the Listener Port field.

7. Click Save.

8. Restart the server.

To configure a JMX connector using the Admin Service

Use the Admin Service to configure a JSR-160 compliant remote JMX connector, which handles communication between the domain administration server and the node agents, which manage server instances on a host machine, for remote server instances.

The Admin Service determines whether the server instance is a regular instance, a domain administration server (DAS), or a combination. A DAS is similar to a J2EE server instance, except that user applications and resources are not deployed to a DAS, though it is capable of serving user application requests. The only significant difference between a DAS and a J2EE Server Instance is that the former can not be a part of a cluster, the homogeneous unit of server instances. In the Platform Edition, there is only one server instance, and it is a combination.

1. Select Configurations from the tree.

2. Select Admin Service from the tree.

3. From the Type drop-down menu, select what you want the Admin service to configure: DAS , DAS and server, or server. Selecting DAS and server is the same as selecting DAS.

4. In the JMX Connector Name field, enter the name of the JMX connector used internally. The name of the connector is system.

To edit the JMX connector configuration

With the Edit JMX Connector screen, you can edit the configuration of the JSR–160 compliant JMX Connector.

1. Select Configurations from the tree.

2. Expand the Admin Service node and click system, which is the JMX connector used internally.

3. Enter the port of the JMX connector server.

   The JMX service URL is a function of the protocol, port, and address, as defined by the JSR–160 1.0 Specification.

4. Enter the protocol that this JMX connector should support.

   The Application Server version 8.2 supports the rmi_jrmp protocol only.

5. In the Realm Name field, enter the name that represents the special administrative realm.

   All authentication is handled by this realm.

6. Select the Enabled checkbox to indicate that transport layer security should be used in the JMX connector.

Changing the J2SE Software

The Application Server relies on the Java 2 Standard Edition (J2SE^TM) software. When the Application Server was installed, the directory for the J2SE software was specified. For instructions on changing the J2SE software, see To configure the JVM general settings.

Using Online Help

The Admin Console’s online help is context-sensitive: When clicking the Help link in the upper right corner, the help browser window displays a topic related to the current Admin Console page. If the current page has no help information, the Using Online Help topic is displayed.

The online help includes conceptual topics that are not context-sensitive. To view one of these topics, select it from the table of contents in the help browser window.

To go back to the previous help screen

1. From within the help browser window, right-click to display a selection menu.

2. Select Back.

Further Information

• Sun Microsystems Worldwide Training - Over 250,000 students each year are trained by Sun and its authorized centers through Web-based courses and at over 250 training sites located in more than 60 countries. For more information, see: http://training.sun.com/.

• The J2EE 1.4 Tutorial - Written for developers, the tutorial has administrative instructions for configuring JMS, setting up JavaMail resources, and managing security. To access the tutorial, go to: http://java.sun.com/j2ee/1.4/docs/tutorial/doc/index.html.

• Application Server Developer’s Guide - This guide contains development information that is specific to the Application Server.

• The asadmin man pages - Available in HTML format, these pages include syntax and examples for all the application server utilities including the asadmin utility commands.

• Application Server Release Notes

• docs.sun.com: Sun Product Documentation - From this site you can search for and access all of our product documentation: http://docs.sun.com/.

• J2EE 1.4 Documentation page - Located on our public Web site, this page has links to the technical documentation for the J2EE 1.4 platform: http://java.sun.com/j2ee/1.4/docs/.

• The Quick Start Guide - This document shows you how to deploy and run a simple Web application. The guide is in the install-dir/docs/QuickStart.html file.