5 Things to Know about UrbanCode Deploy Integration for DevOps
5GS6_Margaret_Ticknor 1000005GS6 Visits (9970)
IBM UrbanCode Deploy is a tool for automating application deployments, it can be integrated with many proprietary and open source software and services in order to address the DevOps philosophy.
In addition to default features, UrbanCode Deploy can be extended by installing plugins that enable additional functionality and integration features such as IBM WebSphere Liberty plugin, Cloud Foundry plugin and the Jenkin plugin. New plugins and updates are being added periodically from IBM, Partners and Communities. Most plugins must be installed into UrbanCode Deploy but there are others that must be installed into the build or orchestration applications like Jenkins Plugin which adds a new Post-Build Action to a Jenkins job to publish artifacts to UbanCode components. You can find the UrbanCode Deploy plugin catalog at: http
The DevOps philosophy sees middleware software and its configuration like artifacts that can be manipulated, tested and deployed. Using this approach UrbanCode Deploy can be used to install middleware products like application servers and their configurations by using plugins or any of the scripting steps available. IBM WebSphere Liberty Plugin or Jboss Application Server Plugin are good examples of how to deploy middleware and automate administrative tasks from UrbanCode Deploy.
Git is one of the most popular Source Control Manager ( SCM) at the moment. Many proprietary and open-source development tools and cloud products use Git as a source code repository and UrbanCode Deploy is not an exception. Selecting Git as Source Configuration Type you can simply add the information of your Git repository in order to fetch artifact from it automatically or manually. You can find instruction about how to integrate UrbanCode with Git at: http
Rational Team Concert is a team collaboration tool that uses the Change and Configuration Management (CCM) application to provide features that integrate development project tasks including iteration planning, process definition, change management, defect tracking, source control, build automation, and reporting. If you use RTC for coding and building your application then publishing your build to UrbanCode Deploy is as easy as defining the connection option for UrbanCode Deploy and defining the target component. Here is a quick overview of the process:
While defining your Build Definition, select Post-build Deploy on the Post-Build page, then in the Build Definition editor, go to Post-build Deploy tab and configure the following option:
You can also enable the Run Application Process check box, in order to execute the deployment process to a target application and environment.
You can find the complete set of instructions at: http
As mentioned earlier, DevOps philosophy applied to UrbanCode Deploy allow us to model server and application configuration as components, by using this approach we can define several configuration components for application server configurations depending on the requirements.
Defining a Liberty Profile cluster is as easy as generate 2 different configuration components, one for the Collective Controller, and other for the Collective members. Each component must include a server.xml file and the specific settings required for each kind of server instance. You can use a tokenized configuration file to customize certain configuration properties depend on the environment you are installing it, like data sources properties. Once you have defined all the configuration simply deploy each component on the desired agent. A practical example of this approach can be found in the IBM Redbooks publ
Sebastian Carrizo is an WebMiddleware Subject Matter Expert in the IBM Delivery Center Argentina (DCA), and Middleware SME in the Application Hosting Global Service Line. He is a foundation level Architect and a system analyst. Sebastian has over 5 years at IBM, and his industry experience include automotive, financial service, steel industry and education.