Setting the Dependency Requirements

Each TIBCO BusinessEvents component, unless its used in standalone mode, has component dependency set on one TIBCO Administrator component or TIBCO Enterprise Administrator component. You can set this component dependency for each of your TIBCO BusinessEvents components. Those components without defined component dependencies do not have enough information for proper publishing.

The TIBCO BusinessEvents component can have the TIBCO Administrator or TIBCO Enterprise Administrator component configuration information so that it can publish, unpublish, and communicate with other components (if required) successfully. A connection is supported between the TIBCO BusinessEvents component and one instance of the TIBCO Administrator component or TIBCO Enterprise Administrator component. Connecting with more than one TIBCO Administrator component or TIBCO Enterprise Administrator component is not supported. After setting the dependency, TIBCO BusinessEvents starts after TIBCO Administrator or TIBCO Enterprise Administrator starts running.

Procedure

  1. During creation or during edit of the TIBCO BusinessEvents component, select "Add/edit default rule settings" from the menu of the component wizard.
  2. Use the Add Rule pull-down list to select the Component Dependency option.
    Setting Component Dependency
  3. From the Reference Component drop-down list, select the name of the TIBCO Administrato or TIBCO Enterprise Administrator component that runs inside your stack.
    Shutdown Dependency
    If you run TIBCO Administrator in the Fault Tolerant mode, clear the Shutdown Dependency check box. Otherwise, all BusinessEvents components can stop if TIBCO Administrator stops working.
    Ordered Shutdown
    It 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, the order of the 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 want to manually restart components later to propagate changes, leave this box cleared.

    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 the TIBCO EMS Server component.

    Pack by Host
    Select this to specify that dependent components must run on the same host.

    For more information on these settings refer, TIBCO Silver Fabric User’s Guide