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.
WebLogic Management provides a unified view to manage WebLogic Server instances deployed on OCI. You can perform lifecycle management operations, such as patching, starting, stopping, or restarting WebLogic domains running on compute instances.
Learn about working with OCI instances in WebLogic Management, the domains and servers in instances, server patch readiness, and how to unregister instances.
Learn about known and operational issues and how to resolve them.
Key Features
Unified view of WebLogic Server instances
Discover WebLogic Server instances deployed on Oracle Cloud Infrastructure (OCI). Identify which versions of WebLogic Server are running on compute instances and whether they're on the latest security patches.
On-demand patching of WebLogic domains
Maintain patch compliance for a fleet of WebLogic Server instances deployed on OCI. WebLogic Management maintains the patch inventory, identifies applicable patches, and applies them on the corresponding WebLogic domains with the click of a button.
Easily rollback the last patches applied to WebLogic domains.
Perform lifecycle management operations on WebLogic domains.
Understanding the Agent π
WebLogic Server domains deployed in Oracle Cloud Infrastructure use the Oracle Cloud Agent to interact with WebLogic Management. You enable the WebLogic Management plugin for Oracle Cloud Agent by registering it with the service. See Registering an OCI Instance.
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.
The WebLogic Management plugin performs the following periodic tasks:
Domain discovery: A configurable scan that runs every 6 hours by default for the service to identify new domains and changes to existing domains. You can also configure the scan at the managed instance level.
Heartbeat detection: Sends a periodic heartbeat to the service so that the service knows that the plugin is active.
Poll for Work: Periodically queries the service for work.
The plugin also communicates with the service for the following tasks:
On-demand scans:
Domain scans identify new servers in the WebLogic domain, checks if the domain is on the recommended patches, and checks if the domain can be patched.
Managed instance scans identify new servers in the managed instance, checks if the managed instance is on the recommended patches, and checks if the managed instance can be patched.
Patch WebLogic domains: The plugin gathers the applicable patches and is responsible for applying the patches to WebLogic Server middleware.
Start, restart and stop WebLogic domains: The plugin starts, restarts, or stops the WebLogic Server instances on the compute instances.
Authorization and Authentication π
Each service in Oracle Cloud Infrastructure integrates with IAM for authentication and authorization, for all interfaces (the Console, SDK or CLI, and REST API).
An administrator in your organization needs to set up compartments, user groups, dynamic groups, and policies in Identity and Access Management (IAM) that control which users can access which services, which resources, and the type of access. For example, the policies control who can create new users, create and manage the cloud network, create instances, create buckets, download objects, and so on. For more information, see Getting Started with Policies.
For details about writing policies for other services, see Policy Reference.
If youβre a regular user (not an administrator) who needs to use the Oracle Cloud Infrastructure resources that your company owns, contact your administrator to set up a user ID for you. The administrator can confirm which compartment or compartments you are permitted to use.
WebLogic Management is available in the following Oracle Cloud Infrastructure commercial regions:
Region Name
Region Identifier
US East (Ashburn)
us-ashburn-1
Search π
Use Search to find resources within a tenancy, Console pages in services, and documentation within the Oracle Cloud Infrastructure getting started and user guides.
Search supports queries for the WebLogic Management resource listed in this section.
You can apply tags to your resources to help you organize them according to your business needs. You can apply tags at the time you create a resource, or you can update the resource later with the wanted tags. For general information about applying tags, see Resource Tags.
If you have permissions to create a resource, then you also have permissions to apply free-form tags to that resource. To apply a defined tag, you must have permissions to use the tag namespace. For more information about tagging, see Resource Tags. If you're not sure whether to apply tags, ask an administrator or skip this option. You can apply tags later.
Ways to Access Oracle Cloud Infrastructure π
Learn the different ways you can access Oracle Cloud Infrastructure.
You can access Oracle Cloud Infrastructure using the Console (a browser-based interface) or the REST API. Instructions for the Console and API are included in topics throughout this guide. For a list of available SDKs, see Software Development Kits and Command Line Interface.
To access the Console, you must use a supported browser. To go to the Console sign-in page, open the navigation menu at the top of this page and click Infrastructure Console. You are prompted to enter your cloud tenant, your user name, and your password.
For general information about using the API, see REST APIs.