8-x Web Methods Upgrade Guide

Title Page

webMethods Upgrade Guide

Version 8.0

April 2010

Copyright& Docu-ment ID
This document applies to webMethods Product Suite Version 8.0 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 © 2008-2010 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 AG’s 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).

Document ID: WEBM-UPG-80-20100415

http://documentation.softwareag.com/legal/



Table of Contents

About This Guide . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Document Conventions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Documentation Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9Online Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

1. Installing Latest 8.0 Releases over 7.1.2, 7.1.3, 7.2, or 7.2.1 . . . . . . . . . . . . . . . . . . . . . 13Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Shut Down Running Products and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Back Up the 7.x webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Install the Latest 8.0 Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . 20Migrate webMethods Broker and JMS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Migrate Integration Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Run the Integration Server Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Run the Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Customize Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Migrate the Integration Server Database Components . . . . . . . . . . . . . . . . . . . . . . . . 24Update WSDLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Use Central User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Run the Migration Utility Silently with Imported Settings . . . . . . . . . . . . . . . . . . . . . . . 25

Migrate Trading Networks Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Migrate My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Migrate My webMethods Server Components and Database Components . . . . . . . . . 26Configure My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Migrate Blaze Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Migrate Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Migrate Design-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Migrate Run-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Migrate Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30Migrate Task Design-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Export Task Application Projects from Designer 7.x . . . . . . . . . . . . . . . . . . . . . . . 31Import 7.0 SP2 Task Application Projects into Designer 8.0 . . . . . . . . . . . . . . . . . 31

Migrate Task Run-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

webMethods Upgrade Guide Version 8.0 3

Table of Contents

Migrate Optimize Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Migrate Optimize Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Update Broker Connection Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Deploy the Optimize Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

To Not Reuse the 7.x CCS Environment Definition . . . . . . . . . . . . . . . . . . . . . . . . 33To Reuse the 7.x CCS Environment Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Deploy the Optimize 8.0 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Rediscover Assets and Reestablish Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Migrate Deployer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Update Database URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36

2. Installing Latest 8.0 Over 8.0 FCS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38Shut Down Running Products and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Back Up the 8.0 FCS webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Upgrade Your RDBMSs or Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Uninstall Certain Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Uninstall CentraSite 8.0 SP1, Tamino XML Server 8.0, and Designer 8.0 (March 2009 Release) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Uninstall EntireX 8.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Delete Trading Networks Additional Reports 8.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

Install the Latest 8.0 Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42Complete the ApplinX Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Complete the EntireX Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Complete the Web Services Stack Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Migrate Integration Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Run the Integration Server Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Customize Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Migrate Trading Networks Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Migrate My webMethods Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Migrate Blaze Rules and Rule Maintenance Applications . . . . . . . . . . . . . . . . . . . . . . . . . . 48Migrate Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Migrate Optimize and Monitor Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Migrate Optimize Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Update Broker Connection Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Deploy the Optimize Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Re-enable Reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

Migrate Deployer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50

3. Installing Latest 8.0 SPx Over Earlier 8.0 SPx . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Shut Down Running Products and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Back Up the 8.0 webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

4 webMethods Upgrade Guide Version 8.0

Table of Contents

Upgrade Your RDBMSs or Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Install 8.0 SPx Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Complete the ApplinX Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Migrate My webMethods Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55Migrate Optimize and Monitor Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

Update Broker Connection Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Deploy the Optimize Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

4. Performing Side-by-Side Migration from 7.x to Latest 8.0 Releases . . . . . . . . . . . . . . 57Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Requirements, Recommendations, and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58Back Up the 7.x webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Back Up 7.x Database Components and Upgrade RDBMSs . . . . . . . . . . . . . . . . . . . . . . . 60Install the Latest 8.0 Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . 62Migrate webMethods Broker and JMS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Set Up the 8.0 Broker Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

To Not Use 7.x Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63To Use 7.x Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

Migrate Integration Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Run the Integration Server Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Migration Utility Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Run the Utility to Perform a Custom Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Customize Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Migrate the Integration Server Database Components . . . . . . . . . . . . . . . . . . . . . . . . 69Update WSDLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Use Central User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Run the Migration Utility Silently with Imported Settings, with a Zip File as Data Source, or

Both . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Migrate Clustered Integration Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Migrate Trading Networks Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Migrate My webMethods Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Apply Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Identify Assets to Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Export Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Import Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Migrate Blaze Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Migrate Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Migrate Design-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75Migrate Run-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Migrate Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76


Table of Contents

Migrate Optimize Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Migrate Optimize Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Deploy the Optimize Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77

Connect Process Engine to Analytic Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77To Not Reuse the 7.x CCS Environment Definition . . . . . . . . . . . . . . . . . . . . . . . . 77To Reuse the 7.x CCS Environment Definition . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Deploy the Optimize 8.0 Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Rediscover Assets and Reestablish Monitoring . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Migrate Deployer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Migrate Connection Information (Aliases) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Migrate Target Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Migrate Deployment Projects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

Update Database URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

5. Performing Side-by-Side Migration from 6.5 to Latest 8.0 Releases . . . . . . . . . . . . . . 83Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Requirements, Recommendations, and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Back Up the 6.5 webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85Back Up 6.5 Databases and Upgrade RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Install the Latest 8.0 Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . 88Migrate webMethods Broker Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Set Up the 8.0 Broker Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Migrate if You Do Not Have Gateways and Territories . . . . . . . . . . . . . . . . . . . . . 90Migrate if You Have Gateways and Territories . . . . . . . . . . . . . . . . . . . . . . . . . . . 91Configure the 8.0 Broker Server to Use 6.5 Storage . . . . . . . . . . . . . . . . . . . . . . . 92

Migrate Java Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Command-Line Utilities Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Broker Java API Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Changed Methods in BrokerConnectionDescriptor Class . . . . . . . . . . . . . . . 95New Methods in BrokerConnectionDescriptor Class . . . . . . . . . . . . . . . . . . . 95New Methods in BrokerServerClient Class . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Migrate C Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Changed Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Removed Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96


Table of Contents

Migrate JMS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Update JMSAdmin Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Convert JMS Client APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Changed Method in WmJMSAdminFactory Class . . . . . . . . . . . . . . . . . . . . . . . . 98Deprecated WmFileMessage Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98New Methods in WmJMSConfig Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98New Fields in WmConnectionFactory Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98New Methods in WmConnectionFactory Class . . . . . . . . . . . . . . . . . . . . . . . . . . . 99New Method in WmQueueConnectionFactory Class . . . . . . . . . . . . . . . . . . . . . . 99New Method in WmTopicConnectionFactory Class . . . . . . . . . . . . . . . . . . . . . . . 99

Library Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99Migrate Integration Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Run the Integration Server Migration Utility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Migration Utility Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100Run the Utility to Perform a Custom Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

Customize Startup Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Migrate the Integration Server Database Components . . . . . . . . . . . . . . . . . . . . . . . . 103Assign Trust Store . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Use Central User Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104Migrate Clustered Integration Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Migrate Trading Networks Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Migrate the Trading Networks Properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Migrate the Trading Networks Database Components . . . . . . . . . . . . . . . . . . . . . . . . . 105Migrate Trading Networks Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Migrate Date and Time Stamps for Migrated Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Migrate Access or Portal Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Apply Fix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Identify Assets to Export . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Export Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Import Assets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109

Migrate Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Migrate Design-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Migrate Run-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Migrate Deployer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Update Database URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112


Table of Contents


About This Guide

This guide is for users who are upgrading to the latest webMethods 8.0 product releases.

Document Conventions

Documentation Installation

You can download the product documentation using the Software AG Installer. Depending on the release of the webMethods product suite, the location of the downloaded documentation will be as shown in the table below.

Convention Description

Bold Identifies elements on a user interface.

Narrow font Identifies storage locations for services on webMethods Integration Server, using the convention folder.subfolder:service.

UPPERCASE Identifies keyboard keys. Keys you must press simultaneously are joined with a plus sign (+).

Italic 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.

Monospace font

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 (...).

For webMethods... The documentation is downloaded to...

6.x The installation directory of each product.

7.x A central directory named _documentation in the main installation directory (webMethods by default).

8.x A central directory named _documentation in the main installation directory (Software AG by default).


About This Guide

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... Go to...

Access the latest version of product documentation.

Software AG Documentation Web site

http://documentation.softwareag.com

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.

Empower Product Support Web site

https://empower.softwareag.com



https://empower.softwareag.com/KnowledgeCenter/default.asp

https://empower.softwareag.com/Products/default.asp

https://empower.softwareag.com

About This Guide

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.

Software AG Developer Community for webMethods

http://communities.softwareag.com/webmethods

If you want to... Go to...


http://communities.softwareag.com/webmethods

About This Guide


1 Installing Latest 8.0 Releases over 7.1.2, 7.1.3, 7.2, or 7.2.1

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Shut Down Running Products and Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

Back Up the 7.x webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Install the Latest 8.0 Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Migrate webMethods Broker and JMS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Migrate Integration Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Migrate Trading Networks Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Migrate My webMethods Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Migrate Blaze Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Migrate Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

Migrate Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

Migrate Optimize Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

Migrate Deployer Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Update Database URLs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36



Overview

This upgrade procedure explains how to install the latest webMethods 8.0 product releases over webMethods 7.1.2, 7.1.3, 7.2, or 7.2.1 products. For some products, you must perform additional tasks to complete the upgrade or to migrate data. This chapter provides instructions for those tasks.

For simplicity, this chapter uses these terms:

The product releases from which you can upgrade are referred to as 7.x. However, you can only upgrade from a 7.1.2, 7.1.3, 7.2, or 7.2.1 release. If you want to upgrade from a 7.1 or 7.1.1 release, you must first upgrade to 7.1.2 or 7.1.3.

The latest 8.0 product releases to which you can upgrade are referred to as 8.0.

Note: This procedure does not explain how to upgrade from CentraSite 7.x to CentraSite 8.0 SP3. If you need to perform that upgrade, contact Software AG Global Consulting Services. CentraSite should be upgraded before any other product.

Important! Because many products share files, you must upgrade all products that are in the same installation directory.

You must upgrade products and migrate data in the order the instructions are presented in this chapter.

Software AG strongly recommends that you upgrade and migrate in a controlled test environment and test that environment for proper operation before upgrading and migrating your production environments.

Important! If you installed language packs on your 7.x products, you cannot overinstall until those language packs are available for your 8.0 products. Then, for each affected product, you must install the 8.0 product and the 8.0 language pack over the 7.x product and 7.x language pack at the same time; you cannot install the 8.0 product at one time, and the 8.0 language pack at another time. For language pack availability, see the Globalization section of the Software AG Empower Web site.


http://empower.softwareag.com


Before You Begin

If you are going to upgrade Integration Server, do the following:

a Allow all guaranteed delivery jobs to finish running. To do so, connect Integration Server to webMethods Broker; in Integration Server Administrator, go to the Settings > Resources > Store Settings page and wait for Current Documents in Outbound Store in the Outbound Document Store area to reach 0.

If you have a cluster of Integration Servers, stop routing client requests to one Integration Server in the cluster and perform the step above, then do the same for the next Integration Server in the cluster, and so on for all Integration Servers in the cluster.

b If you are going to upgrade from Integration Server 7.1.3, apply IS_8-0-1_Migrate_Fix1 to Integration Server 7.1.3 using instructions in the fix readme. Fixes are available from the Software AG Knowledge Center.

If you are going to upgrade business processes, allow them to finish running or use Monitor to stop them.

If you are going to upgrade Optimize, do the following:

a If you want to reuse your Central Configuration System (CCS) Environment definition, export the environment to a file. For instructions, see webMethods Optimize for {Infrastructure|Process} Administrator’s Guide 7.1.

b If the Broker you use with Optimize is using a non-default name or port, start Integration Server and open Integration Server Administrator. Go to the Packages

> Management page, click for the WmOptimize package, and note the Broker URL field value. You will have to re-enter this information after upgrading.

c If you are using Optimize for Infrastructure, start My webMethods Server and open My webMethods. Go to the Administration > Analytics > Infrastructure Components > Monitored Components page and note the components and KPIs you are monitoring. You will have to reselect them after upgrading.

Data from previously monitored SNMP data cannot be migrated. Start Infrastructure Data Collector, open Infrastructure Data Collector Administrator, and do the following:

Clean up previously monitored SNMP data by deleting SNMP metadata. For instructions, see webMethods Optimize for Infrastructure Administrator’s Guide 7.1, Deleting SNMP Component Assets.

Go to the Packages > Management page and disable the WmSNMP package.

If you are going to upgrade My webMethods Server, the upgrade procedure will reset the values below to their default values. If you customized any of these values, start My webMethods Server, open My webMethods, and follow the steps below.




Shut Down Running Products and Applications

1 Shut down the products listed below if they are running on the machine on which you are going to overinstall.

The instructions in the table are for Windows systems. On UNIX systems, use the instructions provided in the product documentation.

The upgrade procedure will reset... Log onto My webMethods Server...

Your CAF Application Runtime Configuration.

As sysadmin, go to the Administration > Configuration > CAF Application Runtime Configuration page, and click Configure Global Defaults. On the Configure Global Defaults page, expand the User Attributes link. Print each page of user attributes.

The start page, login page, shell, skin, and local rules provided with My webMethods Server, and your default skin and shell.

As sysadmin, go to the Administration > User Interface page, and click each of the Rules links. Note the values.

Your task chart portlets. As Administrator, go to the Monitoring > Business > Tasks > Task Chart page, and click the Edit icon for each chart portlet. Note the chart properties.

The task global change and schedule rules.

As Administrator, go to the Administration > Business > Tasks > Task Engine Administration page, and click the Manage Global Change Rules and Manage Global Schedule Rules icons. Click each Rule link and note the rule properties.

Important! If you do not shut down all of the indicated products and applications, the Software AG Installer will not be able to replace key files that are locked by the operating system.



2 Shut down all other applications that are running on the machine on which you are going to overinstall.

Products to Shut Down Method

Running as applications:ApplinXEntireX (all Brokers and RPC Servers)My webMethods Server* and Task EngineOptimize Analytic Engine, Prediction Engine, and Web Service Data CollectorReport Server

Use Windows Start menu (Start > Programs > Software AG > Stop Servers > product)

Running as services:ApplinXBroker Monitor (stops Broker Servers)CentraSite Application Server TierMy webMethods Server* and Task EngineOptimize Analytic Engine, Prediction Engine, and Web Service Data CollectorReport ServerSystem Management Hub**

Use Windows Services window (Software AG webMethods product release)

Running as service:Report Server

Run script (see product documentation)

Tomcat Kit Open a command window and run the command sc stop SAGCTP80

CentraSite Registry RepositoryDeveloperDesignerIntegration Server* (and products it hosts)Optimize Infrastructure Data CollectorTamino XML Server

Use product interface (see product documentation)

*If you have a cluster, shut down all cluster nodes.**System Management Hub services are named Software AG CSLayer Service and EventLayer Service.



Back Up the 7.x webMethods Installation

1 If you are upgrading webMethods Broker, back up the JMS objects and data in each webMethods Broker installation.

2 Back up the entire 7.x webMethods installation directory.

If you have a cluster of Integration Servers, back up the installation for each Integration Server in the cluster.

3 Back up all 7.x databases. For instructions, see your RDBMS vendor documentation.

4 If you are going to upgrade My webMethods Server, go to the 7.x_installation_directory\MWS\server\server_instance\deploy directory and delete all .xml files.

Upgrade Your RDBMSs

Check your RDBMSs against webMethods System Requirements 8.0. If the RDBMS version you are using is not supported by the 8.0 products, you must upgrade to a supported RDBMS version before continuing with the instructions in this chapter.

Install the Latest 8.0 Products

If you are upgrading webMethods Broker, Integration Server, or Infrastructure Data Collector, obtain the license file or license key for that release from [email protected].

Go to the Software AG Documentation Web site and download Software AG Installation Guide 8.0. Follow the instructions in that guide to install your 8.0 products, with the additional guidelines or differences below.

For installation directory, specify the 7.x webMethods installation directory.

If you have a cluster of Integration Servers, overinstall every Integration Server in the cluster. If you have a cluster of My webMethods Servers, choose one node to overinstall. You will upgrade the other nodes later, as described in “Migrate My webMethods Server” on page 26.

Important! After you upgrade to the latest 8.0 product releases, you will not be able to roll back to previous releases. You will only be able to restore previous releases from the backups you create using the instructions in this section.

Important! For My webMethods Server, you must back up the 7.x webMethods installation directory and the MywebMethodsServer database component at the same time. The two must be in sync, or you will experience problems. The same is true for Optimize and the Optimize database components.



mailto:[email protected]


On the Software AG Installer’s product selection tree, existing products are shown in gray followed by the word “Installed” (wizard mode) or the letter “I” (console mode). Select the 8.0 products to install; be sure to select all necessary components of each product (see Software AG Installation Guide 8.0, Typical Development Installations for guidance).

If you are installing a product that uses an RDBMS, select Database Configuration.

You can also select new 8.0 products and optional items such as Documentation.

When the installer asks for product configuration information, do the following:

Note: Do not choose to install CentraSite 8.0 SP3. If you need to upgrade from CentraSite 7.x to CentraSite 8.0 SP3, contact Software AG Global Consulting Services.

Product Action

Optimize Infrastructure Data Collector

Provide the product configuration information as instructed in Software AG Installation Guide 8.0.

Integration Server

Provide the license file.

Indicate whether you want the installer to migrate Integration Server data.

Choose to have the installer migrate the data if you want the installer to automatically run the Integration Server Migration Utility with default values. The default values migrate all port, remote server alias, and Integration Server certificate settings; Web service endpoint aliases; proxy settings; and the Integration Server embedded database.

Choose to not have the installer migrate the data if you want to specify custom migration values (for example, migrate certain ports only), or if you want to export migration values so you can run the migration utility silently on other machines. In this case, you would run the utility after installation using the instructions in “Migrate Integration Server Data” on page 21.

webMethods Broker

Provide the license file.

My webMethods Server

Indicate whether you want the installer to automatically upgrade My webMethods Server server instances. If you do not, you must upgrade them manually one at a time after installation.



If you selected 8.0 products that are not yet installed on your machine, see Software AG Installation Guide 8.0 for instructions on providing the required product configuration information.

If you installed a language pack for a 7.x product, you must overinstall the same language pack for the 8.0 product.

If you had the installer automatically migrate Integration Server data or upgrade My webMethods Server server instances, details of the migration or upgrade are written to the migrationLog.txt file in the 8.0_installation_directory\install\logs directory. If you are using the installer wizard (as opposed to console mode), the installer’s Finish panel provides a link to the file.

If you installed new 8.0 products, create any necessary database components. For detailed information and instructions, see Software AG Installation Guide 8.0.

If you installed on a Windows system, manually remove 7.x entries from the Start menu.

Sample URL Formats for Database Component Migration

For some products, you will migrate data stored in database components, and will need to supply database server URLs. Sample formats are shown below.

Use the DataDirect Connect connection option MaxPooledStatements=35 on all database URLs except those for Trading Networks. This connection option improves performance by caching prepared statements. (Trading Networks caches its prepared statements using its own pooling mechanism).

On UNIX systems, you must enclose the database URL in double quotes.

Important! For each affected product, you must install the 8.0 product and the 8.0 language pack over the 7.x product and 7.x language pack at the same time. You cannot install the 8.0 product at one time, and the 8.0 language pack at another time.

RDBMS Sample URL Format

Oracle jdbc:wm:oracle://server:{1521|port};serviceName=service[;option=value …]

Oracle configured for RAC

jdbc:wm:oracle://server:{1521|port};serviceName=service;AlternateServers=(server:{1521|port};,…);ConnectionRetry=value; ConnectionDelay=value;LoadBalancing=value[;option=value …]

SQL Server jdbc:wm:sqlserver://server:{1433|port} ;databaseName=database[;option=value …]



Migrate webMethods Broker and JMS Data

If you used saved searches for webMethods Broker 7.x in My webMethods, they are no longer available in webMethods Broker 8.0. For instructions on recreating them, see Working with My webMethods 8.0.

Migrate Integration Server Data

If you have a cluster of Integration Servers, repeat this procedure for each Integration Server in the cluster.

Run the Integration Server Migration Utility

If you had the installer automatically migrate your Integration Server 7.x data, skip this section and go to “Customize Startup Files” on page 24.

Overview

This section explains how to use the Integration Server Migration Utility to migrate your Integration Server 7.x data. You have several options, as described below.

You can run a custom migration, in which you choose which data to migrate. The utility gathers your choices through a series of prompts, then migrates the specified data. To run a custom migration, follow the steps below, in this section.

If you are performing migrations for multiple, identical, clustered Integration Servers running on different machines, you can run a custom migration, export your choices to file, and import the choices when you run the utility on other machines.

DB2 for Linux, UNIX, Windows

jdbc:wm:db2://server:{50000|port};databaseName=database[;option=value …]

DB2 for iSeries jdbc:wm:db2://server:{446|port};locationName=location[;option=value …]

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=current_path,schema"

AlternateID is the name of the default schema that is used to qualify unqualified database objects in dynamically prepared SQL statements.




To run a custom migration and export your choices to file, follow the steps below, in this section.

To run a migration with imported choices and a confirmation prompt before the migration actually begins, follow the steps below, in this section. To run a migration with imported choices silently (that is, with no confirmation prompt), see “Run the Migration Utility Silently with Imported Settings” on page 25.

During actual migrations, if migration of a piece of data fails (for example, certificate settings for a port), the utility asks whether to continue with the next piece of data or abort the migration. If you choose to abort, the utility exits. It does not revert the Integration Server 8.0 installation. You can address the issue and run the utility again.

The migration utility writes details of the migration to the migrationLog.txt file in the 8.0_installation_directory\install\logs directory. By default, the utility writes INFO, ERROR, and FATAL messages to the log. If you want to increase the logging level to DEBUG, go to the Integration Server_8.0_directory\bin\migrate directory, open the file log4j.properties file in a text editor, set the log4j.logger.Migration property to DEBUG, MigrationFile, and save and close the file.

Run the Utility

1 Go to the Integration Server_8.0_directory\bin\migrate directory and run the command migrate.{bat|sh}.

2 The utility asks whether to import migration settings. If this is the first time you are running the utility, enter N. If you exported migration settings from an earlier session of the utility, enter Y and provide the full path to the export file (current_directory\migrate.dat).

3 The utility asks whether to migrate port certificate settings to the keystores used in 8.0 SP1. You can migrate all of the settings (enter A), none of the settings (enter N), or selected settings only (enter S). If you enter S, the utility lists each port and asks whether to migrate its certificate settings.

For each SSL port you migrate, the utility will convert certificate settings into the keystores used in 8.0 SP1. If conversion fails, the utility will revert all migration changes it made to the port and disable the port in Integration Server 8.0 SP1.

4 The utility asks whether to migrate remote server alias certificate settings. You can migrate all of the settings (enter A), none of the settings (enter N), or selected settings only (enter S). If you enter S, the utility lists each remote server alias and asks whether to migrate its certificate settings.

For remote server alias you migrate, the utility will convert certificate settings to the 8.0 SP1 format. If the conversion fails, the utility will revert all migration changes it made to the remote server alias in Integration Server 8.0 SP1.

Note: If you do not migrate certificate settings for a port, and a default Integration Server keystore exists in the 8.0 SP1 installation, the port will default to that key-store.



5 The utility asks whether to migrate Web service endpoint aliases. You can migrate all of the aliases (enter A), none of the aliases (enter N), or selected aliases only (enter S). If you enter S, the utility lists each Web service endpoint alias and asks whether to migrate it.

For each alias you migrate that is in use by a WSD, the utility detects the type and transport of the WSD and copies that information to the 8.0 SP1 files. If an alias is not in use by a WSD, the utility copies the type and transport information in such a way that the alias is available to all WSDs, regardless of type or transport.

The utility will convert type and transport information for Web service endpoint aliases to the 8.0 SP1 format. If the conversion fails, the utility will revert all migration changes it made for the alias in Integration Server 8.0 SP1.

6 The utility asks whether to migrate Integration Server certificate settings. If you enter Y, the utility will convert the certificate settings into the keystores used in 8.0 SP1.

7 The utility asks whether to migrate proxy settings. If you enter Y, the utility will convert your proxy settings to the 8.0 SP1 format.

8 If Integration Server 7.x used the embedded database, the utility asks whether to migrate it. If you enter Y, the utility will copy the database tables from Integration Server 7.x to Integration Server 8.0 SP1 and convert the tables to the 8.0 SP1 format.

9 The utility asks whether to export the migration settings from this session. If you enter Y, the utility stores the migration settings in a file named migrate.dat in the directory from which you are running the utility.

10 The utility asks whether to begin migration. If you want the utility to exit without migrating any data, enter N. If you want the utility to migrate data based on the settings you specified, enter Y; the utility prints progress messages to the command window and the migration log. If migration completes successfully, the utility does the following:

Deletes 7.x configuration files that are no longer used by Integration Server 8.0 SP1.

Deletes 7.x properties that are no longer used by Integration Server 8.0 SP1 from the 8.0 SP1 configuration files, and merges the Integration Server port.cnf and listeners.cnf file.

If Integration Server 7.x was part of a cluster, upgrades your clustering configuration to the 8.0 SP1 format.

Deletes all fixes you applied to Integration Server 7.x.

Note: If you do not migrate the embedded database now, Integration Server 8.0 SP1 will create the embedded database automatically on startup but not migrate any data to it.



Customize Startup Files

In Integration Server 8.0, definitions of the environment variables have been moved from the server.{bat|sh} file to the new setenv.{bat|sh} file. If you made any changes to your Integration Server 7.x server.{bat|sh} file, manually reproduce those changes in your 8.0 files. Make sure you reproduce changes you made to your 7.x environment variables in the setenv.{bat|sh} file.

The 7.x files are in the backup you took before installing Integration Server 8.0. The 8.0 files are located in the Integration Server_8.0_directory\bin directory.

Migrate the Integration Server Database Components

If you used an external RDBMS with Integration Server 7.x, you must migrate the ISInternal and ISCoreAudit database components.

1 Shut down all Integration Servers that connect to the 7.x ISInternal and ISCoreAudit database components.

2 On the machine on which you installed the Database Component Configurator, go to the 8.0_installation_directory\common\db\bin directory, open a command window, and migrate each database component by running the command below.

After each command, check the log file dcc_yyyymmddhhmmss in the 8.0_installation_directory\common\db\logs directory. If errors occurred, contact Software AG Customer Care.

3 Start Integration Server 8.0 and connect the ISInternal, ISCoreAudit, Xref (for Cross-Reference), and DocumentHistory functions to the corresponding database components if they are not already connected. If you want to use central user management, also connect the CentralUsers function to the My webMethods Server database component. For instructions, see Software AG Installation Guide 8.0. Then restart Integration Server 8.0.

Update WSDLs

In Integration Server Administrator, go to the Settings > Extended page. If you have the extended setting watt.server.xml.ncname.encode.backward.compatibility and it is set to true, reset it to false. Then regenerate the clients for all Provider Web services that have an operation with field names starting with "xml" in the input signature, output signature, header, or faults.

dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i}-c {ISInternal|ISCoreAudit} -v latest -l db_server_URL -u existing_db_user -p password



Use Central User Management

If you configured Integration Server 7.x to use the My webMethods Server central user management feature, go to the Settings > Resources page in Integration Server Administrator and make sure the MWS SAML Resolver URL field is pointing to the My webMethods Server 8.0 host and port.

If you want to monitor business processes in 8.0, also add the mywebMethodsUsers role and mywebmethodsAdministrator’s role to the Monitor Administrator ACL. For instructions, see Administering My webMethods Server 8.0.

Run the Migration Utility Silently with Imported Settings

If you want to run the migration utility silently using settings exported from an earlier session, follow the instructions below.

1 Go to the Integration Server_8.0_directory\bin\migrate directory on the machine on which you ran the earlier migration session.

2 Copy the migrate.dat file from that directory to any directory on the machine on which you want to run the silent migration session.

3 Open a command window, go to the Integration Server_8.0_directory\bin\migrate directory, and run this command:

Migrate Trading Networks Data

1 Shut down all Integration Servers that connect to the 7.x TradingNetworks database component.

2 Use your data editor to delete all data from the ARCHIVE_WORKTABLE table in the TradingNetworksArchive database component.



{migrate.bat|./migrate.sh} -importFile full_path_to_migrate.dat -silent true

dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i}-c {TradingNetworks|TradingNetworksArchive} -v latest -l db_server_URL-u existing_db_user -p password



Migrate My webMethods Server

Migrate My webMethods Server Components and Database Components

1 If you did not choose the Upgrade My webMethods Server Instances check box during installation, run the command below for each My webMethods Server instance. The command copies all new My webMethods Server 8.0 components to the specified server instance and upgrades the server instance’s My webMethods Server_directory\server\server_instance\config directory.

If you have a cluster of My webMethods Servers, run this command on the node you overinstalled only. You will upgrade the other nodes later.

2 On the machine on which you installed the Database Component Configurator, go to the 8.0_installation_directory\common\db\bin directory and open a command window. Migrate the My webMethods Server database component by running this command:

Check the log file dcc_yyyymmddhhmmss in the 8.0_installation_directory\common\ db\logs directory. If errors occurred, contact Software AG Customer Care.

3 Go to the My webMethods Server_8.0_directory\bin directory and start each My webMethods Server instance by running the command below. The command redeploys 7.x components to the My webMethods Server 8.0. When the command is finished, the My webMethods Server shuts down automatically.

4 If you have a cluster of My webMethods Servers, delete the 7.x cluster nodes you have not upgraded and then add 8.0 nodes. For instructions, see Administering My webMethods Server 8.0.

5 My webMethods Server 7.x used Jetty 5.0 as its Web server; My webMethods Server 8.0 uses Jetty 6.0. If you modified the jetty.xml file in your 7.x installation, use the mws.{bat|sh} getconfig jetty.xml and mws.{bat|sh} putconfig jetty.xml commands to similarly modify your 8.0 jetty.xml file.

6 Restart My webMethods Server 8.0 and open My webMethods.

mws.{bat|sh -s server_instance upgrade

dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw}-c MWS -v latest -l db_server_URL -u existing_db_user -p password

Note: Depending on the number of webMethods product interfaces and language packs you installed, this process might take a long time to complete (for example, an hour).

mws.{bat|sh -s server_instance run



Configure My webMethods Server

1 The upgrade procedure reset the values below to their default values. If you customized any of these values, follow the steps below.

2 Task applications in webMethods 8.0 have new functional privileges that relate to the new 8.0 collaboration processes feature. Even though these privileges are displayed in Permissions Management, you must add these privileges to the task application in case you want to modify them later. To add the privileges to your task applications, start Designer 8.0, go to the Import > Software AG > Existing CAF Projects Into Workspace page, and import the task applications into Designer 8.0 using the Import button in the Solutions View toolbar. The import process automatically checks and adds missing task privileges. Then republish the task applications to My webMethods Server 8.0. For instructions, see webMethods Designer BPM Task Development Help 8.0.

3 My webMethods Server 7.x included a special component called a WebDAV folder that was used if a folder in My webMethods Server needed to be exposed via WebDAV. In My webMethods Server 8.0, the entire My webMethods Server taxonomy is automatically exposed via WebDAV, so the WebDAV folder component is no longer necessary and therefore has been removed. The upgrade procedure automatically converted old webDAV folders into regular My webMethods Server folders so no data is lost. However, the WebDAV URL of these folders has changed, so clients must be updated. For more info about WebDAV support, see Administering My webMethods Server 8.0.

The upgrade procedure reset... Log onto My webMethods Server...

Your 7.x CAF Application Runtime Configuration.

As sysadmin, go to the Administration > Configuration > CAF Application Runtime Configuration page, and similarly modify your 8.0 configuration using your notes from step n in “Before You Begin” on page 15.


Similarly modify your 8.0 rules, skin, and shell using instructions in Administering My webMethods Server 8.0.

Your 7.x task chart portlets. As Administrator, go to the Navigate > Applications > Monitoring > Business > Tasks > Task Chart page and similarly modify your 8.0 task chart portlets using your notes fromstep n in “Before You Begin” on page 15.

The 7.x task global change and schedule rules.

As Administrator, go to the Navigate > Applications > Administration > Business > Tasks > Task Engine Administration page and similarly modify your 8.0 Global Change Rules and Global Schedule Rules using your notes from step n in “Before You Begin” on page 15.



4 In My webMethods Server 7.x, you could create home pages and add portlets to them. The upgrade procedure converted your home pages to a new feature in 8.0 named workspaces, and converted your default 7.x home page to an 8.0 start page. However, the upgrade procedure did not add the workspaces to your My webMethods Navigation tab. For information about workspaces and instructions on adding them to your Navigation tab, see Working with My webMethods 8.0.

Migrate Blaze Rules

Migrate the projects that contain your Blaze rules from Blaze 6.5 to Blaze 6.8. For instructions, see Blaze Advisor Migration 6.8.

Open Blaze Advisor 6.8, open each project that contains 7.x Blaze rules, and deploy the rules to Integration Server 8.0. For instructions, see Using Blaze Rules with BPM and CAF 8.0.

Migrate Business Processes

You migrate 7.x business processes by migrating different types of data, depending on your goals.

If you want to start new instances of migrated 7.x process models in your 8.0 installation, do not have any running 7.x process instances, and do not need to resubmit any 7.x process instances, you must migrate your design-time data. Design-time data are the definitions of your business process models.

If you want to finish 7.x process instances that are already in progress or resubmit 7.x process instances that have completed or failed, you must migrate your run-time data. Run-time data is the complete set of information about 7.x business process models and in progress, completed, or failed 7.x process instances that is stored in the ProcessAudit database component and, if you used it, the Process Engine database component.

If you want to start new instances of migrated 7.x process models in webMethods 8.0, and you want to finish 7.x process instances that are in progress or resubmit 7.x process instances that have completed or failed, you must migrate both your design-time and run-time data.

Migrate Design-Time Data

1 Export business process projects from Designer 7.x as follows:

a Open Designer 7.x and point to your 7.x workspace.

b Go to the File > Export wizard. In the Select panel, click General > Archive File as the export destination and then click Next.



c In the Archive File panel, select all projects that contain business processes. In the To archive file field, specify the directory to which to export the projects. In the Options area, you can accept the default file format options or select others. Click Finish.

d Shut down Designer 7.x.

2 Import 7.x business process projects into Designer 8.0 as follows:

a Open Designer 8.0 and point to a new 8.0 workspace.

b Go to the File > Import wizard. In the Select panel, go to General > Existing Projects into Workspace and then click Next.

c In the Import Projects panel, click Select Archive File, and then select the archive file that contains the projects you exported. The projects appear in the Projects box; select the projects to import and click Finish.

d Make sure the imported projects appear in the Solutions tab, under the Processes node.

3 The Designer 8.0 local metadata implementation is different from that used in earlier releases. Close all projects and then reopen them to re-extract local metadata from the projects so users can search it.

4 If you are migrating from Designer 7.1.2, you must migrate your logical server definitions as follows:

a Open Designer 7.1.2 and export the logical server definitions.

1 Go to Window > Preferences. On the Preferences dialog box, in the left navigation bar, go to webMethods > Process Development > Logical Servers.

2 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 file extension .properties. Click Open.

3 Click OK to close the Preferences dialog box.

b Open Designer 8.0 and import the logical server definitions.

1 Go to Window > Preferences. On the Preferences dialog box, in the left navigation bar, go to Software AG > Integration Servers. The list on the left shows your logical servers, called Integration Servers in Designer 8.0.

2 Click Import, select the .properties file you exported, and click Open. Designer asks whether you want to overwriting existing servers; click OK twice.

3 Redefine the connections to the Integration Servers that will run process steps. For instructions, see webMethods Designer Service Development Help 8.0.



Migrate Run-Time Data

1 Shut down all Integration Servers that connect to the 7.x ProcessEngine or ProcessAudit database component.

2 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 each database component by running the command below.


3 If you are using DB2 RDBMS, issue a DB2 REORG command on the WMPROCESS, PRTPROCESS, PRTINSTANCEITER, and WMPRTXREF tables from the DB2 command line. For example:

Migrate Tasks

You migrate 7.x tasks by migrating different types of data, depending on your goals.

If you want to start new instances of migrated 7.x task application projects in 8.0, you do not have any running 7.x task instances, and you do not need to resubmit any 7.x task instances, migrate your design-time data to 8.0. Design-time data are your task application projects.

If you want to finish 7.x task instances that are in progress or resubmit 7.x task instances that have completed or failed, migrate your run-time data. Run-time data is the complete set of information about 7.x task application projects and in progress or completed 7.x task instances.

If you want to start new instances of migrated 7.x task application projects in 8.0, and you want to finish 7.x task instances that are in progress or resubmit 7.x task instances that have completed or failed, migrate both your design-time data and your run-time data.

dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw}-c {ProcessEngine|ProcessAudit} -v latest -l db_server_URL-u existing_db_user -p password

reorg table database_user.prtinstanceiter



Migrate Task Design-Time Data

Export Task Application Projects from Designer 7.x

1 Start Designer 7.x and point to your 7.x workspace.

2 Go to the File > Export wizard. In the Select panel, click General > Archive File as the export destination and then click Next.

3 In the Archive File panel, select all projects that contain task applications. In the To archive file field, specify the directory to which to export the projects. In the Options area, you can accept the default file format options or select others. Click Finish.

4 Shut down Designer 7.x.

Import 7.0 SP2 Task Application Projects into Designer 8.0

1 Open Designer 8.0 and point to a new 8.0 workspace.

2 Go to Window > Preferences > Server > Runtime Environments. Make sure the Installed server runtimes list includes a My webMethods Server 8.0. If it does not, add one.

3 Go to Software AG > Task Development, make sure all your other task-related Designer preferences are correct, and then click OK.

4 Go to the File > Import wizard. In the Select panel, go to webMethods > Existing CAF Projects into Workspace and then click Next. In the Import Projects panel, click Select Archive File, and then select the archive file that contains the projects you exported. The projects appear in the Projects box; select the projects to import and click Finish.

5 Make sure the imported projects appear in the Solutions tab, under the Tasks node.

6 If errors appear in the Problems tab, click the Navigator tab, right-click each task application project, click CAF Tools, and then click Repair CAF Project. If errors still appear, restart Designer.

7 Publish the imported projects to My webMethods Server. For instructions, see webMethods Designer BPM Task Development Help 8.0.

Migrate Task Run-Time Data

1 Start My webMethods Server 7.x and My webMethods Server 8.0.

2 Log on to My webMethods Server 8.0 as sysAdmin.

3 On the Administration Dashboard, click Migration and then click Tasks Migration.

4 In the Server URL field, enter the URL for My webMethods Server 7.x (by default, http://MWS:8080). In the Task Type ID field, select the task name/label for task instances to migrate. In the Sysadmin Password field, type manage.



5 Click Start Migration. After the migration is complete, My webMethods Server displays a message that lists the number of task instances it migrated.

6 Repeat these steps for all task instances to migrate.

Migrate Optimize Data

Migrate Optimize Database Components

On the machine on which you installed the Database Component Configurator, go to the 8.0_installation_directory\common\db\bin directory, open a command window, and migrate each database component by running the command below.


Update Broker Connection Information

If the Broker you use with Optimize is using either a non-default name or port, start the Integration Server 8.0 that hosts the Optimize Support package and open Integration

Server Administrator. Go to the Packages > Management page, click for the WmOptimize package, enter the Broker URL field value that you noted in “Before You Begin” on page 15, and click Submit.

If you are using Optimize for Process, start the Integration Server 8.0 that hosts a Process Engine and open Integration Server Administrator. Go to the Packages > Management page

and click for the WmPRT package. In the Broker URL field, change localhost to the correct host, the port to the correct port, and Broker #1 to the correct Broker name, and then click Submit.

dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw}-c {Analysis|ProcessTracker|CentralConfiguration|DataPurge|Reporting|Staging}-v latest -l db_server_URL -u existing_db_user -p password

Important! In the URLs, if you are using DB2, you must specify schema using all capital letters. In addition, you must specify the options CreateDefaultPackage=true,ReplacePackage=true, and DynamicSections=3000. These settings will affect all database components in the same schema or database.

Important! Do not change the broker:// or /analysis parts of the URL.



Deploy the Optimize Environment

Unless otherwise noted, see Configuring BAM 8.0 for detailed instructions on each step in the sections below.

To Not Reuse the 7.x CCS Environment Definition

If you do not want to reuse your 7.x Central Configuration System (CCS) Environment definition, start My webMethods Server and configure your Optimize 8.0 environment. Then skip to “Deploy the Optimize 8.0 Environment” on page 34.

To Reuse the 7.x CCS Environment Definition

If you want to reuse your 7.x CCS environment definition, follow the steps below.

1 Start My webMethods Server.

2 Import the 7.x CCS Environment you exported in “Before You Begin” on page 15. When prompted, confirm the migration. When asked “Do you wish to migrate the environment to the latest version?", click Yes. The CCS imports the 7.x environment and migrates it to 8.0 Optimize Logical Servers.

3 In My webMethods, go to the Applications > Administration > System-Wide > Environments > Define Environments page. Under Environment Name, click the environment you imported.

4 If you are using Optimize for Infrastructure, do the following:

a Click the Design Servers tab, click Add, select Infrastructure Data Collector v8.0.1.0, and

then click OK. Click the Map Servers tab and click in the Actions column for Infrastructure Data Collector v8.0.1.0. In the Edit Host Mapping dialog box that displays, move Infrastructure Data Collector v8.0.1.0 from the Available Hosts to Map list to the Mapped Hosts to This Logical Server list, and then click Save.

b Click the Configure Servers tab, open the Infrastructure Data Collector v8.0.1.0 tree, and then click Collector Settings.

Go to the Infrastructure Data Collector_7.x_directory\config directory and open the infradc.cnf file.

Copy the DataCollectorName property setting from the 7.x infradc.cnf file to the Collector Name field on the Configure Servers tab. If you are using the default DataCollectorName InfraDC@host\:port, remove the backslash from the copied value.

The default polling interval was 4 minutes in the 7.x release but is 5 minutes in the 8.0 release. If you want to use your 7.x setting instead of the 8.0 default, copy the pollinterval property setting from the 7.x infradc.cnf file to the Monitor Polling Interval field.



Select the check box next to each Load asset type for which you want to load metadata. If you were monitoring Brokers or Integration Servers in your 7.x environment, select those check boxes. If you will be monitoring Enterprise Transaction Systems (ETS) assets, select the appropriate check boxes.

c Click Save.

5 Click each tab except the Validate tab that shows ; the icon changes to . If you change any settings, and the tab has a Save button, click Save. When all tabs except the

Validate tab show , click the Validate tab.

Deploy the Optimize 8.0 Environment

1 Start the Optimize 8.0 components you installed. These components can include the Analytic and Prediction engines, Infrastructure Data Collector, and the Web Services Data Collector.

2 Deploy your Optimize 8.0 environment.

3 If you are using Optimize for Infrastructure, go to the Infrastructure Data Collector_directory\config directory and open the infradc.cnf file. Set the metadataloaded property to false, save the file, and restart Infrastructure Data Collector.

Rediscover Assets and Reestablish Monitoring

If you are using Optimize for Infrastructure, owing to changes in the definition of metadata, Optimize for Infrastructure assets that were monitored in 7.x will not automatically be monitored in 8.0. Historical readings are retained, but to restart monitoring after migration, you must rediscover the assets and reestablish monitoring for them as described below.

1 In My webMethods, go to the Applications > Administration > Analytics > Infrastructure Components > Discovery page. In the Actions column, rerun discovery for assets you want to monitor.

2 Go to the Applications > Administration > Analytics > Infrastructure Components > Monitored Components page. Select the components and KPIs to monitor that you noted in “Before You Begin” on page 15.

3 Some predefined Optimize KPIs have changed as follows:

IS Service Count now generates delta values. To monitor cumulative values, click IS Service, click Add KPIs, and then click CumulativeCount.

BrokerStats.numEventsPublished, BrokerStats.numEventsQueued and BrokerStats.numEventsDelivered KPIs now generate delta values. To monitor cumulative values, click Broker, click Add KPIs, and then click BrokerStats.cumulativeNumEventsPublished, BrokerStats.cumulativeNumEventsQueued, and BrokerStats.cumulativeNumEventsDelivered.



ClientStats.numEventsPublished, ClientStats.numEventsDelivered and ClientStats.numEventsRetrieved now generate delta values. To monitor cumulative values, click Custom Adapter, click Add KPIs, and then click ClientStats.cumulativeNumEventsPublished, ClientStats.cumulativeNumEventsDelivered, and ClientStats.cumulativeNumEventsRetrieved.

4 Go to the Applications > Administration > Analytics > Infrastructure Components > Discovery page. Click Add Asset. In the Asset Type list, click SNMP, and then follow the instructions in Administering webMethods Optimize 8.0 to rediscover and monitor SNMP agents.

Migrate Deployer Data

Follow the steps below to upgrade your Deployer project builds.

1 Upgrade all source webMethods servers to the latest 8.0 release.

2 Start the upgraded source servers and connect them to Deployer 8.0.

3 Start Deployer. Deployer automatically upgrades your project builds. For details and errors, see the Integration Server 8.0 server log, stored by default in the Integration Server_directory\logs directory.

4 Rebuild any project builds that were not upgraded because they referenced a source server that was not connected in step 2, or because they referenced the Integration Server that hosts Deployer as a source server.

Note: As a result of the KPI definition changes, data previously collected for IS Service, Broker, and Custom Adapter common event maps are deleted during migration.

Important! If a project build references a source server that is not connected, the build will not be upgraded and you will have to rebuild it manually after upgrade.

If a project references the Integration Server that hosts Deployer as a source server, the project build will not be upgraded and you will have to rebuild it manually after upgrade.



Update Database URLs

1 Start Integration Server 8.0 and open Integration Server Administrator.

2 Go to the Settings > JDBC Pools page. For each Pool Alias except the TN pool alias, click Edit in the Edit Pool Alias column. In the Database URL field, add the DataDirect Connect connection option MaxPooledStatements=35. This connection option improves performance by caching prepared statements.

3 Restart Integration Server 8.0.

Note: You do not have to add this option for Trading Networks because Trading Networks caches its prepared statements using its own pooling mechanism.


2 Installing Latest 8.0 Over 8.0 FCS

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38f


Back Up the 8.0 FCS webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40

Upgrade Your RDBMSs or Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Uninstall Certain Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42


Complete the ApplinX Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Complete the EntireX Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Complete the Web Services Stack Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45



Migrate My webMethods Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Migrate Blaze Rules and Rule Maintenance Applications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48


Migrate Optimize and Monitor Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48




Overview

This upgrade procedure explains how to install the latest webMethods 8.0 product releases over webMethods 8.0 FCS products. In some cases, you will uninstall the FCS products and then install the latest releases. In other cases, the installer will install the latest releases in a new directory. In most cases, the Software AG Installer will install the latest releases over the FCS products.

For some products, you must perform additional tasks to complete the upgrade or to migrate data. This chapter provides instructions for those tasks.

Before You Begin

If you are going to upgrade Integration Server, allow all guaranteed delivery jobs to finish running. To do so, connect Integration Server to webMethods Broker; in Integration Server Administrator, go to the Settings > Resources > Store Settings page and wait for Current Documents in Outbound Store in the Outbound Document Store area to reach 0.

If you have a cluster of Integration Servers, stop routing client requests to one Integration Server in the cluster and perform the step above, then do the same for the next Integration Server in the cluster, and so on for all Integration Servers in the cluster.

If you are upgrading business processes, allow them to finish running or use Monitor to stop them.


a If you want to reuse your 8.0 FCS Central Configuration System (CCS) Environment definition, export the 8.0 FCS environment to a file. For instructions, see Administering webMethods Optimize 8.0.

b If the Broker you use with Optimize is using a non-default name or port, start Integration Server 8.0 FCS and open Integration Server Administrator. Go to the

Packages > Management page, click for the WmOptimize package, and note the Broker URL field value. You will have to re-enter this information after upgrading.

Important! Because many products share files, you must upgrade all products that are in the same installation directory.





If you are going to upgrade My webMethods Server, the upgrade procedure will reset the values below to their default values. If you customized any of these values, start My webMethods Server, open My webMethods, and follow the steps below.


1 Shut down the 8.0 FCS products listed below if they are running on the machine on which you are going to overinstall.


The upgrade procedure will reset... Log onto My webMethods Server...

Your CAF Application Runtime Configuration.

As sysadmin, go to the Administration > Configu-ration > CAF Application Runtime Configuration page and click Configure Global Defaults. On the Configure Global Defaults page, expand the User Attributes link. Print each page of user attributes.


As sysadmin, go to the Administration > User Interface page, and click each of the Rules links. Note the values.

Your task chart portlets. As Administrator, go to the Navigate > Applica-tions > Monitoring > Business > Tasks > Task Chart page. For each chart portlet, click the Menu icon and select Properties. Note the chart prop-erties.

The task global change and sched-ule rules.

As Administrator, go to the Navigate > Applica-tions > Administration > Business > Tasks > Task Engine Administration page and click the Man-age Global Change Rules and Manage Global Schedule Rules icons. Click each Rule link and note the rule properties.





Back Up the 8.0 FCS webMethods Installation

1 Back up the entire 8.0 FCS webMethods installation directory.

If you have a cluster of Integration Servers, back up the installation for each Integration Server in the cluster.


Running as applications: ApplinXEntireX (all Brokers and RPC Servers)My webMethods Server* and Task EngineOptimize Analytic Engine, Prediction Engine, and Web Service Data CollectorReport Server













2 Back up all 8.0 FCS databases except Tamino XML Server. For instructions, see your RDBMS vendor documentation.

3 Back up Tamino XML Server 8.0 FCS as follows:

a Start Tamino Manager. Under Tamino > Databases, click the node for a Tamino XML Server database to back up.

b Under the database node, right-click the Backups node and then click Backup. The Backup dialog box appears. Follow the instructions in the dialog box to create the backup.

c Repeat these steps until you have backed up all of your Tamino XML Server databases.

d Copy the backups to a safe location.

4 Back up CentraSite 8.0 SP1 as follows:

a Start the System Management Hub.

b Right-click the CentraSite > Registry/Repository > Backups node and then click Backup.

c Copy the backup to a safe location.

5 If you are going to upgrade My webMethods Server, go to the 8.0_installation_directory\MWS\server\server_instance\deploy directory and delete all .xml files.

Upgrade Your RDBMSs or Databases

webMethods System Requirements 8.0 lists the supported RDBMSs for most products, or refers to additional documentation that lists supported databases for some products. Check your RDBMSs or databases against the list; if the version you are using is not supported by your latest 8.0 products, you must upgrade to a supported version before continuing with the instructions in this chapter.

Important! For My webMethods Server, you must back up the 8.0 FCS webMethods installation directory and the MywebMethodsServer database component at the same time. The two must be in sync, or you will experience problems. The same is true for Optimize and the Optimize database components.



Uninstall Certain Products

Uninstall CentraSite 8.0 SP1, Tamino XML Server 8.0, and Designer 8.0 (March 2009 Release)

Uninstall CentraSite 8.0 SP1, Tamino XML Server 8.0, and Designer 8.0 (March 2009 release). For instructions, see webMethods Installation Guide 8.0 and 8.0 SP1 (March 2009 release). The uninstallation of CentraSite 8.0 SP1 does not delete the Registry Repository files or, on Windows systems, the Windows registry entries that point to those files. When you install CentraSite 8.0 SP3, the installer will detect the Registry Repository 8.0 SP1 files and configure CentraSite 8.0 SP3 to use them.

Uninstall EntireX 8.1

Uninstall EntireX 8.1. For instructions, see webMethods Installation Guide 8.0 FCS (June 2009 release).

Delete Trading Networks Additional Reports 8.0

Go to the 8.0_installation_directory\reporting\reports directory and delete the file SAG_ TradingNetworks(Additional).zip.


Go to the Software AG Documentation Web site and download Software AG Installation Guide 8.0 GA (December 2009). Follow the instructions in that guide to install the latest 8.0 products, with the additional guidelines or differences noted below.

For installation directory, specify the 8.0 FCS webMethods installation directory.

If you have a cluster of Integration Servers, overinstall every Integration Server in the cluster. If you have a cluster of My webMethods Servers, choose one node to overinstall. You will upgrade the other nodes later, as described in “Migrate My webMethods Server Data” on page 47.

Note: Do not uninstall Designer 8.0 (June 2009 release).

Note: Trading Networks Additional Reports were merged into Trading Networks Reports in the webMethods 8.0 GA release.

Important! If your products are distributed across multiple machines, install CentraSite before installing any other product.




On the Software AG Installer’s product selection tree, existing 8.0 FCS products are shown in gray followed by the word “Installed” (wizard mode) or the letter “I” (console mode). Select the latest 8.0 products to install; be sure to select all necessary components of each product (see Software AG Installation Guide 8.0 GA, Typical Development Installations for guidance).

If you are installing a product other than ApplinX and CentraSite that uses an external RDBMS, select Database Configuration.

You can also select new products and optional items such as Documentation.


If you selected 8.0 products that are not yet installed on your machine, see Software AG Installation Guide 8.0 GA for instructions on providing the required product configuration information.

If you had the installer automatically migrate Integration Server data or upgrade My webMethods Server server instances, details of the migration or upgrade are written to the migrationLog.txt file in the 8.0_installation_directory\install\logs directory. If you are using the installer wizard (as opposed to console mode), the installer’s Finish panel provides a link to the file.

If you installed new 8.0 products, create any necessary database components. For detailed information and instructions, see Software AG Installation Guide 8.0 GA.

Product Action

Integration Server

Indicate whether you want the installer to migrate Integration Server 8.0 FCS data to the Integration Server 8.0 latest installation. The installer will automatically run the Integration Server Migration Utility to do the following:

Migrate the embedded database if you used it with Integration Server 8.0 FCS.

Delete Integration Server 8.0 FCS configuration files, fixes, and properties that are no longer used by Integration Server 8.0 latest.

Merge the Integration Server port.cnf and listeners.cnf files.

Note: You can instead choose to run the migration utility manually after installation; see “Migrate Integration Server Data” on page 45.


Indicate whether you want the installer to automatically upgrade My webMethods Server 8.0 FCS server instances. If you do not, you must upgrade them manually one at a time after installation.



Complete the ApplinX Upgrade

1 Back up the database you used as your ApplinX 8.1 repository. For instructions, see your database vendor’s documentation.

2 Open Designer 8.0 latest. In the ApplinX perspective, in the ApplinX Explorer view, right-click each ApplinX application and click Synchronize Repository.

3 Upgrade your JSP or .NET Web applications using the ApplinX Web Application Manager. For instructions, see Framework Management in the ApplinX documentation.

4 Determine whether you modified one or more of these files in ApplinX 8.1:

GXApplinXService.ini

start-gxserver.bat

start-gxserver.sh

gxadmin.bat

gxadmin.sh

config/gxadmin.prp

config/gxstartup.prp

Copy any changes you made from the 8.1 backup files to the equivalent ApplinX 8.1 files. The backup files are located in the ApplinX installation directory and have the file extension .bak.

Complete the EntireX Upgrade

Go to the EntireX_8.1_directory\config\etb directory and copy all directories to the EntireX_8.1_directory\config\etb directory. Then start the EntireX Broker administration service as follows:

System Actions

Windows Go to the Windows Services window and start the Software AG EntireX Broker service.

UNIX Run this command:

EntireX_8.1_directory/bin/sag<x>etbsrv restart



Complete the Web Services Stack Upgrade

If you upgraded the Web Services Stack from 8.0 (March 2009 release), the installer installed Web Services Stack 8.0 SP3 in a new directory and upgraded a Web Services Stack Web application in the Tomcat Kit directory.

If you upgraded from Web Services Stack 8.0 (March 2009 release), or if you upgraded from a Web Services Stack 8.0 SP1 installation that was previously upgraded from 8.0, the installer does not delete the 8.0 or 8.0 SP1 installation.

On Windows systems, the installer also does not delete the Web Services Stack 8.0 entry from the Windows Add or Remove Programs utility. Do not use the Add or Remove Programs utility to remove Web Services Stack 8.0; doing so would remove the Web application in the Tomcat Kit directory that is used by the Web Services Stack SP3 installation.

For instructions on verifying the Web Services Stack installation, see Introduction to Web Services Stack, Verifying Web Services Stack Installation, in the Web Services Stack documentation.


If you have a cluster of Integration Servers, repeat this procedure for each Integration Server in the cluster.


If you had the installer automatically migrate your Integration Server 8.0 data, skip this section and go to “Customize Startup Files” on page 46.

1 The migration utility writes details of the migration to the migrationLog.txt file in the 8.0_installation_directory\install\logs directory. By default, the utility writes INFO, ERROR, and FATAL messages to the log. If you want to increase the logging level to DEBUG, go to the Integration Server_8.0_directory\bin\migrate directory, open the file log4j.properties file in a text editor, set the log4j.logger.Migration property to DEBUG, MigrationFile, and save and close the file.

2 Run the Integration Server migration utility, as follows:

a Go to the Integration Server_8.0_directory\bin\migrate directory and run the command migrate.{bat|sh}.

b If Integration Server 8.0 FCS used the embedded database, the utility asks whether to migrate it. If you enter Y, the utility will convert the 8.0 FCS database tables to the format used in Integration Server 8.0 latest.

Note: If you do not migrate the embedded database now, Integration Server 8.0 latest will migrate it automatically on startup.



c The utility asks whether to begin migration. If you want the utility to exit without migrating any data, enter N. If you want the utility to migrate data based on the settings you specified, enter Y; the utility prints progress messages to the command window and the migration log. If migration completes successfully, the utility does the following:

Deletes 8.0 FCS configuration files that are no longer used by Integration Server 8.0 latest.

Deletes 8.0 FCS properties that are no longer used by Integration Server 8.0 latest from the 8.0 latest configuration files and merges the Integration Server port.cnf and listeners.cnf files.

Deletes all fixes you applied to Integration Server 8.0 FCS.


If you made any changes to your Integration Server 8.0 FCS server.{bat|sh} or setenv.{bat|sh} files, manually reproduce those change in the corresponding Integration Server 8.0 latest files. The 8.0 FCS files are in the backup you took before installing 8.0 latest. The 8.0 latest files are located in the Integration Server_8.0_directory\bin directory.

Migrate the Integration Server Database ComponentsFor instructions, see “Migrate the Integration Server Database Components” on page 24. In the instructions, substitute “8.0 FCS” for “7.x.”

Update WSDLsIn Integration Server Administrator, go to the Settings > Extended page. If you have the extended setting watt.server.xml.ncname.encode.backward.compatibility and it is set to true, reset it to false. Then regenerate the clients for all Provider Web services that have an operation with field names starting with "xml" in the input signature, output signature, header, or faults.


1 Shut down all Integration Servers that connect to the 8.0 FCS TradingNetworks database component.






3 If you installed Trading Networks or Optimize for B2B reports, enable them. For instructions, see Generating webMethods Reports 8.0 GA.

Migrate My webMethods Server Data

1 If you did not choose the Upgrade My webMethods Server Instances check box during installation, run the command below for each My webMethods Server instance. The command copies all new My webMethods Server 8.0 components to the specified server instance and upgrades the server instance’s My webMethods Server_directory\server\server_instance\config directory.

If you have a cluster of My webMethods Servers, run this command on the node you overinstalled only. You will upgrade the other nodes later.

2 On the machine on which you installed the Database Component Configurator, go to the 8.0_installation_directory\common\db\bin directory and open a command window. Migrate the My webMethods Server database component by running this command:


3 Go to the My webMethods Server_8.0_directory\bin directory and start each My webMethods Server instance by running the command below. The command redeploys 8.0 FCS components to the My webMethods Server 8.0 latest. When the command is finished, the My webMethods Server shuts down automatically.

4 If you have a cluster of My webMethods Servers, delete the 8.0 FCS cluster nodes you have not upgraded and then add 8.0 latest nodes. For instructions, see Administering My webMethods Server 8.0.

mws.{bat|sh -s server_instance upgrade

dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw}-c MWS -v latest -l db_server_URL -u existing_db_user -p password

Note: Depending on the number of webMethods product interfaces and language packs you installed, this process might take a long time to complete (for example, an hour).




Migrate Blaze Rules and Rule Maintenance Applications

1 Migrate the projects that contain your Blaze rules from Blaze 6.6.1 to Blaze 6.8. For instructions, see Blaze Advisor Migration 6.8.

2 Open Blaze Advisor 6.8, open each project that contains 8.0 FCS Blaze rules, and deploy the rules to Integration Server 8.0 latest. For instructions, see Using Blaze Rules with BPM and CAF 8.0 GA.

3 Open Blaze Advisor 6.8 and deploy each RMA to My webMethods Server 8.0 latest. For instructions, see Using Blaze Rules with BPM and CAF 8.0 GA.


Follow the instructions in “Migrate Run-Time Data” on page 30, with one exception: to migrate design-time data, simply open Designer 8.0 latest and point to the 8.0 FCS workspace. In the instructions, substitute “8.0 FCS” for “7.x.”

Migrate Optimize and Monitor Data


On the machine on which you installed the Database Component Configurator, go to the 8.0_installation_directory\common\db\bin directory, open a command window, and migrate each database component by running the command below.


dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw}-c {Analysis|ProcessTracker|CentralConfiguration|Reporting|Staging}-v latest -l db_server_URL -u existing_db_user -p password

Important! In the URLs, if you are using DB2, you must specify schema using all capital letters. In addition, you must specify the options CreateDefaultPackage=true,ReplacePackage=true, and DynamicSections=3000.

These settings will affect all database components in the same schema or database.




If the Broker you use with Optimize is using either a non-default name or port, start Integration Server 8.0 latest and open Integration Server Administrator. Go to the

Packages > Management page, click for the WmOptimize package, and enter the Broker URL field value that you noted in “Before You Begin” on page 38.


Unless otherwise noted, see Configuring BAM 8.0 for detailed instructions on each step below.

1 Start My webMethods Server. For instructions, see Administering My webMethods Server 8.0.

2 If you do not want to reuse your 8.0 FCS Central Configuration System (CCS) Environment definition, configure your Optimize 8.0 latest environment.

If you want to reuse your 8.0 FCS CCS Environment definition, import the 8.0 FCS CCS Environment you exported in “Before You Begin” on page 38. When prompted, confirm the migration. When asked “Do you wish to migrate the environment to the latest version?", click Yes. The CCS imports the 8.0 FCS environment and migrates it to 8.0 latest Optimize Logical Servers.

3 Start the Optimize 8.0 latest components you have installed. These components can include the Analytic and Prediction engines, Infrastructure Data Collector, and the Web Services Data Collector.

4 Deploy your Optimize 8.0 latest environment.


6 Go to the Applications > Administration > Analytics > Rules > Rule List page. Delete these predefined rules:

Infrastructure Data Collector About to Run Out of Memory.

Broker Server Low Guaranteed Disk Space.

Complete 24-Bit Region Full.

Complete 31-Bit Region Full.

Complete SD File Full.

Complete Spool File Full.

Complete TIBTAB Full.

Natural Buffer Pool OS Many Objects Loads.

Natural Editor Buffer Pool Full.



Natural Editor Work Full.

Natural Roll Server Many LRB Steals.

Failure Status for all products except Infrastructure Data Collector, Integration Server, and Broker Server. Use keyword search to find this rule.

Critical Resource Message for all products. Use keyword search to find this rule.

Re-enable Reports

If you upgraded Optimize or Monitor reports, reenable them. For instructions, see Generating webMethods Reports 8.0 GA.


Follow the steps below to upgrade your Deployer project builds.

1 Upgrade all source webMethods servers to the latest 8.0 release.

2 Start the upgraded source servers and connect them to Deployer 8.0 latest.

3 Start Deployer. Deployer automatically upgrades your project builds. For details and errors, see the Integration Server 8.0 server log, stored by default in the Integration Server_directory\logs directory.

4 Rebuild any project builds that were not upgraded because they referenced a source server that was not connected in step 2, or because they referenced the Integration Server that hosts Deployer as a source server.

Important! If a project build references a source server that is not connected, the build will not be upgraded and you will have to rebuild it manually after upgrade.

If a project references the Integration Server that hosts Deployer as a source server, the project build will not be upgraded and you will have to rebuild it manually after upgrade.


3 Installing Latest 8.0 SPx Over Earlier 8.0 SPx

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52


Back Up the 8.0 webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Upgrade Your RDBMSs or Databases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Install 8.0 SPx Products . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Complete the ApplinX Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55


Migrate Optimize and Monitor Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56



Overview

This upgrade procedure explains how to install the latest 8.0 service packs over earlier 8.0 service packs.

Before You Begin

If you are going to upgrade Optimize, and the Broker you use with Optimize is using a non-default name or port, start Integration Server 8.0 SP1 and open Integration Server

Administrator. Go to the Packages > Management page, click for the WmOptimize package, and note the Broker URL field value. You will have to re-enter this information after upgrading.


1 Shut down the 8.0 products listed below if they are running on the machine on which you are going to overinstall.


Important! You must upgrade products and migrate data in the order the instructions are presented in this chapter.







Running as applications:ApplinXEntireX (all Brokers and RPC Servers)My webMethods Server* and Task EngineOptimize Analytic Engine, Prediction Engine, and Web Service Data CollectorReport Server












Back Up the 8.0 webMethods Installation

1 Back up the entire 8.0 webMethods installation directory.

2 Back up the 8.0 databases for the products you are upgrading. For instructions, see your RDBMS vendor documentation.

Upgrade Your RDBMSs or Databases

webMethods System Requirements 8.0 GA lists the supported RDBMSs for most products, or refers to additional documentation that lists supported databases for some products. Check your RDBMSs or databases against the list; if the version you are using is not supported by your latest 8.0 products, you must upgrade to a supported version before continuing with the instructions in this chapter.

Install 8.0 SPx Products

Go to the Software AG Documentation Web site and download Software AG Installation Guide 8.0 GA (December 2009). Follow the instructions in that guide to install 8.0 SPx products with the additional guidelines or differences noted below.

For installation directory, specify the 8.0 webMethods installation directory.

On the Software AG Installer’s product selection tree, existing products are shown in gray followed by the word “Installed” (wizard mode) or the letter “I” (console mode). Select Optimize and Monitor 8.0 SP2; be sure to select all necessary components of each product (see Software AG Installation Guide 8.0 GA, Typical Development Installations for guidance).

You can also select new products and optional items such as Documentation. If you select new products that are not yet installed on your machine, see Software AG Installation Guide 8.0 GA for instructions on providing the required product configuration information.


Important! For Optimize, you must back up the 8.0 webMethods installation directory and the Optimize database components at the same time. All must be in sync, or you will experience problems.




Complete the ApplinX Upgrade

1 Back up the database you used as your ApplinX 8.1 SPx repository. For instructions, see your database vendor’s documentation.

2 Open Designer 8.0 SP1. In the ApplinX perspective, in the ApplinX Explorer view, right-click each ApplinX application and click Synchronize Repository.

3 Upgrade your JSP or .NET Web applications using the ApplinX Web Application Manager. For instructions, see Framework Management in the ApplinX documentation.

4 Determine whether you modified one or more of these files in ApplinX 8.1 SPx:

GXApplinXService.ini

start-gxserver.bat

start-gxserver.sh

gxadmin.bat

gxadmin.sh

config/gxadmin.prp

config/gxstartup.prp

Copy any changes you made from the 8.1 SPx backup files to the equivalent ApplinX 8.1 SPx files. The backup files are located in the ApplinX installation directory and have the file extension .bak.


For each My webMethods Server you have installed, go to the My webMethods Server_8.0_directory\bin directory and run this command:

Run this command to start each My webMethods Server:

mws.{bat|sh} -s server_instance update




Migrate Optimize and Monitor Data


If the Broker you use with Optimize is using either a non-default name or port, start Integration Server 8.0 SP1 and open Integration Server Administrator. Go to the Packages

> Management page, click for the WmOptimize package, and enter the Broker URL field value that you noted in “Before You Begin” on page 52.


Unless otherwise noted, see Configuring BAM 8.0 for detailed instructions on each step below.

1 Start My webMethods Server. For instructions, see Administering My webMethods Server 8.0.

2 Start the new Optimize 8.0 SPx components you have installed. These components can include the Analytic and Prediction engines, the Infrastructure Data Collector, and the Web Services Data Collector.

3 Deploy your new Optimize 8.0 SPx environment.



4 Performing Side-by-Side Migration from 7.x to Latest 8.0 Releases

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Requirements, Recommendations, and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Back Up the 7.x webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Back Up 7.x Database Components and Upgrade RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . 60



Migrate webMethods Broker and JMS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63




Migrate Blaze Rules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75


Migrate Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

Migrate Optimize Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76





Overview

This upgrade procedure explains how to upgrade webMethods 7.1.2, 7.1.3, 7.2, or 7.2.1 product releases to the latest webMethods 8.0 product releases.


The product releases from which you can upgrade are referred to as 7.x. However, you can only upgrade from a 7.1.2, 7.1.3, 7.2, or 7.2.1 release. If you want to upgrade from a 7.1 or 7.1.1 release, you must first upgrade to 7.1.2 or 7.1.3.

The latest webMethods 8.0 product releases to which you can upgrade are referred to as 8.0.

Requirements, Recommendations, and Notes

Because many products share files, you must upgrade all products that are in the same installation directory.



If you want to retain your 7.x environment after upgrading, shut down 7.x Integration Servers, Trading Networks Servers, and Optimize components that connect to webMethods database components, copy the databases using vendor instructions, migrate the copied database components, and use the migrated database components with your 8.0 products. This is not necessary for My webMethods Server 8.0, for which you will create a new database component.

Before You Begin

If you are going to upgrade Deployer, do the following:

a Apply DEP_7.1.2_Fix13 to Deployer using the instructions in the fix readme. Fixes are available from the Software AG Knowledge Center.

b Migration of Deployer data after installation requires both Deployer 7.x and Deployer 8.0 to be running. If you are going to install Deployer 8.0 on the same machine as Deployer 7.x, and you want Deployer 8.0 to use the same ports that Deployer 7.x used, change the ports used by the 7.x host Integration Server. For instructions, see webMethods Integration Server Administrator’s Guide 7.1.1.

Note: This procedure does not explain how to upgrade from CentraSite 7.x to Centra-Site 8.0 SP3. If you need to perform that upgrade, contact Software AG Global Con-sulting Services. CentraSite should be upgraded before any other product.




If you are going to upgrade Monitor, apply Monitor_7-1-2_Fix5 and Monitor_7-1-2_MWS_Fix4 to My webMethods Server using the instructions in the fix readmes. Fixes are available from the Software AG Knowledge Center.


a If you want to reuse your Central Configuration System (CCS) Environment definition, export the environment to a file. For instructions, see webMethods Optimize for {Infrastructure|Process} Administrator’s Guide 7.1.

b If you are using Optimize for Infrastructure, start My webMethods Server and open My webMethods. Go to the Administration > Analytics > Infrastructure Components > Monitored Components page and note the components and KPIs you are monitoring. You will have to reselect them after upgrading.

Data from previously monitored SNMP data cannot be migrated. Start Infrastructure Data Collector, open Infrastructure Data Collector Administrator, and clean up previously monitored SNMP data by deleting SNMP metadata. For instructions, see webMethods Optimize for Infrastructure Administrator’s Guide 7.1, Deleting SNMP Component Assets.

In My webMethods, go to the My webMethods > System Settings > Servers page. If you have server settings configured that you want to reuse, such as Server name, Host name, and Port, note these settings. You will have to reenter them after migration.

Back Up the 7.x webMethods Installation

1 Back up your Designer workspace as follows:

If you are storing your .process files or task application projects in a source control system, check in all projects.

If you are not storing your .process files or task application projects in a source control system, back up your .process files and task application projects using the Eclipse Export wizard, as follows:

a Open Designer and point it at the workspace.

b Go to the File > Export wizard.

c In the Select panel, do one of the following:


To export... Identify the export destination...

.process files Click webMethods> Process File and then click Next.

Task application projects Click General> Archive File and then click Next.




d In the Archive File panel, select all .process files or task application projects to export. In the To archive file field, specify the directory to which to export. In the Options area, you can accept the default file format options or select others.

e Click Finish.

f Shut down Designer.

2 If you want to shut down webMethods products, follow the instructions in the webMethods 7.x product documentation.

3 Shut down all other non-webMethods applications that are running.


5 Back up the entire 7.x webMethods installation directory.

Back Up 7.x Database Components and Upgrade RDBMSs

Back up all 7.x webMethods database components. For instructions, see your RDBMS vendor documentation.




Important! You do not have to shut down webMethods products; the installer allows you to reassign webMethods product ports even if the products are running.

Note: If you do not shut down all non-webMethods applications, the Software AG Installer will not be able to replace key files that are locked by the operating system.

Important! For Optimize, you must back up the 7.x webMethods installation direc-tory and the Optimize database components at the same time. All must be in sync, or you will experience problems.

Important! If you are upgrading webMethods Broker, Integration Server, or Infrastruc-ture Data Collector, you must obtain the license file or license key for that release from [email protected].





For the installation directory, specify a new webMethods directory except in the case below.

If you are going to migrate business processes, you must continue using your webMethods Broker 7.x storage, so you must install webMethods Broker 8.0 on the machine that hosts webMethods Broker 7.x.

On the Software AG Installer’s product selection tree, select the 8.0 products to install; be sure to select all necessary components of each product (see Software AG Installation Guide 8.0, Typical Development Installations for guidance).





Note: Do not choose to install CentraSite 8.0 SP3. If you need to upgrade from Cen-traSite 7.x to CentraSite 8.0 SP3, contact Software AG Global Consulting Services.

Product Action

Trading Networks

Point the database connection at the 7.x Trading Networks database component.

Integration Server

Regardless of your 7.x configuration, select the embedded database. Later instructions will explain how to migrate your 7.x data from your embedded database and external RDBMS.

webMethods Broker

If you do not want to continue using your 7.x storage, create a Broker Server configuration. The installer requires your 8.0 webMethods Broker license file to create a Broker Server configuration.

If you want to continue using your 7.x storage, do not create a Broker Server configuration.

Important! You must continue using your 7.x storage if you are going to migrate business processes.


Point the database connection at the RDBMS in which you will create the new database component for My webMethods Server 8.0 data.

Note: You will create the necessary database component after installation.



After product installation is complete, create the 8.0 MywebMethodsServer database component. For instructions, see Software AG Installation Guide 8.0.

If you installed new 8.0 products, also create any necessary database components for those products. For detailed information and instructions, see Software AG Installation Guide 8.0.



Important! Do not create any other database components that you already have. You will migrate the 7.x database components to 8.0 later in this procedure.

Important! On UNIX systems, you must enclose the database URL in double quotes.














Migrate webMethods Broker and JMS Data

Backward Compatibility

Set Up the 8.0 Broker Server

Follow the appropriate instructions below, based on whether you chose to continue using your webMethods Broker 7.x storage.

To Not Use 7.x Storage

If you chose not to continue using your webMethods Broker 7.x storage, you created a 8.0 Broker Server configuration when you installed webMethods Broker 8.0. You must now migrate the 7.x metadata to the 8.0 Broker Server storage.

If you do not have gateways and territories, perform the steps in “Migrate if You Do Not Have Gateways and Territories” on page 90, with these exceptions: you will not be prompted about SSL in step 3d, and do not perform the SSL instructions in step 4.

If you have gateways and territories, perform the steps in “Migrate if You Have Gateways and Territories” on page 91, with these exceptions: you will not be prompted about SSL in step 4d, and do not perform the SSL instructions in step 7.

In either set of instructions, substitute “7.x” for “6.5.2.”

These Broker Servers... Are compatible with these Broker clients...

8.0 Broker Servers 7.x command-line utilities

7.x Broker Client C, C#, Java, and JMS APIs

7.x JMS clients

7.x Broker Servers 8.0 command-line utilities

8.0 Broker Client C and Java APIs

8.0 Broker and JMS user interface on My webMethods Server



To Use 7.x Storage

If you chose to continue using your webMethods Broker 7.x storage (for example, because you want to migrate business processes), you did not create a 8.0 Broker Server configuration during installation. You must now create a 8.0 Broker Server and configure it to use the 7.x storage. You must also remove the 7.x Broker Server from the 7.x Broker Monitor startup configuration and add it to the 8.0 Broker Monitor startup configuration.

1 Stop the 7.x Broker Server, then back up the 7.x Broker Server’s data directory.

2 Back up the 7.x awbrokermon.cfg file. The file is stored in the webMethods Broker_directory\bin directory (for example, C:\webMethods7\Broker\bin or /opt/webMethods7/Broker/bin).

3 Remove the 7.x Broker Server from the 7.x Broker Monitor startup configuration by going to the webMethods Broker_7.x_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.

When asked whether you want to remove the Broker Server from the Broker Server Monitors server configuration, enter Y.

4 Create the 8.0 Broker Server and configure it to use the 7.x storage by going to the webMethods Broker_8.0_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_7.x_data_directory

System Example

Windows server_config remove c:\webmethods7\Broker\data\awbrokers\default

UNIX server_config remove /var/opt/webmethods7/awbrokers/default

server_config add full_path_to_7.x_data_dir -k 8.0_license_file -p 7.x_port

System Example

Windows server_config add c:\webmethods7\Broker\data\awbrokers\default-k 8.0_license_file -p 6871

UNIX server_config add /var/opt/webmethods7/awbrokers/default-k 8.0_license_file -p 6871



5 Make sure the 7.x storage is running under the 8.0 Broker Server:


If you have a cluster of 7.x Integration Servers, see “Migrate Clustered Integration Servers” on page 71 before using the instructions below.

Before You Begin

1 Allow all guaranteed delivery jobs to finish running. To do so, connect Integration Server to webMethods Broker; in Integration Server Administrator, go to the Settings > Resources > Store Settings page and wait for Current Documents in Outbound Store in the Outbound Document Store area to reach 0.

2 If you are going to upgrade business processes, allow them to finish running or use Monitor to stop them. Determine whether you need to migrate run-time data (see “Migrate Business Processes” on page 75). If you need to migrate run-time data, do the following:

a Suspend document retrieval for all triggers, and then wait for Integration Server 7.x to process all documents already retrieved from the Broker. For instructions, see webMethods Integration Server Administrator’s Guide 7.1.1.

b The run-time packages you need to migrate are stored in the Integration Server_7.x_directory\packages directory under project names or custom names you specified in Designer. If any of these packages start with the letters Wm, go to

System Steps

Windows You can do either of the following:

Open the Windows Services window. Make sure the status of the webMethods Broker Server 8.0 (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 8.0.

Run this command: C:\SoftwareAG\Broker\bin\server_config.exe list

UNIX You can run either of these commands:

ps -ef | grep aw

/opt/softwareag/Broker/bin ./server_config list

Make sure the awbroker process is running and that it is running from the 8.0 awbroker file. For example:

brokermonbin 32547 32537 0 Jun27 ? 00:00:03 /opt/softwareag/Broker/bin/awbroker -d /var/opt/webmethods7/awbrokers/default



the Integration Server_8.0_directory\bin\migrate directory, open the packages.cnf file, and add a <value name></value> tag that identifies each package.

3 Shut down Integration Server 7.x.

4 Apply IS_8-0-1_Migrate_Fix1 to Integration Server 8.0 using instructions in the fix readme. Fixes are available from the Software AG Knowledge Center.


Migration Utility Options

This section explains how to use the Integration Server Migration Utility to migrate your Integration Server 7.x data. You have several options, as described below.

You can run the default migration, which automatically migrates all port, remote server alias, and Integration Server 7.x certificate settings; Web service endpoint aliases; proxy settings; and the embedded database, if you used it with Integration Server 7.x. Go to the Integration Server_8.0_directory\bin\migrate directory and run this command:

You can run a custom migration, in which you choose which data to migrate. The utility gathers your choices through a series of prompts, then migrates the specified data. To run a custom migration, follow the steps below, in this section.

If you are performing migrations for multiple, identical, clustered Integration Servers running on different machines, you can run a custom migration, export your choices to file, and import the choices when you run the utility on other machines.

To run a custom migration and export your choices to file, follow the steps below, in this section.

To run a migration with imported choices and a confirmation prompt before the migration actually begins, follow the steps below, in this section. To run a migration with imported choices silently (that is, with no confirmation prompt), see “Run the Migration Utility Silently with Imported Settings, with a Zip File as Data Source, or Both” on page 70.

You can create a Zip file of the Integration Server 7.x installation directory and use the Zip file as the source of Integration Server 7.x data. One use of this option is when your Integration Server 7.x and Integration Server 8.0 are on different machines. For instructions, see “Run the Migration Utility Silently with Imported Settings, with a Zip File as Data Source, or Both” on page 70.

During actual migrations, if migration of a piece of data fails (for example, certificate settings for a port), the utility asks whether to continue with the next piece of data or abort the migration. If you choose to abort, the utility exits. It does not revert the Integration Server 8.0 installation. You can address the issue and run the utility again.

migrate.{bat|sh} -importFile migrate{712|713}sbs.dat




The migration utility writes details of the migration to the migrationLog.txt file in the 8.0_installation_directory\install\logs directory. By default, the utility writes INFO, ERROR, and FATAL messages to the log. If you want to increase the logging level to DEBUG, go to the Integration Server_8.0_directory\bin\migrate directory, open the file log4j.properties file in a text editor, set the log4j.logger.Migration property to DEBUG, MigrationFile, and save and close the file.

Run the Utility to Perform a Custom Migration



3 The utility asks you to identify the Integration Server 7.x installation. Enter the full path to the Integration Server 7.x installation directory (for example, C:\webMethods7\IntegrationServer or /opt/webMethods7/IntegrationServer).

4 The utility asks whether to migrate packages. You can migrate user-created packages and, if installed, certain eStandards Module packages (WmRNPips, WmChemPayloads, and WmPapinetPayloads). You can migrate all the packages (enter A), none of the packages (enter N), or selected packages only (enter S). If you enter S, the utility lists each package and asks whether to migrate it.

If you are going to migrate run-time data for business processes, migrate your business process run-time packages. If you enter S (as opposed to A), the package names are the process model names or custom names you specified in webMethods Modeler, or names prefixed by Wm that you added to the packages.cnf file in step 2b.

5 The utility asks whether to migrate configuration files. You can migrate all configuration files (enter A) or selected configuration files only (enter S). If you enter S, the utility lists each configuration file and asks whether to migrate it. There are about 50 configuration files. If you choose to migrate selected configuration files only, you must enter Y to these prompts:

All prompts that list config/jdbc files.

If you are upgrading Optimize, prompt that lists the WmOptimize.properties file.

If you are upgrading Monitor, prompt that lists the monitor.cnf file.

6 The utility asks whether to migrate port certificate settings to the keystores used in 8.0 SP1. You can migrate all of the settings (enter A), none of the settings (enter N), or selected settings only (enter S). If you enter S, the utility lists each port and asks whether to migrate its certificate settings.

For each SSL port you migrate, the utility will convert certificate settings into the keystores used in 8.0 SP1. If conversion fails, the utility will revert all migration changes it made to the port and disable the port in Integration Server 8.0 SP1.




For remote server alias you migrate, the utility will convert certificate settings to the 8.0 SP1 format. If the conversion fails, the utility will revert all migration changes it made to the remote server alias in Integration Server 8.0 SP1.

8 The utility asks whether to migrate Web service endpoint aliases. You can migrate all of the aliases (enter A), none of the aliases (enter N), or selected aliases only (enter S). If you enter S, the utility lists each Web service endpoint alias and asks whether to migrate it.

For each alias you migrate that is in use by a WSD, the utility detects the type and transport of the WSD and copies that information to the 8.0 SP1 files. If an alias is not in use by a WSD, the utility copies the type and transport information in such a way that the alias is available to all WSDs, regardless of type or transport.

The utility will convert type and transport information for Web service endpoint aliases to the 8.0 SP1 format. If the conversion fails, the utility will revert all migration changes it made for the alias in Integration Server 8.0 SP1.

9 The utility asks whether to migrate Integration Server certificate settings. If you enter Y, the utility will convert the certificate settings into the keystores used in 8.0 SP1.

10 The utility asks whether to migrate proxy settings. If you enter Y, the utility will convert your proxy settings to the 8.0 SP1 format.

11 If Integration Server 7.x used the embedded database, the utility asks whether to migrate it. If you enter Y, the utility will copy the database tables from Integration Server 7.x to Integration Server 8.0 SP1 and convert the tables to the 8.0 SP1 format.



Note: If you do not migrate certificate settings for a port, and a default Integration Server keystore exists in the 8.0 SP1 installation, the port will default to that key-store.

Note: If you do not migrate the embedded database now, Integration Server 8.0 SP1 will create the embedded database automatically on startup but not migrate any data to it.



Deletes 7.x configuration files that are no longer used by Integration Server 8.0 SP1.

Deletes 7.x properties that are no longer used by Integration Server 8.0 SP1 from the 8.0 SP1 configuration files, and merges the Integration Server port.cnf and listeners.cnf file.

If Integration Server 7.x was part of a cluster, upgrades your clustering configuration to the 8.0 SP1 format.


In Integration Server 8.0, definitions of the environment variables have been moved from the server.{bat|sh} file to the new setenv.{bat|sh} file. If you made any changes to your Integration Server 7.x server.{bat|sh} file, manually reproduce those changes in your 8.0 files. Make sure you reproduce changes you made to your 7.x environment variables in the setenv.{bat|sh} file.

The 7.x files are in the backup you took before installing 8.0. The 8.0 files are located in the Integration Server_8.0_directory\bin directory.


1 Shut down all Integration Servers that connect to the 7.x IS Internal and IS Core Audit Log database components.



3 Start Integration Server 8.0 and connect the IS Internal, IS Core Audit Log, Cross Reference, and Document History functions to the corresponding database components if they are not already connected. If you want to use central user management, also connect the CentralUsers function to the My webMethods Server database component. For instructions, see Software AG Installation Guide 8.0. Then restart Integration Server 8.0.

Update WSDLs

Update your WSDLs. In Integration Server Administrator, go to the Settings > Extended page. If you have the extended setting watt.server.xml.ncname.encode.backward.compatibility and it is set to true, reset it to

dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i}-c {ISInternal|ISCoreAudit} -v latest -l db_server_URL -u existing_db_user -p password



false. Then regenerate the clients for all Provider Web services that have an operation with field names starting with "xml" in the input signature, output signature, header, or faults.


If you want Integration Server 8.0 to use the My webMethods Server central user management feature, go to the Settings > Resources page in Integration Server Administrator and point the MWS SAML Resolver URL field at the My webMethods Server 8.0 host and port.

If you want to monitor business processes in 8.0, add the mywebMethodsUsers role and mywebmethodsAdministrator’s role to the Monitor Administrator ACL. For instructions, see Administering My webMethods Server 8.0.

Run the Migration Utility Silently with Imported Settings, with a Zip File as Data Source, or Both

If you want to run the migration utility silently using settings exported from an earlier session, using a Zip file as the source of Integration Server 7.x data, or some combination of these, follow the instructions below.

1 Go to the Integration Server_8.0_directory\bin\migrate directory on the machine on which you ran the earlier migration session.

2 If you want to use exported settings, copy the migrate.dat file from that directory to any directory on the machine on which you want to run the migration session.

3 If you want to use a Zip file as the source of Integration Server 7.x data, create a Zip file of the entire contents of the Integration Server 7.x installation directory and then copy the Zip file to the machine on which you want to run the migration session.

4 Open a command window, go to the Integration Server_8.0_directory\bin\migrate directory, and run this command:

You can specify the options below on the command.

{migrate.bat|./migrate.sh}[options]

Option Enter

-destDir Full path to Integration Server 8.0 (for example, C:\Software AG\IntegrationServer or /opt/webMethods7/Integra-tionServer).

-silent true or false.

-importFile If you are using exported settings, full path to the migrate.dat file.



Migrate Clustered Integration Servers

If you have a cluster of 7.x Integration Servers, Software AG recommends the procedure below. Suppose you have a cluster of three 7.x Integration Servers named IS1, IS2, and IS3 and you are using an external load balancer to distribute client requests. You would do the following:

1 Stop routing client requests to the 7.x IS1 and shut it down. For instructions, see webMethods Integration Server Administrator’s Guide 7.1.1. Migrate the 7.x IS1 data using the instructions in “Run the Integration Server Migration Utility” on page 66. Customize the 8.0 IS1 startup files using the instructions in “Customize Startup Files” on page 69. Repeat this step for the 7.x IS2 and then for the 7.x IS3.

2 Migrate the 7.x Integration Server database components using the instructions in “Migrate the Integration Server Database Components” on page 69.

3 Start the upgraded 8.0 IS3. For instructions, see Administering webMethods Integration Server 8.0. Make sure it is processing client requests. Repeat this step for the upgraded 8.0 IS2 and then for the upgraded 8.0 IS1.

4 If necessary, update WSDLs using the instructions in “Update WSDLs” on page 69 and set up Central User Management using the instructions in “Use Central User Management” on page 70.


1 Migrate the Trading Networks properties file using the instructions in “Migrate Trading Networks Data” on page 105.

2 Migrate the Trading Networks database components, as follows:

a Shut down all Integration Servers that connect to the 7.x TradingNetworks database component.

b If TNS_7-1-2_DB_Fix7 was applied to Trading Networks 7.x, go to the 8.0_installation_directory\common\db\scripts\{oracle|mssql|db2|db2as400}\tradingnetworks\migrate\30_to_31 directory and open the SQL file ora_tns_m_30_to_31.sql. Comment out the sections of the file shown below and then save the file.

-srcDir If you are not using a Zip file as the 7.x data source, full path to Inte-gration Server 7.x (for example, C:\webMethods7\Integration-Server or /opt/webmethods7/IntegrationServer).

-srcFile If you are using a Zip file as the Integration Server 7.x data source, full path to the Zip file.

Option Enter



c On the machine on which you installed the Database Component Configurator, go to the 8.0_installation_directory\common\db\bin directory, open a command window, and migrate each database component by running the command below.


3 Start Integration Server 8.0.

RDBMS Sections to Comment Out

Oracle CREATE INDEX idx_BizDoc_Nativeid ON BizDoc (

NativeID)TABLESPACE WEBMINDX ;

CREATE INDEX idx_BizDoc_Groupid ON BizDoc (

GroupID)TABLESPACE WEBMINDX ;

SQL Server CREATE INDEX idx_BizDoc_Nativeid ON BizDoc (

NativeID)


GroupID)

DB2 CREATE INDEX idx_BizDoc_Nativeid ON BizDoc (

NativeID);


GroupID);





If you want to migrate runtime assets such as folders, Wiki objects, shells, skins, business calendars, roles, users, or custom applications from My webMethods Server 7.x, you must create a file that identifies the assets, export the assets from My webMethods Server 7.x, and then import the assets into My webMethods Server 8.0.

If you want to migrate design-time assets such as tasks, follow the instructions in “Migrate Tasks” on page 30.

Apply Fixes

Apply the appropriate fixes below using the instructions in the fix readmes. Fixes are available from the Software AG Knowledge Center.

Identify Assets to Export

Create a descriptor file with a name that you choose and the extension .txt. Open the file and create one entry for each asset or type of asset to export. Each entry must be on a separate line, and can be listed in any order. Entries cannot start with a forward slash (/). For information on the types of assets you can export and instructions on how to format each entry, do one of the following:

Go to the help directory in the file structure that was extracted when you applied MWS_7.1.2_Fix10. The file name is Syntax Help.xls.

Log on to My webMethods Server 8.0 as sysadmin, go to the Administration > Migration > Content Import/Export page, click Next, and then click Syntax Help.

Assets often have dependencies on other assets; for example, rule assets depend on pages to which they apply, and page assets might depend on users for access permissions. If you do not export assets on which other exported assets depend, you might experience problems after you import the assets. For example, if you export pages that depend on users for access permissions, but you do not export the users, the imported pages will no

Note: If you have a cluster of 7.x My webMethods Servers, the clustering configuration was not migrated to your 8.0 installation. If you want to cluster 8.0 My webMethods Servers, you will have to configure the cluster. For instructions, see Administering My webMethods Server 8.0.

If you are upgrading from... Apply these fixes . . .

My webMethods Server 7.1.2 MWS_7.1.2_Fix10 and MWS_7.1.2_CL_Fix11 to My webMethods Server 7.1.2.

My webMethods Server 7.1.3 MWS_7.1.3_Fix1 and MWS_7.1.3_CL_Fix1 to My webMethods Server 7.1.3.




longer have access permissions associated with them. If you export roles but you do not export the users for those roles, the imported roles will have no users associated with them.

Export Assets

1 Do one of the following:

Go to the My webMethods Server_7.x_directory\bin directory and enter the command below. For target_ folder, specify the folder in which to create a folder structure of all exported assets. Specify server_instance for server instances other than the default. The root folder of the export folder structure will include a file named info.properties that lists all exported assets.

Log on to My webMethods Server as sysadmin and go to the Administration > Migration > Content Import/Export page. Under Migration Properties, select Package for Migration Source Type and Export for Migration Mode, and then click Next. Under Export Properties for Side By Side Upgrade, specify the full path to target_ folder. In the Export Descriptor field, specify the full path to the asset descriptor file. Click Next to begin the export. The export process might take several minutes

2 Check the log file export-mm-dd-yyyy hh mm ss.log in the My webMethods Server_7.x_directory\server\server_instance\logs directory. If errors occurred, contact Software AG Customer Care.

3 Move the contents of the target folder to the machine that hosts My webMethods Server 8.0.

Import Assets

1 Apply MWS_8.0_SP1_Fix2 and MWS_8.0_SP1_CL_Fix2 to My webMethods Server 8.0 using the instructions in the fix readme. Fixes are available from the Software AG Knowledge Center.

2 Start My webMethods Server 8.0 by running this command:


Go to the My webMethods Server_8.0_directory\bin directory and enter the command below. Specify server_instance for server instances other than the default.

mws.{bat|sh} -s server_instance export full_path_to_descriptor_file target_folder


mws.{bat|sh} -s server_instance import full_path_to_info.properties file




Log on to My webMethods Server as sysadmin and go to the Administration > Migration > Content Import/Export page. Under Migration Properties, select Package for Migration Source Type and Import for Migration Mode, and then click Next. Under Import Properties for Side By Side Upgrade, specify the full path to the info.properties file and then click Next.

The import process might take several minutes.

4 Check the log file importyyyy-mm-dd_hh-mm.log in the My webMethods Server_8.0_directory\server\server_instance\logs\yyyy-mm-dd_hh-mm directory. If errors occurred, contact Software AG Customer Care.

5 If you imported skin, shell, login page, rendering, or start page rules, make sure rule evaluation is in the correct order. Go to the Administration > User Interface page, select each rule, and verify the rules evaluation order.

Migrate Blaze Rules

Migrate the projects that contain your Blaze rules from Blaze 6.5 to Blaze 6.8. For instructions, see Blaze Advisor Migration 6.8.

Open Blaze Advisor 6.8, open each project that contains 7.x Blaze rules, and deploy the rules to Integration Server 8.0. For instructions, see Using Blaze Rules with BPM and CAF 8.0.


You migrate 7.x business processes by migrating different types of data, depending on your goals. To determine which types of data to migrate, see “Migrate Business Processes” on page 28. In the instructions, substitute “7.x” for “6.5.1 SP1.”


Follow the instructions in “Migrate Design-Time Data” on page 28.


1 You migrated webMethods Broker to 8.0 using the instructions in“Migrate webMethods Broker and JMS Data” on page 63 and “To Use 7.x Storage” on page 64. Make sure the 7.x Broker used by your 7.x Process Engines has the same name in 8.0 that it had in 7.x.

2 If you migrated process run-time packages using the instructions in “Run the Integration Server Migration Utility” on page 66, make sure the packages exist in the Integration Server_8.0_directory\packages directory. The package names are the project names or custom names you specified in Designer.



3 Prevent new instances of 7.x process models from starting by shutting down all 7.x Integration Servers that host Process Engines.

4 Migrate the ProcessEngine and ProcessAudit database components, as follows:

a Shut down all Integration Servers that connect to the 7.x ProcessEngine or ProcessAudit database component.

b 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 each database component by running the command below.


c If you are using DB2 RDBMS, issue a DB2 REORG command on the WMPROCESS, PRTPROCESS, PRTINSTANCEITER, and WMPRTXREF tables from the DB2 command line. For example:

5 Start Integration Server 8.0 and connect the ProcessEngine and ProcessAudit functions to the corresponding database components if they are not already connected. For instructions, see Software AG Installation Guide 8.0.

6 Enable document retrieval for all triggers on Integration Server 8.0. For instructions, see Administering webMethods Integration Server 8.0.

Migrate Tasks

Follow the instructions in “Migrate Tasks” on page 30.

Migrate Optimize Data


1 Shut down all Optimize components.


dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw}-c {ProcessEngine|ProcessAudit} -v latest -l db_server_URL-u existing_db_user -p password






Unless otherwise noted, see Configuring BAM 8.0 for detailed instructions on each step in the sections below.

Connect Process Engine to Analytic Engine

If you are using Optimize for Process, start the Integration Server 8.0 that hosts a Process Engine and open Integration Server Administrator. Go to the Packages > Management page

and click for the WmPRT package. In the Broker URL field, change localhost to the correct host, the port to the correct port, and Broker #1 to the correct Broker name, and then click Submit.

To Not Reuse the 7.x CCS Environment Definition

If you do not want to reuse your 7.x Central Configuration System (CCS) Environment definition, start My webMethods Server and configure your Optimize 8.0 environment. Then skip to “Deploy the Optimize 8.0 Environment” on page 78.

To Reuse the 7.x CCS Environment Definition

If you want to reuse your 7.x CCS environment definition, follow the steps below.

1 Start My webMethods Server.

2 Import the 7.x CCS Environment you exported in “Before You Begin” on page 58. When prompted, confirm the migration. When asked “Do you wish to migrate the environment to the latest version?", click Yes. The CCS imports the 7.x environment and migrates it to 8.0 Optimize Logical Servers.

dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw}-c {Analysis|ProcessTracker|DataPurge|Reporting|Staging}-v latest -l db_server_URL -u existing_db_user -p password

Important! In the URLs, if you are using DB2, you must specify schema using all capital letters. In addition, you must specify the options CreateDefaultPackage=true,ReplacePackage=true, and DynamicSections=3000. These settings will affect all database components in the same schema or database.

Important! Do not change the broker:// or /analysis parts of the URL.



3 Set up a new database pool for the new 8.0 MywebMethodsServer database component as follows:

a Open My webMethods and go to the Applications > Administration > System-Wide > Environments > Database Pool Configuration page. Click Add Pool. Complete the fields and point at the 8.0 MywebMethodsServer database component.

b Go to the Applications > Administration > System-Wide > Environments > Define Environments page. Under Environment Name, click the environment you imported. Go to the Map DB Pools tab, map the common.directory - Analytic Engine Database Component to the new database pool, and then click Save.

4 Go to the Applications > Administration > System-Wide > Environments > Define Environments page. Under Environment Name, click the environment you imported.

5 If you are using Optimize for Infrastructure, follow the instructions in step 4 in “To Reuse the 7.x CCS Environment Definition” on page 33.

6 Click each tab except the Validate tab that shows ; the icon changes to . If you change any settings, and the tab has a Save button, click Save. When all tabs except the

Validate tab show , click the Validate tab.

Deploy the Optimize 8.0 Environment

1 Start the Optimize 8.0 components you installed. These components can include the Analytic and Prediction engines, Infrastructure Data Collector, and the Web Services Data Collector.

2 Deploy your Optimize 8.0 environment.

3 Go to the My webMethods > System Settings > Servers page. Select the server to use as the default, and specify any additional server information you noted in “Before You Begin” on page 58. Click Check Server Status and make sure the server is available (green icon), then click Save to save the configuration. For more detailed information, see the Configuring Optimize to use an Analytic Engine or Configuring Optimize to Use Multiple Analytic Engines section in Administering webMethods Optimize 8.0.

Rediscover Assets and Reestablish Monitoring

If you are using Optimize for Infrastructure, follow the instructions in “Rediscover Assets and Reestablish Monitoring” on page 34.




Follow the instructions below to migrate source and target webMethods server connection information (aliases), target groups, and deployment projects from Deployer 7.x to Deployer 8.0.

Before You Begin

1 Make sure you are a member of the Administrators ACL, or of the Internal, Developer ACLs, and DeployerAdmin ACLs, for both the Integration Server that hosts Deployer 7.x and the Integration Server that hosts Deployer 8.0. For instructions, see Administering webMethods Integration Server 8.0.

2 Start Deployer 8.0 and go to the Tools > Migrate Data page.

3 In the Host and Port fields, identify the 7.x Deployer to migrate from. In the User and Password fields, provide the user name and password to use to log onto the 7.x Deployer.

4 Deployer 8.0 will list the aliases, target groups, or projects to migrate in the right-hand pane. In the Page Size list, click the number of aliases or projects to list at a time.

Migrate Connection Information (Server Aliases)

1 Click Migrate Server Aliases.

2 In the Select Server list, click the type of server whose aliases to migrate.

3 In the Select column, select the check boxes next to the server aliases to migrate. If you need to change any connection information, you can do so now.

4 Click Migrate Server Aliases. Deployer migrates the selected aliases, then disables those rows and displays Yes in the Migrate column for the aliases.

Important! You must upgrade all source webMethods servers to the latest 8.0 release as instructed in this chapter before you can migrate Deployer data.

Note: Deployer cannot migrate Integration Server HTTPS server aliases.



Migrate Target Groups

1 Make sure you migrated all aliases in each target group you want to migrate. If you do not want to migrate certain aliases in a target group, remove those aliases from the target group in Deployer 7.x.

2 Click Migrate Target Groups.

3 In the Select Server list, click the type of server whose target groups to migrate.

4 In the Simulate Migration column, click in the row for each target group you want to migrate. Deployer displays a message that indicates whether the aliases that are referenced by the target group have been migrated. You must either migrate the aliases or remove them from the target group in Deployer 7.x (see step 1).

5 In the Select column, select the check boxes next to target groups to migrate.

6 Click Migrate Target Groups. Deployer migrates the selected target groups, then disables those rows and displays Yes in the Migrate column for the groups.

Migrate Deployment Projects

1 Start the 8.0 source webMethods servers.

2 Click Migrate Projects.

3 In the right-hand pane, in the Simulate Migration column, click in the row for each project you want to migrate. Deployer displays a message that indicates whether the source servers that are referenced by the project are running. If the message indicates that any of the referenced source servers are not running, you must start the source servers before you can migrate the project.

4 In the Select column, select the check boxes next to the projects to migrate.

5 Click Migrate Projects. Deployer displays a new window with a dynamic migration report.

You can display the migration report for each project in the Report column in the original window. You can display the latest migration report by clicking View Latest Migration Report.

Important! If you do not remove unmigrated aliases from target groups in Deployer 7.x, the migrated target groups in Deployer 8.0 will include invalid aliases, and deployment of projects that use the target groups will fail.

Important! Deployer can only migrate a project if all source webMethods servers referenced by the project have been upgraded to 8.0 and are running.


5 Performing Side-by-Side Migration from 6.5 to Latest 8.0 Releases

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Requirements, Recommendations, and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84

Before You Begin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Back Up the 6.5 webMethods Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

Back Up 6.5 Databases and Upgrade RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86



Migrate webMethods Broker Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Migrate JMS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97



Migrate Access or Portal Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108






Overview

This upgrade procedure explains how to upgrade the latest webMethods 6.5 product releases to the latest webMethods 8.0 product releases. For the products listed below, you must perform additional tasks described in this chapter to complete the upgrade or to migrate data.

webMethods Broker and JMS 6.5.2

Integration Server 6.5 SP3

Trading Networks 6.5 SP1

webMethods Access 6.5.2 or webMethods Portal 6.5.2

webMethods Modeler 6.5.1 SP1 and Process Run Time 6.5.1 SP1 (business processes)

Deployer 6.5 SP1


The product releases from which you can upgrade are referred to as 6.5. However, you can only upgrade from the releases listed above. If you want to upgrade from an earlier release, you must first upgrade to the release listed above.

The latest webMethods 8.0 product releases to which you can upgrade are referred to as 8.0.

Requirements, Recommendations, and Notes

Because many products share files, you must upgrade all products that are in the same installation directory.



If you want to retain your 6.5 environment after upgrading, shut down 6.5 Integration Servers, Trading Networks Servers, and Optimize components that connect to webMethods database components, copy the databases using vendor

Note: You cannot migrate Optimize or Manager Server from 6.5.1 SP2 to 8.0. Instead, you must upgrade to 7.1.2 using instructions in webMethods Upgrade Guide 7.1, and then upgrade from 7.1.2 to 8.0 using instructions in this guide.

You cannot migrate Workflow processes from 6.5 to 8.0. Instead, you must re-implement your Workflow 6.5 projects using Designer 8.0 and Task Engine 8.0.



instructions, migrate the copied database components, and use the migrated database components with your 8.0 products. This is not necessary for My webMethods Server 8.0, for which you will create a new database component.

Before You Begin

If you are going to upgrade Deployer, do the following:

a Apply DEP_6.5.1_Fix16 to Deployer using the instructions in the fix readme. Fixes are available from the Software AG Knowledge Center.

b Migration of Deployer data after installation requires both Deployer 6.5 and Deployer 8.0 to be running. If you are going to install Deployer 8.0 on the same machine as Deployer 6.5, and you want Deployer 8.0 to use the same ports that Deployer 6.5 used, change the ports used by the 6.5 host Integration Server. For instructions, see webMethods Integration Server Administrator’s Guide 6.5.

If you are going to upgrade Monitor, apply MWS_Monitor_6-5-2_SP3_Fix4 to My webMethods Server using the instructions in the fix readme. Fixes are available from the Software AG Knowledge Center.

Back Up the 6.5 webMethods Installation

1 If you want to shut down webMethods products, follow the instructions in the webMethods 6.5 product documentation.

2 Shut down all other non-webMethods applications that are running on the machine.


4 Back up the entire 6.5 webMethods installation directory.


Important! You do not have to shut down webMethods products; the installer allows you to reassign 6.5 webMethods product ports even if the products are running.

Do not shut down the Integration Server Repository Server; it must continue running until all data has been migrated.

Important! If you do not shut down all non-webMethods applications, the Software AG Installer will not be able to replace key files that are locked by the operating system.





Back Up 6.5 Databases and Upgrade RDBMSs

Back up all 6.5 webMethods databases. For instructions, see your RDBMS vendor documentation.



If you are upgrading webMethods Broker, Integration Server, or Infrastructure Data Collector, you must obtain the license file or license key for that release from [email protected].


For the installation directory, specify a new webMethods directory except in the case below.

If you are going to migrate business processes, you must continue using your webMethods Broker 6.5 storage, so you must install webMethods Broker 8.0 on the machine that hosts webMethods Broker 6.5.

On the Software AG Installer’s product selection tree, select the 8.0 products to install; be sure to select all necessary components of each product (see Software AG Installation Guide 8.0, Typical Development Installations for guidance).









Product Action

Trading Networks

Point the database connection at the 6.5 Trading Networks database component.

Integration Server

In the 6.5 release, internal configuration data was stored in the Integration Server Repository. In 8.0, you can choose to store this internal configuration data, called IS Internal data, in an embedded database or an external RDBM. For complete information, see the Data Storage chapter of Software AG Installation Guide 8.0.

When you run the Integration Server migration utility after installation, it will migrate your internal configuration data from the Repository to the storage you choose here. It will also retain your storage settings for IS Core Audit Log data.

webMethods Broker

If you do not want to continue using your 6.5 storage, create a Broker Server configuration. The installer requires your 8.0 webMethods Broker license file to create a Broker Server configuration.

If you want to continue using your 6.5 storage, do not create a Broker Server configuration.

Important! You must continue using your 6.5 storage if you are going to migrate business processes.


Point the database connection at the RDBMS in which you will create the new database component for My webMethods Server 8.0 data.

Note: You will create the necessary database component after installation.

Important! After Integration Server 8.0 and Developer 8.0 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 by running server.bat in the Integration Server_6.5_directory\bin directory and developer.bat in the Developer_6.5_directory\bin directory.



After product installation is complete, create the 8.0 database components that the table below indicates you should create. For instructions, see Software AG Installation Guide 8.0.

If you installed new 8.0 products, also create any necessary database components for those products. For detailed information and instructions, see Software AG Installation Guide 8.0.



If you are migrating... Create the following...

Integration Server If you chose an external RDBMS during installation and want to store cross-referencing 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

Important! For Oracle, use the -t (tablespace) parameter only if the DB_CREATE_FILE_DEST parameter is not set for your Oracle instance.


Create the My webMethods Server database component.

Important! Do not create any other database components that you already have. You will migrate the 6.5 database components to 8.0 later in this procedure.

Important! On UNIX systems, you must enclose the database URL in double quotes.



Migrate webMethods Broker Data


Set Up the 8.0 Broker Server

If you chose not to continue using your webMethods Broker 6.5 storage, you created a 8.0 Broker Server configuration when you installed webMethods Broker 8.0. You must now migrate the 6.5 metadata to the 8.0 Broker Server storage. If you do not have gateways












These Broker Servers... Are compatible with these Broker clients...

8.0 Broker Servers 6.5 command-line utilities

6.5 Broker Client C, COM/ActiveX, Java, and JMS APIs

6.5 Broker Servers 8.0 command-line utilities

8.0 Broker Client C and Java APIs

8.0 Broker and JMS user interface on My webMethods Server



and territories, see “Migrate if You Do Not Have Gateways and Territories” on page 90. If you have gateways and territories, see “Migrate if You Have Gateways and Territories” on page 91.

If you chose to continue using your webMethods Broker 6.5 storage (for example, because you want to migrate business processes), you did not create a 8.0 Broker Server configuration during installation. You must now create a 8.0 Broker Server and configure it to use the 6.5 storage. For instructions, see “Configure the 8.0 Broker Server to Use 6.5 Storage” on page 92.

Migrate if You Do Not Have Gateways and Territories

This section explains how to migrate the Broker Server data and configuration from the 6.5 Broker Server to the 8.0 Broker Server if you do not have gateways and territories.

1 Start My webMethods Server 8.0 and open My webMethods.

2 Start the 6.5 Broker Server. Export the data and the Broker Server configuration from the 6.5 Broker Server as follows:

a In My webMethods, go to the Administration > Messaging > Broker Servers > Servers

page and click in the DETAIL column for the 6.5 Broker Server.

b Click the Export tab, select the check box next to the 6.5 Broker Server, and then click Export.

c Clear the Include System Defined Data check box and click Export. The data is exported in the form of a zip file named ServerExported.zip. Save the zip file in any directory.

d If the zip file is larger than 20 MB, increase the upload file size limit in My webMethods, as follows:

1 Log on to My webMethods Server as system administrator.

2 Go to the Folders > Administrative Folders > Administration Dashboard > Content > Content Service page.

3 In the Set Max File Size field, type the size of the zip file or greater.

4 Click Apply.

3 Start the 8.0 Broker Server. Import the Broker Server data and configuration into the 8.0 Broker Server as follows:

a In My webMethods, go to the Administration > Messaging > Broker Servers > Servers

page and click in the DETAIL column for the 8.0 Broker Server.

b Click the Import tab and click Upload File. Select the ServerExported.zip file and click Upload.

c 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.



d Select the check box next to the 8.0 Broker Server and click Import. If prompted, click Skip SSL Configuration to not import the 6.5 Broker Server SSL configuration; the 6.5 SSL configuration is incompatible with the 8.0 SSL configuration.

4 Your 6.5 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 8.0 Broker Server. For instructions, see Administering webMethods Broker 8.0.

Migrate if You Have Gateways and Territories

This section explains how to migrate the Broker Server data and configuration from the 6.5 Broker Server to the 8.0 Broker Server if you have gateways and territories.

1 Start My webMethods Server 8.0 and open My webMethods.

2 Start the 6.5 Broker Server. Export the data and the Broker Server configuration from the 6.5 Broker Server as follows:

a In My webMethods, go to the Administration > Messaging > Broker Territories > Territories page and click a territory whose configuration you want to export.

b Click the Export tab, select the check box next to the 6.5 Broker Server territory, and then click Export.

c Clear the Include System Defined Data check box and click Export. The data is exported in the form of a zip file named TerritoryExported.zip. Save the zip file in any directory.

d Repeat these steps for each territory whose configuration you want to export.

e If the largest zip file is larger than 20 MB, increase the upload file size limit in My webMethods, as follows:

1 Log on to My webMethods Server as system administrator.

2 Go to the Folders > Administrative Folders > Administration Dashboard > Content > Content Service page.

3 In the Set Max File Size field, type the size of the largest zip file or greater.

4 Click Apply.

3 In My webMethods, go to the Administration > Messaging > Broker Servers > Servers page and stop all 6.5 Broker Servers. Refresh the page and make sure the Broker Servers no longer appear on the list.

4 Start the 8.0 Broker Server. Import the data and the Broker Server configuration into the 8.0 Broker Server as follows:

a In My webMethods, go to the Administration > Messaging > Broker Territories > Territories page.

b Click the Import tab and click Upload File. Select the TerritoryExported.zip file and click Upload.



c 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.

d Select the check box next to the 8.0 Broker Server and click Import. If prompted, click Skip SSL Configuration to not import the 6.5 Broker Server SSL configuration; the 6.5 SSL configuration is not compatible with the 8.0 SSL configuration.

e Repeat these steps for each territory whose configuration you exported.

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.

6 Complete the gateway migration as explained below. For detailed instructions, see Administering webMethods Broker 8.0.

If you installed webMethods Broker 8.0 on the same machine as webMethods Broker 6.5 and the 8.0 Broker Server is using the 6.5 port, the gateways are created, but you must manually set the document types to shared.

If you installed webMethods Broker 8.0 on a different machine than webMethods Broker 6.5 or the 8.0 Broker Server is not using the 6.5 port, you must manually create the gateways and set the document types to shared.

7 Your 6.5 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 8.0 Broker Server. For instructions, see Administering webMethods Broker 8.0.

Configure the 8.0 Broker Server to Use 6.5 Storage

Use this procedure if you want to continue using your 6.5 storage (for example, because you want to migrate business processes), and thus did not create a Broker Server configuration during installation.

The procedure explains how to create an 8.0 Broker Server and configure it to use the 6.5 storage. The procedure also removes the 6.5 Broker Server from the 6.5 Broker Monitor startup configuration and adds it to the 8.0 Broker Monitor startup configuration.

1 Stop the 6.5 Broker Server, then back up the 6.5 Broker Server’s data directory.

2 Set the environment variable ACTIVE_CONFIG to point to the awbrokermon.cfg file for the 6.5 Broker Monitor. The file’s location is as follows:

3 Back up the 6.5 awbrokermon.cfg file.

System awbrokermon.cfg File Location

Windows c:\WINDOWS\webmethods

UNIX /var/opt/webmethods6



4 Remove the 6.5 Broker Server from the 6.5 Broker Monitor startup configuration by going to the webMethods Broker_6.5_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.

When asked whether you want to remove the Broker Server from the Broker Server Monitors server configuration, enter Y.

5 Create the 8.0 Broker Server and configure it to use the 6.5 storage by going to the webMethods Broker_8.0_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.

6 Make sure the 6.5 storage is running under the 8.0 Broker Server:

server_config remove full_path_to_6.5_data_directory

System Example

Windows server_config remove c:\webmethods6\Broker\data\awbrokers\default

UNIX server_config remove /var/opt/webmethods6/awbrokers/default

server_config add full_path_to_6.5_data_dir -k 8.0_license_file -p 6.5_port

System Example

Windows server_config add c:\webmethods6\Broker\data\awbrokers\default-k 8.0_license_file -p 6849

UNIX server_config add /var/opt/webmethods6/awbrokers/default-k 8.0_license_file -p 6849



7 If you are using SSL, convert your keystores to the correct format. For instructions, see Administering webMethods Broker 8.0.

Migrate Java Clients

If you want to migrate Java clients that use SSL to 8.0, you must modify the way the SSL connections are created in your Java source code to reflect the Broker command-line utilities and Java API changes that are documented below.

Command-Line Utilities Changes

System Steps

Windows You can do either of the following:

Open the Windows Services window. Make sure the status of the webMethods Broker Server 8.0 (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 8.0.

Run this command: C:\SoftwareAG\Broker\bin\server_config.exe list

UNIX You can run either of these commands:

ps -ef | grep aw

/opt/softwareag/Broker/bin ./server_config list

Make sure the awbroker process is running and that it is running from the 8.0 awbroker file. For example:

brokermonbin 32547 32537 0 Jun27 ? 00:00:03 /opt/softwareag/Broker/bin/awbroker -d /var/opt/webmethods/awbroker65/default

Command 8.0 Modification

server_config Added optional monitor port parameter, added a sub command ('stopall')

broker_stop Added optional monitor port parameter, changed ID options

broker_start Added optional monitor port parameter



Broker Java API Changes

Changed Methods in BrokerConnectionDescriptor Class

New Methods in BrokerConnectionDescriptor Class

getSSLKeystore()

getSSLKeystoreType()

getSSLTruststore()

getSSLTruststoreType()

broker_create

Changed ID options

broker_delete

broker_load

broker_save

broker_buildall

broker_ping

broker_status

server_conf_backup

server_conf_restore

6.5 Method 8.0 Method

setSSLCertificate(String certificate_file,String password,String distinguished_name)

setSSLCertificate(String keystore_file,String truststore_file,KeystoreType keystore_type,TruststoreType truststore_type,String password)

getSSLCertificate(String certificate_file,String password,String distinguished_name)

getSSLCertificate(String keystore_file,String truststore_file,KeystoreType keystore_type,TruststoreType truststore_type,String password)

getSSLCertificateDns(String certificate_file,String password)

getSSLCertificateDns(String keystore_file,String truststore_file,KeystoreType keystore_type,TruststoreType truststore_type,String password)

getSSLRootDns(String certificate_file,String password)

getSSLRootDns(String keystore_file,String truststore_file,KeystoreType keystore_type,TruststoreType truststore_type,String password)




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()

Migrate C Clients

If you want to migrate C clients that use SSL to 8.0, 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 8.0 Broker Server SSL configuration. For complete information on the 8.0 Broker Server SSL configuration, see Administering webMethods Broker 8.0.

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 Programmer’s Guide 8.0.

Removed Methods

These methods have been removed:

awGetSSLCertificateDns

awGetSSLRootDns



Migrate JMS Data


6.5 JMS clients can run on 8.0 Broker Servers.

The SSL keystore format changed in release 7.x. 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 Administering webMethods Broker 8.0.

Update JMSAdmin Scripts

Use the tables in this section to update the commands in your 6.5 JMSAdmin scripts to be correct for 8.0.


Create DurableSubscriber

Changed SSL parameters

Create Queue

Bind ConnectionFactory

Modify ConnectionFactory

Bind TopicConnectionFactory

Modify TopicConnectionFactory

Bind QueueConnectionFactory

Modify QueueConnectionFactory

Bind QueueAdded optional PriorityOrdering property

Modify Queue

Bind Topic Added optional PriorityOrdering property

Added optional LocalOnly and DeadLetterOnly properties

Modify Topic

Command New Property Removed Property

ConnectionFactory

SSLTruststore sslDNTopicConnectionFactory

QueueConnectionFactory

Topic LocalOnly

DeadLetterOnly



Convert JMS Client APIs

Use the tables in this section to convert the indicated JMS API methods from 6.5 to 8.0.

Changed Method in WmJMSAdminFactory Class

Change this 6.5 method:

create(java.lang.String Broker_host, java.lang.String Broker_name, java.lang.String client_ID, java.lang.String client_group, java.lang.String SSL_keystore, boolean SSL_encrypted, java.lang.String user, java.lang.String password)

To one of these 8.0 methods:

create(java.lang.String Broker_host, java.lang.String Broker_name, java.lang.String client_ID, java.lang.String client_group, java.lang.String SSL_keystore, java.lang.String SSL_truststore, boolean SSL_encrypted, java.lang.String user, java.lang.String password)

create(java.lang.String Broker_host, java.lang.String Broker_name, java.lang.String client_ID, java.lang.String client_group, com.webmethods.jms.util.SSLInfo SSL_info)

Deprecated WmFileMessage Class

The WmFileMessage class is deprecated in JMS 8.0. You should open, read, and write to and from files directly instead.

New Methods in WmJMSConfig Class

setSSLKeystoreType(java.lang.String SSL_keystore)

setSSLProvider(java.lang.String provider)

setSSLTruststore(java.lang.String SSL_truststore)

setSSLTruststoreType(java.lang.String SSL_truststore)

setSSLCipherSuites(java.lang.String cipher_suites)

New Fields in WmConnectionFactory Class

DEFAULT_BROKER_LIST_ORDER

DEFAULT_KEYSTORE_TYPE

DEFAULT_TRUSTSTORE_TYPE

PriorityOrdering

Queue PriorityOrdering

Command New Property Removed Property



New Methods in WmConnectionFactory Class

getSSLKeystoreType()

setSSLKeystoreType(java.lang.String SSL_keystore_type)

getSSLTruststore()

setSSLTruststore(java.lang.String SSL_truststore)

getSSLTruststoreType()

setSSLTruststoreType(java.lang.String SSL_truststore_type)

New Method in WmQueueConnectionFactory Class

createQueueConnection(java.lang.String user, java.lang.String password, java.lang.String access_label_hint)

New Method in WmTopicConnectionFactory Class

createTopicConnection(java.lang.String user, java.lang.String password, java.lang.String access_label_hint)

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 8.0.

New Method Description

createConnection(java.lang.String user, java.lang.String password, java.lang.String access_label_hint)

Create a connection to a Broker using the provided access label hint

setAutomaticControlLabel(boolean enable) Enable a Broker to set control labels automatically (for webMethods' content-based security)

getBrokerListOrder() Get the order to connect with Broker clusters

setBrokerListOrder(java.lang.String Broker_list_order)

Set the order to connect with Broker clusters

6.5 Name and Location 8.0 Name and Location

webMethods_directory\common\lib\wmjmsclient.jar

webMethods Broker_directory\lib\wm-jmsclient.jar

webMethods_directory\common\lib\wmbrokerclient.jar

webMethods Broker_directory\lib\wm-brokerclient.jar




If you have a cluster of 6.5 Integration Servers, see “Migrate Clustered Integration Servers” on page 104 before using the instructions below.

Before You Begin

1 Allow all guaranteed delivery jobs to finish running. To do so, connect Integration Server to webMethods Broker; in Integration Server Administrator, go to the Settings > Resources > Store Settings page and wait for Current Documents in Outbound Store in the Outbound Document Store area to reach 0.

2 If you are going to upgrade business processes, allow them to finish running or use Monitor to stop them. Determine whether you need to migrate run-time data (see “Migrate Business Processes” on page 109). If you need to migrate run-time data, do the following:

a Suspend document retrieval for all triggers, and then wait for Integration Server 6.5 to process all documents already retrieved from the Broker. For instructions, see webMethods Integration Server Administrator’s Guide 6.5.

b The run-time packages you need to migrate are stored in the Integration Server_6.5_directory\packages directory under the process model names or custom names you specified in webMethods Modeler. If any of these packages start with the letters Wm, go to the Integration Server_8.0_directory\bin\migrate directory, open the packages.cnf file, and add a <value name></value> tag that identifies each package.

3 Shut down Integration Server 6.5.

4 Apply IS_8-0-1_Migrate_Fix1 to Integration Server 8.0 using instructions in the fix readme. Fixes are available from the Software AG Knowledge Center.

5 Make sure the Integration Server Repository Server is running. It must continue running until all data has been migrated.


Migration Utility Options

For a list of options offered by the Integration Server Migration Utility, see “Migration Utility Options” on page 66. In the text, substitute “6.5” for “7.x.” If you want to use the default migration option, the name of the file is migrate65sbs.dat. The steps below explain how to use the custom migration option.




Run the Utility to Perform a Custom Migration



3 The utility asks you to identify the Integration Server 6.5 installation. Enter the full path to the Integration Server 6.5 installation directory (for example, C:\webMethods65\IntegrationServer or /opt/webMethods65/IntegrationServer).

4 The utility asks whether to migrate packages. You can migrate user-created packages and, if installed, certain eStandards Module packages (WmRNPips, WmChemPayloads, and WmPapinetPayloads). You can migrate all the packages (enter A), none of the packages (enter N), or selected packages only (enter S). If you enter S, the utility lists each package and asks whether to migrate it.

If you are going to migrate run-time data for business processes, migrate your business process run-time packages. If you enter S (as opposed to A), the package names are the process model names or custom names you specified in webMethods Modeler, or names prefixed by Wm that you added to the packages.cnf file in step 1b.

If you are going to migrate scheduled jobs, migrate the packages that contain the services these jobs invoke.

5 The utility asks whether to migrate configuration files. You can migrate all configuration files (enter A) or selected configuration files only (enter S). If you enter S, the utility lists each configuration file and asks whether to migrate it. You must migrate every config/jdbc file; enter Y to each prompt that lists such a file.

The utility deletes ports for the built-in Integration Server load balancer, which no longer exists in Integration Server 8.0, and clustering ports, which are no longer supported in Integration Server 8.0. You can reconfigure the Integration Server cluster with a third-party load balancer later. The utility also upgrades ports whose format has changed between the Integration Server 6.5 to 8.0 releases.

6 The utility asks whether to migrate port certificate settings to the keystores used in 8.0. You can migrate all of the settings (enter A), none of the settings (enter N), or selected settings only (enter S). If you enter S, the utility lists each port and asks whether to migrate its certificate settings.

For each SSL port you migrate, the utility will convert certificate settings into the keystores used in 8.0. If conversion fails, the utility will revert all migration changes it made to the port and disable the port in Integration Server 8.0.

Note: There are nearly 50 configuration files.

Note: If you do not migrate certificate settings for a port, and a default Integration Server keystore exists in the 8.0 installation, the port will default to that keystore.




For remote server alias you migrate, the utility will convert certificate settings to the 8.0 format. If the conversion fails, the utility will revert all migration changes it made to the remote server alias in Integration Server 8.0.

8 The utility asks whether to migrate Integration Server certificate settings. If you enter Y, the utility will convert the certificate settings into the keystores used in 8.0.

9 The utility asks whether to migrate proxy settings. If you enter Y, the utility will convert your proxy settings to the 8.0 format.

10 In separate prompts, the utility asks whether to migrate scheduled jobs, client certificates, pub.storage settings, trigger join settings, and xref (cross-reference) settings from the Repository to the storage (embedded database or external RDBMS) you specified in the installer.



Deletes 6.5 configuration files that are no longer used by Integration Server 8.0.

Deletes 6.5 properties that are no longer used by Integration Server 8.0 from the 8.0 configuration files, and merges the Integration Server port.cnf and listeners.cnf file.

The Integration Server 6.5 Repository Server was replaced in Integration Server 8.0 by a set of database tables collectively called IS Internal. If you chose the embedded database during installation, the utility migrates your Repository Server data to the embedded database, which contains IS Internal database tables. If you pointed to an external RDBMS during installation and then created the IS Internal database component, the utility migrates your Repository Server data to the IS Internal database component in the external RDBMS.


In Integration Server 8.0, definitions of the environment variables have been moved from the server.{bat|sh} file to the new setenv.{bat|sh} file. If you made any changes to your Integration Server 6.5 server.{bat|sh} file, manually reproduce those changes in your 8.0 files. Make sure you reproduce changes you made to your 6.5 environment variables in the setenv.{bat|sh} file.



The 6.5 files are in the backup you took before installing 8.0. The 8.0 files are located in the Integration Server_8.0_directory\bin directory.


1 Shut down all Integration Servers that connect to the 6.5 IS Core Audit Log and Cross Reference database components.

2 On the machine on which you installed the Database Component Configurator, go to the 8.0_installation_directory\common\db\bin directory and open a command window.

3 Migrate the IS Core Audit Log database component by running this command:

Check the log file dcc_yyyymmddhhmmss in the 8.0_installation_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care.

4 Migrate the Cross Reference database component by running this command:


5 Start Integration Server 8.0 and connect the IS Internal, IS Core Audit Log, Cross Reference, and Document History functions to the corresponding database components if they are not already connected. If you want to use central user management, also connect the CentralUsers function to the My webMethods Server database component. For instructions, see Software AG Installation Guide 8.0. Then restart Integration Server 8.0.

6 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.

Assign Trust Store

If Integration Server 8.0 is inside your firewall and will establish reverse connections to an Integration Server in your DMZ, and your clients will use certificate-based authentication when connecting to the Integration Server 8.0 Internal Registration port, assign a truststore that contains the clients’ CA certificates to that port. For instructions, see Administering webMethods Integration Server 8.0.

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

dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i}-c CrossReference -v latest -l db_server_URL -u existing_db_user -p password -fv 10




If you want Integration Server 8.0 to use the My webMethods Server central user management feature, go to the Settings > Resources page in Integration Server Administrator and point the MWS SAML Resolver URL field at the My webMethods Server 8.0 host and port.

If you want to monitor business processes in 8.0, add the mywebMethodsUsers role and mywebmethodsAdministrator’s role to the Monitor Administrator ACL. For instructions, see Administering My webMethods Server 8.0.

Migrate Clustered Integration Servers

If you have a cluster of 6.5 Integration Servers, Software AG recommends the procedure below. Suppose you have a cluster of three 6.5 Integration Servers named IS1, IS2, and IS3 and you are using a load balancer to distribute client requests. You would do the following:

1 Stop routing client requests to the 6.5 IS1 and shut it down. For instructions, see webMethods Integration Server Administrator’s Guide 6.5. Migrate the 6.5 IS1 data using the instructions in “Run the Integration Server Migration Utility” on page 100. Customize the 8.0 IS1 startup files using the instructions in “Customize Startup Files” on page 102. Repeat this step for the 6.5 IS2 and then for the 6.5 IS3.

2 Migrate the 6.5 Integration Server database components using the instructions in “Migrate the Integration Server Database Components” on page 103.

3 Start the upgraded 8.0 IS3, IS2, and IS1. For instructions, see Administering webMethods Integration Server 8.0.

4 Reconfigure the cluster. For instructions, see webMethods Integration Server Clustering Guide 8.0.

5 Start routing client requests to the cluster.

6 If necessary, assign a truststore using the instructions in “Assign Trust Store” on page 103.

Note: The built-in Integration Server load balancer no longer exists in release 8.0. If you were using the built-in load balancer, and want to continue using load balancing, switch to a third-party load balancer.




Migrate the Trading Networks Properties File

1 If you are migrating on an IBM i5 system, go to the Integration Server_8.0_directory\ packages\WmTN\bin directory, open the setcp.sh file in a text editor, and set the variables listed below as indicated:

2 Go to the Integration Server_8.0_directory\packages\WmTN\config\migrate directory, open a command window, and run this command:

For example:

The command creates a properties.cnf file in the Integration Server_8.0_directory\ packages\WmTN\config\migrate directory.

3 Move the properties.cnf file to the Integration Server_8.0_directory\packages\ WmTN\config directory.

Migrate the Trading Networks Database Components

1 Shut down all Integration Servers that connect to the 6.5 TradingNetworks database component.


Set this variable... To this directory...

SERVDIR Integration Server_8.0_directory

COMMONDIR 8.0_installation_directory/common

WEBMEXT 8.0_installation_directory/common/lib/ext

JDKDIR JVM_or_JDK_directory

MigratePropFile.{bat|sh} path_to_6.5_properties_file

MigratePropFile.sh /opt/webMethods/IntegrationServer/packages/WmTN/config/properties.cnf

dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw|db2i}-c {TradingNetworks|TradingNetworksArchive} -v latest -l db_server_URL-u existing_db_user -p password -fv 10




3 Start Integration Server 8.0 and connect the Trading Networks function to the migrated Trading Networks database component. For instructions, see Software AG Installation Guide 8.0. Then shut down Integration Server 8.0.


1 Go to the Integration Server_8.0_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.

2 Go to the Integration Server_8.0_directory\packages\WmTN\config\migrate directory, open a command window, and run this command:

3 Review the command window to make sure the migration was successful. If errors occurred, contact Software AG Customer Care.

Migrate Date and Time Stamps for Migrated Data

Convert the date and time stamps for migrated Trading Networks data from the host Integration Server’s time zone to Greenwich Mean Time (GMT) so it will display correctly for your time zone. You can take either of two approaches:

If you are converting a large amount of data, run SQL scripts against these tables and fields in the Trading Networks database component:

migratedata_to_tn_7-1.{bat|sh} 6.5

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.

Table Fields

BizDocAttributeDef LastModified

BizDocTypeDef LastModified

BizDoc DocTimestamp, LastModified

BizDocAttribute DateValue

BizDocArrayAttribute DateValue

DeliveryJob TimeCreated, TimeUpdated

ProcessingRule LastModified

ActivityLog Entry Timestamp



Go to the Integration Server_8.0_directory\packages\WmTN\bin directory and run this command:

Then run this Java program:

For example, to convert all data created on or between July 1 and December 31 2008 for a Trading Networks whose time zone is 10 1/2 hours ahead of GMT, and to commit the converted date and time stamps to the Trading Networks database component, you would enter:

After the conversion is complete, start Integration Server 8.0.

TPA TimeCreated, LastModified

EDITracking DocTimestamp, FATimestamp

EDIStatus LockTimeStamp, TimeCreated

setcp.{bat|sh}

java com.wm.app.tn.db.NormalizeTimeStamp Integration Server_8.0_directory date1 dd-Mmm-YY date2 dd-Mmm-YY time_zone [Write]

Parameter Value

Integration Server_8.0_directory

Full path to the Integration Server 8.0 directory.

date1 dd-Mmm-YY

date2 dd-Mmm-YY

To convert the date and time stamps for all Trading Networks data that was created on or before a specified date, specify that date as date1 dd-Mmm-YY.

To convert only data that was created on or between two dates, specify those dates as date1 dd-Mmm-YY and date2 dd-Mmm-YY.

Important! Software AG recommends converting data in batches; for example, you might convert data for one year at a time.

time_zone The time zone in which Trading Networks is running, expressed as GMT+ or GMT- the number of hours difference from GMT.

[Write] Optional. Commits the converted date and time stamps to the Trading Networks database component.

java com.wm.app.tn.db.NormalizeTimeStamp C:\Software AG\IntegrationServer 01-Jul-08 31-Dec-08 GMT+10:30 Write

Table Fields



Migrate Access or Portal Data

If you want to migrate runtime assets such as folders, Wiki objects, shells, skins, roles, users, or custom applications from Access or Portal 6.5, you must create a file that identifies the assets, export the assets from Access or Portal 6.5, and then import the assets into My webMethods Server 8.0.

Apply Fix

Apply MWS_6.5.2_Fix3 to Access or Portal 6.5 using the instructions in the fix readme. Fixes are available from the Software AG Knowledge Center.

Identify Assets to Export

Create a descriptor file with a name that you choose and the extension .txt. Open the file and create one entry for each asset or type of asset to export. Each entry must be on a separate line, and can be listed in any order. Entries cannot start with a forward slash (/). For information on the types of assets you can export and instructions on how to format each entry, do one of the following:

Go to the help directory in the file structure that was extracted when you applied MWS_6.5.2_Fix3. The file name is Syntax Help.xls.

Log on to My webMethods Server 8.0 as sysadmin, go to the Administration > Migration > Content Import/Export page, click Next, and then click Syntax Help.

Assets often have dependencies on other assets; for example, rule assets depend on pages to which they apply, and page assets might depend on users for access permissions. If you do not export assets on which other exported assets depend, you might experience problems after you import the assets. For example, if you export pages that depend on users for access permissions, but you do not export the users, the imported pages will no longer have access permissions associated with them. If you export roles but you do not export the users for those roles, the imported roles will have no users associated with them.

Note: If you have a cluster of 7.x My webMethods Servers, the clustering configuration was not migrated to your 8.0 installation. If you want to cluster 8.0 My webMethods Servers, you will have to configure the cluster. For instructions, see Administering My webMethods Server 8.0.




Export Assets


Go to the Access_or_Portal_6.5_directory\bin directory and enter the command below. For target_ folder, specify the folder in which to create a folder structure of all exported assets. Specify server_instance for server instances other than the default. The root folder of the export folder structure will include a file named info.properties that lists all exported assets.

Log on to Access or Portal as PortalAdmin and go to the Portal Content > Content Migration Wizard page. Under Migration Properties, select Package for Migration Source Type and Export for Migration Mode, and then click Next. Under Export Properties for Side By Side Upgrade, specify the full path to target_ folder. In the Export Descriptor field, specify the full path to the asset descriptor file. Click Next to begin the export. The export process might take several minutes.

2 Check the log file exportyyyy-mm-dd-yyyy hh mm ss.log in the Access_or_Portal_6._directory\server\server_instance\logs directory. If errors occurred, contact Software AG Customer Care.

3 Move the contents of the target folder to the machine that hosts My webMethods Server 8.0.

Import Assets

Follow the instructions in “Import Assets” on page 74.


You migrate 6.5 business processes by migrating different types of data, depending on your goals.

If you want to start new instances of migrated 6.5 process models in your 8.0 installation, do not have any running 6.5 process instances, and do not need to resubmit any 6.5 process instances, you must migrate your design-time data. Design-time data are the definitions of your business process models. In webMethods 6.5, process models were defined and stored in webMethods Modeler 6.5. In webMethods 8.0, process models are defined and stored in Designer 8.0.

If you want to finish 6.5 process instances that are already in progress or resubmit 6.5 process instances that have completed or failed, you must migrate your run-time data. Run-time data is the complete set of information about 6.5 business process models and in progress, completed, or failed 6.5 process instances that is stored in the ProcessAudit database component and, if you used it, the ProcessTrackingStore database component.

portal.{bat|sh} -s server_instance export full_path_to_descriptor_file target_folder



If you want to start new instances of migrated 6.5 process models in webMethods 8.0, and you want to finish 6.5 process instances that are in progress or resubmit 6.5 process instances that have completed or failed, you must migrate both your design-time and run-time data.


1 Open Designer 8.0, choose File > Import, and do one of the following:

In the import source tree, click SoftwareAG > Modeler 6.x process models, and then click Next. For Mode, click Import .Model Files.

If the models were developed on an Integration Server equipped with the Modeler Design Package, you can instead click webMethods > Modeler 6.x process models in the import source tree, and then click Next. For Mode, click Connect to Design Server. Specify the server address, user, and password for the Design Server.

2 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.

3 Click Finish.

4 If you want to see a summary of the import execution, click View Upgrade Log, or go to the workspace\.metadata\plugins\com.process.webmethods.upgrade.impl\ logs directory and open the ModelUpgradeLog.txt file.

5 Generate and upload your process models. For instructions, see the Designer online help.


1 You migrated webMethods Broker to 8.0 using the instructions in “Migrate webMethods Broker Data” on page 89 and “Configure the 8.0 Broker Server to Use 6.5 Storage” on page 92. Make sure the 6.5 Broker used by your 6.5 Process Run Times has the same name in 8.0 that it had in 6.5.

2 If you migrated process run-time packages using the instructions in “Run the Integration Server Migration Utility” on page 100, make sure the packages exist in the Integration Server_8.0_directory\packages directory. The package names are the process model names or custom names you specified in webMethods Modeler.

3 Prevent new instances of 6.5 process models from starting by shutting down all 6.5 Integration Servers that host Process Engines.



4 Migrate the ProcessTrackingStore and ProcessAudit database components as described below.

a Shut down all Integration Servers that connect to the 6.5 ProcessTrackingStore and ProcessAudit database components.

b Do the following for your RDBMS:

c On the machine on which you installed the Database Component Configurator, go to the 8.0_installation_directory\common\db\bin directory and open a command window.

d If you are using Oracle or DB2, run the command below. For Oracle, use the -t (tablespace) parameter only if the DB_CREATE_FILE_DEST parameter is not set for your Oracle instance.


Note: In webMethods 8.0, the ProcessTrackingStore database component is called the ProcessEngine database component.

RDBMS Action

Oracle Execute the ora_pra_m_10_to_20_metadata.sql script in the 8.0_installation_directory\common\db\ scripts\oracle\processaudit\migrate\10_to_20 directory from your database editor.

SQL Server Execute the mss_pra_m_9_to_10_indexnames.sql script in the 8.0_installation_directory\common\db\ scripts\mssql\processaudit\migrate\10_to_20 directory from your database editor.


From your database editor, do the following:

1 Execute the db2_pra_m_9_to_10_migrate.sql script and then the db2_pra_m_dml_tracking.sql script. The scripts are in the 8.0_installation_directory/common/db /scripts/db2/processaudit/ migrate/9to10 directory.

2 Execute the db2_pre_m_9_to_10_migrate.sql script and then the db2_pre_m_dml_tracking.sql script. The scripts are in the 8.0_installation_directory/common/db/scripts/ db2/processengine/migrate/9to10 directory.

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



e For each database component, run the command below.


f If you are using DB2 RDBMS, issue a DB2 REORG command on the WMPROCESS, PRTPROCESS, PRTINSTANCEITER, and WMPRTXREF tables from the DB2 command line. For example:

3 Start Integration Server 8.0 and connect the ProcessEngine and ProcessAudit functions to the corresponding database components if they are not already connected. For instructions, see Software AG Installation Guide 8.0.

4 Enable document retrieval for all triggers on Integration Server 8.0. For instructions, see Administering webMethods Integration Server 8.0.


Follow the instructions in “Migrate Deployer Data” on page 79, with these exceptions:

Target groups did not exist in Deployer 6.5, so you cannot migrate them. Ignore “Migrate Target Groups” on page 80.

You can only migrate projects that contain assets from the latest 6.5 releases of webMethods Broker, Integration Server, and Trading Networks (see “Overview” on page 84).

In the instructions, substitute “6.5” for “7.x.”





dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw}-c {ProcessEngine|ProcessAudit} -v latest -l db_server_URL-u existing_db_user -p password -fv 10




8-x Web Methods Upgrade Guide

Documents

Transcript of 8-x Web Methods Upgrade Guide