Creating a Domain with Servers

A domain can include multiple WebLogic Server clusters and non-clustered WebLogic Server instances. A minimal domain can contain only one WebLogic Server instance, which functions as both an Administration Server and as a Managed server. This domain can be useful while developing applications, but it is not recommended for use in a production environment. Although the scope and purpose of a domain can vary significantly, most WebLogic Server domains contain the components described in this section.

By default, the WebLogic domain created by the P6 EPPM Configuration Wizard creates a domain with an Administration Server (AdminServer) and a Managed Server for each application that you deploy. If you are installing P6 EPPM manually, Oracle recommends you create a managed server for each P6 EPPM application you deploy, similar to the P6 EPPM Configuration Wizard. For example:

To create a domain:

To create a WebLogic Domain:

  1. Run the WebLogic Configuration Wizard.
  2. In the Create Domain window:
    1. Select Create a new WebLogic domain.
    2. In the Domain Location field, enter the location that you want to create the domain.
    3. Click Next.
  3. In the Templates window, select the templates that you want to apply to the domain and click Next.
  4. In the Administrator Account window:
    1. Enter the user name and password information.
    2. Click Next.
  5. In the Domain Mode window:
    1. Select Production Mode.
    2. Select a JDK.
    3. Click Next.
  6. In the Advanced Configuration window:
    1. Select the Administration Server, Managed Servers, and Managed Servers, Clusters and Coherence.
    2. Click Next.
  7. In the Administration Server window:
    1. (Optional) Select Enable SSL and set the SSL listen port if you are enabling Secure Sockets Layer communication.
    2. Click Next.

      See https://docs.oracle.com/middleware/1221/core/ASADM/sslconfig.htm for more details on setting SSL for WebLogic.

  8. In the Node Manager window:
    1. Select a Node Manager Type.
    2. In the Username and Password fields, enter the credentials for the Node Manager.
    3. Click Next.
  9. In the Managed Servers window:
    1. Click Add.
    2. Enter the Name and select the Listen address information.
    3. (Optional) Select the SSL enabled option and set the SSL listen port.
    4. (Optional) Add or delete other managed servers.
    5. Click Next.
  10. In the Clusters window:

    Note: Do not add clusters if you are not using multiple WebLogic server instances for scalability.

    1. (Optional) Click Add.
    2. (Optional) Enter the name of the cluster.
    3. (Optional) Enter the following information: Cluster messaging mode, Multicast address, Multicast port, and Cluster address.
    4. (Optional) Add or delete other configured clusters.
    5. Click Next.

      Note: For information on setting up clusters, use Oracle's WebLogic Server documentation: https://docs.oracle.com/middleware/1221/wls/CLUST/setup.htm.

  11. (Optional) In the Assign Servers to Clusters window, assign a server to a cluster and then click Next.

    Note: Select the Cluster in the right pane, then select the Server in the left pane. Assign the server to the cluster by clicking the right arrow button.

  12. In the Machines window, select Machine (with Windows) and then complete the following:
    1. Click Add.
    2. Enter a machine name.
    3. (Optional) Select the Node manager listen address from the list.

      Note: If you specify an address for a machine that hosts the Administration Server and you need to access the WebLogic Server Node Manager, you must disable the host name verification.

    4. (Optional) Enter the Node manager listen port.
    5. (Optional) Add or delete configured machines.
    6. (Optional) Click Next.
  13. In the Machines window, select Unix Machine (with UNIX) and the complete the following:
    1. Click Add.
    2. Enter a machine name.
    3. (Optional) Select the Post bind GID enabled option to enable a server running on this machine to bind to a UNIX group ID (GID) after it finishes all privileged startup actions.
    4. (Optional) Enter the Post bind GID where a server on this machine will run after it finishes all privileged startup actions. If you do not enter a GID, the server will continue to run under the group where it was started. For this setting to work, you must select the Post bind GID enabled option.
    5. (Optional) Select the Post bind UID enabled option to enable a server running on this machine to bind to a UNIX user ID (UID) after it finishes all privileged startup actions.
    6. (Optional) Enter Post bind UID where a server on this machine will run after it finishes all privileged startup actions. If you do not enter a UID, the server will continue to run under the account where it was started. For this setting to work, you must select the Post bind UID enabled option.
    7. (Optional) Add or delete configured machines.
    8. Click Next.

      Notes:

      • You might want to create machine definitions for the following situations: (1) The Administration Server uses the machine definition (along with the Node Manager application) to start remote servers. (2) WebLogic Server uses configured machine names when determining the server in a cluster that can handle certain tasks, such as HTTP session replication. The WebLogic Server then delegates those tasks to the identified server.
      • You must configure machines for each product installation that runs a Node Manager process. The machine configuration must include values for the listen address and port number parameters.
  14. In the Assign Servers to Machines window:

    Note: A machine is a physical server that will host a WebLogic managed server. Depending on your resource needs and data load, the machines may be in the same physical server where the WebLogic Admin Server is installed or in separate physical servers.

    1. In the Machine list, select the machine where you want to assign a WebLogic Server instance.
    2. Assign the managed and administrative servers that you created to the selected machine.
    3. Review the machine assignments.
    4. Click Next.
  15. In the Configuration Summary window, click Create.

    If given the option, you can click Done now. Otherwise, continue to the next step.

  16. If you are using Windows, in the Creating Domain window:
    1. Select Start Admin Server.
    2. Click Done.
  17. When prompted, enter the administrator user name and password that you entered above.
  18. Repeat this procedure for each new domain.

Last Published Monday, November 4, 2024