Chapter 1 Introduction to Decision Manager : Introduction to Rules Management Server

Introduction to Rules Management Server
You can configure RMS extensively. The product documentation describes the product as shipped, for example, it uses the workflow status values and general workflow behavior. If your installation has been customized, it may not exactly match product documentation. For example, you can implement a multi-stage approval, rather than the one-step approval process shipped with the product.
RMS is a lightweight rules management server component for managing the rules management repository. RMS provides user authentication features, decision project authorization and other project management features, and a project approval workflow.
Decision Manager communicates with RMS to retrieve decision projects, update local copies of decision tables, and commit changes to the decision table repository. RMS users approve or reject such changes.
RMS is implemented using BusinessEvents, and knowledgeable BusinessEvents users can customize it. The BusinessEvents project for RMS contains a state machine for an approval process that can be customized, for example.The BusinessEvents project is located in the BE_HOME/rms/project directory.
RMS provides an easy, secure, and scripted deployment lifecycle. It enables users to do the following:
Deploy approved implementations or projects to a running TIBCO BusinessEvents engine, and also undeploy implementations.
When Decision Manager users check out projects, a copy of the project is copied to their local machine so they can build decision tables. When the tables are committed to the server for approval, an RMS server user decides if the tables are ready for deployment. Class files are built and deployed to the runtime BusinessEvents application.