Upgrading to IBM WebSphere Portal & Web Content Manager Versions 8.5 and 9

Transcription

1 Upgrading to IBM WebSphere Portal & Web Content Manager Versions 8.5 and Juni 2017 IBM Labor Böblingen 1

2 WebSphere Portal Migration Portal services offerings Content update Agenda Portal 8/WAS855 to Portal 85 Migration Migration Strategies v Enabling New Functionality Resource Links Q&A 2

3 WebSphere Portal Migration The goal of Portal Migration is to move all content, applications, and pages from the source to target environment maintain the same look and feel of the original website. To the end user, the website should look and be functionally the same. New Portal features are installed, but not enabled. Some applications and content may need to be manually updated to meet new specifications. Toleration vs. Exploitation 3

4 Migration to WebSphere Portal v9.0 Migrating from Portal v8.5 v Migrating from Portal v7 & v8 4

5 WebSphere Portal Migration to v9.0 Migration can be performed locally or remote. Migration can be non-destructive and allow both the source and target to run simultaneously. Profile migration requires to migrate to v8.5 CF13 before upgrading to v9.0 v8.5 CF13 v9.0 is supported v8.5 < CF13 v9.0 is not supported v7 v9.0 is not supported v8 v9.0 is not supported Profile migration is not cross platform. V8.5 on Linux v9.0 on Linux is supported V8.5 on Windows v9.0 on Linux is not supported Migration does not allow changing cell or node names. Cell and node name changes should be done as a separate task before or after migration Manual migration might bypass limitations See the Knowledge Center documentation for automatic vs. manual migration considerations 5

6 Migration to V9.0 for V8.5 customers Install CF13 on your existing WP v8.5 installation Add JDK 8 to your WAS CF11+ (optional) Install Portal v9 package via IIM Installs v9 binaries and runs ConfigEngine task enable-v9-features Install WAS /JDK 8 and perform profile migration (optional) Application Server Complexity involved in migrating the profile If WAS 9 features are needed 6

7 Migration to V9.0 for V7.0 or V8.0 customers Current Portal v or v users can upgrade to Portal v9 Manual Migration: Migrate to fresh installation of Portal 9 using Portal Administration tools (xmlaccess, cross version syndication etc.) Automated migration: First migrate to WebSphere Portal 8.5 CF13 Follow the steps on the slide for V8.5 customers 7

8 WebSphere Portal Migration to v8.5 Migration can be performed locally or remote. Migration can be non-destructive and allow both the source and target to run simultaneously WCM Support can be added to a Portal Server during migration. Profile migration is only supported from the two previous main versions. v7 v8.5 is supported v8 v8.5 is supported v6.1 v8.5 is not supported Profile migration is not cross platform. v7 on Linux v8.5 on Linux is supported v7 on Windows v8.5 on Linux is not supported Migration does not allow changing cell or node names. Cell and node name changes should be done as a separate task before or after migration Manual migration might bypass limitations See the Knowledge Center documentation for automatic vs. manual migration considerations 8

9 Before Starting a migration Plan Define complete migration plan for each environment Devise a rollback plan System Migration Path and Development Migration Path should be worked in parallel Check out CTC on Greenhouse to get an idea of the new features Migrate once, then stage other environments Implementing new features Prepare Scope required resources and time Obtain necessary software and hardware Determine which applications need to be updated and begin updating them in a sandbox environment Practice Practice and become familiar with the process Stage a migration practice run using an environment that mimics the production environment 9

10 Portal Services offerings Portal Upgrade Value Assessment Explore new Portal Features with Tech Sales Analyze customer site and usage Receive feedback on how the new version of Portal can improve the business value of your site Portal Upgrade Accelerator on the Cloud Submit your environment to the IBM Cloud Receive an updated Portal Environment 10

11 Manual Migration Do you already have a business process to quickly bring up a new environment that will meet all business requirements? Will you need to create this process after migration? IBM Services can assist with the development of a manual migration process. IBM Support can assist if the execution of specific tasks in a manual migration fail. 11

12 Manual Migration Use available WebSphere and Portal administration tools to bring necessary configuration and applications to the target environment. XMLAccess WASAdmin Cross-version Syndication Target environment will be a clean environment with new features enabled. Requires good portal knowledge Automation helps 12

13 Manual Migration Install WebSphere Portal 8.5 with the most recent fix pack Prepare the target environment Set up security such as LDAP, single-sign-on, SSL Run database-transfer Copy the required files for custom applications Install required applications Transfer the JCR content from previous version Export portlet, pages, PZN rules etc. from the source environment and import to v8.5/v9 environment 13

14 Content update Strategies v Cross version synchronization 14

15 Refreshing Content strategies Prohibit updates during migration Changes are not essential Dual updates in both environments Few changes and strong process management Content refresh Many changes Re-migrates entire JCR Database (not just the updates) Not available in v85 15

16 Refreshing Content strategies Cross-version syndication Only for latest v7 and v8001 fix packs Works in one direction, from source to target 16

17 Cross-version syndication Phase 1: Source Environment Source Authoring Phase 2: Add Target Authoring Source Rendering Source Authoring Source Rendering Target Authoring Phase 3: Add Target Rendering Source Authoring Source Rendering Target Authoring Target Rendering Phase 4:Target Goes Live Target Authoring Target Rendering 17

18 Portal v8.0 running WAS v8.5.5 migration Strategies v 18

19 Migrating from Portal v8.0 running WAS v8.5.5 WASPre/PostUpgrade tasks will not work since WebSphere versions are the same Stage a Portal 8/WAS8 environment and migrate the staging environment In-place migration from Portal 8/WAS855 to Portal 8.Next/WAS Back up the wp_profile_root using manageprofiles. Uninstall WebSphere Portal Version 8 using the IBM Installation Manager. Delete files from the WebSphere Application Server AppServer path Install only the Portal 8.5 binary. Do not create a Portal profile. Restore the wp_profile_root using manageprofiles. Continue with Migration workflow starting at the upgradeconfigengine step. CE 8 v8 Pages WP v8 profile WAS WP 8.5 Bin OS

20 Migration strategies Tiered environment Large cluster environment v Locked down environment 20

21 Migration Strategies Scenario 1: Tiered Environment Scenario 2: Large Cluster Scenario 3: Locked-down Environment 21

22 Tiered Environment Make sure lowest tier standalone server has most current content Migrate lowest tier Build out the rest of the environments using s2p and RB Source Dev Test Prod Target 22

23 Tiered Environment Make sure lowest tier standalone server has most current content Migrate lowest tier Build out the rest of the environments using s2p and RB Source Target Dev Syndication Test Syndication Prod 23

24 Migr. Tiered Environment Make sure lowest tier standalone server has most current content Migrate lowest tier Build out the rest of the environments using s2p and RB Source Target Dev Test Prod Dev 24

25 Tiered Environment Make sure lowest tier standalone server has most current content Migrate lowest tier Build out the rest of the environments using s2p and RB Source Target Dev S2P & Rel. Builder Test Prod Dev Test 25

26 Tiered Environment Make sure lowest tier standalone server has most current content Migrate lowest tier Build out the rest of the environments using s2p and RB Dev Test Prod Source Target Dev Test 26

27 Tiered Environment Make sure lowest tier standalone server has most current content Migrate lowest tier Build out the rest of the environments using s2p and RB Dev Test Prod Source Target Dev S2P & Rel. Builder Test Prod 27 Amplify 2017

28 Tiered Environment Make sure lowest tier standalone server has most current content Migrate lowest tier Build out the rest of the environments using s2p and RB Dev Test Prod Source Target Dev Test Prod 28 Amplify 2017

29 Migration best practices Best practices Introducing new functionality Manages pages v Integrate Watson Content Hub content 29

30 Best Practices Keep migration plan simple and do not introduce unnecessary changes Make sure you have a valid backup of your environment before starting the migration Perform remote migration whenever possible Start early with data migration 30

31 Best Practices Use Staging to Production and ReleaseBuilder to build out the target environments Consider differences in the environments (content, customization, test applications or site libraries etc.) Migrate standalone servers and then build out the clusters Staging to Production and ReleaseBuilder can be used to create a staging environment for migration This strategy is also used for migrating to IBM PureSystems or a Portal Farm from a cluster 31

32 New functionality Apply new Portal85 Theme to Portal Take advantage of CTC 4.4 as a basis for the new v8.5 Theme Update content to take advantage of new WCM Features Approver role is replaced by Reviewer and Draft Creator Role Update Page Templates Enable the 8.5 Site Toolbar for VP's Simple theme 32

33 New functionality Update Custom Themes Educate your content authors about new features Site manager Projects Etc. Etc. 33

34 Managed pages Managed Pages treats pages a content items Enable Managed Pages enable-managed-pages create-virtual-portal-site-nodes create-page-nodes Managed Pages Portal Site Library JCR Database Updating content mappings internalize-content-mappings (plan carefully) Content Content Libraries 34

35 Integrate Watson Content Hub content Requires a tenant on IBM Watson Content Hub as a pre-requisite ConfigEngine task config-ch-integ and/or setup-ch-integ-vp creates the required configuration items for the WebSphere Portal installation Credentials to access IBM Watson Content Hub are stored in credential slot dx2dch You need to grant users who need to pick assets access to this credential vault Need to restart WebSphere Portal JVMs afterwards 35

36 Integrate Watson Content Hub content New theme profile (Content Hub Profile) contains the new theme module dch_module which required in the current theme for asset-picker to work In edit mode and select the new Content Hub Page component to find a selection to add a file, video or image to the page Drag any of the page components onto the page Select an asset by clicking the Select File, Selecting Image or Selecting Video buttons The asset references are stored as WCM content based on the Content Hub authoring template 36

37 IBM Watson Content Hub Conversion Tool Command line tool that converts WCM content to the WCH format 37 Amplify Watson 2017 Customer Engagement

38 IBM Watson Content Hub Conversion Tool Saves content, authoring templates, and any files or images referenced by the content hosted in WCM to the local file system Provides analysis on the content and authoring types How many content items implement a specific type? Does a type have fields to do not translate to WCH easily? Converts content and authoring template to the WCH content and type format No presentation layer (yet) Use your content in a central content store to reuse in multiple apps 38

39 IBM Watson Content Hub Conversion Tool Leverages IBM Watson Content Hub Developer Tools (wchtools) to push the converted content and types to WCH The converted content will contain all of the original fields and values that were in the origin Available at: 39

40 Begin your 30-day free trial of Watson Content Hub today 40 Amplify Watson 2017 Customer Engagement

41 For Additional Information IBM Digital Experience Solutions IBM Digital Experience, WebSphere Portal and Web Content Manager Kowledge Center IBM Digital Experience Demonstrations IBM Digital Experience Developer 41

42 For Additional Information IBM Solutions IBM Digital Experience Badges Program WebSphere Portal automated vs. Manual migration rate/mig_consider_avm.html 42

43 For Additional Information WebSphere Portal migration from v6.1 to v8.5 Watson Content Hub Integration into Digital Experience version 9 Installing WebSphere Portal V9 on Portal 8.5 CF

44 For Additional Information A Step-By-Step Guide to performing a standalone WebSphere Portal 9.0 installation 44

45 Vielen Dank! Was Sie interessieren könnte: Docker and Digital Experience "Trends and Best Practices" WCH JumpStart #1 & #2 Hermann Huebler, IBM Digital Experience Lab Services 45 Footer 6/22/2017