Talos from Tech Data is used by customers around the world to automate the configuration of middleware across software development environments, from the sand box right through to production. Thanks to the Technical Architects at CROZ, Talos functionality has been extended to include IBM’s Business Process Manager (BPM) software.
All businesses will have a defined and agreed way of working, a process. The more efficient and effective the process the more agile the organization can be. By combining technology and knowhow, organizations can use IBM BPM to enhance the way they design, automate, implement, measure and improve their business processes. IBM BPM itself is an integrated platform consisting of tooling and run time for executing processes within the platform. It is specifically designed to enable process owners and business users to engage directly in the improvement of their human and machine driven business processes. BPM can help an organization become more agile and flexible in a number of ways, such as increased productivity, speed to market, or achieving compliance with complex corporate governance requirements. BPM is a highly sophisticated middleware suite running on top of WebSphere Application Server and supported by a CROZ-developed Talos toolkit for middleware configuration management.
Getting started with the BPM toolkit is a simple and straightforward process
Just like the WebSphere Application Server (WAS) toolkit, using the BPM toolkit users are able to quickly discover existing, highly-complex BPM topologies, including support for large deployment environments. With the BPM toolkit, you will now read in both the underlying WAS configuration as well as BPM-specific configuration data, including BPM process application data.
Building on top of functionality provided by the WAS toolkit, users have the same high-quality templating support they have come to expect from Talos. In addition to WAS configuration data, BPM application data can also be templated. This is essential for the export and import functionality to properly configure your BPM applications.
If the use case is a migration, upgrade, or otherwise moving BPM from one place to another, once a template has been completed, a payload should be created, and BPM applications to be moved should be exported from the Process Centre. Upon running the install command, the exported zip file containing the process applications is copied to the target system. This can all be automated using one of the available Talos-supported orchestration engines, such as IBM UrbanCode Deploy or Jenkins.
To complete the migration of the BPM process applications on the target environment, the BPM-template payload is applied and BPM process applications are installed and imported. Once data source connections are sorted out, the new environment is ready for usage. Once again, by using an orchestration engine the entire process can be refined to an easily understood series of tasks to help you achieve your IBM BPM administration goals.
By using these simple building blocks, you can design and execute processes to allow you to quickly, easily, and without error manage multiple BPM environments, migrating applications as needed.
DevOps is obviously a buzzword du jour, and Talos delivers in spades, but now you can bring that proven track record to your BPM infrastructure as well. The benefits of DevOps-style automation can now be realized for your enterprise BPM needs with Tech Data’s Talos. With Talos and the CROZ-developed BPM toolkit, formerly complex BPM work becomes routine, automated, and auditable tasks.