webMethods for Microsoft Package 6.5.2 readme

June 2006

This file provides important information you should read before using webMethods for Microsoft Package 6.5.2.

Documentation about how to install webMethods for Microsoft Package is located in the webMethods for Microsoft Package Installation and User’s Guide. Procedures for upgrading webMethods for Microsoft Package are located in the Upgrade Documentation area on the webMethods Bookshelf. For a complete list of webMethods for Microsoft Package documentation, see section 7.0 Documentation in this readme.

For release information about webMethods for Microsoft Package and other components of webMethods Fabric, see webMethods Fabric Release Notes 6.5. For information about technical support, see the General Support Statement for webMethods Fabric.

Contents

1.0 Critical Information

2.0 Known Issues

3.0 Usage Notes

4.0 Enhancements and Fixes

5.0 Deprecated Items

6.0 Globalization

    6.1 Localization and Certification

    6.2 Configuration

    6.3 Known Globalization Issues

7.0 Documentation

    7.1 Major Documentation Changes

    7.2 Known Documentation Issues

8.0 Copyright Information

    8.1 webMethods Copyright

    8.2 Other Product Copyrights

9.0 Contacting webMethods

10.0 Viewing the readme for the Previous Version

1.0 Critical Information

None.

For late-breaking critical information, refer to the Critical Information area on the webMethods Advantage Web site.

2.0 Known Issues

None.

For other known issues and troubleshooting information about webMethods for Microsoft Package, go to the webMethods Advantage Knowledge Base.

3.0 Usage Notes

Public member variables are not detected when generating Integration Services from a .NET assembly.  However, public accessor methods for member variables are detected.  If you wish to have access to an object's public member variable, it must have public accessor methods.

4.0 Enhancements and Fixes

Enhancements

Native C# Client API:
The Client API is no longer based on the J# language and is now a 100 percent C# implementation.  The use of C# gives improved performance and follows the standard .NET method and variable naming conventions.  The API is now packaged as a single .DLL named wmClientAPI.dll.

The Client API has added support for the following data types:
  IData & IData[]
  byte[]
  object[]

Application domains:
Methods can now run within named application domains.  The use of application domains protects the rogue behavior of one set of assemblies from interfering with other assemblies in a different application domain.  It also allows destruction of an application domain, freeing its resources and any DLL locks it may hold.

Improved assembly scanning:
When you create new .NET services from an assembly, the services are now organized in a folder hierarchy consistent with the namespace of the class.   The assembly introspection has improved logic that better handles base class methods.

Object marshalling improvements:
The handling of Object and Object[] types as method parameters or return values has been improved.  In addition, you can now marshall native .NET objects as XML strings, which can be mapped to and manipulated as Integration Server document types. 

Improved code generation for Visual Studio .NET:
The webMethods add-in for Microsoft Visual Studio .NET now generates object-oriented classes.  These classes can be used by your C# or VB projects to invoke integration services. 

5.0 Deprecated Items

The ability of webMethods Developer to generate C# client code for integration services has been deprecated.  This functionality has been replaced with the webMethods add-in for Visual Studio .NET.

6.0 Globalization

The webMethods for Microsoft Package conforms to the international standards of webMethods, which require operation in any country, locale, or language configuration as listed in the webMethods Installation Guide; support for character encodings; and proper formatting, display, and validation of data (such as number and date formats). These features have been tested in this release and any known issues are listed below.

6.1 Localization and Certification

The webMethods for Microsoft Package is provided with an English user interface, messages, and documentation. Language packs containing support for other languages, when available, can be installed at any time using the webMethods Installer. The webMethods for Microsoft Package 6.5.2 supports simultaneous multi-locale operation.

This version of the package was tested with both English and Japanese versions of the .NET operating environment (CLR), including the passing of non-ASCII data values. .NET services invoked through the Microsoft Package have their default thread CultureInfo set by the "Locale Policy" property you apply to the service in webMethods Developer. By default this is the session locale of the user invoking the service, which may be different from either the .NET host environment or the Integration Server's JVM default locale. You can also set the property to a specific value.

6.2 Configuration

If you expect to display non-English data in your webMethods tools, make sure an appropriate font is installed in your operating environment. If you see hollow boxes or black squares where you expect to see non-English data, modify your JRE font.properties file to reference an appropriate font. For information on modifying your font.properties file, go to Sun's Java website. For instructions, see:

http://java.sun.com/j2se/1.4.2/docs/guide/intl/fontprop.html

http://www.unicode.org/help/display_problems.html

6.3 Known Globalization Issues

None.

7.0 Documentation

For webMethods for Microsoft Package 6.5.2 technical documentation, go to the <Integration_Server_Directory>/packages/WmDotNet/pub/doc directory or the webMethods Advantage Bookshelf. These manuals are provided as PDF files:

webMethods for Microsoft Package Client API Programmers Guide 6.5.2

webMethods for Microsoft Package Installation and User’s Guide 6.5.2

webMethods for Microsoft Package Upgrading from 6.5 to 6.5.2

To view the documentation, you must have Adobe Acrobat Reader 4.0 or later.

7.1 Major Documentation Changes

None.

7.2 Known Documentation Issues

None.

8.0 Copyright Information

8.1 webMethods Copyright

webMethods Access, webMethods Administrator, webMethods Broker, webMethods Dashboard, webMethods Developer, webMethods Fabric, webMethods Glue, webMethods Installer, webMethods Integration Server, webMethods Mainframe, webMethods Manager, webMethods Modeler, webMethods Monitor, webMethods Optimize, webMethods Portal, webMethods Servicenet, webMethods Trading Networks, and webMethods Workflow are trademarks of webMethods, Inc. webMethods and the webMethods logo are registered trademarks of webMethods, Inc.

All other marks are the property of their respective owners. Copyright (c) 2006 by webMethods, Inc. All rights reserved, including the right of reproduction in whole or in part in any form.

8.2 Other Product Copyrights

This product includes software developed by Microsoft Corporation.

9.0 Contacting webMethods

Authorized technical support contacts can reach webMethods Customer Care for support via:

Web:      webMethods Advantage  webMethods online support center

E-mail:   support@webMethods.com

Phone:   North America  +1-888-222-8215 or +1 703 460 2584
Europe         +800 963 84-637 or +31 20 77 83 640
Asia Pacific   +1 1-800-088-880 or +61-2-8913 1111
Japan          0120-979-762 (Toll Free in Japan
               or +81-3-6229-3751

In addition, self-service support is available in the webMethods Advantage Knowledge Base and in the webMethods Advantage Customer Forums.

10.0 Viewing the readme for the Previous Version

To view information about the previous release of webMethods for Microsoft Package, see the previous readme on the webMethods Bookshelf.

MSP-RM-652-20060630