Deployit will not install the IBM WebSphere Application Server or IBM WebSphere Portal Server middleware, but it will configure it. That means you will have to manually install WAS or Portal on your hosts (or use a product like Tivoli Provisioning Manager to do this for you).
But, Deployit will configure and manage servers and clusters on top of that installation as well as application oriented configurations such as datasources, queues, topics, etc. Those are typically the configurations you will be doing way more often. For more information, have a look at our blog "So what is a deployment really?" to get a feeling for what is in the scope of an application deployment.
Does Deployit install and configure WebSphere or Portal middleware?
What middleware platforms are supported by Deployit?
Deployit supports all mainstream middleware platforms and associated solutions:
- IBM WebSphere Application Server 5, 6 and 7
- IBM WebSphere Portal Server 6
- IBM WebSphere MQ
- Oracle WebLogic Application Server 10 and 11
- Oracle Service Bus
- JBoss Application Server 4 and 5
- Tomcat Web Server
- Apache HTTPD Server (including virtual hosts management)
- Maven (including Hudson, Bamboo and CruiseControl)
- Eclipse
For non-listed platforms, sometimes a partner-developed plugin exists. But it is also possible to create your own (custom) plugins using Deployit's open plugin API.
Can Deployit handle the "undo" part within a production deployment context?
Yes, absolutely!
Deployit supports upgrading and downgrading of versions equally, so “undo” can be handled simply by re-deploying the previous version. Deployit also gives you the chance to fix transient problems first (e.g. can’t reach a server because it’s not running) and continue the deployment from that point onwards.
How does Deployit differ from build automation tools like Ant, Make and Maven?
Although Wikipedia describes "deployment to production systems" as one of the activities in build automation, build automation tools have no built-in knowledge of concepts such as deployment packages (the application and configuration files to deploy), target environments (test, acceptance, production, etc.), or bindings (what password to use in which environment). Build automation systems also have little or no built-in integrations with middleware systems like WebSphere, WebLogic and JBoss on which to deploy and never have built-in deployment scenarios.
All these factors contribute to the large body of custom deployment scripts built on top of build automation tools that exist today. That is also the reason that Deployit provides plugins to integrate with build automation tools like Maven, in order to help clients ressolve this.
Does Deployit support Java application deployments within complex (custom) environments?
Deployit was designed from the ground up to be extensible. Most users have enough with the out-of-the-box supported platforms like WebSphere, JBoss, WebLogic and Tomcat, but for some situations, you may want to use Deployit's open plugin API. Using the API, you can extend and/or tailor the existing deployment processes. You can even develop your own plugins to support custom middleware or systems not yet supported out-of-the-box, and to add integrations with other application lifecycle management systems such as monitoring systems, change management systems and release management systems.
Can I maintain more than one version of my software package?
Yes, you can certainly deploy an older version without having to reconfigure and destroy the current version's deployment scenario.
Deployit maintains a record of the versions of your application (each deployment package represents a different version), and shows you which version is running in which environment. You can also generate reports on this. This makes it very easy to switch to a different version, whether for an upgrade or a revert.
Does Deployit store data about deployments?
Yes, it does. Deployit keeps track of deployment histories and deployment statistics for audit purposes and process improvements. Deployit can publish / export these data into reports and graphics. Per deployment, Deployit logs what has been deployed to which environment, by whom and at what time.
Does Deployit compare middleware configurations?
Yes, it does. Deployit's sophisticated discovery functionality enables to compare middleware configuration settings before you start the actual application deployment. Deployit automatically discovers and compares names, port numbers, memory usage and configuration settings for middleware servers, clusters and nodes. This ensures you will always deploy to a known environment in a reliable way, with no surprises afterwards.
What is Deployit's key differentiator?
Software applications in general don't just run on an application server, they also need a properly configured database, a message broker and/or an enterprise service bus, a web server and so on. In order to deploy a (new version of an) application, you need to properly configure and update all of these artifacts running on different platforms in a coordinated manner. Other tools often do only partial deployments, e.g. updating the application server. Deployit is unique in that it takes care of the full deployment spectrum and automaticaly configures each and every impacted middleware component during the deployment process.
Where does Deployit fit in Application Lifecycle Management?
An Application Lifecycle Management or ALM solution reduces manual processes, handoffs, and documentation by automating these. According to analyst firm Forrester, this should include the mistakes that creep into the deployment process as well.
That is where Deployit fits in: by using the same best practices, processes and underlying technology for packaging and deploying code from development to test, acceptance and production environments, you as Devops will get a much more robust software release management automation process. Deployit automates the entire deployment process, which results in reliable, repeatable and controlled application deployments.
Moreover, with its open Plugin API, Deployit easily integrates with other ALM-related solutions, like build automation systems, continuous integration systems and change management systems.
ALM 2.0 can not be achieved without deployment automation.
How Can We Help?
XebiaLabs USA
- Phone:508.983.2515
508.983.2512 - 1900 West Park Drive
Suite 280
Westborough,MA 01581 - Email:info@xebialabs.com