Using an SDF Formlibrary with ePortal

ClearPath ePortal Developer provides two methods of modernizing an MCP SDF COBOL application that uses forms in an SDF formlibrary

The SDFXMLEXTRACTOR utility that is provided with ClearPath ePortal extracts the appropriate information out of the formlibrary. Refer to the ClearPath ePortal Implementation and Operations Guide for instructions about installing this utility and to Using the SDFXMLEXTRACTOR Utility for information about using the utility.

Summary of the Modernization Steps Using a T27 Data Source Project

  1. Extract the forms by using the SDFXMLEXTRACTOR utility.

  2. Capture the extracted forms into a T27 data source project.

  3. All of the SDF screen and field definitions are preserved in the T27 data source project.

  4. If desired, change the client messages and change the flow of the data using the orchestration functionality.

  5. Build an ePortal presentation project or projects. Refer to Building Your ePortal Solution for more information.

  6. If appropriate, change the look and feel of any .aspx files.

Both the modernized ePortal presentation project and a T27 terminal use the same MCP SDF COBOL application.

Summary of the Migration Steps Using an MCP COBOL Data Source Project

Note: Refer to MCP COBOL Data Source Project Considerations before starting a migration to an MCP COBOL data source project.

  1. Convert the SDF COBOL application into a COBOL application that does not use an SDF formlibrary.

  2. Configure new Transaction Server configuration entities (Program, Window, and Agenda ) that do not include SDF functionality for the converted COBOL application.

  3. Extract the forms and data descriptions by using the SDFXMLEXTRACTOR utility.

    Import the extracted form layouts and data descriptions into an MCP COBOL data source project. A ClearPath ePortal server message, client message, and a COBOL record image are created for each 01 data description.

  4. Create the flow of data. Refer to Understanding Orchestration.

  5. Build an ePortal presentation project or projects. Refer to Building Your ePortal Solutionfor more information.

  6. If appropriate, change the look and feel of any .aspx files. The ePortal presentation connects to the converted MCP COBOL application, which does not use the formlibrary.