Connection properties
This section explains the properties you can specify on the Connection tab of a message queue connection point.
You are prompted to select the external JMS type that you want ION to connect to. Select one of the pre-registered JMS vendors.
There are some common properties irrespective of the selected JMS vendor and there are some vendor specific properties.
The vendor independent properties of the connection point correspond to the sample implementation that are provided in this folder:
JMSClientBundleWrapper/examples
Sometimes, different samples are supplied for the same vendor depending on the protocols used. For example, there are several samples for TIBCO EMS to connect using SSL, SSL-JNDI and TCP. Registering a driver for one of these protocols does not enable other protocols to communicate with TIBCO EMS server. Each protocol support must be treated as a separate JMS client registration.
See Registering JMS Vendors with ION.
The samples that are provided are meant to be used as a reference. The configuration details and customizations that are required for the actual registration of a JMS client driver can differ from the samples provided. This depends on the deployment requirements of the JMS server.
This table shows the vendor independent properties of the connection point:
| Property | Description |
|---|---|
| Default queue for Reading: | This property is used for reading one or more documents from the JMS queue on the external JMS server and use them in ION. Specify the name of the queue that is used for reading those messages that do not have a specific queue. On the Documents tab you can select the Use Default Queue for all documents option. ION does not poll any other queue and uses this queue to read all documents. Confirm BODs that are published by the external JMS servers are also expected in this queue. Ensure that this queue is unique to this connection point and is not used as a read queue in any other connection point. |
| Default queue for Writing: | This property is required to write one or more documents from ION to the JMS queue. Specify the name of the queue on the external JMS server that is used for writing those messages that do not have a specific queue. On the Documents tab, you can select the Use Default Queue for all documents option. ION writes all incoming documents of this connection point to this queue. |
| Authentication | None: no authentication is required for the message queues. Basic: a user name and password are required for the message queues. |
| User Name: | If basis authentication is used, specify the user name to be used for the queues. These credentials are used by ION to read or write the message queues. |
| Password: | If basis authentication is used, specify the password to be used to connect to the message queues. |
This table shows the vendor specific properties of the connection point:
| Property | Description |
|---|---|
| URL |
Specify the URL of the address of the external JMS server. The format is: tcp://MachineName:portNumber Note that the machine name is the name of the external JMS server. If this is a remote host, ensure to specify the correct host name and test if the port is accessible. |
| Administration Port: | The JMX port that is used by the Active MQ server. This is used by ION to retrieve the metrics that are related to the Manage pages of ION. You can find this port number from the activemq.xml file available under this folder: activemq Install Dir/conf |
| Property | Description |
|---|---|
| Host | Specify the machine name of the IBM MQ
server. The machine name is the name of the external JMS server. If this is a remote host then ensure to specify the correct host name. |
| Port | Port of the IBM MQ server. Ensure that the port is accessible. |
| Queue Manager | Queue Manager of the chosen IBM MQ service |
| Channel | Channel of the chosen IBM MQ service |
| Property | Description |
|---|---|
| URL | Specify the URL of the address of the Tibco server. The
format is: tcp://MachineName:PortNumber The machine name is the name of the external JMS server. If this is a remote host, ensure to specify the correct host name and test if the port is accessible. |
| Property | Description |
|---|---|
| URL | Specify the URL of the address of the Oracle AQ JMS
server. The format is: jdbc:oracle:thin:@//HostName:PortNumber/SystemID The machine name is the name of the external JMS server. If this is a remote host then ensure to specify the correct host name and test if the port is accessible. |
| Internal Logon | This is the role used while making
connection. This can be either default or sysdba. |
| Queue Table | Table where the queues are stored |
To use the Tibco EMS 8.2.0 (JNDI with SSL security) option, the TIbco Enterprise Message Service Server must be configured to support SSL. See the official Tibco EMS documentation and sample files: https://docs.tibco.com/pub/activematrix_businessworks_plugin_for_microsoft_sharepoint/6.0.0/doc/html/GUID-18028D0D-02E9-411F-A5B0-FA3011FCDF71.html
Afterwards you must import the server certificate of the Tibco EMS server into ION.
- Ask your TIbco EMS administrator for the correct server certificate. This
corresponds to the configurations that are specified in the
tibemsd.confandfactories.conffile of TIBCO EMS server. Verify the certificate. The extensionscer,derandcrtare supported byION. Rename the certificate file with one of these extensions before proceeding. - Ensure that the certificate file does not contain the private key.
- When you agree on the authenticity of the certificate, click .
- A window is displayed. Browse to the location of your certificate and select it. Click .
- The certificate is imported in the ION trust store.
ION is tested with TIBCO EMS as the JNDI provider. Continue with specifying the remaining TIBCO EMS specific properties that are shown in this table:
| Property | Description |
|---|---|
| JNDI URL | Specify the provider URL of the TIBCO EMS JNDI server. The format is: tibjmsnaming://<HOST>:<PORT> |
| JNDI Username | Specify the JNDI username. Note that this is different than the username required to connect to the JMS queues. |
| JNDI Password | Specify the password for the JNDI user. |
| Factory Name | Specify the Queue connection factory set in the factories.conf file of TIBCO EMS in the Queue Connection Factory field. For example: SSLQueueConnectionFactory |
| Factory Context | Specify the Initial context factory to be used for the JNDI lookup. For example: com.tibco.tibjms.naming.TibjmsInitialContextFactory |
| URL Package | Prefixes Specify the package that provides the context class user to perform JNDI and SSL operations. For example: com.tibco.tibjms.naming |
| SSL Client Identity: Import Client Certificate |
|
| SSL Client Keystore Password | Specify the password for the client certificate. |
The Tibco 8.2.0 (Plain SSL connection without JNDI) option uses SSL channel to
connect to TIBCO EMS. It requires SSL enabling on the TIBCO side. The server certificate
must be imported into ION. Ask
your TIbco EMS administrator for the correct server certificate. This corresponds to the
configurations that are specified in the tibemsd.conf
and factories.conf file of TIBCO EMS server. Verify
the certificate. The extensions cer, der and crt are
supported byION. Rename the
certificate file with one of these extensions before proceeding.
- Log on to ION.
- Select > .
- Click the Configuration Files tab.
- Click in the Certificate Store.
- A window is displayed. Browse to the location of your certificate and select it. Click .
Continue with specifying the remaining TIBCO 8.2.0 specific properties that are shown in this table:
| Property | Description |
|---|---|
| URL | Specify the SSL URL of the address of the Tibco server. The format is: ssl://MachineName:PortNumber |
If you chose another JMS vendor that is registered by you, the connection properties that you defined are shown. Specify appropriate values.
Click to verify whether the connection details are correct. You are informed whether the test is successful.