Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 2 Creating a TIBCO Silver Fabric Enabler for TIBCO Administrator Stack : Creating a Stack

Creating a Stack
Components can be deployed independently in an Ad Hoc stack. More commonly they need to be deployed with other components in a stack with dependencies and other controls.
For example TIBCO ActiveMatrix BusinessWorks 5.x components depend upon an instance of the TIBCO Administrator component, and both can be present in a stack to work together.
Any number of components could be included in your stack depending on your implementation. You can publish multiple components as one unit to the same Silver Fabric Engine or you may publish components to a Silver Fabric Cloud.
Each TIBCO_DOMAIN can have one stack, but each stack can have multiple components such as multiple TIBCO ActiveMatrix BusinessWorks components. After initially defining a stack, you can still update it by adding or removing components.
To create a TIBCO Silver Fabric Enabler for TIBCO Administrator stack:
1.
2.
Click the Create New Stack button as shown in Figure 22.
Figure 22 Creating a Stack
3.
4.
5.
6.
7.
Figure 23 Stack Builder page - Adding a Component Dependency
Stack Dependency Requirements for use with BusinessWorks 5.x
TIBCO ActiveMatrix BusinessWorks components created using a 5.x Distribution must have a component dependency set on one TIBCO Administrator component you define. Users of BusinessWorks 5.x components must set this component dependency for each of their BusinessWorks 5.x components or those components without it will not have enough information for proper deployment.
A connection is supported between a BusinessWorks 5.x component and one instance of the TIBCO Administrator component. After setting the dependency, TIBCO BusinessWorks starts after TIBCO Administrator is up and running.
To set dependency, follow these steps:
1.
2.
3.
Use the Add Rule pull down to select the Component Dependency option.
Figure 24 Setting a Dependency on the Administrator Component
4.
In the "Reference Component" field, select the name of the TIBCO Administrator component that runs inside your stack.
Shutdown Dependency - If you run TIBCO Administrator in the Fault Tolerant mode, uncheck the Shutdown Dependency checkbox. Otherwise, all BusinessWorks components stop if TIBCO Administrator stops working.
Ordered Shutdown provides for a logical, sequential shutdown so that dependent components are shut down first. Ordered shutdown is especially important when the domain is hosted using a file structure instead of a dependent database. When you have an Administrative component that uses an external database, order of shutdown is less important.
Restart Component for new rules - If new rules are defined for a component that has already been deployed, it must be restarted for the new changes to be applied. If you wish to manually restart components later to propagate changes leave this box unchecked.
If the Administrator component was configured to "Use dependent EMS server" then that dependency must be set here as well.
Pack by Host - Check this to specify that dependent components must run on the same host.
The TIBCO Silver Fabric User’s Guide has more information on all of these settings.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved