Enterprise Server
Features include:
- Configuration of enterprise servers using the Administration Web interface.
- Dynamic debugging of applications that are running under an enterprise server
- Deployment of mainframe and native code applications to an enterprise server.
- CICS Web Interface (CWI) Offers an additional CICS Web Interface (CWI) support to include DOCUMENT and EXTRACT TCPIP CICS
APIs and to provide support for CICS as an HTTP client.
Mainframe Access (MFA) Client Capabilities
Enterprise Developer and Enterprise Test Server provide Mainframe Access (MFA) client capabilities.
When migrating applications, this ensures source and data can be transferred from the mainframe and projects can be setup
more efficiently within the
Enterprise Developer environment to make it easier to demonstrate rapid progress to key stake holders. Once projects are set up, the synchronization
with mainframe artifacts can be automated to deliver significant gains in efficiency.
When rehosting testing workload to Windows, this provides:
- Seamless but secure access to mainframe application source code and data simplifies set up and deployment of the Test Server
platform.
- Significantly increases the breadth of applications that can be tested within the Enterprise Test Server environment as jobs,
programs and utilities that cannot be rehosted to Windows can be remotely accessed on the mainframe.
- Allows source synchronization with mainframe source control systems. Test Server can then be configured to automatically compile
changes as they are checked into source libraries. This provides early exposure to test teams performing smoke or regression
testing.
- Data can continue to reside on the mainframe. COBOL programs running under Test Server can directly access mainframe files.
This not only allows multiple test levels against different subsets of data, it means that sensitive or archive data can remain
in position.
- MFA Synchronisation and Control Monitor (aka "Syncmon") – synchronises selected source components between mainframe hosted
source and a Windows development or test environment
- Automatic Synchronise and Compile to automatically compile modules after source code synchronisation.
- Remote Job (JCL) Step Execution to enable execution of jobs on mainframe that cannot be rehosted to Windows
- Mainframe Call Generator – enables remote execution of mainframe programs that cannot be re-hosted to Windows.
- SourceConnect – allows direct access to source hosted on mainframe.
- DataConnect – allows COBOL file access to data files hosted on mainframe.
Service Interfaces Using the IMTK
Important: We highly recommend that you do the IMTK tutorials to get a feel for using these tools. See
Tutorials: Interface Mapping Toolkit (IMTK) in the
Getting Started section under
Native COBOL Tutorials.
The IMTK enables you to create an interface between a legacy COBOL application running on an
ESI as a service, such as a Web service or Java service, and a non-COBOL client, such as a Web service client or a JSP client.
The interface you create is called a
service interface. In your service interface, you can expose as much or as little of the original legacy application functionality as you choose.
Because legacy applications often perform a wide variety of functions, the creation of a service interface enables you to
limit your end users to access only the functions they need.
You can create the following types of service interfaces for COBOL programs:
- Java Interface
- Web Service from WSDL
- Web Service from request-response JSON schemas
- RESTful Web Service from JSON schema
Attention: To deploy or generate a client for a Java Interface, you must install and configure the Java JDK and a Java application server.
See the
Application Server JCA support for Enterprise Server topic under
Additional Software Requirements.
The process of creating a working service interface to run on
Enterprise Server includes the following:
- Creating and configuring an
enterprise server instance to run the legacy application as a service
- Creating a service interface in an
Enterprise Developer project
- Defining the details of the service interface using the
Interface Mapper
- Deploying the legacy application and service interface to your
enterprise server instance
- Generating one or more clients to access the service running on the
enterprise server instance
Support for the PL/I Language
- The Micro Focus Open PL/I Compiler, Debugger and Runtime are included into the
Enterprise Developer and Enterprise Server products to enable Micro Focus to offer a comprehensive, low-risk migration solution for mainframe
Pl/I applications.
Features include:
- Shared file handling between Micro Focus COBOL and Open PL/I - Open PL/I enables you to use the same filehandler as used by
the Micro Focus COBOL products. Its primary advantage is that it provides support for Indexed files and the ability to execute
PL/I programs under the control of Enterprise Server JCL.
- Shared Memory handling and Corruption detection with the Micro Focus COBOL run-time system.
- Shared Signal Handling with the Micro Focus run-time system.
- Improved support for large PL/I programs.
- Supports the WIDECHAR data type (and the built-in functions associated with it).
- Improved debugging capabilities for applications under development and running in production which help increase the programmers'
productivity during and after migration.
- Support for the PLIDUMP() facility which generates a callstack and shows all static variables, local variables and API parameters
that were in effect at the time of the call to PLIDUMP. PLIDUMP is typically used to analyze application failures while running
in production.
- Support for an enhanced PLITEST API which allows for dynamic attachment of the PL/I Debugger at a point the application programmer
specifies. In addition, the PLITEST interface now has the capability of displaying the Codewatch Debugger UI on any platform
capable of hosting an X-Windows Server.
- Generation of ASA Control Characters when writing to PL/I files with the STREAM and PRINT attributes. When writing PL/I files
that are defined to have the STREAM and PRINT attributes, appropriate control characters are now written to column 1 of the
output dataset to represent a new page, skip(1), skip(2), skip(3), and skip(0) (known as overstrike). This helps ease the
migration and integration of PL/I applications with existing printing subsystems.
- OpenESQL for PL/I - Support for Microsoft SQL Server within Open PL/I included within
Enterprise Developer and Enterprise Test Server is available as an early adopter release. This provides the option to select Microsoft SQL Server
as the target database when migrating PL/I applications that utilize DB2.
- The mature OpenESQL technology Micro Focus has supported for many years for its COBOL customers, is now available for use
with PL/I applications. This means PL/I SQL can now execute against popular relational databases like Microsoft SQL Server
even though a SQL preprocessor for PL/I is not available from the database vendor.
- This support is classified as "Early Adopter". It has been successfully tested by Micro Focus development but has only been
exposed to a limited amount of customer application code.
- The PL/I Dynamic Calls (FETCH/RELEASE) are supported. This provides greater efficiency during migration and less risk as applications
using dynamic calls can be rehosted without significant changes to application logic.
- DB2 UDB Precompiler - A DB2 UDB Precompiler is now available on all platforms for Open PL/I. This feature allows you to migrate
applications which contain EXEC SQL logic.
- Support for the PLISRTx routines to support data types of ZD, PD, FI, BI, and FL.
- Open PL/I DB2 LUW Preprocessor - the Open PL/I DB2 LUW Preprocessor supports ROWID, BLOB and CLOB which widens the breadth
of applications that can be rehosted. Without this support, applications using such features would not be considered as candidates
for migration due to the significant reengineering that would be required.
- Improved Language compatibility with IBM's z/OS based PL/I Compiler - applications that use these IBM mainframe PL/I language
features do not need code modification to function in the same manner using Open PL/I. This reduces risk while accelerating
migration of such programs.
- Support for Open PL/I applications that utilize CICS within Enterprise Server. This provides the ability to re-host mainframe
PL/I applications to lower cost Windows, UNIX or Linux platforms while keeping PL/I code intact to minimize risk. Features
include:
- A new PL/I CICS precompiler.
- Enhanced source level debugging.
- PL/I RTS support for CICS applications.
- Support for IMS/DB and IMS/TM applications - Open PL/I supports the PLITDLI and PLIHSSR interfaces. Customers who wish to
migrate their PL/I Online or Batch applications that utilize IMS can now run them on Enterprise Server.