WLSDM for WebLogic
Published in

WLSDM for WebLogic

Upgrading and Patching WLSDM

WLSDM new releases and updates come continuously, which will transform WLSDM into a unique viewing experience after upgrade. New update with ease of use and bug fixes; It brings the native WebLogic viewing experience offered to date to better levels. By upgrading the current WLSDM version, you can continue to use the WLSDM capabilities you are used to with the latest version.

1. WLSDM Upgrade and Patching Tutorial

1.1 Download latest WLSDM zip package and replace wlsdm_agent.jar

After unzipping the downloaded WLSDM zip, the wlsdm_agent.jar file needs to be placed in the server at $DOMAIN_HOME/wlsdm_agent/ , replacing the old file, by using the command below.

cp $wlsdm_package/jar/wlsdm_agent.jar $DOMAIN_HOME/wlsdm_agent/wlsdm_agent.jar

This operation should be repeated for all servers using the WLSDM agent.

1.2 Replace wlsdm.war

After unzipping the downloaded WLSDM zip, the wlsdm.war file inside has to replace the old file on the Admin Server at ${WEBLOGIC_DOMAIN_HOME}/console-ext/

Use the command below:

cp $wlsdm_package/war/wlsdm.war to ${WEBLOGIC_DOMAIN_HOME}/console-ext/.

1.3 Update startup arguments of the Managed Servers that use the agent

The startup parameter values of the Managed Servers that use the WLSDM agent have to be updated for JDK 1.7.0_40 or JDK 1.7.0_40 Higher or JDK Add the following WLSDM and JFR JVM arguments to WebLogic Managed Server(s)


1.4 Restart the managed servers

The managed servers for which parameters were updated, need to be restart.

1.5 Shut down the Admin Server

After restarting the particular Managed Servers, the Admin Server also needs to be shut down.

1.6 Delete the WLSDM Runtime Folder (Optional)

Using the admin user, the WLSDM folder under $DOMAIN_HOME has to be deleted. This operation needs to be performed for the Admin Server only. If any Managed Server available on AdminServer host, these Managed Server’s also need to be shut down.

Important Note: When this folder is deleted, all WLSDM history data and configurations are deleted accordingly. We do this some time to make a fresh installation. Because, WLSDM’s installation and completing WLSDM wizard is less than a minute. WLSDM also has exporting configuration feature, before deleting this folder, taking a full configuration backup would be helpful while completing wizard again.

1.7 Start the Admin Server and Managed Servers

The Admin Server and the Managed Servers with the updated agent needs to be started in this step.

1.8 Complete the WLSDM configuration

The Configuration wizard needs to be completed using a user with the admin role.

Enter the license key (Optional, Free in Development Mode):

In this step, you can apply the exported WLSDM configuration. For the SMTP settings and other settings, a previously used WLSDM config file can be uploaded

Register WLSDM domain to WL-OPC

Carry out the Domain Resource selection

Configure Metrics, Deployments, and Data Source settings

Configure the monitoring settings then complete the wizard

Useful WLSDM features for security management:

1. Setting the WLSDM-Admin role

To give the WLSDM-Admin role to the user with the WebLogic security monitor role:

1.1. Go to the “Configuration > WLSDM System Settings page”

1.2 Select “system.authorization”

The user with the monitor role is set using “system.authorization.wlsdm.console.administrators” property

2. Removing Decrypt Feature (Optional)

“Data Source Password Encryption” feature and “Decrypt-Encrypt” page will be disabled when “-Dwlsdm.system.adminModeDisabled=true” parameter added to startWebLogic.sh script’s JAVA_OPTIONS. This argument can be used only for AdminServer startWebLogic.sh script.

export JAVA_OPTIONS=”${JAVA_OPTIONS} -Dwlsdm.system.adminModeDisabled=true”

Download WLSDM Now !



Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store