Administration Guide › Action Alerts › Working with CA IT PAM Event/Alert Output Processes › Import the Sample Event/Alert Output Process › View the Sample Event/Alert Output Process

View the Sample Event/Alert Output Process

If you import the sample event/alert output process, you can examine its design in CA IT PAM. Use the following guidelines to become familiar with CA User Activity Reporting Module requirements in the context of the sample process. During this walk-through, you will see where to define web service connect parameters and how the calculation operators are defined. In addition, you will notice product-specific requirements. For example, configuring CA Service Desk as the third party product requires use of the Request_Create operator from the CA Service Desk Module and a precalculation operator that maintains values for severity and priority.

To become familiar with the sample event/alert out process

1. Display the model of your target process.
   1. Launch CA IT PAM and log in.
   2. Click ITPAM Client.
   3. From the File menu, select Open Library Browser.
   4. From the Folders tab, select the library folder containing the model for your target process.

      The name of your process and path appear in the main pane.

   5. Double-click the row containing your process name and path.

   A model similar to the following appears. This example model contains minimal requirements for CA User Activity Reporting Module.

   

2. Notice how the ServiceDesk Basic Parameters meet CA User Activity Reporting Module requirements.
   1. Double click the Request_Create_1 icon.

   

   The Request_Create operator passes the data returned by the action alert query to your target product (application). A similar operator is required for any process that is to be run from CA User Activity Reporting Module.

   1. Under ServiceDesk Basic Parameters, notice that local process parameters are specified with the following syntax:

      BasicParameter = Process.LocalParameter
      

      Note: Local process parameters are the Event/Alert Output Process Parameters you add to CA User Activity Reporting Module when you configure CA IT PAM.

   

   1. Since the target application is the CA Service Desk product, the following local process parameters are defined as described on the following table:

The following example shows valid local parameters for ServiceDesk Basic Parameters. The entries are case-sensitive. That is, Process.ReportedBy must be entered exactly as shown with a capital "R" and a capital "B" for example.

1. Click the ServiceDesk Connect Parameters tab for Request_Create to view the ServiceDesk Connect Parameters.
   • Service Desk URL:"http://<server name>:8080/axis/services/USD_R11_WebService"
   • Service Desk User ID:"<SD user>"
   • Password:"<SD password>"
2. Notice that for CA Service Desk, an adjustment is needed to ensure that the values of severity and priority that are entered in CA User Activity Reporting Module are correctly interpreted by CA Service Desk.
   1. A pre-calculation operator appears after Start and before the Create_Process operator. In the following example, it is named Fix_Sev_Pri.

   

   1. Under Properties, Calculate, the following mappings are defined:

      if (Process.Priority == 1) Process.Priority = "pri:504";
      else if (Process.Priority == 2) Process.Priority = "pri:503";
      else if (Process.Priority == 3) Process.Priority = "pri:502";
      else if (Process.Priority == 4) Process.Priority = "pri:501";
      else if (Process.Priority == 5) Process.Priority = "pri:500";
      

      if (Process.Severity == 1) Process.Severity = "sev:800";
      else if (Process.Severity == 2) Process.Severity = "sev:801";
      else if (Process.Severity == 3) Process.Severity = "sev:802";
      else if (Process.Severity == 4) Process.Severity = "sev:803";
      else if (Process.Severity == 5) Process.Severity = "sev:804";
      

3. Notice that the following return value, or output interface, parameters are formatted as required by CA User Activity Reporting Module:
   • ResultString
   • FaultString
4. View the calculation operator for request creation success. This format must be used in any event/alert output process to be run from CA User Activity Reporting Module.
   1. Click the icon for the calculation operator for request creation success.
   2. Select the Calculate tab and click ... in the source code field.
   3. Notice how the success calculation operator is defined in the source code:

      Process.ResultString = "Request " + Request_Create_1.newRequestNumber + " created in CA Service Desk.";
      

5. View the calculation operator for failure. This format is required for any event/alert output process to be run from CA User Activity Reporting Module.
   1. Click the icon for the calculation operator for failure.
   2. Select the Calculate tab and click ... in the source code field.
   3. Notice how the failure calculation operator is defined in the source code, where the Process.FaultString maps to the appropriate SOAP variable:

      Process.FaultString = Request_Create_1.SoapErrorResponse;