Updating the Stack

When a stack is published and is running, you can still make changes to the stack such as adding other components, changing allocation rules, changing threshold activation rules, or deploying and starting archives on the runtime BusinessEvents Application instantiated on the engine.

Making changes to the stack is as easy as editing, saving, and publishing those changes to any instances that might be running. Some changes might require restart of the changed resource, so consult the TIBCO Silver Fabric documentation for best practices prior to making changes to a production system.

Procedure

  1. After making any changes to a stack, save the changes and then from the Actions list in the main stack page, select Publish Changes. The specified engines are affected by the changes immediately.
  2. If you want to change a BusinessEvents component, do not stop and restart your entire stack. If you want to either deploy, start, stop, or undeploy Business Events project archives here are a couple of ways to accomplish that:
    • Micro-scaling: Start and stop BusinessEvents archives based on your defined rules when they are already in your component. For more information refer to: Creating Archive Scaling Rules.
    • Continuous Deployment (deploy archives directly to BusinessEvents endpoints) - publish (deploy), unpublish (undeploy), start, or stop BusinessEvents archives without having to change any stacks, components, or BusinessEvents engines. Deploying BusinessEvents application archives through REST and cURL commands is described in the next section.