Dependency Requirements

For 5.x Version

Each BusinessWorks component, must have a component dependency set on one TIBCO Administrator component. You must set this component dependency for each of your BusinessWorks components or those components without it will not have enough information for proper deployment.

The BusinessWorks™ component must have the TIBCO Administrator configuration information so that it may publish, undeploy, and communicate with other components (if required) successfully. A connection is supported between a BusinessWorks™ component and one instance of the TIBCO Administrator component - connecting with more than one TIBCO Administrator component is not supported. After setting the dependency, TIBCO BusinessWorks will start after TIBCO Administrator is up and running.

For 6.x Version

If one component requires that another component is running and active before it is started a component dependency must be set to ensure that the dependency is present prior to activation.

For example, a TIBCO ActiveMatrix BusinessWorks component connects with a TIBCO Enterprise Administrator (TEA) component so that it can be monitored and managed. The TIBCO ActiveMatrix BusinessWorks component must have a component dependency set on the TEA component because this connection is established when they are first published and run on TIBCO Silver Fabric.

TIBCO ActiveMatrix BusinessWorks (with bwagent set to run as Client), a BW Client component, must have a dependency set to connect with the only BusinessWorks server component in the stack. The BW Client components can then use the domain created by BW server component.