Global Resource Properties

Connection Settings

The connection settings of global resource can be managed from the adapter properties, from "Global Resource Settings" within the Control Panel, or from WebConsole.

JMS adapter type supports point-to-point communication type that sends to a single application (connection queue) and publish communication type that sends message to multiple applications (the topic connection).

Topic Connection Setting

Basic settings

Item name	Required / Optional	Use of Variables	Description	Remarks
Name	Required	Not available	Enter the name of the connection setting.
Type	Required	Not available	Select [Topic settings].

Required settings

Item name	Required / Optional	Use of Variables	Description	Remarks
XA transaction	Optional	Not available	Select whether to support XA transaction. [Checked]: Supports XA transactions. JMS provider must support XA transactions. [Not Checked]: (default) Does not support XA transactions.
Initial context factory name	Required	Only environment variables are available.	Enter the factory implementation class to generate the initial context. The class name depends on the JMS provider's class libraries stored by $DATASPIDER_HOME/server/plugin/data_processing/modules/jms_adapter. Learn more information about setting the initial context factory from "Preferences" Learn more about class library from "Library Installation".
Provider URL	Required	Only environment variables are available.	Enter the provider URL provided by naming service . Setting depends on each provider. See "Preferences" for more information .
User name	Optional	Only environment variables are available.	Enter the user name to use the naming service.
Password	Optional	Only environment variables are available.	Enter the password to use the naming service.
Topic factory	Required	Only environment variables are available.	Enter the name of the factory to connect to the topic.	The name of the factory is created by an administrator.If you are unsure about the name, please contact your administrator.
Topic name	Required	Only environment variables are available.	Enter the name of the topic.	The name of the topic are created by an administrator.If you are unsure about the name, please contact your administrator.

Property Action

Item name	Description	Remarks
Connection Test	Checks the connection to the host.

Queue Connection Settings

Basic settings

Item name	Required / Optional	Use of Variables	Description	Remarks
Name	Required	Not available	Enter the name of the connection setting.
Type	Required	Not available	Select [Queue settings].

Required Settings

Item name	Required / Optional	Use of Variables	Description	Remarks
XA transactions	Optional	Not available	Select whether to support XA transaction . [Checked]: Supports XA transactions. JMS provider must support XA transactions. [Not Checked]: (default) Does not support XA transactions.
Initial context factory name	Required	Only environment variables are available.	Enter the factory implementation class to generate the initial context. The class name depends on the JMS provider's class libraries stored by $DATASPIDER_HOME/server/plugin/data_processing/modules/jms_adapter. Learn more information about setting the initial context factory from the "Preferences" Learn more about class library from " library installation".
Provider URL	Required	Only environment variables are available.	Enter the provider URL provided by naming service . Setting depends on each provider. See "Preferences}" for more information .
User name	Optional	Only environment variables are available.	Enter the user name to use the naming service.
Password	Optional	Only environment variables are available.	Enter the password to use the naming service.
Queue factory	Required	Only environment variables are available.	Enter the name of the factory to connect to the topic.	The name of the factory is created by an administrator.If you are unsure about the name, please contact your administrator.
Queue name	Required	Only environment variables are available.	Enter the name of the queue.	The name of the queue is created by the administrator.If you are unsure about the name, please contact your administrator.

Property Action

Item name	Description	Remarks
Connection Test	Checks the connection to the host.

Components Pool Settings

Component pool settings can only b set from "Global Resource Settings" from Control Panel or WebConsole.

Security

Security can only be set from "Global resource settings" from Control Panel.

Default

In order to correspond to a variety of JMS vendors,JMS uses JNDI (Java Naming and Directory Interface) naming service and JMS has realized the connection to the provider.

Therefore, JMS does not not unique to each provider to develop a MS adapter, data resource configuration properties naming service URL, and the name QueueConnectionFactory initial binding (setting the Name [Initial context factory name] part) to Simply changing, and we each can be connected JMS provider.

The setting of [Initial context factory name], [Provider URL] depend on the JMS provider, therefore, review the following setting and rewrite anytime.

Enter the IP address and the host name of server run by JMS provider into [myhost].

Naming Service	Initial context factory name	Provider URL
SwiftMQ JNDI Service	com.swiftmq.jndi.InitialContextFactoryImpl	smqp://myhost:4001
IBM WebSphere JNDI service	com.ibm.websphere.naming.WsnInitialContextFactory	iiop://myhost:9001
iPlanet Directory Server (LDAP)	com.sun.jndi.ldap.LdapCtxFactory	ldap://myhost:389
BEA WebLogic JNDI service	weblogic.jndi.WLInitialContextFactory	t3://myhost:7001
File System JNDI Service	com.sun.jndi.fscontext.RefFSContextFactory	file:/tmp/stuff

Connection to the service setting is the one of October 31, 2002.
Contact JMS vendor company for more information.

Operating Environment

SwiftMQ 2.1.3

IBM WebSphere MQ 5.3

Progress SonicMQ 3.5

iPlanet Directory Server

Specification Limits

None.

Main exceptions

Exception Name	Causes	Solution
InvalidPropertyConfigurationException Are not given the resources required fields. : <Property name>	[<property name>] is not specified.	[<property name>] Please specify.
javax.naming.NoInitialContextException: Cannot instantiate class:	[Initial context factory name] is wrong, or class library has not been copied.	Check [Initial context factory name].Or check if the class library has been copied.
javax.naming.ConfigurationException: No scheme found in URI.	[Provider URL] is incorrect.	Confirm [Provider URL].
javax.naming.NameNotFoundException	[Topic factory] or [Queue factory] is incorrect.	Confirm [Topic factory] or [Queue factory].
javax.naming.NameNotFoundException	[Topic name] or [Queue name] is incorrect.	Confirm [Topic name] or [Queue name] .
javax.naming.NamingException: unable to connect, exception = javax.jms.JMSException: error creating socket connection to localhost:4001, message: Connection refused	JMS provider is not running, or the connection settings are incorrect.	Check whether JMS provider is running, or check the contents of connections setting.

Notes

DataSpider does not directly refer to the vendor class, because vendor class is dynamically loaded into the JVM when running, there is a need to store vender class library to $DATASPIDER_HOME/server/plugin/data_processing/modules/jms_adapter.
Learn more from "Library Installation".

Because of the setting of "factory" and "queue name" ,JMS provider may not answer due to the incorrect object name.
About this, please contact us or see the vendors document.
Setting of [User name], [Password] is the user name and password that is also the secure when accessing to JNDI store.If necessary, describe the password if it has been set.