Upon finishing your application development, you will need to package the application and deploy it onto Rhino TAS, so that the application can run and send data to SAS.

When you create a SLEE component JAR file, make sure that you include the following files:

  • The mini-bundle files in your application.

    Rhino TAS needs to read the event definitions from these mini-bundle files. In the JAR file, put the mini-bundle files in subdirectories under META-INF/sas-bundles, with the subdirectory structure matching the names of relevant Java packages. For example, if the mini-bundle is for a package named com.abc.feature.xyz, its path in the JAR file should be META-INF/sas-bundles/com/abc/feature/xyz/sas-bundle.yaml.

  • The compiled Java enums files generated from relevant mini-bundle files.

    Compile and package the enums files like other Java class files. For example, in the JAR file, the path of one of the enums file might be com/abc/feature/xyz/SasEvent.class.

Don’t include the bundle mapping file in the deployment package. Once the application is deployed, you can use the setsasbundlemapping Ant task to install the bundle mapping file onto Rhino TAS.

After deploying the application and installing the relevant bundle mapping file, you can export a resource bundle file from Rhino TAS with the exportsasbundle command. SAS uses information in the resource bundle file to format the data it receives from your application.

Previous page Next page