GreyTower for Novell IDM Documentation

Supported JMS Providers

• WebSphereMQ
• ActiveMQ
• Oracle AQ (Advanced Queueing)
• SoftWired IBUS
• Open JMS
• SpiritSoft
• Tibco EMS
• BEA
• Sonic MQ
• SUN
• JBOSS

PreFlight

• Establish or identify the queues to be used either to hold event messages published to eDirectory and/or event messages subscribed from eDirectoryTM.

• Ensure that the appropriate vendor-specific JMS classes are installed on the server hosting the driver in accordance with the vendor’s recommendation.

• Vendor-specific features: Ensure that any vendor-specific supporting components have been installed and configured properly on the JMS server.

• If you are using the 3.0 relase of the greytower project please make sure you have the support shoal framework libraries. These are needed to support the realtime cluster node notification communication.

Example: when using topics with IBM WebSphere MQ, ensure that the message broker strmqbrk) process has been started

Required Connector Files Comunity Edition

• Jms.jar
• GreyTower.jar
• GreyTower.xml
• JXTA.jar
• shoal.jar
• Plus Vendor Specific supporting Libraries

 

Required Connector Files Enterprise Edition

• Jms.jar
• GreyTower.jar
• GreyTower.xml
• JXTA.jar
• shoal.jar
• (GreyTower-Standby.XML) Optional
• Plus Vendor Specific Supporting Libraries

 

Configuring GreyTower for a Specific JMS Vendor

The Greytower connector needs to know which JMS Vendor it need to connect.

Vendor tag	Vendor Description	Additional Information
MQSeries	IBM WebsphereMQ or MQSeries	use this tag when the installation is on the same server as the connector
MQSeriesRemote	IBM WebsphereMQ or MQSeries	use this tag when the installation is on a separate server and the connector
Oracle	Oracles OJMS or Advanced queueing
ActiveMQ	Apaches Active MQ Product
SonicMQ	Soncids Queuing Product
Tibcojms	Tibcos Enterprise JMS product
JBoss	Jboss queueing Product
SUN	SUN JMS PRoduct
BEA	BEA system JMS

 

GreyTower Advanced Features

In addition to the configurable parameters, the driver supports the use of many additional Java Messaging Services features that enhance the developer’s ability to address a very wide range or integration techniques.

Message Properties.

• JMS Message properties contain a built-in facility for supporting application defined property values. This approach provides a mechanism for adding application specific header fields to a message. Message Properties also enable an application, via message selectors, to have a JMS provider select/filter messages on its behalf using application relevant specific criteria:

• Custom Message properties can be set through a DirXML Style sheet. This method is needed to pass name value pairs to systems that are JMS header dependant.

   An Example of setting a custom header is shown below. We will show you how to set a customer header of Last Name to Smith
   
   {LastName|Smith}
   

  The JMS Shim looks for name value pairs contained by brackets {  } and separated by a ‘|’/
  {FieldName|FieldValue}
   

Setting Binary Values in JMS Message.

• The JMS Driver 2.0 support setting binary content in Subscriber channel Messages. Many legacy application use nonprintable ASCII characters as record delimiters. The current XSLT specification does not contain a mechanism for handling non-printable characters natively.

• Custom Binary characters can be set by using specific markers the JMS Driver know how to interpret. This method is needed to pass binary value pairs to systems that depend on nonprintable characters for their record delimiters.

An Example of setting a Binary Value is shown below. We will show you how to set a Binary Value or 255 or FF.

   {#CC|255}

   The JMS Shim looks for name value pairs contained by brackets {  } and separated by a ‘|’/

  {FieldName|FieldValue}

• In this particular case the JMS Shim know that the specific FieldName of #cc indi-cates it will insert a character of (FieldValue) in the message. The FieldValue Is ex-pressed in integer format so if you wanted to insert an character of FF equivalent you would express this as {#CC|255}

Message Priority.

• JMS defines a 10 level priority value with 0 as the lowest and 9 as the highest. JMS clients or DirXML style sheet logic should consider 0-4 as lower –to-normal priority and 5-9 as normal-to-higher priority. Priority is set to 4, by default.

 

    TTL (Time To Live). 
    JMS defines the length of time in milliseconds that a message should be retained by the message system. Time to live is set to zero by default.

JMSMessageID.

• A JMS Message ID property contains an optional value that uniquely identifies each message sent by a provider. This can be used to historically identify each mes-sage or in concert with Correlation ID to establish a relationship among requests and replies in an asynchronous messaging environment.

Correlation ID.

• The JMS CorrelationID property is used for linking one message with another. It typi-cally links the Message ID of the reply message with its Correlation ID of the request-ing message.

GreyTower Load errors

java.lang.ArrayIndexOutOfBoundsException # > #	There is a problem w/the JDK version when trying to retrieve JMSQueueConnectionFactory object via JNDI. This does not apply to a local JMS connection. Replace the novell provided rt.jar with a more recent version. Recommended you use rt.jar from a JDK version 1.3.1 and above.
no mqjbnd02 in java.library.path’	Ensure that the <MQSeries_Install_Path>\java\lib is in your System path.
MQJMS2008: failed to open MQ queue. MQJMS2005: failed to create MQQueueManager for <>	Ensure the specified queue in the ‘Driver Parameters Xml’ exists on the WebsphereMQ server. Ensure the WebsphereMQ server is running.
MQJMS2006: MQ problem:com.ibm.mq.MQException: Completion Code 2, Reason 2085	Regarding MQ JMS Pub/Sub calls, ensure you have created the mq jms system queues. Example: C:\<MQSeries_Install_Path>\java\bin\runmqsc <queue_manager> < MQJMS_PSQ.mqsc
-295 errors	Almost all-295 errors indicate a missing supporting java class library
-295 javax/transaction/xa/XAException	The JVM 1.4 requires the use of the JTA classes available from java.sun.com
mqjms1046: The character set 437 is not supported	Set the sending client ccsid to 819 (the default)