This topic applies only to Oracle Cloud at Customer.
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)
storeUserConfigcommand 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:
- Access the host that is running the Administration Server for your domain.
- Identify the top level directory of your WebLogic Server installation on this machine. This location is also referred to as
- 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:
Starting and Stopping Servers in Administering Server Startup and Shutdown for Oracle WebLogic Server (188.8.131.52)
Starting and Stopping Servers in Administering Server Startup and Shutdown for Oracle WebLogic Server (184.108.40.206)
Starting and Stopping Servers in Managing Server Startup and Shutdown for Oracle WebLogic Server (10.3.6)
- Determine the administration URL of the Administration Server:
AppToCloud connects to your domain using the T3 protocol. Do not use HTTP.
- Launch a terminal.
- If not already configured on your machine, set the
JAVA_HOMEenvironment variable to the directory where you have installed the Java SE Development Kit (JDK) version 7 or later.For example, on Linux:
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.
- Go to the
bindirectory of your AppToCloud tools installation.
- Run the AppToCloud Client tool.
The Health Check page is displayed.
- 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.
- Enter the Admin URL for your running administration server.
- 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.
- If you selected the Wallet authentication option:
- Click the folder icon next to Wallet Directory.
The Change Wallet dialog is displayed.
- 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.
- Click the user icon next to Admin User Alias.
The Select Credential dialog is displayed.
- 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.
- Click the folder icon next to Wallet Directory.
- Click Run Health Check.
- 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)
- 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.