Slide 1: ZQ410 Unit 4 Transcript
Slide 1: ZQ410 Unit 4 Transcript
Slide 1
You run a deployment by running an application process in a target environment. In this unit, you
learn how to deploy to an environment, create and deploy snapshots, and compare environments
to view the inventory in each one.
Slide 2
Objectives
• Describe what happens in a deployment
• Describe the difference between full and incremental deployments
• Describe why and how to use snapshots
• View which versions are deployed to environments
• View the file differences between the environments
• Preview deployments for impact analysis
• Migrate changes from one environment to another
Slide 3
Topics
• Deploying to an environment
• Examining application environment inventory
• Deploying applications with snapshots
Slide 4
DEPLOYMENTS
As we talked about in the first unit, a deployment is the promotion of an application from one
environment to the next.
Slide 5
Server Agent
CodeStation
Deployment DB 1.1 WEB 1.1 APP 1.0
The IBM UrbanCode Deploy server provides a file transfer capability for deploying files to target
servers. A deployment involves selecting component versions from a repository, moving those
components to the target server, and completing the required tasks for bringing those parts of the
application online.
Slide 6
When you start a deployment, you identify the application process and the component versions to
deploy. You can select any process that is defined for the parent application, and you can use
any components that are associated with the application.
If you want to deploy only the changed versions since the previous deployment, select the Only
Changed Versions check box. If you uncheck this check box, all of the component versions that
you select are deployed, even if they are already in the inventory.
Slide 7
When an application process starts, the Application Process Request page displays information
about the deployment status. Notice that the steps in the log are the same as the component
process.
Slide 8
After a process finishes, the Execution section shows the status. You can click on the bars to get
more details about the processes and steps.
Slide 9
Topics
• Deploying to an environment
• Examining inventory and deployment information
• Deploying applications with snapshots
Slide 10
From the Environments tab of an application, you can see that there’s an inventory system. The
inventory system tracks the desired state of each environment and what has been successfully
deployed to each target resource. Compliancy indicates whether the environment contains those
component versions.
The inventory and compliance for an environment are updated each time that you run an
application process or deploy a snapshot to the environment.
In this example, there are three deployable components that are deployed to two environments.
You can see that the SIT environment has newer versions.
10
Slide 11
IBM UrbanCode Deploy maintains an inventory of every artifact that is deployed to each
environment and also tracks the differences between them. You can compare two environments
to see differences in the versions that they contain.
11
Slide 12
When there is a problem in production or during testing, traceability makes it easier to understand
what changes are going in that could have caused the problem.
12
Slide 13
The History tab show the process requests for a specific environment
You can view the progress of the process by going to the History tab and opening the process
request.
13
Slide 14
The Usage tab shows the environment inventory for each component
You can track the environment inventory for each component by clicking the component and then
going to the Usage tab. IBM UrbanCode Deploy tracks both the version that is currently in an
environment and also what was in various environments over time. This is helpful comparing
flows through environments and identifying what changed.
14
Slide 15
You can filter data, print and save reports, and save search criteria with deployment reports. You
can obtain information for specific reporting periods, such as the number of deployments,
average deployment duration, and total duration. In this example, the Deployment Detail report
shows all deployments for the specified applications, environments, and users for a given time
period.
• Deployment count: Provides information about the number of deployments that ran during
a specified reporting period.
• Deployment average duration: Provides average deployment times for applications that
ran during a specified reporting period.
• Deployment total duration: Provides total deployment times for applications that ran during
a specified reporting period.
• Deployment detail: Shows all deployments for the specified applications, environments,
and users in the specified time period.
15
Slide 16
Topics
• Deploying to an environment
• Examining application environment inventory
• Deploying applications with snapshots
16
Slide 17
Creating a Snapshot
WEB WEB
1 2 3 3
APP APP
1 2 3 1
DB DB
1 2 3 2
Snapshots are models that you create before you deploy the application. A snapshot specifies the
exact version for each component in the application. When a snapshot is created, information is
gathered about the application, including the component versions, for an environment.
Typically, the snapshot is generated in an environment that has no approval gates. This kind of
environment is called an uncontrolled environment.
17
Slide 18
SIT UAT
Component Versions Snapshot
Environment Environment
WEB WEB WEB WEB
1 2 3 3 3 3
DB DB DB DB
1 2 3 2 2 2
You use snapshots to ensure the same exact deployment happens from one environment to
another. If you have several components, selecting a version for each one, each time, could
introduce errors. A snapshot is a single deployable item that you can push from environment to
environment. After all the appropriate stages and approvals for a snapshot are complete, the
snapshot is pushed to production.
18
Slide 19
To create a snapshot, you choose the component versions and processes to include in the
snapshot.
19
Slide 20
You can preview an application snapshot before you deploy it to see the upcoming changes in
resources and properties.
20
Slide 21
When you have a snapshot, you select both the environment to deploy to and the process to use
for the deployment.
21
Slide 22
The deployment looks the same as the original deployment each time the snapshot is used.
22
Slide 23
Snapshot deployed to
UAT environment
The inventory is immediately updated and can be viewed alongside of other environments in the
application.
23
Slide 24
Locks component
versions
Locks configuration
Environments can be configured to specifically lock either snapshot versions or the snapshot
configuration, or both, when snapshots are deployed to the environment.
24
Slide 25
By default, the lock setting for both component versions and snapshot configurations are
determined by the option selected in the Lock Snapshots field on the Create Environment
window. All snapshots used in a request to this deployment will be locked to prevent further
changes.
25
Slide 26
Unit summary
• A deployment is the promotion of an application from one environment to the next
• You run a deployment by running an application process in a target environment
• You can compare two environments to see differences in the versions that they contain
• Snapshots are models that you create before you deploy the application
• A snapshot specifies the exact version for each component in the application
26
Slide 27
27