ZQ410 Unit 2 Transcript

Slide 1

Configuring components and

component processes

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.

Components represent deployable items along with user-defined processes that operate on them,
usually by deploying them. In this unit, you learn how to create a component, import component
versions, create component processes, and work with properties.

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 2

Unit objectives
• Describe the purpose and structure of a component
• Create components and import component artifacts
• Create component processes to deploy components
• Store component information with properties

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 3

Topics
• Components overview
• Creating components and importing component artifacts
• Creating processes to deploy components
• Storing information with properties

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 4

A component is the smallest functional unit of an application

Application

Application process Component Environment

Component processes
Component processes Resources
Steps

Agent
Properties
Properties
Component
Versions
Versions Files

How What Where

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

You will see this representation of the objects in IBM UrbanCode Deploy for the next two units.
This slide shows a visual that groups the parts of the product that make up an application.

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 5

Components describe what gets deployed

Application

Application process Component Environment

Component processes
Component processes Resources
Steps

Agent
Properties
Properties
Component
Versions
Versions Files

What

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

This section focuses on components, which are containers for deployable items and their
deployment instructions. A component usually contains a closely related set of artifacts, and you
would deploy its content on a single target.

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 6

Each component represents artifacts from a single source

Component tiers
of an application

Web
Images and static content
component

Database
Application component
Application WAR file

Application
SQL
component

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

An application consists of a break down of components. In this example, the application has three
component tiers: one for the web content, one for the database content, and one for the
application content. This arrangement gives flexibility to deployments. You can see what versions
of each component are deployed to specific environments. The benefit of IBM UrbanCode Deploy
is that it manages the source file and identifies which files have changes. Then, it deploys only
the changed files.

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 7

A component contains versioned files, component processes, and properties

Properties
Steps

Component
processes
Component

Versions

Files

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

From a high-level view, a component has three major parts: versions, component processes, and
properties.
• A version contains a set of artifacts. Versions ensure that the appropriate set of files get
deployed.
• A component process is a list of commands that run on a target computer. Steps can
manipulate files, run system commands, download files, and run programs.
• Properties are variables that store the locations of files, folders, servers, or other resources
that might change.

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 8

Topics
• Components overview
• Creating components and importing component artifacts
• Creating processes to deploy components
• Storing information with properties

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 9

Component artifacts can come from various source-code management sources

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

When you create a component, you identify its type of artifacts and the location of the artifacts. In
most cases, you add components by connecting the server to the system that hosts the artifacts,
such as a Maven repository. In this example, and when you work through the lab, the versions
are imported from the file system.

In the Create Component window, you’ll need to consider a few things:

• Component Template: First, you decide if you want to base a new component on a
template. Templates allow you to reuse component processes and properties, and can save
you time when you create many components with a similar set of attributes. While this
course doesn’t cover templates, you can consult the video demonstration in the notes
section of this slide for more information.
• Source Configuration Type: The Source Configuration Type identifies the location of the
artifacts. You can choose from many different source control systems.
• Import Versions Automatically: If you select the option to Import Versions Automatically,
the source location is periodically polled for new versions. Any versions that are found are
automatically imported.
• Run Process after a Version is Created: In conjunction to automatically importing
versions, at the bottom of the window, you can choose to run a process after a version is
created. You specify an environment and an application process. Then, any time a new
version is automatically imported, the process runs. You can use this to automatically deploy
a new version any time it’s created.
• Copy to CodeStation: By default, a complete copy of the content is imported into
CodeStation, which leaves the artifacts in their original location untouched. CodeStation is
the embedded artifact repository in IBM UrbanCode Deploy. It tracks file versions and
maintains a complete history for all components.
• Default Versions Type: When you import a version, it can be full or incremental. You make
this selection in the Default Versions Type field before you even import the component. A full
version contains all component artifacts. An incremental version contains only artifacts that
are different from the previous version. It’s additive, like a patch.

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 10

Components have versions that ensure the appropriate component instances

are deployed

Current component
version

Import process for

latest component
version

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

After you define the source for a component, you import its artifacts on the Versions tab. Each
time a component is imported, including the first time, a new version of the component is created.
This is called versioning.

To manually import a new version, you click Import New Versions. The status of the import
process displays in the Currently Running Version Imports section. You can see the agent that is
importing the component.

10

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 11

The agent is typically on the same computer where the artifacts are located

The agent for importing

component versions is defined
in the system settings

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

Version artifacts are imported by the agent on that system. The agent copies the files from a
repository or file system into CodeStation. You can choose the agent that imports versions in the
System Settings.

11

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 12

A new version of the component is created every time a component's artifacts

are modified and imported

New component
version successfully
imported

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

A component might have several versions in CodeStation, and each version has a unique set of
files.

12

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 13

The version import history shows the status of attempted imports

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

You can see the version import history in the Configuration tab. If the version import failed, you
can view the error log. Make sure that the files are available on the agent system and that the
location of these files is correct on the component.

13

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 14

A version contains a set of deployable artifacts

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

After a version is imported successfully, click the new version to view the files that were imported.
Versions let you see all of the files that are associated with a component. In this example, the
images for the web server are listed in the Artifacts section.

14

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 15

Change logs provide information about modifications to components

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

The Changes tab tracks changes made to the component. You can see who modified the
component and the date and time the change was made. This provides you with an audit trail of
who is changing things. In this example, you can see that the basePath property was changed.

15

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 16

Topics
• Components overview
• Creating components and importing component artifacts
• Creating processes to deploy components
• Storing information with properties

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

16

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 17

Component processes deploy, configure, or uninstall component versions

Deployment • Deploys the specified component version to the target resource

Configuration
• Applies a configuration inventory to a deployed component
Deployment

Uninstall • Removes the component version from the target resource

Operational (with • Does not add or remove artifacts from the inventory; it runs steps
version) on a currently deployed component

Operational (no • Same as the Operational (with version) type, except that this type
version needed) does not use a component version

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

At this point, you created your components and imported the versions. So, how does the actual
deployment happen? You deploy components with component processes. Processes define what
IBM UrbanCode Deploy does with a component's artifacts. For example, a component process
can run tasks on a single component, such as deploying it, uninstalling it, or running configuration
tasks on it.

17

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 18

Components contain processes that perform operations on component files

${p:resource/work.dir} is
the default working
directory for the agent

${p:component.name} is
the component name

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

You create a component process in two steps: first, you configure basic information, such as the
name and process type; then, you use the process editor to assemble the process. A component
process is defined for a specific component.

When you create a process, you need to set a few things:

• Process type: The process type determines how the component handles updating the
inventory in IBM UrbanCode Deploy. This is where you decide if your process will deploy
components or configuration, or if it will uninstall a component.
• Inventory status: The Inventory status is a status that is applied to a component version
after the processes successfully runs. An Active status indicates that the component version
is deployed to its target resource.
• Default working directory: The default working directory defines the location that the agent
uses to run the process. You can see the default value in the example, where
${p:resource/work.dir} is the default working directory for the agent and
${p:component.name} is the component name. (The default value resolves to
agent_directory\work\component_name_directory and is stored in the
componentProcess.defaultWorkDir property.)
• Required role: You can set a value in the Required Role field to restrict access to a specific
role of users who can run this process. The available options are derived from the IBM
UrbanCode Deploy security system. The default value is None, meaning anyone can run the
process.

18

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 19

Component processes are created with the process editor

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

Component processes are created with the process editor. To open the process editor, click the
process name. The process editor has a Steps palette on the left and a design space on the right.
A process begins with the Start step and must end with the Finish step.

19

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 20

Process steps are selected from a menu of standard steps that replace typical
deployment scripts and manual processes

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

The available steps in the palette are determined by the installed plug-ins. Plug-ins consist of
distinct processes called steps. Each step consists of a number of properties, a command that
runs the step, and post-processing instructions. Step properties can serve various purposes, from
providing input to the command to supplying some, or all, of the actual command itself.

Some plug-ins are included with the product, but you can install others. IBM UrbanCode Deploy
provides steps for several utility processes, such as inventory management, and workflow control.

20

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 21

A number of plug-ins come with the product and many others are available that
can be downloaded and installed

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

Other process steps are provided by plug-ins that provide integration with common deployment
tools and application servers. A full list of plug-ins can be found on DeveloperWorks at this
address: https://developer.ibm.com/urbancode/plugins/.

Plug-ins provide processing and integration functions. There are two types of plug-ins:
• Source-type plug-ins integrate with external systems to import artifacts and create
component versions. Source-type plug-in properties are typically defined when a component
is created.
• Automation-type plug-ins provide process steps that manipulate components, typically by
deploying them. Automation-type plug-in properties can be set at design time in the process
editor, or at run time in the user interface.

21

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 22

The palette provides automation steps that you can drag onto the process editor

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

The process editor is a visual drag-and-drop editor where you can drag process steps from the
palette onto the design space and configure them as you go. As more steps are placed, you
visually define their relationships with one another.

When you drag a step into the process editor, you can edit the fields for that step. In this
example, the Download Artifacts step is prepopulated with information that you can use.

22

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 23

Processes are versioned artifacts

Current process Reset to any
version in use process version

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

Each time that you save your process, a new version of that process is saved. You can scroll
through the versions to view them and then reset to any process version that you previously
saved.

23

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 24

The Changes tab tracks the creation date and author of the versions

Tracks who made

changes and when

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

When a process is created, information is gathered to inform when a change was made and who
made it.

24

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 25

Processes use different kinds of steps and joining techniques

Conditional • The conditional flag sets a condition on a connection

processes
Switch steps • Branch processes, based on the value of a property

Branching steps • Branch processes so multiple steps run at the same time

Joining steps • Merge processes to return to running a single step at a time

Process step • Items that a post-processing script finds in the step's output log
properties
Preconditions • Preconditions determine whether the step runs

Post-processing • Post-processing scripts run after a step finishes

scripts
Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

A component process can be as simple as a single step or contain numerous relationships,

branches, and process switches. When you design processes, you use different kinds of process
steps and joining techniques.

25

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 26

Conditional processes use flags to set conditions on connections

Process succeeded

Process failed

Either success or fail

is acceptable

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

By default, all connections between steps have the flag set to succeeded, which is the green
circle with a check. This means that the originating step must finish processing before the next
step starts to process. If you set the flag to failed, which is the red circle with an explanation point,
then the step must have a failed process to reach the next step in that branch. And if you set the
flag to a gray circle, the process moves to the next step, whether the previous step’s process
completed or failed.

The possible conditional flags are as follows:

• Success: The process is complete.
• Fail: The process did not finish.
• Both: The process is complete or the process did not finish. Either status is acceptable, and
the next step can start.

26

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 27

Switch steps branch processes based on the value of a property

Switch step with

specific property check

Possible values for

the property

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

When you add a switch step, you specify a property. Then, you add two or more outgoing
connections from the step, each with a possible value for that property. At run time, the process
follows the connection with the matching property value.

27

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 28

Branching steps runs multiple steps at the same time

Both branches, Step B and

Step C, run at the same time

Steps P and Q merge at

Step R, which runs if either
Step P or Q succeeds

All connections up to this

point must reach this step
to process Step D

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

You can branch processes so that multiple steps run at the same time by adding multiple
outgoing connections from a step. You can use a Join step to merge processes into running a
single step at a time. Join steps indicate that all connections to the Join step must succeed. If any
of the steps that connect to a Join step fail or do not run, the Join step causes the process to fail.
In this example, all steps leading up to Steps R and B must complete, as Steps R and B both
connect to a Join step.

28

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 29

Topics
• Components overview
• Creating components and importing component artifacts
• Creating processes to deploy components
• Storing information with properties

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

29

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 30

Properties are variables that store information about different elements

Properties are pointers

within a step to a
predefined property
Properties that are defined for
specific environments

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

Properties are pointers to values. They store information about components, environments,
processes, applications, and global properties for the system. In this example of a component
step, the URL field points to a value that is defined for the environment. At run time, the
environment property, in this case the db.url value, will be substituted here.

30

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 31

Components can have several types of properties

Component

Component
Resource property Environment
types

Version

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

Component properties: Component properties are values defined and set directly on the
component. They stay the same for all versions of the component. So, any time you import a new
version, the properties are already set.

Property definitions: Components have a special type of property called property definitions.
Component property definitions can be used for environments, versions, and resources. You use
definitions when you have a value that the component uses that needs to change each time you
use that component. These properties are defined on the component, but their values are set in
other places. For example, Component environment properties are defined on a component, but
the values are not specified until the component is deployed to an environment. In the previous
slide, the URL field pointed to a predefined environment property called db.url. This allows you to
assign a different database URL to each environment. You might want to do this if you have a
test database at one URL for your development environment and a production database at
another.

• For example, if different database users have access to the development and test
databases, you can set the database user name and password in each environment. Then,
you use a component environment property to point the correct database URL for each
environment. is different in every environment (DEV, QA, SIT, etc.)

• Component version properties are defined on a component, but the values are specified on
component versions. This type of property stores information that changes with each version
of the component, such as a version number. Each component version can have a different
value for its component version property.

• Component resource properties are defined on components, but they are not given a value
until the component is added to an environment as a resource. Then, the property behaves
much like a resource property. Because a component can be added to an environment
multiple times, each instance of the component can have a different value for the component
resource property. If you need to use two copies of a component in the same environment
but use a different value between them, use a resource property definition.
31

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 32

Properties are referred to by scope

Property notation
Component ${p:component/propertyName}

${p:elementType/propertyName}
Environment ${p:environment/propertyName}
location property name

Version ${p:version/propertyName}

Resource ${p:resource/propertyName}
${p:environment/db.url}

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

Properties are referred to by scope. Scope is the type of artifact that contains the property, such
as the environment or component. When you refer to a property, you use the notation that starts
with a dollar sign, open curly brace, p, which stands for property, and then a colon. Then you
identify the artifact, followed by a slash, the property name, and a closed curly brace.

${p:component/prop.name}, where the “p” stands for “property.” It’s says to look in this location
with this name.

Keep in consideration where values change; that is where you want to set the properties.

This slide shows the most commonly used component properties and definition. Application,
environments, resources, the system, and agents all have properties as well. For more
information, see the IBM Knowledge Center:
https://www.ibm.com/support/knowledgecenter/SS4GSP_6.2.3/com.ibm.udeploy.doc/topics/ud_pr
operties_overview.html.

32

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 33

Properties can also be referred to without scope

Property notation with scope Property notation without scope

${p:elementType/propertyName} ${p:propertyName}

location property name property name

${p:environment/db.url} ${p:db.url}

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

There might be situations where you don’t want to reference a specific artifact. In this case, you
can refer to a property without scope by leaving out the artifact (${p:propertyName}). For
example, with the environment variable, db.url, you can refer to it with the artifact name,
environment, as you see on the left (${p:environment/db.url}). Or you can refer to the same
environment variable without scope by removing the artifact name, as shown in the right
(${p:db.url}). In this way, you can refer to properties defined in other places, such as in the
application, system, or resource.

33

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 34

Property scope determines the precedence of properties with the same name

4 5

Agent Environment
3 6
Resource Component

2 7
Component
Application
version

Highest 1 Processes Scope System 8 Lowest

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

If a property is defined in multiple places, its value is determined by the property’s order of
precedence. The order of precedence allows you to override properties in specific contexts. If you
refer to a property without scope, then the property with the highest order of precedence is used.

This slide shows the order of precedence from highest to lowest. The highest precedence is given
to properties that are referenced in processes. The lowest precedence is given to properties
referenced in the system.

In this way, you can override properties to change the application behavior without changing the
code. For example, an application might have a database for testing and a separate database for
production use. In this case, you might create an application property, such as databaseLocation,
to store the testing database location. The application and component processes can refer to the
property without specifying the application scope, like this: ${p:databaseLocation}. Then, in the
production environment, you can override the application property with an environment property
that specifies the production database location. The processes still refer to
${p:databaseLocation}, but in the context of the production environment, the environment
property takes precedence, so the application uses the production database.

34

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 35

Properties are primarily set from the Configuration tab

You can also set properties here:

• Processes
• Rest API and command line
• Output properties

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

You can set properties in the following locations:

• Configuration tab: You can manage properties for applications, components, and
environments
• Processes: Several different steps are available to create and set properties in processes
• REST API and command-line client: Several commands in the REST API and in the
command-line client can set properties
• Output properties: You can pass properties from one step to another within a process

Properties for applications, processes, components, component versions, resources, and agents
are available on their respective configuration tabs. System (global) properties are available on
the Settings tab at the top of the page, by clicking Settings > Properties.

35

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 36

Unit summary
• A component has three major parts: versions, processes, and properties
• Components are added by connecting the server to the system that hosts the artifacts
• A component version contains a set of deployable artifacts
• A component process is a series of user-defined steps that operate on a component's artifacts
• Component properties are values that are assigned on individual components
• Property definitions are defined on the component, but their values are set in other places

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

36

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.
ZQ410 Unit 2 Transcript

Slide 37

Exercises: Configuring components and component processes

• Create components and add user-defined properties to them
• Import artifacts to create component versions
• Create component processes

Unit 2: Configuring components and component processes © Copyright IBM Corporation 2017

37

© Copyright IBM Corporation 2017

Course materials may not be reproduced in whole or in part without the prior written permission of IBM.