Ibm urbancode deploy concepts
•Download as PPTX, PDF•
1 like•839 views
UrbanCode Deploy is an application release automation tool that provides visibility, traceability, and auditing for deployments across distributed, cloud, and virtual environments. It handles the "what", "how", and "where" of deployments by defining components (deployable items) and processes, and targeting resources (environments like servers and databases). Key concepts include components, applications, resources, environments, agents, and plugins. Components represent deployable items and processes, applications coordinate multi-component deployments, resources are targets, and agents facilitate deployments on resources.
Report
Share
Ibm urbancode deploy concepts
- 1. IBM URBANCODE DEPLOY - CONCEPTS Joseph Amrith Raj Paturi
- 2. introduction ■ UrbanCode Deploy is an application release automation solution that combines robust visibility, traceability and auditing capabilities. It allows you to seamlessly deploy to distributed data centres, cloud and virtualized environments—on demand or on a schedule
- 3. The What, How, and Where of the deployment workflow Source : https://www.ibm.com/support/knowle dgecenter/en/SS4GSP_6.0.0/com.ibm. udeploy.doc/topics/intro_ch.html What: the deployable items: binary files, static content, middleware updates, database changes and configurations, and anything else that is associated with the software that IBM UrbanCode Deploy delivers to target destinations. How: refers to combining deployable items with processes to create components, and designing applications that coordinate and orchestrate multi- component deployments. Where: the target destination's hosts and environments: IBM UrbanCode Deploy can scale to any environment.
- 4. Terminology Urbancode deploy components Resources Agents pluginsprocesses Environments Applications • Components • Versions • Component processes • Resources • Resource group • Environments • Processes • Generic processes • Applications • Application process • Agents • Plug-ins
- 5. Components ■ Components are the smallest functional unit of your application. It might be a WAR, it might be some static files. A component is whatever the smallest atomic unit that you can split up your application into. ■ Components represent deployable items along with user-defined processes that operate on them, usually by deploying them. ■ Components have versions, which are used to ensure that the appropriate component instances get deployed ■ A component process is a series of user-defined steps that operate on a component's artifacts. Each component has at least one process defined for it and can have several. Component processes versions
- 6. Application ■ An application is what represents your application that you'll be deploying ■ An application is the mechanism that initiates component deployments; they bring together components with their deployment targets, and orchestrate multi- component deployments
- 7. Resources ■ A resource represents a deployment target, such as a physical server, virtual machine, database, or Java™ Platform, Enterprise Edition container. Components are deployed to resources by agents ■ To run a deployment, at least one resource must be defined and at least one agent. ■ A resource group is a logical collection of resources. Resource groups enable collections of resources to be easily reused. Resource groups can manage multi-tenant scenarios, for example, in which several servers share resources.
- 8. Agents ■ An agent is going to be something that lives on a resource, that lives on something you want to deploy to and facilitates the deployment. ■ An agent is a lightweight process that runs on a host and communicates with the IBM UrbanCode Deploy server. Agents manage the resources that are the actual deployment targets. Each system that participates in a deployment usually has an agent installed on it. When not running deployments, agents run in the background using minimal resources
- 9. Environment ■ An environment represents what you're deploying to. ■ An environment can point to multiple resources; an environment can be a single resource. A resource can be something like a database, it can be where your Apache server lives, it can be anything that you're - any location that your deploying to.
- 10. Urbancode plug-ins ■ Plug-ins provide basic processing functions and integration with third-party tools. IBM UrbanCode Deploy ships with plug-ins for several common deployment processes, and others are readily available for a wide variety of tools, such as middleware tools, databases, servers, and other deployment targets.
- 11. The Summery ■ UrbanCode Deploy is an application release automation solution that combines robust visibility, traceability and auditing capabilities. It allows you to seamlessly deploy to distributed data centres, cloud and virtualized environments—on demand or on a schedule
- 12. About Joseph ■ Joseph Amrith Raj Paturi – WebSphere Consultant ■ IBM Champion forWebSphere – 2012,2013 ■ IBM Champion for middleware – 2016 ■ IBM Champion for cloud – 2018 ■ Blogs : – www.webspherelibertyprofile.wordpress.com – www.websphereapplicationservernotes.wordpress.com ■ Social – Facebook: www.facebook.com/webspherelibrary – Twitter : www.twitter.com/websphere_lib