Publish a Service

What?

When you have created a service, specified the implementation, the definition, availability, and at least one plan, the service is ready to be published.

Only a published service will be available on the Trust1Gateway Marketplace for application developers' use.

Steps

1. Select a service which is in status 'ready'. A service is ready to be published when all steps of the configuration wizard are completed. This is represented in the UI by a "Ready" badge and the lack of any numbers in the service tabs.

   

2. Expand the Actions drop-down menu and select Publish

   

3. Ready? In the newly opened modal, click Confirm Publication

   

Result

A toast message informs you about the status.

The service is now published which means it is available on the Trust1Gateway Marketplace for application developers' use.

A newly published service and applied services must be configured on the gateway proxy. In order to do so, the gateway can take up to a minute to configure and restart the internal proxy. When testing immediately after publishing a service, it's possible that the first request will not be consumed by the targeted service.

A published version conveys the API strategy by dynamically building a service-path, this is referred as the "base-path" and is updated in the base-context field of each provisioned swagger definition. More information about the conventions followed, regarding to the publishing gateway can be found on API Mapping and Proxy Capabilities