Creating Archive Scaling Rules

You can define stacks that add or remove component archives based on archive statistics that are monitored for triggering conditions.

1. After adding components to your stack you can create new scaling rules by opening the Archive Scaling tab and clicking on Create New.
2. Name your new archive scaling rule and give it a description to help you and others quickly identify the purpose and content of your archive scaling rule.
3. Use the Archives tab to define what archive is to be added or removed according to the rules you define in the other tabs. Click Add icon at the right of the column heading row to add one or more archives (process instances) to be scaled up or down in your stack.
   Creating a new Archive Scaling Rule

   
4. Select the BusinessWorks component that was used to upload the application archive file and use the Archive Names field to specify what archive will be subject to the rules you set using the other tabs of the Archive Scaling Rule Editor.
5. Use the Add Archive Conditions tab and click the Add icon to the right of the column heading row to create and define a new Add Archive rule.
6. Select the statistics, the operator, the value, and the sampling window period in seconds to define your condition for adding a new archive.
   Note: The sampling window must be a sufficiently large time period (in seconds) to allow aggregated statistics to be collected. If the sampling window is not big enough, there is a chance that no statistics will be reported in a particular time-frame creating an inadvertent trigger condition.

   By default allocation statistics like "Expected Engine Count", "Client Count", "Allocating Engine Count", and "Actual Engine Count" are collected every 60 seconds and by default component statistics are collected every 10 seconds.

   You can define more than one rule. With more than one rule, set the Satisfies field to specify whether all rules must be satisfied or whether any one rule can be satisfied to trigger addition of a new archive instance.

   Define Archive Scaling Rule conditions

   

   Optionally you can set a preference for running new archives or new process instances on component instances with favorable usage profiles. Select the statistic that is most relevant to your implementation and you can create new process instances there according to those conditions you defined.

7. Use the Remove Archive Conditions tab to release computing resources and remove unused or idle component archives or process instances to scale down your component archives just as you scaled them up according to conditions you define on usage statistics.
8. Use the Target Component Conditions tab allows you to restrict the start of new archive instances to those machines that have the same set of resources that you choose. Set a rule or several rules with statistics, operators, and values as you would on the Add Archive Conditions tab and further restrict where the new Archive instances can start depending on component instances that have:

   Same Component

   This setting works for all component archive scaling.

   From the set of Components

   This setting works only if your component archive is compatible with the set of components present. For example a BusinessWorks archive can scale on a product adapter component.

   Same Component Type

   The process archive has the possibility of being scaled up on different versions of the product

   Same Enabler

   Components that require the same specific enabler should use this option.

   Same Middleware Version

   This selection ensures that the component archive runs on machines with the appropriate middle ware: TIBCO BusinessWorks, TIBCO TRA, TIBCO Hawk, etc.

   Same Enabler and Middleware Version

   This selection ensures that your component archive scales up successfully, but it is the least restrictive of the target component conditions.

   Tip: Only From the Same Set of Components or Same Enabler and Same Middleware Version works 100% of the time.

   Provided that the component archive has the proper component type, TIBCO Silver Fabric can usually find the correct computing environment for scaling up. For example, for a BusinessWorks component archive, a selection of the "Same Component Type" ensures that the Silver Fabric Broker tries and finds an engine with same BusinessWorks component type on which to run a new BusinessWorks component archive.