Proactive insights, news and tips from Oracle Fusion Middleware Support. Learn Oracle from Oracle.

How to run a RDA collection for SOA without providing a password at runtime?

Guest Author
One of my previous blog posts shows in detail how to collect information for a SOA domain using RDA (Remote Diagnostic Agent):

Diagnose SOA Suite 11g Issues Using RDA (Remote Diagnostic Agent).

However, a complete RDA collection for a SOA Suite domain including database artifacts takes some time. Also specific requirements may make it necessary to run the actual RDA collection at times of low system load. Or via a cron job. Usually, during an RDA collection, which connects to the WebLogic Server or to the database, passwords need to be provided.

In newer versions of RDA, functionality has been added so that passwords may be stored in the setup.cfg file in encrypted format. This can be accomplished by using the -A parameter of RDA.

RDA can collect data for one or more domains. RDA can either figure out the name of the administration user to connect to WebLogic Server, or it will ask for it during the setup phase. After the setup is done, a setup.cfg file is created that contains all information necessary to run a collection. Except passwords needed.

To add password information in order to run a RDA collection in silent mode, run the following commands:
  • For every domain (1..n), add the password for the administration user:
    • rda.[cmd|sh] -A WLS_USER_SOA_DOMi

    Use the number of the domain instead of i, like WLS_USER_SOA_DOM1, ..., WLS_USER_SOA_DOMn
  • For every domain (1..n), add the password for the SOAINFRA database schema user:
    • rda.[cmd|sh] -A YourPrefix_SOAINFRA@myhost.mydomain:1521::oracle_sid

After all passwords are stored in setup.cfg, collections can run in silent mode. They can be scheduled via a cron job or run by scripts.

Be the first to comment

Comments ( 0 )
Please enter your name.Please provide a valid email address.Please enter a comment.CAPTCHA challenge response provided was incorrect. Please try again.