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. However, if you are developing or testing a new Web service that should be offered via the sedex Webservice Proxy, it may be necessary to manually configure test endpoints of services.
Customizing sedex Webservice Proxy Endpointsπ
Overriding an Existing Endpointπ
To override the endpoint for a Webservice named my-service (replace my-service with your service name), add the following configuration parameter to the sedex-client-configuration.properties file:
wsproxy.services.my-service.target-url=https://www.example.com/path
Example: To 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.
Overriding the Truststore for an Existing Web Serviceπ
If the custom endpoint of a Webservice requires a custom SSL/TLS certificate not included 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 located at
/conf/certificatesin your sedex-Client directory. - Add the following configuration parameter to your
sedex-client-configuration.propertiesfile:
$ cp /path/to/yourTLSCert.cer <sedex-data>/conf/certificates/upiquery-test.cer
wsproxy.services.UPIQueryService.target-tls-certificate-path=${sedex.home}/conf/certificates/upiquery-test.cer
$ cp /path/to/yourTLSCert.cer <sedex-home>/conf/certificates/upiquery-test.cer
wsproxy.services.UPIQueryService.target-tls-certificate-filename=upiquery-test.cer