Local Web Service Definitions for the sedex Webservice Proxy

Normally the definitions of the Web services offered by the sedex Webservice Proxy are automatically provisioned and require no manual configuration. But if you are developing or testing a new Web service that should be offered via sedex Webservice Proxy, it may be necessary to manually configure test endpoints of services.

Custom sedex Webservice Proxy Endpoints

Adding the following configuration parameter overrides the endpoint for the Webservice with name my-service (adapt the name to your service):

wsproxy.services.my-service.target-url=https://www.example.com/path

Example: override the endpoint of the Web service UPIQueryService:

wsproxy.services.UPIQueryService.target-url=https://wupi-test.zas.admin.ch/wupi_cc/UPIQueryService

If no entry is made for a particular service, the default endpoint defined by sedex is used.

Note: If the custom endpoint of a Webservice requires a custom SSL/TLS certificate not contained in the standard sedex truststore, you can override the default truststore as follows.

Copy your custom SSL/TLS certificate (e.g. upiquery-test.cer) into the local certificate folder of your sedex Client:

 $ cp /path/to/yourTLSCert.cer /path/to/sedex-data/conf/certificates/upiquery-test.cer

Add the following configuration parameter referencing your certificate file:

 wsproxy.services.UPIQueryService.target-tls-certificate-filename=upiquery-test.cer