Skip to Main Content
Return to Navigation

Changing Configuration Settings

This section provides an overview of the WebLogic server configuration files, and discusses how to:

Understanding the WebLogic Server Configuration Files

WebLogic server configuration settings are stored in a collection of files, primarily these include: script, config.xml, and the web.xml and weblogic.xml for each webapp.

Configuration File

Description

setEnv script

SetEnv contains statically and dynamically defined environment variables. It's called from all of the WebLogic administration scripts to assist in building the Java command line. You modify this file using a text editor.

config.xml

Config.xml contains server runtime settings, such as the HTTP port. You modify this file using the Administration Console.

web.xml

weblogic.xml

Located in the WEB-INF directory of each servlet, providing web application descriptors and settings relevant to their application.

Changing the WebLogicAdmin Server’s Listen Ports

In the multi-server configuration, several parameters are set based on the environment detected and delivered defaults. One such parameter is the HTTP port of the WebLogicAdmin server. By default the WebLogicAdmin server’s HTTP listen port is 9999.

To change this value:

  1. Start the WebLogicAdmin server using the startWebLogicAdmin script.

  2. Sign on to the WebLogic Server Console by entering the following URL in a browser:

    http://webserver:9999/console

    Where webserver is the hostname of the WebLogic server.

  3. Navigate to Servers, WebLogicAdmin, Configuration, General.

  4. Modify the value of the Listen Port field.

  5. Click Apply.

  6. Restart the WebLogic server.

If you can't initially start the server due to a port conflict, you can manually edit the value of the ListenPort parameter in that domain’s config.xml file. Creating a backup of config.xml is recommended before manually changing this file.

After changing the ListenPort value in your domain’s config.xml, either directly or using the console, you must also update your setEnv script. Update the ADMINSERVER_PORT environment variable to reflect the new HTTP port. This setting is used by the stopWebLogic and startManagedWebLogic scripts as the default administration server HTTP port.

Changing Application and Server Deployment Targets

With WebLogic, J2EE applications are targeted to any combination of WebLogic servers and WebLogic clusters. A WebLogic cluster is a logical grouping of servers, generally all providing the same application, though that's not a requirement. To change the servers or clusters that to which an application is targeted and deployed, sign on to the Administration Console and update the application's target assignments. You can view and modify application and server target assignments on the Deployments, Applications tabs, and on the Targets tab for each server.

Following is an example of how to change the target assignments of the PeopleSoft Integration Gateway (PSIGW) web application so it’s the only application targeted to the PIA server, and is the sole application on that instance.

To change the target assignments of the PeopleSoft Integration Gateway web application:

  1. Sign on to the WebLogic Server Console.

  2. In the Domain Structure section:

    1. Expand peoplesoft.

    2. Expand Deployments.

    3. Expand Applications.

    4. Expand peoplesoft.

  3. Select PSIGW.

  4. Select the Targets tab.

  5. In the Clusters section, clear the peoplesoftCluster check box.

  6. Click Apply.

  7. In the navigation tree, select PORTAL.

  8. Select the Targets tab.

  9. In the Independent Servers grid, clear the check box for targeting the PORTAL to this server.

  10. Click Apply.

  11. Repeat steps 7 to 10 for the PSEMHUB and remaining servlets.

To deploy an application to a cluster, target the server to the cluster and target the application to the cluster.