using urbancode deploy to migrate to websphere application server version 9
TRANSCRIPT
InterConnect2017
DevOps: Using UrbanCodeDeploy to Migrate to WebSphere Application Server Version 9
Matthew Alexander
1 4/4/2017
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 inthe 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.
Introduction to UrbanCode Deploy
3 4/4/2017
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?
Multi-Tier Application Models Easy to use Process Designer
5 4/4/2017
Benefits of UrbanCode Deploy
Deploy to Public, Private, and Hybrid Cloud
Inventory to Track What is Where
6 4/4/2017
Benefits of UrbanCode Deploy
Quality Gates and Approvals Plugins & Integrations
7 4/4/2017
Benefits of UrbanCode Deploy
Using UrbanCode Deploy with WebSphere Application Server
8 4/4/2017
- 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
- 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
- Includes steps for deploying application files
- Includes steps to perform administrative tasks
11 4/4/2017
WAS Deploy Plug-in
The three plug-ins work in concert for continuous delivery
12 4/4/2017
Continuous Delivery
A Closer Look at the WAS Configure Plug-in
13 4/4/2017
- 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 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
- 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
- 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
- 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
- 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
- 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
- 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
- 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
23 4/4/2017
Configuration Data as Component Artifacts
- 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
Different versions of components may be applied to different environments
25 4/4/2017
Deploying Components
- 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
Challenge: Migrating Configuraitons Across WAS Versions Using UrbanCode Deploy
27 4/4/2017
- 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 UrbanCodeDeploy as a migration tool
28 4/4/2017
An IBM Client’s Challenge
Migrate Files (resource adapters, certificates)
Install UCD Agents and Discover WebSphere Topologies
29 4/4/2017
Approach
Discover Configuration Data from Source, Templatize, Create Components
Add Components to Resource Tree
30 4/4/2017
Approach
Create and Set up an UrbanCode Deploy Application
Deploy the Configuration
31 4/4/2017
Approach
- The client was able to successfully migrate their WAS configuration using UrbanCodeDeploy
- The client then proceeded to migrate applications
- The client will continue to use UrbanCode Deploy to manage WebSphere
32 4/4/2017
Result
- 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
Why Use UrbanCodeDeploy to Migrate WAS Versions?
34 4/4/2017
- 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
36 4/4/2017
Where does UrbanCode Deploy fit in?
Move to the Cloud
37 4/4/2017
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
Resources
39 4/4/2017
- WAS Install: https://developer.ibm.com/urbancode/plugin/websphere-application-server-install/
- WAS Configure: https://developer.ibm.com/urbancode/plugin/websphere-application-server-configure/
- WAS Deploy: https://developer.ibm.com/urbancode/plugin/websphere-application-server-deployment/
40 4/4/2017
UrbanCode Deploy WAS Plug-ins
- Migration Documentation: https://developer.ibm.com/urbancode/docs/migrating-websphere-application-server-versions-ibm-urbancode-deploy-2/
- Example Processes: https://developer.ibm.com/urbancode/plugindoc/ibmucd/ibm-configure/1-2/example-processes/
41 4/4/2017
WAS Configure Plug-in
- Webinar: https://developer.ibm.com/urbancode/docs/may-17-webinar-deploying-to-and-configuring-websphere-application-server-with-urbancode-deploy/
- Usage: https://developer.ibm.com/urbancode/plugindoc/ibmucd/ibm-configure/1-2/usage/
42 4/4/2017
WAS Configure Plug-in
- DeveloperWorks: http://www-03.ibm.com/software/products/en/ucdep
- UrbanCode’s WebSphere microsite: https://developer.ibm.com/urbancode/products/urbancode-deploy/features/managing-ibm-websphere-application-server/
43 4/4/2017
UrbanCode
Notices & Disclaimers
44 4/4/2017
45 4/4/2017
Notices and disclaimers
Copyright © 2017 by International Business Machines Corporation (IBM). No part of this document may be reproduced or transmitted in any form without written permission from IBM.
U.S. Government Users Restricted Rights — use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM.
Information in these presentations (including information relating to products that have not yet been announced by IBM) has been reviewed for accuracy as of the date of initial publication and could include unintentional technical or typographical errors. IBM shall have no responsibility to update this information. This document is distributed “as is” without any warranty, either express or implied. In no event shall IBM be liable for any damage arising from the use of this information, including but not limited to, loss of data, business interruption, loss of profit or loss of opportunity. IBM products and services are warranted according to the terms and conditions of the agreements under which they are provided.
IBM products are manufactured from new parts or new and used parts. In some cases, a product may not be new and may have been previously installed. Regardless, our warranty terms apply.”
Any statements regarding IBM's future direction, intent or product plans are subject to change or withdrawal without notice.
Performance data contained herein was generally obtained in a controlled, isolated environments. Customer examples are presented as illustrations of how those customers have used IBM products and
the results they may have achieved. Actual performance, cost, savings or other results in other operating environments may vary.
References in this document to IBM products, programs, or services does not imply that IBM intends to make such products, programs or services available in all countries in which IBM operates or does business.
Workshops, sessions and associated materials may have been prepared by independent session speakers, and do not necessarily reflect the views of IBM. All materials and discussions are provided for informational purposes only, and are neither intended to, nor shall constitute legal or other guidance or advice to any individual participant or their specific situation.
It is the customer’s responsibility to insure its own compliance with legal requirements and to obtain advice of competent legal counsel as to the identification and interpretation of any relevant laws and regulatory requirements that may affect the customer’s business and any actionsthe customer may need to take to comply with such laws. IBM does not provide legal advice or represent or warrant that its services or products will ensure that the customer is in compliance with any law.
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.
InterConnect2017
47 4/4/2017