webMethods Developer 8.

2 SP1 Readme April 2011

This file contains important information you must read before using webMethods Developer 8.2 SP1. You can find additional information about webMethods Developer 8.2 SP1 on the Software AG Documentation Web site. In addition, the following suite-related information is also available at that location: webMethods Product Suite Release Notes webMethods System Requirements Using the Software AG Installer Installing webMethods Products Using the Software AG Update Manager (fixes) webMethods Upgrade Guide Product Documentation You can find the following information in the Products section of the Empower Web site: Security Information Globalization Information

Contents
1.0 Critical Information 2.0 Known Issues 3.0 Usage Notes 4.0 Fixes and Enhancements 4.1 Fixes and Service Packs Included in This Release 4.2 Resolved Issues 4.3 Enhancements 4.4 Documentation Changes 4.5 Terminology Changes 4.6 Deprecated Items 4.7 Added, Removed, Deprecated, or Changed Built-In Services 4.8 Added, Removed, Deprecated, or Changed APIs 5.0 Copyright Information 6.0 Support

1.0 Critical Information

This section lists the critical issues that were known when this readme was published. For critical information found later, go to the Knowledge Center portion of the Empower Product Support Web site.

webMethods Developer is deprecated and does not support all the features of webMethods Integration Server 8.2. Software AG recommends the use of Software AG Designer for service development.

2.0 Known Issues

This section lists issues that were known when this readme was published. For known issues found later, go to the Knowledge Center portion of the Empower Product Support Web site.

PIE-1416 (was 1-10AEQL) Deleting a service does not remove its associated method. Deleting a Java service from Developer does not remove the corresponding method from the .java file in the [packageName]\code\source directory. This is also true for C/C++ services. To work around this issue, manually delete the method from the .java file. Pay special attention to the contents of .java and similar source files when deleting Java or C/C++ services. PIE-1463 (was 1-10IFYL) Modifications are not removed from reverted services. When multiple Java services are created in the same folder and modified and saved, and one of the new services is reverted, the modifications are not removed from the .java and node.idf files. To work around this issue, when creating a new Java service, immediately check it in before making any changes to it. To make changes to the service, check it out, make the changes, save them, then check the service back in. Pay special attention to the contents of .java and similar source files when reverting new Java services. PIE-1787 (was 1-12G1PV) C/C++ services require the use of unique names. C/C++ Services must be uniquely named. This limitation is a departure from the behavior of Integration Server when the VCS Integration feature is not enabled. There is currently no workaround for this issue. PIE-1811 (was 1-12Q7KF) Revert behaves differently for single C/C++ service creation than for multiple C service creation. There is a difference in the way the Revert behaves when you create a single new C/C++ service and the way it behaves when you create multiple new C services in the same folder. When a single new C/C++ service is created, modified, saved, and then reverted, the modified information is removed from the service, and the method for the service remains in the .java file in the [packageName]\code\source directory. However, if multiple C/C++ services are created in the same folder, modified and saved, and then one of the new services is reverted, the modified information is retained in the service and the method for the service is removed from the .java file. Pay special attention to the contents of .java and similar source files when reverting C/C++ services. To work around this issue, when creating a new C/C++ service, immediately check it in before making any changes to it. To make changes to the service, check the service out, make the changes, save them, and then check the service back in.

PIE-1834 (was 1-12V8Z9) Cannot revert modifications if another Java or C/C++ service is moved or copied to the same folder. While modifying a checked out Java or C/C++ service, if you move or copy another Java or C/C++ service to the same folder, you will not be able to revert the modifications that you make to the Java or C/C++ service that you are modifying. To avoid this problem, do not move or copy Java or C/C++ services until your modifications are saved and checked in. PIE-1926 (was 1-13D9CP) Sync Document Type action fails. This issue applies to environments where document types are published with webMethods Broker and the VCS Integration feature is enabled. If you run the Sync Document Type command against a publishable document without first checking out the documents referenced by the publishable document, the command will fail. To avoid this problem, lock all documents referenced by the publishable document before running the Sync Document Type command against it. PIE-1981 (was 1-13ZYGT) The associated Broker document type still exists when reverting a document type from publishable to nonpublishable. This issue applies to environments where document types are published with webMethods Broker. If you convert a non-publishable document type to publishable, save it, and then revert the document type. The document type will revert to non-publishable, but the associated Broker document type will still exist. Delete the associated Broker document type manually. PIE-2016 (was 1-14528T) Components on Integration Server are not synchronized with components in the VCS repository. For various reasons, a component on the Integration Server may be different from the version of the component in the VCS repository (an out of sync condition). If you attempt to check out an out-of-sync component, Developer displays an error message alerting you to the condition, and the check out aborts. The folder containing the component is placed in a locked state, preventing you from applying various VCS commands to the folder. Because folders do not display the checked out icon, the only way to verify this condition is to apply the View History command to the folder. If the folder is locked/checked out, you can apply the Revert or Check In commands to the folder, and then apply the Get Latest Version command to eliminate the out-of-sync condition. VCS actions applied to a folder apply to all folder contents of the folder. PIE-3760 (was 1-1JH9V9) Deleting a Java service and C service from the same folder does not delete java.frag and node.ndf of one of the services, as well as the .java file. Deleting a Java service and C service that are present in the same folder does not delete the java.frag and node.ndf files of one of the services and the .java file in code\source\... folder. To work around this issue, the files must be manually deleted from the backend VCS system. PIE-3880 (was 1-1KAC53) Copying a folder containing Java services to another location does not copy the .java file in VCS. For a folder containing multiple java services, copy the folder to another package, and then in the VCS system, the code\source folder of the destination package does not contain a .java file. To add the .java file to VCS system, Java services must be checked in.

PIE-3944 (was 1-1LG9PB) View History for ClearCase is not organized as that of VSS. The information in the History for an element is not organized the same way as VSS. There is currently no workaround for this issue. PIE-3946 (was 1-1LG9SF) View History for a checked-in folder does not consistently return results. If you create a folder containing some nodes, when the View History option is enabled, it returns a blank VCS log. The behavior is inconsistent. There is currently no workaround for this issue. PIE-3982 (was 1-1LN3TP) Deleting multiple nodes that contain a C service does not remove its corresponding method for service from the java file. Create multiple nodes in a folder that includes C and Java services. Remove all the nodes except inside the Java service. The method for the C service is still present in the .java file inside code\source folder. To work around this issue, delete the method from the .java file manually. PIE-4052 (was 1-1M60IZ) After renaming a folder containing multiple Java services, the .java file is no longer present. If you create a folder containing multiple Java services and rename the folder, a .java file cannot be found in the code\source folder. To work around this issue, check in the Java service before adding the .java file to VCS. PIE-4055 (was 1-1M67YU) If VCS is ClearCase, loading an earlier version of a folder containing multiple Java services, where some services have been renamed, does not load the nodes with the old names. When a flow or Java service is renamed, Integration Server deletes the service with the old name, and then recreates the service with its name. By default, ClearCase does not load a file that is deleted from its repository. There is currently no workaround for this issue. PIE-4086 (was 1-1MDBR7) Revert on a node leads to the nonexistence of the node. If a Revert is done on a node that is installed directly in a Dynamic View, it disappears from Developer. This issue happens only for certain types of nodes, for example, flat file schemas. The disappearance of the node will not occur if the Integration Server packages folder is not directly residing in a ClearCase view. There is currently no workaround for this issue. PIE-4137 (was 1-1MULXJ) No error message is issued when attempting to edit Trigger Properties from Integration Server Administrator. If a trigger is checked out by a user, another user can check out the same trigger from another Integration Server and edit its properties. There is currently no workaround for this issue.

PIE-4403 (was 1-1NNVV9) Multibyte characters that are provided as check-in comments for ClearCase are corrupted after check-in. If a ClearCase check-in comment includes characters from a double-byte character set (such as Japanese, Chinese, etc.), these characters are not displayed correctly in the "View History" dialog or in ClearCase Explorer. To work around this issue, do not use double-byte characters in the Comments field when checking in a node. PIE-4413 (was 1-1NQJO7) VCS options in Developer are not localized. If the operating system locale is changed and the language packs for Integration Server are installed, the menu items for VCS in Developer are not localized. There is currently no workaround for this issue. PIE-4459 ( was 1-1NW1KN) If the difference between a checked out node and the node in the repository is 2, no error is thrown for VSS. If multiple checkouts are allowed, different users can check out the same node. Assume that vcsuser1 checks out a node and vcsuser2 checks out the same node from a different Developer, then vcsuser2 checks in the node after some time. When vcsuser1 tries to check in the node, in Developer, the node becomes unlocked. However, in VCS, it can be seen that the node is still in its checked-out state. To work around this issue, disable multiple check outs in the VCS system. PIE-4641 (was 1-1OP5QZ) Get Earlier Version based on date does not work correctly. For VSS, if the Developer and Integration Server are running on two different machines, and if the time zone of Integration Server is GMT+05:30 and the time zone of Developer is IST, providing a valid date does not return the expected results. There is currently no workaround for this issue. PIE-5828 (was 1-1SF4AP) In Developer, WS-I compliance test fails for a Web service descriptor if an operation corresponds to a service with non-ASCII characters in the signature. When performing a WS-I compliance test for a Web service descriptor, Developer does not encode nonASCII characters correctly. As a result, the characters are interpreted as invalid and the compliance test fails. To work around this issue, use Designer to test for WS-I compliance for Web service descriptors that have non-ASCII characters in the service signature. PIE-6442 (was 1-1U1OYH) Error while deleting a Checkout element by same user in Designer when Integration Server is configured with Subversion. When deleting a Checkout element by same user in Designer, a NullPointerException is thrown, although the flow service is removed from the server. There is no workaround for this issue.

PIE-6535 (was 1-1U9P2X) Error while importing a package archived through Integration Server configured with Subversion Repo. '.\packages\.svn\entries (Access is denied)' error is generated. To work around this issue, if trying to install as SVN configured folder, remove all '.svn' files and folders before putting the zip file in the inbound folder. After installing the package, commit the package from Developer. PIE-13202 (was 1-YEN2T) VCS Load Earlier Version command fails in non-English locales. When applying the VCS Load Earlier Version by date command to a package, folder, or element, the command fails in locales other than English. There is currently no workaround for this issue. PIE-13294 (was 1-YS06D) Document dependents are not reflecting changes to the document name. When renaming a document, updates to the documents dependents are not immediately reflected in the VCS repository if the document dependents are checked out. To work around this issue, check in the dependent files to apply the changes. PIE-13324 (was 1-YVCE5) Methods for a service are erroneously removed from the .java file after the service is reverted. If you use the new wizard to create multiple Java services in the same folder, modify them, save them, and then revert one of the new services, Integration Server removes the method for the reverted service from the .java file. To work around this issue, when using the new wizard to create a Java service, first check in the service without making any changes to it. When you want to make changes, check out the service, make your changes, save them, and then check the service back in. PIE-13421 (was 1-ZP3YY) Templates cannot be edited. Templates are not editable through Developer once a package has been checked into the VCS repository. Because the template files are read-only, an attempt to save a modified template file results in this error: Could not save the service output template for [component]. com.wm.app.b2b.server.ServiceException: [ISS.0085.9121] Template file exists but is not writeable. To work around this issue, check out the template file manually using the VCS client, apply your modifications, save the file, and then check it in manually with the VCS client. PIE-13524 (was 1-ANBE4) Calls made from Developer to Integration Server never time out. If the Integration Server does not return a response to an invoke, the Developer becomes unresponsive. There is currently no workaround for this issue.

WDP-172 (was 1-12JEGE) Invoking any Integration Server service using Developer-generated code from Microsoft Excel generates an Out of Memory error. To invoke a service in Integration Server from Microsoft Excel, code has to be generated for the service through Developer (Tools > Generate Code). This code is used per the instructions in the webMethods Developers Guide and wmXLTemplate.xls to invoke the service from Microsoft Excel. Upon invoking the service from Microsoft Excel, the client gets an Out of Memory error. To work around this issue, place the following lines in the Visual Basic client code before creating a "Context" object: Dim webmGlobal As New webMethods.Global webmGlobal.InitJVM WDP-205 (was 1-14LW4T) VCS Get Latest Version and Get Earlier Version commands fail for Mainframe transaction services. The Get Latest Version and Get Earlier Version commands will fail when applied to Mainframe transaction services and Mainframe group transactions services, and all transaction or group transaction data is lost. This error occurs because the VCS Integration feature does not add the cfgdata.xml file to the VCS repository. To avoid losing transaction data, do not apply the Get Latest Version or Get Earlier Version commands to Mainframe transaction services. WDP-211 (was 1-15316P) Developer does not recognize valid java.util.Date format. Developer does not recognize dates in the format YYYY-MM-DD HH:MM:SS as valid. It expects dates in the following format: YYYY-MM-DD HH:MM:SS z, where z indicates the time zone. If the value for z is not supplied, Developer returns an error. To work around this issue, add a value for z to the date format (for example, 2008-01-28 12:03:15 EDT). WDP-234 (was 1-161B7P) The original Classpath is not restored when Developer exits. Currently, the developer.bat file does not restore the original Classpath when Developer exits. To work around this issue, save the Classpath before starting Developer and restore the saved Classpath after Developer exits. WDP-322 (was 1-1GX4K9) The password field in the Results panel is neither hidden nor encrypted. If you run the pub.client:http service with inputs to the URL, auth type (basic), auth user, and password fields, and use default values for the other fields, the Results panel displays the auth pass field value in clear text. There is currently no workaround for this issue. WDP-337 (was 1-1HIB3V) Cannot enter data for a recursive document type at run time. When you run a flow that takes a document type with a recursive structure as input, the document field contains the message "Cannot enter data for recursive document types." Use a map step to set the field value, or link a variable to the field. To work around this issue, use Designer or use a map step to set the field value or link a variable to the field in Developer.

WDP-561 (was 1-1NFZ08) A Java.lang.RuntimeException error may occur during the creation of a consumer WSD from an HTTPS URL. When trying to create a consumer Web service descriptor (WSD) from an HTTPS WSDL URL that was generated from a provider WSD, a java.lang.RuntimeException error occurs. To work around this issue, change the WSDL URL from HTTPS to HTTP. WDP-611 (was 1-1O0GTH) The Check Out option is enabled for a locked node. In Developer, even if a node is locked (checked out), the option Check Out is enabled for that element. There is currently no workaround for this issue. WDP-667 (was 1-1P3HY1) If a filter contains a "_" character, all of the published Web services will be returned for the search. If you use an underscore character (_) in filter criteria, the search result will show all of the published Web services rather than a filtered list of Web services. There is currently no workaround for this issue. WDP-863 (was 1-1UKDM5) After deleting a package that contained a consumer WSD, recreating the consumer WSD in an identical location in a new package fails. Suppose that you create a consumer WSD in a package and then you delete the package. If you try to create the same consumer WSD from the same WSDL in a new package, Integration Server will not create the consumer WSD because the namespace information related to the previous folders created for the consumer WSD still exists on Integration Server. Before you delete the package, delete the folder structure that contains the consumer WSD and its associated elements. This ensures that Integration Server removes the namespace information that pertains to the folder and prevents any namespace collisions that might have otherwise occurred if you try to recreate the consumer WSD in the same location.

3.0 Usage Notes

This section highlights product limitations and changes to product behavior introduced in this release.

The public services used to register Java JAX-RPC handlers with custom code remain available, but are deprecated as of 7.1.2. release. The new Integration Server-based service handler feature supersedes the implementing of JAX-RPC handlers through custom Java code, and simplifies the task of building SOAP header handlers. New public services are available for registering handlers and for accessing and manipulating the SOAP body or header. The UDDI Registry tree displays all business services you have permission to view. If you are not the primary owner of a business entity, the services of the entity are grouped under Unknown Business Entity. You will not be able to delete these services or publish a provider Web service descriptor to the Unknown Business Entity tree node.

If you run a flow that takes a document type with a recursive structure as input, the document field displays the message "Cannot enter data for recursive document types. Note that in Developer you can use a map step to set the field value or you can link a variable to the field. This issue is fixed in Designer. A recursive document from the output pipeline that is produced by a map step in a flow cannot be deleted as expected. To delete this type of document from the output pipeline, manually delete the map step in the recursion part first, and then delete the recursive document. A Web service descriptor that does not run in pre-8.2 compatibility mode cannot be viewed or edited using Developer. The Web service descriptor appears in the Navigation panel, but the contents of the Web service descriptor are not displayed in the editor. You must use Designer to view and edit the Web service descriptor.

4.0 Fixes and Enhancements

This section describes the fixes and enhancements included in webMethods Developer 8.2 SP1.

4.1 Fixes and Service Packs Included in This Release

This section lists the fixes and service packs for previous releases that have been included into the current release. If only some issues in a fix or service pack have been included, that partially included fix or service pack is not listed here, and those issues are listed separately in Section 4.2 Resolved Issues. See the Knowledge Center section of the Empower Product Support Web site for more information about fixes and service packs.

ID_6.5_SP4_Fix7 ID_7.1.3_Fix1 ID_7.1.3_Fix2 ID_7-1-2_Fix6 ID_7.1.2_Fix7 ID_7.1.2_Fix8 ID_7.1.2_Fix9 ID_7.1.2_Fix10 ID_7.1.2_Fix11 ID_7.1.2_Fix12 ID_7.1.2_Fix13

ID_8.0_SP1_Fix1 ID_8.0_SP1_Fix2 ID_8.0_SP1_Fix3 ID_8.0_SP1_Fix4

4.2 Resolved Issues

This section lists issues that were resolved in this release and that are not included in the fixes and service packs listed in Section 4.1 Fixes and Service Packs Included in This Release. These issues might have been resolved in a fix or service pack that was not included in its entirety into this release, or they might have been resolved since the last fix or service pack was released.

WDP-956 (was 1-1YFCQG) Analyze WSD results in errors if the WSDL document imports an XML schema definition from a location that is not network addressable. When performing WS-I compliance verification, Developer obtains a WSDL string from Integration Server and creates a temporary WSDL file in the following location: <Install_Directory>\Developer\logs. If the WSDL file imports an XML schema definition from a location that is not network addressable, Developer looks for the XML schema definition on the file system of the Developer host computer. When Developer does not find the XML schema definition, the WS-I compliance check fails. This issue is now resolved.

4.3 Enhancements
This section lists the enhancements introduced in this release.

PIE-14950 New service introduced to refine audit log searches. Using the new Integration Server built-in service pub.flow:setCustomContextID, you can assign a custom value to an auditing context. If Integration Server is configured to write service audit data to a database, you can use the custom value as search criteria to locate and view all corresponding service audit records. You search logged audit data using the webMethods Monitor.

4.4 Documentation Changes

This section describes significant changes to the documentation, such as the addition, relocation, or removal of product guides, online help, chapters, or other major content. None.

4.5 Terminology Changes

This section lists terminology that has changed since the last full release of the product. None.

4.6 Deprecated Items

This section lists product functionality that has been deprecated since the last full release of the product. Deprecated Built-In services and APIs are listed in the relevant sections that follow this one. None.

4.7 Added, Removed, Deprecated, or Changed Built-In Services

This section lists Built-In services that have been added, removed, deprecated, or changed since the last full release of the product. None.

4.8 Added, Removed, Deprecated, or Changed APIs

This section lists APIs that have been added, removed, deprecated, or changed since the last full release of the product. None.

5.0 Copyright Information

Copyright 2011 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, United States of America, and/or their licensors. Detailed information on trademarks and patents owned by Software AG and/or its subsidiaries is located at http://documentation.softwareag.com/legal/. Use of this software is subject to adherence to Software AGs 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).

6.0 Support
To obtain support for webMethods Product Suite components, refer to the following resources: Empower Product Support Web site Visit the Empower Web site to learn about support policies and critical alerts, read technical articles and papers, download products, fixes, and service packs, submit feature/enhancement requests, and more. Software AG Developer Community for webMethods Visit the Software AG Developer Community to access additional articles, demos, and tutorials, technical information, samples, useful resources, online discussion forums, and more. DEV-RM-82SP1-20110421