Continuous Deployment - Deploying Archives Directly to Endpoints

In some situations, deploying archives directly to a running TIBCO BusinessEvents component can be useful, such as when an archive needs to be deployed and run on a system that is already running. This is known as continuous deployment.

Archives can be directly deployed to BusinessEvents instances already running on Silver Fabric engines using the commandline interface (CLI), Silver Fabric API, or an HTTP REST command sent using cURL or a Java client. Refer to the TIBCO Silver Fabric Cloud Administration Guide for more information on the CLI or the Silver Fabric API. Archive deployment, undeployment, starting, and stopping application archives through REST are described in further detail here.

TIBCO Silver Fabric supports many HTTP REST commands to GET, PUT, POST, and DELETE objects and managed resources for use with archive scaling, brokers, components, daemons, enablers, gridlibs, schedules, stacks, and Skyway.

Tip: TIBCO Silver Fabric REST Services are documented in the TIBCO Silver Fabric Administration Tool at Admin > REST Services. They are grouped by resource. Click any method name to see possible parameters if any and example responses.

Continuous deployment is discussed in the section "Deploying Archives Directly to Components" in the TIBCO Silver Fabric Administration Guide.

Prior to using REST CLI with TIBCO Silver Fabric 5.6, you must change the Strict Validation setting at Config > Broker > General to "false".

The TIBCO Silver Fabric Enabler for BusinessEvents adds more REST methods to enable control of BusinessEvents archives.