Activating the Service Registry - 7.1

Talend ESB Infrastructure Services Configuration Guide

EnrichVersion
7.1
EnrichProdName
Talend Data Fabric
Talend Data Services Platform
Talend ESB
Talend MDM Platform
Talend Open Studio for ESB
Talend Real-Time Big Data Platform
EnrichPlatform
Talend ESB
Talend Runtime
task
Design and Development
Installation and Upgrade

There are four available components to the Service Registry, as well as a common bundle for shared functionality.

The simplest way to install them within the Talend Runtime Container is via the following command:

tesb:start-registry

They can also be uninstalled via:

tesb:stop-registry

Alternatively, each individual feature making up the Service Registry can be installed individually with the following commands:

  • feature:install tesb-registry-server

  • feature:install tesb-registry-rest-service

  • feature:install tesb-registry-rest-atom-service

  • feature:install tesb-registry-server-commands

Once installed, run the following command to show the activated features:

list | grep Registry

The installed features displayed should be as follows:

237 | Active   |  80 |  | Talend ESB Registry :: Client :: Common
238 | Active   |  80 |  | Talend ESB Registry :: Common
239 | Active   |  80 |  | Talend ESB Registry :: Client :: Policy
240 | Active   |  80 |  | Talend ESB Registry :: REST :: Security
241 | Active   |  80 |  | Talend ESB Registry :: Client :: WSDL
274 | Active   |  80 |  | Talend ESB Registry :: REST Atom Service
275 | Active   |  80 |  | Talend ESB Registry :: REST Lookup Service
276 | Active   |  80 |  | Talend ESB Registry :: Server
277 | Active   |  80 |  | Talend ESB Registry :: Server :: Commands

You can configure the Service Registry in the etc/org.talend.esb.registry.server.cfg file, with the following parameters. Note that the below values provided by default for those parameters are usually suitable.

Service Registry Configuration Settings
Option Description
repository.home Jackrabbit repository home directory
rmi.enable Whether to enable RMI access to Jackrabbit repository
rmi.host The localhost interface for the RMI registry
rmi.port The port on which the RMI registry is listening
rmi.name The name to which the repository is to be bound in the registry
checker.wsdl.enableWSIcheck Whether to enable the WS-I consistency check for WSDL resources

The Talend Service Registry service is exposed via the container HTTP(s) port which can be configured in the org.ops4j.pax.web.cfg. For more information, see the HTTP Configuration chapter in the Talend ESB Container Administration Guide.

The Registry WSDL client can be installed via the following commands within the Talend Runtime Container:

feature:install tesb-registry-wsdl-client

The Registry Policy client can be installed via the following commands within the Talend Runtime Container:

feature:install tesb-registry-policy-client

Once installed, run the activated features as follows:

list | grep Registry

The installed features dispayed should be as follows:

[235] [Created] [80] Talend ESB Registry :: Client :: Policy
[236] [Created] [80] Talend ESB Registry :: Client :: WSDL

The WSDL client configuration is done in the etc/org.talend.esb.registry.client.wsdl.cfg and the Policy client configuration is done in the etc/org.talend.esb.registry.client.policy.cfg.

To use the Service Registry with SSL, change the registry.url parameter value from http://localhost:8040/services/registry/lookup to https://localhost:9001/services/registry/lookup.

The Service Registry WSDL and Policy clients support two authentication methods: BASIC and SAML. You can use BASIC or SAML authentication by enabling the corresponding settings or no authentication by enabling registry.authentication = NO in the configuration file.

To use BASIC authentication, enable the following settings. The user credentials can be found in etc/users.properties.

#BASIC authentication
registry.authentication.user = tesb
registry.authentication.password = tesb

To use SAML authentication, enable the following settings. Change the WS-Security and STS Client configuration according to your own use case. For more information, see the Talend ESB Service Developer Guide and Talend ESB STS User Guide.

#SAML authentication
security.username = tadmin
security.password = tadmin
security.sts.token.username = myclientkey
security.sts.token.properties = clientKeystore.properties
security.encryption.username = mystskey
security.encryption.properties = clientKeystore.properties

sts.wsdl.location = http://localhost:8040/services/SecurityTokenService/UT?wsdl
sts.namespace = http://docs.oasis-open.org/ws-sx/ws-trust/200512/
sts.service.name = SecurityTokenService
sts.endpoint.name = UT_Port