This document covers the following topics:
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| EntireX Broker | x | x | x | x | x | x | x | x | x | x | x | x | x | x | ||
| EntireX Workbench | x | x | x | x | x | |||||||||||
| EntireX RPC | ||||||||||||||||
| Batch RPC Server/Client | x | x | ||||||||||||||
| C RPC Server/Client | x | x | x | x | x | x | x | x | x | x | x | x | ||||
| CICS RPC Server/Client | x | |||||||||||||||
| IMS RPC Server/Client | x | |||||||||||||||
| Java RPC Server/Client | x | x | x | x | x | x | x | x | x | x | x | x | ||||
| XML/SOAP RPC Server/Client | x | x | x | x | x | x | x | x | x | x | x | x | ||||
| WebSphere MQ RPC Server | x | x | x | x | x | x | x | x | x | x | x | x | ||||
| WebSphere MQ Listener, | x | x | x | x | x | x | x | x | x | x | x | x | ||||
| DCOM RPC Client (1) | x | |||||||||||||||
| .NET RPC Server/Client (1) | x | |||||||||||||||
| RPC-ACI Bridge | x | x | x | x | x | x | x | x | x | x | x | x | ||||
| XML/SOAP Listener | x | x | x | x | x | x | x | x | x | x | x | x | ||||
| EntireX ACI | ||||||||||||||||
| Broker Stubs | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x | x |
| Java ACI | x | x | x | x | x | x | x | x | x | x | x | x | ||||
| .NET ACI | x | |||||||||||||||
| ActiveX Control | x | |||||||||||||||
| EntireX DCOM and DCOM Security | x | x | x | x(3) | ||||||||||||
| System Management Hub | x | x | x | x | x | x | x | x | x | x | x | |||||
| Broker Agent | x | x | x | x | x | x | x | x | x | x | x | x | ||||
| JMS Support | x | x | x | x | x | x | x | x | x | x | x | |||||
| IAF | x | x | x | x | x | x | x | x | x | x | x | x | ||||
| Attach Manager | x(2) | x | x | x | x | x | x | x | x | x | x | x |
In accordance with the license agreement you concluded with Software AG, your EntireX license includes either full functionality or specific EntireX components.
| (1) | Application wizard for Visual Studio .NET 2005 also provided in installation kit. |
| (2) | The attach services supplied with Broker Services are still supported in this version but will be replaced in the future. |
| (3) | Security component only because DCOM is part of the Windows operating system. |
Software AG provides support for the operating system versions supported by their respective manufacturers. Generally, when an operating system provider stops supporting a version of an operating system, Software AG will stop supporting that operating system version as of the next system maintenance (SM) level delivered by Software AG. Although it may be technically possible to run a new version of EntireX on an old operating system, Software AG cannot continue to support operating system versions that are no longer supported by the system's provider.
Software AG plans to provide support for previous versions of EntireX and predecessor products of EntireX as follows:
With this release of EntireX, product versions not listed below are no longer supported.
| Product Release | Platform | Release Date | End-of-Maintenance Date |
|---|---|---|---|
| EntireX Communicator 6.1 | OpenVMS Alpha | August 2001 | EntireX 6.1 will continue to be supported on this platform for as long as this platform itself is supported by Software AG. |
| EntireX Communicator 7.1 | Windows, Solaris, z/OS, Linux Intel, AIX, HP-UX | June 2003 | November 30, 2005 |
| OS/390 | June 2003 | September 30, 2004 | |
| z/OS stubs EXAAPSB, EXAAPSC | June 2003 | June 30, 2006 | |
| Linux S/390 | October 2003 | April 30, 2006 | |
| i5/OS - AS/400-RISC | September 2004 | ||
| BS2000/OSD | September 2005 | ||
| EntireX Communicator 7.2 | Windows, Solaris, Linux Intel | November 2004 | November 30, 2007 |
| z/OS | November 2004 | May 31, 2008 | |
| AIX, HP-UX | November 2004 | December 31, 2007 | |
| Linux IBM zSeries 64 | April 2005 | November 30, 2007 | |
| z/VSE | February 2006 | ||
| EntireX Communicator 7.3 | Windows 2000 | November 2006 | December 31, 2008 |
| Windows, Solaris, Linux Intel 32-bit | November 2006 | February 28, 2009 | |
| Linux Intel 64-bit | February 2007 | April 30, 2009 | |
| z/OS | November 2006 | August 31, 2009 | |
| AIX, HP-UX | December 2006 | ||
| Linux IBM zSeries 64 | February 2007 | ||
| VM/CMS 5.3 - IBM | March 2007 | ||
| webMethods EntireX 8.0 | Windows, Solaris, Linux Intel 32-bit | February 2008 | |
| z/OS | February 2008 | ||
| Linux Intel 64-bit | April 2008 |
If you have access to ServLine24, you can also see the detailed and most recent information in the EntireX Roadmap.
| Operating System | EntireX Version |
Notes |
|---|---|---|
| z/OS V1.8 | 8.0 | |
| z/VSE V3.1, V4.1 | 7.2.2 | |
| BS2000/OSD 4.0, 5.0, 6.0, 7.0 | 7.1 | |
| z/VM V5.2, V5.3 | 7.3 | |
| OpenVMS Alpha | 6.1 | |
| SUSE Linux Enterprise Server 10 for IBM zSeries (64-bit) | 8.0 | Planned for later |
| RedHat Enterprise Linux 5 for IBM zSeries (64-bit) | 8.0 | Planned for later |
| Solaris SPARC 9 and 10 (64-bit) | 8.0 | |
| HP-UX 11.23 (64-bit) for PA-RISC HP-UX 11.i v3 (64-bit) for PA-RISC |
8.0 | Planned for later |
| HP-UX 11i v3 for Itanium 2 | 8.0 | Planned for later |
| AIX 5.3 (64-bit) AIX 6.1 (64-bit) |
8.0 | Planned for later |
| i5/OS 5.3-AS/400-RISC i5/OS 5.4-AS/400-RISC |
7.1 | |
| SUSE Linux Enterprise Server 10 for x86 (32-bit) | 8.0 | |
| SUSE Linux Enterprise Server 10 for AMD64 and EM64T (x86-64) | 8.0 | |
| Red Hat Enterprise Server Linux AS 4 and 5 for x86 (32-bit) | 8.0 | |
| Red Hat Enterprise Server Linux AS 4 and 5 for AMD64 and EM64T (x86-64) | 8.0 | |
| Windows Server 2003 Standard and Enterprise editions (32-bit) Windows XP Professional (32-bit) Windows Vista (32-bit) |
8.0 |
The following functionality is no longer supported in version 8.0 of webMethods EntireX:
Entire Net-Work on Windows and UNIX.
The EntireX CORBA Gateway and the EntireX Broker ACI for CORBA.
Broker Services:
WebSphere MQ is supported with the new EntireX WebSphere MQ RPC Server. See section EntireX WebSphere MQ RPC Server
The Broker Services APPC Adapter for LU6.2 has been retired. We recommend using the standard EntireX functionality. Possible migration paths can vary and should be determined based on your projects. See Introduction to EntireX for an overview of EntireX.
Generation of web services from EntireX DCOM type libraries and the Apache Axis module that exposes EntireX DCOM objects as web services.
The TCP/IP-based transport interface using secure sockets based on Sun's JavaTM Secure Socket Extension (JSSE) version 1.0.2 and on IBM's JavaTM Secure Socket Extension (JSSE)version 1.0.2. SSL support is now part of Java.
Broker Agent library BrokerAgent.dll for native communication to Broker 2.1.
The Workbench starter jwiz.exe. Use the
script workbench.bat or the EntireX Workbench
startup command line instead of jwiz.exe. See also
Using EntireX
Workbench from a Command Line.
XML/SOAP Wrapper: XML Adapters (version 6.x) is no longer supported by XML/SOAP Runtime.
UDDI version 1 is no longer supported.
The Brokervb.dll is no longer delivered.
On Windows and UNIX, the persistent store B-tree has been retired. This functionality is provided by a production-safe embedded store, which has been available since version 7.3. See Migrating the Persistent Store under UNIX | Windows.
C Wrapper. The feature to redirect the generated output to standard out or any file has been retired. The AUTOCONV function which offers the mapping functionality is integrated into the C Wrapper of the EntireX Workbench, the autconv modules have been retired.
The enhancement of the PATH variable to include the runtime modules of ...\Common Files\Software AG\ for the RPC and ACI applications.
For the COBOL Wrapper the deprecated options APOST and QUOTE for enclosing string literal has been retired.
COBOL RPC clients now support only Natural RPC Servers of Natural 4.1.2 (z/OS) or Natural 6.1 (Windows/UNIX) or above.
IDL Extractor for Natural now supports only the Natural RPC Servers of Natural 4.1.2 (Mainframe) or Natural 6.1 (Windows/UNIX) or above.
The secondary subscriber store (SSTORE) is no longer supported. We recommend you use the PSTORE persistent store to store your subscriber data, by setting the Broker-specific parameter SUBSCRIBER-STORE=PSTORE.
EntireX RPC BMQ Bridge. We recommend you use the new Reliable RPC functionality.
The Software AG IDL Extractor for COBOL no longer supports extraction in command-line mode. The IDL Extractor for COBOL works only within the EntireX Workbench. This was the only viable means of providing user-driven COBOL-to-IDL mapping.
All modules of the EXS libraries are not supported with this release. If you use one or more modules from the EXS library for you own applications, we recommend you migrate to Natural Security (NSF).
The EntireX Security Gateway (SAF Gateway) is included into the Broker Access modules. The security access is handled solely by the Broker.
The attach services supplied with Broker Services are still supported in this version but will be replaced in the future.
Broker Services documentation is provided as PDF. Please note that this documentation also includes features that have been dropped.
Java 1.4
The architecture of the EntireX XML/SOAP Listener (formerly known as XML Servlet) and EntireX XML/SOAP RPC Server changed with version 8.0. The previous version worked as a web application running directly in the web server; the current version works as part of Software AG Common Web Services Stack, which is a web application running in a web server. This change has impact on configuration, packaging and deployment of EntireX web services.
The used XML parser has changed. XML/SOAP Wrapper uses XMLStreamParser, so the classpath must contain the JAR files of XMLStreamParser. The EntireX installation comes with stax-api.jar and wstx-asl.jar. The two XMLStreamParser JAR files are located in <EntireX Home>/classes.
The XML/SOAP Listener requires a Web Services Stack installation. The Web Services Stack web application is the container of XML/SOAP Listener, in previous versions the XML/SOAP Listener (formerly referred to as XMLServlet) was a web application itself. The file entirex.jar containing the XML/SOAP Runtime is placed in directory lib of the Web Services Stack web application. EntireX web service is created using the with XML Mapping Editor as in previous versions and with a Packaging Wizard to build an AAR file. The AAR file contains all information for this web service and must be deployed to the web application.
The WAR file entirex-forward.war is provided for using the existing URL of an older XML/SOAP Runtime for example "host:8080/entirex/xmlrt".
See Migration with entirex-forward.war in Administration of the EntireX XML/SOAP Listener UNIX | Windows.
The XML/SOAP RPC Server requires the directory of a Software AG Common Web Services Stack installation. The JAR file
wsstack-client.jar located in <WS_STACK_HOME>/lib must be added to
classpath. File entirex.jar from EntireX
installation must also be present in classpath. The configuration
file can be used as before. To make use of the latest features, some extensions
in configuration file are required. See documentation for more
information.
Note:
The migration procedure described in here is only needed if you did
not perform a persistent store cold start after installing Broker version 8.0.
Run the migration only if you want Broker version v80 to process units of work
(UOWs) created with Broker version 7.1 or 7.2. We recommend you make a backup
copy of the persistent store before running the migration.
Add attribute RUN-MODE = MIGRATION to
the DEFAULTS = BROKER section of your Broker attribute file to
instruct Broker to migrate the existing UOWs from version 7.1 or 7.2 format to
version 8.0 format. The Broker task will automatically stop when it has
finished the migration procedure.
If the PSTORE contains UOWs created with Broker version 7.1 or 7.2 and
UOWs created with Broker version 8.0, you need to define the date and time of
the change to Broker version 8.0, using Broker attributes
PSTORE-CHANGE-DATE=yyyy.mm.dd and
PSTORE-CHANGE-TIME=hh:mm:ss in the
DEFAULTS = BROKER section of the attribute file.
If TRACE-LEVEL = 1 is specified in the
Broker attribute file, the SYSOUT data set of the Broker output files will
contain a migration report headed by message ETBM0171 Migration
Processing Report.
See the following sample attributes for the PSTORE migration:
DEFAULTS = BROKER PSTORE = HOT PSTORE-CHANGE-DATE = 2008.01.16 PSTORE-CHANGE-TIME = 18:15:00 RUN-MODE = MIGRATION TRACE-LEVEL = 1
After successful migration, remove the line "RUN-MODE =
MIGRATION" line from the Broker attribute file and restart
Broker to consume the units of work as usual.
