When making configuration changes, you may need to restart the server for the changes to take effect. The following sections identify when you will need to restart the server for each configuration change:
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
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
The following table describes the port listeners of the Application Server.
Table 1–1 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. |