Configure BEA WebLogic servers

After creating a middleware server representation of a BEA WebLogic server, update the configuration settings so that they match the BEA WebLogic installation.

Federate the node running the BEA WebLogic server, and create a representation of the server.

If we installed BEA WebLogic in a location other than the default directory, update the WebSphere variables with the installation directory. To perform operations on the server, configure the server operations for the BEA WebLogic middleware server representation.

  • Intelligent Management support for using BEA WebLogic servers is stabilized. We can use the console or wsadmin scripting to manage these servers.

    1. Update the WebSphere variables so that they match the settings on the node running the BEA WebLogic server.

      • If we use wsadmin scripting to edit the variables, follow the directions in the topic on modifying variables .

      • To edit the variables in the console, click Environment > WebSphere variables.

      Update the following variables:

      WEBLOGIC_ADMINHOST

      Host name of the WebLogic administration server.

      Default value: localhost

      Scope: Cell

      WEBLOGIC_ADMINPORT

      Port of the WebLogic administration server.

      Default value: 7001

      Scope: Cell

      WEBLOGIC_ADMINPROTOCOL

      Protocol to use to connect to the WebLogic administration server.

      Default value:t3

      Scope: Cell

      WEBLOGIC_ADMINURL

      Specifies the URL for the WebLogic administration server. The value is created from other variables.

      Default value: ${WEBLOGIC_ADMINPROTOCOL}://${WEBLOGIC_ADMINHOST}:${WEBLOGIC_ADMINPORT}

      Scope: Cell

      WEBLOGIC_SERVERROOT

      Specifies an alias to the WEBLOGIC_DOMAINDIR variable.

      Default value: ${WEBLOGIC_DOMAIN_DIR}

      Scope: Cell

      WEBLOGIC_SERVERNAME

      Name of the server in the WebLogic administration environment.

      Default value: ${WAS_SERVER_NAME}

      Scope: Server

      BEA_HOME

      Root installation location.

      Default value: C:\bea

      Default value: /opt/bea

      Scope: Cell

      WEBLOGIC_HOME

      Specifies the WebLogic root directory. The root is version-specific, for example {$BEA_HOME}\weblogic91.

      Default value:{$BEA_HOME}\weblogic

      Scope: Cell

      WEBLOGIC_DOMAINNAME

      Name of the WebLogic domain.

      Default value: myDomain

      Scope: Cell

      WEBLOGIC_DOMAINDIR

      Builds the path to the WebLogic domain.

      Default value:${BEA_HOME}\user_projects\domains\${WEBLOGIC_DOMAINNAME}

      Scope: Cell

      If the home directory is different on different nodes in the configuration, create a variable with the same name for specific nodes.

    2. Update the server operations for the BEA WebLogic server to include the user name and password.

      • If we use wsadmin to update server operations, follow the directions in the topic on starting the wsadmin client . The startMiddlewareServer command and the stopMiddlewareServer commands require a user name and password to run.

      • If we use the console, click Servers > Other middleware servers > BEA WebLogic servers > weblogic_server > Server operations. Edit the stop server operation to include the user name and password that you use for this operation.

    3. Optional: Update the HTTP and HTTPS ports for your servers. The default port is 7001. If we use a value other than the default, you must change the port.

      • If we use wsadmin scripting, use the modifyForeignServerProperty command in the middleware server management administrative tasks to change the ports.

      • If we use the console, click Servers > Other middleware servers > BEA WebLogic servers > weblogic_server. Edit HTTP connector or HTTPS connector. Click OK. Save and synchronize your changes.


    What to do next

    • To use this configuration when we are configuring the other BEA WebLogic servers, create a server template of the current BEA WebLogic server.

    • View the log files for the BEA WebLogic server on the computer that hosts it.

    • Edit configuration files for the BEA WebLogic server on the computer that hosts it.

    • After creating representations of all the BEA WebLogic servers, we can add the representations to a dynamic cluster.


    Related concepts

  • Middleware nodes and servers
  • Supported middleware server types


    Related tasks

  • Add, managing, and removing nodes
  • Configure middleware server operations
  • Modify variables
  • Start the wsadmin client
  • Add middleware servers to configurations
  • Create middleware server templates
  • Configure the external log viewing service
  • Create dynamic clusters
  • Intelligent Management: middleware server management administrative tasks

  • addNode command
  • Intelligent Management: middleware server creation administrative tasks