Copyright © Cloud Software Group, Inc. All Rights Reserved

Phase 2: Domain Setup and Installation

A TIBCO administration domain is the set of software and hardware resources used by your integration project. See TIBCO Administration Domain for an overview.

This section gives an overview of planning the administration domain setup and installing the components.

Domain setup is different during development and during deployment testing and production. • During development, each developer may install an Administration Server and set up an administration domain on their machine and develop and test the project there. • During deployment testing and production, one TIBCO Administration Server manages the project and the ACL (Access Control List). Only authorized users can create and save projects or start and stop processes.

Planning the Domain

When you install a TIBCO ActiveMatrix ¹BusinessWorks component, you must specify the administration domain to which a machine belongs. Before installing the software, you should therefore determine what resources should belong to a administration domain. Ask yourself these questions:

•	For development environments, do I need to share work with other developers? If so, all machines that need to share work should be part of the same administration domain. If not, this machine can have its own administration domain.

•	What machines do I need to run my project? By default, all machines within an administration domain are expected to be in the same network subnet. You can, however, set up your system to use TIBCO Rendezvous rvrd and can then use TIBCO ActiveMatrix BusinessWorks across subnets.

•	Which components (adapters or process engines) should run on which machine?

•	Where should I run my TIBCO Administration Server?

•	Who are the users that need to make changes to the project? For which component does each user need to make changes (e.g. start or stop an adapter)?

•	Who are the users that need to view information about the running project? Which component(s) does each user need to view?

•	How will the project handle load balancing and fail-over?

The illustration below shows a possible administration domain setup for the example scenario:

•	The TIBCO Administration Server runs on machine 1.

•	The PeopleSoft and Siebel adapters run on machine 2.

•	The process engine runs on machine 3.

•	The PeopleSoft and Siebel systems run outside the administration domain.

Figure 14 Domain setup for example program

Installing Components

A flexible installer allows you to install one or more components on each machine following these steps:

1.	Install TIBCO Runtime Agent (TRA) on each machine in your domain.

2.	Install the TIBCO Administration Server and specify the administration domain name, and the administration user and password.

3.	Install other TIBCO ActiveMatrix BusinessWorks process engine(s) into the administration domain.

4.	Install adapters into the administration domain.

---

1

 

Copyright © Cloud Software Group, Inc. All Rights Reserved