webMethods Integration Server Upgrading from 4.x to 6.

Overview
To upgrade Integration Server 4.x to Integration Server 6.5, read Before You Begin and then complete the following: Back Up the Integration Server 4.x Installation on page 4. You backup and record settings from the previous Integration Server to reconfigure into Integration Server 6.5. Create Database Tables on page 4. You run the scripts that the webMethods Installer provides to create the tables. Install Integration Server 6.5 on page 5. You install Integration Server 6.5 in a different directory from Integration Server 4.x. Complete the Integration Server Upgrade on page 5. You complete the upgrade by updating settings, configuration files, and logging databases. If the 4.x installation includes a cluster of Integration Servers, plan to upgrade the cluster in an order that maximizes availability. For example, you might want to remove or bring down all but one server in the cluster during the migration. Then, migrate the last server before bringing the entire upgraded cluster online. For information about clustering, see the webMethods Integration Server Clustering Guide. Note: Earlier releases of Integration Server 4.x were called B2B servers. This guide refers to all 4.x servers as Integration Servers.

Before You Begin

Before upgrading to Integration Server 6.5, review the following information.

Critical Information
If you currently use Trading Networks Conversation Manager 4.6, Business Integrator 4.6, Process Monitor 4.6, or Workflow 4.6 and want to continue using webMethods Business Process Management (BPM) capabilities, do not upgrade to Integration Server 6.5. The BPM products will be supported with Integration Server 6.5 when the 6.5 BPM products become available later this year. If you are an existing customer who uses Integration Server, but you do not plan to use any BPM capabilities at this time, then webMethods Monitor 6.1.5 is supported on webMethods Integration Server 6.5 for IS Core monitoring functionality only, namely services, documents, and activations. For instructions on installing and configuring Monitor 6.1.5 on your Integration Server 6.5, see the webMethods Installation Guide.

IS-UPG-4xto65-20050511

webMethods Integration Server: Upgrading from 4.x to 6.5

Important! Although Monitor 6.1.5 is supported for IS Core monitoring functionality only, you still need to configure a Process Audit database and associate the Process Audit functional alias with a JDBC Pool. For scalability purposes, webMethods recommends you configure the IS Core Audit database and the Process Audit database in separate database schemas. For details about configuring the Process Audit database, see the webMethods Logging Guide. Integration Server 6.5 does not support C/C++ or Visual Basic code generation on 64bit platforms. AS/400 and Mac OS are no longer supported platforms for webMethods Monitor.

Flow
Prior to Integration Server 6.5, conditional expressions that compare numeric string values returned incorrect results if the numeric value exceeded the precision of java.lang.Double. For example, if your condition is: (string1 == string2) string1 = 012345678901234567 string2 = 012345678901234568 Then the flow engine returns true for this condition even though the numeric values are not equal. In Integration Server 6.5, the expression evaluator is enhanced to process arbitrary-length numeric strings correctly. The text of flow exceptions due to time out or unknown service has changed. Prior to Integration Server 6.5, you received the following error if there was a time out at an INVOKE step that did not have a label: com.wm.lang.flow.FlowException: [ISC.0049.9013] Timeout at 'unlabeled INVOKE' In Integration Server 6.5, the error message includes the name of the service being invoked, as follows: com.wm.lang.flow.FlowException: [ISC.0049.9013] Timeout at 'Invoke for flow.test:delay'

Web Services/SOAP
Prior to Integration Server 6.5, the pub.client:soapHTTP and pub.client:soapRPC services set the outbound Content-type header to text/xml without specifying the UTF-8 charset. This caused the data to be processed incorrectly if the Web server assumes the 8859-1 encoding when processing the UTF-8 bytes. In Integration Server 6.1 Service Pack 1, a new parameter contentType was added to the input signature of the pub.client:soapHTTP and pub.client:soapRPC services that allows the

IS-UPG-4xto65-20050511

webMethods Integration Server: Upgrading from 4.x to 6.5

user to specify the UTF-8 charset encoding. However, in 6.1 Service Pack 1, the default behavior excludes the UTF-8 charset. In Integration Server 6.5, the contentType parameter is available and the default behavior is to include the UTF-8 charset. Set the parameter only if you need to revert to the previous behavior of excluding the charset tag. The SOAP Envelope reference now points to the 2001 XML Schema recommendation. Prior to Integration Server 6.5, SOAP envelopes referenced the 1999 draft of the XML Schema recommendation. In Integration Server 6.5, SOAP envelopes will have the following namespace declarations: xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"

XML Parsing
Integration Server 6.5 enforces stricter validation when it encounters malformed entities during XML parsing. Previously, Integration Server did not detect malformed entities and parsed them into an empty string. The Integration Server now throws an exception if it detects a malformed entity. This is a change in the default behavior. If you want to revert to the previous default behavior in which Integration Server does not throw an exception when malformed entities are encountered, set the watt.server.xml.enforceEntityRef parameter to false.

Deprecated Server Parameters

The following parameters for LDAP have been deleted:
watt.server.ldap.attr.member watt.server.ldap.attr.password watt.server.ldap.attr.userid watt.server.ldap.directoryRoot watt.server.ldap.groupFilter watt.server.ldap.groupRoot watt.server.ldap.security.credential watt.server.ldap.security.principal watt.server.ldap.server watt.server.ldap.userFilter watt.server.ldap.userRoot watt.server.ldap.usersInGroups

IS-UPG-4xto65-20050511

webMethods Integration Server: Upgrading from 4.x to 6.5

Back Up the Integration Server 4.x Installation

1 2 Start Integration Server if it is not already running and open Integration Server Administrator. Complete the following steps to record Integration Server 4.x configuration settings: a Go to the Security > Ports page and record all settings on that page by printing the page. For HTTPS ports, click the link in the Port column to display the View HTTPS Port Details page and record all settings on that page by printing the page. Go to the Security > Ports page. For each port configured as Deny by Default, click Edit in the Access Mode column. Record the allowed services for each port by printing the page. Prepare your application packages for migration by creating package zip files, as follows: 1 2 Go to the Packages > Publishing page. Select a package and click Create and Delete Releases. On the page that appears, click Create Release. 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_directory\replicate\outbound directory. Repeat the previous step for each package. For more information about creating a release, see the webMethods Integration Server Administrators Guide.

3 d

If you imported client certificates to Integration Server 4.x, go to the Security > Certificates > Client Certificates page in the Integration Server Administrator and record the settings on that page. Then remove each imported certificate from Integration Server 4.x by clicking in the row for each certificate.

3 4

Shut down Integration Server 4.x. Back up the Integration Server 4.x installation directory.

Create Database Tables

By default, Integration Server 6.5 writes IS Core Audit Log, Process Audit Log, and CrossReference data to flat files. You can configure Integration Server to write this data to a database. The webMethods Installer provides scripts to create the necessary tables. You need to create the Document History tables because, unlike the other types of data, Integration Server always writes Document History data to a database. For information about how to create the tables, see the Preparing the Database chapter in the webMethods Installation Guide.

IS-UPG-4xto65-20050511

webMethods Integration Server: Upgrading from 4.x to 6.5

Install Integration Server 6.5

Important! For complete instructions on installing, configuring, and completing the installation of Integration Server 6.5, see the webMethods Installation Guide. 1 2 3 Download webMethods Installer 6.5 from the webMethods Advantage Web site at http://advantage.webmethods.com and run the installer. Specify a different installation directory from Integration Server 4.x. Complete the webMethods Installer instructions.

Complete the Integration Server Upgrade

After you install Integration Server 6.5, perform the following steps to complete the upgrade: Step One: Migrate 4.x Configuration Files and Certificates on page 6. Step Two: Migrate 4.x Repository Data on page 7. Step Three: Associate the Document History Function with the Database on page 9. Step Four: Migrate 4.x Packages on page 10. Step Five: Define 6.5 Ports on page 10. Step Six: Import Client Certificates on page 10. Step Seven: Review Logging Facilities on page 11. Step Eight: Test the Migration on page 11.

IS-UPG-4xto65-20050511

webMethods Integration Server: Upgrading from 4.x to 6.5

Step One: Migrate 4.x Configuration Files and Certificates

1 Navigate to the Integration Server_directory\config directory in the 4.x installation and copy the following files to the same directory in the 6.5 installation. Note: Your Integration Server configuration determines which of the files listed below are present. Some of the files might not exist in your config directory. acls.cnf codegen.cnf eventcfg.bin jobs.cnf ldap.cnf 2 port.cnf publishers.cnf redir.cnf released_pkg.cnf remote.cnf server.cnf subscribers.cnf users.cnf

Navigate to the certificate directory (by default, Integration Server_directory\config) in the 4.x installation and copy the certificates to the same directory in the 6.5 installation. Navigate to the Integration Server_directory\lib\jars directory in the 4.x installation. a Copy all user-created and adapter-related .zip and .jar files that need to be loaded into the Integration Server classpath to the Integration Server_directory\lib\jars directory in the 6.5 installation. Copy all user-created and adapter-related .zip and .jar files that need to be loaded into your system classpath to the Integration Server_directory\lib\system directory in the 6.5 installation.

Important! If webMethods components other than adapters wrote .zip or .jar files to the Integration Server_directory\lib\jars directory in the 4.x installation, do not copy those files to the 6.5 installation. 4 Navigate to the Integration Server_directory\bin directory in the 4.x installation and migrate any custom CLASSPATH values in the server.bat or server.sh file to the same file in the same directory of the 6.5 installation. The 6.5 scripts are restructured, so you need to edit only the PREPENDCLASSES and APPENDCLASSES lines. Navigate to the Integration Server_directory\config directory in the 6.5 installation. a Delete the following deprecated properties in the server.cnf file:
watt.debug2.checkfullrate watt.debug2.commentLine watt.debug2.formatLine watt.debug2.logstringfile watt.debug2.maxlogsize

IS-UPG-4xto65-20050511

webMethods Integration Server: Upgrading from 4.x to 6.5

watt.debug2.outputLine watt.server.oldkey watt.server.serverLogFmt watt.server.logRotate watt.server.logRotateInterval

b 6 7

Save the file. When you start Integration Server, it will merge the 4.x server.cnf settings into the new 6.5 server.cnf file.

Navigate to Integration Server_directory\packages\WmDB\config in the backup 4.x directory and copy the jdbc.cnf file to the same directory in the 6.5 installation. Navigate to Integration Server_directory\packages\WmRoot\config in the backup 4.x directory and copy the listeners.cnf file to the same directory in the 6.5 installation.

Step Two: Migrate 4.x Repository Data

If you use the Integration Server Repository to store data, you must migrate the 4.x Repository to the Integration Server 6.5 installation. The process of migrating Repository data varies based on the Repository you were using in the 4.x installation. Repository Built-in filebased Built-in JDBCbased Action Navigate to the Integration Server_directory\WmRepository2 directory in the 4.x installation and copy the contents of the directory to the same directory in the 6.5 installation. 1 Create a Repository Server alias for the database that contains the Integration Server 4.x Repository data. For instructions, see the webMethods Integration Server Clustering Guide. Configure the Integration Server 6.5 Repository to use this alias. For instructions, see the webMethods Integration Server Administrators Guide.

IS-UPG-4xto65-20050511

webMethods Integration Server: Upgrading from 4.x to 6.5

Repository Remote filebased

Action 1 Navigate to the Integration Server_directory\ reposerver\WmRepository2 directory in the 4.x installation and copy the contents of the directory to the same directory in the 6.5 installation. Navigate to the Integration Server_directory\reposerver directory in the 4.x installation and copy the Repository.ini file over the same file in the same directory in the 6.5 installation. Navigate to the Integration Server_directory\reposerver\config directory in the 4.x installation and copy the contents of the directory to the same directory in the 6.5 installation. Navigate to the Integration Server_directory\reposerver\bin directory in the 6.5 installation and run the repoui.bat or repoui.sh program. The program displays the webMethods Repository Configuration dialog box. Select the File System check box and modify the relative path if necessary to identify the location of the 6.5 Repository. Create a Repository Server alias for the primary Repository to which Integration Server 6.5 will connect and for each secondary Repository to which Integration Server 6.5 might connect. For instructions, see the webMethods Integration Server Clustering Guide. Configure the 6.5 Integration Server Repository to use these aliases. For instructions, see the webMethods Integration Server Administrators Guide. Navigate to the Integration Server_directory\reposerver\config directory in the 4.x installation and copy the contents of the directory to the same directory in the 6.5 installation. Navigate to the Integration Server_directory\reposerver directory in the 4.x installation and copy the Repository.ini file over the same file in the same directory in the 6.5 installation. Create a Repository Server alias for the primary Repository to which Integration Server 6.5 will connect and for each secondary Repository to which Integration Server 6.5 might connect. For instructions, see the webMethods Integration Server Clustering Guide. Configure the 6.5 Integration Server Repository to use these aliases. For instructions, see the webMethods Integration Server Administrators Guide.

Remote JDBCbased

IS-UPG-4xto65-20050511

webMethods Integration Server: Upgrading from 4.x to 6.5

If you changed the CLASSPATH in the Repository Server startup scripts for the 4.x installation, reapply the changes to the scripts for the 6.5 installation, as follows: 1 2 3 4 5 Navigate to the Integration Server_directory\reposerver\bin directory in the 4.x installation and open the repostore.bat or respostore.sh file in a text editor. Navigate to the Integration Server_directory\reposerver\bin directory in the 6.5 installation and open the repostore.bat or respostore.sh file in a text editor. Copy any changes you made to the 4.x file to the 6.5 file. Save and close the 6.5 files. Repeat the previous steps for the repoui.bat or repoui.sh file.

Step Three: Associate the Document History Function with the Database
1 2 3 Start Integration Server 6.5 if it is not already running and open Integration Server Administrator. Go to the Settings > JDBC Pools page. Associate the Document History function with the database as follows: a b c d e In the Functional Alias Definitions area, locate the Edit Association column for the Document History functional alias and click Edit in that column. In the Associated Pool Alias list, click the JDBC connection pool to use. Click Save Settings. Integration Server Administrator returns to the Settings > JDBC Pools page. In the Functional Alias Definitions area, locate the Restart Function column for the Document History functional alias. Click Restart. In the Functional Alias Definitions area, locate the Test column for the Document History functional alias on the far right side of the page. Test the connection by clicking .

4 5 6

Go to the Settings > Extended page, then click Edit Extended Settings. In the Extended Settings box, set the watt.server.auditStore parameter to database. Click Save Changes.

IS-UPG-4xto65-20050511

webMethods Integration Server: Upgrading from 4.x to 6.5

Step Four: Migrate 4.x Packages

1 Navigate to the Integration Server_directory\replicate\outbound directory of the 4.x installation and copy the packages you zipped to the Integration Server_directory\ replicate\inbound directory of the 6.5 installation. In Integration Server Administrator, go to the Packages > Management > Install Inbound Releases page. In the Release file name list, click the package that you want to migrate, and then click Install Release. The Integration Server installs the package, then displays a message that says the package has been installed and activated. Repeat the previous step for each package you want to migrate. If you installed packages that have ports associated with them, verify that the server replicated the correct security settings for the port. If necessary, reconfigure the ports with their original security settings. Go to the Access Mode page for each port and click Reset to Default Access Settings. The Integration Server keeps the Deny by Default access mode but populates the Allow list with a group of Anonymous services. You will reconfigure your port security settings in the next section.

2 3

4 5

Step Five: Define 6.5 Ports

Note: You cannot replicate your WmRoot package from Integration Server 4.x to Integration Server 6.5. If you were using a port with clustering and internal load balancing, you do not need to recreate it now. When enabling clustering in Integration Server 6.5, you can create a special port for internal load balancing. For information about how to create a port, see the webMethods Integration Server Administrators Guide. 1 2 In Integration Server Administrator, go to the Security > Ports page. Add any ports that were not added when you installed your inbound packages and recreate the ports that were associated with the WmRoot package. Use the port information you recorded earlier.

Step Six: Import Client Certificates

If you recorded imported client certificate settings from Integration Server 4.x, go to the Security > Certificates > Client Certificates page and import the client certificates into Integration Server 6.5. Then map each certificate to the appropriate user account. For instructions about importing and mapping certificates, see the webMethods Integration Server Administrators Guide.

IS-UPG-4xto65-20050511

10

webMethods Integration Server: Upgrading from 4.x to 6.5

Step Seven: Review Logging Facilities

In Integration Server 6.5, you can log messages for many new facilities. For descriptions of these facilities and instructions on adding their messages to your logging output, see the webMethods Logging Guide.

Step Eight: Test the Migration

Restart Integration Server 6.5 to make sure that all your package startup services work. Then open Integration Server Administrator, go to the Packages > Management page, and make sure all your packages loaded without errors.

webMethods Administrator, webMethods Broker, webMethods Dashboard, webMethods Developer, webMethods Fabric, webMethods Glue, webMethods Installer, webMethods Integration Server, webMethods Mainframe, webMethods Manager, webMethods Mobile, webMethods Modeler, webMethods Monitor, webMethods Optimize, webMethods Portal, webMethods Trading Networks, and webMethods Workflow are trademarks of webMethods, Inc. webMethods and the webMethods logo are registered trademarks of webMethods, Inc. Copyright 2005 by webMethods, Inc. All rights reserved, including the right of reproduction in whole or in part in any form.

IS-UPG-4xto65-20050511

11