************************************************************************ webMethods EntireX 8.

1 SP2 for UNIX and Windows Update, with Changes for Hotfix 5 and Hotfix 20 Software AG, May 25, 2010 Software AG Uhlandstrasse 12 64297 Darmstadt Germany ************************************************************************ Table of Contents ================= 1 Scope 1.1 UNIX Platforms 1.2 Windows Platforms 2 New Functionality 3 Changes 3.1 Web Services Wrapper 4 General Dependencies 5 Product Installation 5.1 5.2 5.3 5.4 General Information Installation under Windows Vista and Windows 2008 Typical Installation over Existing EntireX Version Installation with Core and Administration Components Only

6 Known Problems 6.1 Broker 6.2 Examples 6.2.1 UNIX Examples 6.2.2 Windows Examples 6.2.3 Natural RPC Client Examples 6.3 Micro Focus COBOL 6.4 Fields with Format T 6.5 System Management Hub 6.6 Starting the Designer on Linux 6.7 Workbench 6.7.1 Java Wrapper for Natural Business Services 6.7.2 Natural Wrapper 6.7.3 IDL Extractor for COBOL 6.7.4 C Wrapper 6.7.5 COBOL Wrapper 6.7.6 PL/I Wrapper 6.7.7 IDL Editor 6.7.8 XML Tester 6.7.9 COBOL Parameter Selection Wizard 6.7.10 Java Wrapper 6.8 Other Problems 6.8.1 EntireX Mini Runtime 6.8.2 SAGTRPC User Exit 6.8.3 WebSphere MQ RPC Server and WebSphere MQ Listener 6.9 Attach Manager 7 Solved Problems 7.1 Examples 7.2 Workbench 7.2.1 IDL Extractor for COBOL

7.2.2 IDL Extractor for Natural 7.2.3 IDL Extractor for WSDL 7.2.4 IDL Editor 7.2.5 webMethods Integration Server Wrapper 7.2.6 Software AG IDL Extractor for webMethods Integration Server 7.2.7 Web Services Wrapper 7.2.8 Java Wrapper 7.2.9 COBOL Wrapper 7.2.10 XML Tester 7.3 XML RPC Server 7.4 System Management Hub 7.5 Other problems 8 Restrictions 8.1 New TRACE-LEVEL Attributes 9 Documentation 9.1 Software AG Documentation Websites 9.2 Viewing the Documentation under Windows XP SP2 ************************************************************************ 1 Scope ======= This document describes issues relevant for the platforms listed below. Issues specific to z/OS users are described in a separate readme delivered with EntireX on this platform. 1.1 UNIX Platforms -----------------SUSE Linux Enterprise Server 10 and 11 for x86 (32-bit) SUSE Linux Enterprise Server 10 and 11 for AMD64 and EM64T (x86-64) Red Hat Enterprise Linux 5 for x86 (32-bit) Red Hat Enterprise Linux 5 for AMD64 and EM64T (x86-64)

Before you install EntireX, we suggest you install the maintenance level or patches recommended by the system vendor. See also section 'UNIX Prerequisites' in the EntireX Release Notes before you install. 1.2 Windows Platforms --------------------Windows Windows Windows Windows Windows Windows Windows Windows Windows Server 2003 Standard Edition (32-bit) Server 2008 Standard Edition (32-bit) * 2003 Enterprise Edition (32-bit) 2008 Enterprise Edition (32-bit) * XP Professional (32-bit) Vista (32-bit) 7 Professional (32-bit) 7 Enterprise (32-bit) 7 Ultimate (32-bit)

(*) EntireX on Windows Server 2008 (Standard and Enterprise editions) is a 32-bit version, but it is also supported on 64-bit Windows Server 2008 machines. This means that EntireX can be installed on this platform, but can only run in 32-bit mode. 2 New Functionality ===================

See the Release Notes in the EntireX documentation for a detailed list of new functionality with this release. For EntireX Workbench enhancements for IDL Extractor for Integration Server and Integration Server Wrapper, see the webMethods EntireX Adapter documentation. 3 Changes ========= 3.1 Web Services Wrapper -----------------------The Web Services Wrapper now by default generates XML Schema definitions in the WSDL, which preserves length restrictions of strings. For example, an alphanumeric of length 10 in the IDL (A10) results in the the following XML Schema in the WSDL: <xsd:simpleType> <xsd:restriction base="xsd:string"> <xsd:length value="10"/> </xsd:restriction> </xsd:simpleType> If you prefer just "xsd:string" without length restriction in the XML Schema definition, you can uncheck the preference 'Generate Simple Types' under 'Window > Preferences > Software AG > EntireX > Web Services Wrapper > Mapping'. Additionally, the Web Services Wrapper using WSDL now by default does not make XML Schema elements unique (by appending numbers to the names). If you need unique XML Schema element names you can check the preference 'Make XML Schema element names unique' under 'Window > Preferences > Software AG > EntireX > Web Services Wrapper > Mapping'. 4 General Dependencies ====================== See the Release Notes in the EntireX documentation. 5 Product Installation ====================== 5.1 General Information ----------------------Before you install EntireX, all EntireX applications (brokers and RPC servers) must be stopped. Do not stop the EntireX Broker Administration Service. 5.2 Installation under Windows Vista and Windows 2008 ----------------------------------------------------We recommend switching off UAC (User Access Control) before you start installation under Windows Vista and Windows 2008. Alternatively, make sure that the Designer is installed by a user with Administrator permissions. webMethods EntireX fulfills the "Works with Windows Vista" requirements. 5.3 Typical Installation over Existing EntireX Version -----------------------------------------------------If EntireX 8.1 SP1 is already installed and you choose Typical Installation (either EntireX or NaturalONE), the latest version of

EntireX is not selected automatically. Open the EntireX product node in the installation tree and select manually the EntireX components you want to install. This does not apply if EntireX is not yet installed. 5.4 Installation with Core and Administration Components Only ------------------------------------------------------------If EntireX 8.1.1 is installed with only Core and Administration components (and not the Broker component), the autostart option for the EntireX Default Broker does not work when upgrading to 8.1.2 and additionally installing the Broker component. Workaround: Use the System Management Hub administration and turn on Autostart using the context menu of ETB001. After that, the broker can be also started from the context menu. If you want to use the Default Broker with SSL, you need to copy the three .pem files (key-file.pem, key-store.pem and trust-store.pem) from the EntireX/config/etb directory to the EntireX/config/etb/ETB001 directory. 6 Known Problems ================ 6.1 Broker ---------If you provide invalid credentials for a broker with SECURITY=YES and AUTHENTICATION-TYPE="iaf://...", an empty dialog box appears instead of the message "Invalid credentials". Note that the credentials are invalid and choose 'Close'. 6.2 Examples -----------6.2.1 UNIX Examples - A warning may be issued when you build the examples under Solaris, depending on the compiler version. The option xarch=v9 is deprecated with compiler version 5.9. However, because EntireX supports older compiler versions, this message cannot be avoided because the old compilers do not recognize the new option. - The executable callableserver in directory EntireX/examples/RPC/basic/example/CserverCallable is wrongly linked. Call the make command in this directory to link the example before you use it. 6.2.2 Windows Examples - <EXXDIR>\examples\RPC\basic\businessDemo\Cserver problem: In the Visual Studio projects, the include path to the <EXXDIR>\include Directory must be changed. Two additional "..\" levels must be added to find erx.h in the EntireX\include directory. The path in server.bat also needs two additional "..\" to find the rpcserver in the EntireX\bin directory. 6.2.3 Natural RPC Client Examples With the Natural RPC client examples CALCCLT.NSP and SQRECLT.NSP in folder <EXXDIR>\examples\RPC\basic\NaturalClient and the SENDCLT.NSP reliable RPC example in folder <EXXDIR>\examples\RPC\reliable\NaturalClient it is not possible to set the RPC user ID and RPC password. This may be required if you are using a Natural RPC server that is running with Natural Security or the impersonation feature of the Batch, IMS or CICS RPC Server. In the map of the examples, only EntireX Authentication (user ID and password for the broker) can be entered.

Use USR1071N or USR1071X from library SYSEXT to set user ID and password for RPC servers. Refer to the library SYSEXT for more information. 6.3 Micro Focus COBOL --------------------- Micro Focus COBOL RPC clients cannot be used with the EntireX Mini Runtime. EntireX core files must be installed. - Unicode support is not provided for the EntireX Micro Focus COBOL RPC server on UNIX platforms. Unicode support is available for - Micro Focus COBOL RPC clients on UNIX and Windows - Micro Focus COBOL RPC server on Windows - The EntireX Micro Focus COBOL RPC server does not support standard Windows DLLs or standard shared libraries (*.sl) objects (*.so) linked dynamic single-threaded with the Micro Focus COBOL runtime. Use static linking or dynamic multithreaded linking. - The COBOL Wrapper used in combination with the EntireX Micro Focus COBOL RPC Server does not support IDL structs containing IDL unbounded arrays or IDL unbounded groups. 6.4 Fields with Format T -----------------------When using the Natural tester for testing subprograms that use Natural TIME fields, please note that any time precision after the second is not included in the test editor. This may result in incorrect data being displayed and/or invalid data being passed to the subprogram at execution time. 6.5 System Management Hub ------------------------- Incorrect attribute status of a remote broker in SMH SMH displays incorrect values for attributes SERVICE-UPDATE and AUTOLOGON for a remote broker. 6.6 Starting the Designer on Linux ---------------------------------Problems with starting Designer on Linux In some cases there may be a problem with starting the Designer on Linux. Eclipse 3.4.2 has problems with the XULrunner 1.9.1. A workaround could be to install XULrunner 1.9.0 and setting the org.eclipse.swt.browser.XULRunnerPath property to point at XULrunner 1.9.0. For more information, see the Eclipse documentation at http://www.eclipse.org/swt/faq.php#specifyxulrunner . 6.7 Workbench ------------6.7.1 Java Wrapper for Natural Business Services - Java Client Generation for Business Services If you generate a Java client form a Business Service (.bsrv file), please make sure the underlying Natural subprogram data areas do not contain direction modifier comments such as "/* in" or "/* out" and the "BY VALUE" (IN direction) option on the parameter fields. These are currently not supported, and the resulting generated code will contain compile errors if they are used. 6.7.2 Natural Wrapper - When generating Natural clients from Software AG IDL, the following problems may occur: - STOWing the generated Natural objects into a remote RPC Environment is not supported in this version. Workaround: Use SAVE and catalog (compile) the generated Natural objects directly in the target Natural Library, for example with

the CATALL command. - Reserved Natural words as IDL parameter names are not supported with - NaturalONE 8.1.1 - remote RPC Environment and RPC server in Windows and UNIX using Natural version 6.3.8 Workaround: Modify the IDL parameters, so there is no conflict with Natural reserved words. Note: Reserved Natural words are supported in a remote RPC Environment in z/OS with Natural version 4.2.6 SP 2 using SAVE. - With the Natural RPC client examples (*.NSP) it is not possible to set the RPC user ID and RPC password. This may be required if you are using a Natural RPC server that is running with Natural Security. In the map of the examples, only EntireX Authentication (user ID and password for the broker) can be entered. Use USR1071N or USR1071X from library SYSEXT to set user ID and password for Natural RPC servers. Refer to the library SYSEXT for more information. This is the same problem as described under 'Natural RPC Client Examples' above. - The Natural Wrapper does not map IDL parameters to valid Natural parameters if the first character is one of -, _, /, @, $, 0-9 and lowercase a-z. Workaround: Modify your IDL accordingly before using the Natural Wrapper. If the IDL was extracted using the IDL Extractor for Natural, uncheck the check box 'Replace special characters in parameter names by underscore' to keep the original parameter names. 6.7.3 IDL Extractor for COBOL - In the COBOL Parameter Selection Wizard: Do not select single Redefine Paths. Always select the complete Redefine group and perform the mapping of the desired redefine path in the COBOL Mapping Editor. - When the COBOL Mapping Editor is reopened, the icons indicating the direction of a parameter are not loaded correctly. There is currently no workaround available. - In the COBOL Mapping Editor: Do not rename a program with function "Map to operation". - The IDL Extractor for COBOL does not support ODO objects correctly if they are members (child objects) of a group without any non-ODO objects. Example: 1 ODO-GROUP. 2 ODO-OBJECT-1. 2 ODO-OBJECT-2. 1 ODO-SUBJECT OCCURS 1 TO 10 DEPENDING ON ODO-OBJECT-1 IN ODO-GROUP. In such a case, the ODO-GROUP should offer SUPPRESS only. Workaround: SUPRESS the ODO-GROUP manually. - With interface types 'CICS with DFHCOMMAREA calling convention' and 'CICS with DFHCOMMAREA large buffer interface', it is possible that you are not able to set the IDL directions as you wish. This is the case if the COBOL data structures from which you are extracting are defined with a series of COBOL groups: 01 DFHCOMMAREA. 02 GROUP-2. 03 GROUP-3. 04 FIELD1 PIC X. 04 FIELD2 PIC X. In this example, IDL directions might be required for fields FIELD1 and FIELD2. However, the IDL Extractor for COBOL only allows you to set the IDL direction for GROUP-2. Workaround: Remove the series of COBOL groups between DFHCOMMAREA and the fields manually before extraction. - Do not use the function 'Edit COBOL Mapping ...'. If your server mapping (SVM) file contains suppressed parameters, the SVM file will be incorrect. 6.7.4 C Wrapper - Callable RPC Server

On Windows and UNIX, the Callable RPC Server is wrongly linked and therefore cannot be used directly after installation. To use the server, relink it with the provided makefile. For more information on how to build, see the corresponding readme.txt file. On Windows, the server example DLLs for the basic example (DEXAMPLE.dll and EXAMPLE.DLL) must also be built, see above. - There is no multithreaded client example delivered. 6.7.5 COBOL Wrapper An RPC client built with the COBOL Wrapper does not send the IDL library and IDL program to the broker for accounting purposes. 6.7.6 PL/I Wrapper The PL/I Wrapper for the client side generates a copybook containing all prototypes of the client interface objects. If this member is included in a client application (which is the normal case) and not all client interface objects of the library are referenced in the same client application, UNRESOLVED EXTERNALs are given by the linkage editor. Workaround: Remove or comment out prototypes you do not need. Alternatively, you can remove or comment out the IDL programs in the IDL file. 6.7.7 IDL Editor - Operations on the IDL text with the outline view's context menu (e.g. 'New', 'Delete', 'Rename...', 'Properties') may result in corrupt IDL syntax. This is a known problem which will be fixed in a future version or patch. To avoid this problem, save the changes between two operations with the context menu. - The IDL Editor allows the notation of unbounded arrays and groups with a lower bound not equal to 1, e.g. the following format ../5:V, 10:V although this is not valid IDL syntax. Most wrappers ignore the lower bound and still use a lower bound of 1, so this is not a real problem. If there is a problem with such an IDL, correct your IDL and set a value of 1. 6.7.8 XML Tester If you use the XML Tester with an AAR file that does not contain an EntireX service (e.g. a Web service generated with Natural business service), an error occurs if a sample generation is selected. 6.7.9 COBOL Parameter Selection Wizard In the COBOL Parameter Selection Wizard, do not select single Redefine Paths. Always select the complete Redefine group, and perform the mapping of the desired Redefine path in the COBOL Mapping Editor. 6.7.10 Java Wrapper The folder for the generated Java source files is wrong if you generate Java source files in different projects in one session. The source folder of the first project you used in that session is used for all projects. Workaround: restart Software AG Designer to generate source files in a second project. 6.8 Other Problems -----------------6.8.1 EntireX Mini Runtime If you have only the EntireX Mini Runtime installed and you use one of the following components, the component might fail due to an incorrect search path for shared libraries.

C Wrapper .NET Wrapper DCOM Wrapper Broker ActiveX Control

Workaround: Copy the broker32.dll in %CommonProgramFiles%\Software AG to broker.dll. Hotfix 8.1.1.2 is now available. Install this hotfix to solves this problem. 6.8.2 SAGTRPC User Exit A new conversion module using the SAGTRPC user exit approach cannot be built. The resulting module does not work and cannot be used. Workaround: Use your existing conversion module built with a previous EntireX version. 6.8.3 WebSphere MQ RPC Server and WebSphere MQ Listener If WebSphere MQ version 7 is used, unpredictable results and error situations may occur. The Java API of MQ version 7 is not compatible with version 6 that is used by EntireX. You can communicate with an MQ Server version 7, but you need to use the MQ version 6 JAR files together with the EntireX components. 6.9 Attach Manager -----------------If you terminate a registered service using the System Management Hub it should terminate all servers offering that service. An Attach Manager should not be affected by this terminate because it does not offer that service itself but just the task to launch an appropriate server. In the current version, however, an Attach Manager is also terminated. A solution of this problem is scheduled for next correction level. 7 Solved Problems ================= 7.1 Examples ------------ 'example.dll' and 'dexample.dll' were missing The missing dlls have been added in 'EntireX\examples\RPC\basic\example\Cserver' directory. - Wrong EXAMPLE values in startjavaserver script In the script 'EntireX\smh\scripts\startjavaserver.bat' and 'EntireX/smh/scripts/startjavaserver.bsh' the wrong EXAMPLE values have been corrected. 7.2 Workbench ------------7.2.1 IDL Extractor for COBOL - IDL Extractor for COBOL: extracting ODO leads to syntax error The IDL Extractor for COBOL did not support qualified ODO objects. Example: "01 ODO-SUBJECT OCCURS 1 TO 10 DEPENDING ON ODO-OBJECT IN ODO-OBJECT-GROUP." - IDL Extractor for COBOL failed with source files containing ++INCLUDE or -INC statements When the include statement started from column 8 the statement was ignored and thus no copy book was included. The IDL Extractor for COBOL now supports CA Librarian -INC and CA Panvalet ++INCLUDE statements in the following way with this version:

- The CA Librarian -INC statements must start in column 1 and end in column 4, followed by one or more space and the name of the member to include. - The CA Panvalet ++INCLUDE statements can begin from column 1 through column 12. - IDL Extractor for COBOL: IDL incomplete when extracting from a remore environment When extracting from a remore source, some lines got lost. - Web Services Wrapper The Web Services Wrapper generates schema definitions with length restrictions in the WSDL by default for fixed length alphanumeric IDL data types (An). The option 'Generate simple types' in the Designer preferences 'Software AG > EntireX > Web Service Wrapper > Mapping' is now checked by default. 7.2.2 IDL Extractor for Natural - Unknown Host Exception Modifed parameters in a Natural RPC environment are not used when trying again to create an IDL file. 7.2.3 IDL Extractor for WSDL - Resolving imported/included relative file name. - Consuming nested XML Schema using SOAP headers and SOAP - XML Mapping Editor warnings 7.2.4 IDL Editor - Set the direction of an IDL Parameter using the outline view: Update the relevant IDL text inside the IDL Editor. - Duplicate Java parameter names are not marked with problem marker. This is relevant only for the Java Wrapper. 7.2.5 webMethods Integration Server Wrapper - The Integration Server Wrapper is compatible with EntireX Adapter for ESB version 7.2 and 8.0. 7.2.6 Software AG IDL Extractor for webMethods Integration Server - The IDL Extractor for Integration Server is compatible with EntireX Adapter for ESB version 7.2 and 8.0. 7.2.7 Web Services Wrapper - Web Services Wrapper generates schema definitions with length restrictions in the WSDL by default for fixed length alphanumeric IDL data types (An). The option "Generate simple types" in the Designer preferences 'Software AG > EntireX > Web Service Wrapper > Mapping' is now checked by default. - Unable to generate WSDL in some configurations. 7.2.8 Java Wrapper - Add IMS BMP interoperability. 7.2.9 COBOL Wrapper - Correct operating system is used for properties page action 'Restore Defaults'. 7.2.10 XML Tester - Fixed NPE when quick calling with invalid AAR or XMM file. XML Schema documents specified by sections with mixed XML Schema styles, fault definitions. on XMM files.

7.3 XML RPC Server ------------------ XML server performance degrades The performance of the XML server has been significantly improved. - XML Runtime: V-Array with non-defined values The usage of an unbounded group array with non-defined values in all subelements results in ArrayOutOfBoundsException. - NullPointer Exception in XML RPC Server XML/SOAP RPC Server throws a NullPointerException if receiving a fault document with activated trace. - XML RPC Server Error 2000 0087 XML/SOAP RPC server ignores the usage of repository in configuration file. - XML RPC Server deployment Deployment of XML mappings into XML RPC server is now enabled by default. The property entirex.server.allowdevelopment is set to TRUE by default in file 'EntireX/config/entirex.xmlrpcserver.properties'. 7.4 System Management Hub ------------------------- Secured Broker shows information in SMH without setting credentials Now these informations can be displayed only after setting the credentials. 7.5 Other problems ------------------ Visual Studio Add-ins did not work for different users than the installation user The Visual Studio Add-ins now work for any user. 8 Restrictions ============== 8.1 New TRACE-LEVEL Attributes -----------------------------Currently the new transport-specific TRACE-LEVEL attributes (for transport methods Entire Net-Work, TCP/IP and SSL) cannot be modified using System Management Hub or Broker Command Services. This functionality will be provided in a future version. 9 Documentation =============== 9.1 Software AG Documentation Websites -------------------------------------You can also access the documentation from the Software AG websites: http://documentation.softwareag.com https://empower.softwareag.com 9.2 Viewing the Documentation under Windows XP SP2 -------------------------------------------------With Service Pack 2 (SP2) for Windows XP and Service Pack 1 (SP1) for Server 2003, Microsoft introduced a range of powerful new security features that restrict active content that runs locally on the user's computer. Active content includes ActiveX controls, Java applets and JavaScript. Software AG's documentation Web pages contain some JavaScript, and the

SEARCH and CONTENTS capabilities are implemented as Java applets. As a result, when viewing documentation Web pages that reside on the user's PC, users of Internet Explorer and Mozilla Firefox are informed that active content is blocked. Users must explicitly and repeatedly allow active content if they wants to make use of the documentation's full navigation features. Note that this behavior is only observed when reading Web pages installed locally on the user's PC, including those on CD in the PC's CD-ROM drive. The active content for which Software AG is responsible, that is, the JavaScript code in our HTML documentation pages, will not harm the user's computer. The risk in using the navigation applets is negligible: Software AG has received no reports from users concerning any harm caused to a computer by the applets. We therefore suggest that when reading Software AG documentation in a local context, the user allow active content via the Security settings in the browser (with Internet Explorer, usually found under Tools > Internet Options > Advanced). Full details of alternatives can be found on the home page of the suppliers of the navigation applets: http://www.phdcc.com/xpsp2.htm ======================================================================== Copyright (C) 1997-2010 Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, United States of America, and/or their licensors. ======================================================================== EXX-81SP2-20100525