Run-Time Architecture

When the integration project is deployed, the different process engines and adapters are ready to run on the machines in the TIBCO administration domain.

You deploy your project and start each component individually from the TIBCO Administrator GUI. After all adapters and process engines have been started, process instances are created by process starters. A process starter could be, for example, a File Poller or an Adapter Subscriber activity waiting for incoming data. When data arrives, the process starter creates a process instance using the process definition to which it belongs, and the activities in the process are executed in sequence.

In Process instances created from a process definition, a JMS Queue Receiver activity creates an instance of the process definition to which it belongs each time it receives input.

Figure 19: Process instances created from a process definition

While different process instances are running, any alerts that were scheduled during deployment configuration are sent to the specified recipient by the TIBCO Administration server. In addition, the TIBCO Administrator GUI allows monitoring of the running project at different levels of detail, and can collect tracing information for later analysis.

For the example discussed in this manual, the process engine could perform these tasks:

  • Receive data from an application server via JMS, data from a PeopleSoft Order Management System via the appropriate adapter, and data from a shipping service via SOAP.

  • Enter data into a PeopleSoft Order Management system and data into a Siebel customer service system via the appropriate adapters.

  • Send certain orders out for credit approval and receive approval or refusal.

All components are monitored and managed by way of TIBCO Administrator, which also provides security and repository management. Users can access TIBCO Administrator using the TIBCO Administrator GUI.

Figure 20: Example scenario data flow