1 CAMM Operation and Environment Dependencies

The installation of CAMM involves a few manual steps and the configuration of supporting subsystems including an RDBMS-based CAMM Data Repository.

To guarantee the successful deployment and operation of CAMM, you are expected to:

• Understand CAMM operation modes

• Comply with the pre-deployment and post-deployment requirements

• Understand or have access to someone who understands basic database management in order to setup the repository database

It is important to choose the proper CAMM Operation mode and comply with the environment requirements before starting the actual deployment.

1.1 CAMM Operation Modes

CAMM can operate in two modes: Service Mode and Standalone Application Mode. This section provides some insight into these modes of operation.

1.1.1 Service Mode

CAMM typically runs as a headless Java process that monitors your Oracle WebLogic, Oracle SOA Suite, and/or IBM WebSphere environments. In service mode, monitoring of your applications continues in the background, even when the user interface is not present. Service Mode is the default mode.

The user interface is delivered as a Java applet in a web browser.

Figure 1-1 visualizes the Service Mode CAMM topology:

Figure 1-1 Service Mode CAMM Topology

1.1.2 Standalone Application Mode

In the Standalone Application Mode, CAMM runs as a GUI based application rather than a UNIX daemon or Windows service. In contrast to the Service Mode, this mode provides a single-user GUI and does not require a separate web container to host the web application for browser GUI delivery. The Standalone Application Mode is used primarily for quality assurance and demonstration purposes.

When you start the GUI application, CAMM starts, and when the application is closed, CAMM discontinues operation. In this mode, monitoring and data collection continue only when the application is running. It is useful for occasional debugging and testing of configuration and general connectivity to systems in your environment. However, in most environments where continuous monitoring is required, it is advised to run CAMM in Service Mode.

The following figure shows an example of CAMM deployed in Standalone Application Mode monitoring an Oracle WebLogic and IBM WebSphere application server environment:

Figure 1-2 Application Mode Camm Topology