Sie sind auf Seite 1von 13

webMethods Integration Server Upgrading from 6.0.1 to 6.

Overview
You upgrade Integration Server 6.0.1 to Integration Server 6.1 by installing Integration Server 6.1 over Integration Server 6.0.1. Except where noted, all configuration files and files you created in Integration Server 6.0.1 remain unchanged in Integration Server 6.1. If the 6.0.1 installation includes a cluster of Integration Servers, plan to upgrade the cluster in an order that maximizes availability. You might want to remove or bring down all servers but one in the cluster during the migration, then migrate that one server last before bringing the entire new cluster online. 6.0.1 Integration Server can operate fully with 6.1 Brokers. For information on clustering, see the webMethods Integration Server Clustering Guide.

Back Up the Integration Server 6.0.1 Installation


1 Record Integration Server 6.0.1 settings, as follows: a b c Start Integration Server and open Integration Server Administrator. If Integration Server connects to a Broker, go to the Settings > Broker page and record all settings by printing the page. If you are currently using publish/subscribe functionality with Integration Server 6.0.1 and are not using the default document stores settings, go to the Settings > Resources > Document Stores page and record all settings by printing the page. If you imported client certificates into Integration Server, go to the Security > Certificates > Configure Client Certificates page and record all settings by printing the page. Then remove each imported certificate from Integration Server by clicking in the row for each certificate. Navigate to the Integration Server_directory\bin directory and create a backup copy of the server.bat or server.sh file. You will use this backup later to set properties in the 6.1 server.bat or server.sh file the same way they were set in Integration Server 6.0.1. Navigate to the Integration Server_directory\reposerver\bin directory and create a backup copy of the repoui.bat or repoui.sh file. You will use this backup later to set properties in the 6.1 repoui.bat or repoui.sh file the same way they were set in Integration Server 6.0.1.

Shut down all 6.0.1 webMethods components and all other applications that are running on the machine on which you are going to install 6.1 Integration Server. In

IS-UPG-601to61-20040618

webMethods Integration Server: Upgrading from 6.0.1 to 6.1

addition, if any business processes are running, wait for them to complete normally or use Monitor to stop them. Important! If all components, applications, and business processes are not shut down, the installer will not be able to replace key files that are locked by the operating system. 3 4 Back up the Integration Server 6.0.1 installation directory (by default, webMethods6\IntegrationServer). Back up the IS Core Audit Log, Process Audit Log, and Cross-Reference databases, as follows: Database Oracle SQL Server Sybase DB2 UDB 5 Action Use Oracles export (exp or exp80) utility. Use SQL Server Enterprise Manager. See the Sybase documentation. See the DB2 UDB documentation.

Install the database scripts available through the webMethods Installer, then create the Document History database table. For instructions, see the Preparing the Database chapter in the webMethods Installation Guide. Important! Do not follow the instructions in that chapter to create any database tables that already exist in your databases. Instead, use the instructions later in this chapter to upgrade 6.0.1 tables to 6.1 formats.

Install Integration Server 6.1


Important! For complete instructions on installing, configuring, and completing the installation of Integration Server 6.1, see the webMethods Installation Guide. 1 2 3 Download webMethods Installer 6.1 from the webMethods Advantage Web site at http://advantage.webmethods.com and run the installer. Specify the installation directory as the directory that contains webMethods 6.0.1 (by default, webMethods6). The component configuration panels display the values from the 6.0.1 installation. If your 6.0.1 license key has expired or is about to expire, supply the Integration Server 6.1 license key provided by webMethods. If Integration Server 6.0.1 was installed as a Windows application, you can install Integration Server 6.1 as a Windows service. If Integration Server 6.0.1 was installed as

IS-UPG-601to61-20040618

webMethods Integration Server: Upgrading from 6.0.1 to 6.1

a Windows service and you want to run Integration Server 6.1 as a Windows application, you can do so after installation is complete. Complete the Integration Server Upgrade on page 3 provides instructions. Define a JDBC connection pool for the Document History database. If you already have JDBC connection pools for the IS Core Audit Log, Process Audit Log, and CrossReference databases in the 6.1 installation, you can redefine them to be different from the connection pools for the 6.0.1 installation. For instructions on defining connection pools, see the chapter on specifying Integration Server configuration information in the webMethods Installation Guide. Note: You can also change the JDBC connection pool definitions after the upgrade is complete. For instructions, see the webMethods Integration Server Administrators Guide.

Complete the Integration Server Upgrade


Update the Startup File
If you made changes to the server.bat or server.sh file in the 6.0.1 installation, follow these steps: 1 2 3 4 Navigate to the backup of the server.bat or server.sh file you created before you installed Integration Server 6.1 and open the backup file in a text editor. Navigate to the Integration Server_directory\bin directory in the 6.1 installation and open the server.bat or server.sh file in a text editor. Copy any changes made to the 6.0.1 file to the 6.1 file. Save and close the files.

Update Repository Configuration Files


If you used a local Integration Server Repository with the 6.0.1 installation and made changes to the 6.0.1 repoui.bat or repoui.sh file, follow these steps: 1 2 3 4 Navigate to the backup of the repoui.bat or repoui.sh file you created before you installed Integration Server 6.1 and open the backup file in a text editor. Navigate to the Integration Server_directory\reposerver\bin directory in the 6.1 installation and open the repoui.bat or repoui.sh file in a text editor. Copy any changes made to the 6.0.1 file to the 6.1 file. Save and close the files.

If you made changes to the repostore.bat or repostore.sh and repoconfig.bat or repoconfig.sh files, repeat the previous steps for those files as well.

IS-UPG-601to61-20040618

webMethods Integration Server: Upgrading from 6.0.1 to 6.1

Update ACL Settings


1 2 Navigate to the Integration Server_directory\config directory in the 6.1 installation. Open the aclmap_sm.cnf file in a text editor and do the following: a Add these lines to the bottom of the file:
<value name="wm.server.pki">Administrators</value> <value name="wm.server.nsimpl">Developers</value>

Locate this line:


<value name="wm.tomcat">Developers</value>

If the line exists in the file, change it as shown below. If the line does not exist in the file, add the line shown below.
<value name="wm.tomcat">Administrators</value>

Remove these lines:


<value <value <value <value <value name="com.wm.app.enterprise.admin.startup">BrokerAdministrators</value> name="wm.prt.admin:configSettings">Administrators</value> name="com.wm.app.enterprise.admin">BrokerAdministrators</value> name="com.wm.app.enterprise.admin.startup:setPackageACLs">Developers</value> name="com.wm.app.enterprise.admin.startup:initialize">Developers</value>

d 3

Save and close the file.

Open the acllist.cnf file in a text editor and do the following: a Add these lines to the bottom of the file:
<value <value <value <value <value name="pub.smime:getContentType">WmPrivate</value> name="pub.uddi">Developers</value> name="pub.uddi.client.util">WmPrivate</value> name="omi">Administrators</value> name="wm.ism">Administrators</value>

Remove these lines:


<value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value name="wm.server.ff:SEFParse">WmPrivate</value> name="wm.server.ff:createDocumentType">Administrators</value> name="wm.server.ff:createFFDictionary">Administrators</value> name="wm.server.ff:createFFSchema">Administrators</value> name="wm.server.ff:getAllDefinitions">Administrators</value> name="wm.server.ff:getDefinition">Administrators</value> name="wm.server.ff:getDictionaryEntries">Administrators</value> name="wm.server.ff:init">Administrators</value> name="wm.server.ff:registerContentHandler">Administrators</value> name="wm.server.ff:saveDocumentDataForUI">Administrators</value> name="wm.server.ff:setACLs">Administrators</value> name="wm.server.ff:shutdown">Administrators</value> name="Tutorial">Developers</value> name="Tutorial:setACLS">Administrators</value> name="Tutorial:ftpData">Developers</value> name="Tutorial:importData">Developers</value> name="Tutorial:PurchaseOrderDT">Developers</value>

IS-UPG-601to61-20040618

webMethods Integration Server: Upgrading from 6.0.1 to 6.1

<value <value <value <value

name="Tutorial:PurchaseOrder">Developers</value> name="Tutorial:CommaSeparetedID">Developers</value> name="Tutorial:CommaSeparetedNoID">Developers</value> name="Tutorial:OrderData">Developers</value>

c 4

Save and close the file.

Open the aclread.cnf file in a text editor and do the following: a Add these lines to the bottom of the file:
<value name="pub.uddi">WmPrivate</value> <value name="omi"> WmPrivate </value> <value name="wm.ism"> WmPrivate </value>

Remove these lines:


<value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value name="wm.server.ff:SEFParse">WmPrivate</value> name="wm.server.ff:createDocumentType">Administrators</value> name="wm.server.ff:createFFDictionary">Administrators</value> name="wm.server.ff:createFFSchema">Administrators</value> name="wm.server.ff:getAllDefinitions">Administrators</value> name="wm.server.ff:getDefinition">Administrators</value> name="wm.server.ff:getDictionaryEntries">Administrators</value> name="wm.server.ff:init">Administrators</value> name="wm.server.ff:registerContentHandler">Administrators</value> name="wm.server.ff:saveDocumentDataForUI">Administrators</value> name="wm.server.ff:setACLs">Administrators</value> name="wm.server.ff:shutdown">Administrators</value> name="Tutorial">Developers</value> name="Tutorial:setACLS">WmPrivate</value> name="Tutorial:ftpData">Developers</value> name="Tutorial:importData">Developers</value> name="Tutorial:PurchaseOrderDT">Developers</value> name="Tutorial:PurchaseOrder">Developers</value> name="Tutorial:CommaSeparetedID">Developers</value> name="Tutorial:CommaSeparetedNoID">Developers</value> name="Tutorial:OrderData">Developers</value>

c 5

Save and close the file.

Open the aclwrite file in a text editor and do the following: a Add these lines to the bottom of the file:
<value name="pub.uddi">WmPrivate</value> <value name="omi"> WmPrivate </value> <value name="wm.ism"> WmPrivate </value>

IS-UPG-601to61-20040618

webMethods Integration Server: Upgrading from 6.0.1 to 6.1

Remove these lines:


<value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value <value name="wm.server.ff:SEFParse">WmPrivate</value> name="wm.server.ff:createDocumentType">Administrators</value> name="wm.server.ff:createFFDictionary">Administrators</value> name="wm.server.ff:createFFSchema">Administrators</value> name="wm.server.ff:getAllDefinitions">Administrators</value> name="wm.server.ff:getDefinition">Administrators</value> name="wm.server.ff:getDictionaryEntries">Administrators</value> name="wm.server.ff:init">Administrators</value> name="wm.server.ff:registerContentHandler">Administrators</value> name="wm.server.ff:saveDocumentDataForUI">Administrators</value> name="wm.server.ff:setACLs">Administrators</value> name="wm.server.ff:shutdown">Administrators</value> name="Tutorial">Developers</value> name="Tutorial:setACLS">Administrators</value> name="Tutorial:ftpData">Developers</value> name="Tutorial:importData">Developers</value> name="Tutorial:PurchaseOrderDT">Developers</value> name="Tutorial:PurchaseOrder">Developers</value> name="Tutorial:CommaSeparetedID">Developers</value> name="Tutorial:CommaSeparetedNoID">Developers</value> name="Tutorial:OrderData">Developers</value>

Save and close the file.

Upgrade the Logging Database


Important! When you run the IS Core Audit Log scripts listed in this section on a SQL Server database, you might see warnings about maximum key length for the IDX_SESS_SVRID, IDX_ERR_SVRID, IDX_TXIN_SVRID, and IDX_TXOUT_SVRID indices. If your Integration Server IDs will be no longer than 900 bytes (300 multi-byte characters), you can ignore this warning. If your Integration Server IDs will be longer than 900 bytes, remove the indices. If you are storing 6.0.1 IS Core Audit Log data, Process Audit Log data, or both in a database, follow the steps below. 1 Create the 6.1 database tables and migrate the 6.0.1 data to the 6.1 tables. In your database editor, navigate to the webMethods_directory\common\db\scripts\migrate directory in the 6.1 installation and execute the appropriate scripts: Data IS Core Audit Log Process Audit Log Migrate Table Script File mig_iscoreaudit_6-0-1_to_6-1_database.sql mig_processaudit_6-0-1_to_6-1_database.sql

IS-UPG-601to61-20040618

webMethods Integration Server: Upgrading from 6.0.1 to 6.1

If you installed Monitor 6.0.1 Service Pack 1 and archived 6.0.1 logging data, create the 6.1 archive tables and migrate the archived 6.0.1 data to the 6.1 archive tables. In your database editor, navigate to the webMethods_directory\common\db\ scripts\migrate directory in the 6.1 installation and execute the appropriate scripts: Data IS Core Audit Log Process Audit Log Migrate Table Script File mig_archive_iscoreaudit_6-0-1_to_6-1_database.sql mig_archive_processaudit_6-0-1_to_6-1_database.sql

Start Integration Server 6.1 and open Integration Server Administrator. Note: When you start Integration Server, Monitor starts automatically and completes the upgrade of the logging database.

4 5

Go to the Settings > Extended page, then click Edit Extended Settings. In the Extended Settings box, type watt.server.auditLoadSchema=true, then click Save Changes.

Associate the Document History Function with the Database


1 2 In Integration Server Administrator 6.1, go to the Settings > JDBC Pools page. Associate the Document History function with the database as follows: a b c d In the Functional Alias Definitions area, locate the Edit Association column for the DocumentHistory 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. Initialize the connection pool. In the Functional Alias Definitions area, locate the Restart Function column for the DocumentHistory functional alias on the far right side of the page. Click Restart. Make sure the function can connect to the database. In the Functional Alias Definitions area, locate the Test column for the DocumentHistory functional alias on the far right side of the page. Test the connection by clicking .

IS-UPG-601to61-20040618

webMethods Integration Server: Upgrading from 6.0.1 to 6.1

Update Integration Server Settings


1 In Integration Server Administrator 6.1, go to the Settings > Extended page, then click Edit Extended Settings. In the Extended Settings box, type the following:
watt.server.auditlog.gd=true watt.server.broker.replyConsumer.sweeperInterval=30000 watt.server.broker.producer.multiclient=1 watt.server.auditMaxFetchSize=100 watt.server.broker.replyConsumer.fetchSize=5 watt.server.idr.reaperInterval=10 watt.server.auditlog.session=true watt.security.fips.mode=false watt.config.systemProperties=mail.imap.partialfetch\=true watt.server.auditlog.error=true watt.net.ftpDataConnTimeout=60000 watt.server.tx.jobdir=logs/jobsin watt.security.fips.provider=Entrust watt.net.ftpConnTimeout=900000 watt.server.broker.replyConsumer.multiclient=1 watt.server.auditDBSize=10 watt.server:auditThreshold=100

Then click Save Changes. 2 If you recorded Broker configuration settings from Integration Server 6.0.1, go to the Settings > Broker > Edit page. Enter the 6.0.1 Broker configuration settings, then click Save Changes. If you recorded document stores settings from Integration Server 6.0.1, go to the Settings > Resources > Document Stores > Edit page. Enter the 6.0.1 document stores settings, then click Save Changes. If you recorded imported client certificate settings from Integration Server 6.0.1, go to the Security > Certificates > Configure Client Certificates page and import the client certificates into Integration Server 6.1. Then map each certificate to the appropriate user account. For instructions, see the webMethods Integration Server Administrators Guide.

Review Logging Facilities


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

IS-UPG-601to61-20040618

webMethods Integration Server: Upgrading from 6.0.1 to 6.1

Test the Migration


Restart Integration Server 6.1 to make sure 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. Note: The Integration Server server log displays error messages concerning Trading Networks. Ignore these messages.

Run Integration Server as a Windows Application


If Integration Server 6.0.1 was installed as a Windows service and you want Integration Server 6.1 to run as a Windows application, you must remove the Windows service for Integration Server. To do so, open a command window, navigate to the Integration Server_directory\support\win32 directory and run this command:
installSvc.bat unreg

Other Migration Considerations


Reconfigured Document Store Properties
When you have an Integration Server that is connected to a Broker and you upgrade both components to 6.1, two settings change on the 6.1 Integration Server. In Integration Server Administrator, on the Settings > Resources > Document Stores page, the Duration box (used for inbound document history) and the Inbound Client Side Queuing box both become unavailable. For information on the inbound document history and inbound client side queueing, see the webMethods Integration Server Administrators Guide.

Stricter XML Parsing


In the earlier version, the XML parser was lenient with XML end tags that were missing a >. For example, the following XML fragment was processed without error:
<?xml version="1.0"?><foo><bar> abc </bar</foo>

In version 6.1, the XML parser will throw an exception when XML end tags are missing a >. For example:
com.wm.app.b2b.server.ServiceException: [ISC.0042.9331] Malformed end tag </bar>: missing '>'

Fixed Java API


In the earlier version, when decoding XML files that did not declare an encoding, the com.wm.util.XMLCoder class assumed the default file encoding of the Integration Servers JRE. Since UTF-8 is the default encoding for XML files that do not declare an

IS-UPG-601to61-20040618

webMethods Integration Server: Upgrading from 6.0.1 to 6.1

encoding, this behavior was incorrect. In version 6.1, the com.wm.util.XMLCoder class assumes UTF-8 for such files. If you experience problems decoding an XMLCoder file you produced using a pre-webMethods 6 version of Integration Server, set the encoding attribute in the files XML prolog to the appropriate encoding.

Changed Services
In the earlier version, the documentation for the pub.date:dateTimeFormat service stated that the sliding window algorithm the service used to resolve two-digit years was [49, +50] years from the current year. However, the service actually incorrectly used a sliding window of [-79, +20] years from the current year. In version 6.1, the pub.date:dateTimeFormat service has been fixed to conform to the documentation and to match the other pub.date services. If your application was dependent on the previous incorrect sliding window behavior, you can revert to the previous behavior. To do so, in Integration Server Administrator, go to the Settings > Extended page and click Edit Extended Settings. In the Extended Settings box, type watt.server.pubDateTimeFormat.javaSlidingWindow=true, then click Save Changes. In the earlier version, the service specifications for the pub.mime services declared the mimeData parameter as an Object type. The actual type of this variable has always been a subclass of IData (Document). In version 6.1, the service specifications have been updated to declare the mimeData parameter as a Document type. No impact on existing flows is anticipated. In the earlier version, the pub.xml:documentToXMLString service (also known as the pub.web:recordToDocument service) did not process null data consistently. In some cases, the service omitted null values from the XML output String or added them with the content null. In version 6.1, the service consistently adds null values to the XML output String as empty tags. In the earlier version, if Integration Server tried to connect to an HTTPS server using the pub.client:http service but the certificates provided were not sufficient to gain access, the service returned a 200 OK status. Since the connection was not successful, this status code was incorrect. In version 6.1, the service throws a ServiceException under these conditions. In the earlier version, the pub.soap.utils:addBodyEntry and addHeaderEntry services did not require body and header entries in SOAP documents to have a namespace name. However, namespace names in body and header entries are required for interoperability with the products of some other vendors. In version 6.1, these services throw an exception if the body or header entry in a SOAP document does not have a namespace name. The pub.soap.utils:addBodyEntry service throws this exception:
Invalid Body Entry. SOAP Body Entries must have a namespace name.

IS-UPG-601to61-20040618

10

webMethods Integration Server: Upgrading from 6.0.1 to 6.1

The pub.soap.utils:addHeaderEntry service throws this exception:


Invalid Header Entry. SOAP Header Entries must have a namespace name.

You can revert to the previous behavior. To do so, in Integration Server Administrator, go to the Settings > Extended page and click Edit Extended Settings. In the Extended Settings box, type watt.server.SOAP.enforceMsgPartNS=false, then click Save Changes. In version 6.0.1, the pub.flow:getTransportInfo service did not declare filePolling outputs. However, when the service was called through a File Polling listener, the service placed the outputs in the pipeline. In version 6.1, the pub.flow:getTransportInfo service declares outputs for the filePolling protocol. The outputs are declared in the pub.flow:getTransportInfo service specification and they are different from the outputs produced in version 6.0.1. If you used getTransportInfo with File Polling listeners in version 6.0.1, you might have to update your mappings. In version 6.0.1, the pub.security.reverseInvoke:listRegisteredConnections service returned a String totalRemoteConnections variable that was not declared in the services output specification. In version 6.1, this extraneous output has been removed from the specification. In version 6.0.1, the String arithmetic services in the pub.math folder returned the toString() representation of the result number. In version 6.1, the output value is formatted for the null locale (US English format). This format is almost identical to the output format for version 6.0.1, with some subtle differences. In version 6.1, large floats are no longer returned using scientific notation. For example, in version 6.0.1, the addFloats service returned 2.4691356E7 for 12345678 + 12345678. In version 6.1, the service returns 24691356. Also, some precision errors have been fixed. For example, in version 6.0.1, the addFloats service returned 42.010000000000005 for 17.01 + 25. In version 6.1, the service returns 42.01. Note: If extremely precise calculations are critical to your application, you should write your own Java services to perform math functions.

Improved Publish and Subscribe Performance


In version 6.0.1, the signature and pubNetAddr fields in the pub.publish:envelope service were declared as type java.lang.Byte[]. In version 6.1, to improve performance, the type for both fields has been changed to byte[]. The Integration Server 6.0.1 readme cautioned against using these fields, but it is safe to use the fields in Integration Server 6.1.

Fixed Conditional Expressions


In version 6.0.1, Integration Server did not correctly process conditional expressions involving Boolean variables when the Boolean variable was instantiated in a Java service using Boolean myVar = Boolean.FALSE; (as opposed to Boolean myVar = new Boolean(false);). The condition myVar returned the boolean value of myVar (in this case, FALSE) if myVar was instantiated using the first method. However, if the

IS-UPG-601to61-20040618

11

webMethods Integration Server: Upgrading from 6.0.1 to 6.1

condition myVar was instantiated using the second method, myVar returned whether myVar exists in the pipeline (in this case, TRUE). In version 6.1, the condition myVar consistently evaluates whether myVar exists in the pipeline, regardless of how the variable was instantiated. In version 6.0.1, conditional expressions that compared numeric objects to constants surrounded by double quotes did not work correctly. Greater than or less than comparisons always evaluated to false. For example, MyInteger > 5 always returned false. Also, if MyFloats value was 5.0, then MyFloat == 5.0 returned true, but MyFloat == 5 or MyFloat == 5.00 returned false. In version 6.1, the condition evaluates correctly against the value of the quoted constant.

Fixed Validation Errors


In version 6.0.1, validation for a constrained object did not report an error when a String or Document (IData) variable was passed in. In version 6.1, validation reports an error under this condition. For example, if a document specifies a field type as java.lang.Integer but a String is present during validation, validation reports this error:
[ISC.0082.9033] Java type mismatch; expected java.lang.Integer, got java.lang.String

The format of the validation error message for service input and output validation changed slightly from version 6.0.1 to version 6.1. In version 6.0.1, the error message format was as follows:
com.wm.app.b2b.server.ServiceException: Input validation for service failed: folder:serv /var1 VV-005 [ISC.0082.9034] Field is absent, field must exist

In version 6.1, the error message format is as follows:


com.wm.app.b2b.server.ServiceException: [ISC.0049.9005] Input validation for service 'folder:serv' failed: '/var1 VV-005 [ISC.0082.9034] Field is absent, field must exist'

If your application contained logic to parse the exact String, you might have to update the logic.

Other Enhancements
In version 6.0.1, the watt.server.dispatcher.readInterval property was introduced. In version 6.1, this property is no longer used because the read interval is determined using a self-adjusting algorithm. The factors used to determine whether to save filter information with webMethods Broker document subscriptions changed from version 6.0.1 to version 6.1. In version 6.0.1, if any part of the Integration Server filter did not have an equivalent in Broker filter syntax, Integration Server saved the subscription on the Broker but did not save any part of the filter on the Broker. In version 6.1, under the same conditions,

IS-UPG-601to61-20040618

12

webMethods Integration Server: Upgrading from 6.0.1 to 6.1

Integration Server saves the subscription on the Broker with all parts of the filter that have an equivalent in Broker filter syntax. Integration Server does not save any parts of the filter that do not have an equivalent on the Broker. In version 6.0.1, Integration Server saved String comparisons that use standard operators on the Broker. In version 6.1, Integration Server never saves such String comparisons on the Broker. Depending on the type of filters used in your triggers, these changes might affect the volume of network traffic between Integration Server and Broker Server in the 6.1 installation. For more information on filters, see Publish-Subscribe Developers Guide. You can restore pipeline files that you produced in pre-webMethods 6 versions using version 6.1. However, you cannot restore some saved pipeline files produced in version 6.1 using pre-webMethods 6 versions. Specifically, pipeline files produced in version 6.1 that contain java.lang.Float or java.lang.Double objects are not compatible with pre-webMethods 6 versions.

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, webMethods Workflow, and the webMethods logo are trademarks of webMethods, Inc. webMethods is a registered trademark of webMethods, Inc. Copyright 2004 by webMethods, Inc. All rights reserved, including the right of reproduction in whole or in part in any form.

IS-UPG-601to61-20040618

13