Professional Documents
Culture Documents
April 2011
This document applies to webMethods Product Suite Version 7.1 and 7.2 and to all subsequent releases. Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions. Copyright 2007-2011 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, United States of America, and/or their licensors. The name Software AG, webMethods, and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA, Inc. and/or their licensors. Other company and product names mentioned herein may be trademarks of their respective owners. Use of this software is subject to adherence to Software AGs licensing conditions and terms. These terms are part of the product documentation, located at http://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s). This software may include portions of third-party products. For third-party copyright notices and license terms, please refer to "License Texts, Copyright Notices and Disclaimers of Third Party Products." This document is part of the product documentation, located at http://documentation.softwareag.com/legal/ and/or in the root installation directory of the licensed product(s).
Table of Contents
About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Documentation Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Online Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1. Migrating from 6.1 to 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Back Up the 6.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install webMethods Product Suite 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . Migrate webMethods Broker 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.2 Broker Servers and 6.1 Broker Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 Broker Servers and 7.1.2 Broker Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up Broker Server to Use 6.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate if You Do Not Have Gateways and Territories . . . . . . . . . . . . . . . . . . . . . Migrate if You Have Gateways and Territories . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure 7.1.2 Broker Server to Use the 6.1 Combined Storage Session . . . . . . Configure the Forwarding Behavior of a Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate JMS Provider 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.1 JMS Clients and Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Granularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Message Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Update JMSAdmin Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Bound Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modify Connection Factory Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modify Topic and Queue Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modify Client Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Modify Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New JMSAdmin Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JMSAdmin Command Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Other Changes to Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Convert JMS Client APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . AdminFactory Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . QueueAdmin Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . QueueConnectionFactoryAdmin Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TopicAdmin Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . TopicConnectionFactoryAdmin Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9 9 10 11 13 14 14 15 16 18 19 19 19 19 20 20 21 22 24 25 25 25 25 25 26 26 26 27 27 28 28 28 29 31 31 31 31 32 33 33
Table of Contents
TopicConnectionFactory Client ID Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Library Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Integration Server 6.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Integration Server Database Components . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the 6.1 Repository Server Data to IS Internal . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Configuration Data and User-Created Packages . . . . . . . . . . . . . . . . . . . . . . . Configure Integration Server 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Trading Networks 6.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Trading Networks Database Components . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the tspace Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate 6.1.5 Business Process Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2. Migrating from 6.5 to 7.1.2 and 7.1.3 or Designer 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Back Up the 6.5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install webMethods Product Suite 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . Migrate webMethods Broker 6.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7.1.2 Broker Servers and 6.5.2 Broker Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . 6.5.2 Broker Servers and 7.1.2 Broker Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up the 7.1.2 Broker Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate if You Do Not Have Gateways and Territories . . . . . . . . . . . . . . . . . . . . . Migrate if You Have Gateways and Territories . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure the 7.1.2 Broker Server to Use 6.5.2 Storage . . . . . . . . . . . . . . . . . . . . Migrate Java Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Command-Line Utilities Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Broker Java API Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changed Methods in BrokerConnectionDescriptor Class . . . . . . . . . . . . . . . New Methods in BrokerConnectionDescriptor Class . . . . . . . . . . . . . . . . . . . New Methods in BrokerServerClient Class . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate C Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changed Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Removed Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate JMS 6.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Update JMSAdmin Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . JMSAdmin Command Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Convert JMS Client APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Changed Method in WmJMSAdminFactory Class . . . . . . . . . . . . . . . . . . . . . . . . . Deprecated WmFileMessage Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
34 34 35 35 36 37 37 39 39 39 40 41 41 42 45 46 47 48 48 51 52 52 52 52 52 53 54 55 57 57 57 57 58 58 59 59 59 59 59 60 60 61 61 61
Table of Contents
New Methods in WmJMSConfig Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Fields in WmConnectionFactory Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . New Methods in WmConnectionFactory Class . . . . . . . . . . . . . . . . . . . . . . . . . . . New Method in WmQueueConnectionFactory Class . . . . . . . . . . . . . . . . . . . . . . New Method in WmTopicConnectionFactory Class . . . . . . . . . . . . . . . . . . . . . . . Library Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Integration Server 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Configuration Data and User-Created Packages . . . . . . . . . . . . . . . . . . . . . . Migrate the 6.5 Repository Server Data to IS Internal . . . . . . . . . . . . . . . . . . . . . . . . . Configure Integration Server 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Check Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Integration Server Database Components . . . . . . . . . . . . . . . . . . . . . . . . Migrate Trading Networks 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Trading Networks Properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Trading Networks Database Components . . . . . . . . . . . . . . . . . . . . . . . . . Migrate 6.5.x Custom Portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate 6.5.1 Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Design-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Run-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Process Audit Log Database Component . . . . . . . . . . . . . . . . . . Migrate the Process Tracking Store Database Component . . . . . . . . . . . . . . Complete the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Optimize 6.5.1 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Optimize 6.5 SP2 to Optimize 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install Optimize 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Transform Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Analysis and Process Tracker Database Components . . . . . . . . . . . Create Storage and Grant Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare DB2 for Linux, UNIX, Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Analysis Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Process Tracker Database Component . . . . . . . . . . . . . . . . . . . Start the 7.0 SP2 Analytic Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Drop the 7.0 SP2 Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Optimize 7.0 SP2 to Optimize 7.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Define Rule Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Analysis and Process Tracker Database Components . . . . . . . . . . . Create a New Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3. Migrating from Fabric 7 to 7.1.2 or Designer 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Back Up the Fabric 7 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install webMethods Product Suite 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
62 62 62 62 63 63 63 63 64 65 66 66 67 67 68 69 70 70 71 71 71 72 72 73 73 74 74 74 76 76 76 77 77 78 78 78 78 78 79 81 82 83 84 84
Table of Contents
Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . Migrate webMethods Broker and JMS 6.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Integration Server 6.5 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Trading Networks 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate My webMethods Server 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate 7.0 SP2 Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Design-Time Data to Designer 7.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Design-Time Data to Designer 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Export Process Models and Logical Server Definitions from Designer 7.0 SP2 . . Import Process Models and Logical Server Definitions into Designer 7.2 . . . . . . . Migrate Run-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Start the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate 7.0 SP2 Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Design-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Export Task Projects from Designer 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . Import 7.0 SP2 Task Projects into Designer 7.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Run-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Metadata Library 7.0 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Optimize 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Optimize Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a New Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Data Purge Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Deployer 7.0 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4. Upgrading from 7.x to 7.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Back Up the Earlier 7.x Installation and Remove Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare to Upgrade a My webMethods Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare to Upgrade a 7.1.1 My webMethods Server Cluster . . . . . . . . . . . . . . . . . . . . Prepare to Upgrade a 7.1.2 My webMethods Server Cluster . . . . . . . . . . . . . . . . . . . . Install webMethods Product Suite 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Integration Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Integration Server 7.1.2 or 7.1.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Convert JAX-RPC Handlers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Integration Server 7.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Increase PermGen Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Update the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Convert JAX-RPC Handlers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Trading Networks Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
87 87 87 88 88 89 89 90 90 91 92 92 93 94 94 95 95 95 96 96 97 97 97 98 99 101 102 103 103 104 104 105 105 106 106 107 108 108 108 108 109 109 110 110
Table of Contents
Migrate Trading Networks Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Set Up Trading Networks to Work with My webMethods Server . . . . . . . . . . . . . . . . . Complete the Metadata Library Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Designer Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the My webMethods Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate My webMethods Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade a My webMethods Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Design-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Run-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Optimize Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Configure Infrastructure Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Optimize Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Create a New Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate the Data Purge Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Deployer Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
110 111 112 112 113 113 114 116 116 116 117 117 117 118 118 119
Table of Contents
Document Conventions
Convention Bold Narrow font Description Identifies elements on a user interface. Identifies storage locations for services on webMethods Integration Server, using the convention folder.subfolder:service.
Description Identifies keyboard keys. Keys you must press simultaneously are joined with a plus sign (+). Identifies variables for which you must supply values specific to your own situation or environment. Identifies new terms the first time they occur in the text. Identifies text you must type or messages displayed by the system. Indicates a set of choices from which you must choose one. Type only the information inside the curly braces. Do not type the { } symbols. Separates two mutually exclusive choices in a syntax line. Type one of these choices. Do not type the | symbol. Indicates one or more options. Type only the information inside the square brackets. Do not type the [ ] symbols. Indicates that you can type multiple options of the same type. Type only the information. Do not type the ellipsis (...).
Monospace font
{} | [] ...
Documentation Installation
You can download the product documentation using the Installer. Depending on the release of the webMethods product suite, the location of the downloaded documentation will be as shown in the table below. For webMethods... 6.x 7.x 8.x The documentation is downloaded to... The installation directory of each product. A central directory named _documentation in the main installation directory (webMethods by default). A central directory named _documentation in the main installation directory (Software AG by default).
10
Online Information
You can find additional information about Software AG products at the locations listed below. Note: The Empower Product Support Web site and the Software AG Documentation Web site replace Software AG ServLine24 and webMethods Advantage. If you want to... Access the latest version of product documentation. Find information about product releases and tools that you can use to resolve problems. See the Knowledge Center to: Read technical articles and papers. Download fixes and service packs. Learn about critical alerts. See the Products area to: Download products. Download certified samples. Get information about product availability. Access documentation for all supported versions of products. Submit feature/enhancement requests. Go to... Software AG Documentation Web site http://documentation.softwareag.com Empower Product Support Web site https://empower.softwareag.com
11
If you want to... Access additional articles, demos, and tutorials. Obtain technical information, useful resources, and online discussion forums, moderated by Software AG professionals, to help you do more with Software AG technology. Use the online discussion forums to exchange best practices and chat with other experts. Expand your knowledge about product documentation, code samples, articles, online seminars, and tutorials. Link to external Web sites that discuss open standards and many Web technology topics. See how other customers are streamlining their operations with technology from Software AG.
12
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Back Up the 6.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install webMethods Product Suite 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate webMethods Broker 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate JMS Provider 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Integration Server 6.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Trading Networks 6.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate 6.1.5 Business Process Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
13
Overview
This upgrade procedure explains how to upgrade your 6.1.x products to webMethods product suite 7.1.2 and 7.1.3, and how to migrate the following: Data from:
webMethods Broker and JMS Provider 6.1 or 6.1 SPx Integration Server 6.1 or 6.1 SPx Trading Networks 6.1 or 6.1 SPx
Business process models from webMethods Modeler 6.1.5 There is no procedure for migrating data from the 6.1.x products listed below to webMethods product suite 7.1.2 and 7.1.3. However, you can upgrade those 6.1.x products to the indicated 7.1.2 and 7.1.3 products, all of which contain considerably more functionality than their 6.1.x counterparts. 6.1.x Product webMethods Manager Console 6.1.5 webMethods Manager Server 6.1.5 Optimize 6.1.5 PRT 6.1 or 6.1.5 webMethods Workflow 6.1.5 webMethods Product Suite 7.1.2 Replacement Optimize for Infrastructure 7.1.2 Optimize for Process 7.1.2 Process Engine 7.1.2 Designer 7.1.2 and Task Engine 7.1.3
Important! You must upgrade all of your products at the same time; you cannot use 6.1 products with 7.1.x products. You must upgrade products and migrate data in the order presented in this chapter. Software AG strongly recommends that you upgrade and migrate in a controlled test environment and test that installation for proper operation before upgrading and migrating your production environments.
14
3 4
Back up the entire 6.1 webMethods installation directory on each machine, and back up your 6.1 webMethods databases as instructed by your RDBMS vendor. For each Integration Server 6.1, do the following: a b Start Integration Server and open Integration Server Administrator. Record port settings and prepare the ports for migration, as follows: 1 2 Go to the SecurityPorts page and print the page. For each HTTPS, Proxy, HTTPS Proxy, SOCK, and SSL SOCK port, click the link in the Port column to display the View type Port Details page and print the page. Reverse invoke was rearchitected in Integration Server 7.1.2 and load balancing was removed, so you cannot migrate ports that relate to those features. Delete Proxy, HTTPS Proxy, SOCK, SSL SOCK, Registration, and Load Balancer ports from the list by clicking in the row for each port. Record the name of the package that is associated with each remaining port. Go to the PackagesPublishingCreate and Delete Releases page. Click Create Release for a user-created package. Scroll to the bottom of the page that appears and click Create Release. Integration Server creates a zip file containing the package and places the zip file in the Integration Server_6.1_directory\replicate\outbound directory. Repeat these steps for each user-created package.
4 c 1 2 3
4 d e f
Record your imported client certificate and user mappings by going to the SecurityCertificatesConfigure Client Certificates page and printing it. Record your Broker connection by going to the SettingsBrokerEdit Broker Settings page and printing it. If you have configured LDAP on the Integration Server, record your LDAP configuration by going to the SecurityUsers & GroupsJNDI Settings page and printing it. If the Integration Server is part of a cluster, record all the cluster information by going to the SettingsClustering page and printing it.
g 5
Shut down Integration Server. Do not shut down the Repository Server; make sure it continues running until all data has been migrated.
15
16
When the installer asks for product configuration information, do the following: Product Trading Networks Integration Server Action Point the database connection at the 6.1 Trading Networks database component. If you choose to use an external RDBMS (as opposed to the embedded database), point the database connection at the 6.1 IS Core Audit Log database component if it exists. Otherwise, point at the external RDBMS you will use for Integration Server 7.1.3 data (see the next bullet, below). If you want to begin using separate storage sessions, create a Broker Server configuration. The installer requires your webMethods Broker license key to create a Broker Server configuration; make sure to supply the 7.1.2 license key. The installer will also create separate storage sessions for the 7.1.2 Broker Server. Later, you will migrate the 6.5.2 metadata to the 7.1.2 Broker Server. If you want to continue using your 6.1 combined storage session, do not create a Broker Server configuration. Later, you will create the 7.1.2 Broker Server (but not the separate storage sessions) and configure it to use the 6.5.2 storage. After product installation is complete, create the webMethods product suite 7.1.2 database components that the table below indicates you should create; for instructions, see webMethods Installation Guide 7.1. Do not create database components that the table indicates you should not create; you will migrate the 6.1 database components to 7.1.2 later in this procedure. Note: For 7.1.3 products, you will still create 7.1.2 database components. If you are migrating... Integration Server Do the following... Do not create the IS Core Audit Log and Document History database components. If you chose the embedded database during installation, or if you stored 6.1 cross-referencing data in the Cross Reference database component, do not create a Cross Reference database component. If you chose an external RDBMS during installation and want to store crossreferencing data in it, create the Cross Reference database component.
webMethod s Broker
17
Do the following... If you chose an external RDBMS during installation, create the IS Internal and Distributed Locking database components. If you are using Oracle or DB2 for Linux, UNIX, Windows,first create storage and a tablespace directory for IS Internal by running this command:
dbConfigurator.{bat|sh} -a create -d {oracle|db2luw} -c storage -v latest -l db_server_URL -u existing_db_user -p password -au db_admin_user -ap password -t full_path_to_new_tablespace_directory
Oracle example:
dbConfigurator.bat -a create -d oracle -c storage -v latest -l jdbc:wm:oracle://localhost:1521;ServiceName=ORCL -u webmuser -p webmuser -au admin_user -ap admin_user -t C:\oradata\orcl
Important! Use the -t (tablespace) parameter only if the DB_CREATE_FILE_DEST parameter is not set for your Oracle instance. DB2 for LUW example:
dbConfigurator.bat -a create -d db2luw -c storage -v latest -l jdbc:wm:db2://localhost:50000;databaseName=webm_db -u webmuser -p webmuser -au admin_user -ap admin_user -t C:\DB2\Data\
Trading Networks
Do not create the Trading Networks and Trading Networks Archive database components.
18
Important! On UNIX systems, you must enclose the URL in double quotes. For DB2, if the product will connect to a schema other than the default schema for the specified database user, you must specify these connection options in the URL:
;AlternateId=schema;InitializationString="SET CURRENT PATH=schema" AlternateID
is the name of the default schema that is used to qualify unqualified database objects in dynamically prepared SQL statements.
19
Start the 7.1.2 Broker Server. Import the Broker Server data and configuration into the 7.1.2 Broker Server as follows: a b In My webMethods, go to the AdministrationMessagingBroker ServersServers page and click in the DETAIL column for the 7.1.2 Broker Server. Click the Import tab and click Upload File. Select the ServerExported.zip file and click Upload.
20
The Target Object area shows the webMethods Broker objects you can import. You can change the target Brokers for your imported objects; to do so, click the Broker links in the Target Object area and make the changes. Select the check box next to the 7.1.2 Broker Server and click Import. If prompted, click Skip SSL Configuration to not import the 6.1 Broker Server SSL configuration; the 6.1 SSL configuration is incompatible with the 7.1.2 SSL configuration.
Your 6.1 Broker Server SSL configuration was not imported. If you are using SSL, convert your SSL keystores to the correct format and configure SSL, including ACLs, for the 7.1.2 Broker Server. For instructions, see webMethods Broker Administrators Guide 7.1.
d e
In My webMethods, go to the AdministrationMessagingBroker ServersServers page and stop all 6.1 Broker Servers. Refresh the page and make sure the Broker Servers no longer appear on the list.
21
Start the 7.1.2 Broker Server. Import the data and the Broker Server configuration into the 7.1.2 Broker Server as follows: a b c In My webMethods, go to the AdministrationMessagingBroker Territories Territories page. Click the Import tab and click Upload File. Select the TerritoryExported.zip file and click Upload. The Target Object area shows the webMethods Broker objects you can import. You can change the target Brokers for your imported objects; to do so, click the Broker links in the Target Object area and make the changes. Select the check box next to the 7.1.2 Broker Server and click Import. If prompted, click Skip SSL Configuration to not import the 6.1 Broker Server SSL configuration; the 6.1 SSL configuration is incompatible with the 7.1.2 SSL configuration. Repeat these steps for each territory whose configuration you exported.
e 5
If you exported and imported the local territory, you will have a one-sided gateway from the remote territory to the local territory. To create a two-sided gateway, import the local territory again. Complete the gateway migration as explained below. For detailed instructions, see webMethods Broker Administrators Guide 7.1.
If you installed webMethods Broker 7.1.2 on the same machine as webMethods Broker 6.1 and the Broker Server is using the 6.1 port, the gateways are created, but you must manually set the document types to shared. If you installed webMethods Broker 7.1.2 on a different machine than webMethods Broker 6.1 or the Broker Server is not using the 6.1 port, you must manually create the gateways and set the document types to shared.
Your 6.1 Broker Server SSL configuration was not imported. If you are using SSL, convert your SSL keystores to the correct format and configure SSL, including ACLs, for the 7.1.2 Broker Server. For instructions, see webMethods Broker Administrators Guide 7.1. Go to Configure the Forwarding Behavior of a Gateway on page 24 in this procedure.
Configure 7.1.2 Broker Server to Use the 6.1 Combined Storage Session
Use this procedure if you want to continue using your 6.1 combined storage session, and thus did not create a Broker Server configuration during installation. This procedure explains how to create a 7.1.2 Broker Server and configure it to use the 6.1 storage. The procedure also removes the 6.1 Broker Server from the 6.1 Broker Monitor startup configuration and adds it to the 7.1.2 Broker Monitor startup configuration. 1 2 Stop the 6.1 Broker Server, then back up the 6.1 Broker Servers data directory. Set the environment variable ACTIVE_CONFIG to point to the awbrokermon.cfg file for the 6.1 Broker Monitor. The files location is as follows:
22
Back up the 6.1 awbrokermon.cfg file. Remove the 6.1 Broker Server from the 6.1 Broker Monitor startup configuration by going to the webMethods Broker_6.1_directory\bin directory and running the command below. If any part of the data directory path contains a space, enclose the entire path in quotes.
server_config remove full_path_to_6.1_data_directory
Example
server_config remove c:\webmethods6\Broker\data\awbrokers\default server_config remove /var/opt/webmethods6/awbrokers/default
Create the 7.1.2 Broker Server and configure it to use the 6.1 combined storage session by going to the webMethods Broker_7.1.2_directory/bin directory and running the command below. If any part of the data directory path contains a space, enclose the entire path in quotes. Important! For license_key, supply your 7.1.2 webMethods Broker license key.
server_config add full_path_to_6.1_data_directory -k license_key -p port
Example
server_config add c:\webmethods6\Broker\data\awbrokers\default -k WLRS8X-E073106-S000-KH-C10100-2SBR-N4NMPX -p 6871 server_config add /var/opt/webmethods6/awbrokers/default -k WLRS8X-E073106-S000-KH-C10100-2SBR-N4NMPX -p 6871
Make sure the 6.1 combined storage session is running under the 7.1.2 Broker Server: System Windows 1 2 3 Steps Open the Windows Services window. Make sure the status of the webMethods Broker Server 7.1 (port) service is Started. Right-click the service and click Properties. Make sure the value in the Path to Executable field points to the awbroker file for 7.1.2.
23
System UNIX 1 2
Make sure the awbroker process is running and that it is running from the 7.1.2 awbroker file. For example:
brokermon bin 32547 32537 0 Jun27 ? 00:00:03 /opt/webMethods71/Broker/bin/awbroker -d /var/opt/webmethods/awbrokers6/default
7 8
If you are using SSL, convert your keystores to the correct format. For instructions, see webMethods Broker Administrators Guide 7.1. See Configure the Forwarding Behavior of a Gateway, below.
24
time, queue space, and network bandwidth. Make sure the list includes only the document types to which clients in the remote territory actually subscribe. For procedures, see webMethods Broker Administrators Guide 7.1. Important! Software AG strongly encourages you to leave your gateway Broker in static mode. It is inherently more reliable. Additionally, dynamic forwarding might be deprecated in a future release. However, if you need to switch to dynamic mode, you can do so. For instructions, see webMethods Broker Administrators Guide 7.1.
Message Granularity
webMethods Broker and JMS offer explicit acknowledgment of non-persistent (volatile) messages and support for sequence numbers on volatile messages. JMS 7.1.2 allows for finer granularity of quality of service with the assignment of delivery mode and time-tolive on a per-message basis, and the assignment of storage type and lifecycle on a perclient basis.
Message Persistence
For JMS 7.1.2, event types are no longer used to control the persistence of messages. Persistence is now specified using the DeliveryMode (per message), as defined by Java Message Service Specification version 1.1.
25
SSL
The SSL keystore format changed in release 7.1. If you have been using Spyrus keystore files, you must migrate your keystores to the new format and bind the new location of the keystore and truststore in your Connection Factories. For instructions, see webMethods Broker Administrators Guide 7.1.
End the JMSAdmin 6.1 session. Edit the export file as follows: a Change the properties for administered objects as described in Modify Connection Factory Objects on page 27 and Modify Topic and Queue Destinations on page 27. Modify client groups as explained in Modify Client Groups on page 28. Update commands as described in Modify Commands on page 28.
b c
26
d e 4 a b c d 5
Start JMSAdmin 7.1.2 and do the following: Change the context to the one in which to bind the objects. Run the JMSAdmin import command on the saved file. Use the appropriate JMSAdmin create commands to create the bound objects on the Broker. Assign the appropriate permissions to the objects.
27
Both forms of the create queue command create a document type of the form JMS::Queues::queue. For more information, see JMSAdmin Command Changes on page 29.
To migrate 6.1 scripts to 7.1.2, Software AG recommends you create a new (replacement) client group that contains the permissions of the above 6.1 client groups, using the JMSAdmin permit command. The following example shows how to create a new client group named ReplacementClientGroup for use in your 6.1 JMSAdmin scripts, and how to assign the client group the appropriate permissions for the topics specified in the table.
create group ReplacementClientGroup permit group ReplacementClientGroup to publish TopicC permit group ReplacementClientGroup to subscribe TopicA TopicB TopicD
Note: For JMS 7.1.2, the Broker client group properties lifecycle and storage type are set as appropriate for the type of Broker client being created. You cannot change these properties in JMS.
Modify Commands
This section lists changes to JMSAdmin 7.1.2 since release 6.1. New JMSAdmin Commands The commands below were added in JMSAdmin 7.1. For more information, see webMethods Messaging Programmers Guide 7.1. Display Bind ConnectionFactory Modify ConnectionFactory
28
Set Broker Set Encoding Set RecoverMode JMSAdmin Command Changes Command Import Unbind Create Group 7.1 Modification Added optional encoding parameters Added a wildcard (*) parameter to allow unbinding all JMS objects in the current context Removed the optional client group type parameter Removed the create group name for factory form of the command Create Topic Create DurableSubscriber Removed the optional NON-PERSISTENT clause Changed SSL parameters Added a new form of the command that lets you directly create a durable subscriber client on a Broker without having to use bound JMS objects (that is, topics and connection factories) Delete DurableSubscriber Create Queue Removed SSL parameters Changed SSL parameters Added a new form of the command that lets you directly create a queue client on a Broker without having to use bound JMS objects (that is, queues and connection factories) Delete Queue Permit Deny Bind ConnectionFactory Modify ConnectionFactory Bind TopicConnectionFactory Modify TopicConnectionFactory Bind QueueConnectionFactory Modify QueueConnectionFactory Changed SSL parameters and added marshalling class names Removed SSL parameters Changed command syntax
29
7.1 Modification Added optional PriorityOrdering property Added optional PriorityOrdering property Added optional LocalOnly and DeadLetterOnly properties Property Added After 6.1 Application UseXA ClientGroup ClientId marshallInClassName marshallOutClassName SSLTruststore Property Removed After 6.1 ConnectionClientID ConnectionClientGroup SessionClientGroup SubscriberClientGroup DurableSubscriberClientGroup TCPConnectionSharing SharedState SharedStateOrdering StrictClientID TemporaryEventTopicName sslDN
Command TopicConnectionFactory
QueueConnectionFactory
Topic
30
Command Queue
Other Changes to Commands Identifiers for variables used with JMSAdmin commands can now start with a dollar sign ($) or a percent sign (%).
AdminFactory Class
Convert this 6.1 method... newQueue newQueueConnectionFactory newTopic newTopicConnectionFactory To this 7.1.2 method... WmJMSFactory.getQueue WmJMSFactory.getQueueConnectionFactory WmJMSFactory.getTopic WmJMSFactory.getTopicConnectionFactory
QueueAdmin Class
Convert this 6.1 method... asXML asADL getClientGroup setClientGroup getName setName getSharedState setSharedState getSharedStateOrdering To this 7.1.2 method... Not supported in 7.1.2. Use the export command in the JMSAdmin command-line utility instead. WmQueueConnectionFactory.getClientGroup WmQueueConnectionFactory.setClientGroup WmQueue.getName WmQueue.setName WmQueue.getSharedState WmQueue.setSharedState WmQueue.getSharedStateOrdering
31
QueueConnectionFactoryAdmin Class
Convert this 6.1 method... asADL asXML getAutoReconnect setAutoReconnect getBrokerHost setBrokerHost getBrokerName setBrokerName getConnectionClientId setConnectionClientId getConnectionClientGroup setConnectionClientGroup getDurableClientGroup setDurableClientGroup getSessionClientGroup setSessionClientGroup getSharedState setSharedState getSharedStateOrdering setSharedStateOrdering getSSLCertificateFilename setSSLCertificateFilename getSSLEncrypted setSSLEncrypted getStrictClientId setStrictClientId To this 7.1.2 method... Not supported in 7.1.2. Use the export command in the JMSAdmin command-line utility instead. WmJMSConfig.getReconnectAttempts WmJMSConfig.setReconnectAttempts WmQueueConnectionFactory.getBrokerHost WmQueueConnectionFactory.setBrokerHost WmQueueConnectionFactory.getBrokerName WmQueueConnectionFactory.setBrokerName WmQueueConnectionFactory.getClientID WmQueueConnectionFactory.setClientID WmQueueConnectionFactory.getClientGroup WmQueueConnectioNFactory.setClientGroup WmQueueConnectionFactory.getClientGroup WmQueueConnectionFactory.setClientGroup WmQueueConnectionFactory.getClientGroup WmQueueConnectionFactory.setClientGroup WmQueue.getSharedState WmQueue.setSharedState WmQueue.getSharedStateOrdering WmQueue.setSharedStateOrdering WmQueueConnectionFactory.getSSLKeystore WmQueueConnectionFactory.setSSLKeystore WmQueueConnectionFactory.getSSLEncrypted WmQueueConnectionFactory.setSSLEncrypted Conforms to JMS specification Conforms to JMS specification
32
To this 7.1.2 method... WmQueueConnectionFactory.getClientGroup WmQueueConnectionFactory.setClientGroup Single TCP connection per JMS client
TopicAdmin Class
Convert this 6.1 method... asXML asADL getName setName To this 7.1.2 method... Not supported in 7.1.2. Use the export command in the JMSAdmin command-line utility instead. WmTopic.getName WmTopic.setName
TopicConnectionFactoryAdmin Class
Convert this 6.1 method... asADL asXML getAutoReconnect setAutoReconnect getBrokerHost setBrokerHost getBrokerName setBrokerName getConnectionClientId setConnectionClientId getConnectionClientGroup setConnectionClientGroup getDurableClientGroup setDurableClientGroup getSessionClientGroup setSessionClientGroup getSharedState To this 7.1.2 method... Not supported in 7.1.2. Use the export command in the JMSAdmin command-line utility instead. WmJMSConfig.getReconnectAttempts WmJMSConfig.setReconnectAttempts WmTopicConnectionFactory.getBrokerHost WmTopicConnectionFactory.setBrokerHost WmTopicConnectionFactory.getBrokerName WmTopicConnectionFactory.setBrokerName WmTopicConnectionFactory.getClientID WmTopicConnectionFactory.setClientID WmTopicConnectionFactory.getClientGroup WmTopicConnectionFactory.setClientGroup WmTopicConnectionFactory.getClientGroup WmTopicConnectionFactory.setClientGroup WmTopicConnectionFactory.getClientGroup WmTopicConnectionFactory.setClientGroup WmTopic.getSharedState
33
Convert this 6.1 method... setSharedState getSharedStateOrdering setSharedStateOrdering getSSLCertificateFilename setSSLCertificateFilename getSSLEncrypted setSSLEncrypted getStrictClientId setStrictClientId getSubscriberClientGroup setSubscriberClientGroup getTcpConnectionSharing setTcpConnectionSharing getTemporaryTopicEventType setTemporaryTopicEventType
To this 7.1.2 method... WmTopic.setSharedState WmTopic.getSharedStateOrdering WmTopic.setSharedStateOrdering WmTopicConnectionFactory.getSSLKeystore WmTopicConnectionFactory.setSSLKeystore WmTopicConnectionFactory.getSSLEncrypted WmTopicConnectionFactory.setSSLEncrypted Conform to JMS specification WmTopicConnectionFactory.getClientGroup WmTopicConnectionFactory.setClientGroup Single TCP connection per JMS client Single TCP connection per JMS client WmTemporaryDestination.getEventType WmTemporaryDestination.setEventType
Library Locations
The table below lists changes to webMethods Broker and JMS JAR file names and locations. You will have to make appropriate changes to the CLASSPATH for stand-alone JMS clients and to settings for application servers used with JMS 7.1.2. 6.1 Name and Location webMethods Broker_directory\lib\ BrokerJMS61.jar webMethods_directory\common\lib\ client61.jar 7.1.2 Name and Location webMethods Broker_directory\lib\ wmjmsclient.jar webMethods Broker_directory\lib\ wmbrokerclient.jar
34
6.1 Name and Location webMethods Broker_directory\lib\ jmsnaming61.jar webMethods Broker_directory\lib\ jmsadmin61.jar
7.1.2 Name and Location webMethods Broker_directory\lib\ wmjmsnaming.jar webMethods Broker_directory\lib\ wmjmsadmin.jar webMethods Broker_directory\lib\ g11nutils.jar
Migrate the Cross-Reference database component. If you are using Oracle or DB2, run this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|db2luw|db2i} -c crossreference -v latest -l db_server_URL -u existing_db_user -p password fv 10
35
For the Integration Server 7.1.3 release, columns in the Document History database component were changed to solve a character conversion issue with the SQL Server driver. If you are using SQL Server, migrate the Document History database component by running this command:
dbConfigurator.bat -a migrate -d sqlserver -c documenthistory -v latest -l db_server_URL -u existing_db_user -p password -fv 9
Start Integration Server 7.1.3 and connect the IS Core Audit Log and Document History functions to the migrated database components if they are not already connected. If you are using an external RDBMS (as opposed to the internal database), also connect the Cross Reference function. For instructions, see webMethods Installation Guide 7.1. Then shut down Integration Server 7.1.3.
The migration utility asks whether you are using the embedded database or an external RDBMS. If you are using an external RDBMS but did not supply the connection parameters during installation, the migration utility asks for the connection parameters for the IS Internal database component. If you stored cross-referencing data in the Repository Server, the migration utility also asks for the connection parameters for the Cross Reference database component. b 2 When the migration utility is finished running, it shows the message Migration complete in the command window.
If you are using an external RDBMS, data associated with pub.storage services is migrated to the IS_DATASTORE table in the IS Internal database component in the RDBMS. For DB2, the size of a BLOB column is defined when the table is created; you might find that the VALUE column in the IS_DATASTORE table is not wide enough for your pub.storage data. If necessary, use DB2 commands to modify the width.
36
In Back Up the 6.1 Installation on page 14, you recorded the name of each package that was associated with a port in Integration Server 6.1. Identify the system packages in that list; system packages usually have the prefix Wm and are not user-created packages. For each of the identified system packages, go to the Integration Server_6.1_directory\packages\system_package\config directory and copy the listeners.cnf file to the equivalent Integration Server 7.1.3 directory. If the file already exists in that directory, overwrite the file. Important! The config directories for some system packages do not get created until after you start Integration Server. If one or more of the config directories you need do not yet exist, create them.
If you used the WmDB package in Integration Server 6.5, go to the Integration Server_6.1_backup_directory\packages\WmDB\config directory and copy the jdbc.cnf file to the Integration Server_7.1.3_directory\packages\WmDB\config directory. Copy the user-created-package zip files you created in Back Up the 6.1 Installation on page 14 to the Integration Server_7.1.3_directory\replicate\ inbound directory. Go to the Integration Server_6.1_directory\bin directory and open the server.bat or server.sh file in a text editor. Copy the PREPENDCLASSES and APPENDCLASSES lines to the equivalent file in the Integration Server_7.1.3_directory\bin directory. If you are using SSL, copy the server side certificates from the Integration Server 6.1 installation to the corresponding location in the Integration Server 7.1.3 installation.
4 5
37
Using the port information you recorded earlier, re-create the gateway ports and create a Diagnostic port. For detailed instructions, see webMethods Integration Server Administrators Guide 7.1.1. In Integration Server Administrator, go to the PackagesManagementInstall Inbound Releases page. In the Release file name list, click a package you want to migrate, and then click Install Release. The Integration Server installs the package and then displays a message that says the package has been installed and activated. Repeat this step for each package you want to migrate.
Return to the SecurityPorts page and do the following: a If you installed packages that have ports associated with them, make sure Integration Server replicated the correct security settings for the port. If necessary, reconfigure the ports with their original security settings. For each port associated with a user-created package, click the link in the Access Mode column, then click Reset to default access settings. Integration Server keeps the Deny by Default access mode but populates the Allow List with a group of services that have Anonymous ACL.
Configure your Broker connection using the data you recorded in Back Up the 6.1 Installation on page 14 and the new SSL connection parameters in Integration Server 7.1.3. For instructions, see webMethods Integration Server Administrators Guide 7.1.1. The WmTomcat package uses a global deployment descriptor file named web.xml to specify default configuration settings for all Web applications you deploy on Integration Server. If you modified any settings, copy the file from the Integration Server_6.1_directory\web\conf directory to the Integration Server_7.1.3_directory\ web\conf directory. If you configured LDAP in Integration Server 6.1, reconfigure it in Integration Server 7.1.3 using the data you recorded in Back Up the 6.1 Installation on page 14. Note: webMethods product suite 7.1.2 and 7.1.3 offers a new feature named Central User Management. This feature lets Integration Server authenticate and authorize users and user directories defined in My webMethods Server. If you installed My webMethods Server, Software AG recommends that you configure LDAP directories in My webMethods Server and then configure central users in Integration Server. For instructions, see My webMethods Server Administrators Guide 7.1.1 and webMethods Integration Server Administrators Guide 7.1.1, respectively.
38
If the Integration Server 7.1.3 is part of a cluster, reconfigure the cluster. For instructions, see webMethods Integration Server Clustering Guide 7.1.1. Note: The built-in Integration Server load balancer no longer exists in release 7.1.3. If you were using the built-in load balancer, and want to continue using load balancing, switch to a third-party load balancer.
Reverse Invoke has been replaced by Reverse HTTP Gateway. For instructions on configuring the Reverse HTTP Gateway, see the webMethods Integration Server Administrators Guide 7.1.1.
Check Certificates
1 2 Go to the SecurityCertificates page. Make sure the outbound server certificates exist in the indicated location. Go to the SecurityCertificatesConfigure Client Certificates page. Make sure the client certificates are present in the indicated location. Also make sure the client certificates are mapped to the correct user by checking against the data you recorded in Back Up the 6.1 Installation on page 14.
39
Go to the Integration Server_7.1.3_directory\packages\WmTN\config\migrate directory, open a command window, and run this command:
MigratePropFile.{bat|sh} path_to_6.1_properties_file
Example:
MigratePropFile.sh /opt/webMethods/IntegrationServer/packages/WmTN/config/properties.cnf
The command creates a properties.cnf file in the Integration Server_7.1.3_directory\ packages\WmTN\config\migrate directory. 3 Move the properties.cnf file to the Integration Server_7.1.3_directory\packages\ WmTN\config directory.
Migrate the Trading Networks Archive database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i} -c tradingnetworksarchive -v latest -l db_server_URL -u existing_db_user -p password -fv 9
40
Migrate the Trading Networks data, as follows: a Start Integration Server 7.1.3 and connect the Trading Networks function to the migrated Trading Networks database component. For instructions, see webMethods Installation Guide 7.1. Then shut down Integration Server 7.1.3. Go to the Integration Server_7.1.3_directory\packages\WmTN\bin directory, open the setcp.bat or setcp.sh file in a text editor, and make sure the file points to the JVM you want to use. Go to the Integration Server_7.1.3_directory\packages\WmTN\config\migrate directory, open a command window, and run this command:
migratedata_to_tn_7-1.{bat|sh} 6.1
Review the command window to make sure the migration was successful. If errors occurred, contact Software AG Customer Care. Note: Because processing rule names must be unique, the migration utility scans the data for duplicate rule names. If it finds duplicates, the utility adds a sequence number to the each rule name to make the names unique.
tn.tspace.max
watt.server.tspace.max
41
You must move these properties to Integration Server 7.1.3 and rename them, as follows: 1 2 3 4 5 Shut down Integration Server 7.1.3. Go to the Integration Server 6.1_directory\packages\WmTN\config directory and open the properties.cnf file in a text file. Copy the tn.tspace.location and tn.tspace.max properties to the server.cnf file in the Integration Server_7.1.3_directory\config directory. Rename the properties as shown in the table above. Enable users to view and edit the properties, as follows: a b c d 6 Start Integration Server 7.1.3 and open Integration Server Administrator. Go to the SettingsExtended page. Integration Server Administrator lists the configuration properties specified in the server.cnf file. Click Show and Hide Keys and then click the check box for the watt.server.tspace.location and watt.server.tspace.max properties. Click Save Changes. Integration Server Administrator lists the properties and their values.
If the models were developed on an Integration Server equipped with the Modeler Design Package, click Connect to Design Server. Specify the server address, user, and password for the Design Server. If the models were developed using Modeler Offline mode, click Offline. Click and then click Browse and go to the Modeler installation directory.
In the Select process models to be imported list, click the models to import. In Select the process project, click the process project in which to store the models or create a new project in which to store them. Click Finish.
42
If you want to see a summary of the import execution, click View Import Log, or go to the workspace\.metadata\plugins\com.process.webmethods.upgrade.impl\ logs directory and open the ModelUpgradeLog.txt file. Generate and upload your 7.1.2 process models. For instructions, see the Designer online help.
43
44
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Back Up the 6.5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install webMethods Product Suite 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate webMethods Broker 6.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate JMS 6.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Integration Server 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Trading Networks 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate 6.5.x Custom Portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate 6.5.1 Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Optimize 6.5.1 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
45
Overview
This upgrade procedure explains how to upgrade your 6.5.x products to webMethods product suite 7.1.2 and 7.1.3 or Designer 7.2, and how to migrate the following: Data from:
webMethods Broker and JMS 6.5, 6.5.1, or 6.5.2 Integration Server 6.5, 6.5 SP1, 6.5 SP2, or 6.5 SP3 Trading Networks 6.5 or 6.5 SP1
Optimize 6.5.1 SP2 process monitoring data Important! If you are using Manager Server 6.5.x with Optimize 6.5.1 SP2, you cannot migrate Optimize 6.5.1 SP2 process monitoring data. In addition, you cannot migrate Manager Server 6.5.1 SP2 data. Instead, you must re-establish your monitoring setup using Infrastructure Data Collector 7.1.2. Custom portlets from webMethods Access or webMethods Portal 6.5.1 or 6.5.2 Business process models and data from webMethods Modeler 6.5.1 and Process Run Time 6.5.1 SP1 You cannot migrate Workflow processes from 6.5 to webMethods product suite 7.1.2 and 7.1.3. Instead, you must re-implement your Workflow 6.5 projects using Designer 7.1.2 or 7.2 and Task Engine 7.1.3. Important! You must upgrade all of your products at the same time; you cannot use 6.5 products with 7.1.x or 7.2 products. You must upgrade products and migrate data in the order presented in this chapter. Software AG strongly recommends that you upgrade and migrate in a controlled test environment and test that installation for proper operation before upgrading and migrating your production environments.
46
4 c 1 2 3
47
d e f
Record your imported client certificate and user mappings by going to the SecurityCertificatesConfigure Client Certificates page and printing it. Record your Broker connection by going to the SettingsBrokerEdit page and printing it. If you have configured LDAP on the Integration Server, record your LDAP configuration by going to the SecurityUsers & GroupsExternal User Management Configuration page and printing it. If the Integration Server is part of a cluster, record all the cluster information by going to the SettingsClustering page and printing it.
g 5
Shut down Integration Server. Do not shut down the Repository Server; make sure it continues running until all data has been migrated.
For the installation directory, specify a new webMethods directory. If you are going to migrate business processes, you must continue using your webMethods Broker 6.5.2 storage, so you must install webMethods Broker on the machine that hosts webMethods Broker 6.5.2.
On the installers product selection tree, select the 7.1.2 and 7.1.3 products to install; be sure to select all necessary pieces for each product (see the Development Installations chapter in webMethods Installation Guide 7.1). If you are installing products that use an RDBMS, also select the Database Component Configurator.
When the installer asks for product configuration information, do the following:
48
Action Point the database connection at the 6.5 Trading Networks database component. If you choose to use an external RDBMS (as opposed to the embedded database), point the database connection at the 6.5 IS Core Audit Log database component if it exists. Otherwise, point at the external RDBMS you will use for Integration Server 7.1.3 data (see the next bullet, below). If you do not want to continue using your 6.5.2 storage, create a Broker Server configuration. The installer requires your webMethods Broker license key to create a Broker Server configuration. Make sure to supply the 7.1.2 license key. If you want to continue using your 6.5.2 storage, do not create a Broker Server configuration. Important! If you want to migrate business processes, you must continue using your 6.5.2 storage.
webMethods Broker
My webMethods Server
Point the database connection at the RDBMS you will use for My webMethods Server 7.1.3 data (see the next bullet, below).
Important! After Integration Server 7.1.3 and Developer 7.1.3 are installed, you will no longer be able to launch Integration Server 6.5 and Developer 6.5 from the Windows Start menu. You will have to launch these products from the command line instead. Go to the Integration Server_6.5_directory\bin directory and run server.bat, and go to the Developer_6.5_directory\bin directory and run developer.bat. 2 After product installation is complete, create the webMethods product suite 7.1.2 database components that the table below indicates you should create; for instructions, see webMethods Installation Guide 7.1. Do not create database components that the table indicates you should not create; you will migrate the 6.5 database components to 7.1.2 later in this procedure. Note: For 7.1.3 products, you will still create 7.1.2 database components. If you are migrating... Business processes Integration Server Do the following... Do not create the Process Audit Log and Process Engine database components. Do not create the IS Core Audit Log and Document History database components.
49
Do the following... If you are not migrating business processes, create the Process Audit Log database component. If you chose the embedded database during installation, or if you stored 6.5 cross-referencing data in the Cross Reference database component, do not create a Cross Reference database component. If you chose an external RDBMS during installation and want to store crossreferencing data in it, create the Cross Reference database component. If you chose an external RDBMS during installation, create the IS Internal and Distributed Locking database components. If you are using Oracle or DB2 for Linux, UNIX, Windows,first create storage and a tablespace directory for IS Internal by running this command:
dbConfigurator.{bat|sh} -a create -d {oracle|db2luw} -c storage -v latest -l db_server_URL -u existing_db_user -p password -au db_admin_user -ap password -t full_path_to_new_tablespace_directory
Oracle example:
dbConfigurator.bat -a create -d oracle -c storage -v latest -l jdbc:wm:oracle://localhost:1521;ServiceName=ORCL -u webmuser -p webmuser -au admin_user -ap admin_user -t C:\oradata\orcl
Important! Use the -t (tablespace) parameter only if the DB_CREATE_FILE_DEST parameter is not set for your Oracle instance. DB2 for LUW example:
dbConfigurator.bat -a create -d db2luw -c storage -v latest -l jdbc:wm:db2://localhost:50000;databaseName=webm_db -u webmuser -p webmuser -au admin_user -ap admin_user -t C:\DB2\Data\
My webMethods Server
50
Do the following... If you are using Manager Server 6.5.x with Optimize 6.5.1 SP2, create the Analysis and Process Tracker database components. If you are not using Manager Server 6.5.x with Optimize 6.5.1 SP2, do not create the Analysis and Process Tracker database components.
Trading Networks
Do not create the Trading Networks and Trading Networks Archive database components.
Important! On UNIX systems, you must enclose the URL in double quotes. For DB2, if the product will connect to a schema other than the default schema for the specified database user, you must specify these connection options in the URL:
;AlternateId=schema;InitializationString="SET CURRENT PATH=schema" AlternateID
is the name of the default schema that is used to qualify unqualified database objects in dynamically prepared SQL statements.
51
52
Start the 7.1.2 Broker Server. Import the Broker Server data and configuration into the 7.1.2 Broker Server as follows: a b c In My webMethods, go to the AdministrationMessagingBroker ServersServers page and click in the DETAIL column for the 7.1.2 Broker Server. Click the Import tab and click Upload File. Select the ServerExported.zip file and click Upload. The Target Object area shows the webMethods Broker objects you can import. You can change the target Brokers for your imported objects; to do so, click the Broker links in the Target Object area and make the changes. Select the check box next to the 7.1.2 Broker Server and click Import. If prompted, click Skip SSL Configuration to not import the 6.5.2 Broker Server SSL configuration; the 6.5.2 SSL configuration is incompatible with the 7.1.2 SSL configuration.
Your 6.5.2 Broker Server SSL configuration was not imported. If you are using SSL, convert your SSL keystores to the correct format and configure SSL, including ACLs, for the 7.1.2 Broker Server. For instructions, see webMethods Broker Administrators Guide 7.1.
53
d e
In My webMethods, go to the AdministrationMessagingBroker ServersServers page and stop all 6.5.2 Broker Servers. Refresh the page and make sure the Broker Servers no longer appear on the list. Start the 7.1.2 Broker Server. Import the data and the Broker Server configuration into the 7.1.2 Broker Server as follows: a b c In My webMethods, go to the AdministrationMessagingBroker Territories Territories page. Click the Import tab and click Upload File. Select the TerritoryExported.zip file and click Upload. The Target Object area shows the webMethods Broker objects you can import. You can change the target Brokers for your imported objects; to do so, click the Broker links in the Target Object area and make the changes. Select the check box next to the 7.1.2 Broker Server and click Import. If prompted, click Skip SSL Configuration to not import the 6.5.2 Broker Server SSL configuration; the 6.5.2 SSL configuration is not compatible with the 7.1.2 SSL configuration. Repeat these steps for each territory whose configuration you exported.
54
If you exported and imported the local territory, you will have a one-sided gateway from the remote territory to the local territory. To create a two-sided gateway, import the local territory again. Complete the gateway migration as explained below. For detailed instructions, see webMethods Broker Administrators Guide 7.1.
If you installed webMethods Broker 7.1.2 on the same machine as webMethods Broker 6.5.2 and the 7.1.2 Broker Server is using the 6.5.2 port, the gateways are created, but you must manually set the document types to shared. If you installed webMethods Broker 7.1.2 on a different machine than webMethods Broker 6.5.2 or the 7.1.2 Broker Server is not using the 6.5.2 port, you must manually create the gateways and set the document types to shared.
Your 6.5.2 Broker Server SSL configuration was not imported. If you are using SSL, convert your SSL keystores to the correct format and configure SSL, including ACLs, for the 7.1.2 Broker Server. For instructions, see webMethods Broker Administrators Guide 7.1.
Back up the 6.5.2 awbrokermon.cfg file. Remove the 6.5.2 Broker Server from the 6.5.2 Broker Monitor startup configuration by going to the webMethods Broker_6.5.2_directory\bin directory and running the command below. If any part of the data directory path contains a space, enclose the entire path in quotes.
server_config remove full_path_to_6.5.2_data_directory
55
Example
server_config remove c:\webmethods6\Broker\data\awbrokers\default server_config remove /var/opt/webmethods6/awbrokers/default
Create the 7.1.2 Broker Server and configure it to use the 6.5.2 storage by going to the webMethods Broker_7.1.2_directory/bin directory and running the command below. If any part of the data directory path contains a space, enclose the entire path in quotes. Important! For license_key, supply your 7.1.2 webMethods Broker license key.
server_config add full_path_to_6.5.2_data_directory -k license_key -p port
Example
server_config add c:\webmethods6\Broker\data\awbrokers\default -k WLRS8X-E073106-S000-KH-C10100-2SBR-N4NMPX -p 6871 server_config add /var/opt/webmethods6/awbrokers/default -k WLRS8X-E073106-S000-KH-C10100-2SBR-N4NMPX -p 6871
Make sure the 6.5.2 storage is running under the 7.1.2 Broker Server: System Windows 1 2 3 UNIX 1 2 Steps Open the Windows Services window. Make sure the status of the webMethods Broker Server 7.1 (port) service is Started. Right-click the service and click Properties. Make sure the value in the Path to Executable field points to the awbroker file for 7.1.2. Enter this command:
ps -ef | grep aw
Make sure the awbroker process is running and that it is running from the 7.1.2 awbroker file. For example:
brokermon bin 32547 32537 0 Jun27 ? 00:00:03 /opt/webMethods71/Broker/bin/awbroker -d /var/opt/webmethods/awbrokers6/default
If you are using SSL, convert your keystores to the correct format. For instructions, see webMethods Broker Administrators Guide 7.1.
56
57
7.1.2 Method getSSLCertificateDns(String keystore_file, String truststore_file, KeystoreType keystore_type, TruststoreType truststore_type,String password) getSSLRootDns(String keystore_file, String truststore_file, KeystoreType keystore_type, TruststoreType truststore_type,String password)
New Methods in BrokerConnectionDescriptor Class getSSLKeystore() getSSLKeystoreType() getSSLTruststore() getSSLTruststoreType() New Methods in BrokerServerClient Class startServerProcess(String Broker Monitor_host,int Broker Monitor_port,int Broker_port) getServerProcessRunStatus(String Broker Monitor_host,int Broker Monitor_port,int Broker_port) setSSLConfigV2(COM.activesw.api.client.BrokerSSLConfigV2 new_config) getActiveSSLConfigV2() getSavedSSLConfigV2() getActiveSSLIdentity() getSavedSSLIdentity()
58
Migrate C Clients
If you want to migrate C clients that use SSL to 7.1.2, you must modify the way SSL connections are created in your C source code to reflect the Broker C API changes that are documented below. These API changes are consistent with the 7.1.2 Broker Server SSL configuration. For complete information on the 7.1.2 Broker Server SSL configuration, see webMethods Broker Administrators Guide 7.1.
Changed Methods
These methods have been changed to accept the truststore file instead of the distinguished name: awGetDescriptorSSLCertificate awSetDescriptorSSLCertificate awGetSSLCertificate For more information, see webMethods Broker Client C API Programmers Guide 7.1.2.
Removed Methods
These methods have been removed: awGetSSLCertificateDns awGetSSLRootDns
59
sslDN
Queue
PriorityOrdering
60
61
62
Library Locations
The table below lists changes to webMethods Broker and JMS JAR file names and locations. You will have to make appropriate changes to the CLASSPATH for stand-alone JMS clients and to settings for application servers used with JMS 7.1.2. 6.5.2 Name and Location webMethods_directory\common\lib\ wmjmsclient.jar webMethods_directory\common\lib\ wmbrokerclient.jar 7.1.2 Name and Location webMethods Broker_directory\lib\ wmjmsclient.jar webMethods Broker_directory\lib\ wmbrokerclient.jar webMethods Broker_directory\lib\ g11nutils.jar
In Back Up the 6.5 Installation on page 47, you recorded the name of each package that was associated with a port in Integration Server 6.5. Identify the system packages in that list; system packages usually have the prefix Wm and are not user-created packages. For each of the identified system packages, go to the Integration
63
Server_6.5_directory\packages\system_package\config directory and copy the listeners.cnf file to the equivalent Integration Server 7.1.3 directory. If the file already exists in that directory, overwrite the file. Important! The config directories for some system packages do not get created until after you start Integration Server. If one or more of the config directories you need do not yet exist, create them. 3 If you used the WmDB package in Integration Server 6.5, go to the Integration Server_6.5_backup_directory\packages\WmDB\config directory and copy the jdbc.cnf file to the Integration Server_7.1.3_directory\packages\WmDB\config directory. Copy the user-created-package zip files you created in Back Up the 6.5 Installation on page 47 to the Integration Server_7.1.3_directory/replicate/ inbound directory. Go to the Integration Server_6.5_directory\bin directory and open the server.bat or server.sh file in a text editor. Copy the PREPENDCLASSES and APPENDCLASSES lines to the equivalent file in the Integration Server_7.1.3_directory\bin directory. If you are using SSL, copy the server side certificates from the Integration Server 6.5 installation to the corresponding location in the Integration Server 7.1.3 installation. Important! Do not start Integration Server 7.1.3 at this point. You must migrate the Repository Server data before starting Integration Server, or unpredictable results might occur.
4 5
The migration utility asks whether you are using the embedded database or an external RDBMS. If you are using an external RDBMS but did not supply the connection parameters during installation, the migration utility asks for the connection parameters for the IS Internal database component. If you stored cross-referencing data in the Repository Server, the migration utility also asks for the connection parameters for the Cross Reference database component. b When the migration utility is finished running, it shows the message Migration complete in the command window.
64
If you are using an external RDBMS, data associated with pub.storage services is migrated to the IS_DATASTORE table in the IS Internal database component in the RDBMS. For DB2, the size of a BLOB column is defined when the table is created; you might find that the VALUE column in the IS_DATASTORE table is not wide enough for your pub.storage data. If necessary, use DB2 commands to modify the width.
b c
Install 6.5 user-created packages as follows: a b In Integration Server Administrator for Integration Server 7.1.3, go to the PackagesManagementInstall Inbound Releases page. In the Release file name list, click a package you want to migrate, and then click Install Release. The Integration Server installs the package and then displays a message that says the package has been installed and activated. Repeat this step for each package you want to migrate.
Return to the SecurityPorts page and do the following: a If you installed packages that have ports associated with them, make sure Integration Server replicated the correct security settings for the port. If necessary, reconfigure the ports with their original security settings. For each port associated with a user-created package, click the link in the Access Mode column, then click Reset to default access settings. Integration Server keeps the Deny by Default access mode but populates the Allow List with a group of services that have Anonymous ACL.
Configure your Broker connection using the data you recorded in Back Up the 6.5 Installation on page 47 and the new SSL connection parameters in Integration Server 7.1.3. For instructions, see webMethods Integration Server Administrators Guide 7.1.1. The WmTomcat package uses a global deployment descriptor file named web.xml to specify default configuration settings for all Web applications you deploy on Integration Server. If you modified any settings, copy the file from the Integration Server_6.5_directory\web\conf directory to the Integration Server_7.1.3_directory\ web\conf directory.
65
If you configured LDAP in Integration Server 6.5, reconfigure it in Integration Server 7.1.3 using the data you recorded in Back Up the 6.5 Installation on page 47. Note: webMethods product suite 7.1.2 and 7.1.3 offers a new feature named Central User Management. This feature lets Integration Server authenticate and authorize users and user directories defined in My webMethods Server. If you installed My webMethods Server, Software AG recommends that you configure LDAP directories in My webMethods Server and then configure central users in Integration Server. For instructions, see My webMethods Server Administrators Guide 7.1.1 and webMethods Integration Server Administrators Guide 7.1.1, respectively.
If the Integration Server 7.1.3 is part of a cluster, reconfigure the cluster. For instructions, see webMethods Integration Server Clustering Guide 7.1.1. Note: The built-in Integration Server load balancer no longer exists in release 7.1.3. If you were using the built-in load balancer, and want to continue using load balancing, switch to a third-party load balancer.
Reverse Invoke has been replaced by Reverse HTTP Gateway. For instructions on configuring the Reverse HTTP Gateway, see webMethods Integration Server Administrators Guide 7.1.1.
Check Certificates
1 2 Go to the SecurityCertificates page. Make sure the outbound server certificates exist in the indicated location. Go to the SecurityCertificatesConfigure Client Certificates page. Make sure the client certificates are present in the indicated location. Also make sure the client certificates are mapped to the correct user by checking against the data you recorded in Back Up the 6.5 Installation on page 47.
66
If you are migrating from Integration Server 6.5 or 6.5 SP1, migrate the IS Core Audit Log database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i} -c iscoreaudit -v latest -l db_server_URL -u existing_db_user -p password -fv 10
If you are migrating from Integration Server 6.5 SP2 or 6.5 SP3, migrate the IS Core Audit Log database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i} -c iscoreaudit -v latest -l db_server_URL -u existing_db_user -p password -fv 11
Start Integration Server 7.1.3 and connect the IS Core Audit Log, Cross Reference, and Document History functions to the migrated database components if they are not already connected. For instructions, see webMethods Installation Guide 7.1. Then restart Integration Server 7.1.3.
Go to the Integration Server_7.1.3_directory\packages\WmTN\config\migrate directory, open a command window, and run this command:
MigratePropFile.{bat|sh} path_to_6.5_properties_file
67
For example:
MigratePropFile.sh
/opt/webMethods/IntegrationServer/packages/WmTN/config/properties.cnf
The command creates a properties.cnf file in the Integration Server_7.1.3_directory\ packages\WmTN\config\migrate directory. 3 Move the properties.cnf file to the Integration Server_7.1.3_directory\packages\ WmTN\config directory.
On the machine on which you installed the Database Component Configurator, go to the webMethods_7.1.2_directory\common\db\bin directory and open a command window. Migrate the Trading Networks database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i} -c tradingnetworks -v latest -l db_server_URL -u existing_db_user -p password -fv 10
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care. 5 Migrate the Trading Networks Archive database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i} -c tradingnetworksarchive -v latest -l db_server_URL -u existing_db_user -p password -fv 10
68
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care. 6 Migrate the Trading Networks data, as follows: a Start Integration Server 7.1.3 and connect the Trading Networks function to the migrated Trading Networks database component. For instructions, see webMethods Installation Guide 7.1. Then shut down Integration Server 7.1.3. Go to the Integration Server_7.1.3_directory\packages\WmTN\bin directory, open the setcp.bat or setcp.sh file in a text editor, and make sure the file points to the JVM you want to use. Go to the Integration Server_7.1.3_directory\packages\WmTN\config\migrate directory, open a command window, and run this command:
migratedata_to_tn_7-1.{bat|sh} 6.5
Review the command window to make sure the migration was successful. If errors occurred, contact Software AG Customer Care. Note: Because processing rule names must be unique, the migration utility scans the data for duplicate rule names. If it finds duplicates, the utility adds a sequence number to the each rule name to make the names unique.
69
If the models were developed on an Integration Server equipped with the Modeler Design Package, click Connect to Design Server. Specify the server address, user, and password for the Design Server. If the models were developed using Modeler Offline mode, click Offline. Click and then click Browse and go to the Modeler installation directory.
In the Select process models to be imported list, click the models to import. In Select the process project, click the process project in which to store the models or create a new project in which to store them. Click Finish. If you want to see a summary of the import execution, click View Import Log, or go to the workspace\.metadata\plugins\com.process.webmethods.upgrade.impl\ logs directory and open the ModelUpgradeLog.txt file. Generate and upload your process models. For instructions, see the Designer online help.
5 6
70
Copy the packages from the Integration Server_6.5_directory\replicate\outbound directory to the Integration Server_7.1.3_directory\replicate\inbound directory. Install the packages on Integration Server 7.1.3, as follows: 1 2 3 4 5 In Integration Server Administrator for Integration Server 7.1.3, go to the PackagesManagementInstall Inbound Releases page. In the Release file name list, click one of the packages you archived and copied. Clear the Activate upon installation check box. Click Install Release. Repeat these steps for all the packages you copied.
Prevent new instances of 6.5.1 process models from starting by shutting down all 6.5 Integration Servers that host Process Engines.
71
Migrate the Process Audit Log Database Component 1 If you are using DB2 for Linux, UNIX, Windows, do the following: a b c Go to the webMethods_directory/common/db/scripts/db2/processaudit/migrate/ 9to10 directory. Execute the db2_pra_m_9_to_10_migrate.sql script. Execute the db2_pra_m_dml_tracking.sql script. Note: Your database editor might prompt you to supply the right delimiter. 2 For all RDBMSs, run this command:
DbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw} -c processaudit -v 20 -l db_server_URL -u existing_db_user -p password -fv 10
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care. 3 For all RDBMSs, run this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw} -c processaudit -v latest -l db_server_URL -u existing_db_user -p password -fv 20
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care. Migrate the Process Tracking Store Database Component Note: In webMethods product suite 7.1.2 and 7.1.3, the Process Tracking Store database component has been renamed the Process Engine database component. 1 If you are using DB2 for Linux, UNIX, Windows, do the following: a b c Go to the webMethods_directory/common/db/scripts/db2/processengine/migrate/ 9to10 directory. Execute the db2_pre_m_9_to_10_migrate.sql script. Execute the db2_pre_m_dml_tracking.sql script. Note: Your database editor might prompt you to supply the right delimiter.
72
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care. 3 For all RDBMSs, run this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw} -c processengine -v latest -l db_server_URL -u existing_db_user -p password -fv 20
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care.
3 4
73
Optimize 7.0 SP2 Analytic Engine Database Scripts build 7.0.0.2.52 My webMethods Server 7.0 SP2 with the Central Configuration user interface
Create the 7.0 SP2 My webMethods Server and Process Audit Log database components in a separate schema. Note: These database components are used only temporarily. They do not need to contain any data from the 6.5.1 installation.
Configure and start My webMethods Server 7.0 SP2. For instructions, see My webMethods Server Administrators Guide 7.0 SP2.
Transform Data
For detailed instructions on each of the steps below, see webMethods Optimize Central Configuration and Deployment Guide 7.0. 1 Create a configuration for Analytic Engine 7.0 SP2. Make sure the JDBC pools for Analysis and Process Tracker point to the 6.5.1 SP2 schemas. Make sure the JDBC pool for Process Audit Log points to the 7.0 SP2 schema. Deploy the configuration to a file. The file name is DeployedEnvironment.zip. Go to the Analytic Engine host machine and extract the DeployedEnvironment.zip file to any directory. Go to the extraction_directory\host\Analytic Engine\config directory. Copy the contents of that directory over the contents of the Optimize_7.0 SP2_directory\ analysis\conf directory. Configure the Password Administrator Utility and transfer logical server passwords.
2 3 4
74
If you are using an HP-UX PA-RISC system, go to the Optimize_7.0 SP2_directory\ optimize\analysis\bin directory, open the preMigrationRules.sh script in a text editor, and replace the contents of the file with the following:
#!/bin/sh ## --------------------------------------------------------------## $Id: //bpodepot/optimize/huttSP2/bin/analysis/preMigrateRules.sh#3 $ ## $DateTime: 2007/04/12 14:24:04 $ ## $Revision: #3 $ ## --------------------------------------------------------------args1=$1 args2=$2 args3=$3 args4=$4 . ./kenobiEnv.sh # Configure JAVA executable if [ -z "${JAVA_HOME}" ] ; then echo "JAVA_HOME environment variable not set. Unable to continue." exit 1 fi # Check to make sure all environment variables are correct if [ -z "${OPTIMIZE_ANALYSIS_HOME}" ] ; then echo "OPTIMIZE_ANALYSIS_HOME environment variable not set. Unable to continue." exit 1 fi CLASSPATH=${OPTIMIZE_ANALYSIS_HOME}/bin/opt65.jar CLASSPATH=${CLASSPATH}:${OPTIMIZE_ANALYSIS_HOME}/lib/sl53_cj36.jar CLASSPATH=${CLASSPATH}:${OPTIMIZE_ANALYSIS_HOME}/lib/glue.jar export CLASSPATH $JAVA_HOME/bin/java -Doptimize.home.path=$OPTIMIZE_ANALYSIS_HOME com.dante.analysis.rules.RuleXMLTranslator $arg1 $arg2 $arg3 $arg4
Extract 6.5.1 SP2 rules from the Analysis database component to the file system. Go to the Optimize_7.0 SP2_directory\optimize\analysis\bin directory and run the preMigrateRules.{bat|sh} script as shown below. RDBMS Oracle Command
preMigrateRules.{bat|sh} "jdbc:wm:oracle://host:{1521|port};serviceName=service" existing_db_user password com.wm.dd.jdbc.oracle.OracleDriver preMigrateRules.bat "jdbc:wm:sqlserver://host:{1433|port} ;databaseName=database" existing_db_user password com.wm.dd.jdbc.sqlserver.SQLServerDriver preMigrateRules.{bat|sh} "jdbc:wm:db2://host:{50000|port};databaseName=database ;AlternateId=schema;showSelectableTables=false" existing_db_user password com.wm.dd.jdbc.db2.DB2Driver
75
Prepare DB2 for Linux, UNIX, Windows If you are migrating database components in DB2 for Linux, UNIX, Windows, run the command below for each schema:
dbInstaller.{bat|sh} create db2udb componenttracker latest db_server_URL existing_db_user password
Example:
dbInstaller.sh create db2udb componenttracker latest "jdbc:wm:db2://localhost:50000;databaseName=S651SP2 ;AlternateId=COMPONENTTRACKER651SP2;InitializationString=SET CURRENT PATH=current_path,COMPONENTTRACKER651SP2" userid userpwd
76
Migrate the Analysis Database Component You might have the Optimize 6.5.1 SP2 database components Analysis and Process Tracker in separate schemas or in the same schema. If you installed Analysis and Process Tracker in different schemas, they each have a supporting Operation Management database component. If you installed Analysis and Process Tracker in the same schema, they share a single Operation Management database component. 1 Migrate the Operation Management database component by running this command:
dbInstaller.{bat|sh} migrate {oracle|mssql|db2db2} operationmanagement 15 db_server_URL existing_db_user password 10
Example:
dbInstaller.bat create mssql distributedlocking latest jdbc:wm:sqlserver://localhost:1433;databaseName=analysis651SP2db analysisuser analysispwd
Go to the Optimize_7.0 SP2_directory/analysis/bin directory and run the migrate65to70.{bat|sh} script. The script writes execution information to the Optimize_7.0 SP2_directory/analysis/log directory. Run this command:
dbInstaller.{bat|sh} migrate {oracle|mssql|db2udb} analysis 25 db_server_URL existing_db_user password 24
Migrate the Process Tracker Database Component 1 If the Process Tracker database component was in a different schema than Analysis, migrate Operation Management by running this command:
dbInstaller.{bat|sh}migrate {oracle|mssql|db2udb} operationmanagement 15 db_server_URL existing_db_user password 10
77
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care. Note: When you start the Analytic Engine after completing the migration tasks in this section, the engine will perform the final migration of Analysis data. 3 Migrate the Process Tracker database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw} -c processtracker -v latest -l db_server_URL -u existing_db_user -p password -fv 25
78
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care.
79
80
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Back Up the Fabric 7 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install webMethods Product Suite 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate webMethods Broker and JMS 6.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Integration Server 6.5 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Trading Networks 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate My webMethods Server 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate 7.0 SP2 Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate 7.0 SP2 Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Metadata Library 7.0 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Optimize 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Deployer 7.0 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
81
Overview
This upgrade procedure explains how to upgrade your Fabric 7 products to webMethods product suite 7.1.2 and 7.1.3 or Designer 7.2, and how to migrate the following: Data from:
webMethods Broker and JMS 6.5.2 Integration Server 6.5 SP2 or SP3 Trading Networks 6.5 or 6.5 SP1 My webMethods Server 7.0 SP2 Deployer 7.0
Optimize 7.0 SP2 process monitoring data Important! If you are using Infrastructure Data Collector 7.0 SP2 with Optimize 7.0 SP2, you cannot migrate Optimize process monitoring data. In addition, you cannot migrate Infrastructure Data Collector 7.0 SP2 data. Instead, you must re-establish your monitoring setup using Infrastructure Data Collector 7.1.2. Custom portlets from Designer 7.0 SP2 and My webMethods Server 7.0 SP2 Business process models and data from Designer 7.0 SP2 and Process Engine 7.0 SP2 Task applications from My webMethods Server 7.0 SP2 and Task Engine 7.0 SP2 Important! You must upgrade all of your products at the same time; you cannot use Fabric 7 products with 7.1.x or 7.2 products. You must upgrade products and migrate data in the order presented in this chapter. Software AG strongly recommends that you upgrade and migrate in a controlled test environment and test that installation for proper operation before upgrading and migrating your production environments.
82
4 c 1 2 3
83
d e f
Record your imported client certificate and user mappings by going to the SecurityCertificatesConfigure Client Certificates page and printing it. Record your Broker connection by going to the SettingsBrokerEdit page and printing it. If you have configured LDAP on the Integration Server, record your LDAP configuration by going to the SecurityUsers & GroupsExternal User Management Configuration page and printing it. If the Integration Server is part of a cluster, record all the cluster information by going to the SettingsClustering page and printing it.
g 5
Shut down Integration Server. Do not shut down the Repository Server; make sure it continues running until all data has been migrated.
84
When the installer asks for product configuration information, do the following: Product Trading Networks Integration Server Action Point the database connection at the 6.5 Trading Networks database component. If you choose to use an external RDBMS (as opposed to the embedded database), point the database connection at the 6.1 IS Core Audit Log database component if it exists. Otherwise, point at the external RDBMS you will use for Integration Server 7.1.3 data (see the next bullet, below). Point the database connection at the RDBMS you will use for Metadata Library 7.1.1 data. If you do not want to continue using your 6.5.2 storage, create a Broker Server configuration. The installer requires your webMethods Broker license key to create a Broker Server configuration. Make sure to supply the 7.1.2 license key. If you want to continue using your 6.5.2 storage, do not create a Broker Server configuration. Important! If you want to migrate business processes, you must continue using your 6.5.2 storage. My webMethods Server
and 7
Point the database connection at the RDBMS you will use for My webMethods Server 7.1.3 data (see the next bullet, below).
Important! After Integration Server 7.1.3 and Developer 7.1.3 are installed, you will no longer be able to launch Integration Server 6.5 SP2 and Developer 6.5 SP3 from the Windows Start menu. Go to the Integration Server_6.5 SP2_directory\bin directory and run server.bat, and go to the Developer_6.5 SP3_directory\bin directory and run developer.bat. After product installation is complete, create the webMethods product suite 7.1.2 database components that the table below indicates you should create; for instructions, see webMethods Installation Guide 7.1. Do not create database components that the table indicates you should not create; you will migrate the Fabric 7 database components to 7.1.2 later in this procedure. Note: For 7.1.3 products, you will still create 7.1.2 database components.
85
Do the following... Do not create the Process Audit Log and Process Engine database components. If you are not migrating business processes, create the Process Audit Log database component. If you chose an external RDBMS during installation, create the IS Internal and Distributed Locking database components. If you are using Oracle or DB2 for Linux, UNIX, Windows,first create storage and a tablespace directory for IS Internal by running this command:
dbConfigurator.{bat|sh} -a create -d {oracle|db2luw} -c storage -v latest -l db_server_URL -u existing_db_user -p password -au db_admin_user -ap password -t full_path_to_new_tablespace_directory
Important! For Oracle, use the -t (tablespace) parameter only if the DB_CREATE_FILE_DEST parameter is not set for your Oracle instance. Do not create the IS Core Audit Log and Document History database components. If you chose the embedded database during installation, or if you stored 6.5 SP2 cross-referencing data in the Cross Reference database component, do not create a Cross Reference database component. If you chose an external RDBMS during installation and want to store cross-referencing data in it, create the Cross Reference database component. Metadata Library My webMethods Server Optimize Create the Metadata Reasoner and Metadata Repository database components. Create the My webMethods Server database component. If you are using Infrastructure Data Collector 7.0 SP2 with Optimize Optimize 7.0 SP2, create the Analysis and Process Tracker database components. If you are not using Infrastructure Data Collector 7.0 SP2 with Optimize 7.0 SP2, do not create the Analysis and Process Tracker database components. Trading Networks Do not create the Trading Networks and Trading Networks Archive database components.
86
Important! On UNIX systems, you must enclose the URL in double quotes. For DB2, if the product will connect to a schema other than the default schema for the specified database user, you must specify these connection options in the URL:
;AlternateId=schema;InitializationString="SET CURRENT PATH=schema" AlternateID
is the name of the default schema that is used to qualify unqualified database objects in dynamically prepared SQL statements.
87
If you need to migrate more than 500 assets, deployment will be faster if you divide the assets into four projects. Do the following: 1 Create these four projects:
User, group, role, and directory service assets. Composite and task application assets. Custom page and folder assets. Shell, skin, renderer, and rule assets.
If users, groups, or roles appear as dependencies in the second, third, or fourth project, mark them as Exists.
88
2 3 d
Create a project build, deployment map, and deployment candidate for each project. Deploy the projects to My webMethods Server 7.1.3 separately, in the order shown above.
If you deployed My webMethods Server rules, the order in which the deployed rules are resolved with the existing rules on the target servers might need modification. Review the rule order after deployment and modify as necessary.
89
If you did not migrate task applications (see Migrate 7.0 SP2 Tasks on page 94), you have not yet created the workspace index for Designer 7.1.2. Create the workspace index now, as follows: a In Windows Explorer, go to the workspace_directory\.metadata\.plugins\ com.webmethods.sc.metadata.core\.stores directory and delete all the files and folders in the directory. Start Designer 7.1.2. For each process project in the workspace, in the Navigator view, right-click to display the context menu and click Close Project, then rightclick and click Open Project.
Open each process and regenerate it. When you open a process that contains pools, Designer asks, This process must be upgraded to view in the current version of Designer. Do you wish to save the changes? Click OK, and then re-generate the process.
5 6
Update your process projects to point to the new project classpath. In the Navigator view, right-click each project and choose to run the CAF Repair Tool. Open Designer 7.1.2 and generate and upload your 7.1.2 process models. For instructions, see the Designer online help.
90
Click Export and identify the directory to which to export. You can export to any directory; for example, you might export the logical server definitions to the directory that contains the exported process models. In the File name field, type the file name for the preferences. Designer will add the extension .properties. Click Open.
Import Process Models and Logical Server Definitions into Designer 7.2
1 2 Open Designer 7.2. You can import process models into a variety of projects, existing or new, or you can import import multiple process models into a single, existing project.
To import process models into a variety of existing or new projects, do the following: 1 2 Go to FileImport. On the Select panel, in the Select an import source box, go to Software AG Process File and then click Next. In the Select file field, select a process model you exported and click Open. In the Select Project field, specify the existing or new project into which to import the process model. Click Finish. 3 Repeat for every process model you want to import.
To import multiple process models into a single, existing project, do the following: 1 2 3 Go to FileImport. On the Select panel, in the Select an import source box, go to GeneralFile System and then click Next. On the File System panel, in the From directory field, browse to the directory that contains the process models you exported. Select the check box next to each .process file to import. In the Into folder field, specify the existing project into which to import. Click Finish.
91
Import logical server definitions as follows: a b Go to WindowPreferences. On the Preferences dialog box, in the left navigation bar, go to Software AGIntegration Servers. The list on the left shows your logical servers, called Integration Servers in Designer 7.2. Click Import, select the .properties file you exported, and click Open. Designer asks whether you want to overwriting existing servers; click OK twice.
c 4
Configure Designer 7.2 to connect to the Integration Servers. For instructions, see the Designer online help.
Copy the packages from the Integration Server_6.5 SP2_directory\replicate\ outbound directory to the Integration Server_7.1.3_directory\replicate\ inbound directory.
92
Install the packages on Integration Server 7.1.3, as follows: 1 2 3 4 5 In Integration Server Administrator for Integration Server 7.1.3, go to the PackagesManagementInstall Inbound Releases page. In the Release file name list, click one of the packages you archived and copied. Clear the Activate upon installation check box. Click Install Release. Repeat these steps for all the packages you copied.
Prevent new instances of 7.0 SP2 process models from starting by shutting down all 6.5 SP2 Integration Servers that host Process Engines.
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care. 4 Migrate the Process Engine database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw} -c processengine -v latest -l db_server_URL -u existing_db_user -p password -fv 20
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care.
93
3 4 5
94
c 3
c 4
Make sure the imported 7.0 SP2 task projects appear in the Solutions tab, under the Tasks node. Note: If errors appear in the Problems tab, click the Navigator tab, right-click each task project, click CAF Tools, and then click Repair CAF Project. If errors still appear, restart Designer.
Publish the task projects to My webMethods Server. For instructions, see the Designer online help.
95
3 4
96
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care. Note: When you start the Analytic Engine after completing the migration tasks in this section, the engine will perform the final migration of Analysis data. 3 Migrate the Process Tracker database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw} -c processtracker -v latest -l db_server_URL -u existing_db_user -p password -fv 25
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care.
97
Map these database pools... Analysis and Process Tracker Process Audit Log
To these database components... Analysis and Process Tracker database components you migrated. If you migrated business processes, map to the Process Audit Log database component you migrated. If you did not migrate business processes, map to the new 7.1.2 Process Audit Log database component.
My webMethods Server
7.1.2 My webMethods Server database component. Note: For My webMethods Server 7.1.3, the database component is still 7.1.2.
3 4
Start the Optimize 7.1.2 engines. Deploy the Optimize 7.1.2 environment.
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care.
98
Description Replaces the entire rule list. Overwrites existing rules and deploys new rules into the rule set.
1 2
Apply DEP_7-1-2_Fix1 to Deployer 7.1.2 using the instructions in the fix readme. Do the following to reset the Overwrite Existing TN Rules property correctly in your existing projects from Deployer 7.0:
To correct all projects, invoke the service http://Deployer_host:Deployer_port /invoke/wm.deployer.gui.UIProject:migrateProjects. To correct a specific project, invoke the service http://Deployer_host:Deployer_port/ invoke/wm.deployer.gui.UIProject:migrateProjects?projectName=project Important! - If you changed any project properties before applying DEP_7-1-2 _Fix1, the service cannot reset the property correctly. Instead, Deployer resets the property to the equivalent setting for No regardless of the property's previous setting. If you want to use the equivalent setting for Yes instead, you must manually reset the property. Note: If you later import a 7.0 project (for example, from a backup), Deployer 7.1.2 resets the property correctly automatically.
If you are using Deployer command line mode to import project properties for 7.0 projects, you must reset the property manually. Follow these steps for each project properties file you import: a b Go to the Integration Server_directory\packages\WmDeployer\replicate\ inbound directory. Open the project_properties file.
99
Locate the overwriteTNRules property and do the following: 1 2 3 Replace the word "overwriteTNRules" with the word "deployTNRules." Set the deployTNRules property to REPLACE or OVERWRITE_EXISTING_ADDNEW. Save and close the file.
100
Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Back Up the Earlier 7.x Installation and Remove Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prepare to Upgrade a My webMethods Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Install webMethods Product Suite 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Integration Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Trading Networks Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Metadata Library Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Designer Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the My webMethods Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Migrate Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Optimize Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Complete the Deployer Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
101
Overview
This upgrade procedure explains how to upgrade webMethods products as follows: Upgrade from... 7.1 or 7.1.1 webMethods Broker, Deployer, Designer, Developer, Integration Server, Monitor, My webMethods Server, Optimize, Process Engine, and Trading Networks 7.1 Metadata Library Note: Metadata Library did not have a release after 7.1.1. 7.1, 7.1.1, or 7.1.2 Developer, Integration Server, and Designer Composite Applications plug-ins 7.1.1 or 7.1.2 My webMethods Server 7.2 Designer Composite Applications plug-ins 6.5.1 or 6.5.3 Blaze Advisor 6.5 or 6.5.3 Blaze Rule Service Plug-in and Blaze Rule Service Support Note: The release numbering for these products was changed from 6.x to match the 7.x release numbering used for the rest of the webMethods product suite. Since you will upgrade by installing over the earlier products, you will not need to migrate data in most cases. However, for some products, you must perform certain tasks to complete the upgrade or to migrate data. This chapter provides instructions for those products. Important! You must upgrade all of your products at the same time. You must upgrade products and migrate data in the order presented in this chapter. Software AG strongly recommends that you upgrade and migrate in a controlled test environment and test that installation for proper operation before upgrading and migrating your production environments. 7.1.3 7.1.3 7.2.1 6.5.5 7.1.2 To... 7.1.2
7.1.1
102
103
104
For the installation directory, specify the directory that contains your earlier 7.x webMethods products. On the installers product selection tree, already installed 7.xproducts are shown in gray followed by the word Installed (wizard mode) or the letter I (console mode). Select the 7.1.2 and 7.1.3 products to install; be sure to select all necessary pieces for each product (see the Development Installations chapter in webMethods Installation Guide 7.1). If you are installing products that use an RDBMS, also select the Database Component Configurator. Note: As you select products, top-level product nodes might turn gray. You can ignore this; it will not adversely affect installation.
Important! If you are upgrading from Integration Server 7.1, after installing Integration Server 7.1.3, do not increase PermGen space as indicated in the webMethods Installation Guide 7.1. Instead, follow the instructions in Migrate Integration Server 7.1 Data on page 108.
105
If you are upgrading from Integration Server 7.1.1, migrate the IS Core Audit Log database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i} -c iscoreaudit -v latest -l db_server_URL -u existing_db_user -p password
If you are upgrading from Integration Server 7.1.2, migrate the IS Internal database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i} -c isinternal -v latest -l db_server_URL -u existing_db_user -p password
If you are upgrading from Integration Server 7.1.1, migrate the IS Internal database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i} -c isinternal -v latest -l db_server_URL -u existing_db_user -p password
If you are also upgrading My webMethods Server, apply TC_7-1-2_Fix1 to Integration Server 7.1.3 using the instructions in the fix readme. Fixes are available from the Software AG Knowledge Center. Start Integration Server 7.1.3 and connect the IS Core Audit Log, IS Internal, Cross Reference, and Document History functions to the migrated database components. For instructions, see webMethods Installation Guide 7.1. Then restart Integration Server 7.1.3.
106
The Integration Server services created in the previous steps. The QNames of the headers processed by the new service-based handler. A unique descriptive name for the new service-based handler.
5 6
Manually run the startup service once to register the new service-based handler. In all Web service descriptors (WSDs) that use the JAX-RPC handler, replace the JAXRPC handler with the new service-based handler, as follows: a b c d Remove headers with QNames that are supported by the JAX-RPC handler. Remove the JAX-RPC handler from the WSD. Add the new service-based handler to the WSD. Add the headers you removed in step a.
107
Change it to:
set JAVA_MEMSET=-Xms%JAVA_MIN_MEM% -Xmx%JAVA_MAX_MEM% -XX:MaxPermSize=%JAVA_MAX_PERM_SIZE%
Change it to:
set JAVA2_MEMSET=-Xms%JAVA_MIN_MEM% -Xmx%JAVA_MAX_MEM% -XX:MaxPermSize=%JAVA_MAX_PERM_SIZE% -Xrs %XPATH_IMPL% -DWM_HOME="%WM_HOME%"
UNIX, IBM i5, or Mac System By default, the webMethods Installer installs a Sun JDK for Integration Server 7.1.3 on Linux and Solaris systems. If you are using the default JDK on those systems, or if you are using your own Sun JDK on one of those systems, another UNIX system, or an IBM i5 or Mac system, complete the steps below. Note: If you receive java.lang.OutOfMemoryError: PermGen space exceptions when running Integration Server, set the PermGen space higher than the 128 MB mentioned in this section.
108
1 2
Go to the Integration Server_directory/bin directory and open the server.sh file in a text editor. Locate this line
JAVA_MAX_MEM=512M
Change it to:
JAVA_RUN="${JAVA_DIR}/${JAVA_EXE} ${JAVA_MEMSET} ${JAVA_PERM_SIZESET} ${JAVA_OPT_PREFER_IP4V}"
109
If you are also upgrading My webMethods Server, apply TC_7-1-2_Fix1 to Integration Server 7.1.3 using the instructions in the fix readme. Fixes are available from the Software AG Knowledge Center. Start Integration Server 7.1.3 and connect the IS Core Audit Log, IS Internal, Cross Reference, and Document History functions to the migrated database components. For instructions, see webMethods Installation Guide 7.1. Then restart Integration Server 7.1.3.
110
Comment out the following: For TNS_ 7-1-1_DB_ Fix1 Fix2 Comment out... The index in the Create table FX_RoutingStatus section. The Create table FX_RoutingStatus and Create table FX_UserStatus sections.
d 5
On the machine on which you installed the Database Component Configurator, go to the webMethods_directory\common\db\bin directory, open a command window, and mMigrate the Trading Networks database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i} -c tradingnetworks -v latest -l db_server_URL -u existing_db_user -p password -fv 20
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_directory\common\ db\logs directory. If errors occurred, contact Software AG Customer Care.
c 2
Click Save Changes. The property changes dynamically; you do not have to restart Integration Server.
In Trading Networks 7.1.2, all Trading Networks-related roles you create in My webMethods are automatically granted access to the My webMethods Administrative Preferences page. This page enables users to connect to Trading Networks and specify other Trading Networks options. With Trading Networks 7.1 and 7.1.1, this access was not granted automatically, so you must now grant it manually. Grant all Trading Networks-related roles access to the Administrative Preferences page as follows: a b c Go to the AdministrationSystem-WideUser ManagementRoles page. In the Roles list, click TN Administrative Preferences. Click the Members tab, and then click Edit Members.
111
d e
In the Select Principal(s) dialog box, click Roles, then click Search. In the Available list, click every Trading Networks-related role and then click Apply.
3 UNIX 1 2
Save and close the file. Go to the Metadata Library_directory/library/bin directory and open the library.sh file in a text editor. In the JAVA_DIR=${JAVA_HOME} line, replace ${JAVA_HOME} with the path to the JDK you want to use (for example, JAVA_DIR=webMethods_directory/jvm/linux150). Save and close the file.
Metadata Library 7.1 supported Infravio X-Registry 6.6, but Metadata Library 7.1.1 supports CentraSite GE 7.1 and CentraSite EE 3.1.7. If you want to use CentraSite with Metadata Library 7.1.1, configure the CentraSite Asset Publisher. For instructions, see webMethods Metadata Library Users Guide 7.1.1.
112
On the machine on which you installed the Database Component Configurator, go to the webMethods_directory\common\db\bin directory, open a command window, and migrate the My webMethods Server database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw} -c MyWebMethodsServer -v latest -l db_server_URL -u existing_db_user -p password
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_directory\common\ db\logs directory. If errors occurred, contact Software AG Customer Care. Important! You must retain the database permissions used in this step until My webMethods Server is started and initialized so that My webMethods Server can create database tables and views. 3 Go to the 7.x_installation_directory\MWS\bin directory, open a command window, and run the command below to upgrade your My webMethods Server files and configuration. The name of the default My webMethods Server instance is default.
mws -s server_instance upgrade
Start My webMethods Server to complete the upgrade process. My webMethods Server redeploys all components and shuts down. You can now restart My webMethods Server and operate it normally. If you are upgrading a My webMethods Server cluster, go to Upgrade a My webMethods Server Cluster, below.
113
3 4 5
From the upgraded My webMethods Servers host machine, copy the common, jvm, and install directories to the webMethods installation directory you created on the node host machine. From the upgraded My webMethods Servers host machine, copy all contents of the MWS directory except the MWS/server/default/ data/repository directory to the webMethods installation directory you created on the node host machine. Note: If you stored your shared files on a dedicated network device, the repository directory will not exist on the upgraded My webMethods Servers host machine. If it does exist, do not copy the repository directory because it must remain in the network shared location where it is accessible to all cluster nodes
On the node host machine, go to the 7.x_installation_directory\MWS\ server\default\bin directory and open the server.properties.{bat|sh} file in a text editor. Update or add the environment variable below to the file. For node_name, use the name of the node that you wrote down in step 3. System Windows UNIX Environment Variable set NODE_NAME=node_name NODE_NAME=node_name
114
d 6
If you used asymmetric component deployment mode in My webMethods Server and you deployed different versions or sets of custom components to My webMethods Server, go to the 7.x_installation_directory\MWS\server\deploy directory for each node and make sure the correct versions of custom components are present. Start each node in the cluster using the command below. You can start the nodes in any order. The default My webMethods Server instance is named default.
mws -s server_instance {run|start}
Restart each node in the cluster using the command below. You can restart the nodes in any order.
mws -s server_instance restart
For each node, go to the 7.x_installation_directory/MWS/server/default/deploy/portal.war/WEB-INF directory and open the server-config.wsdd file. If it does not contain the XML tags below, add them to the end of the section that contains service elements.
<service name="SAML" provider="java:MSG" style="message" use="literal"> <parameter name="allowedMethods" value="samlAssertionHandler"/> <parameter name="className" value="com.webmethods.portal.portlet.wm_xt_samlsecurityservice.endpoint.S amlServiceEndpoint"/> </service>
10 On any node, retrieve the cluster.xml config file from the My webMethods Server database by going to the7.x_installation_directory/MWS/bin directory and running this command:
mws.bat getconfig cluster.xml
11 Open the cluster.xml file and make sure the list of cluster nodes matches your My webMethods Server cluster. If any nodes listed in the file do not exist in your My webMethods Server cluster, delete those nodes from the file and then upload the file to the My webMethods Server database by running this command:
mws.bat putconfig cluster.xml
115
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_directory\common\ db\logs directory. If errors occurred, contact Software AG Customer Care. 4 Migrate the Process Audit Log database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw} -c processaudit -v latest -l db_server_URL -u existing_db_user -p password -fv 30
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_directory\common\ db\logs directory. If errors occurred, contact Software AG Customer Care.
116
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_directory\common\ db\logs directory. If errors occurred, contact Software AG Customer Care. Note: When you start the Analytic Engine after completing the migration tasks in this section, the engine will perform the final migration of Analysis data. 3 Migrate the Process Tracker database component by running this command:
dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw} -c processtracker -v latest -l db_server_URL -u existing_db_user -p password -fv 30
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_directory\common\ db\logs directory. If errors occurred, contact Software AG Customer Care.
117
Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_directory\common\ db\logs directory. If errors occurred, contact Software AG Customer Care.
118
Description Replaces the entire rule list. Overwrites existing rules and deploys new rules into the rule set.
1 2
Apply DEP_7-1-2_Fix1 to Deployer 7.1.2 using the instructions in the fix readme. Do the following to reset the Overwrite Existing TN Rules property correctly in your existing projects from Deployer 7.1 or 7.1.1:
To correct all projects, invoke the service http://Deployer_host:Deployer_port /invoke/wm.deployer.gui.UIProject:migrateProjects. To correct a specific project, invoke the service http://Deployer_host:Deployer_port/ invoke/wm.deployer.gui.UIProject:migrateProjects?projectName=project Important! - If you changed any project properties before applying DEP_7-12_Fix1, the service cannot reset the property correctly. Instead, Deployer resets the property to the equivalent setting for No regardless of the property's previous setting. If you want to use the equivalent setting for Yes instead, you must manually reset the property. Note: If you later import a 7.1 or 7.1.1 project (for example, from a backup), Deployer 7.1.2 resets the property correctly automatically.
If you are using Deployer command line mode to import project properties for 7.1 or 7.1.1 projects, you must reset the property manually. Follow these steps for each project properties file you import: a b Go to the Integration Server_7.1.3_directory\packages\WmDeployer\replicate\ inbound directory. Open the project_properties file.
119
Locate the overwriteTNRules property and do the following: 1 2 3 Replace the word "overwriteTNRules" with the word "deployTNRules." Set the deployTNRules property to REPLACE or OVERWRITE_EXISTING_ADDNEW. Save and close the file.
120