URI Format and Options - 6.3

Talend ESB Mediation Developer Guide

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

The component can connect to the local platform mbean server with the following URI:

jmx://platform?options

A remote mbean server url can be provided following the initial JMX scheme like so:

jmx:service:jmx:rmi:///jndi/rmi://localhost:1099/jmxrmi?options

You can append query options to the URI in the following format, ?options=value&option2=value&..., where option can be:

Table 12. 

Property

Required

Default

Description

format

no

xml

Format for the message body. Either "xml" or "raw". If xml, the notification is serialized to xml. If raw, then the raw java object is set as the body.

user

no 

 

Credentials for making a remote connection.

password

no 

 

Credentials for making a remote connection.

objectDomain

yes

 

The domain for the mbean you're connecting to.

objectName

no 

 

The name key for the mbean you're connecting to. This value is mutually exclusive with the object properties that get passed. (see below)

notificationFilter

no 

 

Reference to a bean that implements the NotificationFilter. The #ref syntax should be used to reference the bean via the Registry.

handback

no 

 

Value to handback to the listener when a notification is received. This value will be put in the message header with the key "jmx.handback"

testConnection-OnStartup

true

Starting with Camel 2.11, if true, the consumer will throw an exception when unable to establish the JMX connection upon startup. If false, the consumer will attempt to establish the JMX connection every 'x' seconds until the connection is made - where 'x' is the configured using the reconnectDelay option.

reconnectOn-ConnectionFailure

false

Starting with Camel 2.11, if true, the consumer will attempt to reconnect to the JMX server when any connection failure occurs. The consumer will attempt to re-establish the JMX connection every 'x' seconds until the connection is made-- where 'x' is the configured using the reconnectDelay option.

reconnectDelay

10 seconds

Starting with Camel 2.11, the number of seconds to wait before retrying creation of the initial connection or before reconnecting a lost connection.