Weblogic Multiple Instances

Learn more about Weblogic that can run multiple instances on a single endpoint. To support accurate detection and seamless patching of all Weblogic installations, BigFix uses the Middleware Scanner. The scanner discovers all installed versions and paths, while the patching process updates outdated versions in a single execution.

Scanner Process

For running the scans on every software versions, refer to BigFix Scanner for Middleware Application. These results are then used by the Weblogic patching tasks to determine which instances require updates.

Note: Before performing any patching activity, it is recommended to create a backup of all custom configurations, instance files, and environment-specific settings. This ensures that you can restore custom configurations if required after the patching process.

Patching Process

Before starting the Weblogic patching process, it is recommended to review that all the required prerequisites are met. Refer to the documentation based on your Weblogic version:

Recommended:

Weblogic 12.2.1.4: https://docs.oracle.com/en/middleware/idm/identity-governance/12.2.1.4/bpspb/prerequisites.html

The Weblogic patching task uses the scanner results to identify lower versions and update them to the patch version specified in the task.

Select the applicable computer in the BigFix Console to review installed versions.
When you take action on the endpoint, the patching task reads the results.xml and identifies all Weblogic instances.
All outdated/lower Weblogic versions are updated in a single execution, including:
Recommended:
If only one instance is found, that specific instance is patched.

If multiple instances (for example, five) are found, the task loops through all five instances and attempts to patch them all in a single execution.
If the installed version is the same or greater, then the patching is skipped.
Note:
- Services must be stopped before starting the patching process and should be restarted once the patching is complete.

Exit codes and their meanings

When performing tasks such as patching or extracting files in Weblogic, certain exit codes may be returned to indicate the outcome of the operation. These codes help to find the issues during the installation or update process. Below is a list of common exit codes, along with their meanings and suggested actions to resolve the issues.

Table 1. Exit codes and their meanings
Exit code	Action
Exit Code 11: Patch Failure	Patching for one or more Weblogic instances has failed. Check the logs in the <BES Client>/middleware/weblogic and /middleware/ for full details.