WebSphere deployment automation with uDeploy
Overview
Download
- uDeploy Overview
- uDeploy 4.8
- Product Tour
- Features
- Screenshots
- Technology
- Integrations
- Scenarios
- Data Sheet
-
Blueprint
-
Product Demo
-
Blueprint
-
Product Demo
Integrations
uDeploy has over 75 out-of-the-box integrations with leading third-party systems. The integrations were written with one goal in mind: helping you derive value faster with
less work.
uDeploy integrates with a number of Java Application servers including JBoss, Tomcat, Weblogic, WebSphere and others. A typical integration provides steps for stopping a server or application, deploying new code, updating configuration, and restarting.
uDeploy is at home in Microsoft shops. The integration with IIS provides steps for deploying applications, as well as creating, starting, and stopping sites, application pools and applications. Integrations with Sharepoint, SQL Server and BizTalk are also available.
uDeploy integrates with load balances such as F5 devices and Citrix Netscaler. A typical integration for a load balancer includes removing nodes from the system in preparation for upgrade and re-adding them after they pass post-deployment smoke tests. Other infrastructure tools like monitoring systems can also be manipulated as part of a release.
Tracing a deployment back to the build can be critical for audit purposes. For teams that already have a build system or build storage area, uDeploy provides integrations with a number of build tools including Hudson/Jenkins, JetBrains TeamCity, Microsoft TFS/TeamBuild and our own AnthillPro and uBuild products. Integration capabilities include retrieving deployables and writing status back to the build tool as appropriate.
uDeploy integrates with databases in two ways. It provides wrappers for command line database clients to enable their consistent inclusion in automated deployment processes. It also provides a database deployment toolkit. The toolkit is JDBC based, and enables teams to establish repeatable, ordered application of database changes.
Reporting tools also have built-in integrations. Unlike "builds" these reporting tools often operate on an extract and promote model. uDeploy can comfortably handle this scenario and treat the migrations as either full extracts or incremental moves.
Integration Approaches
There are several different types of integrations that the tools that make up uDeploy have to external systems.
The Automation Engine has 75+ integrations with external tools, and all of these integrations are available as Plugins to the automation system.
The Package System (PKS) also has integrations with external systems. The external systems that PKS integrates with are typically systems that can be deployed to: e.g., J2EE server, databases, and other types of software systems.
The Configuration Engine has integrations with external systems similar to those of the Package System. However, the goal of the Configuration Engine is to deploy configuration changes declaratively alongside code changes. While the Package System deploys code changes, the Configuration Engine deploys the configuration changes.
The Artifact Repository also has integrations with external systems that deliver artifacts for deployments. Typically, these external systems are Build Systems such as AnthillPro, Microsoft TFS, or Hudson.
