With Rhino SAS API, you can implement SAS tracing, which means capturing call processing data in your application and sending it to SAS.

Tip For a development environment, you can manage all the development, deployment, and configuration tasks yourself. However, for a production environment, you may need the help of an administrator to handle tasks such as application deployment or Rhino SAS facility configuration.

To implement SAS tracing for a component in your application, take the following steps:

  1. Create a mini-bundle file — a yaml file that defines events.

  2. Add events to the mini-bundle.

    In each event, you can define parameters for the data you want to send.

  3. Generate a Java enums file from the mini-bundle.

    The enums file contains the enums that represent the events in the mini-bundle and the data the events use.

  4. In your code, add logic for capturing and sending data.

  5. Create a bundle mapping file — a yaml file that defines a unique ID for each mini-bundle in your application.

    In the data sent to SAS, these IDs are added to the event IDs as prefixes so that SAS can differentiate events from different components within the deployed application.

  6. Build your application and deploy it onto Rhino TAS.

  7. Configure the SAS facility to connect to relevant SAS servers and then enable SAS tracing.

  8. Export a resource bundle file from Rhino TAS.

    The resource bundle file is a yaml file that contains event and enum definitions from the mini-bundles, with the event IDs prefixed with relevant IDs from the bundle mapping file. SAS uses information in the file to display events.

  9. Import the resource bundle file in SAS and test the data sent from your application.

Note Information about exporting the resource bundle file and configuring the SAS facility is in the Rhino Administration and Deployment Guide.

The use of the resource bundle file enables Rhino TAS to send only event IDs and relevant parameter values to SAS. SAS reads the event summary information locally from the imported resource bundle file. This way, Rhino SAS API makes efficient use of the bandwidth between Rhino TAS and SAS.

Subsections provide detailed instructions on each step, with necessary code examples. For a complete code example that involves all the steps, check the example service source code of the HTTP Resource Adaptor. The HTTP Resource Adaptor Guide provides more information about the code.

Previous page Next page