
This post is from the XebiaLabs blog and has not been updated since the original publish date.
XL Deploy plugin for Tibco BusinessWorks
The Tibco Business Works plug-in manages the deployment of Business Works applications, application configuration as well as EMS Server artefacts such as queues and topics. The plugin leverages AppManager standard commands in order to create, update and delete Tibco BW and EMS components and eliminates the tedious scripts generally used to perform variable substitutions.
Use XL Deploy to create insight in what version of each application has been deployed onto the different stages of your DTAP pipeline. Deploying the same application package to every stage in your DTAP pipeline greatly contributes to the stability and predictability of the result of a deployment.
Use XL Deploy to define the different components such as your Tibco BW Engine (tibco.Domain hereunder) processes and EMS servers, two pieces of Tibco middleware involved in a typical Business Works setup. From an application perspective, define the various components of your Tibco application such as EARs, EAR configuration files, queues, topics and other EMS scripts.
Variable substitutions for these different artefacts will be performed automatically with XL Deploy standard dictionaries, allowing environment-specific configuration.
[caption id="attachment_7639" align="alignright" width="289"] Tibco Application[/caption]
[caption id="attachment_7638" align="alignleft" width="300"]
Tibco Infrastructure[/caption]
[caption id="attachment_7640" align="aligncenter" width="281"]
Tibco Deployment[/caption]
As the plugin capture Tibco BW best-practices for the deployment of Tibco artifacts, XL Deploy will automatically sequence the deployment operations in the correct order. For example, a package composed of EARs, queues and topics, will typically produce a deployment sequence based on the following:
- Deploy queues
- Deploy topics
- Deploy EARs in nostart mode
- Configure EARs
- Start EARs
- Deploy and update of BW applications and associated configuration
- Deploy and update EMS resources (queues, topics)
- Deploy and execute EMS scripts
- Direct deployment of EMS configuration files with EMS restart
- Deployment of Catalog definitions
More from the Blog
View more

Discover the change management practices that are ripe for optimization

Reckoning DevOps’ role in the enterprise value stream
