SlideShare a Scribd company logo
1 of 59
© Copyright IBM Corporation 2014
Essentials of UrbanCode Deploy QQ147
Components
2 © Copyright IBM Corporation 2014
Agenda
What are components?
Aspects of a component
Creating a component
Importing Component versions
Component processes
Component templates
3 © Copyright IBM Corporation 2014
Objectives
After completing this module you are able to:
•Import artifacts to create a component
•Set environment properties on components
•Add versions to the components
•Create component processes
•Create component templates
4 © Copyright IBM Corporation 2014
What are components?
• Components represent deployable items along with
user-defined processes that operate on them. For
example:
• A typical Java-™ Platform, Enterprise Edition application
typically has three components (application, database, and
web components).
• Large applications might have many more.
5 © Copyright IBM Corporation 2014
Features of a component
The main features that make up a component are as
follows:
• Source configuration
• Component versions
• Component properties
• Component processes
6 © Copyright IBM Corporation 2014
Creating a component
To create a component:
1. Choose the Components tab.
2. Create New Component.
7 © Copyright IBM Corporation 2014
Creating a component
You see this page:
8 © Copyright IBM Corporation 2014
Creating a component
The fields on the form:
Name: Provide a name for the component. It might
reflect the item or tier of the application to be deployed.
Description: An optional field to elaborate on the
contents of this component.
9 © Copyright IBM Corporation 2014
Creating a component
Teams: With this field, you can associate a team with a
component. To learn more about teams, see the
security module or refer to the documentation.
Template: Components can be created from a
template. Templates are covered later in this module.
10 © Copyright IBM Corporation 2014
Creating a component
Component Type: You can select one of two types of
components, Standard and z/OS. Choose z/OS only if
this component is intended to be deployed to a
mainframe.
11 © Copyright IBM Corporation 2014
Creating a component
Source Config Type: In this field, you can define how
artifacts are associated with a component. Several
available choices come with the product. The
available choices are defined by source configuration
plug-ins. Each plug-in defines a single type of
artifact. You can import artifacts manually or have
IBM UrbanCode Deploy import them automatically.
12 © Copyright IBM Corporation 2014
Source config type file system
13 © Copyright IBM Corporation 2014
Creating a component
Use Base Path for importing a file system. In the
field, you specify where to get the files for
importing. The files are moving from the file
system to the UrbanCode Deploy artifact
repository for storage until they are deployed.
14 © Copyright IBM Corporation 2014
Creating a component
Import Versions Automatically: If this option is
selected, IBM UrbanCode Deploy polls the Source
Config for new versions.
Copy to Codestation: Select this option, if you want
to store the component versions in the IBM UrbanCode
Deploy repository (Codestation).
15 © Copyright IBM Corporation 2014
Creating a component
Default Version Type: Two version types are
available: full and incremental. Choose Full, if the
contents of the component versions represent the
entire component. Choose Incremental, if the
contents are a subset of the full component. For this
course you select Full versions.
16 © Copyright IBM Corporation 2014
Creating a component
Import version settings:
These settings determine which agent is
responsible for importing the versions into
IBM UrbanCode Deploy. Typically the first
selection is fine.
17 © Copyright IBM Corporation 2014
Creating a component
Inherit Cleanup Settings: Select this check box to
inherit the cleanup settings that are defined for the
server. If not, you must define your own cleanup
policies.
Run process after creating a new version: Select
this check box to launch a process immediately after
the IBM UrbanCode Deploy system recognizes a new
version.
18 © Copyright IBM Corporation 2014
Creating a component
Upon completion, your form looks like this illustration:
19 © Copyright IBM Corporation 2014
Creating a component
Next, click Save, and you see your new component.
20 © Copyright IBM Corporation 2014
Version import overview
After learning how to create a component, you learn
how to create a component version. Components can
have many component versions. These versions are
deployed later.
For the example, the File System Source Config type is
used. Before importing the versions, you must check a
few things first.
21 © Copyright IBM Corporation 2014
Version import overview
Recall that Use the system’s default version import
agent/tag was selected earlier in this module.
Next, define which agent to use for importing
the versions.
22 © Copyright IBM Corporation 2014
Version import overview
23 © Copyright IBM Corporation 2014
Version import overview
After you click System Settings, to the left you see
General Settings, and near the bottom there is an
entry for Agent for Version Imports. Choose the
agent to use to import the versions. Typically the agent
is on the same computer where the artifacts are
located. For help on installing agents, see the product
documentation for Agent Installation.
Check the next slide for a screen capture.
24 © Copyright IBM Corporation 2014
Version import overview
25 © Copyright IBM Corporation 2014
Version import overview
As you can see, we have a file located in this directory:
/tmp/artifacts
The file is called myApp.ear.
This file will be imported into IBM UrbanCode Deploy.
Next, you import the file.
26 © Copyright IBM Corporation 2014
Version import overview
To import the file, you must return to the Component.
Click the Components tab, and then click the
component that you created. You see this page:
27 © Copyright IBM Corporation 2014
Version import overview
Next, click the Versions tab, and then click Import
new Versions. You see this page:
28 © Copyright IBM Corporation 2014
Version import overview
In the Version Name field, define the name of the
version to import.
For example, enter 1.3.0.4.
Then, click Save.
29 © Copyright IBM Corporation 2014
Version import overview
You see the imported version.
30 © Copyright IBM Corporation 2014
Version import overview
By clicking the new version, you see the files that were
imported under the Artifacts section.
31 © Copyright IBM Corporation 2014
Component processes
After you import a version, you define a process for
how to deploy that version. The idea is to create a
repeatable process that can be reused as new versions
of the component are developed.
32 © Copyright IBM Corporation 2014
Component processes
First, go back to the component, and click the Process
tab.
33 © Copyright IBM Corporation 2014
Component processes
Next, click Create New Process, and name the
process. For example, type Deploy.
34 © Copyright IBM Corporation 2014
Component processes
You also see a few other fields:
Process Type: This value determines how the
component handles updating the inventory in
UrbanCode Deploy. For more information, see
Inventory Management.
Inventory Status: This value is the status to be applied
to the inventory. Typically, you use the default value,
Active.
35 © Copyright IBM Corporation 2014
Component processes
The Default Working Directory: This value is the location
from which the agent runs the process on the target
computer. By default, you see this entry:
${p:resource/work.dir}/${p:component.name}
This location is a property that resolves to the agent
installation location on the target server.
For example, the property resolves to this value:
/opt/ibm-ucd/agent/var/work/exampleComp
36 © Copyright IBM Corporation 2014
Component processes
Required Role: Set this value to restrict access to a
specific role of users who can run this process. For
more information, see the Security module in the
course or in the documentation.
Finally, click Save.
37 © Copyright IBM Corporation 2014
Component processes
Now you can see the process.
38 © Copyright IBM Corporation 2014
Component processes
Next, click the new process. Click the word Deploy.
This action takes you to the graphical design process
editor. Here, you define the automation for the process.
See the next slide.
39 © Copyright IBM Corporation 2014
Component processes
40 © Copyright IBM Corporation 2014
Component processes
To the left you see the Step Palette. The palette
includes the available automation steps to drag onto
the process editor field. The steps that are available are
determined by the plug-ins that have been loaded into
UrbanCode Deploy. A full list of plug-ins can be found
here at this address:
https://developer.ibm.com/urbancode/plugins/
41 © Copyright IBM Corporation 2014
Component processes
To the right, you see the START and FINISH blocks.
These determine the start and end points of the
automation process.
The next step is to create a simple process to copy the
file to the target server.
42 © Copyright IBM Corporation 2014
Component processes
First, find the Download Artifacts step in the palette.
43 © Copyright IBM Corporation 2014
Component processes
Click the Download Artifacts step, and drag it
between the START and FINISH steps.
You see the step editor. This is depicted on the next
slide.
44 © Copyright IBM Corporation 2014
Component processes
45 © Copyright IBM Corporation 2014
Component processes
When you drag a step into the process editor, you can
edit the fields for that step. The Download Artifacts
step is prepopulated with information that you can use.
Simply save this step as is. The fields define the
inclusion of all files to be downloaded from the
component version (**/*).
46 © Copyright IBM Corporation 2014
Component processes
Click Save for the step. You see the step in the middle
of the process designer.
Next, connect the START box to the Download
Artifacts step. Then, connect the Download Artifacts
step to the FINISH box.
47 © Copyright IBM Corporation 2014
Component processes
If you hover your mouse pointer over the START box,
you see a blue circle that includes an arrow.
Click that arrow, and drag it to the
Download Artifacts step to connect the two.
48 © Copyright IBM Corporation 2014
Component processes
The two steps are connected:
49 © Copyright IBM Corporation 2014
Component processes
Next, connect the Download Artifacts step to the
FINISH box in the same way as you did before.
50 © Copyright IBM Corporation 2014
Component processes
Notice that this line has a green circle with a white
check mark inside it. This mark indicates the direction
to go if the Download Artifacts step is complete. You
can click the green circle to cycle through other options.
51 © Copyright IBM Corporation 2014
Component processes
The red circle indicates the direction to go if the
previous step fails. The gray circle indicates
that you want the process to follow a specific
path regardless of whether the step passes or fails.
52 © Copyright IBM Corporation 2014
Component processes
Finally, save the process. To save your process, click
the diskette icon at the top of the step palette.
53 © Copyright IBM Corporation 2014
Component templates
Ideally, you do not want to create new component
processes and duplicate configurations every time that
you add a component. For this reason, there are
component templates. Now that you are familiar with
how to create a component and the working parts of a
component, the next step is to look at component
templates.
54 © Copyright IBM Corporation 2014
Component templates
Click the main Components tab in the upper left, and
then click Templates.
55 © Copyright IBM Corporation 2014
Component templates
You see a complete list of the available component
templates.
56 © Copyright IBM Corporation 2014
Component templates
Click Create New Component Template,
name the template, and then click Save.
57 © Copyright IBM Corporation 2014
Component templates
Examine the component template and notice how
similar it is to a component. The component template
has all the same attributes as a defined component,
except for versions and a few others.
The idea is to design a component template with the
corresponding processes. Then, when you create a
component you can simply choose your template and
import the version.
58 © Copyright IBM Corporation 2014
Component templates
Organizations create templates for processes that are
used throughout teams and organizations. For
example, if an organization deploys applications to
IBM® WebSphere® Application Server or Tomcat, they
might create a WebSphere template and a Tomcat
template. These templates define the processes for
deploying applications to the application servers.
When they want to create a component to be deployed
to WebSphere Application Server or Tomcat, they can
reuse the template.
59 © Copyright IBM Corporation 2014
Summary
You are familiar with how to complete these tasks:
• Import artifacts to create a component
• Add versions to components
• Create component processes
• Create component templates

More Related Content

Viewers also liked

Engineering Consulting - Continuous Improvement
Engineering Consulting - Continuous ImprovementEngineering Consulting - Continuous Improvement
Engineering Consulting - Continuous Improvementalapping
 
Application module slides
Application module slidesApplication module slides
Application module slidesJoanne Scouler
 
Resources Module slides
Resources Module slidesResources Module slides
Resources Module slidesJoanne Scouler
 
Karim Baina Big Data ENSIAS December 2016
Karim Baina Big Data ENSIAS December 2016Karim Baina Big Data ENSIAS December 2016
Karim Baina Big Data ENSIAS December 2016Karim Baïna
 

Viewers also liked (10)

Engineering Consulting - Continuous Improvement
Engineering Consulting - Continuous ImprovementEngineering Consulting - Continuous Improvement
Engineering Consulting - Continuous Improvement
 
Components lab
Components labComponents lab
Components lab
 
Security lab
Security labSecurity lab
Security lab
 
Overview
OverviewOverview
Overview
 
Securitywebinar3 tph3
Securitywebinar3 tph3Securitywebinar3 tph3
Securitywebinar3 tph3
 
Resourceslab fixed
Resourceslab fixedResourceslab fixed
Resourceslab fixed
 
Application module slides
Application module slidesApplication module slides
Application module slides
 
Resources Module slides
Resources Module slidesResources Module slides
Resources Module slides
 
Home Worx
Home WorxHome Worx
Home Worx
 
Karim Baina Big Data ENSIAS December 2016
Karim Baina Big Data ENSIAS December 2016Karim Baina Big Data ENSIAS December 2016
Karim Baina Big Data ENSIAS December 2016
 

Similar to Components module slides

building-a-fdm-application-for-a-hfm-target
 building-a-fdm-application-for-a-hfm-target building-a-fdm-application-for-a-hfm-target
building-a-fdm-application-for-a-hfm-targetSid Mehta
 
UrbanCode Deploy course and product overview slides
UrbanCode Deploy course and product overview slidesUrbanCode Deploy course and product overview slides
UrbanCode Deploy course and product overview slidesIBM Rational software
 
Upgrade to IBM z/OS V2.4 technical actions
Upgrade to IBM z/OS V2.4 technical actionsUpgrade to IBM z/OS V2.4 technical actions
Upgrade to IBM z/OS V2.4 technical actionsMarna Walle
 
2018.02.11 installation guide rhapsody in c and cpp
2018.02.11 installation guide rhapsody in c and cpp2018.02.11 installation guide rhapsody in c and cpp
2018.02.11 installation guide rhapsody in c and cppFrank Braun
 
Bpc 10.0 NW Mass User Management tool
Bpc 10.0 NW Mass User Management toolBpc 10.0 NW Mass User Management tool
Bpc 10.0 NW Mass User Management toolShanmugam Veerichetty
 
Streamlining React Component Development and Sharing with bit.pptx
Streamlining React Component Development and Sharing with bit.pptxStreamlining React Component Development and Sharing with bit.pptx
Streamlining React Component Development and Sharing with bit.pptxShubhamJayswal6
 
Instant chime plugin_installation_guide_for_ibm_sametime_9
Instant chime plugin_installation_guide_for_ibm_sametime_9Instant chime plugin_installation_guide_for_ibm_sametime_9
Instant chime plugin_installation_guide_for_ibm_sametime_9a8us
 
Create software builds with jazz team build
Create software builds with jazz team buildCreate software builds with jazz team build
Create software builds with jazz team buildBill Duncan
 
Getting started with IBM Rational Rhapsody in Ada
Getting started with IBM Rational Rhapsody in AdaGetting started with IBM Rational Rhapsody in Ada
Getting started with IBM Rational Rhapsody in AdaFrank Braun
 
Populating your domino directory or any domino database with tivoli directory...
Populating your domino directory or any domino database with tivoli directory...Populating your domino directory or any domino database with tivoli directory...
Populating your domino directory or any domino database with tivoli directory...dominion
 
Deploying configuring caching
Deploying configuring cachingDeploying configuring caching
Deploying configuring cachingaspnet123
 
Installation of PC-Lint and its using in Visual Studio 2005
Installation of PC-Lint and its using in Visual Studio 2005Installation of PC-Lint and its using in Visual Studio 2005
Installation of PC-Lint and its using in Visual Studio 2005PVS-Studio
 

Similar to Components module slides (20)

UCD components
UCD components UCD components
UCD components
 
Components lab
Components labComponents lab
Components lab
 
building-a-fdm-application-for-a-hfm-target
 building-a-fdm-application-for-a-hfm-target building-a-fdm-application-for-a-hfm-target
building-a-fdm-application-for-a-hfm-target
 
UrbanCode Deploy course and product overview slides
UrbanCode Deploy course and product overview slidesUrbanCode Deploy course and product overview slides
UrbanCode Deploy course and product overview slides
 
Application slides
Application slidesApplication slides
Application slides
 
Homestead demo
Homestead demoHomestead demo
Homestead demo
 
Upgrade to IBM z/OS V2.4 technical actions
Upgrade to IBM z/OS V2.4 technical actionsUpgrade to IBM z/OS V2.4 technical actions
Upgrade to IBM z/OS V2.4 technical actions
 
2018.02.11 installation guide rhapsody in c and cpp
2018.02.11 installation guide rhapsody in c and cpp2018.02.11 installation guide rhapsody in c and cpp
2018.02.11 installation guide rhapsody in c and cpp
 
Bpc 10.0 NW Mass User Management tool
Bpc 10.0 NW Mass User Management toolBpc 10.0 NW Mass User Management tool
Bpc 10.0 NW Mass User Management tool
 
Applications lab
Applications labApplications lab
Applications lab
 
Streamlining React Component Development and Sharing with bit.pptx
Streamlining React Component Development and Sharing with bit.pptxStreamlining React Component Development and Sharing with bit.pptx
Streamlining React Component Development and Sharing with bit.pptx
 
Magento Meetup New Delhi- Console
Magento Meetup New Delhi- ConsoleMagento Meetup New Delhi- Console
Magento Meetup New Delhi- Console
 
Applications lab
Applications lab Applications lab
Applications lab
 
Instant chime plugin_installation_guide_for_ibm_sametime_9
Instant chime plugin_installation_guide_for_ibm_sametime_9Instant chime plugin_installation_guide_for_ibm_sametime_9
Instant chime plugin_installation_guide_for_ibm_sametime_9
 
Create software builds with jazz team build
Create software builds with jazz team buildCreate software builds with jazz team build
Create software builds with jazz team build
 
Getting started with IBM Rational Rhapsody in Ada
Getting started with IBM Rational Rhapsody in AdaGetting started with IBM Rational Rhapsody in Ada
Getting started with IBM Rational Rhapsody in Ada
 
Populating your domino directory or any domino database with tivoli directory...
Populating your domino directory or any domino database with tivoli directory...Populating your domino directory or any domino database with tivoli directory...
Populating your domino directory or any domino database with tivoli directory...
 
Compose Camp - Session2.pdf
Compose Camp - Session2.pdfCompose Camp - Session2.pdf
Compose Camp - Session2.pdf
 
Deploying configuring caching
Deploying configuring cachingDeploying configuring caching
Deploying configuring caching
 
Installation of PC-Lint and its using in Visual Studio 2005
Installation of PC-Lint and its using in Visual Studio 2005Installation of PC-Lint and its using in Visual Studio 2005
Installation of PC-Lint and its using in Visual Studio 2005
 

Recently uploaded

4.16.24 21st Century Movements for Black Lives.pptx
4.16.24 21st Century Movements for Black Lives.pptx4.16.24 21st Century Movements for Black Lives.pptx
4.16.24 21st Century Movements for Black Lives.pptxmary850239
 
Q-Factor General Quiz-7th April 2024, Quiz Club NITW
Q-Factor General Quiz-7th April 2024, Quiz Club NITWQ-Factor General Quiz-7th April 2024, Quiz Club NITW
Q-Factor General Quiz-7th April 2024, Quiz Club NITWQuiz Club NITW
 
Mental Health Awareness - a toolkit for supporting young minds
Mental Health Awareness - a toolkit for supporting young mindsMental Health Awareness - a toolkit for supporting young minds
Mental Health Awareness - a toolkit for supporting young mindsPooky Knightsmith
 
ICS2208 Lecture6 Notes for SL spaces.pdf
ICS2208 Lecture6 Notes for SL spaces.pdfICS2208 Lecture6 Notes for SL spaces.pdf
ICS2208 Lecture6 Notes for SL spaces.pdfVanessa Camilleri
 
Mythology Quiz-4th April 2024, Quiz Club NITW
Mythology Quiz-4th April 2024, Quiz Club NITWMythology Quiz-4th April 2024, Quiz Club NITW
Mythology Quiz-4th April 2024, Quiz Club NITWQuiz Club NITW
 
Q-Factor HISPOL Quiz-6th April 2024, Quiz Club NITW
Q-Factor HISPOL Quiz-6th April 2024, Quiz Club NITWQ-Factor HISPOL Quiz-6th April 2024, Quiz Club NITW
Q-Factor HISPOL Quiz-6th April 2024, Quiz Club NITWQuiz Club NITW
 
How to Fix XML SyntaxError in Odoo the 17
How to Fix XML SyntaxError in Odoo the 17How to Fix XML SyntaxError in Odoo the 17
How to Fix XML SyntaxError in Odoo the 17Celine George
 
Active Learning Strategies (in short ALS).pdf
Active Learning Strategies (in short ALS).pdfActive Learning Strategies (in short ALS).pdf
Active Learning Strategies (in short ALS).pdfPatidar M
 
INTRODUCTION TO CATHOLIC CHRISTOLOGY.pptx
INTRODUCTION TO CATHOLIC CHRISTOLOGY.pptxINTRODUCTION TO CATHOLIC CHRISTOLOGY.pptx
INTRODUCTION TO CATHOLIC CHRISTOLOGY.pptxHumphrey A Beña
 
BIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptx
BIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptxBIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptx
BIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptxSayali Powar
 
How to Make a Duplicate of Your Odoo 17 Database
How to Make a Duplicate of Your Odoo 17 DatabaseHow to Make a Duplicate of Your Odoo 17 Database
How to Make a Duplicate of Your Odoo 17 DatabaseCeline George
 
Concurrency Control in Database Management system
Concurrency Control in Database Management systemConcurrency Control in Database Management system
Concurrency Control in Database Management systemChristalin Nelson
 
Student Profile Sample - We help schools to connect the data they have, with ...
Student Profile Sample - We help schools to connect the data they have, with ...Student Profile Sample - We help schools to connect the data they have, with ...
Student Profile Sample - We help schools to connect the data they have, with ...Seán Kennedy
 
Unraveling Hypertext_ Analyzing Postmodern Elements in Literature.pptx
Unraveling Hypertext_ Analyzing  Postmodern Elements in  Literature.pptxUnraveling Hypertext_ Analyzing  Postmodern Elements in  Literature.pptx
Unraveling Hypertext_ Analyzing Postmodern Elements in Literature.pptxDhatriParmar
 
Reading and Writing Skills 11 quarter 4 melc 1
Reading and Writing Skills 11 quarter 4 melc 1Reading and Writing Skills 11 quarter 4 melc 1
Reading and Writing Skills 11 quarter 4 melc 1GloryAnnCastre1
 
Q4-PPT-Music9_Lesson-1-Romantic-Opera.pptx
Q4-PPT-Music9_Lesson-1-Romantic-Opera.pptxQ4-PPT-Music9_Lesson-1-Romantic-Opera.pptx
Q4-PPT-Music9_Lesson-1-Romantic-Opera.pptxlancelewisportillo
 
Textual Evidence in Reading and Writing of SHS
Textual Evidence in Reading and Writing of SHSTextual Evidence in Reading and Writing of SHS
Textual Evidence in Reading and Writing of SHSMae Pangan
 
Using Grammatical Signals Suitable to Patterns of Idea Development
Using Grammatical Signals Suitable to Patterns of Idea DevelopmentUsing Grammatical Signals Suitable to Patterns of Idea Development
Using Grammatical Signals Suitable to Patterns of Idea Developmentchesterberbo7
 

Recently uploaded (20)

4.16.24 21st Century Movements for Black Lives.pptx
4.16.24 21st Century Movements for Black Lives.pptx4.16.24 21st Century Movements for Black Lives.pptx
4.16.24 21st Century Movements for Black Lives.pptx
 
prashanth updated resume 2024 for Teaching Profession
prashanth updated resume 2024 for Teaching Professionprashanth updated resume 2024 for Teaching Profession
prashanth updated resume 2024 for Teaching Profession
 
Q-Factor General Quiz-7th April 2024, Quiz Club NITW
Q-Factor General Quiz-7th April 2024, Quiz Club NITWQ-Factor General Quiz-7th April 2024, Quiz Club NITW
Q-Factor General Quiz-7th April 2024, Quiz Club NITW
 
Mental Health Awareness - a toolkit for supporting young minds
Mental Health Awareness - a toolkit for supporting young mindsMental Health Awareness - a toolkit for supporting young minds
Mental Health Awareness - a toolkit for supporting young minds
 
ICS2208 Lecture6 Notes for SL spaces.pdf
ICS2208 Lecture6 Notes for SL spaces.pdfICS2208 Lecture6 Notes for SL spaces.pdf
ICS2208 Lecture6 Notes for SL spaces.pdf
 
INCLUSIVE EDUCATION PRACTICES FOR TEACHERS AND TRAINERS.pptx
INCLUSIVE EDUCATION PRACTICES FOR TEACHERS AND TRAINERS.pptxINCLUSIVE EDUCATION PRACTICES FOR TEACHERS AND TRAINERS.pptx
INCLUSIVE EDUCATION PRACTICES FOR TEACHERS AND TRAINERS.pptx
 
Mythology Quiz-4th April 2024, Quiz Club NITW
Mythology Quiz-4th April 2024, Quiz Club NITWMythology Quiz-4th April 2024, Quiz Club NITW
Mythology Quiz-4th April 2024, Quiz Club NITW
 
Q-Factor HISPOL Quiz-6th April 2024, Quiz Club NITW
Q-Factor HISPOL Quiz-6th April 2024, Quiz Club NITWQ-Factor HISPOL Quiz-6th April 2024, Quiz Club NITW
Q-Factor HISPOL Quiz-6th April 2024, Quiz Club NITW
 
How to Fix XML SyntaxError in Odoo the 17
How to Fix XML SyntaxError in Odoo the 17How to Fix XML SyntaxError in Odoo the 17
How to Fix XML SyntaxError in Odoo the 17
 
Active Learning Strategies (in short ALS).pdf
Active Learning Strategies (in short ALS).pdfActive Learning Strategies (in short ALS).pdf
Active Learning Strategies (in short ALS).pdf
 
INTRODUCTION TO CATHOLIC CHRISTOLOGY.pptx
INTRODUCTION TO CATHOLIC CHRISTOLOGY.pptxINTRODUCTION TO CATHOLIC CHRISTOLOGY.pptx
INTRODUCTION TO CATHOLIC CHRISTOLOGY.pptx
 
BIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptx
BIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptxBIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptx
BIOCHEMISTRY-CARBOHYDRATE METABOLISM CHAPTER 2.pptx
 
How to Make a Duplicate of Your Odoo 17 Database
How to Make a Duplicate of Your Odoo 17 DatabaseHow to Make a Duplicate of Your Odoo 17 Database
How to Make a Duplicate of Your Odoo 17 Database
 
Concurrency Control in Database Management system
Concurrency Control in Database Management systemConcurrency Control in Database Management system
Concurrency Control in Database Management system
 
Student Profile Sample - We help schools to connect the data they have, with ...
Student Profile Sample - We help schools to connect the data they have, with ...Student Profile Sample - We help schools to connect the data they have, with ...
Student Profile Sample - We help schools to connect the data they have, with ...
 
Unraveling Hypertext_ Analyzing Postmodern Elements in Literature.pptx
Unraveling Hypertext_ Analyzing  Postmodern Elements in  Literature.pptxUnraveling Hypertext_ Analyzing  Postmodern Elements in  Literature.pptx
Unraveling Hypertext_ Analyzing Postmodern Elements in Literature.pptx
 
Reading and Writing Skills 11 quarter 4 melc 1
Reading and Writing Skills 11 quarter 4 melc 1Reading and Writing Skills 11 quarter 4 melc 1
Reading and Writing Skills 11 quarter 4 melc 1
 
Q4-PPT-Music9_Lesson-1-Romantic-Opera.pptx
Q4-PPT-Music9_Lesson-1-Romantic-Opera.pptxQ4-PPT-Music9_Lesson-1-Romantic-Opera.pptx
Q4-PPT-Music9_Lesson-1-Romantic-Opera.pptx
 
Textual Evidence in Reading and Writing of SHS
Textual Evidence in Reading and Writing of SHSTextual Evidence in Reading and Writing of SHS
Textual Evidence in Reading and Writing of SHS
 
Using Grammatical Signals Suitable to Patterns of Idea Development
Using Grammatical Signals Suitable to Patterns of Idea DevelopmentUsing Grammatical Signals Suitable to Patterns of Idea Development
Using Grammatical Signals Suitable to Patterns of Idea Development
 

Components module slides

  • 1. © Copyright IBM Corporation 2014 Essentials of UrbanCode Deploy QQ147 Components
  • 2. 2 © Copyright IBM Corporation 2014 Agenda What are components? Aspects of a component Creating a component Importing Component versions Component processes Component templates
  • 3. 3 © Copyright IBM Corporation 2014 Objectives After completing this module you are able to: •Import artifacts to create a component •Set environment properties on components •Add versions to the components •Create component processes •Create component templates
  • 4. 4 © Copyright IBM Corporation 2014 What are components? • Components represent deployable items along with user-defined processes that operate on them. For example: • A typical Java-™ Platform, Enterprise Edition application typically has three components (application, database, and web components). • Large applications might have many more.
  • 5. 5 © Copyright IBM Corporation 2014 Features of a component The main features that make up a component are as follows: • Source configuration • Component versions • Component properties • Component processes
  • 6. 6 © Copyright IBM Corporation 2014 Creating a component To create a component: 1. Choose the Components tab. 2. Create New Component.
  • 7. 7 © Copyright IBM Corporation 2014 Creating a component You see this page:
  • 8. 8 © Copyright IBM Corporation 2014 Creating a component The fields on the form: Name: Provide a name for the component. It might reflect the item or tier of the application to be deployed. Description: An optional field to elaborate on the contents of this component.
  • 9. 9 © Copyright IBM Corporation 2014 Creating a component Teams: With this field, you can associate a team with a component. To learn more about teams, see the security module or refer to the documentation. Template: Components can be created from a template. Templates are covered later in this module.
  • 10. 10 © Copyright IBM Corporation 2014 Creating a component Component Type: You can select one of two types of components, Standard and z/OS. Choose z/OS only if this component is intended to be deployed to a mainframe.
  • 11. 11 © Copyright IBM Corporation 2014 Creating a component Source Config Type: In this field, you can define how artifacts are associated with a component. Several available choices come with the product. The available choices are defined by source configuration plug-ins. Each plug-in defines a single type of artifact. You can import artifacts manually or have IBM UrbanCode Deploy import them automatically.
  • 12. 12 © Copyright IBM Corporation 2014 Source config type file system
  • 13. 13 © Copyright IBM Corporation 2014 Creating a component Use Base Path for importing a file system. In the field, you specify where to get the files for importing. The files are moving from the file system to the UrbanCode Deploy artifact repository for storage until they are deployed.
  • 14. 14 © Copyright IBM Corporation 2014 Creating a component Import Versions Automatically: If this option is selected, IBM UrbanCode Deploy polls the Source Config for new versions. Copy to Codestation: Select this option, if you want to store the component versions in the IBM UrbanCode Deploy repository (Codestation).
  • 15. 15 © Copyright IBM Corporation 2014 Creating a component Default Version Type: Two version types are available: full and incremental. Choose Full, if the contents of the component versions represent the entire component. Choose Incremental, if the contents are a subset of the full component. For this course you select Full versions.
  • 16. 16 © Copyright IBM Corporation 2014 Creating a component Import version settings: These settings determine which agent is responsible for importing the versions into IBM UrbanCode Deploy. Typically the first selection is fine.
  • 17. 17 © Copyright IBM Corporation 2014 Creating a component Inherit Cleanup Settings: Select this check box to inherit the cleanup settings that are defined for the server. If not, you must define your own cleanup policies. Run process after creating a new version: Select this check box to launch a process immediately after the IBM UrbanCode Deploy system recognizes a new version.
  • 18. 18 © Copyright IBM Corporation 2014 Creating a component Upon completion, your form looks like this illustration:
  • 19. 19 © Copyright IBM Corporation 2014 Creating a component Next, click Save, and you see your new component.
  • 20. 20 © Copyright IBM Corporation 2014 Version import overview After learning how to create a component, you learn how to create a component version. Components can have many component versions. These versions are deployed later. For the example, the File System Source Config type is used. Before importing the versions, you must check a few things first.
  • 21. 21 © Copyright IBM Corporation 2014 Version import overview Recall that Use the system’s default version import agent/tag was selected earlier in this module. Next, define which agent to use for importing the versions.
  • 22. 22 © Copyright IBM Corporation 2014 Version import overview
  • 23. 23 © Copyright IBM Corporation 2014 Version import overview After you click System Settings, to the left you see General Settings, and near the bottom there is an entry for Agent for Version Imports. Choose the agent to use to import the versions. Typically the agent is on the same computer where the artifacts are located. For help on installing agents, see the product documentation for Agent Installation. Check the next slide for a screen capture.
  • 24. 24 © Copyright IBM Corporation 2014 Version import overview
  • 25. 25 © Copyright IBM Corporation 2014 Version import overview As you can see, we have a file located in this directory: /tmp/artifacts The file is called myApp.ear. This file will be imported into IBM UrbanCode Deploy. Next, you import the file.
  • 26. 26 © Copyright IBM Corporation 2014 Version import overview To import the file, you must return to the Component. Click the Components tab, and then click the component that you created. You see this page:
  • 27. 27 © Copyright IBM Corporation 2014 Version import overview Next, click the Versions tab, and then click Import new Versions. You see this page:
  • 28. 28 © Copyright IBM Corporation 2014 Version import overview In the Version Name field, define the name of the version to import. For example, enter 1.3.0.4. Then, click Save.
  • 29. 29 © Copyright IBM Corporation 2014 Version import overview You see the imported version.
  • 30. 30 © Copyright IBM Corporation 2014 Version import overview By clicking the new version, you see the files that were imported under the Artifacts section.
  • 31. 31 © Copyright IBM Corporation 2014 Component processes After you import a version, you define a process for how to deploy that version. The idea is to create a repeatable process that can be reused as new versions of the component are developed.
  • 32. 32 © Copyright IBM Corporation 2014 Component processes First, go back to the component, and click the Process tab.
  • 33. 33 © Copyright IBM Corporation 2014 Component processes Next, click Create New Process, and name the process. For example, type Deploy.
  • 34. 34 © Copyright IBM Corporation 2014 Component processes You also see a few other fields: Process Type: This value determines how the component handles updating the inventory in UrbanCode Deploy. For more information, see Inventory Management. Inventory Status: This value is the status to be applied to the inventory. Typically, you use the default value, Active.
  • 35. 35 © Copyright IBM Corporation 2014 Component processes The Default Working Directory: This value is the location from which the agent runs the process on the target computer. By default, you see this entry: ${p:resource/work.dir}/${p:component.name} This location is a property that resolves to the agent installation location on the target server. For example, the property resolves to this value: /opt/ibm-ucd/agent/var/work/exampleComp
  • 36. 36 © Copyright IBM Corporation 2014 Component processes Required Role: Set this value to restrict access to a specific role of users who can run this process. For more information, see the Security module in the course or in the documentation. Finally, click Save.
  • 37. 37 © Copyright IBM Corporation 2014 Component processes Now you can see the process.
  • 38. 38 © Copyright IBM Corporation 2014 Component processes Next, click the new process. Click the word Deploy. This action takes you to the graphical design process editor. Here, you define the automation for the process. See the next slide.
  • 39. 39 © Copyright IBM Corporation 2014 Component processes
  • 40. 40 © Copyright IBM Corporation 2014 Component processes To the left you see the Step Palette. The palette includes the available automation steps to drag onto the process editor field. The steps that are available are determined by the plug-ins that have been loaded into UrbanCode Deploy. A full list of plug-ins can be found here at this address: https://developer.ibm.com/urbancode/plugins/
  • 41. 41 © Copyright IBM Corporation 2014 Component processes To the right, you see the START and FINISH blocks. These determine the start and end points of the automation process. The next step is to create a simple process to copy the file to the target server.
  • 42. 42 © Copyright IBM Corporation 2014 Component processes First, find the Download Artifacts step in the palette.
  • 43. 43 © Copyright IBM Corporation 2014 Component processes Click the Download Artifacts step, and drag it between the START and FINISH steps. You see the step editor. This is depicted on the next slide.
  • 44. 44 © Copyright IBM Corporation 2014 Component processes
  • 45. 45 © Copyright IBM Corporation 2014 Component processes When you drag a step into the process editor, you can edit the fields for that step. The Download Artifacts step is prepopulated with information that you can use. Simply save this step as is. The fields define the inclusion of all files to be downloaded from the component version (**/*).
  • 46. 46 © Copyright IBM Corporation 2014 Component processes Click Save for the step. You see the step in the middle of the process designer. Next, connect the START box to the Download Artifacts step. Then, connect the Download Artifacts step to the FINISH box.
  • 47. 47 © Copyright IBM Corporation 2014 Component processes If you hover your mouse pointer over the START box, you see a blue circle that includes an arrow. Click that arrow, and drag it to the Download Artifacts step to connect the two.
  • 48. 48 © Copyright IBM Corporation 2014 Component processes The two steps are connected:
  • 49. 49 © Copyright IBM Corporation 2014 Component processes Next, connect the Download Artifacts step to the FINISH box in the same way as you did before.
  • 50. 50 © Copyright IBM Corporation 2014 Component processes Notice that this line has a green circle with a white check mark inside it. This mark indicates the direction to go if the Download Artifacts step is complete. You can click the green circle to cycle through other options.
  • 51. 51 © Copyright IBM Corporation 2014 Component processes The red circle indicates the direction to go if the previous step fails. The gray circle indicates that you want the process to follow a specific path regardless of whether the step passes or fails.
  • 52. 52 © Copyright IBM Corporation 2014 Component processes Finally, save the process. To save your process, click the diskette icon at the top of the step palette.
  • 53. 53 © Copyright IBM Corporation 2014 Component templates Ideally, you do not want to create new component processes and duplicate configurations every time that you add a component. For this reason, there are component templates. Now that you are familiar with how to create a component and the working parts of a component, the next step is to look at component templates.
  • 54. 54 © Copyright IBM Corporation 2014 Component templates Click the main Components tab in the upper left, and then click Templates.
  • 55. 55 © Copyright IBM Corporation 2014 Component templates You see a complete list of the available component templates.
  • 56. 56 © Copyright IBM Corporation 2014 Component templates Click Create New Component Template, name the template, and then click Save.
  • 57. 57 © Copyright IBM Corporation 2014 Component templates Examine the component template and notice how similar it is to a component. The component template has all the same attributes as a defined component, except for versions and a few others. The idea is to design a component template with the corresponding processes. Then, when you create a component you can simply choose your template and import the version.
  • 58. 58 © Copyright IBM Corporation 2014 Component templates Organizations create templates for processes that are used throughout teams and organizations. For example, if an organization deploys applications to IBM® WebSphere® Application Server or Tomcat, they might create a WebSphere template and a Tomcat template. These templates define the processes for deploying applications to the application servers. When they want to create a component to be deployed to WebSphere Application Server or Tomcat, they can reuse the template.
  • 59. 59 © Copyright IBM Corporation 2014 Summary You are familiar with how to complete these tasks: • Import artifacts to create a component • Add versions to components • Create component processes • Create component templates

Editor's Notes

  1. You define a component – pick source type – opens a plugin – some fields depend on the source configuration plug-in, depends on the stuff you manage. Depends on the type of component – for a web server you supply credentials and URLS – and some of that depends on where artifact will end up. Source config just defines the source type – two flavors of plugins the source config plugin or the automation plugin. The source types used to be baked in now they are plug-ins. Incremental and complete versions. Tom Component properties – can be anything you want it to be – like on resouces – you can have properties on components and resources. Add more properties there. Could be credentials or URLs. Component resource properties – it is a hard thing for new users to get. Component processes – they do 90% of the work on the component. The application does the other 10% of the work on the component. You run an application to deploy a component. Application process does some directing and stuff like that.
  2. Note that components may also be imported into UrbanCode Deploy. In lab we import the components.
  3. After you choose the source config type the form changes depending on the source config plugin you will get different fields. You put stuff in a repository when you create the component – if you use codestation that’s where it goes. Usually a component consists of artifacts. For file type you specify where they find the files. There are about 12 source config types. Only 2 types of component – with zOS the file structures and coding change. But if you are not putting it on the mainframe everything else is the same. Component could be considered as a container for artifacts and the processes that operate on them. If you want to use a template you use it there. Then you get a type of component with pre-defined attributes. With a template you can already have processes pre-defined.
  4. Some fields are shared by all components but some fields are unique depending on the component’s source.
  5. Source Config Type is a way of specifying where you get artifacts. When artifacts are imported automatically, IBM UrbanCode Deploy periodically checks the artifacts for changes. Whenever changes are detected, a new component version is created. You can control how often artifacts are checked. Source could be DB tables—not every artifact is a file.
  6. The example used here is of importing a "file system." By importing a file system, the component gets the files it will use. Import implies movement. That's exactly what is happening. The files are moving from the file system to the UrbanCode Deploy CodeStation artifact repository, where they are stored until they are moved again (deployed). In the deployment process, you specify another directory, which is called a working directory, that defines where to place the artifacts during the deployment.
  7. Usually you don’t import versions automatically – you don’t always want new versions. Interval is set in system settings. You normally do copy to codestation unless you have your own repository. If you use codestation you do this.
  8. There are two types of versions Full and Incremental. With incremental the agent compares the version that is out there with the incremental to see what has changed. Incrementals are used a lot with databases because you do not want to change the whole database. You don’t want to replace a whole database every time you have a change. Incrementals are often the ones that are rolled back.
  9. You have to use some agent to import stuff into codestation. You have to see this up – you pick an agent to use by default. You can pick an agent with a deployment or by default it uses the system agent. If you choose the second you specify the agent – you are forced to pick an agent. 3rd is you have a bunch of agents and if you have a big shot you have several agents and if it doesn’t matter which agent does the work you can select the agent by a tag.
  10. You usually check the clean up box. That is to use the default behavior. This has to do with how long versions are kept in codestation. You can change in system settings. Default is forever. If you have lots of versions that is probably not what you want to do. By default version it is keep every version forever. Run process after creating a new version – not typically used normally you would not do this. but you could run a generic process and the trigger might be any time you import a new version. If you have automatic import – it’s a generic process that is kicked off when there is a new version in codestation. It’s not about deploying.
  11. This is about creating a component version. Earlier you selected don’t select auto version creation. This is how you manually create a version of a component. You defined parameters of a component and here you give it artifacts. You defined where the artifacts were located but you haven’t loaded the artifacts into codestation yet. This is how you get them into codestation. If we had selected auto version import it would have gone to get the versions. It is better to have a manual import to become familiar with process. We do a manual import in the lab.
  12. Artifacts are not always files – could be a database. It will put all the artifacts in codestation and they will all be in component version 1.3.0.4.
  13. There are different types of component processes, deploy is the most commonly used. Uninstall takes a component off a resource. Leaves the component but it takes it off a resource. Operational - does not change actual inventory but changes properties. An operational process does not add anything new to the environment.
  14. After you import a version, you define the process that deploys it. The idea is to create a repeatable process that can be reused as new versions of the component are developed. You can make your own statuses – you could have a complicated deployment that goes through different stages in which case you could create your own statuses and direct UCD to use the different statuses by default there is only one – active.
  15. This is the location where the agent is going to do the work. The property resolves to an actual spot where the component process does the work.
  16. This is security
  17. The plugins on the left are shipped with the product.
  18. You don’t always have to have it. But for a deployment process it is the most used step – agent pulls the artifacts from codestation into the working directory. That’s the location we talked about earlier that the property resolved to.
  19. To the left you see the Step Palette. The palette provides automation steps that you can drag onto the process editor. The available steps are determined by the installed plug-ins. Some plug-ins are shipped with the product and you can install others. A full list of plug-ins can be found here at this address:
  20. This way you can reuse conponent processes on a different component – or you could define the properties for any component you create. It could include the component processes or it could not – doesn’t have to.