Introduction

Copyright © Cloud Software Group, Inc. All Rights Reserved

Chapter 7 Phase 5: Deployment : Introduction

Introduction

When you have completed and tested the first prototype of your integration project in the development environment, you are ready to deploy it to a testing environment.

In a traditional business integration project, domain configuration is a labor-intensive process that is likely to require multiple iterations before all components are in place. The administrator must tweak the configuration files for different components on different machines. To optimize the configuration, administrator must manually keep a record of the different configurations that were tested.

TIBCO ActiveMatrix BusinessWorks, in contrast, allows you to use the TIBCO Administrator GUI to create a deployment configuration and then deploy the project.

•

You use the TIBCO Designer GUI to create an Enterprise Archive file (EAR file) containing the adapter configurations and process definitions you wish to deploy.

•

TIBCO Administrator uses the EAR file when creating the deployment configuration.

•

You can deploy the project in TIBCO Administrator and the necessary scripts and other information is sent to the machines within the deployment.

TIBCO ActiveMatrix BusinessWorks Project Phases

When process design is complete and all testing from the TIBCO Designer GUI results in success, the project is ready for deployment.

The illustration below shows how a project moves through the development and deployment phases.

Figure 23 Project development phases

1.

Using TIBCO Designer, the developer configures adapter services and saves the project with configured adapters. Different adapters could potentially be configured by different developers and included in one project.

2.

Using TIBCO Designer, the developer configures activities for the business process(es) and saves the project, which now includes process definition(s).

3.

The built-in test mode is used for preliminary testing and debugging of the business process(es).

4.

Using TIBCO Designer, the developer prepares the Enterprise Archive File (EAR file) by creating Enterprise Archives containing the desired adapter configurations and process definitions.

At this stage, the developer moves from the TIBCO Designer development GUI to the TIBCO Administrator run-time GUI and performs these tasks:

1.

From the TIBCO Administrator GUI, the deployment configuration is created and deployed. The TIBCO Administration Server sends all necessary information to the individual machines. All components now become visible in the TIBCO Administrator GUI (but are not started).

2.

From the TIBCO Administrator GUI, the developer starts each component (adapter and process engine). As a result, all process starters are waiting for the events that cause them to create process instances.

3.

Each time an event arrives that triggers a process starter, the TIBCO ActiveMatrix BusinessWorks engine creates a process instance, which uses the associated process definition to process the incoming data.

4.

Using the TIBCO Administrator GUI, the developer can monitor the different processes running on the different machines.

If appropriate, the project can be modified and saved from TIBCO Designer. In that case, you must create a new EAR file and place the new file into the deployment configuration. You must then stop and restart the desired deployment for the changes to take effect.

For more information about creating EAR files and deployment configurations, see TIBCO ActiveMatrix BusinessWorks Administration.