Read Using the SDFXMLEXTRACTOR Utility and Using the SDFXMLEXTRACTOR Utility before doing the following procedures.
Procedure 1 - Extracting the Forms and Data Descriptions
If not already done, determine the name of the dictionary that contains the formlibrary and determine the name of the formlibrary.
Use the CANDE statement found in ”Running the SDFXMLEXTRACTOR Utility for a COBOL Data Source Project” in Using the SDFXMLEXTRACTOR Utility. Refer to COBOL Project SDFXMLEXTRACTOR Utility Example for an example.
Copy the output files from the MCP server to the PC on which the ClearPath ePortal Developer software is running by using Client Access Services. Refer to Client Access Services Overview for information.
Procedure 2 - Converting an Existing MCP SDF COBOL Application to a Non-SDF COBOL Application
Copy an existing SDF COBOL program to a new COBOL program.
Modify the new COBOL program, by doing the following:
Remove the DICTIONARY statement, FROM DICTIONARY clause, and FORM-KEY functions.
Add the <output file name prefix>/COBOLRECORD file generated by the SDFXMLEXTRACTOR utility.
If Transaction Server entity names are referenced, change the entity names (for example, Program, Window, Agenda).
Compile the new COBOL program.
Create the required Transaction Server configuration entities (for example, Program, Window, Agenda) that do not include a reference to a formlibrary for the new COBOL application.
Procedure 3 - Creating the MCP COBOL Data Source Project and Populating the Project
To create an MCP COBOL data source project
Perform procedure 2 in Creating an MCP COBOL Data Source Project.
Return to this procedure.
To import the SDF formlibrary forms and COBOL data descriptions into the MCP COBOL data source project
On Solution Explorer, highlight the folder of the ePortal data source project.
On the Project menu, click Import SDF Formlibrary.
In the SDF Extractor Output XML File Name box, browse to or type the location of the .xml file that was copied to the PC.
In the SDF Extractor Output COBOL File Name box, browse to or type the location of the COBOL file that was copied to the PC.
Note: If you are importing the SDF Formlibrary in the MCP Cobol Data Source project, do not change the Auto Create Client Message and Auto Recreate Client Message properties from the MCP Cobol Data Source Project property dialog box and leave the default setting of these properties set to False.
Click OK.
The form layouts and COBOL data descriptions are imported into the MCP COBOL data source project. The time that the importation process takes depends on the number and complexity of the forms.
Select the Output pane to monitor the SDF importation progress and watch for warnings or errors.
When the importation process is complete, server messages with an .eprec extension and COBOL record images with a .COBXML extension are found in the Server Messages folder of the project, and client messages are found in the Client Messages folder.
Characteristics of Imported ClearPath ePortal Server Messages and Data Source Records
After importation into the MCP COBOL ePortal data source project, each server message has the following content:
The name of the form is the name of the server message and the data source record.
The form and field definitions, including the field names, of the form are used in the server message and the data source record.
The outputTransmittable field of the form is a read-only input field.
These characteristics can be changed by opening the ePortal Message View window and editing any server message.
Procedure 4 - The Next Step
Go to Creating Client Messages, Modifying Client Messages, Deleting a Client Message, and Creating a Simple Orchestration.