Skip Headers
Oracle® Communications Network Integrity Installation Guide
Release 7.2.2

Part Number E36031-01
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

4 Installing and Configuring Oracle WebLogic Server

Network Integrity is installed and run on an instance of the WebLogic Administration Server. This chapter describes procedures relating to installing the WebLogic Administration Server and other required applications, and also configuring the WebLogic Server domain where you install Network Integrity.

Note:

Ensure that the Administration Server is running in the WebLogic Server domain before you install Network Integrity.

Installation and configuration tasks include:

About Java Requirements

WebLogic Server is a Java application and needs a Java environment in which to run. You can use any of the popular, available Java environments for your WebLogic server.

When WebLogic server is installed on IBM AIX, Oracle recommends installing IBM Java.

When WebLogic Server is installed on Linux or Solaris, Oracle recommends installing JDK.

Installing IBM Java

Download the Java SDK from the IBM Web site.

For information on installing IBM Java, refer to IBM Java Installation documentation.

Installing JDK

Use a 64-bit Java Development Kit (JDK) on a 64-bit OS for a successful Network Integrity installation.

Download JDK for the required platform from the Oracle Technology Network Web site:

http://www.oracle.com/technology

For information on installing JDK, see the JDK installation documentation.

Downloading and Installing WebLogic Server

Oracle WebLogic Server is available as a component of the Oracle Fusion Middleware 11g media pack.

Download Oracle WebLogic Server from the Network Integrity media pack on the Oracle software delivery Web site:

https://edelivery.oracle.com/

For information about installing Oracle WebLogic Server, see the Oracle WebLogic documentation.

Installing Patches

After you install Oracle WebLogic Server, you must install any applicable patches. The patches must be downloaded from the My Oracle Support web site and can be applied using the WebLogic Smart Update tool.

Note:

The first time you use the update tool, you will be prompted to perform an upgrade. Accept this upgrade, as the tool shipped with the WebLogic Server is outdated.

Download the following patch(es), from the My Oracle Support web site:

https://support.oracle.com

14331527

15842881

For information about downloading and applying patches, see Knowledge Article 1302053.1 - Master Note: How to Locate and Download Patches for WebLogic Server Using My Oracle Support and Knowledge Article 1075833.1 - Master Note on WebLogic Server (WLS) Patches, Upgrade Installers, and Full Installers.

Installing Application Development Runtime 11g

Download Oracle Application Development Runtime 11g from the Network Integrity media pack on the Oracle software delivery Web site:

https://edelivery.oracle.com/

For installing Oracle Application Development Runtime 11g, see the Oracle WebLogic documentation.

Note:

The Oracle Fusion Middleware 11g Application Developer Installer installs both Oracle Application Development Runtime and Oracle Enterprise Manager.

Install Application Developer with the same credentials used to install WebLogic Server.

For more information on the Application Development Framework, see Oracle Fusion Middleware Fusion Developer's Guide for Oracle Application Development Framework.

Installing Oracle Enterprise Scheduling Service

To install Oracle Enterprise Scheduling Service (ESS) using the Installer, perform the following:

  1. Create a temporary directory (dir).

  2. Download the Network Integrity software for your operating system from the Oracle software delivery Web site:

    https://edelivery.oracle.com

    and save it to dir:

  3. Extract the contents of the software pack to dir.

    The extracted software pack has the following structure: integrity/Disk1/install/

  4. Run the Oracle Universal Installer using the following command:

    /dir/integrity/Disk1/install/runInstaller -jreloc jdk_Path/jre_Path
    

    Where jdk_Path/jre_Path is the JDK or JRE location.

  5. Click Next.

    The Select a Product to Install screen appears.

  6. Select the Oracle Enterprise Scheduling Service option, and click Next.

    The Specify Home Details screen appears.

  7. In the Specify Home Details screen, do the following:

    1. In the Name field, enter a name to identify your installation as an Oracle Product in OUI.

    2. In the Path field, enter MW_Home/oracle_ess for the path to the folder where you want to install ESS.

    3. Click Next.

      The Summary Screen appears.

    4. Review the details and click Install.

      The ESS product is installed.

    5. Click Exit to close the installer.

Creating/Extending a WebLogic Server Domain for a Standalone Installation

Before creating a WebLogic Server domain, you must have finished installing Oracle Application Development Runtime. See "Installing Application Development Runtime 11g" for more information.

Note:

Extending the WebLogic Server domain occurs when upgrading Network Integrity from the 7.1.0.x release to the 7.2.2 release.

To create a standalone WebLogic Server domain:

  1. Go to the following path:

    WL_Home/common/bin
    
  2. Enter the following command:

    ./config.sh
    

    The Welcome screen of the Fusion Middleware Configuration Wizard appears.

  3. Select the Create a New WebLogic domain option and click Next.

    The Select Domain Source screen appears.

  4. Select the Generate a domain configured automatically to support the following products: option and from the provided list, select the following products:

    • Oracle Enterprise Manager - 11.1.1.0 [oracle_common]

    • Oracle Enterprise Scheduling Service Basic - 11.1.1.0 [oracle_common]

    • Oracle WSM Policy Manager - 11.1.1.0 [oracle_common]

    • Oracle JRF - 11.1.1.0 [oracle_common]

  5. Click Next.

    The Specify Domain Name and Location screen appears.

  6. In the Domain name field, enter a domain name.

  7. In the Domain location field, enter the path and directory for the domain files. For example, enter the value:

    MW_Home/user_projects/domains/base_domains
    
  8. In the Application location field, enter the path and directory for the application files. For example, enter the value:

    MW_Home/user_projects/applications/application_name
    
  9. Click Next.

    The Configure Administrator User Name and Password screen appears.

  10. In the User name field, enter the administrator user name.

  11. In the User password field, enter the administrator user password. The password must be a minimum of 8 alphanumeric characters, and must contain at least one number or special character.

    In the Confirm password field, reenter your password.

  12. (Optional) In the Description field, enter information about the administrator. For example: This user is the default administrator (or whatever text fits your business practices).

  13. In the WebLogic Domain Startup Mode section, select the Production Mode option.

    In the Available JDKs section, select the required JDK. Oracle recommends the Sun JDK.

  14. Click Other JDK to browse to the location of another JDK. Ensure that this JDK is supported. See "Network Integrity System Requirements" for details.

  15. Click Next.

    The Configure JDBC Component Schema screen appears.

  16. Configure the ESS schema, MDS schema, and OWSM MDS schema components, by performing the following:

    1. In the Vendor field, select the vendor name for the component schema.

    2. In the DBMS/Service field, enter the driver used by the component schema.

    3. In the Driver field, select the driver used by the component schema.

    4. In the Host Name field, enter the host name/ip address for the component schema.

    5. In the Port field, enter the port number used by the schema component.

    6. In the Schema Owner field, enter the owner name for the schema component.

      Note:

      The Schema Owner name format is: prefix_ESS for ESS schema or prefix_MDS for MDS and OWSM MDS schema.
    7. In the Schema Password field, enter the password for the schema component.

      Note:

      If you are installing on a RAC DB, select the Convert to RAC multidata source option.
    8. Click Next.

      The Configuration Wizard will validate all the connections. Verify that all the JDBC component connections pass the validation test.

  17. Click Next.

    The Select Optional Configuration screen appears.

  18. Select the services to install in the WebLogic Server domain:

    • Administration Server

    • Managed Servers, Clusters and Machines

    • Deployments and Services

    Note:

    Oracle recommends that production environments for Network Integrity use a minimum of an Administration Server and one or more Managed Servers or Clusters. Lab environments can be installed on an Administration Server only, if desired.

    If you select only Administration Server, the Domain Creation wizard does not display some dialog boxes pertaining to managed servers or clusters.

  19. Click Next.

    The Configure the Administration Server screen appears.

  20. Do the following:

    1. In the Name field, enter the Administration Server name.

      This single server serves as the Network Integrity domain Administration Server.

    2. In the Listen Address field, select a DNS or an IP address.

      Note:

      Use listener addresses that are equal to a resolvable DNS host or IP address. Do not use localhost or 127.0.0.1. Those addresses interfere with clustered servers.
    3. In the Listen Port field, accept the default.

    4. In the SSL Listen Port field, enter a port that is not used by another domain.

    5. Select SSL enabled if you are enabling SSL.

      It is not a requirement to either enable or disable SSL.

    6. Click Next.

      The Configure Managed Servers screen appears.

  21. Do the following:

    Note:

    A managed server, called ess_server1, will automatically be added.
    1. In the Name field, change the name for the managed server, if required.

    2. In the Listen address field, enter the host, or IP address of the system where the managed server is running.

      Note:

      Use listener addresses that are equal to a resolvable DNS host or IP address. Do not use localhost or 127.0.0.1. Those addresses interfere with clustered servers.
    3. In the Listen port field, enter the number of the port where the managed server listens for incoming messages. 8061

    4. In the SSL listen port field, enter the appropriate value only if SSL is selected.

    5. Select SSL enabled as required.

    6. (Optional) Create further managed servers as required on your Network Integrity deployment.

    7. Click Next

      The Configure Clusters screen appears.

  22. Click Next, as you are performing a standalone installation, that is, you are not using clustering in this installation.

    The Configure Machines screen appears

    Use this screen to change the configuration information for systems. A computer is the logical expression of the system that hosts one or more WebLogic Server instances. The Administration Server and the Node Manager application use the system definition to start remote servers.

  23. Add the systems by doing one of the following:

    • Select the Machine tab, and do the following:

      1. Click Add to create the first system.

      2. In the Name field, enter a name for the system.

      3. In the Node manager listen address field, enter the host or IP address of the node manager.

      4. In the Node manager listen port, enter the port number for the node manager.

      5. Create further systems as required on your Network Integrity deployment.

      6. Click Next.

        The Assign Servers to Machines screen appears.

    • Select the UNIX Machine tab, and do the following:

      1. Click Add to create the first UNIX system.

      2. If required, select Post bind GID enabled. The default state is unselected.

      3. In the Post bind GID field, enter a value or select the default.

      4. In the Post bind UID field, enter a value or select the default.

      5. In the Node manager listen address field, enter the host or IP address of the node manager.

      6. In the Node manager listen port field, enter the port number of the node manager.

      7. (Optional) Create further systems or UNIX systems as required on your Network Integrity deployment.

      8. Click Next.

        The Target Deployments to Cluster or Servers screen appears.

  24. Click Next.

    The Target Services to Clusters or Servers screen appears.

  25. Click Next.

    The Configuration Summary screen appears.

  26. Review the summary to verify the contents of your domain.

    Click Previous to return to prior screens to modify their content.

  27. Click Create to create the domain.

  28. To finish the domain creation process, click Done, after the domain is created successfully.

  29. To set memory requirements, see "Setting Memory Requirements for Network Integrity".

  30. Continue with the procedures in "Starting the WebLogic Server".

For more information on Oracle WebLogic Server Domains, see Oracle Fusion Middleware Installation Guide for Oracle Enterprise Content Management.

Setting Memory Requirements for Network Integrity

You must set appropriate memory requirement values in the WebLogic server to be able to install multiple cartridges after Network Integrity installation. Not allotting enough memory space for the WebLogic domain can cause errors during cartridge deployment.

The example shows the entries in the setDomainEnv.sh file for setting the memory requirement values for Network Integrity:

  1. In the WebLogic domain bin folder, open the setDomainEnv.sh file.

  2. Set the memory arguments for your JVM as follows:

    WLS_MEM_ARGS_64BIT="-Xms20g -Xmx20g"
    
  3. Set Perm size as:

    MEM_PERM_SIZE_64BIT="-XX:PermSize=1024m"
    MEM_MAX_PERM_SIZE_64BIT="-XX:MaxPermSize=1024m"
    

Note:

Although these values can be adjusted based on system memory availability, when using high-end systems, the above configuration is recommended for running Network Integrity.

Creating a WebLogic Server Domain for a Server Cluster Installation

A server cluster arrangement is used for load balancing, scalability, and failover. A clustered server installation (also called an Administration Server with cluster-managed servers installation) is one in which one or more WebLogic server instances are managed by a separate Administration Server. In this arrangement, clustering the Managed Servers in WebLogic allows the servers to work as one unit, rather than as several independent processing units. This is the configuration Oracle recommends because it provides protection if a server fails.

When working with a cluster, install the Cartridge Management Web Services (CMWS) and Network Integrity adapters on the system where the Administration server is running.

Caution:

Ensure that you run the Network Integrity Installer from the Administration server.

Installation Scenario

This installation scenario includes two clustered Managed Servers (networkintegrity01 and networkintegrity02) that are separate from the Administration Server, an Administration server, and a hardware load balancer, used for load balancing. Managed Servers are instances of WebLogic used to host enterprise applications, in this case, Network Integrity.

Note:

For more information on configuring the load balancer, see Network Integrity System Administrator's Guide.

This example uses a shared disk storage environment.

The advantages of using shared disk storage are: easier Network Integrity installation, maintenance, and cartridge deployment.

Using shared disk storage allows the Administration Server and all of the managed servers in the cluster to use the same instance of WebLogic. The systems on which the servers reside must have access to the shared storage.

Network Integrity does not support session replication; however, Network Integrity does support server failover.

Server Cluster Example

Refer to the values in Table 4-1 and Table 4-2 to set up the cluster arrangement.

Table 4-1 Server Cluster Example Values

Value Example

Domain_Home

WL_Home/user_projects/domains/networkintegritycluster

Domain login

weblogic

Domain password

networkintegritycluster

Cluster DNS

NetworkIntegrityClusterDNS

(It includes the networkintegrity01 and networkintegrity02 listening IP addresses.)


Table 4-2 Servers in a Sample Cluster

Value Administration Server Cluster-managed Server #1 Cluster-managed Server #2

WebLogic server

networkintegrityAdmin

networkintegrity01

networkintegrity02

Listening port

IP_Address:8063

IP_Address:8065

IP_Address:8066

Machine

NETINT1

NETINT2

NETINT3


Figure 4-1 shows the servers in a sample server cluster.

Figure 4-1 Servers in a Sample Cluster

An example of a cluster of servers.

Network Integrity Server Cluster Prerequisites

The prerequisites for setting up a Network Integrity server cluster are:

  • Oracle WebLogic administration experience.

  • A hardware load balancer is required. Refer to the server load balancer configuration for details.

  • A DNS entry containing all of the cluster-managed servers' listening addresses serves as the Network Integrity cluster address.

  • A system that hosts multiple cluster-managed servers must be multi-homed.

  • All cluster-managed servers must reside in the same subnet for multicast traffic. See below.

  • Multicast is used for the following:

    • WebLogic cluster heart beats and JNDI updates

  • Ensure that multicasts do not collide in the same domain and other domains.

Overview of Steps for Setting Up Network Integrity on a Server Cluster

Note:

The figures shown in this section are for reference only. The actual server names that you use may be different from those shown in the figures.

For the considered scenario, installing Network Integrity on an Oracle WebLogic Server cluster arrangement involves:

  • Installing Oracle WebLogic Server 11g and Network Integrity software on the shared disk storage.

  • Deleting all JMS resources.

  • Creating server instances for each WebLogic server in your system, and creating your cluster.

  • Deploying the Network Integrity data source and the Network Integrity transaction data source on the cluster.

  • Modifying the startup script on the shared disk storage.

  • Manually modifying the config.xml file.

  • Starting up the Administration Server and all cluster-managed servers.

  • Logging in to Network Integrity through the server load balancer.

Installing WebLogic Server and Network Integrity in a Clustered Environment

Before creating a WebLogic Server domain, you must have finished installing Oracle Application Development Runtime. See "Installing Application Development Runtime 11g" for more information.

Install WebLogic on the shared disk storage.

After you install WebLogic:

  • Create a domain

  • Start the WebLogic server

  • Install Network Integrity

Creating a Domain

To create a domain:

  1. Go to MW_Home/weblogic10.3/common/bin and run the WebLogic domain configuration script:

    ./config.sh
    

    The Welcome screen appears.

  2. Select Create a new WebLogic domain and click Next.

    The Select Domain Source screen appears.

  3. Select the Generate a domain configured automatically to support the following products: option and from the provided list, select the following products:

    • Oracle Enterprise Manager - 11.1.1.0 [oracle_common]

    • Oracle Enterprise Scheduling Service Basic - 11.1.1.0 [oracle_common]

    • Oracle WSM Policy Manager - 11.1.1.0 [oracle_common]

    • Oracle JRF - 11.1.1.0 [oracle_common]

  4. Do the following:

    1. In the Domain name field, enter an appropriate domain name for your requirements or standards.

    2. In the Domain location field, enter the path and directory for the domain files. For example:

      MW_Home/user_projects/domains/base_domains
      
    3. In the Application location field, enter the path and directory for the application files. For example, enter the value:

      MW_Home/user_projects/applications/application_name
      
    4. Click Next.

      The Configure Administrator User Name and Password screen appears.

  5. Do the following:

    1. In the User name field, enter the administrator user name.

    2. In the User password field, enter the administrator user password. The password must be a minimum of 8 alphanumeric characters, and must contain at least one number or special character.

    3. In the Confirm password field, reenter your password.

    4. (Optional) In the Description field, enter information about the administrator.

      For example: This user is the default administrator.

    5. Click Next.

      The Configure Server Start Mode and JDK screen appears.

  6. In the WebLogic Domain Startup Mode section, select one of the following:

    • Development Mode, or

    • Production Mode

  7. In the Available JDKs section, select the required JDK. Oracle recommends the Sun JDK.

  8. Click Other JDK to browse to the location of another JDK and click Next.

    Note:

    Ensure that this JDK is supported. See "Network Integrity System Requirements" for more information.

    The Configure JDBC Component Schema screen appears.

  9. Configure the ESS schema, MDS schema, and OWSM MDS schema components, by performing the following:

    1. In the Vendor field, select the vendor name for the component schema.

    2. In the DBMS/Service field, enter the driver used by the component schema.

    3. In the Driver field, select the driver used by the component schema.

    4. In the Host Name field, enter the host name/ip address for the component schema.

    5. In the Port field, enter the port number used by the schema component.

    6. In the Schema Owner field, enter the owner name for the schema component.

      Note:

      The Schema Owner name format is: prefix_ESS for ESS schema or prefix_MDS for MDS and OWSM MDS schema.
    7. In the Schema Password field, enter the password for the schema component.

      Note:

      If you are installing on a RAC DB, select the Convert to RAC multidata source option.
    8. Click Next.

      The Configuration Wizard will validate all the connections. Verify that all the JDBC component connections pass the validation test.

  10. Click Next.

    The Select Optional Configuration screen appears.

  11. Select the following:

    • Administration Server

    • Managed Servers, Clusters and Machines

    • Deployments and Services

  12. Click Next.

    The Configure the Administration Server screen appears.

  13. Do the following:

    1. In the Name field, enter your Administration Server name.

    2. In the Listen Address field, select a DNS or an IP address.

      Note:

      Use listener addresses that are equal to a resolvable DNS host or IP address. Do not use localhost or 127.0.0.1. Those addresses interfere with clustered servers.
    3. In the Listen Port field, accept the default.

    4. In the SSL Listen Port field, enter a port that is not used by another domain.

    5. Select SSL enabled if you are enabling SSL .

      It is not a requirement to either enable or disable SSL.

    6. Click Next.

      The Configure Managed Servers screen appears.

  14. Do the following:

    Note:

    A managed server, called ess_server1, will automatically be added to the list.
    1. In the Name field, enter a name for the managed server, if required.

    2. In the Listen address field, enter the host, or IP address of the system where the managed server is running.

      Note:

      Use listener addresses that are equal to a resolvable DNS host or IP address. Do not use localhost or 127.0.0.1. Those addresses interfere with clustered servers.
    3. In the Listen port field, enter the number of the port where the managed server listens for incoming messages.

    4. In the SSL listen port field, enter the appropriate value only if SSL is selected.

    5. Select SSL enabled as required.

    6. (Optional) Create further managed servers as required on your Network Integrity deployment.

    7. Click Next.

      The Configure Clusters screen appears.

  15. Do the following:

    1. Click Add to start configuring the cluster.

    2. In the Name field, enter the name for the cluster.

    3. In the Cluster messaging mode field, provide information about the messaging type to use in the cluster.

    4. In the Multicast address field, provide the multicast address that the cluster members use to communicate with each other.

    5. In the Multicast port field, provide the multicast port (between 1 and 65535) that the cluster members use to communicate with each other.

    6. In the Cluster address field, provide the cluster address information.

      The cluster address contains each managed server along with the managed server's port separated by a comma. Separate the managed server and the port number by a colon.

    7. Click Next.

      The Assign Servers to Clusters screen appears.

  16. Assign the servers to the cluster by moving the managed servers in the left pane to the required cluster in the right pane.

  17. Click Next.

    The Configure Machines screen appears. Use this screen to change the configuration information for the systems. A computer is the logical expression of the system that hosts one or more WebLogic Server instances. The Administration Server and the Node Manager application use the system definition to start remote servers.

  18. (Optional) Add the systems by doing one of the following:

    • Select the Machine tab, and do the following:

      1. Click Add to create the first system.

      2. In the Name field, enter a name for the system.

      3. In the Node manager listen address field, enter the host, or IP address of the node manager.

      4. In the Node manager listen port, enter the port number for the node manager.

      5. Create further systems as required on your Network Integrity deployment.

      6. Click Next.

        The Target Deployments to Clusters or Servers screen appears.

    • Select the UNIX Machine tab, and do the following:

      1. Click Add to create the first UNIX system.

      2. If required, select Post bind GID enabled. The default state is unselected.

      3. In the Post bind GID field, enter a value or select the default.

      4. In the Post bind UID field, enter a value or select the default.

      5. In the Node manager listen address field, enter the host, or IP address of the node manager.

      6. In the Node manager listen port field, enter the port number of the node manager.

      7. (Optional) Create further systems or UNIX systems as required on your Network Integrity deployment.

      8. Click Next.

        The Target Deployments to Clusters or Servers screen appears.

  19. Click Next.

    The Target Services to Clusters or Servers screen appears.

  20. Click Next.

    The Configuration Summary screen appears.

  21. Review the summary to verify the contents of your domain. Click Previous to return to prior screens to modify their content.

  22. Click Create to create the domain.

  23. After the domain is created successfully, click Done.

  24. Continue with the procedures in "Starting the WebLogic Server".

    For more information on configuring managed cluster servers, see Configuring Managed Cluster Servers.

    You can now log in to the Administration console and start the Administration Server manually.

Note:

Create domains for remote system in the same manner, in the respective systems.

Starting the WebLogic Server

To start the WebLogic server:

  1. Open a command window.

  2. Go to the Domain_Home/bin and enter the command:

    ./startWebLogic.sh 
    

    The script starts the WebLogic server.

  3. Verify that the server started by logging in to the WebLogic server administration console or by checking the log files.

    To access the WebLogic server administration console:

    1. Go to:

    2. http://ServerName:Port/console
      

      where ServerName is the name of the Administration Server system and Port is the Administration Server port number.

    3. Enter the WebLogic server administration user name and password.

    4. In the Domain Structure tree, expand Environment, and click Servers.

      The Summary of Servers screen appears.

    5. View the State of the server and see RUNNING.

      If the State is not RUNNING, you may need to wait a short period and refresh the page.

  4. Look at the bottom of the Administration Server command window.

    The command window should contain the following lines:

    Server state changed to RUNNINGServer started in RUNNING mode
    

Starting the Cluster Member Servers

Note:

If you have configured the node manager, you can start the Network Integrity cluster member servers using the WebLogic Administration Console.

Note:

If the managed servers are started simultaneously, the javax.naming.NameNotFoundException error message is displayed for JMS queues created under JDJMSModule module. To prevent this error message from being displayed, do not start the managed servers simultaneously.

To start the cluster member servers:

  1. Log in to the first cluster server system.

  2. Go to the DOMAIN_Home/bin directory.

  3. Start the cluster server using the following command executed from the system where the managed server is defined:

    ./startManagedWebLogic.sh cluster_managed_server_name admin_server_URL
    
  4. Start the second server by using the following command executed from the system where the managed server is defined:

    ./startManagedWebLogic.sh cluster_managed_server_name admin_server_URL
    
  5. To view the log file for each of the managed servers to verify that the server is in RUNNING mode, in a command window, enter:

    tail -f Managed_Server_1.log
    tail -f Managed_Server_2.log
    
  6. Look at the end of the managed server log files.

    The log files should contain the following lines:

    Server state changed to RUNNING
    Server started in RUNNING mode
    

    If you encounter errors (returned to the terminal, and contained in WebLogic Server domain and server logs) about the Stuck Thread Max Time: value being exceeded during these processes, see "Configuring the WebLogic Server StuckThreadMaxTime Value".

  7. Log in to the WebLogic console to check all of the cluster server states.

  8. Go to:

  9. http://ServerName:Port/console
    

    where ServerName is the name of the Administration Server system and Port is the Administration Server port number.

  10. Enter the WebLogic server administration user name and password.

  11. Select Servers and verify that the State of all servers is RUNNING. If you encounter

Note:

To configure the Node Manager, see the Oracle WebLogic documentation on the Oracle Technology Network located at:

http://www.oracle.com/technology

Configuring the WebLogic Server StuckThreadMaxTime Value

During the installation of Oracle WebLogic Server and Network Integrity in a clustered environment, if the execute thread takes more time than the Stuck Thread Max Time declared in WebLogic, a Stuck Thread Max Time error is displayed.

Stuck Thread Max Time is a property in WebLogic for performance tuning. It is defined as “the number of seconds that a thread must be continually working before this server considers the thread stuck”. The minimum value is 0 seconds; the default is 600 seconds.

Consider setting Stuck Thread Max Time from its default 600 seconds to a larger value such as 3600 seconds.

Use the WebLogic Console to change this value:

  1. Log in to the WebLogic Administration console.

  2. In the Home page, select Environment.

  3. Select Servers, and then click Admin Server.

  4. Select Configuration, and then click Tuning.

  5. Increase the value of Stuck Thread Max Time to 3600.

  6. Restart your domain. Your changes take effect only after a restart.

Configuring Automatic Service Migration (ASM) on the WebLogic Server

WebLogic server's Automatic Service Migration (ASM) framework monitors the health of JMS services and automatically migrates failing services to healthy and available servers. You configure WebLogic server for automatic service migration for failover and high availability.

For information on configuring Automatic Service Migration (ASM) on the WebLogic server, see Roadmap for Configuring Automatic Migration of JMS-related Services.

Caution:

Not configuring ASM on your WebLogic server results in the Network Integrity installer giving the following warning when launched:

Migration policy for the 'target' is manual. Recommended value is automatic migration. Refer to the JMS recommendations section of the documentation.

If you choose not to configure ASM, ignore the warning and continue with the installation.

To configure auto migration for JMS service in a WebLogic cluster:

  1. Configured Managed Servers and the Node Manager.

  2. Configure the Migration Leasing Basis as follows:

    1. Select the cluster where you are planning Auto JMS Service migration and select the Migration tab.

    2. Add all systems to Candidate Machines For Migratable Servers.

    3. Select the Migration Basis as Consensus.

    4. Save the changes and activate.

  3. Configure migratable targets as follows:

    1. Select the migratable target and select the Migration tab.

    2. Select Auto-Migrate Exactly-Once Services as Service Migration Policy.

    3. Add all Constrained Candidate Servers available.

    4. Repeat these steps for each migratable target associated with member servers in the cluster.

  4. Continue with installing Network Integrity.

  5. Once Network Integrity is installed, you can verify whether the environment is ready for JMS Service Auto Migration by following these steps:

    1. Select servers and navigate to the Migration tab.

    2. All member servers are selected in the JMS Service Candidate Servers list .

    3. Repeat these steps for all member servers in the cluster.

Verifying WebLogic Administration Server Migration

To ensure that the WebLogic Administration server has migrated:

  1. Log on to the Oracle WebLogic Server Administration Console.

    The Administration Console Home screen appears.

  2. Under Environment select Migratable Targets.

    The Summary of Migratable Targets screen appears.

  3. Select the Control tab to display it.

  4. If the WebLogic Administration server has migrated, then, in the Migratable Targets table, the ServerName in the Current Hosting Server column equals the corresponding ServerName in the Name column.

  5. In case the servers names showing in the two columns are different, do the following:

    1. Select the check box corresponding to the ServerName, and click Migrate.

      The Migrate Migratable Targets screen appears.

    2. From the New hosting server list, select the name of the hosting server and click OK.

      The server is migrated.