RDA 8.01 - Now A Better Experience for WebLogic Administrators
By Daniel Mortimer-Oracle on Oct 07, 2013
What is RDA?
Not familiar with RDA (Remote Diagnostic Agent)? Well I won't use this blog entry to provide a lesson, but if you want to learn more, take a look at these two support articles:
- Get Proactive with Fusion Middleware : Resolve Problems Faster! Use Remote Diagnostic Agent [ID 1498376.1]
- How to Run Remote Diagnostic Agent ( RDA ) Against Oracle WebLogic Server ( WLS ) [ID 1262157.1]
Too many questions in set up
"I have to answer too many questions at set up time!". The first of two criticisms leveled at a RDA collection which targeted a WebLogic Server based technology stack. Well I pleased to say that the number of questions of has been reduced.
If, for example, you set up RDA using the "WebLogicServer" profile, you will encounter a set up dialogue similar to the one copied / pasted from a Weblogic 12c solution, on Unix, below.
Tip: Work through the set up questions a little quicker by configuring your environment variables to point at your Middleware Home and location of your WebLogic domain prior to running RDA set up. Doing so, allows RDA to find default values for certain questions, which means you can just hit return and move on.
# Setting the environment . /home/oracle/app/FMW12c_1212/config/user_projects/domains/my_domain/bin/setDomainEnv.sh ORACLE_HOME=/home/oracle/app/FMW12c_1212/oh; export ORACLE_HOME
# Running RDA set up
cd /home/oracle/software/rda ./rda.sh -S -p WebLogicServer # Set up dialogue
Enter the network domain name for this server > uk.acme.com Enter the Oracle home to be used for data analysis Hit "Return" to accept the default (/home/oracle/app/FMW12c_1212/oh) >
Enter the location of the directory where the domains to analyze are located (For example in UNIX, <BEA Home>/user_projects/domains or <Middleware Home>/user_projects/domains) Hit "Return" to accept the default (/home/oracle/app/FMW12c_1212/config/user_projects/domains) >
For a successful WLS connection, ensure that the domain Admin Server is up and running. Data Collection Type: 1 Perform offline collection 2 Perform online collection (using WLS connection) Enter the item number Hit "Return" to accept the default (2) > Select a Oracle WebLogic Server domain home target list: 1 Domain my_domain (in /home/oracle/app/FMW12c_1212/config/user_projects/domains) A All Oracle WebLogic Server domain home targets D Define a new Oracle WebLogic Server domain home target E Edit an Oracle WebLogic Server domain home target N No Oracle WebLogic Server domain home targets Enter your selection, as a comma-separated list of item numbers or ranges Hit "Return" to accept the default (1) >
Server list for 'my_domain' domain: 1 AdminServer 2 ms3 Enter your selection, as a comma-separated list of item numbers or ranges Hit "Return" to accept the default (1-2) >
Are custom scripts used to start Oracle WebLogic servers (Y/N)?
Hit "Return" to accept the default (N) > # The next prompt concerns OCM. You are not required to configure OCM. # If time is short, just answer 'N' RDA benefits from Oracle Configuration Manager by improving its data collection. Oracle Configuration Manager (OCM) collects the configuration information and uploads it to the OCM Repository in connected mode. When OCM is configured in disconnected mode, it adds the OCM payload to the RDA report packages in future RDA runs. Pending Configurations in /home/oracle/app/FMW12c_1212/oh: MH_T0001 Middleware home /home/oracle/app/FMW12c_1212/oh Hit 'Return' to continue Do you want RDA to configure OCM now (Y/N)? Hit "Return" to accept the default (Y) > N
# After answering the prompts set up will be complete. # Now just launch the command line script (no parameters) # to run the collection ./rda.sh
"Cannot see the wood for the trees" in the output
This is the second of the criticisms. RDA does collects many files and metrics - this is one its strengths. Yet I think it is fair to say that the presentation of WebLogic Server data in the RDA Start Menu (generated as part of the output) lacked some order and structure. For example, server log files were somewhat buried, and similarly, unless you knew to scroll down to WLST collections, you could not easily ascertain the basic contents of a targeted Weblogic domain. In RDA 8.01, the sub menus for the WebLogic Domain and Servers have been re-ordered to address this concern. Review the screenshots below.
Figure 1 : WebLogic Domain Sub Menu
Note: In the Main Index, RDA will only list managed servers which have been targeted for collection. In this example, only AdminServer and ms3 were targeted for collection. Yet we can see from the Domain MBeans that the domain contains other managed servers and a cluster.
Figure 2 : MBean Drill Down Example - Admin Server State
Figure 3: WebLogic Server Sub Menu
To take advantage of these changes download the latest version of RDA. The download links can be found in
Get Proactive with Fusion Middleware : Resolve Problems Faster! Use Remote Diagnostic Agent [ID 1498376.1]