Thursday, November 29, 2012

EM12c: How to use Weblogic Domain Provisioning Profile with Gold Image?

Assumption: User has EM12cR2 with FMW plugin

A WebLogic Domain Provisioning Profile consists of the Middleware Home, binaries and the domain configuration. One can create a WLS domain provisioning profile, save it in the Software Library, and then use the saved profile as the source for creating new WebLogic domains. This will ensure that future WebLogic installations follow a standard, consistent configuration.
Lets see an example how to create WLS domain provisioning profile.

1. Both source as well destination Host and source WLS domain are monitored target on EMCC.
2. You have the host credentials for both source machine as well as destination host.
3. Source Weblogic Domain should be JRF enabled.

Steps to create WLS domain provisioning profile:
1. Select Enterprise menu->Provisioning and Patching->Software Library.

2. From the Actions menu->click Create Folder to create a folder in which the profile you are creating is to be stored as shown below:
3. Select the newly created folder->Actions menu-> Create Entity-> Component

4. A Create Component window appears. From the Select Subtype drop-down list, select the "WebLogic Domain Provisioning Profile" component and click Continue.

5. In the Create WebLogic Domain Provisioning Profile wizard: Describe page, provide details as given below:

6. Click Next. The Create WebLogic Domain Provisioning Profile: Configure page appears. Do ensure that checkbox for 'Include the binaries from Middleware Home in the profile to be created.' is selected. Now using search icon, select the source Weblogic Domain, from which you would like to create the gold image.
Provide the host credentials in the lower panel as shown here:

7. Click Next. In the Review page, review the profile information and click Save and Upload.

8. The <Job Name> is displayed at the top of the page. Navigate to the Job Activity page and check the job status.
Once it has been completed, navigate to the Software Library page and confirm if all the components of the profile (WebLogic Domain, MWHome, and Profile) have a Ready Status. You can also verify if the profile has been successfully created by navigating to the Middleware Provisioning page. From the Enterprise menu, select Provisioning and Patching, then select Middleware Provisioning and check if the profile is displayed there. You can now use this profile as the source for future WebLogic Domain installations.

Steps to clone a WLS domain from a WLS domain provisioning profile:
1.  Select Enterprise menu->Provisioning and Patching-> Middleware Provisioning.

2. Select profile that was created in earlier steps from the Profiles section->click Provision. ( or select the Middleware Provisioning deployment procedure and click Launch)

3. In the Source page of Provisioning wizard, the selected component and its location is displayed. Click Next.

4. In the Middleware Provisioning: Destinations page, specify the destination hosts on which the WebLogic Domain is to be cloned. Also provide host credentials. For details look at given image:

In the lower panel "Destination Locations" section, one can specify the location of the Middleware Home on the Host machine. The Create a New Middleware Home option is selected by default.

In the Middleware Home Directory field, one enter the full path to the directory in which the Middleware Home is to be created.

In the JDK Home Location field, enter the absolute path to the JDK directory to be used on the destination Host. This field can be edited only if the JDK Home in the source domain is in an external location. If the JDK Home in the source domain is internal and installed in the Middleware Home, this field cannot be edited.

In the Working Directory field, specify the directory on the destination Host on which the cloning related files are temporarily stored.

5. Click Next. Now the Middleware Provisioning: Domain Configuration page appears. This page contains a set of links to several pages where one can enter the properties that are most likely to be reconfigured like domain name, listen addresses for the administration server and managed servers, Node Manager/Machine configuration and JDBC data sources. By default, the source domain configuration settings are used as default values for the destination domain.

In the Server Startup Mode, select JRF startup clssses.

For more details on configuration, go to step 15-23 on

6. In the Schedule page, select default values. Click Next.

7. On the Review page, review the details. click Submit.

8. In the Procedure Activity page, view the status of the execution of the job and steps in the deployment procedure. Click the Status link for each step to view the details of the execution of each step. One can click Debug to set the logging level to Debug and click Stop to stop the procedure execution.

9. Once the procedure is successful, goto Targets->Middleware and see the newly created wls domain target.

Monday, November 19, 2012

EM12c: How to deploy JVMD agent on weblogic 12c manually?

Assumption: User has EM12cR2 with FMW plugin

Simple option would be to deploy jamagent via Diagnostics Agent Deployment wizard. In case when deployment job fails for some reason then jamagent can be deployed manually. Instructions are given below.

1. Goto Setup Menu->Application Performance Management->Select JVM Diagnostics Engine->Click on Configure button as shown here

2. Select 'JVMs and Pools' tab on 'JVM Diagnostics Setup' page

3. Click on Download button

4. It will show you a Dialogue box that will list options to download JVMD Agent/DB Agent/JVMD Engine. Select JVMD Agent.

5. For a weblogic server, do provide the WLS server EM target name as Target Name and WLS Domain name as Pool Name. Click on Download button.

6. Download jamagent.war

7. Take this jamagent.war and deploy it via weblogic console UI.

Note: One can find more info on

Friday, November 09, 2012

EM12c: How to change the EM Agent Port?

The EMAgent uses a particular port to receive requests from the OMS. This port number is defined by default when one installs the EMAgent on a target host.
If one needs to modify this port at some point, one can use the following steps.

To change the EMAgent port:

1. Stop the EMAgent.
$ $AGENT_HOME/bin/emctl stop agent

2. Modify the $AGENT_HOME/sysman/config/ file in the EMAgent home directory:
    For example:

    Modify the <port number> in the EMD_URL property so the EMAgent uses a new unused port on the target host.

3. Start the EMAgent.
$ $AGENT_HOME/bin/emctl start agent

With this port change the target name of agent will not change on OMS side, it will still show the original port. But it will work using the new port now as given below

$ ./emctl status agent
Oracle Enterprise Manager Cloud Control 12c Release 2 
Copyright (c) 1996, 2012 Oracle Corporation.  All rights reserved.
Agent Version     :
OMS Version       :
Protocol Version  :
Agent Home        : /home/oracle/agent12c/agent_inst
Agent Binaries    : /home/user01/agent12c/core/
Agent Process ID  : 5732
Parent Process ID : 5643
Agent URL         :
Repository URL    :
Started at        : 2012-11-09 10:02:47
Started by user   : oracle
Last Reload       : (none)
Last successful upload                       : 2012-11-09 11:35:21
Last attempted upload                        : 2012-11-09 11:35:21
Total Megabytes of XML files uploaded so far : 0.2
Number of XML files pending upload           : 0
Size of XML files pending upload(MB)         : 0
Available disk space on upload filesystem    : 64.97%
Collection Status                            : Collections enabled
Heartbeat Status                             : Ok
Last attempted heartbeat to OMS              : 2012-11-09 11:37:11
Last successful heartbeat to OMS             : 2012-11-09 11:37:11
Next scheduled heartbeat to OMS              : 2012-11-09 11:38:11

Agent is Running and Ready