Inbound JMS integration

The base configuration of PolicyCenter includes a high-performance multi-threaded integration with inbound queues of Java Message Service (JMS) messages. PolicyCenter provides two classes, one for processing message replies, and one as a startable plugin. You cannot modify the code in the plugin implementation class in Studio, but you can use one or more instances of these integrations to work with your own file data. The inbound JMS integration supports application servers that implement the JSR-236 specification. These application servers currently include IBM WebSphere, JBoss, and Oracle Weblogic. You develop your own class that processes an individual message, and the inbound JMS framework handles message dispatch and thread management.

PolicyCenter logs any exception that the integration process method in your code throws. The next actions that PolicyCenter takes depend on the stoponerror and ordered configuration subelements.

If both the stoponerror and ordered subelements have the value true, PolicyCenter stops processing on that queue until the plugin is restarted or the server is restarted.
If the stoponerror subelement is false, or stoponerror is true and the ordered subelement is false, PolicyCenter executes roll-back logic for any processing that has occurred for this message. For a typical implementation of a JMS queue, the message is returned to the queue for retrying.

Be sure to catch any errors in your processing code and log any issues so that an administrator can identify and resolve the problem.

PolicyCenter can use JMS implementations on the application server but PolicyCenter does not include its own JMS implementation. Guidewire does not support inbound JMS integration on a Tomcat server. To provide inbound JMS integration to your PolicyCenter application, deploy PolicyCenter on one of the other supported application servers. For additional advice on setting up or configuring an inbound JMS integration with PolicyCenter, contact Guidewire Customer Support.