Skip Headers
Oracle® Composite Application Monitor and Modeler Installation and Configuration Guide
Release 10.2.0.5.1

Part Number E14147-03
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Index
Index
Go to Feedback page
Contact Us

Go to previous page
Previous
Go to next page
Next
PDF · Mobi · ePub

Quick Steps for Installing the CAMM Agent

The following list summarizes the steps used to install the CAMM Agent (Agent). For details of the installation, refer to the chapters in this manual.

  1. Collect the credentials for database and application server installation

  2. Unpack the zip file

  3. Run Disk1/InstData/<platform>/VM/install.bin

  4. Select the location to install into when prompted, do not create links

  5. Start the configuration console by running em10g/bin/config.sh

  6. Connect a web browser to https://<server>:5560/qvadmin

  7. Log in as admin/admin (user name/password), you will be prompted to change the password on login

  8. Go to the Configuration tab and click Database Configuration

  9. Select the default MyOracle connection and click Edit Configuration

  10. Enter your database access credentials

  11. Click Test Connection to verify database connection and then click OK

  12. If you are monitoring a WebLogic server, deploy em10g/deploy/HttpDeployer.ear to your admin server. This step is optional for OC4J.

  13. Return to the CAMM UI, click Resource Configuration

  14. Click Create New Resource

  15. Click Configure and enter your application server access information

  16. Click OK to return to the previous screen

  17. Click Test Connection. If you are monitoring a WebLogic server, wait for the em10g/lib/bea/<version>_runtime directory to be created and populated with jar files. This could take a few minutes. If nothing happens, check log/manager-log#.csv for exceptions.

  18. Click Back to return to the previous screen and then click Deploy

  19. On the subsequent screen, select Deploy from the Command menu and then select the servers/cluster you want to deploy the Agent to. Ensure that the admin server is always selected.

  20. Click Continue

  21. Wait for deployment to complete. Verify that the UI reports Deployment Successful; if not, check for exceptions in log/manager-log#.csv

  22. Click Back to return to the previous screen and then click Save

  23. Close the browser-based console

  24. Shut down the configuration console by running em10g/bin/acshut.sh

  25. Wait about 15 seconds for the shutdown to complete

  26. Restart the application servers you deployed the Agent to

  27. Start the CAMM Manager by running em10g/bin/acsera.sh (for example, nohup ./acsera.sh &")

  28. Wait for discovery to occur. You can check that discovery is happening by looking to see if em10g/darchive/server_archive is created and growing, and then that em10g/darchive/app_archive is created and growing. If you think something is going wrong, you can check log/manager-log#.csv for exceptions, but this process can take several minutes.

  29. Connect a web browser to https://<server>:5560/qvadmin

  30. Click the CAMM node in the navigation tree and verify in the Agent Information table that the Agent Status for all servers you deployed the Agent to are REPORTING