JMS Connection
The JMS connection is a Messaging connection. Use the JMS connection to read messages from a JMS server. You can create and manage a JMS connection in the Developer tool or through infacmd.
Prerequisites to Create a JMS Connection and a JMS Data Object
Before you create a JMS connection or data object, you must include the JMS provider client libraries on the machine running Informatica Big Data Streaming.
To create a JMS connections, copy the following JAR files from the IBM MQ server:
- •com.ibm.mq.allclient.jar
- •com.ibm.mq.axis2.jar
- •com.ibm.mq.commonservices.jar
- •com.ibm.mq.defaultconfig.jar
- •com.ibm.mq.headers.jar
- •com.ibm.mq.jar
- •com.ibm.mq.jmqi.jar
- •com.ibm.mq.jms.Nojndi.jar
- •com.ibm.mq.pcf.jar
- •com.ibm.mq.pcf.jar
- •fscontext.jar
- •jms.jar
- •providerutil.jar
- •com.ibm.mq.postcard.jar
- •com.ibm.mq.soap.jar
- •com.ibm.mq.tools.ras.jar
- •com.ibm.mq.traceControl.jar
- •com.ibm.mqjms.jar
- •jndi.jar
- •jta.jar
- •ldap.jar
- •rmm.jar
Place the client JAR files in the following location:
- •Developer tool installation directory: <Developer Tool Installation Directory>/clients/DeveloperClient/connectors/thirdparty/infa.jms/common
Prerequisites to Use a JMS Connection and a JMS Data Object
Before you use a JMS connection and JMS data object in your streaming mapping, perform the following tasks:
1. Verify that the IBM MQ client is installed on all the cluster nodes.
2. Copy the JAR files from the IBM MQ server.
3. Place the JAR files in the following directory on the machine where the Data Integration Service runs:
INFA_HOME/services/shared/hadoop/<Hadoop distribution>/extras/spark-auxjars/
For example, /CDH_5.13/extras/spark-auxjars
4. Create the .bindings file using the IBM MQ Server.
The .bindings file must have the details of the MQ Objects that the data objects in the streaming mappings use.
5. Copy the .bindings file to the Developer tool machine.
6. When you create the JMS connection, configure the Connection URL property with the location of the .bindings file on the Developer tool machine.
7. Place the .bindings file in the same path on all the cluster nodes.
The default location of the files is /etc
For example, file:///etc
8. Before you run the mapping, update the Connection URL property with the location of the .bindings file on the cluster nodes.
General Properties
The following table describes the general connection properties for the JMS connection:
Property | Description |
|---|
Name | The name of the connection. The name is not case sensitive and must be unique within the domain. You can change this property after you create the connection. The name cannot exceed 128 characters, contain spaces, or contain the following special characters: ~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? / |
ID | The string that the Data Integration Service uses to identify the connection. The ID is not case sensitive. It must be 255 characters or less and must be unique in the domain. You cannot change this property after you create the connection. Default value is the connection name. |
Description | The description of the connection. Enter a string that you can use to identify the connection. The description cannot exceed 4,000 characters. |
Location | The domain where you want to create the connection. Select the domain name. |
Type | The connection type. Select Messaging/JMS. |
Connection Properties
The following table describes the connection properties for the JMS connection:
Property | Description |
|---|
Connection URL | The location and port of the JMS provider on which to connect. For example: tcp://jndiserverA:61616 |
User Name | User name to the connection factory. |
Password | The password of the user account that you use to connect to the connection factory. |
JNDI Context Factory | The JMS provider specific initial JNDI context factory implementation for connecting to the JNDI service. This value is a fully qualified class name of the Initial Context Factory. For example, the class name of the Initial Context Factory for ActiveMQ is org.apache.activemq.jndi.ActiveMQInitialContextFactory For more information, see the documentation of the JMS provider. |
JNDI Package Prefixes | A colon-delimited list of package prefixes to use when loading URL context factories. These are the package prefixes for the name of the factory class that will create a URL context factory. For more information about the values, see the documentation of the JMS provider. |
JMS Connection Factory | The name of the object in the JNDI server that enables the JMS Client to create JMS connections. For example, jms/QCF or jmsSalesSystem. |
Creating a JMS Connection using Informatica Command Line Program
You can use the infacmd command line program to create a JMS connection. Access the command from the <Informatica installation directory>/clients/DeveloperClient/infacmd directory.
On UNIX, run the following command:
sh infacmd.sh createConnection
On Windows, run the following command:
infacmd.bat createConnection
Enter connection options in the following format:
... -o option_name='value' option_name='value' ...
For example, run the following command to create a JMS connection on UNIX:
sh infacmd.sh createConnection -dn <domain name> -un <domain name> -pd <domain password> -cn <connection name> -cid <connection id> -ct Jms -o url='<url_val>' username=<u_val> password=<pass_val> contextFactory='<cf_val>' packagePrefixes='<pp_val>' jmsConnectionFactory='<jcf_val>'
For more information about the CreateConnection command, see the Informatica Command Reference Guide.