web methods upgrade guides

Title Page

webMethods Upgrade Guide

Version 7.1 and 7.2

April 2011

Copyright& Docu-ment ID
This document applies to webMethods Product Suite Version 7.1 and 7.2 and to all subsequent releases.

Specifications contained herein are subject to change and these changes will be reported in subsequent release notes or new editions.

Copyright © 2007-2011 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, United States of America, and/or their licensors.

The name Software AG, webMethods, and all Software AG product names are either trademarks or registered trademarks of Software AG and/or Software AG USA, Inc. and/or their licensors. Other company and product names mentioned herein may be trademarks of their respective owners.

Use of this software is subject to adherence to Software 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-71-20110422

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



Table of Contents

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

1. Migrating from 6.1 to 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Back Up the 6.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15Install webMethods Product Suite 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . 18Migrate webMethods Broker 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 197.1.2 Broker Servers and 6.1 Broker Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 196.1 Broker Servers and 7.1.2 Broker Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Set Up Broker Server to Use 6.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20Migrate if You Do Not Have Gateways and Territories . . . . . . . . . . . . . . . . . . . . . 20Migrate if You Have Gateways and Territories . . . . . . . . . . . . . . . . . . . . . . . . . . . 21Configure 7.1.2 Broker Server to Use the 6.1 Combined Storage Session . . . . . . 22

Configure the Forwarding Behavior of a Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24Migrate JMS Provider 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 256.1 JMS Clients and Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Message Granularity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Message Persistence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25SSL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Update JMSAdmin Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Migrate Bound Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26Modify Connection Factory Objects . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Modify Topic and Queue Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27Modify Client Groups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28Modify Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

New JMSAdmin Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 28JMSAdmin Command Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29Other Changes to Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Convert JMS Client APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31AdminFactory Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31QueueAdmin Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31QueueConnectionFactoryAdmin Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32TopicAdmin Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33TopicConnectionFactoryAdmin Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

webMethods Upgrade Guide Version 7.1 and 7.2 3

Table of Contents

TopicConnectionFactory Client ID Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Library Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

Migrate Integration Server 6.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Migrate the Integration Server Database Components . . . . . . . . . . . . . . . . . . . . . . . . . 35Migrate the 6.1 Repository Server Data to IS Internal . . . . . . . . . . . . . . . . . . . . . . . . . 36Migrate Configuration Data and User-Created Packages . . . . . . . . . . . . . . . . . . . . . . . 37Configure Integration Server 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37Check Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Migrate Trading Networks 6.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Migrate the Properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Migrate the Trading Networks Database Components . . . . . . . . . . . . . . . . . . . . . . . . . 40Migrate the Certificate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Migrate the tspace Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

Migrate 6.1.5 Business Process Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42

2. Migrating from 6.5 to 7.1.2 and 7.1.3 or Designer 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Back Up the 6.5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Install webMethods Product Suite 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . 51Migrate webMethods Broker 6.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 527.1.2 Broker Servers and 6.5.2 Broker Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . 526.5.2 Broker Servers and 7.1.2 Broker Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Set Up the 7.1.2 Broker Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52Migrate if You Do Not Have Gateways and Territories . . . . . . . . . . . . . . . . . . . . . 53Migrate if You Have Gateways and Territories . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Configure the 7.1.2 Broker Server to Use 6.5.2 Storage . . . . . . . . . . . . . . . . . . . . 55

Migrate Java Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Command-Line Utilities Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57Broker Java API Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57

Changed Methods in BrokerConnectionDescriptor Class . . . . . . . . . . . . . . . 57New Methods in BrokerConnectionDescriptor Class . . . . . . . . . . . . . . . . . . . 58New Methods in BrokerServerClient Class . . . . . . . . . . . . . . . . . . . . . . . . . . 58

Migrate C Clients . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Changed Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Removed Methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Migrate JMS 6.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Backward Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59Update JMSAdmin Scripts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

JMSAdmin Command Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60Convert JMS Client APIs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

Changed Method in WmJMSAdminFactory Class . . . . . . . . . . . . . . . . . . . . . . . . . 61Deprecated WmFileMessage Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61

4 webMethods Upgrade Guide Version 7.1 and 7.2

Table of Contents

New Methods in WmJMSConfig Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62New Fields in WmConnectionFactory Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62New Methods in WmConnectionFactory Class . . . . . . . . . . . . . . . . . . . . . . . . . . . 62New Method in WmQueueConnectionFactory Class . . . . . . . . . . . . . . . . . . . . . . 62New Method in WmTopicConnectionFactory Class . . . . . . . . . . . . . . . . . . . . . . . 63

Library Locations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Migrate Integration Server 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Migrate Configuration Data and User-Created Packages . . . . . . . . . . . . . . . . . . . . . . 63Migrate the 6.5 Repository Server Data to IS Internal . . . . . . . . . . . . . . . . . . . . . . . . . 64Configure Integration Server 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65Check Certificates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66Migrate the Integration Server Database Components . . . . . . . . . . . . . . . . . . . . . . . . 66

Migrate Trading Networks 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Migrate the Trading Networks Properties File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67Migrate the Trading Networks Database Components . . . . . . . . . . . . . . . . . . . . . . . . . 68

Migrate 6.5.x Custom Portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69Migrate 6.5.1 Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Migrate Design-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70Migrate Run-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Start the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71Migrate the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71

Migrate the Process Audit Log Database Component . . . . . . . . . . . . . . . . . . 72Migrate the Process Tracking Store Database Component . . . . . . . . . . . . . . 72

Complete the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73Migrate Optimize 6.5.1 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73

Migrate Optimize 6.5 SP2 to Optimize 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Install Optimize 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Transform Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74Migrate the Analysis and Process Tracker Database Components . . . . . . . . . . . 76

Create Storage and Grant Privileges . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Prepare DB2 for Linux, UNIX, Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76Migrate the Analysis Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . 77Migrate the Process Tracker Database Component . . . . . . . . . . . . . . . . . . . 77

Start the 7.0 SP2 Analytic Engine . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Drop the 7.0 SP2 Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

Migrate Optimize 7.0 SP2 to Optimize 7.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Define Rule Alerts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Migrate the Analysis and Process Tracker Database Components . . . . . . . . . . . 78Create a New Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79

3. Migrating from Fabric 7 to 7.1.2 or Designer 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Back Up the Fabric 7 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84Install webMethods Product Suite 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84


Table of Contents

Sample URL Formats for Database Component Migration . . . . . . . . . . . . . . . . . . . . . . . . . 87Migrate webMethods Broker and JMS 6.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Migrate Integration Server 6.5 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87Migrate Trading Networks 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Migrate My webMethods Server 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Migrate 7.0 SP2 Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Migrate Design-Time Data to Designer 7.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89Migrate Design-Time Data to Designer 7.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90

Export Process Models and Logical Server Definitions from Designer 7.0 SP2 . . 90Import Process Models and Logical Server Definitions into Designer 7.2 . . . . . . . 91

Migrate Run-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Start the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92Migrate the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93Complete the Migration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Migrate 7.0 SP2 Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94Migrate Design-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95

Export Task Projects from Designer 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95Import 7.0 SP2 Task Projects into Designer 7.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . 95

Migrate Run-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Complete the Metadata Library 7.0 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96Migrate Optimize 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Migrate Optimize Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Create a New Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97Migrate the Data Purge Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98

Complete the Deployer 7.0 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

4. Upgrading from 7.x to 7.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102Back Up the Earlier 7.x Installation and Remove Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103Prepare to Upgrade a My webMethods Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Prepare to Upgrade a 7.1.1 My webMethods Server Cluster . . . . . . . . . . . . . . . . . . . . 104Prepare to Upgrade a 7.1.2 My webMethods Server Cluster . . . . . . . . . . . . . . . . . . . . 105

Install webMethods Product Suite 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105Complete the Integration Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Migrate Integration Server 7.1.2 or 7.1.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106Convert JAX-RPC Handlers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107

Migrate Integration Server 7.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108Increase PermGen Space . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Windows System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108UNIX, IBM i5, or Mac System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108

Update the Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Migrate the Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109Convert JAX-RPC Handlers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Complete the Trading Networks Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110


Table of Contents

Migrate Trading Networks Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110Set Up Trading Networks to Work with My webMethods Server . . . . . . . . . . . . . . . . . 111

Complete the Metadata Library Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Complete the Designer Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112Complete the My webMethods Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Migrate My webMethods Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113Upgrade a My webMethods Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 114

Migrate Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Migrate Design-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116Migrate Run-Time Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Complete the Optimize Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Configure Infrastructure Data Collector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Migrate Optimize Database Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117Create a New Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118Migrate the Data Purge Database Component . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118

Complete the Deployer Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119


Table of Contents


About This Guide

This guide is for users who are upgrading to the 7.1 webMethods product suite. The products that make up this suite are listed below.

Document Conventions

Product Release

Fair Isaac Blaze AdvisorBlaze Rule Server Plug-in to DeveloperBlaze Rule Service Support on Integration Server

6.5.57.1.27.1.2

webMethods Broker 7.1.2

webMethods Deployer 7.1.2

webMethods Designer

Business Processes plug-ins 7.1.2

Composite Applications plug-ins 7.1.3

Business Processes plug-ins 7.2

ESB and Integration Server plug-ins 7.2

Composite Applications plug-ins 7.2.1

webMethods Developer 7.1.3

webMethods Integration Server 7.1.3

webMethods Metadata Library 7.1.1

webMethods Monitor 7.1.2

My webMethods Server and Task Engine 7.1.3

My webMethods users interfaces for Broker and JMS, Central Configurator, Monitor, Optimize for B2B, Optimize for Infrastructure, Optimize for Process, and Trading Networks

7.1.2

webMethods Process Engine 7.1.2

webMethods Optimize 7.1.2

webMethods Trading Networks (Console and Server) 7.1.2

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.


About This Guide

Documentation Installation

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

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

Convention Description


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


http://documentation.softwareag.com

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

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


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

1 Migrating from 6.1 to 7.1.2 and 7.1.3

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

Back Up the 6.1 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Upgrade Your RDBMSs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Install webMethods Product Suite 7.1.2 and 7.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16

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

Migrate webMethods Broker 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Migrate JMS Provider 6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25

Migrate Integration Server 6.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

Migrate Trading Networks 6.1 Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

Migrate 6.1.5 Business Process Models . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42



Overview

This upgrade procedure explains how to upgrade your 6.1.x products to webMethods product suite 7.1.2 and 7.1.3, and how to migrate the following:

Data from:

webMethods Broker and JMS Provider 6.1 or 6.1 SPx

Integration Server 6.1 or 6.1 SPx

Trading Networks 6.1 or 6.1 SPx

Business process models from webMethods Modeler 6.1.5

There is no procedure for migrating data from the 6.1.x products listed below to webMethods product suite 7.1.2 and 7.1.3. However, you can upgrade those 6.1.x products to the indicated 7.1.2 and 7.1.3 products, all of which contain considerably more functionality than their 6.1.x counterparts.

Back Up the 6.1 Installation

1 Allow all Integration Server guaranteed delivery jobs to finish running. Allow all business processes to finish running or use webMethods Monitor to stop them. Shut down all 6.1 webMethods products and all other applications that are running on the machines on which you are going to install webMethods product suite 7.1.2 and 7.1.3.

2 For each webMethods Broker 6.1, back up your JMS objects and data.

6.1.x Product webMethods Product Suite 7.1.2 Replacement

webMethods Manager Console 6.1.5Optimize for Infrastructure 7.1.2

webMethods Manager Server 6.1.5

Optimize 6.1.5 Optimize for Process 7.1.2

PRT 6.1 or 6.1.5 Process Engine 7.1.2

webMethods Workflow 6.1.5 Designer 7.1.2 and Task Engine 7.1.3

Important! You must upgrade all of your products at the same time; you cannot use 6.1 products with 7.1.x products. You must upgrade products and migrate data in the order presented in this chapter.

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

Important! If all of the above are not shut down, the installer will not be able to replace key files that are locked by the operating system.



3 Back up the entire 6.1 webMethods installation directory on each machine, and back up your 6.1 webMethods databases as instructed by your RDBMS vendor.

4 For each Integration Server 6.1, do the following:

a Start Integration Server and open Integration Server Administrator.

b Record port settings and prepare the ports for migration, as follows:

1 Go to the SecurityPorts page and print the page.

2 For each HTTPS, Proxy, HTTPS Proxy, SOCK, and SSL SOCK port, click the link in the Port column to display the View type Port Details page and print the page.

3 Reverse invoke was rearchitected in Integration Server 7.1.2 and load balancing was removed, so you cannot migrate ports that relate to those features. Delete Proxy, HTTPS Proxy, SOCK, SSL SOCK, Registration, and

Load Balancer ports from the list by clicking in the row for each port.

4 Record the name of the package that is associated with each remaining port.

c Prepare your user-created packages for migration, as follows:

1 Go to the PackagesPublishingCreate and Delete Releases page.

2 Click Create Release for a user-created package.

3 Scroll to the bottom of the page that appears and click Create Release. Integration Server creates a zip file containing the package and places the zip file in the Integration Server_6.1_directory\replicate\outbound directory.

4 Repeat these steps for each user-created package.

d Record your imported client certificate and user mappings by going to the SecurityCertificatesConfigure Client Certificates page and printing it.

e Record your Broker connection by going to the SettingsBrokerEdit Broker Settings page and printing it.

f If you have configured LDAP on the Integration Server, record your LDAP configuration by going to the SecurityUsers & GroupsJNDI Settings page and printing it.

g If the Integration Server is part of a cluster, record all the cluster information by going to the SettingsClustering page and printing it.

5 Shut down Integration Server. Do not shut down the Repository Server; make sure it continues running until all data has been migrated.

Upgrade Your RDBMSs

Check your RDBMSs against webMethods System Requirements 7.1. If the RDBMS version you are using is not supported by webMethods product suite 7.1.2 and 7.1.3, you must upgrade to a supported version before continuing with the instructions in this chapter.



Install webMethods Product Suite 7.1.2 and 7.1.3

Go to the documentation area of the Empower Product Support Web site and download webMethods Installation Guide 7.1. Follow the instructions in that guide to install webMethods product suite 7.1.2 and 7.1.3, with these additional guidelines or differences:

For the installation directory, specify a new webMethods directory.

For webMethods Broker, you must make a storage choice that might require you to install on a certain machine. webMethods Broker 6.1 used a combined storage session, where all data were maintained in the same set of storage files. webMethods Broker 7.1.2 supports combined storage, but by default uses separate storage sessions. With separate storage sessions, metadata such as document-type and client-group definitions are maintained in one session and run-time data such as document instances and client queues are maintained in another session. Software AG strongly recommends you use separate storage sessions in production environments because you can then use the server_conf_backup utility to back up the Broker Server’s metadata without taking the Broker Server offline. If you want to begin using separate storage sessions, you can install webMethods Broker 7.1.2 on any machine. If you want to continue using your 6.1 combined storage session, you must install webMethods Broker 7.1.2 on the machine that hosts the webMethods Broker 6.1 installation.

On the installer’s product selection tree, select the 7.1.2 and 7.1.3 products to install; be sure to select all necessary pieces for each product (see the “Development Installations” chapter in webMethods Installation Guide 7.1).

If you are installing products that use an RDBMS, also select the Database Component Configurator.

Important! If you are upgrading to webMethods Broker 7.1.2, you must obtain the 7.1.2 license key from [email protected]. You can use your existing license key for Integration Server.


mailto:[email protected]



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

After product installation is complete, create the webMethods product suite 7.1.2 database components that the table below indicates you should create; for instructions, see webMethods Installation Guide 7.1. Do not create database components that the table indicates you should not create; you will migrate the 6.1 database components to 7.1.2 later in this procedure.

Product Action

Trading Networks

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

Integration Server

If you choose to use an external RDBMS (as opposed to the embedded database), point the database connection at the 6.1 IS Core Audit Log database component if it exists. Otherwise, point at the external RDBMS you will use for Integration Server 7.1.3 data (see the next bullet, below).

webMethods Broker

If you want to begin using separate storage sessions, create a Broker Server configuration. The installer requires your webMethods Broker license key to create a Broker Server configuration; make sure to supply the 7.1.2 license key. The installer will also create separate storage sessions for the 7.1.2 Broker Server. Later, you will migrate the 6.5.2 metadata to the 7.1.2 Broker Server.

If you want to continue using your 6.1 combined storage session, do not create a Broker Server configuration. Later, you will create the 7.1.2 Broker Server (but not the separate storage sessions) and configure it to use the 6.5.2 storage.

Note: For 7.1.3 products, you will still create 7.1.2 database components.

If you are migrating... Do the following...

Integration Server Do not create the IS Core Audit Log and Document History database components.

If you chose the embedded database during installation, or if you stored 6.1 cross-referencing data in the Cross Reference database component, do not create a Cross Reference database component. If you chose an external RDBMS during installation and want to store cross-referencing data in it, create the Cross Reference database component.



Sample URL Formats for Database Component Migration

For Integration Server and Trading Networks, you will migrate data stored in webMethods database components, and you will need to supply database server URLs. Sample formats are shown below.

If you chose an external RDBMS during installation, cre-ate the IS Internal and Distributed Locking database com-ponents. If you are using Oracle or DB2 for Linux, UNIX, Windows, first create storage and a tablespace directory for IS Internal by running this command:

dbConfigurator.{bat|sh} -a create -d {oracle|db2luw}-c storage -v latest -l db_server_URL-u existing_db_user -p password -au db_admin_user-ap password -t full_path_to_new_tablespace_directory

Oracle example:

dbConfigurator.bat -a create -d oracle -c storage-v latest -l jdbc:wm:oracle://localhost:1521;ServiceName=ORCL-u webmuser -p webmuser -au admin_user -ap admin_user-t C:\oradata\orcl

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

DB2 for LUW example:

dbConfigurator.bat -a create -d db2luw -c storage-v latest -l jdbc:wm:db2://localhost:50000;databaseName=webm_db-u webmuser -p webmuser -au admin_user -ap admin_user-t C:\DB2\Data\

Trading Networks Do not create the Trading Networks and Trading Networks Archive database components.

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 …]




For DB2, if the product will connect to a schema other than the default schema for the specified database user, you must specify these connection options in the URL:

;AlternateId=schema;InitializationString="SET CURRENT PATH=schema"

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

Migrate webMethods Broker 6.1

Backward Compatibility

7.1.2 Broker Servers and 6.1 Broker Clients

7.1.2 Broker Servers are compatible with these 6.1 Broker clients:

Command-line tools/utilities

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

6.1 Broker Servers and 7.1.2 Broker Clients

6.1 Broker Servers are compatible with these 7.1.2 Broker clients:

Broker and JMS user interface 7.1.2 on My webMethods Server

Command-line utilities

Broker Client C and Java APIs

6.1 Broker Servers do not support the complete set of 7.1.2 API functionality. For example, if you use a 7.1.2 Broker client with a 6.1 Broker Server, the client keep-alive, gateway keep-alive, gateway pause, UTC time stamp, and server_config for dual storage sessions features are not supported.

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 …]

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




Set Up Broker Server to Use 6.1 Data

If you chose to begin using separate storage sessions in webMethods Broker 7.1.2, you created a 7.1.2 Broker Server configuration during installation. You must now migrate the 6.1 metadata to the 7.1.2 Broker Server metadata storage. If you do not have gateways and territories, see “Migrate if You Do Not Have Gateways and Territories” on page 20. If you do have gateways and territories, see “Migrate if You Have Gateways and Territories” on page 21.

If you chose to continue using your 6.1 combined storage session, you did not create a 7.1.2 Broker Server configuration during installation. You must now create a 7.1.2 Broker Server and configure it to use the 6.1 combined storage session. For instructions, see “Configure 7.1.2 Broker Server to Use the 6.1 Combined Storage Session” on page 22.

Migrate if You Do Not Have Gateways and Territories

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

1 Start My webMethods Server 7.1.2 and open My webMethods.

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

a In My webMethods, go to the AdministrationMessagingBroker ServersServers

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

b Click the Export tab, select the check box next to the 6.1 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 FoldersAdministrative FoldersAdministration DashboardContent 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 7.1.2 Broker Server. Import the Broker Server data and configuration into the 7.1.2 Broker Server as follows:


page and click in the DETAIL column for the 7.1.2 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 7.1.2 Broker Server and click Import. If prompted, click Skip SSL Configuration to not import the 6.1 Broker Server SSL configuration; the 6.1 SSL configuration is incompatible with the 7.1.2 SSL configuration.

4 Your 6.1 Broker Server SSL configuration was not imported. If you are using SSL, convert your SSL keystores to the correct format and configure SSL, including ACLs, for the 7.1.2 Broker Server. For instructions, see webMethods Broker Administrator’s Guide 7.1.

Migrate if You Have Gateways and Territories

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


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

a In My webMethods, go to the AdministrationMessagingBroker TerritoriesTerritories page and click a territory whose configuration you want to export.

b Click the Export tab, select the check box next to the 6.1 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:


2 Go to the FoldersAdministrative FoldersAdministration DashboardContentContent 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 AdministrationMessagingBroker ServersServers page and stop all 6.1 Broker Servers. Refresh the page and make sure the Broker Servers no longer appear on the list.



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

a In My webMethods, go to the AdministrationMessagingBroker TerritoriesTerritories page.

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


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

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 webMethods Broker Administrator’s Guide 7.1.

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

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

7 Your 6.1 Broker Server SSL configuration was not imported. If you are using SSL, convert your SSL keystores to the correct format and configure SSL, including ACLs, for the 7.1.2 Broker Server. For instructions, see webMethods Broker Administrator’s Guide 7.1.

8 Go to “Configure the Forwarding Behavior of a Gateway” on page 24 in this procedure.

Configure 7.1.2 Broker Server to Use the 6.1 Combined Storage Session

Use this procedure if you want to continue using your 6.1 combined storage session, and thus did not create a Broker Server configuration during installation.

This procedure explains how to create a 7.1.2 Broker Server and configure it to use the 6.1 storage. The procedure also removes the 6.1 Broker Server from the 6.1 Broker Monitor startup configuration and adds it to the 7.1.2 Broker Monitor startup configuration.

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

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



3 Back up the 6.1 awbrokermon.cfg file.

4 Remove the 6.1 Broker Server from the 6.1 Broker Monitor startup configuration by going to the webMethods Broker_6.1_directory\bin directory and running the command below. If any part of the data directory path contains a space, enclose the entire path in quotes.

5 Create the 7.1.2 Broker Server and configure it to use the 6.1 combined storage session by going to the webMethods Broker_7.1.2_directory/bin directory and running the command below. If any part of the data directory path contains a space, enclose the entire path in quotes.

6 Make sure the 6.1 combined storage session is running under the 7.1.2 Broker Server:

System awbrokermon.cfg File Location

Windows c:\WINDOWS\webmethods

UNIX /var/opt/webmethods6

server_config remove full_path_to_6.1_data_directory

System Example

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

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

Important! For license_key, supply your 7.1.2 webMethods Broker license key.

server_config add full_path_to_6.1_data_directory -k license_key -p port

System Example

Windows server_config add c:\webmethods6\Broker\data\awbrokers\default-k WLRS8X-E073106-S000-KH-C10100-2SBR-N4NMPX -p 6871

UNIX server_config add /var/opt/webmethods6/awbrokers/default-k WLRS8X-E073106-S000-KH-C10100-2SBR-N4NMPX -p 6871

System Steps

Windows 1

2

3

Open the Windows Services window.

Make sure the status of the webMethods Broker Server 7.1 (port) service is Started.

Right-click the service and click Properties. Make sure the value in the Path to Executable field points to the awbroker file for 7.1.2.



7 If you are using SSL, convert your keystores to the correct format. For instructions, see webMethods Broker Administrator’s Guide 7.1.

8 See “Configure the Forwarding Behavior of a Gateway”, below.

Configure the Forwarding Behavior of a Gateway

In webMethods Broker 6.1, a gateway Broker used dynamic gateway forwarding to generate and maintain the subscription list for a remote Broker. In this mode, when a client in a remote territory subscribed to or dropped its subscription to a particular document type, the remote Broker communicated the event to the gateway Broker, and the gateway Broker dynamically updated its subscription list.

webMethods Broker 7.1.2 uses a new mode called static gateway forwarding. In this mode, the gateway Broker automatically generates a subscription for each document type in its “allow-forward” list. In other words, the 7.1.2 gateway Broker derives the subscription list from the document types the remote territory is permitted to receive. This mode simplifies the subscription process and eliminates the gateway Broker’s dependence on the successful propagation of subscription events, greatly improving gateway reliability.

In webMethods Broker 7.1.2, static gateway forwarding is enabled by default. As a result, you might see the following after you upgrade:

An increase in the number of documents the gateway Broker places in the forward queue for the remote Broker, and a corresponding increase in the number of messages flowing between the gateway Broker and the remote Broker.

If the dead-letter queue is enabled on the remote Broker, an increase in the number of documents deposited in that queue.

After you upgrade a gateway Broker, Software AG recommends that you carefully review the allow-forward list for that gateway. In static mode, it is important to configure this list carefully; the gateway Broker will forward all documents on the list, even those for which there are no actual subscribers. Forwarding such documents wastes processing

UNIX 1 Enter this command:

ps -ef | grep aw

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

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

System Steps



time, queue space, and network bandwidth. Make sure the list includes only the document types to which clients in the remote territory actually subscribe. For procedures, see webMethods Broker Administrator’s Guide 7.1.

Migrate JMS Provider 6.1


6.1 JMS Clients and Objects

6.1 JMS clients can run on 7.1.2 Broker Servers.

Because they use different messaging formats, 6.1 JMS clients cannot exchange messages directly with 7.1.2 JMS clients. If you need 6.1 and 7.1.2 JMS clients to exchange messages, you can use the marshalling feature in JMS 7.1.2 to convert 7.1.2 messages to the 6.1 format, or in JMS Provider 6.1 to convert 6.1 messages to the 7.1.2 format. For instructions, see webMethods Messaging Programmer’s Guide 7.1.

JMS Provider 6.1 utilities and JMS 7.1.2 utilities are not compatible. 6.1 JMS clients can only use administered objects (that is, connection factories and destinations) generated using 6.1 utilities, and 7.1.2 JMS clients can only use administered objects generated using 7.1.2 utilities. In addition, administered objects created using 6.1 utilities and script files generated using 6.1 utilities are not compatible with administered objects created using 7.1.2 utilities and script files generated using 7.1.2 utilities. If you are planning to use the same naming directories for JMS 7.1.2 that you used for JMS Provider 6.1, you must migrate the JMS data. For instructions, see “Update JMSAdmin Scripts” on page 26.

Message Granularity

webMethods Broker and JMS offer explicit acknowledgment of non-persistent (volatile) messages and support for sequence numbers on volatile messages. JMS 7.1.2 allows for finer granularity of quality of service with the assignment of delivery mode and time-to-live on a per-message basis, and the assignment of storage type and lifecycle on a per-client basis.

Message Persistence

For JMS 7.1.2, event types are no longer used to control the persistence of messages. Persistence is now specified using the DeliveryMode (per message), as defined by Java Message Service Specification version 1.1.

Important! Software AG strongly encourages you to leave your gateway Broker in static mode. It is inherently more reliable. Additionally, dynamic forwarding might be deprecated in a future release. However, if you need to switch to dynamic mode, you can do so. For instructions, see webMethods Broker Administrator’s Guide 7.1.



SSL

The SSL keystore format changed in release 7.1. If you have been using Spyrus keystore files, you must migrate your keystores to the new format and bind the new location of the keystore and truststore in your Connection Factories. For instructions, see webMethods Broker Administrator’s Guide 7.1.

Update JMSAdmin Scripts

JMS Provider 6.1 utilities and JMS 7.1.2 utilities are not compatible. JMS Provider 6.1 included the broker_jms admin utility, which used XML scripts to generate JMS objects. That utility was deprecated in JMS Provider 6.1 SP1 and was replaced by the JMSAdmin 6.1 command-line utility, which uses its own scripting language to generate JMS objects.

JMS objects created using broker_jms 6.1 and JMSAdmin script files generated using JMSAdmin 6.1 are not compatible with objects and JMSAdmin script files created using JMSAdmin 7.1.2. If you are planning to use the JMS Provider 6.1 naming directories for JMS 7.1.2, follow the instructions in “Migrate Bound Objects”, below.

6.1 JMS clients can only use administered objects (that is, connection factories and destinations) generated using 6.1 utilities, and 7.1.2 JMS clients can only use administered objects generated using 7.1.2 utilities. If you want to continue using 6.1 JMS clients with Broker Server 7.1.2, create 7.1.2 administered objects containing the same data as the 6.1 administered objects and store the 7.1.2 objects in a different naming directory than the 6.1 naming directory. If you want to migrate all of your 6.1 JMS clients to 7.1.2, you can continue to use the 6.1 naming directory. To do so, unbind your 6.1 objects and rebind them using the instructions in “Migrate Bound Objects”.

Migrate Bound Objects

Below are general steps for using JMSAdmin to migrate administered objects that are bound to a JNDI context.

1 Start JMSAdmin 6.1 and do the following:

a Change the context to the one in which the bound objects are located.

b Export the bound objects to a file.

c Unbind the objects from the naming directory provider.

2 End the JMSAdmin 6.1 session.

3 Edit the export file as follows:

a Change the properties for administered objects as described in “Modify Connection Factory Objects” on page 27 and “Modify Topic and Queue Destinations” on page 27.

b Modify client groups as explained in “Modify Client Groups” on page 28.

c Update commands as described in “Modify Commands” on page 28.



d Remove any obsolete properties.

e Save the changes.

4 Start JMSAdmin 7.1.2 and do the following:

a Change the context to the one in which to bind the objects.

b Run the JMSAdmin import command on the saved file.

c Use the appropriate JMSAdmin create commands to create the bound objects on the Broker.

d Assign the appropriate permissions to the objects.

5 End the JMSAdmin 7.1.2 session.

Modify Connection Factory Objects

Make the following changes for connection factory objects (TopicConnectionFactory and QueueConnectionFactory) in your JMSAdmin scripts:

Either rename the connectionClientID property to clientID or remove the property. If the connection factory is used to create a connection for a durable subscriber, the clientID property must be set while binding the connection factory object.

If you want to have multiple client sessions connecting to the same Broker client queue, set the sharedState and sharedStateOrdering properties on the destinations that will use the connection factory. The sharedStateOrdering property guarantees to the client session that the documents it receives from a particular publisher will always be in the publishing order. If the sharedState and sharedStateOrdering properties are set in the bind commands for the connection factory, remove them.

For more information, see “JMSAdmin Command Changes” on page 29.

Modify Topic and Queue Destinations

In JMS Provider 6.1, a script is allowed to use a topic that does not exist on the Broker. In this case, the JMS Provider used DefaultEvent. In JMS 7.1.2, you must explicitly create the document on the Broker using the create topic command, and grant permissions using the permit group command.

In JMS 7.1.2, there is no Broker::JMS::DefaultEvent document type. You must explicitly create a queue with the create queue command. Doing so will create one document type per queue. There are two forms of this command:

One form allows you to create a queue and specify all its properties.

The other form adopts the properties set by the bind queue command for the specified factory object (QueueConnectionFactory or ConnectionFactory). It also grants send and receive permissions for the document type to the client group used by the factory object specified in the command.



Both forms of the create queue command create a document type of the form JMS::Queues::queue. For more information, see “JMSAdmin Command Changes” on page 29.

Modify Client Groups

JMS Provider 6.1 used a number of different client groups with possibly different publish and subscribe permissions. JMS 7.1.2 uses only one client group per connection. The 6.1 client groups are listed in the table below, along with example can-publish and can-subscribe permissions.

To migrate 6.1 scripts to 7.1.2, Software AG recommends you create a new (replacement) client group that contains the permissions of the above 6.1 client groups, using the JMSAdmin permit command.

The following example shows how to create a new client group named ReplacementClientGroup for use in your 6.1 JMSAdmin scripts, and how to assign the client group the appropriate permissions for the topics specified in the table.

Modify Commands

This section lists changes to JMSAdmin 7.1.2 since release 6.1.

New JMSAdmin Commands

The commands below were added in JMSAdmin 7.1. For more information, see webMethods Messaging Programmer’s Guide 7.1.

Display

Bind ConnectionFactory

Modify ConnectionFactory

Client Group Name

Example Permissions

Can-Publish Can-Subscribe

SubscriberClientGroup X TopicA

DurableSubscriberClientGroup X TopicB

SessionClientGroup TopicC TopicD

ConnectionClientGroup X X

create group ReplacementClientGrouppermit group ReplacementClientGroup to publish TopicCpermit group ReplacementClientGroup to subscribe TopicA TopicB TopicD

Note: For JMS 7.1.2, the Broker client group properties “lifecycle” and “storage type” are set as appropriate for the type of Broker client being created. You cannot change these properties in JMS.



Set Broker

Set Encoding

Set RecoverMode

JMSAdmin Command Changes

Command 7.1 Modification

Import Added optional encoding parameters

Unbind Added a wildcard (*) parameter to allow unbinding all JMS objects in the current context

Create Group Removed the optional client group type parameter

Removed the create group name for factory form of the command

Create Topic Removed the optional NON-PERSISTENT clause

Create DurableSubscriber Changed SSL parameters

Added a new form of the command that lets you directly create a durable subscriber client on a Broker without having to use bound JMS objects (that is, topics and connection factories)

Delete DurableSubscriber Removed SSL parameters

Create Queue Changed SSL parameters

Added a new form of the command that lets you directly create a queue client on a Broker without having to use bound JMS objects (that is, queues and connection factories)

Delete Queue Removed SSL parameters

PermitChanged command syntax

Deny


Changed SSL parameters and added marshalling class names


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 Property Added After 6.1 Property Removed After 6.1

TopicConnectionFactory Application ConnectionClientID

UseXA ConnectionClientGroup

ClientGroup SessionClientGroup

ClientId SubscriberClientGroup

marshallInClassName DurableSubscriberClientGroup

marshallOutClassName TCPConnectionSharing

SSLTruststore SharedState

SharedStateOrdering

StrictClientID

TemporaryEventTopicName

sslDN

QueueConnectionFactory Application ConnectionClientID

UseXA ConnectionClientGroup

ClientGroup SessionClientGroup

ClientId TCPConnectionSharing

marshallInClassName SharedState

marshallOutClassName SharedStateOrdering

SSLTruststore StrictClientID

sslDN

Topic SharedState

SharedStateOrdering

EventType

LocalOnly

DeadLetterOnly

PriorityOrdering

Command 7.1 Modification



Other Changes to Commands

Identifiers for variables used with JMSAdmin commands can now start with a dollar sign ($) or a percent sign (%).

Convert JMS Client APIs

Use the tables in this section to convert the indicated JMS Provider 6.1 API methods to JMS 7.1.2. The 6.1 methods belong to the com.wm.broker.jms package, which webMethods does not ship with 7.1.2. The 7.1.2 methods belong to the com.webmethods.jms package. The methods in the tables are grouped according to the 6.1 classes.

AdminFactory Class

QueueAdmin Class

Queue SharedState ClientGroup

SharedStateOrdering

PriorityOrdering

Convert this 6.1 method... To this 7.1.2 method...

newQueue WmJMSFactory.getQueue

newQueueConnectionFactory WmJMSFactory.getQueueConnectionFactory

newTopic WmJMSFactory.getTopic

newTopicConnectionFactory WmJMSFactory.getTopicConnectionFactory


asXML Not supported in 7.1.2. Use the export command in the JMSAdmin command-line utility instead.asADL

getClientGroup WmQueueConnectionFactory.getClientGroup

setClientGroup WmQueueConnectionFactory.setClientGroup

getName WmQueue.getName

setName WmQueue.setName

getSharedState WmQueue.getSharedState

setSharedState WmQueue.setSharedState

getSharedStateOrdering WmQueue.getSharedStateOrdering

Command Property Added After 6.1 Property Removed After 6.1



QueueConnectionFactoryAdmin Class

setSharedStateOrdering WmQueue.setSharedStateOrdering

_remove Not supported in 7.1.2


asADL Not supported in 7.1.2. Use the export command in the JMSAdmin command-line utility instead.asXML

getAutoReconnect WmJMSConfig.getReconnectAttempts

setAutoReconnect WmJMSConfig.setReconnectAttempts

getBrokerHost WmQueueConnectionFactory.getBrokerHost

setBrokerHost WmQueueConnectionFactory.setBrokerHost

getBrokerName WmQueueConnectionFactory.getBrokerName

setBrokerName WmQueueConnectionFactory.setBrokerName

getConnectionClientId WmQueueConnectionFactory.getClientID

setConnectionClientId WmQueueConnectionFactory.setClientID

getConnectionClientGroup WmQueueConnectionFactory.getClientGroup

setConnectionClientGroup WmQueueConnectioNFactory.setClientGroup

getDurableClientGroup WmQueueConnectionFactory.getClientGroup

setDurableClientGroup WmQueueConnectionFactory.setClientGroup

getSessionClientGroup WmQueueConnectionFactory.getClientGroup

setSessionClientGroup WmQueueConnectionFactory.setClientGroup

getSharedState WmQueue.getSharedState

setSharedState WmQueue.setSharedState

getSharedStateOrdering WmQueue.getSharedStateOrdering

setSharedStateOrdering WmQueue.setSharedStateOrdering

getSSLCertificateFilename WmQueueConnectionFactory.getSSLKeystore

setSSLCertificateFilename WmQueueConnectionFactory.setSSLKeystore

getSSLEncrypted WmQueueConnectionFactory.getSSLEncrypted

setSSLEncrypted WmQueueConnectionFactory.setSSLEncrypted

getStrictClientId Conforms to JMS specification

setStrictClientId Conforms to JMS specification




TopicAdmin Class

TopicConnectionFactoryAdmin Class

getSubscriberClientGroup WmQueueConnectionFactory.getClientGroup

setSubscriberClientGroup WmQueueConnectionFactory.setClientGroup

getTcpConnectionSharingSingle TCP connection per JMS client

setTcpConnectionSharing


asXML Not supported in 7.1.2. Use the export command in the JMSAdmin command-line utility instead.asADL

getName WmTopic.getName

setName WmTopic.setName


asADL Not supported in 7.1.2. Use the export command in the JMSAdmin command-line utility instead.asXML

getAutoReconnect WmJMSConfig.getReconnectAttempts

setAutoReconnect WmJMSConfig.setReconnectAttempts

getBrokerHost WmTopicConnectionFactory.getBrokerHost

setBrokerHost WmTopicConnectionFactory.setBrokerHost

getBrokerName WmTopicConnectionFactory.getBrokerName

setBrokerName WmTopicConnectionFactory.setBrokerName

getConnectionClientId WmTopicConnectionFactory.getClientID

setConnectionClientId WmTopicConnectionFactory.setClientID

getConnectionClientGroup WmTopicConnectionFactory.getClientGroup

setConnectionClientGroup WmTopicConnectionFactory.setClientGroup

getDurableClientGroup WmTopicConnectionFactory.getClientGroup

setDurableClientGroup WmTopicConnectionFactory.setClientGroup

getSessionClientGroup WmTopicConnectionFactory.getClientGroup

setSessionClientGroup WmTopicConnectionFactory.setClientGroup

getSharedState WmTopic.getSharedState




TopicConnectionFactory Client ID Values

JMS 7.1.2 does not use the TopicConnectionFactory ConnectionClientID property. The property has been changed to clientID, as have the accessor methods for that property.

JMS connections do not require a unique clientID; you can use the system default. If you supply your own clientID, the value must be unique. You only need supply your own clientID when you are going to use durable subscribers, where JMS has to distinguish between different connections associated with a particular connection factory.

Library Locations

The table below lists changes to webMethods Broker and JMS JAR file names and locations. You will have to make appropriate changes to the CLASSPATH for stand-alone JMS clients and to settings for application servers used with JMS 7.1.2.

setSharedState WmTopic.setSharedState

getSharedStateOrdering WmTopic.getSharedStateOrdering

setSharedStateOrdering WmTopic.setSharedStateOrdering

getSSLCertificateFilename WmTopicConnectionFactory.getSSLKeystore

setSSLCertificateFilename WmTopicConnectionFactory.setSSLKeystore

getSSLEncrypted WmTopicConnectionFactory.getSSLEncrypted

setSSLEncrypted WmTopicConnectionFactory.setSSLEncrypted

getStrictClientIdConform to JMS specification

setStrictClientId

getSubscriberClientGroup WmTopicConnectionFactory.getClientGroup

setSubscriberClientGroup WmTopicConnectionFactory.setClientGroup

getTcpConnectionSharing Single TCP connection per JMS client

setTcpConnectionSharing Single TCP connection per JMS client

getTemporaryTopicEventType WmTemporaryDestination.getEventType

setTemporaryTopicEventType WmTemporaryDestination.setEventType

6.1 Name and Location 7.1.2 Name and Location

webMethods Broker_directory\lib\BrokerJMS61.jar

webMethods Broker_directory\lib\wmjmsclient.jar

webMethods_directory\common\lib\client61.jar

webMethods Broker_directory\lib\wmbrokerclient.jar




Migrate Integration Server 6.1 Data

Migrate the Integration Server Database Components

After each command you run in this section, make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care.

1 Shut down all Integration Servers that connect to the 6.1 IS Core Audit Log, Cross Reference, and Document History database components.

2 On the machine on which you installed the Database Component Configurator, go to the webMethods_7.1.2_directory\common\db\bin directory and open a command window.

3 Migrate the IS Core Audit Log database component by running this command:

4 Migrate the Cross-Reference database component.

If you are using Oracle or DB2, run this command:

If you are using SQL Server, run this command:

webMethods Broker_directory\lib\jmsnaming61.jar

webMethods Broker_directory\lib\wmjmsnaming.jar

webMethods Broker_directory\lib\jmsadmin61.jar

webMethods Broker_directory\lib\wmjmsadmin.jar

webMethods Broker_directory\lib\g11nutils.jar

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 9

dbConfigurator.{bat|sh} -a migrate -d {oracle|db2luw|db2i}-c crossreference -v latest -l db_server_URL -u existing_db_user -p passwordfv 10

dbConfigurator.bat -a migrate -d sqlserver -c crossreference -v latest-l db_server_URL -u existing_db_user -p password -fv 9

6.1 Name and Location 7.1.2 Name and Location



5 For the Integration Server 7.1.3 release, columns in the Document History database component were changed to solve a character conversion issue with the SQL Server driver. If you are using SQL Server, migrate the Document History database component by running this command:

6 Start Integration Server 7.1.3 and connect the IS Core Audit Log and Document History functions to the migrated database components if they are not already connected. If you are using an external RDBMS (as opposed to the internal database), also connect the Cross Reference function. For instructions, see webMethods Installation Guide 7.1. Then shut down Integration Server 7.1.3.

Migrate the 6.1 Repository Server Data to IS Internal

The Integration Server 6.1 Repository Server has been replaced by a set of database tables collectively called IS Internal. You must migrate Repository Server data to these tables. The migration utility will ask whether you want to migrate to the embedded database that contains the IS Internal database tables (chosen during installation) or an external RDBMS that contains the IS Internal database component (created after installation).

1 Run the migration utility, as follows:

a Go to the Integration Server_7.1.3_directory\bin\migrate directory, open a command window, and run this command:

The migration utility asks whether you are using the embedded database or an external RDBMS. If you are using an external RDBMS but did not supply the connection parameters during installation, the migration utility asks for the connection parameters for the IS Internal database component. If you stored cross-referencing data in the Repository Server, the migration utility also asks for the connection parameters for the Cross Reference database component.

b When the migration utility is finished running, it shows the message “Migration complete” in the command window.

2 If you are using an external RDBMS, data associated with pub.storage services is migrated to the IS_DATASTORE table in the IS Internal database component in the RDBMS. For DB2, the size of a BLOB column is defined when the table is created; you might find that the VALUE column in the IS_DATASTORE table is not wide enough for your pub.storage data. If necessary, use DB2 commands to modify the width.

dbConfigurator.bat -a migrate -d sqlserver -c documenthistory -v latest -l db_server_URL -u existing_db_user -p password -fv 9

migrate.{bat|sh} Integration Server_6.1_directory Integration Server_7.1.3_directory



Migrate Configuration Data and User-Created Packages

1 Go to the Integration Server_6.1_directory\config directory. Copy each of the files listed below that is present in that directory to the Integration Server_7.1.3_directory\config directory:

2 In “Back Up the 6.1 Installation” on page 14, you recorded the name of each package that was associated with a port in Integration Server 6.1. Identify the system packages in that list; system packages usually have the prefix “Wm” and are not user-created packages. For each of the identified system packages, go to the Integration Server_6.1_directory\packages\system_package\config directory and copy the listeners.cnf file to the equivalent Integration Server 7.1.3 directory. If the file already exists in that directory, overwrite the file.

3 If you used the WmDB package in Integration Server 6.5, go to the Integration Server_6.1_backup_directory\packages\WmDB\config directory and copy the jdbc.cnf file to the Integration Server_7.1.3_directory\packages\WmDB\config directory.

4 Copy the user-created-package zip files you created in “Back Up the 6.1 Installation” on page 14 to the Integration Server_7.1.3_directory\replicate\ inbound directory.

5 Go to the Integration Server_6.1_directory\bin directory and open the server.bat or server.sh file in a text editor. Copy the PREPENDCLASSES and APPENDCLASSES lines to the equivalent file in the Integration Server_7.1.3_directory\bin directory.

6 If you are using SSL, copy the server side certificates from the Integration Server 6.1 installation to the corresponding location in the Integration Server 7.1.3 installation.

Configure Integration Server 7.1.3

1 Start Integration Server 7.1.3 and open Integration Server Administrator.

2 Check and re-create ports as follows:

a Go to the SecurityPorts page and make sure all ports other than those associated with reverse invoke, load balancing, and user-created packages were created successfully.

b For HTTPS and FTPS ports, make sure the certificates are at the location specified in the Integration Server 7.1.3 Port Details page.

acllist.cnf aclwrite.cnf server.cnf

aclmap_sm.cnf port.cnf subscribers.cnf

aclread.cnf publishers.cnf users.cnf

acls.cnf remote.cnf

Important! The config directories for some system packages do not get created until after you start Integration Server. If one or more of the config directories you need do not yet exist, create them.



c Using the port information you recorded earlier, re-create the gateway ports and create a Diagnostic port. For detailed instructions, see webMethods Integration Server Administrator’s Guide 7.1.1.

3 Install the 6.1 user-created packages as follows:

a In Integration Server Administrator, go to the PackagesManagementInstall Inbound Releases page.

b In the Release file name list, click a package you want to migrate, and then click Install Release. The Integration Server installs the package and then displays a message that says the package has been installed and activated. Repeat this step for each package you want to migrate.

4 Return to the SecurityPorts page and do the following:

a If you installed packages that have ports associated with them, make sure Integration Server replicated the correct security settings for the port. If necessary, reconfigure the ports with their original security settings.

b For each port associated with a user-created package, click the link in the Access Mode column, then click Reset to default access settings. Integration Server keeps the Deny by Default access mode but populates the Allow List with a group of services that have Anonymous ACL.

5 Configure your Broker connection using the data you recorded in “Back Up the 6.1 Installation” on page 14 and the new SSL connection parameters in Integration Server 7.1.3. For instructions, see webMethods Integration Server Administrator’s Guide 7.1.1.

6 The WmTomcat package uses a global deployment descriptor file named web.xml to specify default configuration settings for all Web applications you deploy on Integration Server. If you modified any settings, copy the file from the Integration Server_6.1_directory\web\conf directory to the Integration Server_7.1.3_directory\ web\conf directory.

7 If you configured LDAP in Integration Server 6.1, reconfigure it in Integration Server 7.1.3 using the data you recorded in “Back Up the 6.1 Installation” on page 14.

Note: webMethods product suite 7.1.2 and 7.1.3 offers a new feature named Central User Management. This feature lets Integration Server authenticate and authorize users and user directories defined in My webMethods Server. If you installed My webMethods Server, Software AG recommends that you configure LDAP directories in My webMethods Server and then configure central users in Integration Server. For instructions, see My webMethods Server Administrator’s Guide 7.1.1 and webMethods Integration Server Administrator’s Guide 7.1.1, respectively.



8 If the Integration Server 7.1.3 is part of a cluster, reconfigure the cluster. For instructions, see webMethods Integration Server Clustering Guide 7.1.1.

9 Reverse Invoke has been replaced by Reverse HTTP Gateway. For instructions on configuring the Reverse HTTP Gateway, see the webMethods Integration Server Administrator’s Guide 7.1.1.

Check Certificates

1 Go to the SecurityCertificates page. Make sure the outbound server certificates exist in the indicated location.

2 Go to the SecurityCertificatesConfigure Client Certificates page. Make sure the client certificates are present in the indicated location. Also make sure the client certificates are mapped to the correct user by checking against the data you recorded in “Back Up the 6.1 Installation” on page 14.

Migrate Trading Networks 6.1 Data

Migrate the Properties File

Migrate your Trading Networks Server 6.1 properties file to your Trading Networks Server 7.1.2 installation as follows:

1 If you are migrating on an IBM i5 system, go to the Integration Server_7.1.3_directory\ packages\WmTN\bin directory, open the setcp.sh file in a text editor, and set the variables listed below as indicated:

Note: The built-in Integration Server load balancer no longer exists in release 7.1.3. If you were using the built-in load balancer, and want to continue using load balancing, switch to a third-party load balancer.

Set this variable... To this directory...

SERVDIR Integration Server_7.1.3_directory

COMMONDIR webMethods_7.1.2_directory/common

WEBMEXT webMethods_7.1.2_directory/common/lib/ext

JDKDIR JVM_or_JDK_directory



2 Go to the Integration Server_7.1.3_directory\packages\WmTN\config\migrate directory, open a command window, and run this command:

Example:

The command creates a properties.cnf file in the Integration Server_7.1.3_directory\ packages\WmTN\config\migrate directory.

3 Move the properties.cnf file to the Integration Server_7.1.3_directory\packages\ WmTN\config directory.

Migrate the Trading Networks Database Components


1 Shut down all 6.1 Integration Servers that connect to the Trading Networks database component.


3 Migrate the Trading Networks database component by running this command:

4 Migrate the Trading Networks Archive database component by running this command:

MigratePropFile.{bat|sh} path_to_6.1_properties_file

MigratePropFile.sh /opt/webMethods/IntegrationServer/packages/WmTN/config/properties.cnf

Note: The migration process converts the date and time stamp for all Trading Networks transactions to Greenwich Mean Time (GMT).

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

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



5 Migrate the Trading Networks data, as follows:

a Start Integration Server 7.1.3 and connect the Trading Networks function to the migrated Trading Networks database component. For instructions, see webMethods Installation Guide 7.1. Then shut down Integration Server 7.1.3.

b Go to the Integration Server_7.1.3_directory\packages\WmTN\bin directory, open the setcp.bat or setcp.sh file in a text editor, and make sure the file points to the JVM you want to use.

c Go to the Integration Server_7.1.3_directory\packages\WmTN\config\migrate directory, open a command window, and run this command:

d Review the command window to make sure the migration was successful. If errors occurred, contact Software AG Customer Care.

Migrate the Certificate

If you are using Trading Networks partner certificates, migrate them by starting Integration Server 7.1.3, opening Integration Server Administrator, and running the wm.tn.admin.migrate:migrateCerts service.

Migrate the tspace Properties

The following Trading Networks properties have been moved from Trading Networks to Integration Server:

migratedata_to_tn_7-1.{bat|sh} 6.1

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.

Old Property New Property Specifies...

tn.tspace.location watt.server.tspace.location Absolute directory path of the hard disk drive space in which the Integration Server is to temporarily store large documents rather than keep them in memory.

tn.tspace.max watt.server.tspace.max Maximum number of bytes that can be stored at any one time in the hard disk drive space that you defined using the watt.server.tspace.location property.



You must move these properties to Integration Server 7.1.3 and rename them, as follows:

1 Shut down Integration Server 7.1.3.

2 Go to the Integration Server 6.1_directory\packages\WmTN\config directory and open the properties.cnf file in a text file.

3 Copy the tn.tspace.location and tn.tspace.max properties to the server.cnf file in the Integration Server_7.1.3_directory\config directory.

4 Rename the properties as shown in the table above.

5 Enable users to view and edit the properties, as follows:

a Start Integration Server 7.1.3 and open Integration Server Administrator.

b Go to the SettingsExtended page. Integration Server Administrator lists the configuration properties specified in the server.cnf file.

c Click Show and Hide Keys and then click the check box for the watt.server.tspace.location and watt.server.tspace.max properties.

d Click Save Changes. Integration Server Administrator lists the properties and their values.

6 Start Integration Server 7.1.3.

Migrate 6.1.5 Business Process Models

Business processes involve two types of data; design-time data (definitions of business process models) and run-time data (in-progress, completed, or failed process instances). You can migrate 6.1.5 design-time data to webMethods product suite 7.1.2 and 7.1.3. In webMethods 6.1, process models were defined and stored in webMethods Modeler 6.1.5. In webMethods product suite 7.1.2 and 7.1.3, process model definitions are defined and stored in webMethods Designer 7.1.2.

1 Open Designer 7.1.2 and choose FileImport.

2 In the import source tree, click webMethodsModeler 6.x process models, then click Next.

3 For Mode, choose one of the following:

If the models were developed on an Integration Server equipped with the Modeler Design Package, click Connect to Design Server. Specify the server address, user, and password for the Design Server.

If the models were developed using Modeler Offline mode, click Offline. Click and then click Browse and go to the Modeler installation directory.

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

5 Click Finish.



6 If you want to see a summary of the import execution, click View Import Log, or go to the workspace\.metadata\plugins\com.process.webmethods.upgrade.impl\ logs directory and open the ModelUpgradeLog.txt file.

7 Generate and upload your 7.1.2 process models. For instructions, see the Designer online help.


2 Migrating from 6.5 to 7.1.2 and 7.1.3 or Designer 7.2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

Back Up the 6.5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47




Migrate webMethods Broker 6.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Migrate JMS 6.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59

Migrate Integration Server 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Migrate Trading Networks 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Migrate 6.5.x Custom Portlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Migrate 6.5.1 Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70

Migrate Optimize 6.5.1 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73



Overview

This upgrade procedure explains how to upgrade your 6.5.x products to webMethods product suite 7.1.2 and 7.1.3 or Designer 7.2, and how to migrate the following:

Data from:

webMethods Broker and JMS 6.5, 6.5.1, or 6.5.2

Integration Server 6.5, 6.5 SP1, 6.5 SP2, or 6.5 SP3

Trading Networks 6.5 or 6.5 SP1

Optimize 6.5.1 SP2 process monitoring data

Custom portlets from webMethods Access or webMethods Portal 6.5.1 or 6.5.2

Business process models and data from webMethods Modeler 6.5.1 and Process Run Time 6.5.1 SP1

You cannot migrate Workflow processes from 6.5 to webMethods product suite 7.1.2 and 7.1.3. Instead, you must re-implement your Workflow 6.5 projects using Designer 7.1.2 or 7.2 and Task Engine 7.1.3.

Important! If you are using Manager Server 6.5.x with Optimize 6.5.1 SP2, you cannot migrate Optimize 6.5.1 SP2 process monitoring data.

In addition, you cannot migrate Manager Server 6.5.1 SP2 data. Instead, you must re-establish your monitoring setup using Infrastructure Data Collector 7.1.2.

Important! You must upgrade all of your products at the same time; you cannot use 6.5 products with 7.1.x or 7.2 products. You must upgrade products and migrate data in the order presented in this chapter.




Back Up the 6.5 Installation

1 Allow all Integration Server guaranteed delivery jobs to finish running. Allow all business processes to finish running or use webMethods Monitor to stop them. Shut down all 6.5 webMethods products and all other applications that are running on the machines on which you are going to install webMethods product suite 7.1.2 and 7.1.3.

2 For each webMethods Broker 6.5 installation, back up your JMS objects and data.

3 Back up the entire 6.5 webMethods installation directory on each machine, and back up your 6.5 webMethods databases as instructed by your RDBMS vendor.

4 For each Integration Server 6.5, do the following:




2 For each port of type HTTPS, Proxy, HTTPS Proxy, SOCK, and SSL SOCK, click the link in the Port column to display the View type Port Details page and print the page.

3 Reverse invoke was rearchitected in Integration Server 7.1.2 and load balancing was removed, so you cannot migrate ports that relate to those features. Delete ports of type Proxy, HTTPS Proxy, SOCK, SSL SOCK,

Registration, Load Balancer, and Diagnostic from the list by clicking in the row for each port.

4 Record the name of the package that is associated with each remaining port.




3 Scroll to the bottom of the page that appears and click Create Release. Integration Server creates a zip file containing the package and places the zip file in the Integration Server_6.5_directory\replicate\outbound directory.



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




e Record your Broker connection by going to the SettingsBrokerEdit page and printing it.

f If you have configured LDAP on the Integration Server, record your LDAP configuration by going to the SecurityUsers & GroupsExternal User Management Configuration page and printing it.



Upgrade Your RDBMSs



1 Go to the documentation area of the Empower Product Support Web site and download webMethods Installation Guide 7.1. Follow the instructions in that guide to install webMethods product suite 7.1.2 and 7.1.3, with these additional guidelines or differences:


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

On the installer’s product selection tree, select the 7.1.2 and 7.1.3 products to install; be sure to select all necessary pieces for each product (see the “Development Installations” chapter in webMethods Installation Guide 7.1).








2 After product installation is complete, create the webMethods product suite 7.1.2 database components that the table below indicates you should create; for instructions, see webMethods Installation Guide 7.1. Do not create database components that the table indicates you should not create; you will migrate the 6.5 database components to 7.1.2 later in this procedure.

Product Action

Trading Networks


Integration Server


webMethods Broker

If you do not want to continue using your 6.5.2 storage, create a Broker Server configuration. The installer requires your webMethods Broker license key to create a Broker Server configuration. Make sure to supply the 7.1.2 license key.

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

Important! If you want to migrate business processes, you must continue using your 6.5.2 storage.

My webMethods Server

Point the database connection at the RDBMS you will use for My webMethods Server 7.1.3 data (see the next bullet, below).

Important! After Integration Server 7.1.3 and Developer 7.1.3 are installed, you will no longer be able to launch Integration Server 6.5 and Developer 6.5 from the Windows Start menu. You will have to launch these products from the command line instead. Go to the Integration Server_6.5_directory\bin directory and run server.bat, and go to the Developer_6.5_directory\bin directory and run developer.bat.



Business processes Do not create the Process Audit Log and Process Engine database components.

Integration Server Do not create the IS Core Audit Log and Document History database components.



If you are not migrating business processes, create the Process Audit Log database component.

If you chose the embedded database during installation, or if you stored 6.5 cross-referencing data in the Cross Reference database component, do not create a Cross Reference database component. If you chose an external RDBMS during installation and want to store 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

Oracle example:

dbConfigurator.bat -a create -d oracle -c storage-v latest-l jdbc:wm:oracle://localhost:1521;ServiceName=ORCL-u webmuser -p webmuser -au admin_user -ap admin_user-t C:\oradata\orcl

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

DB2 for LUW example:

dbConfigurator.bat -a create -d db2luw -c storage-v latest-l jdbc:wm:db2://localhost:50000;databaseName=webm_db-u webmuser -p webmuser -au admin_user -ap admin_user-t C:\DB2\Data\


Create the My webMethods Server database component.





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




Optimize If you are using Manager Server 6.5.x with Optimize 6.5.1 SP2, create the Analysis and Process Tracker database components.

If you are not using Manager Server 6.5.x with Optimize 6.5.1 SP2, do not create the Analysis and Process Tracker database components.














Migrate webMethods Broker 6.5.2


7.1.2 Broker Servers and 6.5.2 Broker Clients

7.1.2 Broker Servers are compatible with these 6.5.2 Broker clients:

6.5.2 Command-line utilities

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

6.5.2 Broker Servers and 7.1.2 Broker Clients

6.5.2 Broker Servers are compatible with these 7.1.2 Broker clients:

7.1.2 Broker and JMS user interface on My webMethods Server

7.1.2 command-line utilities

7.1.2 Broker Client C and Java APIs

Set Up the 7.1.2 Broker Server

If you chose not to continue using your 6.5.2 storage, you created a 7.1.2 Broker Server configuration during installation. You must now migrate the 6.5.2 metadata to the 7.1.2 Broker Server storage. If you do not have gateways and territories, see “Migrate if You Do Not Have Gateways and Territories” on page 53. If you have gateways and territories, see “Migrate if You Have Gateways and Territories” on page 54.

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



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.2 Broker Server to the 7.1.2 Broker Server if you do not have gateways and territories.


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



b Click the Export tab, select the check box next to the 6.5.2 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:



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

4 Click Apply.

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



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


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

4 Your 6.5.2 Broker Server SSL configuration was not imported. If you are using SSL, convert your SSL keystores to the correct format and configure SSL, including ACLs, for the 7.1.2 Broker Server. For instructions, see webMethods Broker Administrator’s Guide 7.1.



Migrate if You Have Gateways and Territories

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


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

a In My webMethods, go to the AdministrationMessagingBroker TerritoriesTerritories 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.2 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:



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 AdministrationMessagingBroker ServersServers page and stop all 6.5.2 Broker Servers. Refresh the page and make sure the Broker Servers no longer appear on the list.

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

a In My webMethods, go to the AdministrationMessagingBroker TerritoriesTerritories page.

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


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

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 webMethods Broker Administrator’s Guide 7.1.

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

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

7 Your 6.5.2 Broker Server SSL configuration was not imported. If you are using SSL, convert your SSL keystores to the correct format and configure SSL, including ACLs, for the 7.1.2 Broker Server. For instructions, see webMethods Broker Administrator’s Guide 7.1.

Configure the 7.1.2 Broker Server to Use 6.5.2 Storage

Use this procedure if you want to continue using your 6.5.2 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 a 7.1.2 Broker Server and configure it to use the 6.5.2 storage. The procedure also removes the 6.5.2 Broker Server from the 6.5.2 Broker Monitor startup configuration and adds it to the 7.1.2 Broker Monitor startup configuration.

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

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

3 Back up the 6.5.2 awbrokermon.cfg file.

4 Remove the 6.5.2 Broker Server from the 6.5.2 Broker Monitor startup configuration by going to the webMethods Broker_6.5.2_directory\bin directory and running the command below. If any part of the data directory path contains a space, enclose the entire path in quotes.

System awbrokermon.cfg File Location

Windows c:\WINDOWS\webmethods

UNIX /var/opt/webmethods6

server_config remove full_path_to_6.5.2_data_directory



5 Create the 7.1.2 Broker Server and configure it to use the 6.5.2 storage by going to the webMethods Broker_7.1.2_directory/bin directory and running the command below. If any part of the data directory path contains a space, enclose the entire path in quotes.

6 Make sure the 6.5.2 storage is running under the 7.1.2 Broker Server:

7 If you are using SSL, convert your keystores to the correct format. For instructions, see webMethods Broker Administrator’s Guide 7.1.

System Example

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

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

Important! For license_key, supply your 7.1.2 webMethods Broker license key.

server_config add full_path_to_6.5.2_data_directory -k license_key -p port

System Example

Windows server_config add c:\webmethods6\Broker\data\awbrokers\default-k WLRS8X-E073106-S000-KH-C10100-2SBR-N4NMPX -p 6871

UNIX server_config add /var/opt/webmethods6/awbrokers/default-k WLRS8X-E073106-S000-KH-C10100-2SBR-N4NMPX -p 6871

System Steps

Windows 1

2

3

Open the Windows Services window.

Make sure the status of the webMethods Broker Server 7.1 (port) service is Started.

Right-click the service and click Properties. Make sure the value in the Path to Executable field points to the awbroker file for 7.1.2.

UNIX 1 Enter this command:

ps -ef | grep aw

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

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



Migrate Java Clients

If you want to migrate Java clients that use SSL to 7.1.2, 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

Broker Java API Changes

Changed Methods in BrokerConnectionDescriptor Class

Command 7.1.2 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_create

Changed ID options

broker_delete

broker_load

broker_save

broker_buildall

broker_ping

broker_status

server_conf_backup

server_conf_restore

6.5.2 Method 7.1.2 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)



New Methods in BrokerConnectionDescriptor Class

getSSLKeystore()

getSSLKeystoreType()

getSSLTruststore()

getSSLTruststoreType()

New Methods in BrokerServerClient Class

startServerProcess(String Broker Monitor_host,int Broker Monitor_port,int Broker_port)

getServerProcessRunStatus(String Broker Monitor_host,int Broker Monitor_port,int Broker_port)

setSSLConfigV2(COM.activesw.api.client.BrokerSSLConfigV2 new_config)

getActiveSSLConfigV2()

getSavedSSLConfigV2()

getActiveSSLIdentity()

getSavedSSLIdentity()

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)

6.5.2 Method 7.1.2 Method



Migrate C Clients

If you want to migrate C clients that use SSL to 7.1.2, you must modify the way SSL connections are created in your C source code to reflect the Broker C API changes that are documented below. These API changes are consistent with the 7.1.2 Broker Server SSL configuration. For complete information on the 7.1.2 Broker Server SSL configuration, see webMethods Broker Administrator’s Guide 7.1.

Changed Methods

These methods have been changed to accept the truststore file instead of the distinguished name:

awGetDescriptorSSLCertificate

awSetDescriptorSSLCertificate

awGetSSLCertificate

For more information, see webMethods Broker Client C API Programmer’s Guide 7.1.2.

Removed Methods

These methods have been removed:

awGetSSLCertificateDns

awGetSSLRootDns

Migrate JMS 6.5.2


6.5.2 JMS clients can run on 7.1.2 Broker Servers.

The SSL keystore format changed in release 7.1. If you have been using Spyrus keystore files, you must migrate your keystores to the new format and bind the new location of the keystore and truststore in your Connection Factories. For instructions, see webMethods Broker Administrator’s Guide 7.1.



Update JMSAdmin Scripts

Use the tables in this section to update the commands in your 6.5.2 JMSAdmin scripts to be correct for 7.1.2.

JMSAdmin Command Changes

Command 7.1.2 Modification

Create DurableSubscriber

Changed SSL parameters

Create Queue



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

PriorityOrdering

Queue PriorityOrdering



Convert JMS Client APIs

Use the tables in this section to convert the indicated JMS API methods from 6.5.2 to 7.1.2.

Changed Method in WmJMSAdminFactory Class

Change this 6.5.2 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 7.1.2 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 7.1.2. 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

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



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

Migrate Integration Server 6.5

Migrate Configuration Data and User-Created Packages

1 Go to the Integration Server_6.5_directory\config directory. Copy each of the files listed below that is present in that directory to the Integration Server_7.1.3_directory\config directory:

2 In “Back Up the 6.5 Installation” on page 47, you recorded the name of each package that was associated with a port in Integration Server 6.5. Identify the system packages in that list; system packages usually have the prefix “Wm” and are not user-created packages. For each of the identified system packages, go to the Integration

6.5.2 Name and Location 7.1.2 Name and Location

webMethods_directory\common\lib\wmjmsclient.jar

webMethods Broker_directory\lib\wmjmsclient.jar

webMethods_directory\common\lib\wmbrokerclient.jar

webMethods Broker_directory\lib\wmbrokerclient.jar

webMethods Broker_directory\lib\g11nutils.jar

acllist.cnf port.cnf users.cnf

aclmap_sm.cnf publishers.cnf configPassman.cnf

aclread.cnf remote.cnf passman.cnf

acls.cnf server.cnf empw.dat

aclwrite.cnf subscribers.cnf txnPassStore.dat



Server_6.5_directory\packages\system_package\config directory and copy the listeners.cnf file to the equivalent Integration Server 7.1.3 directory. If the file already exists in that directory, overwrite the file.

3 If you used the WmDB package in Integration Server 6.5, go to the Integration Server_6.5_backup_directory\packages\WmDB\config directory and copy the jdbc.cnf file to the Integration Server_7.1.3_directory\packages\WmDB\config directory.

4 Copy the user-created-package zip files you created in “Back Up the 6.5 Installation” on page 47 to the Integration Server_7.1.3_directory/replicate/ inbound directory.

5 Go to the Integration Server_6.5_directory\bin directory and open the server.bat or server.sh file in a text editor. Copy the PREPENDCLASSES and APPENDCLASSES lines to the equivalent file in the Integration Server_7.1.3_directory\bin directory.

6 If you are using SSL, copy the server side certificates from the Integration Server 6.5 installation to the corresponding location in the Integration Server 7.1.3 installation.

Migrate the 6.5 Repository Server Data to IS Internal

The Integration Server 6.5 Repository Server has been replaced by a set of database tables collectively called IS Internal. You must migrate Repository Server data to these tables. The migration utility will ask whether you want to migrate to the embedded database that contains the IS Internal database tables (chosen during installation) or an external RDBMS that contains the IS Internal database component (created after installation).

1 Run the migration utility, as follows:

a Go to the Integration Server_7.1.3_directory\bin\migrate directory, open a command window, and run this command:

The migration utility asks whether you are using the embedded database or an external RDBMS. If you are using an external RDBMS but did not supply the connection parameters during installation, the migration utility asks for the connection parameters for the IS Internal database component. If you stored cross-referencing data in the Repository Server, the migration utility also asks for the connection parameters for the Cross Reference database component.

b When the migration utility is finished running, it shows the message “Migration complete” in the command window.

Important! The config directories for some system packages do not get created until after you start Integration Server. If one or more of the config directories you need do not yet exist, create them.

Important! Do not start Integration Server 7.1.3 at this point. You must migrate the Repository Server data before starting Integration Server, or unpredictable results might occur.

migrate.{bat|sh} Integration Server_6.5_directory Integration Server_7.1.3_directory



2 If you are using an external RDBMS, data associated with pub.storage services is migrated to the IS_DATASTORE table in the IS Internal database component in the RDBMS. For DB2, the size of a BLOB column is defined when the table is created; you might find that the VALUE column in the IS_DATASTORE table is not wide enough for your pub.storage data. If necessary, use DB2 commands to modify the width.

Configure Integration Server 7.1.3

1 Start Integration Server 7.1.3 and open Integration Server Administrator.

2 Check and re-create ports as follows:

a Go to the SecurityPorts page and make sure all ports other than those associated with reverse invoke, load balancing, and user-created packages were created successfully.

b For HTTPS and FTPS ports, make sure the certificates are at the location specified in the Integration Server 7.1.3 Port Details page.

c Using the port information you recorded earlier, re-create the gateway ports and the Diagnostic port. For detailed instructions, see webMethods Integration Server Administrator’s Guide 7.1.1.

3 Install 6.5 user-created packages as follows:

a In Integration Server Administrator for Integration Server 7.1.3, go to the PackagesManagementInstall Inbound Releases page.

b In the Release file name list, click a package you want to migrate, and then click Install Release. The Integration Server installs the package and then displays a message that says the package has been installed and activated. Repeat this step for each package you want to migrate.

4 Return to the SecurityPorts page and do the following:

a If you installed packages that have ports associated with them, make sure Integration Server replicated the correct security settings for the port. If necessary, reconfigure the ports with their original security settings.

b For each port associated with a user-created package, click the link in the Access Mode column, then click Reset to default access settings. Integration Server keeps the Deny by Default access mode but populates the Allow List with a group of services that have Anonymous ACL.

5 Configure your Broker connection using the data you recorded in “Back Up the 6.5 Installation” on page 47 and the new SSL connection parameters in Integration Server 7.1.3. For instructions, see webMethods Integration Server Administrator’s Guide 7.1.1.

6 The WmTomcat package uses a global deployment descriptor file named web.xml to specify default configuration settings for all Web applications you deploy on Integration Server. If you modified any settings, copy the file from the Integration Server_6.5_directory\web\conf directory to the Integration Server_7.1.3_directory\ web\conf directory.



7 If you configured LDAP in Integration Server 6.5, reconfigure it in Integration Server 7.1.3 using the data you recorded in “Back Up the 6.5 Installation” on page 47.

8 If the Integration Server 7.1.3 is part of a cluster, reconfigure the cluster. For instructions, see webMethods Integration Server Clustering Guide 7.1.1.

9 Reverse Invoke has been replaced by Reverse HTTP Gateway. For instructions on configuring the Reverse HTTP Gateway, see webMethods Integration Server Administrator’s Guide 7.1.1.

Check Certificates

1 Go to the SecurityCertificates page. Make sure the outbound server certificates exist in the indicated location.

2 Go to the SecurityCertificatesConfigure Client Certificates page. Make sure the client certificates are present in the indicated location. Also make sure the client certificates are mapped to the correct user by checking against the data you recorded in “Back Up the 6.5 Installation” on page 47.

Migrate the Integration Server Database Components


1 Shut down all Integration Servers that connect to the 6.5 IS Core Audit Log, Cross Reference, and Document History database components.


Note: webMethods product suite 7.1.2 and 7.1.3 offers a new feature named Central User Management. This feature lets Integration Server authenticate and authorize users and user directories defined in My webMethods Server. If you installed My webMethods Server, Software AG recommends that you configure LDAP directories in My webMethods Server and then configure central users in Integration Server. For instructions, see My webMethods Server Administrator’s Guide 7.1.1 and webMethods Integration Server Administrator’s Guide 7.1.1, respectively.

Note: The built-in Integration Server load balancer no longer exists in release 7.1.3. If you were using the built-in load balancer, and want to continue using load balancing, switch to a third-party load balancer.



3 If you are migrating from Integration Server 6.5 or 6.5 SP1, migrate the IS Core Audit Log database component by running this command:

If you are migrating from Integration Server 6.5 SP2 or 6.5 SP3, migrate the IS Core Audit Log database component by running this command:

4 Migrate the Cross Reference database component by running this command:

5 Start Integration Server 7.1.3 and connect the IS Core Audit Log, Cross Reference, and Document History functions to the migrated database components if they are not already connected. For instructions, see webMethods Installation Guide 7.1. Then restart Integration Server 7.1.3.

Migrate Trading Networks 6.5

Migrate the Trading Networks Properties File

1 If you are migrating on an IBM i5 system, go to the Integration Server_7.1.3_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_7.1.3_directory\packages\WmTN\config\migrate directory, open a command window, and run this command:



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

Set this variable... To this directory...

SERVDIR Integration Server_7.1.3_directory

COMMONDIR webMethods_7.1.2_directory/common

WEBMEXT webMethods_7.1.2_directory/common/lib/ext

JDKDIR JVM_or_JDK_directory

MigratePropFile.{bat|sh} path_to_6.5_properties_file



For example:

The command creates a properties.cnf file in the Integration Server_7.1.3_directory\ packages\WmTN\config\migrate directory.

3 Move the properties.cnf file to the Integration Server_7.1.3_directory\packages\ WmTN\config directory.

Migrate the Trading Networks Database Components

1 Shut down all 6.5 Integration Servers that connect to the Trading Networks database component.

2 If you applied TNS_6-5_Fix57 to Trading Networks 6.5, do the following:

a Go to the webMethods_directory/common/db/scripts/database_type/ tradingnetworks/migrate/20_to_25 directory.

b Open the database_type_tns_m_20_to_25.sql script in a text editor.

c Comment out the Alter table REMOTE section.

d Save and close the script.


4 Migrate the Trading Networks database component by running this command:

Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.1.2_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care.

5 Migrate the Trading Networks Archive database component by running this command:

MigratePropFile.sh /opt/webMethods/IntegrationServer/packages/WmTN/config/properties.cnf

Note: The migration process converts the date and time stamp for all Trading Networks data to Greenwich Mean Time (GMT).


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




6 Migrate the Trading Networks data, as follows:

a Start Integration Server 7.1.3 and connect the Trading Networks function to the migrated Trading Networks database component. For instructions, see webMethods Installation Guide 7.1. Then shut down Integration Server 7.1.3.

b Go to the Integration Server_7.1.3_directory\packages\WmTN\bin directory, open the setcp.bat or setcp.sh file in a text editor, and make sure the file points to the JVM you want to use.

c Go to the Integration Server_7.1.3_directory\packages\WmTN\config\migrate directory, open a command window, and run this command:

d Review the command window to make sure the migration was successful. If errors occurred, contact Software AG Customer Care.

7 Start Integration Server 7.1.3.

Migrate 6.5.x Custom Portlets

1 Identify the directory that contains the custom portlets developed using Access or Portal 6.5.x.

2 Copy the portlets to the My webMethods Server_7.1.3_directory/server/server/deploy directory.

3 Start My webMethods Server 7.1.3.

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.

Note: Software AG cannot control the contents of custom portlets. If a custom portlet contains items that the upgrade scripts were not designed to handle, they might not deploy successfully.



Migrate 6.5.1 Business Processes

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

If you want to start new instances of migrated 6.5.1 process models in your 7.1.2 installation, do not have any running 6.5.1 process instances, and do not need to resubmit any 6.5.1 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.1. In webMethods product suite 7.1.2 and 7.1.3, process models are defined and stored in Designer 7.1.2 or 7.2.

If you want to finish 6.5.1 process instances that are already in progress or resubmit 6.5.1 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.1 business process models and in progress, completed, or failed 6.5.1 process instances that is stored in the Process Audit Log database component and, if you used it, the Process Tracking Store database component.

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

Migrate Design-Time Data

1 Open Designer 7.1.2 or 7.2 and choose FileImport.

2 In the import source tree, click webMethodsModeler 6.x process models, then click Next.

3 For Mode, choose one of the following:

If the models were developed on an Integration Server equipped with the Modeler Design Package, click Connect to Design Server. Specify the server address, user, and password for the Design Server.

If the models were developed using Modeler Offline mode, click Offline. Click and then click Browse and go to the Modeler installation directory.

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

5 Click Finish.

6 If you want to see a summary of the import execution, click View Import Log, or go to the workspace\.metadata\plugins\com.process.webmethods.upgrade.impl\ logs directory and open the ModelUpgradeLog.txt file.

7 Generate and upload your process models. For instructions, see the Designer online help.



Migrate Run-Time Data

Start the Migration

1 If you have not yet migrated webMethods Broker to 7.1.2, do so now. For instructions, see “Migrate webMethods Broker 6.5.2” on page 52, and make sure you follow the instructions in “Configure the 7.1.2 Broker Server to Use 6.5.2 Storage” on page 55. Also make sure the 6.5.2 Broker used by your 6.5.1 Process Engines has the same name in 7.1.2 that it had in 6.5.2.

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

3 Migrate the Integration Server 6.5 packages that contain the triggers and generated process artifacts for the process models as described below. Each package is named using the project name or the custom-generated package name you specified.

a In Integration Server Administrator for Integration Server 6.5, archive each

package by clicking in the Archive column. By default, archiving creates a file named package.zip.

b Copy the packages from the Integration Server_6.5_directory\replicate\outbound directory to the Integration Server_7.1.3_directory\replicate\inbound directory.

c Install the packages on Integration Server 7.1.3, as follows:

1 In Integration Server Administrator for Integration Server 7.1.3, go to the PackagesManagementInstall Inbound Releases page.

2 In the Release file name list, click one of the packages you archived and copied.

3 Clear the Activate upon installation check box.

4 Click Install Release.

5 Repeat these steps for all the packages you copied.

4 Prevent new instances of 6.5.1 process models from starting by shutting down all 6.5 Integration Servers that host Process Engines.

Migrate the Database Components

1 Shut down all 6.5 Integration Servers that connect to the Process Audit Log and Process Tracking Store database components.


Note: The steps in this section are the same whether you migrated your design-time data to Designer 7.1.2 or 7.2.



Migrate the Process Audit Log Database Component

1 If you are using DB2 for Linux, UNIX, Windows, do the following:

a Go to the webMethods_directory/common/db/scripts/db2/processaudit/migrate/ 9to10 directory.

b Execute the db2_pra_m_9_to_10_migrate.sql script.

c Execute the db2_pra_m_dml_tracking.sql script.

2 For all RDBMSs, run this command:




Migrate the Process Tracking Store Database Component

1 If you are using DB2 for Linux, UNIX, Windows, do the following:

a Go to the webMethods_directory/common/db/scripts/db2/processengine/migrate/ 9to10 directory.

b Execute the db2_pre_m_9_to_10_migrate.sql script.

c Execute the db2_pre_m_dml_tracking.sql script.

Note: Your database editor might prompt you to supply the right delimiter.

DbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw}-c processaudit -v 20 -l db_server_URL -u existing_db_user -p password -fv 10

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

Note: In webMethods product suite 7.1.2 and 7.1.3, the Process Tracking Store database component has been renamed the Process Engine database component.

Note: Your database editor might prompt you to supply the right delimiter.







Complete the Migration

1 Start Integration Server 7.1.3 and connect the Process Audit Log and Process Engine functions to the migrated database components. For instructions, see webMethods Installation Guide 7.1. The instructions say to restart Integration Server, but do not do so yet.

2 In Integration Server Administrator for Integration Server 7.1.3, go to the PackagesManagement page. Click Active Inactive Packages and activate the packages you archived and copied to Integration Server 7.1.3 in “Start the Migration” on page 71.

3 Restart Integration Server 7.1.3.

4 Enable document retrieval for all triggers on Integration Server 7.1.3. For instructions, see webMethods Integration Server Administrator’s Guide 7.1.1.

Migrate Optimize 6.5.1 SP2

To migrate Optimize process monitoring data from 6.5.1 SP2 to 7.1.2, you must do the following:

Migrate from Optimize 6.5 SP2 to Optimize 7.0 SP2, including starting the Optimize 7.0 SP2 Analytic Engine.

Migrate from Optimize 7.0 SP2 to Optimize 7.1.2.

dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2luw}-c processengine -v 20 -l db_server_URL -u existing_db_user -p password-fv 10

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

Important! Use this procedure only if you are using Optimize 6.5.1 SP2 without Manager Server 6.5.x. If you are using Manager Server 6.5.x with Optimize 6.5.1 SP2, you cannot migrate Optimize process monitoring data.



Migrate Optimize 6.5 SP2 to Optimize 7.0 SP2

Install Optimize 7.0 SP2

Using the instructions in webMethods Installation Guide 7.0 SP2, do the following:

1 Install the following in a new webMethods directory:

Optimize 7.0 SP2 Analytic Engine

Database Scripts build 7.0.0.2.52

My webMethods Server 7.0 SP2 with the Central Configuration user interface

2 Create the 7.0 SP2 My webMethods Server and Process Audit Log database components in a separate schema.

3 Configure and start My webMethods Server 7.0 SP2. For instructions, see My webMethods Server Administrator’s Guide 7.0 SP2.

Transform Data

For detailed instructions on each of the steps below, see webMethods Optimize Central Configuration and Deployment Guide 7.0.

1 Create a configuration for Analytic Engine 7.0 SP2. Make sure the JDBC pools for Analysis and Process Tracker point to the 6.5.1 SP2 schemas. Make sure the JDBC pool for Process Audit Log points to the 7.0 SP2 schema.

2 Deploy the configuration to a file. The file name is DeployedEnvironment.zip.

3 Go to the Analytic Engine host machine and extract the DeployedEnvironment.zip file to any directory.

4 Go to the extraction_directory\host\Analytic Engine\config directory. Copy the contents of that directory over the contents of the Optimize_7.0 SP2_directory\ analysis\conf directory.

5 Configure the Password Administrator Utility and transfer logical server passwords.

Note: These database components are used only temporarily. They do not need to contain any data from the 6.5.1 installation.



6 If you are using an HP-UX PA-RISC system, go to the Optimize_7.0 SP2_directory\ optimize\analysis\bin directory, open the preMigrationRules.sh script in a text editor, and replace the contents of the file with the following:

7 Extract 6.5.1 SP2 rules from the Analysis database component to the file system. Go to the Optimize_7.0 SP2_directory\optimize\analysis\bin directory and run the preMigrateRules.{bat|sh} script as shown below.

#!/bin/sh## ---------------------------------------------------------------## $Id: //bpodepot/optimize/huttSP2/bin/analysis/preMigrateRules.sh#3 $## $DateTime: 2007/04/12 14:24:04 $## $Revision: #3 $## ---------------------------------------------------------------args1=$1args2=$2args3=$3args4=$4

. ./kenobiEnv.sh

# Configure JAVA executableif [ -z "${JAVA_HOME}" ] ; then echo "JAVA_HOME environment variable not set. Unable to continue." exit 1fi# Check to make sure all environment variables are correctif [ -z "${OPTIMIZE_ANALYSIS_HOME}" ] ; then echo "OPTIMIZE_ANALYSIS_HOME environment variable not set. Unable to continue." exit 1fi

CLASSPATH=${OPTIMIZE_ANALYSIS_HOME}/bin/opt65.jarCLASSPATH=${CLASSPATH}:${OPTIMIZE_ANALYSIS_HOME}/lib/sl53_cj36.jarCLASSPATH=${CLASSPATH}:${OPTIMIZE_ANALYSIS_HOME}/lib/glue.jarexport CLASSPATH

$JAVA_HOME/bin/java -Doptimize.home.path=$OPTIMIZE_ANALYSIS_HOME com.dante.analysis.rules.RuleXMLTranslator $arg1 $arg2 $arg3 $arg4

RDBMS Command

Oracle preMigrateRules.{bat|sh} "jdbc:wm:oracle://host:{1521|port};serviceName=service" existing_db_user password com.wm.dd.jdbc.oracle.OracleDriver

SQL Server

preMigrateRules.bat "jdbc:wm:sqlserver://host:{1433|port};databaseName=database" existing_db_user passwordcom.wm.dd.jdbc.sqlserver.SQLServerDriver


preMigrateRules.{bat|sh} "jdbc:wm:db2://host:{50000|port};databaseName=database;AlternateId=schema;showSelectableTables=false" existing_db_user password com.wm.dd.jdbc.db2.DB2Driver



Migrate the Analysis and Process Tracker Database Components

After each command you run in this section, make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_7.0_directory\common\ db\logs directory. If errors occurred, contact Software AG Customer Care.

Create Storage and Grant Privileges

You must create storage in the same databases that host the 6.5.1 SP2 Analysis and Process Tracker database components, and then migrate the data from the 6.5.1 SP2 database components to the new storage. You must also grant privileges to the data. If you install the Analysis and Process Tracker database components in the same schema, you can use the same storage for both. For instructions, see webMethods Installation Guide 7.0 SP2.

On the machine on which you installed Database Scripts, go to the webMethods_7.0_directory\common\db\bin directory, open a command window, and run the command below for each schema to create storage and grant privileges:

Prepare DB2 for Linux, UNIX, Windows

If you are migrating database components in DB2 for Linux, UNIX, Windows, run the command below for each schema:

Example:

dbInstaller.{bat|sh} create {oracle|mssql|db2udb}storage latest db_server_URL db_admin_user password existing_db_user password {full_path_to_new_tablespace_directory|database_name}

dbInstaller.{bat|sh} create db2udb componenttracker latestdb_server_URL existing_db_user password

dbInstaller.sh create db2udb componenttracker latest"jdbc:wm:db2://localhost:50000;databaseName=S651SP2;AlternateId=COMPONENTTRACKER651SP2;InitializationString=SET CURRENT PATH=current_path,COMPONENTTRACKER651SP2" userid userpwd



Migrate the Analysis Database Component

You might have the Optimize 6.5.1 SP2 database components Analysis and Process Tracker in separate schemas or in the same schema. If you installed Analysis and Process Tracker in different schemas, they each have a supporting Operation Management database component. If you installed Analysis and Process Tracker in the same schema, they share a single Operation Management database component.

1 Migrate the Operation Management database component by running this command:

2 Install the Distributed Locking database component:

Example:

3 Migrate the Analysis database component.

a Run this command:

b Go to the Optimize_7.0 SP2_directory/analysis/bin directory and run the migrate65to70.{bat|sh} script. The script writes execution information to the Optimize_7.0 SP2_directory/analysis/log directory.

c Run this command:

Migrate the Process Tracker Database Component

1 If the Process Tracker database component was in a different schema than Analysis, migrate Operation Management by running this command:

2 Migrate the Process Tracker database component by running this command:

dbInstaller.{bat|sh} migrate {oracle|mssql|db2db2}operationmanagement 15 db_server_URL existing_db_user password 10

dbInstaller.{bat|sh} create {oracle|mssql|db2udb}distributedlocking latest db_server_URL existing_db_user password

dbInstaller.bat create mssql distributedlocking latest jdbc:wm:sqlserver://localhost:1433;databaseName=analysis651SP2dbanalysisuser analysispwd

dbInstaller.{bat|sh} migrate {oracle|mssql|db2udb}analysis 23 db_server_URL existing_db_user password 10

dbInstaller.{bat|sh} migrate {oracle|mssql|db2udb} analysis 25db_server_URL existing_db_user password 24

dbInstaller.{bat|sh}migrate {oracle|mssql|db2udb}operationmanagement 15 db_server_URL existing_db_user password 10

dbInstaller.{bat|sh} migrate {oracle|mssql|db2luw}processtracker 25 db_server_URL existing_db_user password 10



Start the 7.0 SP2 Analytic Engine

Start the 7.0 SP2 Analytic Engine.

Drop the 7.0 SP2 Database Components

Drop the 7.0 SP2 My webMethods Server and Process Audit Log database components you created in “Install Optimize 7.0 SP2” on page 74.

Migrate Optimize 7.0 SP2 to Optimize 7.1.2

Perform the tasks in this section using the 7.1.2 products you installed earlier in this procedure. Use the 7.1.2 My webMethods Server database component. If you migrated business processes, use the migrated Process Audit Log database component; if you did not migrate business processes, use the 7.1.2 Process Audit Log database component.

Define Rule Alerts

If you defined rule alerts in Optimize 6.5.1 SP2, make sure the users that were assigned to receive these alerts are defined in My webMethods 7.1.3. For instructions, see My webMethods Server Administrator's Guide 7.1.1.

Migrate the Analysis and Process Tracker Database Components


2 Migrate the Analysis database component by running this command:



dbConfigurator.{bat|sh} -a migrate -d {oracle|sqlserver|db2udb}-c analysis -v latest -l db_server_URL -u existing_db_user -p password -fv 25

Note: When you start the Analytic Engine after completing the migration tasks in this section, the engine will perform the final migration of Analysis data.

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




Create a New Environment

For detailed instructions for these steps, see webMethods Central Configuration and Deployment Guide 7.1.

1 Create a new Optimize 7.1.2 environment and configure it like the Optimize 6.5.1 SP2 environment from which you are upgrading. Map the database pools to your database components as follows:

2 Start the Optimize 7.1.2 engines.

3 Deploy the Optimize 7.1.2 environment.

Map these database pools... To these database components...

Analysis and Process Tracker

Analysis and Process Tracker database components you migrated.

Process Audit Log If you migrated business processes, map to the Process Audit Log database component you migrated.

If you did not migrate business processes, map to the new 7.1.2 Process Audit Log database component.

My webMethods Server 7.1.2 My webMethods Server database component.

Note: For My webMethods Server 7.1.3, the database component is still 7.1.2.


3 Migrating from Fabric 7 to 7.1.2 or Designer 7.2

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

Back Up the Fabric 7 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83




Migrate webMethods Broker and JMS 6.5.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Migrate Integration Server 6.5 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

Migrate Trading Networks 6.5 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Migrate My webMethods Server 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88

Migrate 7.0 SP2 Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89

Migrate 7.0 SP2 Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Complete the Metadata Library 7.0 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Migrate Optimize 7.0 SP2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Complete the Deployer 7.0 Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99



Overview

This upgrade procedure explains how to upgrade your Fabric 7 products to webMethods product suite 7.1.2 and 7.1.3 or Designer 7.2, and how to migrate the following:

Data from:

webMethods Broker and JMS 6.5.2

Integration Server 6.5 SP2 or SP3

Trading Networks 6.5 or 6.5 SP1

My webMethods Server 7.0 SP2

Deployer 7.0

Optimize 7.0 SP2 process monitoring data

Custom portlets from Designer 7.0 SP2 and My webMethods Server 7.0 SP2

Business process models and data from Designer 7.0 SP2 and Process Engine 7.0 SP2

Task applications from My webMethods Server 7.0 SP2 and Task Engine 7.0 SP2

Important! If you are using Infrastructure Data Collector 7.0 SP2 with Optimize 7.0 SP2, you cannot migrate Optimize process monitoring data.

In addition, you cannot migrate Infrastructure Data Collector 7.0 SP2 data. Instead, you must re-establish your monitoring setup using Infrastructure Data Collector 7.1.2.

Important! You must upgrade all of your products at the same time; you cannot use Fabric 7 products with 7.1.x or 7.2 products. You must upgrade products and migrate data in the order presented in this chapter.




Back Up the Fabric 7 Installation

1 Allow all Integration Server guaranteed delivery jobs to finish running. Allow all business processes to finish running or use webMethods Monitor to stop them. Shut down all Fabric 7 products and all other applications that are running on the machines on which you are going to install webMethods product suite 7.1.2 and 7.1.3.

2 For each webMethods Broker 6.5 installation, back up your JMS objects and data.

3 Back up the entire Fabric 7 installation directory on each machine, and back up your Fabric 7 databases as instructed by your RDBMS vendor.

4 For each Integration Server 6.5 SP2, do the following:




2 For each port of type HTTPS, Proxy, HTTPS Proxy, SOCK, and SSL SOCK, click the link in the Port column to display the View type Port Details page and print the page.

3 Reverse invoke was rearchitected in Integration Server 7.1.2 and load balancing was removed, so you cannot migrate ports that relate to those features. Delete ports of type Proxy, HTTPS Proxy, SOCK, SSL SOCK,

Registration, Load Balancer, and Diagnostic from the list by clicking in the row for each port.

4 For each remaining port, record the package with which the port is associated.




3 Scroll to the bottom of the page that appears and click Create Release. Integration Server creates a zip file containing the package and places the zip file in the Integration Server_6.5 SP2_directory\replicate\outbound directory.







e Record your Broker connection by going to the SettingsBrokerEdit page and printing it.

f If you have configured LDAP on the Integration Server, record your LDAP configuration by going to the SecurityUsers & GroupsExternal User Management Configuration page and printing it.



Upgrade Your RDBMSs



Go to the documentation area of the Empower Product Support Web site and download webMethods Installation Guide 7.1. Follow the instructions in that guide to install webMethods product suite 7.1.2 and 7.1.3, with these additional guidelines or differences:


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

On the installer’s product selection tree, select the 7.1.2 and 7.1.3 products to install; be sure to select all necessary pieces for each product (see the “Development Installations” chapter in webMethods Installation Guide 7.1). If you are upgrading My webMethods Server, also select Deployer 7.1.2.








and 7

After product installation is complete, create the webMethods product suite 7.1.2 database components that the table below indicates you should create; for instructions, see webMethods Installation Guide 7.1. Do not create database components that the table indicates you should not create; you will migrate the Fabric 7 database components to 7.1.2 later in this procedure.

Product Action

Trading Networks


Integration Server


Metadata Library Point the database connection at the RDBMS you will use for Metadata Library 7.1.1 data.

webMethods Broker

If you do not want to continue using your 6.5.2 storage, create a Broker Server configuration. The installer requires your webMethods Broker license key to create a Broker Server configuration. Make sure to supply the 7.1.2 license key.

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

Important! If you want to migrate business processes, you must continue using your 6.5.2 storage.


Point the database connection at the RDBMS you will use for My webMethods Server 7.1.3 data (see the next bullet, below).

Important! After Integration Server 7.1.3 and Developer 7.1.3 are installed, you will no longer be able to launch Integration Server 6.5 SP2 and Developer 6.5 SP3 from the Windows Start menu. Go to the Integration Server_6.5 SP2_directory\bin directory and run server.bat, and go to the Developer_6.5 SP3_directory\bin directory and run developer.bat.





Business processes Do not create the Process Audit Log and Process Engine database components.

Integration Server If you are not migrating business processes, create the Process Audit Log database component.

If you chose an external RDBMS during installation, create the IS Internal and Distributed Locking database components. If you are using Oracle or DB2 for Linux, UNIX, Windows, first create storage and a tablespace directory for IS Internal by running this command:

dbConfigurator.{bat|sh} -a create -d {oracle|db2luw} -c storage -v latest -l db_server_URL-u existing_db_user -p password -au db_admin_user -ap password -t full_path_to_new_tablespace_directory

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

Do not create the IS Core Audit Log and Document History database components.

If you chose the embedded database during installation, or if you stored 6.5 SP2 cross-referencing data in the Cross Reference database component, do not create a Cross Reference database component. If you chose an external RDBMS during installation and want to store cross-referencing data in it, create the Cross Reference database component.

Metadata Library Create the Metadata Reasoner and Metadata Repository database components.


Create the My webMethods Server database component.

Optimize If you are using Infrastructure Data Collector 7.0 SP2 with Optimize Optimize 7.0 SP2, create the Analysis and Process Tracker database components.

If you are not using Infrastructure Data Collector 7.0 SP2 with Optimize 7.0 SP2, do not create the Analysis and Process Tracker database components.





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




Migrate webMethods Broker and JMS 6.5.2

Follow the instructions in “Migrate webMethods Broker 6.5.2” on page 52 and “Migrate JMS 6.5.2” on page 59.

Migrate Integration Server 6.5 SP2

Follow the instructions in “Migrate Integration Server 6.5” on page 63.

After you complete those instructions, migrate Blaze 6.1.5 rule services to Blaze 6.5. In Blaze Advisor 6.5, open each project that contains 6.1.5 rules and redeploy the rules to Integration Server 7.1.3. For detailed instructions on each of these steps, see the Designer 7.1.2 online help.












Migrate Trading Networks 6.5

Follow the instructions in “Migrate Trading Networks 6.5” on page 67.

Migrate My webMethods Server 7.0 SP2

For detailed instructions on using Deployer 7.1.2, see webMethods Deployer User’s Guide 7.1.2.

1 Make sure your dedicated LDAP or user/group database is online.

2 Apply MWS_7-0_SP2_Fix10 to My webMethods Server 7.0 SP2 using the instructions in the fix readme.

3 Start My webMethods Servers 7.0 SP2 and 7.1.3.

4 Start Integration Server, open Integration Server Administrator, and go to the SolutionsDeployer page. In Deployer, do the following:

a Configure communication between Deployer and My webMethods Server 7.0 SP2 and Deployer and My webMethods Server 7.1.3. Make sure the Exclude Core Task Engine and Include security dependencies configuration properties are set to Yes.

b Create a project and set the project properties. In the MWS Deployment Options area, set all options to Yes except Export Content as Reference. If you do not need that option, set it to No.

c If you need to migrate fewer than 500 assets (including dependencies), do the following:

1 Create a single deployment set.

2 Create a project build, deployment map, and deployment candidate.

3 Deploy the deployment set to My webMethods Server 7.1.3.

If you need to migrate more than 500 assets, deployment will be faster if you divide the assets into four projects. Do the following:

1 Create these four projects:

User, group, role, and directory service assets.

Composite and task application assets.

Custom page and folder assets.

Shell, skin, renderer, and rule assets.

If users, groups, or roles appear as dependencies in the second, third, or fourth project, mark them as Exists.


https://advantage.webmethods.com/knowledgebase?oid=1614324920


2 Create a project build, deployment map, and deployment candidate for each project.

3 Deploy the projects to My webMethods Server 7.1.3 separately, in the order shown above.

d If you deployed My webMethods Server rules, the order in which the deployed rules are resolved with the existing rules on the target servers might need modification. Review the rule order after deployment and modify as necessary.

Migrate 7.0 SP2 Business Processes

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

If you want to start new instances of migrated 7.0 SP2 process models in your 7.1.2 installation, do not have any running 7.0 SP2 process instances, and do not need to resubmit any 7.0 SP2 process instances, you must migrate your design-time data. Design-time data are the definitions of your business process models. You can migrate your design-time data to Designer 7.1.2 or 7.2.

If you want to finish 7.0 SP2 process instances that are in progress or resubmit 7.0 SP2 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.0 SP2 business process models and in progress or completed 7.0 SP2 process instances that is stored in the Process Audit Log and Process Engine database components.

If you want to start new instances of migrated 7.0 SP2 process models in the 7.1.2 installation, and you want to finish 7.0 SP2 process instances that are in progress or resubmit 7.0 SP2 process instances that have completed or failed, you must migrate both your design-time and run-time data.

Migrate Design-Time Data to Designer 7.1.2

Reuse the Eclipse workspace you used with Designer 7.0 SP2, as follows:

1 Open Designer 7.0 SP2, make sure all your preferences are current and accurate, and close Designer 7.0 SP2.

2 Open Designer 7.1.2, point it at the Eclipse workspace you used with Designer 7.0 SP2, and close Designer 7.1.2.



3 If you did not migrate task applications (see “Migrate 7.0 SP2 Tasks” on page 94), you have not yet created the workspace index for Designer 7.1.2. Create the workspace index now, as follows:

a In Windows Explorer, go to the workspace_directory\.metadata\.plugins\ com.webmethods.sc.metadata.core\.stores directory and delete all the files and folders in the directory.

b Start Designer 7.1.2. For each process project in the workspace, in the Navigator view, right-click to display the context menu and click Close Project, then right-click and click Open Project.

4 Open each process and regenerate it.

When you open a process that contains pools, Designer asks, “This process must be upgraded to view in the current version of Designer. Do you wish to save the changes?” Click OK, and then re-generate the process.

5 Update your process projects to point to the new project classpath. In the Navigator view, right-click each project and choose to run the CAF Repair Tool.

6 Open Designer 7.1.2 and generate and upload your 7.1.2 process models. For instructions, see the Designer online help.

Migrate Design-Time Data to Designer 7.2

Export Process Models and Logical Server Definitions from Designer 7.0 SP2

1 Open Designer 7.0 SP2.

2 Export process models as follows:

a Go to FileExport.

b On the Select panel, in the Select an export destination box, go to webMethods Process File and then click Next.

c On the Process File Export panel, you can choose to export all process models in a project or certain process models only. To do the former, select the check box for the project whose process models to export in the box on the left. To do the latter, select the check boxes for the process models to export in the box on the right.

In the To directory field, type the directory to which to export the process models. You can export to any directory.

Click Finish.

3 Export logical server definitions as follows:

a Go to WindowPreferences.

b On the Preferences dialog box, in the left navigation bar, go to webMethodsProcess DevelopmentLogical Servers.



c Click Export and identify the directory to which to export. You can export to any directory; for example, you might export the logical server definitions to the directory that contains the exported process models.

In the File name field, type the file name for the preferences. Designer will add the extension .properties.

Click Open.

d Click OK to close the Preferences dialog box.

Import Process Models and Logical Server Definitions into Designer 7.2

1 Open Designer 7.2.

2 You can import process models into a variety of projects, existing or new, or you can import import multiple process models into a single, existing project.

To import process models into a variety of existing or new projects, do the following:

1 Go to FileImport.

2 On the Select panel, in the Select an import source box, go to Software AG Process File and then click Next.

In the Select file field, select a process model you exported and click Open.

In the Select Project field, specify the existing or new project into which to import the process model.

Click Finish.

3 Repeat for every process model you want to import.

To import multiple process models into a single, existing project, do the following:

1 Go to FileImport.

2 On the Select panel, in the Select an import source box, go to GeneralFile System and then click Next.

3 On the File System panel, in the From directory field, browse to the directory that contains the process models you exported. Select the check box next to each .process file to import.

In the Into folder field, specify the existing project into which to import.

Click Finish.



3 Import logical server definitions as follows:

a Go to WindowPreferences.

b On the Preferences dialog box, in the left navigation bar, go to Software AGIntegration Servers. The list on the left shows your logical servers, called Integration Servers in Designer 7.2.

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

4 Configure Designer 7.2 to connect to the Integration Servers. For instructions, see the Designer online help.


Start the Migration

1 If you have not yet migrated webMethods Broker to 7.1.2, do so now. For instructions, see “Migrate webMethods Broker 6.5.2” on page 52, and make sure you follow the instructions in “Configure the 7.1.2 Broker Server to Use 6.5.2 Storage” on page 55. Also make sure the 6.5.2 Broker used by your Process Engines has the same name in 7.1.2 that it had in 6.5.2.

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

3 Migrate the Integration Server 6.5 SP2 packages that contain the triggers and generated process artifacts for the process models as described below. Each package is named using the project name or the custom-generated package name you specified.

a In Integration Server Administrator for Integration Server 6.5 SP2, archive each

package by clicking in the Archive column. By default, archiving creates a file named package.zip.

b Copy the packages from the Integration Server_6.5 SP2_directory\replicate\ outbound directory to the Integration Server_7.1.3_directory\replicate\ inbound directory.




c Install the packages on Integration Server 7.1.3, as follows:

1 In Integration Server Administrator for Integration Server 7.1.3, go to the PackagesManagementInstall Inbound Releases page.

2 In the Release file name list, click one of the packages you archived and copied.

3 Clear the Activate upon installation check box.

4 Click Install Release.

5 Repeat these steps for all the packages you copied.

4 Prevent new instances of 7.0 SP2 process models from starting by shutting down all 6.5 SP2 Integration Servers that host Process Engines.


1 Shut down all 6.5 SP2 Integration Servers that connect to the Process Audit Log and Process Tracking Store database components.


3 Migrate the Process Audit Log database component by running this command:


4 Migrate the Process Engine database component by running this command:



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



Complete the Migration

1 Start Integration Server 7.1.3 and connect the Process Audit Log and Process Engine functions to the migrated database components. For instructions, see webMethods Installation Guide 7.1. The instructions say to restart Integration Server, but do not do so yet.

2 In Integration Server Administrator for Integration Server 7.1.3, go to the PackagesManagement page. Click Active Inactive Packages and activate the packages you archived and copied to Integration Server 7.1.3 in “Start the Migration” on page 92.

3 Restart Integration Server 7.1.3.

4 If you want to migrate 7.0 SP2 tasks, do so now.

5 Re-enable document retrieval for all triggers on Integration Server 7.1.3. For instructions, see webMethods Integration Server Administrator’s Guide 7.1.1.

Migrate 7.0 SP2 Tasks

You migrate 7.0 SP2 tasks by migrating task applications and task instances.

If you want to start new instances of migrated 7.0 SP2 task applications in 7.1.3, you do not have any running 7.0 SP2 task instances, and you do not need to resubmit any 7.0 SP2 task instances, migrate your design-time data to 7.1.3. Design-time data are your task applications.

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

If you want to start new instances of migrated 7.0 SP2 task applications in 7.1.3, and you want to finish 7.0 SP2 task instances that are in progress or resubmit 7.0 SP2 task instances that have completed or failed, migrate both your design-time data and your run-time data.




Export Task Projects from Designer 7.0 SP2

1 Open Designer 7.0 SP2 and point it at the 7.0 SP2 workspace.

2 Go to the FileExport wizard.

a In the Select panel, click GeneralArchive File as the export destination and then click Next.

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

c Click Finish.

3 Shut down Designer 7.0 SP2.

Import 7.0 SP2 Task Projects into Designer 7.1.2

1 Open Designer 7.1.2 and point it at a new 7.1.2 workspace.

2 Go to WindowPreferences and do the following:

a Go to ServerInstalled Runtimes. Make sure the Installed server runtimes list includes a My webMethods Server 7.1.3. If it does not, add one.

b Go to webMethodsTask Development and make sure all your other task-related Designer preferences are correct.

c Click OK.

3 Go to the FileImport wizard.

a In the Select panel, go to webMethodsExisting CAF Projects into Workspace and then click Next.

b In the Import Projects panel, click Select Archive File, and select the archive file that contains the 7.0 SP2 task projects you exported. The 7.0 SP2 task projects appear in the Projects box. Select the task projects to import.

c Click Finish.

4 Make sure the imported 7.0 SP2 task projects appear in the Solutions tab, under the Tasks node.

5 Publish the task projects to My webMethods Server. For instructions, see the Designer online help.

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




1 Download MWS_7-0_SP2_Fix8. Apply the fix to the webMethods 7.0 SP2 installation directory. See the fix readme for installation instructions.

2 Start My webMethods Server 7.0 SP2 and My webMethods Server 7.1.3.

3 Log on to My webMethods Server 7.1.3 under SysAdmin manage.

4 On the Administration Dashboard, do the following:

a Click Migration and then click Tasks Migration.

b In the Server URL field, enter the URL for My webMethods Server 7.0 SP2 (by default, http://MWS:8080).

c In the Task Type ID field, select the task name/label for task instances to migrate.

d In the Sysadmin Password field, type manage.

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

f Repeat these steps for all task instances to migrate.

Complete the Metadata Library 7.0 Upgrade

1 Start Metadata Library 7.1.1 by going to the Metadata Library_7.1.1_directory/ library/bin directory and clicking the library.{bat|sh} program. If you get error or exception messages, investigate and correct before continuing.

2 Go to the Metadata Library_7.1.1_directory/mlivp directory and click the setup.{bat|sh} program. A message indicates that you will lose your existing metadata if you continue; click Yes. Setup takes several minutes to complete.

3 Configure Metadata Library 7.1.1. For instructions, see webMethods Metadata Library User’s Guide 7.1.1.

4 You cannot access Fabric 7 metadata from Metadata Library 7.1.1. To recover the metadata, or publish new data, publish the metadata from Designer 7.1.2, Integration Server 7.1.3, and CentraSite GE 7.1 to Metadata Library 7.1.1. For instructions, see the Designer 7.1.2 online help and webMethods Metadata Library User’s Guide 7.1.1.


https://advantage.webmethods.com/advantage?w=0&targChanId=-536884337&typeName=FIX&prodOID=536945864&count=3


Migrate Optimize 7.0 SP2

Migrate Optimize Database Components








1 Configure and start My webMethods Server. For instructions, see My webMethods Server Administrator’s Guide 7.1.1.

2 Create a new Optimize 7.1.2 environment and configure it like the Optimize 7.0 SP2 environment from which you are upgrading. Map the database pools to your database components as follows:

Important! Use this procedure only if you are using Optimize 7.0 SP2 without Infrastructure Data Collector 7.0 SP2. If you are using Infrastructure Data Collector 7.0 SP2 with Optimize 7.0 SP2, you cannot migrate Optimize process monitoring data.

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





3 Start the Optimize 7.1.2 engines.


Migrate the Data Purge Database Component

On the machine on which you installed the Database Component Configurator, go to the webMethods_7.1.2_directory\common\db\bin directory, open a command window, and migrate the Data Purge database component by running this command:









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



Complete the Deployer 7.0 Upgrade

If you have 7.0 projects that include Trading Networks assets, perform the steps in this section. For detailed information about Deployer, see the webMethods Deployer User’s Guide.

In Deployer, one of the project properties lets you specify what Deployer should do when Trading Networks rules you are trying to deploy already exist on target Integration Servers. In Deployer 7.0, the possible values for this property were Yes and No. In Deployer 7.1.2, the equivalent values are as shown below.

1 Apply DEP_7-1-2_Fix1 to Deployer 7.1.2 using the instructions in the fix readme.

2 Do the following to reset the Overwrite Existing TN Rules property correctly in your existing projects from Deployer 7.0:

To correct all projects, invoke the service http://Deployer_host:Deployer_port /invoke/wm.deployer.gui.UIProject:migrateProjects.

To correct a specific project, invoke the service http://Deployer_host:Deployer_port/ invoke/wm.deployer.gui.UIProject:migrateProjects?projectName=project

If you are using Deployer command line mode to import project properties for 7.0 projects, you must reset the property manually. Follow these steps for each project properties file you import:

a Go to the Integration Server_directory\packages\WmDeployer\replicate\ inbound directory.

b Open the project_properties file.

7.1.1 Values Description

GUI - Overwrite Existing TN Rules Option

Command Line - deployTNRules Option

Yes Replaces the entire rule list. Replace All REPLACE

No Overwrites existing rules and deploys new rules into the rule set.

Merge OVERWRITE_EXISTING_ADDNEW

Important! - If you changed any project properties before applying DEP_7-1-2 _Fix1, the service cannot reset the property correctly. Instead, Deployer resets the property to the equivalent setting for No regardless of the property's previous setting. If you want to use the equivalent setting for Yes instead, you must manually reset the property.

Note: If you later import a 7.0 project (for example, from a backup), Deployer 7.1.2 resets the property correctly automatically.


https://advantage.webmethods.com/article/?id=1614325789


c Locate the overwriteTNRules property and do the following:

1 Replace the word "overwriteTNRules" with the word "deployTNRules."

2 Set the deployTNRules property to REPLACE or OVERWRITE_EXISTING_ADDNEW.

3 Save and close the file.


4 Upgrading from 7.x to 7.x

Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

Back Up the Earlier 7.x Installation and Remove Fixes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103


Prepare to Upgrade a My webMethods Server Cluster . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104


Complete the Integration Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Complete the Trading Networks Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 110

Complete the Metadata Library Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Complete the Designer Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112

Complete the My webMethods Server Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Migrate Business Processes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 116

Complete the Optimize Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117

Complete the Deployer Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 119



Overview

This upgrade procedure explains how to upgrade webMethods products as follows:

Since you will upgrade by installing over the earlier products, you will not need to migrate data in most cases. However, for some products, you must perform certain tasks to complete the upgrade or to migrate data. This chapter provides instructions for those products.

Upgrade from... To...

7.1 or 7.1.1 webMethods Broker, Deployer, Designer, Developer, Integration Server, Monitor, My webMethods Server, Optimize, Process Engine, and Trading Networks

7.1.2

7.1 Metadata Library

Note: Metadata Library did not have a release after 7.1.1.

7.1.1

7.1, 7.1.1, or 7.1.2 Developer, Integration Server, and Designer Composite Applications plug-ins

7.1.3

7.1.1 or 7.1.2 My webMethods Server 7.1.3

7.2 Designer Composite Applications plug-ins 7.2.1

6.5.1 or 6.5.3 Blaze Advisor 6.5.5

6.5 or 6.5.3 Blaze Rule Service Plug-in and Blaze Rule Service Support

Note: The release numbering for these products was changed from 6.x to match the 7.x release numbering used for the rest of the webMethods product suite.

7.1.2

Important! You must upgrade all of your products at the same time. You must upgrade products and migrate data in the order presented in this chapter.




Back Up the Earlier 7.x Installation and Remove Fixes

1 Allow all Integration Server guaranteed delivery jobs to finish running. Allow all business processes to finish running or use webMethods Monitor to stop them.

2 Shut down all webMethods products and all other applications that are running on the machines on which you are going to overinstall products.

3 Back up the entire installation directory on each machine, and back up your databases as instructed by your RDBMS vendor.

4 If you are upgrading Integration Server, go to the Integration Server_7.x_directory\ updates directory and remove all fixes by deleting all IS_7-1*.jar, IS_7-1-1*.jar, and IS_7-1-2*.jar, IS_7.1.2*.jar files, as appropriate.

5 If you are upgrading Developer, go to the Developer_7.x_directory\ updates directory and remove all fixes by deleting all ID_7-1*.jar, ID_7-1-1*.jar, ID_7-1-2*.jar, and ID_7.1.2*.jar files, as appropriate.

6 If you are upgrading Deployer, go to the Integration Server_7.x_directory\replicate\ inbound directory and remove all fixes by deleting the WmDeployer.zip file.

Upgrade Your RDBMSs






Prepare to Upgrade a My webMethods Server Cluster

If you clustered My webMethods Server, you must perform the steps in this section.

The architecture for clustering My webMethods Server has changed. In 7.1.1, a cluster consists of a My webMethods Server on one machine and nodes on other machines. In 7.1.2 and 7.1.3, a cluster consists of multiple My webMethods Servers and a load balancer.

To upgrade a cluster, you upgrade a single My webMethods Server as described in this section, and then later clone that My webMethods Server as described in “Upgrade a My webMethods Server Cluster” on page 114. Cloning ensures that all cluster nodes are identical.

Prepare to Upgrade a 7.1.1 My webMethods Server Cluster1 Shut down My webMethods Server and all the nodes in the cluster.

2 The nodes in a 7.1.1 cluster point to shared files that are stored on either the My webMethods Server host machine or a dedicated network device. If the shared files are stored on a dedicated network device, you must copy the shared files to the My webMethods Server host machine as follows:

a On the dedicated network device, go to the shared webMethods installation directory (for example, \\shared\webMethods7).

b Copy the common, jvm, and install directories from the shared webMethods installation directory to the webMethods installation directory on the My webMethods Server host machine.

c Copy all contents of the MWS directory except the MWS/server/default/ data/repository directory to the webMethods installation directory on the My webMethods Server host machine.

3 On the My webMethods Server host machine, go to the 7.1.1_installation_directory/MWS/server/deploy directory and delete all fix_name.xml files.

4 If your shared file content services point to a dedicated network device, make sure the device is accessible.

Note: Do not copy the repository directory because it must remain in the network shared location where it is accessible to all cluster nodes.



Prepare to Upgrade a 7.1.2 My webMethods Server ClusterChoose one My webMethods Server in the cluster to upgrade and do the following on the host machine for that My webMethods Server:

1 Go to the 7.1.2_installation_directory/MWS/server/deploy directory and delete all fix_name.xml files.

2 Go to the 7.1.2_installation_directory/MWS/server/config directory. If the cluster.xml file is present, delete it.


1 Go to the documentation area of the Empower Product Support Web site and download webMethods Installation Guide 7.1. Follow the instructions in that guide to install webMethods product suite 7.1.2 and 7.1.3, with these additional guidelines or differences:

For the installation directory, specify the directory that contains your earlier 7.x webMethods products.

On the installer’s product selection tree, already installed 7.x products are shown in gray followed by the word “Installed” (wizard mode) or the letter “I” (console mode). Select the 7.1.2 and 7.1.3 products to install; be sure to select all necessary pieces for each product (see the “Development Installations” chapter in webMethods Installation Guide 7.1).


Note: As you select products, top-level product nodes might turn gray. You can ignore this; it will not adversely affect installation.

Important! If you are upgrading from Integration Server 7.1, after installing Integration Server 7.1.3, do not increase PermGen space as indicated in the webMethods Installation Guide 7.1. Instead, follow the instructions in “Migrate Integration Server 7.1 Data” on page 108.




Complete the Integration Server Upgrade

Migrate Integration Server 7.1.2 or 7.1.1 Data

After each command you run in this section, make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care.

1 Shut down all Integration Servers that connect to the 7.1.2 or 7.1.1 IS Core Audit Log or IS Internal database components.

2 On the machine on which you installed the Database Component Configurator, go to the webMethods_directory\common\db\bin directory and open a command window.

3 If you are upgrading from Integration Server 7.1.2, migrate the IS Core Audit Log database component by running this command:

If you are upgrading from Integration Server 7.1.1, migrate the IS Core Audit Log database component by running this command:

4 If you are upgrading from Integration Server 7.1.2, migrate the IS Internal database component by running this command:

5 If you are upgrading from Integration Server 7.1.1, migrate the IS Internal database component by running this command:

6 If you are also upgrading My webMethods Server, apply TC_7-1-2_Fix1 to Integration Server 7.1.3 using the instructions in the fix readme. Fixes are available from the Software AG Knowledge Center.

7 Start Integration Server 7.1.3 and connect the IS Core Audit Log, IS Internal, Cross Reference, and Document History functions to the migrated database components. For instructions, see webMethods Installation Guide 7.1. Then restart Integration Server 7.1.3.

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

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

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

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




Convert JAX-RPC Handlers

Services for registering JAX-RPC handlers are deprecated in Integration Server 7.1.3 and will not be available in Integration Server 8.0. Software AG recommends converting your JAX-RPC handlers into service-based handlers now to avoid compatibility problems in the future.

For information on the new services below, see webMethods Integration Server and webMethods Developer Documentation Supplement 7.1.2.

For each custom JAX-RPC handler, do the following:

1 Create an Integration Server service that implements the JAX-RPC handler’s handleRequest processing. One possible approach is to copy the general implementation logic from the handler’s handleRequest method into an Integration Server Java service, and to use the new pub.soap.handler* services to get the SOAP message and header elements for processing. Use the pub.soap.handler:handlerSpec specification as the signature of the Java service.

2 Create an Integration Server service that implements the JAX-RPC handler’s handleResponse processing. You could use the same approach as in step 1, but copy the logic from the handleResponse method.

3 Create an Integration Server service that implements the JAX-RPC handler’s handleFault processing. You could use the same approach as in step 1, but copy the logic from the handleFault method.

4 Create an Integration Server package startup service that uses the new pub.soap.handler:registerWmProvider or registerWmConsumer service to register the new service-based handler as a provider or consumer handler by specifying the following:

The Integration Server services created in the previous steps.

The QNames of the headers processed by the new service-based handler.

A unique descriptive name for the new service-based handler.

5 Manually run the startup service once to register the new service-based handler.

6 In all Web service descriptors (WSDs) that use the JAX-RPC handler, replace the JAX-RPC handler with the new service-based handler, as follows:

a Remove headers with QNames that are supported by the JAX-RPC handler.

b Remove the JAX-RPC handler from the WSD.

c Add the new service-based handler to the WSD.

d Add the headers you removed in step a.



Migrate Integration Server 7.1 Data

Increase PermGen Space

Windows System

By default, the webMethods Installer installs a Sun JDK for Integration Server 7.1.3 on Windows systems. If you are using the default JDK, or if you are using your own Sun JDK, complete the steps below.

1 Go to the Integration Server_directory/bin directory and open the server.bat file in a text editor.

2 Locate this line:

set JAVA_MAX_MEM=512M

Add this line beneath it:

set JAVA_MAX_PERM_SIZE=128M

3 Locate this line:

set JAVA_MEMSET=-ms%JAVA_MIN_MEM% -mx%JAVA_MAX_MEM%

Change it to:

set JAVA_MEMSET=-Xms%JAVA_MIN_MEM% -Xmx%JAVA_MAX_MEM%-XX:MaxPermSize=%JAVA_MAX_PERM_SIZE%

4 Locate this line:

set JAVA2_MEMSET=-Xms%JAVA_MIN_MEM% -Xmx%JAVA_MAX_MEM% -Xrs %XPATH_IMPL%-DWM_HOME="%WM_HOME%"

Change it to:

set JAVA2_MEMSET=-Xms%JAVA_MIN_MEM% -Xmx%JAVA_MAX_MEM%-XX:MaxPermSize=%JAVA_MAX_PERM_SIZE% -Xrs %XPATH_IMPL% -DWM_HOME="%WM_HOME%"


UNIX, IBM i5, or Mac System

By default, the webMethods Installer installs a Sun JDK for Integration Server 7.1.3 on Linux and Solaris systems. If you are using the default JDK on those systems, or if you are using your own Sun JDK on one of those systems, another UNIX system, or an IBM i5 or Mac system, complete the steps below.

Note: If you receive java.lang.OutOfMemoryError: PermGen space exceptions when running Integration Server, set the PermGen space higher than the 128 MB mentioned in this section.

Note: If you receive java.lang.OutOfMemoryError: PermGen space exceptions when running Integration Server, set the PermGen space higher than the 128 MB mentioned in this section.



1 Go to the Integration Server_directory/bin directory and open the server.sh file in a text editor.

2 Locate this line

JAVA_MAX_MEM=512M

Add these lines beneath it:

JAVA_MAX_PERM_SIZE=128MJAVA_PERM_SIZESET=-XX:MaxPermSize=${JAVA_MAX_PERM_SIZE}

3 Locate this line:

JAVA_RUN="${JAVA_DIR}/${JAVA_EXE} ${JAVA_MEMSET} ${JAVA_OPT_PREFER_IP4V}"

Change it to:

JAVA_RUN="${JAVA_DIR}/${JAVA_EXE} ${JAVA_MEMSET} ${JAVA_PERM_SIZESET} ${JAVA_OPT_PREFER_IP4V}"


Update the Configuration File

Go to the Integration Server_directory/bin directory and open the ini.cnf file in a text editor. Locate the text wm-caf-jsf-impl.jar and replace it with wm-caf-jsf-mws.jar, then save and close the file.


After each command you run in this section, make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_directory\ common\db\logs directory. If errors occurred, contact Software AG Customer Care.

1 Shut down all Integration Servers that connect to the 7.1 IS Core Audit Log, IS Internal, Cross Reference, and Document History database components.


3 Migrate the IS Core Audit Log database component by running this command:

4 Migrate the IS Internal database component by running this command:


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



5 Migrate the Cross Reference database component by running this command:

6 If you are also upgrading My webMethods Server, apply TC_7-1-2_Fix1 to Integration Server 7.1.3 using the instructions in the fix readme. Fixes are available from the Software AG Knowledge Center.

7 Start Integration Server 7.1.3 and connect the IS Core Audit Log, IS Internal, Cross Reference, and Document History functions to the migrated database components. For instructions, see webMethods Installation Guide 7.1. Then restart Integration Server 7.1.3.

Convert JAX-RPC Handlers

Services for registering JAX-RPC handlers are deprecated in Integration Server 7.1.3 and will not be available in Integration Server 8.0. Software AG recommends converting your JAX-RPC handlers into service-based handlers now to avoid compatibility problems in the future. For instructions, see “Convert JAX-RPC Handlers” on page 107.

Complete the Trading Networks Upgrade

Migrate Trading Networks Data

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

2 Go to the Integration Server_7.x_directory/updates directory and remove Trading Networks fixes by deleting all TNS_7-1_*.jar and TNS_7-1-1*.jar files.

3 Go to the Trading Networks Console_7.1_directory/updates directory and remove Trading Networks Console fixes by deleting all TNC_7-1_*.jar and TNC_7-1-1*.jar files.

4 If you are upgrading from Trading Networks 7.1and you applied TNS_7-1-1_DB_Fix1, or if you are upgrading from Trading Networks 7.1.1 and you applied TNS_7-1-1_DB_Fix2, do the following:

a Go to the webMethods_directory/common/db/scripts/database_type/ tradingnetworks/migrate/20_to_25 directory.

b Open the database_type_tns_m_20_to_25.sql script in a text editor.

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

Note: The migration process converts the date and time stamp for all Trading Networks data to Greenwich Mean Time (GMT).




c Comment out the following:

d Save and close the script.

5 On the machine on which you installed the Database Component Configurator, go to the webMethods_directory\common\db\bin directory, open a command window, and mMigrate the Trading Networks database component by running this command:

Make sure the command was successful by checking the log file dcc_yyyymmddHHMMss in the webMethods_directory\common\ db\logs directory. If errors occurred, contact Software AG Customer Care.

Set Up Trading Networks to Work with My webMethods Server

1 Enable My webMethods Server 7.1.3 to call Trading Networks services, as follows:

a Start Integration Server 7.1.3 and open Integration Server Administrator.

b Go to the SettingsExtended page and click Edit Extended Settings. In the Extended Settings box, type the property as follows:

watt.server.auth.samlResolver=http://My webMethods Server_7.1.3_host:My webMethods Server_7.1.3_port/services/SAML

c Click Save Changes. The property changes dynamically; you do not have to restart Integration Server.

2 In Trading Networks 7.1.2, all Trading Networks-related roles you create in My webMethods are automatically granted access to the My webMethods Administrative Preferences page. This page enables users to connect to Trading Networks and specify other Trading Networks options. With Trading Networks 7.1 and 7.1.1, this access was not granted automatically, so you must now grant it manually. Grant all Trading Networks-related roles access to the Administrative Preferences page as follows:

a Go to the AdministrationSystem-WideUser ManagementRoles page.

b In the Roles list, click TN Administrative Preferences.

c Click the Members tab, and then click Edit Members.

For TNS_7-1-1_DB_ Comment out...

Fix1 The index in the Create table FX_RoutingStatus section.

Fix2 The Create table FX_RoutingStatus and Create table FX_UserStatus sections.




d In the Select Principal(s) dialog box, click Roles, then click Search.

e In the Available list, click every Trading Networks-related role and then click Apply.

Complete the Metadata Library Upgrade

Identify the JDK you want Metadata Library to use.

Metadata Library 7.1 supported Infravio X-Registry 6.6, but Metadata Library 7.1.1 supports CentraSite GE 7.1 and CentraSite EE 3.1.7. If you want to use CentraSite with Metadata Library 7.1.1, configure the CentraSite Asset Publisher. For instructions, see webMethods Metadata Library User’s Guide 7.1.1.

Complete the Designer Upgrade

1 Open Designer 7.1.2 or 7.2.

2 In the Navigator view, right-click each portlet application project and click CAF ToolsRepair CAF Project.

3 Click the Problems tab. If you see errors, restart Designer.

System Steps

Windows 1 Go to the Metadata Library_directory\library\bin directory and open the setJava.bat file in a text editor.

2 Use the rem command to comment out the set JAVA_DIR line (that is, rem set JAVA_DIR=${JAVA_HOME}). This will cause Metadata Library to use the JDK specified by the JAVA_HOME environment parameter. If you want Metadata Library to use a different JDK instead, add a new JAVA_DIR line just beneath the commented-out JAVA_DIR line, and specify the path to that JDK:

rem set JAVA_DIR=${JAVA_HOME}set JAVA_DIR=path_to_JDK


UNIX 1 Go to the Metadata Library_directory/library/bin directory and open the library.sh file in a text editor.

2 In the JAVA_DIR=${JAVA_HOME} line, replace ${JAVA_HOME} with the path to the JDK you want to use (for example, JAVA_DIR=webMethods_directory/jvm/linux150).


Note: You might see errors. Ignore them and go to the next step.



Complete the My webMethods Server Upgrade

Migrate My webMethods Server Data

1 Go to the 7.x_installation_directory\MWS\server\default\config directory, open the mws.db.xml file, and make sure the JDBC connection information is correct.

1 If you are upgrading from My webMethods Server 7.1.1 and you have applied MWS_7-1-1_CL_Fix9 or higher, or if you are upgrading from My webMethods Server 7.1.2 and you have applied MWS_7-1-2_CL_Fix1 or higher, drop the index (IX_T_JMS_QUEUE_1) from your database by running the appropriate command below from your database editor:

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 the My webMethods Server database component by running this command:


3 Go to the 7.x_installation_directory\MWS\bin directory, open a command window, and run the command below to upgrade your My webMethods Server files and configuration. The name of the default My webMethods Server instance is default.

4 Start My webMethods Server to complete the upgrade process. My webMethods Server redeploys all components and shuts down. You can now restart My webMethods Server and operate it normally.

5 If you are upgrading a My webMethods Server cluster, go to Upgrade a My webMethods Server Cluster, below.

RDBMS Command

Oracle or DB2 DROP INDEX IX_T_JMS_QUEUE_1;

SQL Server DROP INDEX T_JMS_QUEUE.IX_T_JMS_QUEUE_1;

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

Important! You must retain the database permissions used in this step until My webMethods Server is started and initialized so that My webMethods Server can create database tables and views.

mws -s server_instance upgrade



Upgrade a My webMethods Server Cluster

When you upgrade a 7.1.1 or 7.1.2 My webMethods Server cluster, you do not actually upgrade each cluster node. Instead you create each node by cloning the My webMethods Server you upgraded in “Prepare to Upgrade a My webMethods Server Cluster” on page 104. Cloning ensures that all cluster nodes are identical.

1 Restart My webMethods Server.

2 If the cluster is on a Windows system, you must update the content service location to use Universal Naming Convention (UNC) paths instead of mapped drives. Log on as sysadmin and open Administration Dashboard > Content > Content Service Admin and change paths where needed.

3 As My webMethods Server administrator, go to the Cluster Administration page. Write down the names of all nodes in the cluster.

4 Shut down the My webMethods Server you upgraded earlier.

5 For each node in the cluster, do the following:

a Create a webMethods installation directory on the node host machine that is identical to the webMethods installation directory on the upgraded My webMethods Server’s host machine (for example, c:\webMethods7).

b Create a My webMethods Server installation on the node host machine.

From the upgraded My webMethods Server’s host machine, copy the common, jvm, and install directories to the webMethods installation directory you created on the node host machine.

From the upgraded My webMethods Server’s host machine, copy all contents of the MWS directory except the MWS/server/default/ data/repository directory to the webMethods installation directory you created on the node host machine.

c On the node host machine, go to the 7.x_installation_directory\MWS\ server\default\bin directory and open the server.properties.{bat|sh} file in a text editor. Update or add the environment variable below to the file. For node_name, use the name of the node that you wrote down in step 3.

Note: If you stored your shared files on a dedicated network device, the repository directory will not exist on the upgraded My webMethods Server’s host machine. If it does exist, do not copy the repository directory because it must remain in the network shared location where it is accessible to all cluster nodes

System Environment Variable

Windows set NODE_NAME=node_name

UNIX NODE_NAME=node_name



d Save and close the file.

6 If you used asymmetric component deployment mode in My webMethods Server and you deployed different versions or sets of custom components to My webMethods Server, go to the 7.x_installation_directory\MWS\server\deploy directory for each node and make sure the correct versions of custom components are present.

7 Start each node in the cluster using the command below. You can start the nodes in any order. The default My webMethods Server instance is named default.

8 Restart each node in the cluster using the command below. You can restart the nodes in any order.

9 For each node, go to the 7.x_installation_directory/MWS/server/default/deploy/portal.war/WEB-INF directory and open the server-config.wsdd file. If it does not contain the XML tags below, add them to the end of the section that contains service elements.

<service name="SAML" provider="java:MSG" style="message" use="literal"><parameter name="allowedMethods" value="samlAssertionHandler"/><parameter name="className" value="com.webmethods.portal.portlet.wm_xt_samlsecurityservice.endpoint.SamlServiceEndpoint"/>

</service>

10 On any node, retrieve the cluster.xml config file from the My webMethods Server database by going to the7.x_installation_directory/MWS/bin directory and running this command:

11 Open the cluster.xml file and make sure the list of cluster nodes matches your My webMethods Server cluster. If any nodes listed in the file do not exist in your My webMethods Server cluster, delete those nodes from the file and then upload the file to the My webMethods Server database by running this command:

mws -s server_instance {run|start}

mws -s server_instance restart

mws.bat getconfig cluster.xml

mws.bat putconfig cluster.xml



Migrate Business Processes


If you are migrating from 7.1 or 7.1.1 to Designer 7.1.2, you do not need to migrate your design-time data. It is already in the correct location.

If you are migrating from 7.1, 7.1.1, or 7.1.2 to Designer 7.2, follow the instructions in “Migrate Design-Time Data to Designer 7.2” on page 90.


1 Shut down all 7.1.3 Integration Servers that connect to the Process Engine database component.


3 Migrate the Process Engine database component by running this command:


4 Migrate the Process Audit Log database component by running this command:



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




Complete the Optimize Upgrade

Configure Infrastructure Data Collector

1 Go to the Infrastructure Data Collector_directory\config directory and open the infradc.cnf file in a text editor.

2 Set the infradc metadataloaded property to false.


Migrate Optimize Database Components






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







1 Configure and start My webMethods Server. For instructions, see My webMethods Server Administrator’s Guide 7.1.1.

2 Create a new Optimize 7.1.2 environment and configure it like the Optimize 7.1 environment from which you are upgrading. Map the database pools to your database components as follows:

3 Start the Optimize 7.1.2 Analytic and Prediction engines.


Migrate the Data Purge Database Component

On the machine on which you installed the Database Component Configurator, go to the webMethods_7.1.2_directory\common\db\bin directory, open a command window, and migrate the Data Purge database component by running this command:









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



Complete the Deployer Upgrade

If you have 7.1 or 7.1.1 projects that include Trading Networks assets, perform the steps in this section. For detailed information about Deployer, see the webMethods Deployer User’s Guide.

In Deployer, one of the project properties lets you specify what Deployer should do when Trading Networks rules you are trying to deploy already exist on target Integration Servers. In Deployer 7.1 or 7.1.1, the possible settings for this property were Yes and No. In Deployer 7.1.2, the equivalent settings are as shown below.

1 Apply DEP_7-1-2_Fix1 to Deployer 7.1.2 using the instructions in the fix readme.

2 Do the following to reset the Overwrite Existing TN Rules property correctly in your existing projects from Deployer 7.1 or 7.1.1:

To correct all projects, invoke the service http://Deployer_host:Deployer_port /invoke/wm.deployer.gui.UIProject:migrateProjects.

To correct a specific project, invoke the service http://Deployer_host:Deployer_port/ invoke/wm.deployer.gui.UIProject:migrateProjects?projectName=project

If you are using Deployer command line mode to import project properties for 7.1 or 7.1.1 projects, you must reset the property manually. Follow these steps for each project properties file you import:

a Go to the Integration Server_7.1.3_directory\packages\WmDeployer\replicate\ inbound directory.

b Open the project_properties file.

7.1.1 Values Description

GUI - Overwrite Existing TN Rules Option

Command Line - deployTNRules Option

Yes Replaces the entire rule list. Replace All REPLACE

No Overwrites existing rules and deploys new rules into the rule set.

Merge OVERWRITE_EXISTING_ADDNEW

Important! - If you changed any project properties before applying DEP_7-1-2_Fix1, the service cannot reset the property correctly. Instead, Deployer resets the property to the equivalent setting for No regardless of the property's previous setting. If you want to use the equivalent setting for Yes instead, you must manually reset the property.

Note: If you later import a 7.1 or 7.1.1 project (for example, from a backup), Deployer 7.1.2 resets the property correctly automatically.


https://advantage.webmethods.com/article/?id=1614325789


c Locate the overwriteTNRules property and do the following:

1 Replace the word "overwriteTNRules" with the word "deployTNRules."

2 Set the deployTNRules property to REPLACE or OVERWRITE_EXISTING_ADDNEW.



web methods upgrade guides

Documents