This section describes how an RMS project is created and used by Decision Manager users. This section assumes initial RMS configuration has been done. It describes the approval workflow shipped with the product.
RMS can be customized. Different user roles can be given different permissions, and the approval workflow can be changed and extended. The following is a general overview of the procedures in the product as shipped.
1. A BusinessEvents user creates a TIBCO BusinessEvents project, creating the ontology, and writing rules that make use of virtual rule functions (VRFs). (VRFs are implemented later by a business user using decision tables.)
2. An RMS user takes the EAR file from that BusinessEvents project and sets up an RMS project for it. He or she creates access control files, and other files that are needed by the project such as domain model files and test files.
4. A business user logs in to Decision Manager and requests a decision project by checking it out and saving the project to disk.
5. The business user creates one or more decision tables and saves the modified decision project locally. Business users with permission can create domain models to make data entry more reliable.
6. The business user tests the decision tables locally with a locally running BusinessEvents engine started by Decision Manager automatically. Business users with permission can create test data.
9. RMS generates class files in a known location on a production BusinessEvents engine. (Or the files can be manually copied there as needed.)
10. The class files are either hot deployed to a running system, or are deployed when the BusinessEvents system starts up, depending on configuration and timing.The end result is that the business logic defined by the business user is now part of the BusinessEvents application.
Copyright © TIBCO Software Inc. All Rights Reserved.