Services and Connectors: Service Testing e-learning Course Resource

Transcription

1 Services and Connectors: Service Testing e-learning Course Resource Service Activities You can individually unit test your service activity prior to creating a service package and service rule. The service activity can be unit tested in the same way that you would unit test other activities. Remember: Once the service rule is created, the service rule executes actions such as creating a Page, executing a Model, and setting data from the Request. You can create a wrapper activity (that calls the service activity) to set up some of these action and then unit test by running the wrapper activity. Below is an example of the simplest service activity. It adds 100 to the input (BaseValue parameter), returning a result (CalculatedValue parameter). 1. Click the green icon on toolbar to start unit testing the activity. 2. Enter a value for the BaseValue input parameter in the testing dialog that displays and click Execute. 1 Pegasystems Inc.

2 Here is the resultant status window after performing the test: This activity updates an output parameter. If it was updating the contents of some other page on the Clipboard, access the Clipboard tool to see the results. Rule-Parse-XML Specialized rules in data transformations can be individually unit tested outside of testing your service rule or service activity. For instance, use the Run icon available on a Rule-Parse-XML rule to enter the text to be parsed in several different ways and then view the parse results. Below is a screenshot of a Rule-Parse-XML rule, along with its unit testing window. Click on the green run icon to perform the unit test. This rule is an OOTB rule that is not part of the rest of this example. 2 Pegasystems Inc.

3 Service Rules The Run icon available on a service rule allows you to unit test it. By unit testing a service rule, you can test both the service activity and the data transformations. You are prompted to enter in Request parameters, and if execution is successful, you can view the Response parameter result. When testing service rules, you can also identify whether you are going to use the logged in Requestor context or a completely new Requestor context. When using the logged in Requestor context, you can view the results in the Clipboard viewer. To test a service rule: 1. Click the green run icon on a service rule to open the parameters window. 2. Enter values for the Request parameters - in this case BaseValue. 3 Pegasystems Inc.

4 3. Click Execute to display the simulation results window. Note the new value is 600, which is the 500 that was input, plus 100 added by the service activity. If you use the logged in Requestor context, then view the results in the Clipboard viewer. Trace Open Rule For some service rules you can perform a Trace Open Rule, which opens up a tracer session that enables you to trace the service rule and the service activity. Select Services in the trace options to enable this feature. The trace output for a service shows you the data transformations that occur during Request and Response. To individually trace a Service Rule: 1. Select Trace Open Rule from the menu to display the Tracer. Trace Open Rule is only available when you are displaying a Service Rule rule form. 4 Pegasystems Inc.

5 2. Click the wrench icon to display the trace options, and at a minimum select Activity Steps and Services for tracing. 5 Pegasystems Inc.

6 3. Conduct a unit test exactly as performed as described in the Service Rules section. Upon completion of the test, the Tracer shows its output. Because you are tracing services, the tracer displays output regarding the data transformations (see highlighted areas for Inbound and Outbound mapping). PAL Use PAL to individually test your service rules and service activities. It is also possible to write PAL statistics to a log file using the PAL API. PAL is executed in the same manner for services as for anything else. The key is to refresh PAL statistics just prior to performing the unit test of the service rule. prlogging.xml You can log the execution of PRPC classes that support service processing by configuring the classes in prlogging.xml. Below is a snapshot of a portion of prlogging.xml. The file can be found at <tomcat root>\webapps\prweb\web-inf\classes. The highlighted entry is not what is logged when interested in service issues, but it is a java class that has been enabled for logging. There are some java classes that specifically support service processing, and these can be found in the javadoc and/or some of the PDF reference material for this course. The idea is that you can log information for classes that process services, and the configuration would be similar to the category entries indicated below: 6 Pegasystems Inc.

7 Alert Configuration There are different options for configuring alerts relevant to services. Configuration is done in prconfig.xml. The following are some screenshots of alert configuration items that can be configured in prconfig.xml. There are many things that can be configured in prconfig.xml. The items below illustrate configuration relevant to services. prconfig.xml can be found at <tomcat root>\webapps\prweb\web-inf\classes, the same location as prlogging.xml. These screenshots are from the ConfigurationSettingsReference guide on the PDN: 7 Pegasystems Inc.

8 8 Pegasystems Inc.

9 9 Pegasystems Inc.

10 10 Pegasystems Inc.

11 11 Pegasystems Inc.