WebStudio and RMS User Workflow

The rules authored in TIBCO BusinessEvents WebStudio are made available to a TIBCO BusinessEvents application after following a complete approval workflow.

Step 1: RMS Project Setup

A TIBCO BusinessEvents user creates a TIBCO BusinessEvents project, adding the ontology, and writing rules that make use of virtual rule functions (VRFs) and Rule Templates.

The TIBCO BusinessEvents project for RMS is stored at the location defined by a property in the RMS server configuration. The RMS project requires an access control file for authorization.

The RMS server must be running so that the login and workflow actions are available in the TIBCO BusinessEvents WebStudio component.

Step 2: TIBCO BusinessEvents WebStudio

A business user starts the TIBCO BusinessEvents WebStudio component, logs on to RMS, and checks out the project. The business user creates one or more decision tables, business rules, or process and saves the modified project locally, then commits them for approval.

Note: If the business user is creating/modifying the decision table for the first time, then the user generates EAR files before creating/modifying decision tables.

Step 3: Approval

An RMS user (with the "approval" access control rights) working in TIBCO BusinessEvents WebStudio receives the request and reviews the checked-in artifacts and then approves or rejects them. The approved artifacts are available for subsequent checkouts or updates.

Step 4: Generating Deployable Files

An RMS user generates deployable files for resources that are ready for deployment. You can generate EAR files or class files.

Step 5: Deployment

EAR files are deployed in the usual way, as explained in TIBCO BusinessEvents Administration. Class files for decision tables and rule template instance files for business rules are deployed by placing them in a configured location recognized by the TIBCO BusinessEvents engines at start up. They can also be hot-deployed.