Deploying and redeploying a monitoring profile

Deploy or redeploy a monitoring profile in a Policy Project.

Before you begin

Create a monitoring profile and save it to a Policy Project by following the instructions in Creating a monitoring profile.

About this task

If you deploy a monitoring profile, it must be deployed in a policy project, and the XML file must have an extension of .monprofile.xml. To deploy a monitoring profile, complete step 1 and step 2 in the Procedure.

You can redeploy a monitoring profile by completing step 3 in the Procedure.

You can override a deployed monitoring profile by completing step 4 in the Procedure.

As an alternative to deploying the monitoring profile, you can place the monprofile.xml file in the integration server's overrides directory, as described in step 5 in the Procedure.

Procedure

  1. Create a BAR file to contain your Policy Project by completing the following steps:
    1. In the IBM® App Connect Enterprise Toolkit, switch to the Integration Development perspective.
    2. In the Application Development view, right-click the BAR file that contains the message flows, then click Open with > BAR Editor.
    3. Click the Manage tab.
    4. Click the message flow on which you want to set the monitoring profile configurable service. The properties that you can configure for the message flow are displayed in the Properties view.
    5. In the Monitoring Profile Name field, enter the name of a monitoring profile.
    6. Save the BAR file.
  2. Deploy the BAR file to your integration server.
  3. Optional: If you make further changes to the monitoring profile, you can save it to the Policy Project, edit the BAR file, and redeploy it to your integration server. All message flows that use the monitoring profile are stopped and restarted to use the new values.
    For more information, see Monitoring profiles.
  4. Optional: You can also override a deployed monitoring profile by putting an updated .monprofile.xml file in the integration server's overrides directory, as described in Order of precedence for overrides.
    You must restart the integration server to pick up any newly added or changed monprofile.xml file in the integration server's overrides directory.

As an alternative to deploying the monitoring profile, you can place the monprofile.xml file in the integration server's overrides directory, by completing the following step:

  1. Optional: As an alternative to deploying the monitoring profile, you can place the monprofile.xml file in the integration server's overrides directory.
    For integration servers that are managed by an integration node, the location of the overrides directory is $MQSI_WORKPATH/components/<Node name>/overrides/node.conf.yaml.
    For independent integration servers, the location of the overrides directory is <work directory>/overrides.
    You must restart the integration server to pick up any newly added or changed monprofile.xml file in the integration server's overrides directory.

What to do next

Monitoring for the flow is inactive. Deploying the BAR file does not activate monitoring for the flow. After you create and deploy the monitoring profile in a policy project, you must apply and activate the monitoring profile by using either the mqsichangeflowmonitoring command or the administration REST API. For more information, see Applying and activating a monitoring profile.

Alternatively, you can specify the monitoring profile as a BAR file override as described in Configurable properties in a BAR file.