Continuous Deployment Life Cycle
The continuous deployment life cycle has four REST operations that may be executed using cURL methods.
- Deploy
- Send an archive to a Silver Fabric Engine running an Adapter for Files (Unix/Win) Component that meets the criteria specified. The Deploy REST method enables specification of a properties files with criteria dictating where and how the archive should be deployed.
- Start
- Start an archive that was deployed to an Engine.
- Stop
- Stop an archive that is running on an Engine.
- Undeploy
- Undeploy an archive from an Engine, stopping any running instances of that archive on that Engine.
- Deploy
Adapter for Files (Unix/Win) application archives may be deployed directly to an appropriate Silver Fabric Engine (TIBCO Logical Machine) by calling the REST method. - Deployment File
When deploying an archive by REST you must include a deployment file, which will specify at least one selection criteria for determining which Engine and Component will receive the deployed archive. - Continuous Deployment Timeout
Continuous deployment transfers can timeout due to one or more factors. - Start
Using REST you can also start application archives that were deployed but not started. You must know the Engine-Id, Engine-Instance, and the full application ArchiveName. - Stop
You can stop application archives that are running on an Engine by REST method by submitting a cURL expression to the Silver Fabric Broker. You must know the Engine-Id, Engine-Instance, and the full application ArchiveName. - Undeploy
You can undeploy application archives that are running on an Engine by REST method by submitting a cURL expression to the Silver Fabric Broker. You must know the Engine-Id, Engine-Instance, and the full application ArchiveName.
Copyright © Cloud Software Group, Inc. All rights reserved.