Downloaded 64 times
Uploaded byIBM UrbanCode Products
Using UrbanCode Deploy to Migrate to WebSphere Application Server Version 9
The document discusses how IBM UrbanCode Deploy can be utilized to automate the migration and management of WebSphere Application Server configurations. It outlines the benefits, techniques for configuration management, and the steps required to migrate applications without downtime. Additionally, it emphasizes the tool’s capabilities in continuous delivery and integration into cloud environments.
More Related Content
Similar to Using UrbanCode Deploy to Migrate to WebSphere Application Server Version 9
Using UrbanCode Deploy to Migrate to WebSphere Application Server Version 9
- 1. InterConnect 2017 DevOps: Using UrbanCode Deployto Migrate to WebSphere Application Server Version 9 Matthew Alexander 1 4/4/2017
- 2. 2 4/4/2017 Please note IBM’sstatements 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.
- 3.
- 4. IBM UrbanCode Deployis 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?
- 5. Multi-Tier Application ModelsEasy to use Process Designer 5 4/4/2017 Benefits of UrbanCode Deploy
- 6. Deploy to Public,Private, and Hybrid Cloud Inventory to Track What is Where 6 4/4/2017 Benefits of UrbanCode Deploy
- 7. Quality Gates andApprovals Plugins & Integrations 7 4/4/2017 Benefits of UrbanCode Deploy
- 8. Using UrbanCode Deploy withWebSphere Application Server 8 4/4/2017
- 9. - Provides stepsto 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 configurationsas code - Allows versioning and comparison of configuration - Allows configurations to be deployed across environments 10 4/4/2017 WAS Configure Plug-in
- 11. - Includes stepsfor deploying application files - Includes steps to perform administrative tasks 11 4/4/2017 WAS Deploy Plug-in
- 12. The three plug-inswork in concert for continuous delivery 12 4/4/2017 Continuous Delivery
- 13. A Closer Lookat the WAS Configure Plug-in 13 4/4/2017
- 14. - Minimal historyof 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 ConfigurePlugin – 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 timeprocess 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 executedagainst 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 aconfiguration 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 environmentspecific 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 allowsconfiguration 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 ConfigurationSnippet 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. 23 4/4/2017 Configuration Dataas Component Artifacts
- 24. - The ResourceTree 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 ofcomponents may be applied to different environments 25 4/4/2017 Deploying Components
- 26. - Versions ofconfiguration 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
- 27. Challenge: Migrating Configuraitons Across WASVersions Using UrbanCode Deploy 27 4/4/2017
- 28. - Needed tomigrate 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
- 29. Migrate Files (resource adapters, certificates) InstallUCD Agents and Discover WebSphere Topologies 29 4/4/2017 Approach
- 30. Discover Configuration Data fromSource, Templatize, Create Components Add Components to Resource Tree 30 4/4/2017 Approach
- 31. Create and Setup an UrbanCode Deploy Application Deploy the Configuration 31 4/4/2017 Approach
- 32. - The clientwas 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, suchas 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
- 34. Why Use UrbanCode Deployto Migrate WAS Versions? 34 4/4/2017
- 35. - Keep yourcurrent 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. 36 4/4/2017 Where doesUrbanCode Deploy fit in?
- 37. Move to theCloud 37 4/4/2017
- 38. The migration approachmay 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
- 39.
- 40. - WAS Install: https://developer.ibm.com/urbanc ode/plugin/websphere- application-server-install/ -WAS Configure: https://developer.ibm.com/urbanc ode/plugin/websphere- application-server-configure/ - WAS Deploy: https://developer.ibm.com/urbanc ode/plugin/websphere- application-server-deployment/ 40 4/4/2017 UrbanCode Deploy WAS Plug-ins
- 41. - Migration Documentation: https://developer.ibm.com/urbanc ode/docs/migrating-websphere- application-server-versions-ibm- urbancode-deploy-2/ -Example Processes: https://developer.ibm.com/urbanc ode/plugindoc/ibmucd/ibm- configure/1-2/example- processes/ 41 4/4/2017 WAS Configure Plug-in
- 42.
- 43. - DeveloperWorks: http://www- 03.ibm.com/software/products/en /ucdep -UrbanCode’s WebSphere microsite: https://developer.ibm.com/urbanc ode/products/urbancode- deploy/features/managing-ibm- websphere-application-server/ 43 4/4/2017 UrbanCode
- 44. Notices & Disclaimers 444/4/2017
- 45. 45 4/4/2017 Notices anddisclaimers 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 actions the 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. 46 4/4/2017 Notices anddisclaimers 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.
- 47.