IBM UrbanCode Deploy is an enterprise application deployment automation utility that combines ease-of-use with fine-grain control for managing the deployment of applications through multiple environments. IBM UrbanCode automates and manages the deployments of business applications made of many component pieces such as Web Services, databases, content, CICS and mobile apps. Through automation, costly errors and manual labor are drastically reduced, time-to-market is accelerated, cost is driven down and risk is lowered. UrbanCode Deploy also provides capabilieis for designing and deploying full-stack environments on cloud and updating configurations for existing cloud environments.In the related products listing on this page we have provided subset of the strongest interactions with other IBM tools. However, IBM UrbanCode Deploy has over 180 different plugins across various types and discipline areas to provide extensive integrations. The UrbanCode family of products as whole has over 400 plugins.
2. 2 4/4/2017
Please note
IBM’s statements regarding its plans, directions, and intent
are subject to change or withdrawal without notice at IBM’s
sole discretion.
Information regarding potential future products is intended to
outline our general product direction and it should not be relied
on in making a purchasing decision.
The information mentioned regarding potential future products
is not a commitment, promise, or legal obligation to deliver
any material, code or functionality. Information about potential
future products may not be incorporated into any contract.
The development, release, and timing of any future features
or functionality described for our products remains at our sole
discretion.
Performance is based on measurements and projections
using standard IBM benchmarks in a controlled environment.
The actual throughput or performance that any user will
experience will vary depending upon many factors, including
considerations such as the amount of multiprogramming in
the user’s job stream, the I/O configuration, the storage
configuration, and the workload processed. Therefore, no
assurance can be given that an individual user will achieve
results similar to those stated here.
4. IBM UrbanCode Deploy is a tool for automating application deployments through
your environments. It is designed to facilitate rapid feedback and continuous
delivery in agile development while providing the audit trails, versioning and
approvals needed in production.
4 4/4/2017
What is UrbanCode Deploy?
9. - Provides steps to assist with
installing WebSphere
- Includes an example
application showing a standard
installation of WAS Network
Deployment
9 4/4/2017
WAS Install Plug-in
10. - Manages WebSphere
configurations as code
- Allows versioning and
comparison of configuration
- Allows configurations to be
deployed across environments
10 4/4/2017
WAS Configure Plug-in
11. - Includes steps for deploying
application files
- Includes steps to perform
administrative tasks
11 4/4/2017
WAS Deploy Plug-in
12. The three plug-ins work in concert for continuous delivery
12 4/4/2017
Continuous Delivery
13. A Closer Look at the
WAS Configure Plug-in
13 4/4/2017
14. - Minimal history of configuration
changes
- Manual comparison of
configuration values across
environments
- Automated deployments may
require manual resources to
update configuration
- Application configuration
complexity outgrows human
ability to manage
14 4/4/2017
Challenges with Managing WAS Configurations
15. 15 4/4/2017
WAS Configure Plugin – High Level Flow
Artifact Library
Application
EAREAR
WARWAR
DBDB
WAS
Config
Templates
Exemplar
WAS Cell
Plugin
Import
configuration
WAS Configuration Template Creation
+ Templates
Assembled
PROD
QA
DEV
Deploy and promote application and
configuration across environments
1
2
3
4
16. - JSON format
- May be managed as component version artifacts in UrbanCode Deploy
- May be managed at different scopes (Cell, Node, Server, Cluster)
16 4/4/2017
Configuration Data
17. - One time process to create
baseline configuration
- Steps are provided to assist in
creating templates
- Sample processes are provided
to create templates and
components
17 4/4/2017
Template Creation
18. - Is executed against an existing
WebSphere environment
- Retrieves configuration from
WebSphere
- Stores the configuration data in
one JSON file
18 4/4/2017
Configuration Discovery Step
19. - Takes a configuration data file
and splits it into multiple data
files representing different
WebSphere scopes
- Configuration files will be
created for the Cell, Nodes,
Servers, and Clusters
19 4/4/2017
Extract Configuration Data Step
20. - Replaces environment specific
values in the configuration data
with tokens
- Steps exist to templatize Cell,
Node, Server, and Cluster
configuration data
- Users have the option to
replace additional values with
tokens
20 4/4/2017
Templatize Configuration Data Steps
21. - Tokenization allows configuration data to be environment independent
- Tokens are replaced with specified values before applying configuration data
- Additional values may be tokenized
21 4/4/2017
Templatized Configuration Data
22. - Create Configuration Snippet
step extracts entries from
configuration data
- Allows for access control to
who may change which
configuration
- Snippets may be templatized
further
- Snippets may be merged with
base configuration files at apply
time
22 4/4/2017
Breaking Down Configuration Data Further
24. - The Resource Tree inside
UrbanCode Deploy shows a
representation of your WAS
topology
- UrbanCode Deploy is able to
discover and display the
topology
- Components are added to the
resource tree under the
resources they manage
24 4/4/2017
Resource Tree
25. Different versions of components may be applied to different environments
25 4/4/2017
Deploying Components
26. - Versions of configuration data
may be compared to discover
differences
- Configuration data may be
compared to the actual
configuration on WebSphere, to
detect configuration drift
- Automated processes may be
created to alert users of
configuration drift
26 4/4/2017
Comparing Configurations
28. - Needed to migrate from WAS 7
to WAS 8.5.5
- Stopping WebSphere was not
acceptable
- Struggled for over a year to
complete the migration
- Desired to use UrbanCode
Deploy as a migration tool
28 4/4/2017
An IBM Client’s Challenge
31. Create and Set up an
UrbanCode Deploy
Application
Deploy the Configuration
31 4/4/2017
Approach
32. - The client was able to
successfully migrate their WAS
configuration using UrbanCode
Deploy
- The client then proceeded to
migrate applications
- The client will continue to use
UrbanCode Deploy to manage
WebSphere
32 4/4/2017
Result
33. - Files, such as resource adapter
.rar files, must be installed on
the target environment
- Configuration data may contain
file system paths which differ
across environments
- The User Defined Tokenization
field of the templatize steps
may be used to update values
33 4/4/2017
Considerations
35. - Keep your current WAS
environment running
- Perform migration in a timely
manner
- After migration, may continue
using UrbanCode Deploy to
manage WAS in a DevOps
scenario
- If performing migration using
WAS tools, may still use
UrbanCode Deploy to compare
before/after configuration
35 4/4/2017
Benefits
38. The migration approach may be
used to move to the cloud
- Capture Configuration Data
- Install WAS on the Cloud
- Apply Configuration Data
38 4/4/2017
Lift and Shift to the Cloud
46. 46 4/4/2017
Notices and disclaimers
continued
Information concerning non-IBM products was obtained from the
suppliers of those products, their published announcements or other
publicly available sources. IBM has not tested those products in
connection with this publication and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be
addressed to the suppliers of those products. IBM does not warrant the
quality of any third-party products, or the ability of any such third-party
products to interoperate with IBM’s products. IBM expressly disclaims
all warranties, expressed or implied, including but not limited to, the
implied warranties of merchantability and fitness for a particular,
purpose.
The provision of the information contained herein is not intended to, and
does not, grant any right or license under any IBM patents, copyrights,
trademarks or other intellectual property right.
IBM, the IBM logo, ibm.com, Aspera®, Bluemix, Blueworks Live, CICS,
Clearcase, Cognos®, DOORS®, Emptoris®, Enterprise Document
Management System™, FASP®, FileNet®, Global Business Services®,
Global Technology Services®, IBM ExperienceOne™, IBM SmartCloud®,
IBM Social Business®, Information on Demand, ILOG, Maximo®,
MQIntegrator®, MQSeries®, Netcool®, OMEGAMON, OpenPower,
PureAnalytics™, PureApplication®, pureCluster™, PureCoverage®,
PureData®, PureExperience®, PureFlex®, pureQuery®, pureScale®,
PureSystems®, QRadar®, Rational®, Rhapsody®, Smarter Commerce®,
SoDA, SPSS, Sterling Commerce®, StoredIQ, Tealeaf®, Tivoli® Trusteer®,
Unica®, urban{code}®, Watson, WebSphere®, Worklight®, X-Force® and
System z® Z/OS, are trademarks of International Business Machines
Corporation, registered in many jurisdictions worldwide. Other product
and service names might be trademarks of IBM or other companies. A
current list of IBM trademarks is available on the Web at "Copyright and
trademark information" at: www.ibm.com/legal/copytrade.shtml.