Enhancements to deploying and managing service flows
The process of deploying service flows now includes the flexibility to define resources dynamically using a new service flow properties file. You can now manage the deployed service flows using a management transaction.
service flow project tools now generates a service flow file that describes the modeled service flow. The service flow file contains the definition of the server adapters, programs, and transactions that are required to run the service flow in CICS. When you deploy this file into the runtime environment, it replaces the properties file update job that existed in previous releases.
The RDO job that updates the CSD is now optionally generated and is not required to define the service flows in CICS. Instead of updating the CSD, you can use the service flow file to create the resource definitions. This option is set in service flow project tools. However, the definitions for the service flow do not persist across a cold start of the CICS region.
The service flow repository file DFHMAASF
A new service flow repository file called DFHMAASF replaces the properties file. The new file contains a record for every service flow that is deployed. When a request message is received by the CICS SFR program interface, DFHMADPL, to invoke a service flow, DFHMADPL reads the service flow repository file and puts the information that is defined for the service flow into BTS data-containers. The flow navigator and server adapters uses these BTS data-containers in their processing.
The flow management transaction CMAN
The supplied transaction CMAN enables you to browse the definitions for each service flow in the service flow repository file. You can use the transaction to install, enable, disable, and delete service flows.