Web Service Wizards-2: Creating Process Definition Stubs From a WSDL File

When we use this Web Service wizard...? To know click here

To create a service resource and process definition stubs from a WSDL file, perform the following procedure:

• Place the WSDL file in your project directory.
• If your project is not open, open your project in TIBCO Designer. If your project is already open in TIBCO Designer, choose Resources > Refresh from the menu
• Create a transport shared configuration resource (either HTTP Connection or JMS Connection) to use as the transport for the web service.
• Select and right-click on the name of the WSDL file in the project tree.
• Choose Tools or Multi-User > Generate Web Service > From WSDL from the pop-up menu. The WSDL to Process dialog appears.
• Review the values for the fields in the WSDL to Process dialog. The default values may be sufficient for your purposes, or you may wish to change the values.
• Click Generate to create a Service resource and process definition stubs for the operations in this WSDL file. The Service resource is named (interfaceName)-service and the process definition stubs are named (portType)(operationName). The service and process definition stubs are placed in the location specified in the WSDL to Process dialog.
• Click the (interfaceName)-service resource in the project tree to display the service. Ensure the endpoint bindings are specified correctly. For HTTP transports, you may need to specify the Endpoint URI. For JMS transports,you must specify the destination name and other JMS configuration information.
• Click on each process definition stub and provide the implementation for each operation by completing the process definition for the operation.

Read more...

Web Service Wizards-1: Creating Web Services From Process Definitions

When we use this Web Service wizard...? To know click here

Procedure To create a service resource and WSDL file from one or more process definitions

• Open a project in TIBCO Designer and create one or more process definitions that implement operations you wish to expose as web services. The input,output, and error schemas for each process definition must be specified as WSDL messages.
• Create a transport shared configuration resource (either HTTP Connection or JMS Connection) to use as the transport for the web service.
• Select and right-click on the name of one of the process definitions in the project tree.
• Choose Tools or Multi-User > Generate Web Service > From Process from the pop-up menu.The Generate Web Service dialog appears.
• Review the values for the fields in the Generate Web Service dialog. The default values may be sufficient for your purposes, or you may wish to change the values.
• Click Generate to create a Service resource and WSDL file for the selected process definitions.The Service resource is named intf(processDefinitionName)-service and the WSDL file is named intf(processDefinitionName).
• Click the intf(processDefinitionName)-service resource in the project tree to display the service. Ensure the endpoint bindings are specified correctly. For HTTP transports, you may need to specify the Endpoint URI. For JMStransports, you must specify the destination name and other JMS configuration information.

Read more...

Web Service Wizards

TIBCO BusinessWorks provides two wizards for easily creating web services. The two wizards are useful in the following situations:

• you wish to expose one or more process definitions as web services.
• you have a WSDL file describing the interface to a web service and you wish to quickly create the process definition stubs that will implement the operations in the interface

Wizard 1: Creating Web Services From Process Definitions

Wizard 2: Creating Process Definition Stubs From a WSDL File

Will describe about these wizards in the next posts.

Read more...

General procedure to create Web service in TIBCO

1. Create XSDs to define the input, output, and fault messages for the web service.
2. Create a WSDL File resource that defines the interface to the web service.
3. Create a process definition that performs the work of the web service. Use the SOAP Event Source process starter for this process definition. Use the SOAP Send Reply activity to return a reply or the SOAP Send Fault activity to return a fault to the client.
4. Create a process definition that retrieves the concrete WSDL file and sends it to web service clients. Use the HTTP Receiver process starter and the Retrieve Resources activity for this process definition.

Read more...

Redeploying an Application: Changes Made to EAR and Deployment Files

If you change both the TIBCO Designer project and the deployment configuration file, you must upload both when redeploying. For example, you may want to make the following changes:

• add new services or delete existing services (adapter, process or form flow archives)
• add or remove deployment level or service level variables (including Adapter SDK properties)
• change checkpoint storage from File to JDBC or JDBC to JDBC, where the new JDBC Shared Resource was not part of the Shared Archive in the original EAR file

If you have changed both the TIBCO Designer project and the deployment configuration file, complete the following steps to redeploy the changed application:

1. Build an EAR file using the buildear utility. For example:buildear -s -ear /filenotify.archive
2. Generate a new deployment configuration file using the EAR file created in the previous step, the deployment configuration file used when previously deploying the application and specify a new deployment configuration file.
3. After you have made the changes to your deployment configuration file, you are ready to deploy the application.

Read more...

Starting & Stopping Applications in Batch Mode

The following command starts all applications specified in the AppManage.batch file that is located in the directory specified for the -dir option. The directory must have been created earlier using the -batchExport option.

AppManage -batchstart -domain mydomain -user admin -pw admin -dir c:\adminbatch\mybatch\

The following command stops all applications specified in the AppManage.batch file that is located in the directory specified for the -dir option.

AppManage -batchstop -domain mydomain -user admin -pw admin -dir c:\adminbatch\mybatch\

Read more...

AppManage in Batch Mode

To use the AppManage utility in batch mode you must first create an AppManage.batch file. The file lists the applications and their corresponding EAR and XML files. You can create the file manually, but the files listed in the AppManage.batch file must be specified using relative file paths. The base of those relative paths is the directory specified by the –dir option that is given on the AppManage command line.

The easiest way is to generate the file using the -batchExport option. In addition to creating the AppManage.batch file, the option creates an enterprise archive file and XML file for each application in the given domain.

After creating the AppManage.batch file, you can use the AppManage utility to do the following operations in batch mode:

• Deploy applications
• Undeploy applications
• Start or stop applications
• Delete applications
• Kill applications
• Change the transport

Read more...

How to start the AppManage and buildear utilities

To start the AppManage utility, change directory to TIBCO_TRA_HOME\bin and type AppManage -action where options include -export, -upload, -config, -deploy, and -undeploy etc.

• The AppManage utility must be run on a machine that is part of the administration domain you are updating.

Starting Buildear:

To start the buildear utility, change directory to TIBCO_TRA_HOME\bin and type

buildear -options.

You should verify your project by loading it into TIBCO Designer before you use the project with the buildear utility. If the project doesn't load correctly in TIBCO Designer, the buildear utility doesn't support it.

Read more...

AppManage utility Log Files

The AppManage utility writes information to a log file. The log file location depends on whether you are accessing an administration domain or not.

• If you are not accessing an administration domain, the log is written to the TIBCO_TRA_HOME\logs\ApplicationManagement.log file.
• If you are accessing an administration domain, the log is written to the TIBCO_TRA_DOMAIN_HOME\domain-name\logs\ApplicationManagement.log file.

A comparison log file is generated if you export from an EAR file without specifying an administration domain. This information can help you decide whether you need to change the deployment configuration file after an EAR filechanges.

For example, using the following command line, the AppManage utility compare sthe oldconfiguration.xml file with the given EAR file. If any service, global variables, or both have been added, removed, or updated, a log file is created in the same directory where the oldconfiguration.xml file resides, using the file name, oldconfiguration.xml.log.

AppManage -export -ear c:\ears\timer_wait.ear -deployConfig oldconfiguration.xml -outnewconfiguration.xml

Read more...

Uses of AppManage utility in Scripting Deployment

• The AppManage utility creates an XML based deployment configuration file in which deployment options can be defined.
• The utility also uploads the deployment file and EAR file into a TIBCO Administrator administration domain.
• Create a deployment configuration file based on information in an EAR file, or from an application already configured in the TIBCO Administrator GUI.
• Upload an EAR file to an administration domain without specifying deployment configuration options. After the file is imported, it is ready to be configured with deployment options and deployed using the TIBCO Administrator GUI.
• Upload an EAR file and a deployment configuration file and deploy the application in one operation. Using this method, you can quickly deploy your applications in multiple domains.
• Export all application archives and deployment configuration files within adomain, so they can be batch deleted, started, stopped, undeployed, or deployed in another domain. For TIBCO Rendezvous administration domains, you can change the transport set for application to administration server communication, from rv (Rendezvous) to local, or the reverse.
• Undeploy a deployed application.
• Delete an application from an administration domain.
• Start a service instance of an application.
• Stop a successfully deployed service instance of an application.

Read more...

About AppManage Utility- Script deployment

The scripting tools allow you to build an EAR file for an application configured in TIBCO Designer, then load the application into one or more TIBCO Administrator administration domains. Deployment options can be specified in a deployment configuration file that is created using the AppManage utility.

• If your application is not complex and needs only machine bindings defined for each domain, you can use the AppManage utility to create the deployment configuration file from information in the EAR file, then edit the configuration file with the machine names where the applications will be deployed. In this scenario, the TIBCO Administrator GUI is not used.
• If your application is complex and needs more than machine bindings defined, you can import an EAR file into the TIBCO Administrator GUI and specify deployment configuration options for the application. This method is preferred if your application includes complex mappings, such as fault tolerance, runtime variables, alerts and so on.

In this scenario, the TIBCO Administrator GUI is used to initially set the application’s deployment configuration options. After the options are set, the TIBCO Administrator GUI is no longer used. The AppManage utility updates the deployment configuration file from the application configured in the TIBCO Administrator GUI. The file is edited for each administration domain by changing machine bindings and so on, then deployed into each administration domain.

Read more...

About Tibco Silver

TIBCO Silver is the industry's first cloud application delivery platform for the enterprise.It enables organizations to quickly and cost effectively deliver business applications in a secure, well-governed and reliable environment that exploits the elasticity of the cloud.

The Independent Platform for Cloud Applications

TIBCO Silver was designed from the ground up to support cloud application delivery for Global 2000 enterprises. What this means to you is TIBCO Silver addresses all your reliability, scalability, and security challenges of cloud computing for the enterprise regardless of the underlying infrastructure.

Scaling to Meet Business SLAs
TIBCO Silver leverages TIBCO's event-driven middleware to sense and respond to changes in application usage.

Bridging the Security Gap
TIBCO Silver provides an agile infrastructure that delivers governance where and when you want it. This means you are in control and it never gets in the way.

Read more...

What Is tibbr?

tibbr™ is the first communication tool specifically built for the workplace that allows the right information to find you.

Unlike social networking applications that focus on the concept of “following people,” tibbr is the first to take an entirely new approach to social computing by allowing you to follow subjects too.

This subject-based approach allows a greater degree of flexibility in what information a user needs and wants to receive at precisely the right time.

Read more...

TIBCO HAWK: About Alert messages

Alert messages originate from a rulebase that implements the monitoring policy or logic. When a specified condition occurs, the agent publishes an alert message to the TIBCO Hawk Display and presents it by colors to show the severity of the alert.

It uses colors such as red for high alert, orange for medium alert, yellow for low alert, cyan if it’s recovering, green if it’s ok and purple for no heartbeat. These colors are default to the Hawk Display but it also allows you to change them based on your own preference.

You can also suspend an alert message that will be temporarily neutralized to prevent it from interfering with other monitoring tasks. If ever a condition ceases, these alerts will be cleared or removed in the Display.

Read more...

TIBCO HAWK: Rulebase scheduling

Rulebase scheduling allows you to create a schedule that defines when a rulebase, rule, test or action is active or not. These schedules can be imposed on the rulebase to control the monitoring activity and performing corrective tasks.

You can define and assign a schedule using the TIBCO Hawk Display, which must be saved on a file so that it can be assigned later on to one or more agents and can be applied to any rulebase objects.In creating a schedule, you can also specify inclusion and exclusion periods. For example, you can set a rulebase to be activated only during office hours and be deactivated during holidays.

Read more...

About hawk rulebases

• Rulebase refers to a collection of rules that controls the monitoring conducted by the agents, which can be created or modified using the rulebase editor in the TIBCO HAWK Display.
• It uses a microagent method as a data source to create one or more tests.
• These tests use If/else construct to check the conditions and includes action if the condition evaluates to true.
• An action, can be sending an alert or notification messages, execute an OS command, creating post condition, or invoking another microgent method.

Read more...

Application Management Interface

Application Management Interface (AMI) is a gateway between the external applications and Hawk System that uses RV Messaging to communicate. It is used as a protocol in instrumenting an application with a management interface that allows the application to be monitored and controlled by exposing internal application methods to the TIBCO Hawk system.

Read more...

Difference between the Hawk Microagent and Application Microagents

Hawk Microagents are default microagents residing on your local machine to monitor system’s health and statistics. Hawk Microagents can be a platform-specific or platform-independent microagent. It means that every platform has its own specific microagent or it has microagents that are default to any platform.

The Application Microagents, on the other hand, are microagents that are specifically created or coded to monitor the application statistics. Only those applications that use AMI are dynamically discovered by the Hawk System and represented by microagents that enables those applications to be managed and monitored.

Read more...

How does TIBCO Hawk agent operates?

The Hawk agent uses microagents as an object to represent and interact with the managed object in your local machine. Then, the agent loads the rulebases as monitoring policies to monitor your system or your applications.

It uses RV Messaging to communicate with the microagents, and uses EMS or RV messaging to communicate with other agents, Event Service and Hawk Display. It also communicates using instances of TIBCO Hawk Display but it works independently with the Display and other agents.

Read more...

Features of TIBCO Hawk Event Service

The TIBCO Hawk Event Service does not only record the activity of TIBCO Hawk agents but it also logs and subscribes to all TIBCO Hawk system events such as agent activation and expiration, microagent and rulebase changes, alerts and clears.

The external applications must be saved on a data file in order for them to access the logs. If ever there is an expired or non-communicating agent in the network, the Event Service provides the use of a user-supplied script to notify the system administrator.

Read more...

About TIBCO Hawk Display

The TIBCO Hawk Display is a local window for all the activities in the network, which provides a graphical user interface used for viewing active agents in the network. It displays container icons that are created for each agent and arranged in clusters. These agent icons are, by default, clustered according to subnets. It also allows you to customize container icons and to convey added information that can be useful for your monitoring. Menus and dialogs are provided for you to create, modify and distribute rulebases to any agent present in the network. You can also invoke a microagent method that allows you to view the results immediately.

Read more...

TIBCO Hawk system architecture

There are two major components that make up the TIBCO Hawk System: Agents and Console Applications.

Agents reside on each computer in the network and perform monitoring and managing duties. It uses rulebases as a monitoring policy and microagents to extract monitoring information and to carry-out specified tasks.

The Console Applications, on the other hand, can be further divided into three subcomponents: the TIBCO Hawk Display that provides the interface to monitor and manage agent behavior in your network, the Event Service that records and logs all the activities of the agent, and the bridges to other management systems.

Read more...

About TIBCO HAWK

TIBCO Hawk is a network monitoring and management software for distributed systems and applications in the enterprise. It is designed using the concept of an independent smart agent that runs on each node in the network to monitor local conditions, so there is no need for a centralized monitoring console or frequent pooling across the network that can consume more bandwidth or cause network traffic.

One of the advantages of using TIBCO Hawk is that it uses less bandwidth while monitoring every machine in the network. It is because TIBCO Hawk distributes the monitoring load to each machine that has locally installed Hawk agents in order to conserve system resources and network bandwidth. The system administrator has now the capability to monitor the operating system, the application parameters and behaviors of each machine in the network using only less bandwidth. Another great advantage of TIBCO Hawk is that, in case of network failure, the Hawk agents will continue to perform local tasks because each agent operates independently from the other.

One of the benefits of using TIBCO Hawk is that it reduces sudden or unexpected system outages and slowdowns. TIBCO Hawk has this capability to automatically repair failures and slowdowns within seconds of detection and it also allows problems to be found and fixed before any slowdowns and failures can occur.

Read more...

Business Process Management( BPM) and its activities

Business Process Management(BPM) is simply the management of your business processes. It is a simple yet a powerful concept that helps you increase the efficiency of your business processes. It is a combination of processes and technology. It improves the execution and monitoring of processes. These processes may involve the tasks between two persons, a person and an application or between two applications.

Activities of BPM:

First is the modeling of business processes. This is where you create a flow of your process. You analyze the sequence and model it based on your working environment. Next is the deployment of your created model. The business process model that you create will be deployed so that it will be ready for execution. After that is, the execution where the process is already being used. The process is in action and users can already interact with the application. The last one is the monitoring and maintenance of the application. Monitoring the output and maintaining the processes are essential to every application.

Read more...

Advantages of iProcess Suite

• It can accept any type of business process flow.
• Simplifies complex business processes.
• Offers full visibility of business flow across the entire enterprise.
• It reduces the time consumed in managing the processes.
• It increases the speed of execution of each process.

Another advantage of using this software is that humans and system tasks work hand in hand. For example, if a certain company orders a large amount of items that costs a large amount of money to an iProcess user company, it is a bit inappropriate for the system to comply with that order automatically, so an authentication of the manager or supervisor is needed first before the compliance of the order. It offers excellent flexibility to business changes. Rules and regulations of a business firm can change anytime. IProcess Suite can easily adjust to these new rules with ease.

Read more...

TIBCO iProcess Conductor

Business processes are prone to unavoidable circumstances that might change how a business process will flow. Because of this complexity, TIBCO iProcess™ Conductoris created. Business applications that are already deployed in the iProcess Engine can dynamically be modified using this tool. There might be inevitable changes that would happen during the runtime of the processes, which need to be taken into account immediately. In that case, this tool is the best choice to do the job.

Read more...

TIBCO iProcess Decisions and TIBCO iProcess Engine

TIBCO iProcess™ Decisions:

Every business is accompanied by business rules. These rules are important and should always be followed. At a certain time, rules in businesses can change. For the management to easily adapt to these new rules, TIBCO iProcess™ Decisions provides us with a spreadsheet user interface that handles these rules. This tool has a user friendly environment that even non-technical personnel can use to modify, test and analyze business rules. It has an excellent flexibility to respond to fast changing business rules.

TIBCO iProcess™ Engine:

TIBCO iProcess™ Engine is responsible for the execution of the business processes. All business models are deployed in this engine. It is the one that makes sure that the processes are running. Users and Administrators are connected to this engine. This engine is also responsible for the cases, tasks and instances created by the users and the administrators.

Experience increase in productivity, save cost and achieve efficient business flow. TIBCO iProcess Suite is a powerful business process management tool that will definitely benefit you and your company.

Read more...

About TIBCO iProcess Client

The TIBCO iProcess Client is the single focal point for defining and managing procedures.

The TIBCO iProcess Client consists of:

• The Work Queue Manager
• The Procedure Manager

The Work Queue Manager displays user's queues and work items and the Procedure Manager displays all of the procedures currently available.

From the Procedure Manager, you can:

• create and edit procedures. The TIBCO iProcess Modeler is started from theTIBCO iProcess Client.
• organize and manage your procedures as a hierarchical structure of procedure libraries, in the same way as, for example, you manage files and directories.

Read more...

Integrate your own custom functions with TIBCO BusinessEvents

TIBCO BusinessEvents allows you to write your own custom functions in Javaand add them to the function registry, making them available from within thefunction registry along with the prepackaged functions in the rule editor.The steps below summarize the tasks required to integrate your own customfunctions with TIBCO BusinessEvents:

1. Write your custom static function in Java and compile it.
2. Create functions.catalog, an XML file that makes it possible to access yourcustom functions from the functions registry within the rule editor. The XMLcan also include information for a tool tip for each function.
3. Create a .jar file that includes your .class file and functions.catalog.
4. Add the location of the .jar file to the class path for the BusinessEventsServer and Workbench. Also add locations for any dependent classes.

Read more...

BusinessEvents: Validating a Decision Table

Validate the decision table before testing or committing it to RMS. To validate,from Table menu, select Validate. If there are any access control violations orsyntax errors in the tables, they are shown in the Problems View tab at the bottomof the application. Take corrective actions and then validate the table again untilall errors are resolved.

NullPointerExceptions are silently ignored when a condition throws such anexception because you passed a null String to a function that does not check fornull, or because you accessed a property of a null contained concept(parent.child.property and child is null).

If a condition table cell is empty, it is skipped and thus considered to be evaluatedas true.

While working on the decision project, you can create multiple virtual rulefunction implementations by creating multiple decision tables. However, before committing the decision project to RMS, you should only commit one decisiontable per virtual rule function. During testing you can have multiple tables so youcan decide which ones to deploy to the engine and test. However, if you commitall implementations, only the last one will take effect if all of them are deployed.

Read more...

BusinessEvents:Importing a Decision Table from a Microsoft Excel File

You can import data from a Microsoft Excel file to create a decision table. For some examples see BE_HOME/DecisionManager/examples/ExcelFiles.

To import data:

1. Open the Decision Project.
2. From File menu, select Import. A browse window is displayed.
3. Click Browse to select the Microsoft Excel file to import, and name your decision table.
4. Select the virtual rule function you want to implement with your decision table, and click OK.The data imported from the Microsoft Excel file is saved to the decision table and you can continue modifying the data or add new data.

For custom conditions, and custom actions to be imported from Excel, mark the header names as "CustomCondition" and "CustomAction" respectively.

Read more...

BusinessEvents: Working with Decision Tables

• Click Add to add rows. Enter the data in the new cells or drag and drop the properties form Argument Explorer.
• Click Fit Content to resize the columns so they fit around the text.
• You can search for certain values by entering text in the Search field.
• Click Show Text button to see the contents of the cell, instead of just the values you are comparing with for the attributes you have dragged to the condition and action areas.
• Drag and drop the catalog functions you see collapsed by default on the right side of the application. Drag and drop them to the function area (marked by the ) or to the cell you are editing. For example, if you want to compare some attribute that is of type integer against the rounded value of "39.99", you could say in one of your conditions "< Math.round(39.99)" by dragging and dropping the Math round function from the Standard Functions
  window and then entering the arguments of that function.
• Right-click on the condition area on the properties you dragged there to take a few actions relating to the column you have clicked on. For example, you can move the column, remove it, or change other field settings.
• Click on the drop-down menu on the properties dragged to either the condition or the action area to filter out which rows to show based on the values. For example, if you want to see just the Account.AccountType where AccountType is "current" and you want to filter out all the other rows that do not have this value, select the "current" value from the drop-down list that will show you all the values you have entered so far in that column.
• Click Remove to delete rows. If you add more rows after this operation, the row IDs are not reused.
• Right-click on column headers and choose Remove to delete any conditions or actions from the table. You cannot remove the last condition column because a minimum of one condition column must exist if you have any action columns. When you remove columns, certain rows may also get merged if they now share the same values in their condition cells. If this happens, if you have non-custom actions and the rows have the same priority, the last row to be merged will have its actions be merged and the others deleted.
• Select Table > Show Property, to see meta-data of the entire decision table. You can only modify the effective date and the expiration date.

Read more...

BusinessEvents: Creating a Decision Table

After successfully logging in to the application, some menu options are enabled depending on the roles that your account belongs to User Roles.

When a business user logs in to the Decision Manager application, the following menu options are enabled:

• Project > Checkout/Update/Commit/Show Status
• File > New/Open/Logout/Exit
• Edit > Select All
• Access menu if you also have the RULE_ADMINISTATOR role

As a business user, you can use Decision Manager to create Decision Tables.To Create a Decision Table

1. Open a decision project.
2. From File menu, select New > Decision Table Rule Function, and choose a name for the Decision Table.
3. Select a Virtual Rule Function that you want to implement from the Project Explorer.
4. Click OK.The arguments of the virtual rule function you are implementing are shown in theArgument Explorer view. Expand the Entities (concepts and events) to see theirproperties from Argument Explorer.
5. Decide on which properties you want to use to make a decision table. Drag and drop those properties onto the Condition or Action area.For example, if the arguments are two concepts called BankUser and Application,you can decide to accept the Application based on a users's age and credit score.In this case, drag and drop BankUser's "age" and BankUser's "creditScore"attributes from the Argument Explorer view to the condition area of the decisiontable. Then, you drag and drop the Application's "status" attribute to the Actionarea.
6. When you are done creating the decision table, click File > Save.

• If two rows end up with the same conditions after you make modifications, they will get merged into one row. All actions will also be merged.
• It is invalid to provide a string property value that starts with an integer (such as "12hello" unless you specifically wrap the value around double quotes.
• Blank cells, or cells that have a * in them, as well as disabled cells are all ignored and automatically treated as true.

Read more...

TIBCO BusinessEvents Resources

Access control is enforced for the TIBCO BusinessEvents resources. There are twotypes of access control modes:

• BusinessEvents Resource: This mode is used for populating the Project Explorer view in Decision Manager. BusinessEvents Resource mode is the default mode.


• Domain Model: This model is used for enforcing the Access Control in domain model editor.

The following allows you to create a new domain model entry for any resource which matches the ID AllP.

Read more...

BusinessEvents: Access Control System Overview

The Access Control System manages the permissions to the users based on their roles. Using the access control system, the IT Administrator can restrict business users from accessing or modifying certain resources of a Decision Project.

Access control is role based. Thus, the users belonging to same role will have same access permissions. One user can play different roles in an organization, so the user's permissions are a unification of the permissions that each role the user belongs to gets.

By default, all permissions are denied. Each of the permissions must be grantedexplicitly. Permissions do not have hierarchies. The order in which permissionsare specified is irrelevant.

A role can have zero or more permissions. Each role is represented by a name.A Permission can have one Action and a resource for which the action applies. For example, an action could be Read, Write, or Send. A resource or entity could be arule, attribute, and so on. For example, you could specify Read permission for allattributes of a particular concept.

All of these ACL settings are specified in the

%rms.proejct.location%/%rms.project.name%/config/%rms.project.name

%.acl file as specified in the be-rms.tra file.

Read more...

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...

BusinessEvents: About Rules Management Server

The lightweight Rules Management Server (RMS), a product of TIBCOBusinessEvents family, serves as a rules management repository. RMS is builtusing TIBCO BusinessEvents itself. Decision Manager communicates with this server to retrieve rules and other artifacts, get updates, commit them, approve orreject those rules, and deploy them to a production system. Only one decision project can be made available to the users per RMS instance. RMS allows you to:

• Authenticate against an LDAP or file-based system
• Access to certain parts of a project depending on your user role
• Checkout a project
• Get updates to that project
• Commit your project
• See the status of your project

If you have logged in to RMS as a Rule Administrator, it allows you to:

• Set up projects with domain models and test data pre-defined, as well as set project security policies
• Approve or reject committed projects and give feedback to the business users
• Check on the status of all projects committed and keep track of all project versions
• Deploy approved rules to a running TIBCO BusinessEvents engine of your choice

The RMS is implemented using TIBCO BusinessEvents. It contains a statemachine, rules, events, and catalog functions. The TIBCO Designer source code to this implementation is provided in the distribution in the BE_HOME/rms/projectdirectory. If you wish to customize the default behavior, you modify this project.

Read more...

TIBCO BusinessEvents: About Decision Manager

Decision Manager, a component in the BusinessEvents family, is an Eclipse-based Rich Client Platform (RCP) application. Its friendly user interface allows business personnel with little or no technical background to author, test, and deploy rules to the BusinessEvents engine. It simplifies complex rules by breaking them into multiple simple rules. Each simple rule is represented by a row in a decision table. It also provides IT personnel an easy, secure, and scripted deployment lifecycle by exposing an extensible Rules Management System.

Different users can use this application differently. Users include:

• Business User
• Developer
• Rule Administrator

The business user uses this application to write, test, and maintain decisions without having to know the underlying technical details or writing code. The business user can drag and drop the properties of entities (concepts and events) to create decision logic and simulate the rules, without understanding the rule language. Developers use this application to define, modify, and deploy the configuration of a rule system, with minimal supervision and minimal implementation overhead.

In the Decision Manager application, Decision Table is an interface with rows and columns for a business user to capture threshold values and business rules in a tabular format.

The Decision Manager application enables business users to easily create simple BusinessEvents rules using the decision table feature. A decision table is a user interface with rows and columns.

Decision Tables are used to provide an implementation to Virtual Rule Functions created in TIBCO Designer. In TIBCO Designer, you cannot set the Output Argument or Return type of Virtual Rule Function. The virtual rule functions by definition have no implementation and if invoked from a rule without one will throw an exception. Thus, a decision table can be used to provide implementations to such virtual rule functions.

Read more...