Add Oracle WebLogic Server/Domain

You can add Oracle WebLogic Server/Domain entities using the Add Entity UI or using the cloud agent command line interface (omcli) with the appropriate JSON files.

Step 1: Prepare Oracle WebLogic Server/Domain for monitoring.

Prerequisites

To enable monitoring of a Oracle WebLogic Server (WLS), use a WebLogic user with at least the Monitor role. The user can also have Operator or Administrator roles, which include the Monitor role.

If you have enabled the Oracle WebLogic Server with SSL, you must export the certificate from its keystore and import it in the Cloud Agent keystore. Perform the following steps:
  1. Stop the Cloud Agent.

    omcli stop agent

  2. Export the certificate from the WLS instance JMX SSL keystore to the Cloud Agent's truststore. For example, on a UNIX host:

    cd <agent base Directory>/agentStateDir/sysman/config/montrust

    keytool -exportcert -alias <alias of WLS SSL key> -file <Exported Cert Name> -keystore <path to the WLS SSL Keystore>.keystore -storepass <WLS SSL Keystore password> -rfc

  3. Import the WLS instance JMX SSL keystore to the Cloud Agent's truststore:

    keytool -import -noprompt -alias <alias agent's truststore key> -file <Exported Cert Name>.cer -keystore AgentTrust.jks -storepass <Agent truststore password, default is "welcome">

  4. Restart the Cloud Agent..

    omcli start agent

Step 2: Decide how you want to add the Oracle WebLogic Server/Domain.

You can add Oracle WebLogic Server/Domain entities using one of two ways:

  • Add them from UI
  • Use the agent's omcli add_entity command with the appropriate JSON files

Adding Entities from the UI

  1. From the Management Cloud main menu, select Administration, Discovery, and then Add Entity. The Add Entity page displays.
  2. Select the Oracle WebLogic Server/Domain Entity Type.
  3. Enter the following UI properties.
    WebLogic Domain /WebLogic Server UI Fields
    • Entity Name: Your WebLogic Domain name.
    • Port: The port used for WebLogic Admin Server(Console).
    • Protocol: The protocol used for WebLogic Server - For example: t3
    • Administration Server Host: the fully-qualified host name where the WebLogic Admin Server is installed.
    • Discover Coherence: (True/False) Specify whether Coherence Clusters deployed on the Weblogic domain should discovered. This option is set to True by default. Turn this option off when discovering a SOA Suite domain.
    • Cloud Agent: Cloud agent monitoring the host where WebLogic is installed.

    Monitoring Credentials (WebLogic Server Credentials)

    • Username: WebLogic Server user name.
    • Password: WebLogic Server username password.

See Add Entities from the Console for detailed instructions on using the Add Entity UI.

Using omcli and the Appropriate JSON Files

  1. Download and extract the required JSON file(s) from the master JSON zip file. See the table below for the specific JSON files you'll need.
  2. Edit the file(s) and specify the requisite properties shown below.
    WebLogic Domain /WebLogic Server JSON Files and Properties

    Definition File: omc_weblogic_domain_sample.json

    Note:

    When you add a WebLogic Domain entity (requiring credentials), because Oracle Management Cloud connects to the WebLogic Admin Server, all WebLogic Clusters and WebLogic Servers that are part of that domain are automatically discovered. There’s no need to add them separately.
    • name: Your WebLogic Domain name.
    • displayName: Name displayed in the Oracle Infrastructure Monitoring User Interface.
    • timezoneRegion: Time zone of your entity. It is recommended that you use the long values IANA-maintained TZ database time zones. For example: America/New_York
    • port: Under “value”, provide the port used for WebLogic Admin Server(Console).
    • protocol: Under “value”, provide the protocol used for WebLogic Server - For example: t3
    • admin_server_host: Under “value”, provide the fully-qualified host name where the WebLogic Admin Server is installed.

    Credential File: omc_weblogic_domain_sample_creds.json

    • username: Under “value”, within the square brackets, provide the WebLogic Domain monitoring user name. You must have defined this user in the Prerequisite Tasks step.
    • password: Under “value”, within the square brackets, provide the WebLogic Domain monitoring user’s password.

    Do not remove the square brackets.

  3. Add the entity using omcli.
    omcli add_entity agent DEFINITION_FILE [-credential_file CREDENTIAL_FILE [-encryption_method_gpg]] 
  4. Verify the status of the newly added entity.
    omcli status_entity agent DEFINITION_FILE

See step 4. Adding Entities to Your Service of Add Entities Using JSON Files for more information.

Step 3: (Optional but recommended) Set up alerts.

To enable lights-out monitoring, you can set up alert rules to generate alerts and send notifications if your entities have performance issues.

See Set Up Alert Rules and Set Up Alert Thresholds and Notifications.

Troubleshooting

If you run into any issues regarding discovery or monitoring of Oracle WebLogic Server/Domain, see the following: