Oracle® Composite Application Monitor and Modeler Installation and Configuration Guide Release 10.2.0.5.1 Part Number E14147-03 |
|
|
PDF · Mobi · ePub |
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.
Collect the credentials for database and application server installation
Unpack the zip file
Run Disk1/InstData/<platform>/VM/install.bin
Select the location to install into when prompted, do not create links
Start the configuration console by running em10g/bin/config.sh
Connect a web browser to https://<server>:5560/qvadmin
Log in as admin/admin (user name/password), you will be prompted to change the password on login
Go to the Configuration tab and click Database Configuration
Select the default MyOracle connection and click Edit Configuration
Enter your database access credentials
Click Test Connection to verify database connection and then click OK
If you are monitoring a WebLogic server, deploy em10g/deploy/HttpDeployer.ear to your admin server. This step is optional for OC4J.
Return to the CAMM UI, click Resource Configuration
Click Create New Resource
Click Configure and enter your application server access information
Click OK to return to the previous screen
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.
Click Back to return to the previous screen and then click Deploy
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.
Click Continue
Wait for deployment to complete. Verify that the UI reports Deployment Successful; if not, check for exceptions in log/manager-log#.csv
Click Back to return to the previous screen and then click Save
Close the browser-based console
Shut down the configuration console by running em10g/bin/acshut.sh
Wait about 15 seconds for the shutdown to complete
Restart the application servers you deployed the Agent to
Start the CAMM Manager by running em10g/bin/acsera.sh (for example, nohup ./acsera.sh &")
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.
Connect a web browser to https://<server>:5560/qvadmin
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