TIBCO BusinessEvents: Workflow

1. User in your enterprise creates a TIBCO Designer project, creates an ontology, and writes rules that makes use of virtual rule functions to be implemented later by a business user using decision tables.
2. IT Administrator takes the Designer project and sets up the RMS.
3. IT Administrator starts the TIBCO BusinessEvents Rules Management Server.
4. Business user logs in with valid credentials and requests decision project by checking it out and saving it to the disk.
5. Depending on the permissions given by the Rule Administrator, business user creates a decision table.
6. The business user saves the modified decision project locally.
7. The business user tests the decision tables locally with a locally running BusinessEvents engine started by Decision Manager automatically.
8. The business user submits the modified or the new decision table for approval once done with the project.
9. Rule Administrator receives the request and approves or rejects the project.10.Rule Administrator takes the deployed class files generated automatically and deploys them to a production BusinessEvents engine.

Read more...

BusinessEvents: User Roles of Decision Manager

Explaining about different user roles of Decision Manager, and various tasks that they can undertake.

Decision Manager has the following End Users:

• Business User: In this role, you use the client application to update the existing projects by creating decision tables in a decision project, modifying the tables, checking-in and checking-out the decision projects and submitting the projects for approval to the Approver.
• Rule Administrator: In this role, you setup RMS, create and set up the projects, and ensure proper deployment. You decide what the business user can do using Decision Manager. You could fulfill the roles of the Approver and Deployer as well.
• Approver: In this role, you use the client application to approve or deny decision projects committed by the business users.
• Deployer: In this role, you use the client application to select approved entities and deploy or undeploy them.
• Developer: This user customizes the client and or uses it as a User Interface (UI) component library. This user can perform the following:

1. Configuring the business user’s user interface
2. Writing the new UI components
3. Creating project structure model—Authoring rules
4. Authoring rules
5. Creating and validating deployment process
6. Verifying the entire system before releasing it to the rest of the organization

Read more...