D Installing Advanced Management Console in a Clustered Environment — An Example

This section describes an example to install the Advanced Management Console on a Linux platform. You can deploy the Advanced Management Console in a WebLogic cluster environment to improve the performance. Multiple Managed servers running on different hosts,  which are managed by the WebLogic cluster can work together to serve all requests in a round-robin mode.

This appendix contains the following:

In a nut shell, the following is an overview of the steps involved to install the Advanced Management Console in a clustered environment:
  1. Ensure that all machines are available.

  2. Ensure that you can login with shell access and you have root credentials.

  3. Install setup on the first server, for example SRV1.

  4. Install setup on the 2nd server, for example, SRV2.

  5. Install setup on the database server (SRVDB).

  6. Deploy the Advanced Management Console application. You need to have the WebLogic Admin server running on SRV1 to access console and Node managers running on SRV1 and SRV2.

  7. Install the Advanced Management Console agents using SCCM or manual steps.

Installing and Configuring WebLogic Server

You need to install the WebLogic server on each host on which, the target managed server is running. A domain needs to be created on the first host.

To install the Advanced Management Console in a WebLogic cluster, you need at least 4 machines – 2 of which are required for setting up the WebLogic servers and one machine for setting up the database. The load balancer is shared across multiple setups.
To install WebLogic server and create a domain:
  1. See Installing WebLogic Server.

  2. Create and configure a WebLogic server domain.

Configuring Machines and Server (SRV1) on a WebLogic Server Console

To configure the WebLogic server, you need to configure the required machines and servers on the WebLogic server console.

This topic mainly details how to create first machine in the cluster (SRV1). To configure machines and servers on a WebLogic server console:

  1. Edit the nodemanager properties to start the Node manager on DNS name instead of localhost. In this guide, ${MW_HOME} represents the WebLogic Server home directory.

    [deployment@SRV1 nodemanager]$ pwd
    ${MW_HOME}/user_project/domains/base_domain/nodemanager
    [deployment@SRV1 nodemanager]$ vi nodemanager.properties 
    Set ListenAddress=SRV1.yourdomain.com
    
  2. Start the WebLogic console:

    [deployment@SRV1 bin]$ pwd
    ${MW_HOME}/user_projects/domains/base_domain/bin
    [deployment@SRV1 bin]$ nohup ./startWebLogic.sh &
    [1] 7820
    [deployment@SRV1 bin]$
    
  3. Start the Node Manager:

    [deployment@SRV1 bin]$ pwd
    ${MW_HOME}/bin
    [deployment@SRV1 bin]$ nohup ./startNodeManager.sh &
    [2] 7991
    [deployment@SRV1 bin]$
    
  4. Login to the WebLogic console with the WebLogic administration user: http://SRV1.yourdomain.com:7001/console/login/LoginForm.jsp.

  5. Click Environment and click Machines from the left panel.

  6. Click New and enter SRV1 DNS name and select Unix from the drop-down list, and then click Next.

  7. Enter SRV1 DNS name and click Finish.

  8. Similarly, repeat step 6 and 7 to create machine for SRV2.

  9. Navigate to Environment and then click Servers from the left panel.

  10. Click New and enter server details, with the listen address as DNS name and a port number. Make sure to select Yes, create a new cluster...., and then click Next.

  11. Name new cluster, for example, cluster-0 and click Finish.

  12. Click the server name and associate this server with SRV1 and enable SSL and click Save.

  13. Configure server for SRV2 following steps 9 through 12. Make sure to associate this server with existing cluster you created earlier.

  14. Click on servers again and configure a heap size by navigating to Server Start from configuration page.

  15. Click Services and then click JTA from the left panel.

  16. Update the Timeout Seconds and then click Save. See Setting Up WebLogic Server JTA .

Creating Domain Pack

To create a domain pack, in SRV1, update as follows:
[deployment@SRV1 Oracle_Home]$ java -version
java version "1.8.0_121"
Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
[deployment@SRV1 ]$ export PATH=${MW_HOME}/oracle_common/common/bin:$PATH
[deployment@SRV1 ]$ export DOMAIN=${MW_HOME}
[deployment@SRV1 ]$ pack.sh -managed=true -domain=$DOMAIN -template=/tmp/template.jar -template_name="/tmp/template_name"
<< read domain from ${MW_HOME}
  succeed: read domain from ${MW_HOME}
<< set config option Managed to "true"
  succeed: set config option Managed to "true"
<< write template to "/tmp/template.jar"
..............................
 >> succeed: write template to "/tmp/template.jar"
<< close template
  succeed: close template
[deployment@SRV1 base_domain]$

Configuring Second Machine in Cluster (SRV2)

To configure second machine:

  1. To install WebLogic server, see Installing WebLogic Server. Click Cancel when asked to create domain.

  2. Check if the pack was created by using Create Domain Pack.

  3. Copy pack file from SRV1 to SRV2.

    [deployment@SRV2 base_domain]$ scp /tmp/template.jar deployment@SRV2:/tmp/.
    
  4. Unpack the domain by ssh on to SRV2:

    [deployment@SRV2 Oracle_Home]$ java -version
    java version "1.8.0_121"
    Java(TM) SE Runtime Environment (build 1.8.0_121-b13)
    Java HotSpot(TM) 64-Bit Server VM (build 25.121-b13, mixed mode)
    [deployment@SRV2 Oracle_Home]$ export DOMAIN=${MW_HOME}
    [deployment@SRV2 Oracle_Home]$ unpack.sh -domain=$DOMAIN -template=/tmp/template.jar
    << read template from "/tmp/template.jar"
      succeed: read template from "/tmp/template.jar"
    << set config option DomainName to "base_domain"
      succeed: set config option DomainName to "base_domain"
      validateConfig "KeyStorePasswords"
      succeed: validateConfig "KeyStorePasswords"
    << write Domain to ${MW_HOME}
    ..................................................
    << close template
      succeed: close template
    [deployment@SRV2 Oracle_Home]$
    
  5. Start Node Manager on SRV2:

    [deployment@SRV2 bin]$ pwd
    ${MW_HOME}/bin
    [deployment@SRV2 bin]$ nohup ./startNodeManager.sh &
    [1] 10632
    [deployment@SRV2jb bin]$
    

Configuring Load Balancer

A load balancer sits in front of the backend WebLogic servers. Any load balancer can be used. As the load balancer is a transfer station for each packet between the clients and the backend servers, it could be a single point bottleneck. Therefore a hardware load balancer is highly recommended.

Deploying Java Advanced Management Console Application

To deploy the application:

  1. Check if you have completed installation and configuration steps for SRV1 and SRV2.

  2. Check if the WebLogic Server is started on SRV1. If not, then you need to start it.

  3. Login to WebLogic console on SRV1.

  4. Click Deployments from the left panel.

  5. Click Install and Install jax-rs-2.0.war from WebLogic deployment libraries. Click Next and then Next.

  6. In the Deployment targets page, select All servers in the cluster to deploy this library for all servers and then click Next.

  7. Click Next and Finish on next screens to accept defaults.

  8. To deploy the Advanced Management Console application, click Deployments from the left panel.

  9. Click Install and select JavaAMC deployment package. Click Next and then Next.

  10. In the Deployment Targets page, select All servers in the cluster to deploy this library for all servers and click Next.

  11. Click Next and Finish.

  12. Click Deployments from left panel to make sure deployment is done.

Installing and Configuring Oracle Database

Before you begin to install and configure the Oracle database, make sure you can get root authority as the configuration requires root authority.

Configuring Data Source in WebLogic Server

To Configure Data Source in WebLogic server, see Configuring WebLogic Server with Oracle Database.

Note:

The data source needs to be deployed on the cluster instead of the single WebLogic server.