Oracle Cloud Infrastructure Documentation

Getting Started with WebLogic Management

Before you get started with WebLogic Management, you must complete prerequisite tasks and ensure that access has been granted.

Important

Pre-General Availability: 2024-10-11

The following legal notice applies to Oracle pre-GA releases. For copyright and other applicable notices, see Oracle Legal Notices.

Pre-General Availability Draft Documentation Notice

This documentation is in pre-General Availability status and is intended for demonstration and preliminary use only. It may not be specific to the hardware on which you are using the software. Oracle Corporation and its affiliates are not responsible for and expressly disclaim all warranties of any kind with respect to this documentation and will not be responsible for any loss, costs, or damages incurred due to the use of this documentation.

Before getting started, ensure you meet the basic prerequisites for the service, and then complete the following tasks to get started:

Prerequisites

  • You're familiar with Oracle Cloud Infrastructure (OCI) and OCI services. To get started with OCI, see Welcome to Oracle Cloud Infrastructure.
  • You have access to an OCI tenancy.
  • A tenancy administrator in your organization already set up user groups, dynamic groups and compartments to use to control can access WebLogic Management and its resources.
  • You have provisioned and deployed WebLogic Servers that can be managed using WebLogic Management.
  • You have installed Oracle Cloud Agent on the instances running WebLogic Servers.
Important

WebLogic Management requires minimum Oracle Cloud Agent version 1.47. For instances with an older version installed, upgrade the Oracle Cloud Agent to 1.47 or later.

Setting Up Required IAM Policy

The Set up policy feature creates the policies required to use WebLogic Management. These required policies must be set at the root compartment (tenancy) by a tenancy administrator, otherwise, WebLogic Management can't discover domains.

User groups, dynamic groups and IAM policies specify which users and services can access certain OCI resources. You must identify which WebLogic Management resources the service can manage and which users can manage those resources. To do this, define user groups, dynamic groups, and then set up the required IAM policy.

If you're new to policies, see Getting Started with Policies. If you have specific policy requirements or use cases, see Policies and Permissions for more information.

Required policy statements

The Set up policy feature creates the following policy statements that are required policy to use the service.

Policy statement Description
Allow group $USER_GROUP to manage instance-family in compartment id $COMPARTMENT_ID

Allows the user group to manage WebLogic Management plugin in the compartment and its subcompartments.
Allow group $USER_GROUP to read instance-agent-plugins in compartment id $COMPARTMENT_ID

Allows the user group to interact with the WebLogic Management plugin in the compartment and its subcompartments.
Allow group $USER_GROUP to manage wlms-family in compartment id $COMPARTMENT_ID

Allows the user group to manage all WebLogic Management resources in the compartment and its subcompartments.
Allow group $USER_GROUP to use wlms-config in tenancy

Allows the user group to read and update the WebLogic Management Service configuration for the tenancy.
Allow group $USER_GROUP to manage secrets in compartment id $COMPARTMENT_ID

Allows the user group to manage OCI secrets in the compartment and its subcompartments.
Allow dynamic-group $DYNAMIC_GROUP to read secret-bundles in compartment id $COMPARTMENT_ID

Allows the WebLogic Management plugin to read OCI secrets in the compartment and its subcompartments.
Allow dynamic-group $DYNAMIC_GROUP to use wlms-managed-instance-plugins in tenancy

Allows the WebLogic Management plugin to use the WebLogic Management service.
Allow resource wlms server-components to read instance-family in compartment id $COMPARTMENT_ID

Allows the WebLogic Management plugin to check the status of OCI instances.
Set up policies

  1. Verify you have the manage policies in tenancy permission. If you only have read or use permissions, you get an authorization error.

  2. Open the navigation menu and click Observability & Management. Under WebLogic Management, click Overview.
  3. Under List scope, select the compartment that contains the WebLogic domains running on OCI managed instances.
  4. Click Set up policy.
  5. In the Set up policy panel, provide the required information:
    1. Policy name: Accept the default name or enter a friendly name for the policy.
    2. Target compartment: Select the compartment to grant permissions to use the service.
    3. Identity domain: Select the identity domain where the user group and dynamic group resides.
    4. User group: Select a user group to grant permission to use the service.
    5. Dynamic group: Select a dynamic group to grant permissions to use the service.
    Note

    If you are not ready or do not have permission to set up the policies, click Copy policy statements. Then, you can use these statements to create the policies or you can give them to the tenancy administrator. See Manually Creating Required IAM Policy.
  6. Click Set up.

Registering an OCI Instance

When you register an instance with WebLogic Management Service it displays in the Console as a managed instance.
  1. Install the Oracle Cloud Agent software, if it's not already installed. Verify the version is 1.47.0 or later.
  2. Open the navigation menu, click Compute, and then click Instances.
  3. Click the instance that you want to register.
  4. Click the Oracle Cloud Agent tab.
  5. Enable the WebLogic Management Service Agent.
  6. Wait up to 10 minutes for the Oracle Cloud Agent to enable the WebLogic Management Service Agent plugin.
    Important

    After you enable the WebLogic Management plugin on an instance, the instance registers with the service. The Console, however, does not display WebLogic domains on the instance until after the initial discovery scan, which is scheduled at the top of the following hour. Or, you can start an on-demand scan after the WebLogic Management plugin is running on the instance.

    When the scan detects the presence of WebLogic domains, the plugin reports the discovery details to the service. This initial discovery phase can take some time to complete.

  7. When the initial discovery phase is completed, verify that the resources are visible in the Console and that their status is Active. See Verifying WebLogic Management Resources.
    Important

    If the initial scan does not discover any WebLogic domains, verify that the domain discovery settings are correct.
Repeat these steps for each instance you want to manage with WebLogic Management Service.

Verifying WebLogic Management Resources

Review WebLogic Management in the Console and verify that the instances are visible and their resources are available and active.
  1. Open the navigation menu and click Observability & Management. Under WebLogic Management, click Managed instances.
  2. Under List scope, select the compartment that contains the instance.
  3. Confirm the instance appears in the table, and verify the status is Active.
    Important

    If the instance is not in the list, verify that WebLogic Management is enabled and you set up the required WebLogic Management policy.
  4. Click the name of the instance to view its details.
  5. In the Servers section, verify the servers and their domains are listed and that the servers are running.
    Important

    If you do not see any servers or domains, verify that the domain discovery settings are correct.
  6. Click WebLogic Management and then Domains
  7. From the Domains list, verify the domains on the instance are listed.
  8. Click the name of a domain to view its details.
  9. In the Servers section, review the restart order and change, if necessary. See Viewing or Setting Restart Order of Servers.

What's Next

After you have completed the prerequisites, set up IAM policy, and registered instances, go to the WebLogic Management Overview page to see a summary of instances, domains and servers and their statuses.

Complete the following configuration tasks: