When a stack is published and 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 BusinessWorks Application instantiated on the engine.
Making changes to the stack is as easy as editing, saving, and publishing those changes to any instances that are 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
-
After making any changes to a stack,
Save the changes
-
Select
Publish Changes
from the Actions list in the main stack page.The specified engines are affected by the changes immediately
If you want to change a BusinessWorks component, you do not need to stop and restart your entire stack. If you want to deploy, start, stop, and undeploy Business Works project archives here are a couple of ways to accomplish that:
- Micro-scaling - Start and stop BusinessWorks 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 BusinessWorks endpoints) - publish (deploy), unpublish (undeploy), start, or stop BusinessWorks archives without having to change any stacks, components, or BusinessWorks engines. Deploying BusinessWorks application archives via REST and cURL commands is described in the next section.
Copyright © Cloud Software Group, Inc. All rights reserved.
