Académique Documents
Professionnel Documents
Culture Documents
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.
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
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.
IS-UPG-601to61-20040618
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.
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
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>
d 3
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>
IS-UPG-601to61-20040618
c 4
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>
c 5
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
IS-UPG-601to61-20040618
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.
IS-UPG-601to61-20040618
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.
IS-UPG-601to61-20040618
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 '>'
IS-UPG-601to61-20040618
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
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.
IS-UPG-601to61-20040618
11
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.
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
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
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