Version 9.6	SEARCH   CONTENTS   |   PDF BOOKS   |   HOME   UP   PREV   NEXT

A server mapping file (SVM) enables the RPC server to correctly support special COBOL syntax such as REDEFINEs, JUSTIFIED, SYNCHRONIZE and OCCURS DEPENDING ON clauses, LEVEL-88 fields, etc. If one of these elements is used, the EntireX Workbench automatically extracts an SVM file in addition to the IDL (interface definition language), or an SVM file is generated by the COBOL Wrapper for a server skeleton. The SVM file is used at runtime to marshal and unmarshal the RPC data stream.

This document covers the following topics:

• SVM Files in the EntireX Workbench

• SVM Files in the RPC Server

• Source Control of SVM Files

• Change Management of SVM Files

• Compare SVM Files

• List Deployed SVM Files

• Check if an SVM File Revision has been Deployed

• Access Control: Secure SVM File Deployment

• When is an SVM File Required?

SVM Files in the EntireX Workbench

In the EntireX Workbench, an SVM file has to relate to an appropriate IDL file. Therefore, you always have to keep the IDL file and the SVM file together in the same folder.

If there is an SVM file and a corresponding IDL file,

• at least one of the IDL programs in the corresponding IDL file requires server-mapping information to correctly call the target server. For those IDL programs, there is an SVM entry (line) in the Workbench SVM file.

• deployment of the SVM file to the RPC server is mandatory, see Server Mapping Deployment.

If there is an IDL file but no corresponding SVM file,

• there is no IDL program that requires server mapping information.

SVM Files in the RPC Server

For Micro Focus RPC Servers under UNIX or Windows, the SVM files of the Workbench are stored as directories (folders) and operating system files. For each IDL library, a directory is created by the deployment service during deployment and each SVM entry is stored as an operating system file within this directory. The anchor of the SVM directories is configured by the server mapping file subparameter "path" of parameter "svm", see Configuring the RPC Server. For example, deploying the file example.svm from the EntireX directory examples/RPC/basic/example results in folder EXAMPLE and operating system files for the SVM entries CALC and SQUARE:

../EXAMPLE
/CALC.svm
/SQUARE.svm

If one server requires an SVM file, you need to provide this to the RPC server:

• Development environments: to allow the deployment of new SVM files, enable the deployment service. See Enabling the Deployment Service.

• Production environments: provide SVM files to the RPC server. See configuration parameter svm.

If no server requires an SVM file, you can execute the RPC server without SVM files:

• Development environments: you can disable the deployment service. See Disabling the Deployment Service.

• Production environments: there is no need to provide SVM files to the RPC server. See configuration parameter svm.

Source Control of SVM Files

Because SVM entries within an SVM file contain text data only, a Workbench SVM file is text-based (although it is not intended for human consumption). Therefore, you can include it in your source control management together with the IDL file and the COBOL source(s) as a triplet that should always be kept in sync.

Change Management of SVM Files

For the Micro Focus RPC Server under UNIX or Windows, change management within SVM directories (see SVM Files in the RPC Server) is similar to change management within ordinary operating system directories (folders). All updates to the SVM hierarchy done after a backup must be kept.

All Workbench SVM files added since the last backup should be available.

Compare SVM Files

For SVM files in the EntireX Workbench format, you can use a third party file/text compare tool to check if two files are identical.

The SVM entries (corresponding to lines in a Workbench SVM file) contain a creation timestamp at offset 276 (decimal) in the format YYYYMMDDHHIISST. The precision is 1/10 of a second.

List Deployed SVM Files

To list the contents of an SVM directory (see SVM Files in the RPC Server), use the Windows Explorer (for Windows) or the ls command (for UNIX).

Check if an SVM File Revision has been Deployed

SVM entries (corresponding to lines in Workbench SVM files) contain a creation timestamp at offset 276 (decimal) in the format YYYYMMDDHHIISST. Precision is 1/10 of a second. The creation timestamp can be checked.

The timestamp can be found on the same offset in the SVM files stored as operating system files in SVM directories.

Access Control: Secure SVM File Deployment

For deployment with the Server Mapping Deployment Wizard, use EntireX Security if the broker is running on platforms z/OS, UNIX , Windows or z/VSE. See Enabling the Deployment Service.

When is an SVM File Required?

For the IDL Extractor for COBOL

For the COBOL Wrapper

This depends on the interface type chosen and the IDL type:

www.softwareag.com

Copyright © 1997-2014 Software AG, Darmstadt, Germany.

SEARCH   CONTENTS   |   PDF BOOKS   |   HOME   UP   PREV   NEXT