Use this page to add a new service to the current server.
- Specify the name of the service, up to 255 characters. You cannot include angle brackets (<>) or ampersands (&) in the name.
A service name can consist of a service namespace and an operation name, separated by a special character. The character depends
on which request handler is being used, MFRHSOAP, MFHRJSON, or MFRHBINP.
If there is no separating character, the name of the operation is considered to be the same as the service namespace.
If the service is going to use the MFRHSOAP or MFRHBINP request handler, the text before the first pound character (#) in
the name is considered to be the service namespace and the text after is considered to be the name of the operation.
If the service is going to use the MFRHBINP request handler, the text before the last period character (.) in the name is
considered to be the service namespace and the text after is considered to be the name of the operation.
Note: You can change the name of a service only when the server has a status of
- Search Order
- Specifies the search order of the service. If more than one service object has the same name, then a program client can use
Search Order to decide which service to use. The lower the search order is, the higher the search priority.
- Service Class
- Specifies the service class of the service (optional). This field provides a means of grouping services, so that a client
program can ask for a class of service rather than a specific named service. Service classes beginning with MF are reserved
for Micro Focus use. Service Class can be up to 32 characters in length.
- Specifies the version string of the service. This consists of three elements in decreasing order of significance: major version,
minor version, build version. This can be used to distinguish between services of the same name or class.
- Transaction Management
- Select the type of transaction management that this service uses:
- For a service in which the COBOL application manages their own transactions.
- For a service in which the COBOL application leaves transaction management to the application container. If the client is
transactional, such as a J2EE transactional request, this setting is ignored and the service is forced to be container-managed.
Container-managed services should not make any explicit transactional requests, for example, EXEC SQL COMMIT WORK statements.
- Check this to request that for each request for this service the request and response blocks are written to the enterprise
server dump data set. Only use this option if you need diagnostics as it degrades performance.
Restriction: This option only applies to services that represent COBOL applications that are executed by a request handler. It has no effect
for services that are used only for directory lookup purposes, such as the MF JES service.
- Click this to set the service to available.
- Select the required request handler to be the associated handler. You must add a listener before you can see available handlers
and associate a handler with the service.
- Select the required package to be the associated package. You must add a listener before you can see available packages and
associate a package with the service.
- Specify textual configuration information that determines the startup and run-time behavior of the service.
- An optional field that is used to specify a description of the service, for example, its purpose and owner.
- Lists the listeners that are available to be allocated to this service. Click a listener to select it for adding to accepting
listeners. A service can have more than one listener.