Chapter 2: Configuring Enterprise Server/MTO

This chapter explains the Enterprise Server/MTO configuration required for CICS service interfaces.

For information on configuring Enterprise Server/MTO for an IMS application, see the chapter IMS Installation Verification of your Micro Focus Server Configuration and Administration Guide.

Overview

The CICS applications you can extend using Net Express must be running under Enterprise Server with Mainframe Transaction Option (ES/MTO).You can use applications that have been created in Net Express, that have been migrated to Net Express from the mainframe, or that have been migrated from Mainframe Express. You must have your CICS application running in ES/MTO before you can access it via a service interface.

For complete information on running a CICS application under ES/MTO, see the section Deploying to Enterprise Server in the chapter CICS Walkthrough in your Mainframe Transaction Option Developer's Guide.

Create an Enterprise Server

When you create an enterprise server instance for your application, configure it as follows:

• Enable MTO
• The transaction path must point to your program executables
• The file path must point to your data files
• The map path must point to your BMS modules (.mod files)
• The resource definition path must point to your resource definition (.rdf) file
• For commarea-based CICS applications, set the number of SEPs to be the same as the peak number of concurrent service requests you anticipate receiving
• For screen-based CICS applications, set the number of SEPs to be twice as many as the peak number of concurrent service requests you anticipate receiving
• For single-user testing, set the number of SEPs to 3
• The endpoint URL defined in your service deployment settings must match the Web Services and J2EE listener definition. The default deployment setting endpoint URL for a service is http://localhost:9003.

  Note: For a Web Service, if you do not specify an endpoint URL the underlying communications calls resolve the service automatically regardless of the port setting of the Web Service and J2EE listener in Enterprise Server.

Updating Existing Resource Definitions

You must update your application's exisiting resource definition files to include resource definitions that are required for CICS services. To do this, use the caspcupg utility, located in your Net Express ver\Base\Bin directory. Execute the utility from a Net Express command prompt as follows:

caspcupg /dp=resourcedefinitionpath /o

Where resourcedefinitionpath is the path to your resource definition (.rdf) file.

Caspcupg writes a list of updated or added resources to the screen and to a log file.

Once you have updated your resource definitions, you must add the DFHBRDG group to your startup list. We supply an IMTKCICS startup list that already contains DFHBRDG. For more information on startup lists, see the section Controlling CICS Resources in the chapter Administering MTO-enabled Enterprise Servers for CICS of your Micro Focus Server Mainframe Transaction Option Configuration and Administration Guide.

Copyright © 2007 Micro Focus (IP) Ltd. All rights reserved.