Service Access Settings
The Service Access Settings page allows you to configure the webMethods Integration Server services to be called externally over HTTPS. The services will be available to consumers based on the Allow All and Deny All access modes.
To configure service access settings
Log in to the IBM® webMethods Cloud Container.
From the IBM webMethods Cloud Container navigation bar, click Solutions > Solution List > Select a solution > Manage > Service Access Settings.
On the Service Access Settings page, configure the webMethods Integration Server services to be called externally over HTTPS. Required fields are marked with an asterisk on the screen.
| Field | Description |
|---|---|
| Base URL | The base URL is a part of the complete service URL, for example, https://tenant1.container.webmethodscloud.com/integration/service.* |
| Solution Alias | An alias for the solution in the base URL. The alias name for a solution is unique in that particular environment. |
| Select Integration Server | Select the solution webMethods Integration Server instance where the services need to be configured. |
| Access Mode | Ensure that the access mode of the services are properly set. Select Deny
All if you want to deny most of the services to be invoked and allow a few. Then click
ADD to add services to the Allowed Services table. In the Add Service window,
the Base URL is a part of the complete service URL. In the Service URL field, type the
webMethods Integration Server Service URL. The Base URL and the Service URL together forms the
complete service URL. Select Allow All if you want to allow most of the services to be
invoked and deny a few. Click ADD to add services to the Denied Services table. In the
Add Service window, the Base URL is a part of the complete service URL. In the
Service URL field, type the webMethods Integration Server Service URL. The Base URL and the
Service URL together forms the complete service URL. You can update the service URL by clicking the Edit icon beside the service URL in the services table.The services will be available to be invoked from a software application, for example, a REST client, after you add the services to the table. For example, the Service URL /invoke/pub.math:addInts has the following components: Directive - Invoke Namespace of the service - pub.math:addInts You can match all services to be allowed or denied by typing * at the end of the Service URL. For example, if you have two services, service url1: /invoke/pub.date:formatDate and service url2: /invoke/pub.date:getCurrentDate /invoke/, then instead of typing two entries, you can provide only one entry, service url: /invoke/pub.date.*. All services matching pub.date will be allowed or denied. |