Bug 780493 (SOA-2924)

Affects: Documentation (Ref Guide, User Guide, etc.)
Help Desk Ticket Reference: https://c.na7.visual.force.com/apex/Case_View?id=500A0000004T5VT&sfdc.override=1
project_key: SOA

Thank you for providing Section 1.19 of the ESB Administration Guide.  This is a *fantastic* addition to the documentation.

Please make Section 1.19 even more useful by altering as follows:

In the first few paragraphs there is a detailed discussion of how <jms-jca-provider> configures both incoming messages as well as messages that are outgoing from the ESB's perspective.  Please augment this discussion with a simple diagram that depicts the situation to be certain it's absolutely clear.

The bottom of the section cautions the user not to use JCA pooled connections for listed ESB components that use internal pooling.  Please provide a snippet from a sample jboss-esb.xml that demonstrates using inbound JCA and outbound 'direct' connections for one of those components.  The text describes it, but having an example provided will remove all doubt that the user is interpreting the document correctly.

These changes will give GSS something we can point to when we're contacted with WebSphere MQ usage questions.  Lacking this documentation, we are sometimes engaged in discussions with customers where we end up having to explain these very things.  (These discussions can be difficult, as we first have to erase customer expectations of how things might work.  The customer might even question our interpretation of standards, etc. if we are describing situations not aligned with their thinking.)  Having it documented clearly at the onset could prevent some of our most troublesome tickets.

Thanks also for providing Section 1.9, which I find a great addition to the documentation.