Setting Dependency Requirements

For each Adapter for Files Component, you must set dependency on the TIBCO Administrator Component.

1. During creation or edit of the Stack select Add/edit default rule settings from the Menu of the Component Wizard.
2. Use the Add a Rule pull down to select the Component Dependency option.
   Setting an Administrator Component Dependency

   

   In this way, the component knows all TIBCO Administrator configuration information. After setting the dependency, TIBCO Adapter for Files will start after TIBCO Administrator is up and running.

3. In the "Depend On" Reference Component field, select the name of the TIBCO Administrator Component that runs inside your Stack.
   Note: If you run TIBCO Administrator in the Fault Tolerant mode, uncheck the Shutdown Dependency checkbox. Otherwise, all Adapter for Files Components will stop if TIBCO Administrator stops working.

   If the 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 Administrator Component, which must also have a dependency on TIBCO EMS Server Component.

   It is recommended that you check Ordered Shutdown to close dependent components when the TIBCO Administrator is shut down.

   • Shutdown Dependency establishes a requirement for the parent, specified in the Depend on field, to be active to keep the dependent component running.

     When selected the stack stops component dependencies if the parent component becomes unresponsive.

     If you run TIBCO Administrator in the Fault Tolerant mode, clear the Shutdown Dependency check box. Otherwise, all Adapter for Files components will 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 cleared.
   • Pack by Host: Check the check box 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.

4. Save and Run your stack.