Check the Health on an On-Premises WebLogic Domain

Only Oracle Cloud at Customer This topic applies only to Oracle Cloud at Customer.

Use the AppToCloud Client to validate your on-premises WebLogic Server domain and applications in preparation to move them to an Oracle Java Cloud Service environment.
You must always run a Health Check on your WebLogic Server domain prior to performing an Export. It performs the following:
  • Connects to your running Administration Server

  • Verifies that your domain is in a healthy state

  • Generates the initial archive file that will be used during the export

  • Collects runtime information from all running servers in the domain, including the server’s JVM arguments and classpath

Before you perform a Health Check, you must install the AppToCloud tools to the host machine that is running the Administration Server for your domain. You must also ensure that your source domain meets all required prerequisites.

The AppToCloud Client can be used to perform both the Health Check and the Export tasks. Alternatively, you can perform these tasks from the command line or a script.

Decide how you want to specify the administrator credentials for the domain. Choose from one of these options:

  • Enter the credentials in the AppToCloud Client user interface.

  • Use the AppToCloud Client to store the credentials in a new Oracle Wallet file, or select credentials in an existing file.

  • Use the WebLogic Scripting Tool (WLST) storeUserConfig command to generate an encrypted file containing the credentials. Provide the locations of this file and the associated key file.

Any warnings or errors that the Health Check tool detects are written to a log, an HTML report, and the archive file. The Export tool checks the validation results in the archive before completing the export of your domain’s configuration.

To check the health of a WebLogic Server domain:

  1. Access the host that is running the Administration Server for your domain.
  2. Identify the top level directory of your WebLogic Server installation on this machine. This location is also referred to as ORACLE_HOME.

    For example, /u01/app/fmw.

  3. Start all servers in the domain if they are not already running.

    Refer to the relevant documentation for your version of WebLogic Server. For example:

  4. Determine the administration URL of the Administration Server: t3://host:port.

    For example, t3://myserver.mycompany.com:7001 or t3://192.0.2.10:9001

    AppToCloud connects to your domain using the T3 protocol. Do not use HTTP.

  5. Launch a terminal.
  6. If not already configured on your machine, set the JAVA_HOME environment variable to the directory where you have installed the Java SE Development Kit (JDK) version 7 or later.
    For example, on Linux:
    export JAVA_HOME=/u01/jdk

    On Windows:

    set JAVA_HOME=c:\u01\jdk

    Note:

    Do not run the AppToCloud tools using an older JDK version than the version being used to run your WebLogic Server domain. In addition, if your domain is running JDK 6, you must use a separate JDK 7 installation to run the AppToCloud tools.
  7. Go to the bin directory of your AppToCloud tools installation.

    For example: cd /u01/tools/oracle_jcs_app2cloud/bin

  8. Run the AppToCloud Client tool.

    On Linux: a2c-client.sh

    On Windows: a2c-client.cmd

    The Health Check page is displayed.

  9. Specify the Oracle Home directory for your WebLogic Server installation. Also enter an Output Directory for the Health Check.

    Optionally use the folder icons to browse your local file system. If the output directory does not exist it will be created.

  10. Enter the Admin URL for your running administration server.
  11. Select an Authentication option:
    • Password: Enter the Admin User and Admin Password for your domain.
    • Wallet: Proceed to the next step.
    • Config File: Use WLS Config File and WLS Key File to provide the location of your WebLogic credential file and corresponding key file.
  12. If you selected the Wallet authentication option:
    1. Click the folder icon next to Wallet Directory.

      The Change Wallet dialog is displayed.

    2. Choose to use an existing wallet or create a new one. Then click OK and follow the instructions:
      • Select an existing wallet: Select the folder containing the wallet. Enter a password if one is required.

      • Create a new wallet: Select a folder for your new wallet.

      • Create a new encrypted wallet: Select a folder for your new wallet and then enter a password.

    3. Click the user icon next to Admin User Alias.

      The Select Credential dialog is displayed.

    4. Select an existing credential in the wallet or click New to create a new one.

      For a new credential, enter its Alias, User and Password.

      Click OK to return to the main Health Check page.

  13. Click Run Health Check.
  14. Use the Progress, Report and Log tabs to verify that the Health Check completed successfully.

    An example Progress output:

    Initializing...
    Connecting to domain...
    Checking Java configuration...
    Checking applications health...
    Checking datasource health...
    Checking JMS health...
    Finished.

    An example Log output:

    Checking Domain Health
    Connecting to domain
    
    Connected to domain domainName
    
    Checking Java Configuration
    
    Checking server runtime : AdminServer
    
    Checking server runtime: serverName
    
    Checking server runtime: serverName
    
    Done checking Java Configuration
    
    Checking Servers Health
    Done checking Servers Health
    
    Checking componentName
    Checking componentName
    Done checking Domain Health
    
    Activity Log for HEALTHCHECK
    
    Informational Messages:
    Any informational messages
    
    Warning Messages:
    Any warning messages
    
    Error Messages:
    Any error messages
    
    An HTML version of this report can be found at outputDirectory/reports/reportFile
    
    Output archive saved as outputDirectory/archiveFile. You can use this archive for the a2c-export tool.
    
    a2c-healthcheck completed successfully (exit code = 0)
  15. If any problems are described in the Report or Log, address these problems and then click Run Health Check again.

    If the AppToCloud Client experiences time-out errors while trying to connect to your servers, click the Settings icon and modify the WLST Timeout field.

After completing the health check, you are ready to export the domain.