Deploying monitor models using the Fast Path option

Use the Fast Path option to deploy a monitor model with default settings and a minimum amount of monitor model customization. You can use the Fast Path option when you deploy a new monitor model or when you deploy a new version of an existing monitor model. You can also use the Fast Path option in a development or test environment.

1. From the WebSphere® Application Server administrative console, click Applications > Monitor Models. The table that is displayed lists all of the currently deployed monitor models.
2. Click Install.
3. Specify the location of the EAR file you want to deploy, and then click Next.
4. Select Fast Path - Prompt only when additional information is required, and click Next.
5. From the Install New Application page, use the fast path to complete these steps:
   1. Step 1: Select installation options

      Complete this page, and then click any of the following optional steps in the left column. Step 4, Configure security for the monitor model requires input when application security is enabled.

      To deploy a new version of a monitor model, change the name of the monitor model in the Application name field.

      If you are deploying a new version of an existing monitor model, the version time stamp must be more recent than any previously deployed versions of that model. When you deploy a new version, the previous version is automatically configured to process events associated with existing monitoring-context instances only (meaning, a CEI distribution mode of active). New monitoring-context instances are created only by the new version. Also, events associated with any previous versions that were configured with a CEI distribution mode of inactive (event queue recoverable) are processed by the new version before it processes events on its own event queue.

   2. Step 2: Map modules to servers

      If you want to take advantage of workload management throughout a cluster for your 6.1, 6.2, or 7.0 monitor model, you can map Enterprise JavaBeans (EJB) modules to different servers or clusters. The moderator EJB module can use a cluster for high availability only, and the model logic EJB module can use a cluster for high availability and for scalability. If you do not want to take advantage of workload management, there is no benefit in deploying to separate targets.

      If you want to take advantage of workload management throughout a cluster for your 7.5 or 8.0 monitor model, you can also map an Enterprise JavaBeans™ (EJB) module to a cluster. In a 7.5 or 8.0 monitor model, the model logic EJB module can use a cluster for high availability and for scalability.

      When mapping the modules of a monitor model application, the target cluster must meet the following requirements in order to host the modules:

      • The cluster members of the target cluster must reside on nodes that have been augmented with the IBM® Business Monitor profile template.
      • When creating the first cluster member of the target cluster, you must have selected a server template containing the text defaultWBM in the name.

      For additional information about the benefits of mapping EJB modules to servers in a distributed environment, see the topic "EJB modules mapped to distributed servers" in the related links.
      • For 6.1, 6.2, and 7.0 monitor models:
        1. Select the moderator module from the list of modules. The name ends with "Moderator."
        2. From the Clusters and servers list, select the target cluster for the moderator module and click Apply.
        3. Click Apply.
        4. Select the model logic module from the list of modules. The name ends with "ModelLogic."
        5. From the Clusters and servers list, select the target cluster for the model logic module and click Apply.
        6. Click Apply.
      • For 7.5 and 8.0 monitor models:
        1. Select the model logic module from the list of modules. The name ends with "ModelLogic."
        2. From the Clusters and servers list, select the target cluster for the model logic module and click Apply.
        3. Click Apply.
   3. Step 3: Metadata for modules

      Use this page to instruct a Java Platform, Enterprise Edition (Java EE) 5 enterprise bean (EJB) or web module deployment descriptor to ignore annotations that specify deployment information. If the metadata-complete attribute is set to true, annotations that specify deployment information are ignored.

   4. Step 4: Configure security for the monitor model

      Input is required if application security is enabled.

      For a monitor model to be visible to users, it must be added to a resource group and users must be assigned a role within that resource group. Select an existing resource group or create a new resource group for the monitor model you are deploying.

   5. Step 5: Summary

      To complete the deployment steps, verify that all information is correct, and click Finish.

6. To review the model deployment information, click Review changes before saving or discarding, or to save the model, click Save directly to the master configuration.