Deploying your secure service in Talend Runtime

This section explains how to configure https-conduits in Talend Runtime to deploy your client job or service. You need to follow these steps if you want to deploy your service in Talend Runtime, because the tSetKeystore you created only gives you access to the service provider server and its exposed services in Talend Studio or in standalone Job mode.

Procedure

Copy the JKS you created in etc/keystores in Talend Runtime.
Create a file in the etc folder in Talend Runtime and use the following pattern to name it org.apache.cxf.http.conduits-XXXXX.cfg.
Here, XXXXX should be replaced by the same name as your services. Any pattern is picked up by the server. You can create as many http_conduits files as required. Talend Runtime will load all of them and evaluate them in the order defined and according to the URL pattern defined in the http-conduits file.
Edit the file you created and take sample parameters from org.apache.cxf.http.conduits-common.cfg.
This file is provided as sample in the etc folder in Talend Runtime. If you only have one service, you can edit the file directly, without making another copy.
Open and edit the file org.apache.cxf.http.conduits-XXXXX.cfg and replace the JKS files locations and password you created using keytool.

Information noteNote: The context variables for the tSetKeystore component have no effect in Talend Runtime, but it is a good practice to keep them in sync with the values you have on the server. This way, you can test your client or service both in Talend Studio and in Talend Runtime. The certificate configuration for tSetKeystore will be overridden by org.apache.cxf.http.conduits-XXXXX.cfg in Talend Runtime.
Restart Talend Runtime to apply the changes to Talend Runtime Container, then test the service using SOAPUI.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!

Leave your feedback here