Creating JMS Destination Resources and Connection Factory

The PIX/PDQ Manager uses JMS topics to make outbound patient notification updates available to the domains that subscribe to those updates. The Sun Master Index generates outbound messages for patient updates in XML format to the PatientTopic destination. The BPEL processes that handle update notifications make the information available to either HL7 v2 or HL7 v3 destinations according to the IHE framework.

You can create the JMS artifacts manually as described below or rerun the installer as mentioned earlier.

To Create the JMS Destination Resources and Connection Factory

1. In the left portion of the Admin Console, expand Resources, expand JMS Resources, and then select Connection Factories.

2. On the New JMS Connection Factory page, click New.

3. Enter the following information:

   • JNDI Name – jms/PatientOutBoundServer (this name is case-sensitive)

   • Resource Type – javax.jms.TopicConnectionFactory

4. Create the following additional properties and enter the property values:

   • UserName – A JMS user name. The default user name is admin.

   • Password – A password for the above user name. The default password is admin.

5. Click OK.

6. In the left portion of the Admin Console, select Destination Resources under JMS Resources.

7. On the New JMS Destination Resource page, click New.

8. Use this page to create the following topics:

   JNDI Name	Resource Type	Physical Destination Name	Purpose
   PatientTopic	javax.jms.Topic	PatientTopic	Updates to the Master Index patient records are written to this topic.
   tHL7V3	javax.jms.Topic	tHL7V3	HL7 v3 updates to patient records are processed through a BPEL process and written to this topic.
   tHL7V2	javax.jms.Topic	tHL7V2	HL7 v2 updates to patient records are processed through a BPEL process and written to this topic.
   tSUNXDS	javax.jms.Topic	tSUNXDS	This is a placeholder and is not currently used.
   tXDSMerge	javax.jms.Topic	tXDSMerge	This is a placeholder and is not currently used.