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


Chapter 2 Creating a TIBCO Silver Fabric Enabler for ActiveMatrix Service Grid Stack : Creating a Stack

Creating a Stack
Components are published from within a Stack. Any number of Components could be included in your Stack depending on your implementation, but at the minimum, a Service Grid Stack must have a TIBCO ActiveMatrix Administrator Component and an instance of the TIBCO ActiveMatrix Runtime Component. TIBCO ActiveMatrix Runtime component(s) depend upon an instance of the TIBCO ActiveMatrix Administrator Component.
Once you have created Components, you can create a Stack so they will be published to a Silver Fabric Engine as a unit.
After initially defining a Stack, you can still update it by adding or removing Service Grid Components, but if you have set Deployment Persistence to true then any changes you make will not be propagated to the instances that are persistent and protected.
To create a TIBCO Silver Fabric Enabler for ActiveMatrix Service Grid Stack:
1.
In the TIBCO Silver® Fabric Administration Tool, select Stacks > Stacks.
2.
Click the Create New Stack button.
3.
4.
5.
Figure 24 Stack Builder page - Adding a Component Dependency
Dependency Requirements
Each Service Grid Component, must have a component dependency set on one TIBCO ActiveMatrix Administrator Component. You must set this Component Dependency for each of your Service Grid Components or those components without it will not have enough information for proper publishing.
The Component must have the TIBCO ActiveMatrix Administrator configuration information so that it may publish, unpublish, and communicate with other components successfully. A connection is supported between a Component and one instance of the TIBCO ActiveMatrix Administrator Component. Connecting with more than one TIBCO ActiveMatrix Administrator Component is not supported. After setting the dependency, the component will start after TIBCO ActiveMatrix Administrator is up and running.
To set that dependency, follow these steps:
1.
During creation or during edit of the Component, select "Add/edit default rule settings" from the Menu of the Component Wizard.
2.
Use the Add Rule pull down to select the Component Dependency option.
Figure 25 Setting a Dependency on the Administrator Component
In the "Reference Component" field, select the name of the TIBCO ActiveMatrix Administrator Component that runs inside your Stack.
Shutdown Dependency - Because TIBCO ActiveMatrix Administrator does not support the Fault Tolerant mode this setting will not apply.
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 on a dependent database. When you have an ActiveMatrix 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 published, 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 ActiveMatrix Administrator Component was configured to "Use dependent EMS server" then that dependency must be set here as well.
When using a dependent TIBCO Enterprise Message Service server, the dependency should be set in the TIBCO ActiveMatrix Administrator Component, which must also have a dependency on TIBCO EMS Server Component.
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.
 
 
Publish the Stack
Refer to the TIBCO Silver Fabric User’s Guide for information on publishing and managing Stacks.
 
Configuring for Failover - Replicating TIBCO ActiveMatrix Runtime Hosts
TIBCO ActiveMatrix Runtime Hosts can be configured to provide failover replication from one TIBCO Silver Fabric Engine to another to provide a secure transition from an unresponsive host machine. Configure the Components, Stack and Engines with the following settings to be prepared to move TIBCO ActiveMatrix Runtime Hosts from one machine to another using the same TIBCO_HOME:
a.
b.
c.
For example if the shared drive were /mnt/shared and the ActiveMatrix Administrator component was called MyAMXComponent, name the shared path: /mnt/shared/MyAMXComponent
TIBCO_Home would be in the directory: /mnt/shared/MyAMXComponent/<TIBCO_HOME>
ConfigHome would be in the directory: /mnt/shared/MyAMXComponent/<ConfigHome>
d.
e.
TIBCO ActiveMatrix Service Grid Runtime Hosts are monitored and polled by TIBCO Administrator and any prolonged response failure will first trigger attempts to re-establish a connection, if that fails the component will be restarted, and if that fails the TIBCO ActiveMatrix runtime host will be replicated and started on a different preferred host.

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