Section | Description |
General Info | Identifies The folder in which the service is contained and the service name. The name of the package with which the service is associated. The type of service: Flow, Java, or C/C++. Whether the service is stateless or not. The allowed HTTP methods. An alternative name for the service that can include special characters, which are not allowed while creating the service. Whether the service is marked as a favorite or not. Marking services as favorites lets the users quickly see only the services they need in a project. A list of comma-separated values that you can use to search and group package assets. Version of the package in which the service was introduced. Whether the service is deprecated or not. Whether the service is available for use outside the package or not. |
Universal Name | The name that will be used to qualify the name of this service. It consists of the namespace name and the local name. By convention, a URI is generally used as the namespace name (e.g., http://www.gsx.com/gl). This assures that the universal name is globally unique. The local name uniquely identifies the service within the collection encompassed by namespace name. Most sites use the unqualified portion of the service name as the local name You may use any sequence of characters or digits for the namespace name and the local name. |
Java-Specific Parameters | For a Java service, identifies the Java class name and method name for the service. |
Access Control | Identifies the ACLs assigned to the service or specification. For information about ACLs, services, and specifications, see
Controlling Access to Resources with
ACLs. |
Cache Control | Identifies whether the server is to save the results of executing this service in cache. For information, see
Caching Service Results. |
Data Formatting | Identifies the name of a binding service that parses incoming XML for the service, the output template associated with the service (if any), and the type of the output template (HTML or XML). For information about output templates, refer to the Dynamic Server Pages and Output Templates Developer's Guide. |
Concurrent Requests Limit | Identifies the following: Whether the concurrent requests limit for the service when it is invoked as a top-level service is enabled or not. The maximum number of concurrent executions of a service when the concurrent requests limit is enabled for the service invoked as a top-level service. For more information, see IBM webMethods Service Development Help. |