Specify JMS message properties with UMS send protocol ?

Hi,
is there a way to specify JMS Message properties when sending a message throught Universal Message Service (UMS) ?
I was not able to find any reference to this kind of usage.
Additionally, how do we specify filters (if possible) when receiving messages from UMS?
Thanks.

I have written an UDF to determine the filename dynamicly:
//write your code here
String str = "SAPDATA-" + a + "ES" + ".xml";
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey FileName = DynamicConfigurationKey.create("http:/"+"/sap.com/xi/XI/System/File","FileName");
conf.put(FileName, str);
return "";

Similar Messages

Additional JMS Message Properties

Hi Guru's,
I am looking for a solution to dynamicly set the filename for JMS receiver adapter. What I have found so far is that this should be done with the Additional JMS Message Properties...
Based on a field from the source structure I want to determine the filename which will be send via the JMS adapter. Is there any documentation available on how to achieve this?
Best regards,
Guido Koopmann

I have written an UDF to determine the filename dynamicly:
//write your code here
String str = "SAPDATA-" + a + "ES" + ".xml";
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey FileName = DynamicConfigurationKey.create("http:/"+"/sap.com/xi/XI/System/File","FileName");
conf.put(FileName, str);
return "";

Propagate custom JMS message properties to replyTo message

WebServices are invoked over JMS. In the SOAP JMS message request, I want to record some information in JMS properties and get them back in the reply JMS message received in the replyTo queue. I wonder if there is a way to do that, either by writing custom hook to copy over custom JMS message properties, or WLS recognize special JMS message properties that will be propagated.

I have written an UDF to determine the filename dynamicly:
//write your code here
String str = "SAPDATA-" + a + "ES" + ".xml";
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey FileName = DynamicConfigurationKey.create("http:/"+"/sap.com/xi/XI/System/File","FileName");
conf.put(FileName, str);
return "";

XSLT sender plugin fails to set JMS message properties

When creating a JMS message to be put on a JMS queue, one of the XSLT for the XSLT automation plugin fails to set JMS string properties like: wlsmimehdrContent_Type
The content on the xslt are listed below.
The xslt in CPRLookupRequest.xslt sets:
wlsmimehdrContent_Type
SERVICE_SUFFIX
OSM_EVENT_TYPE
as expected, but the almost similar plugin NABSCreditEvalPluginRequest.xsl fails to set the same string JMS properties.
I'm looking for a clue, because I'm clueless. I'm an XSLT newbie, so it might be something simple.
The core part of the problem is put in bold in the listings below
h2. CPRLookupRequest.xslt:
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns="http://java.sun.com/products/oss/xml/ServiceActivation" xmlns:xsl="http://www.w3.org/1999/XSL/Transform" xmlns:oms="urn:com:metasolv:oms:xmlapi:1" xmlns:java="http://xml.apache.org/xalan/java" xmlns:xalan="http://xml.apache.org/xalan" xmlns:mslv-sa="http://www.metasolv.com/oss/ServiceActivation/2003" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:co="http://java.sun.com/products/oss/xml/Common" exclude-result-prefixes="oms java xsl xalan">
     <xsl:param name="automator"/>
     <xsl:param name="log"/>
     <xsl:param name="context"/>
     <xsl:param name="outboundMessage"/>
     <xsl:output method="xml" indent="yes" omit-xml-declaration="no" xalan:indent-amount="5"/>
     <xsl:template match="/">
          <xsl:apply-templates select="oms:GetOrder.Response">
               <xsl:with-param name="SERVICE_SUFFIX" select="'CprDomain/Cpr'"/>
               <xsl:with-param name="OSM_EVENT_TYPE" select="'CPR_LOOKUP'"/>
          </xsl:apply-templates>
     </xsl:template>
     <xsl:template match="oms:GetOrder.Response">
          <xsl:param name="SERVICE_SUFFIX" />
          <xsl:param name="OSM_EVENT_TYPE" />
*<xsl:variable name="void2" select="java:setStringProperty($outboundMessage, '_wls_mimehdrContent_Type', 'text/xml; charset=UTF-8')" />*
*<xsl:variable name="void3" select="java:setStringProperty($outboundMessage, 'SERVICE_SUFFIX', $SERVICE_SUFFIX)" />*
*<xsl:variable name="void4" select="java:setStringProperty($outboundMessage, 'OSM_EVENT_TYPE', $OSM_EVENT_TYPE)" />*
          <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
               <env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                    <m:getPersonByCPR xmlns:m="/Cpr">
                         <getPersonByCprRequestInfo xmlns:n1="java:dk.tdc.soa.cpr.extern.datatypes" xsi:type="n1:GetPersonByCprRequestInfo">
                              <applicationId xsi:type="xsd:string"><xsl:text>CPR</xsl:text></applicationId>
                              <cprNumber xsi:type="xsd:string"><xsl:value-of select="oms:_root/oms:cpr" /></cprNumber>
                         </getPersonByCprRequestInfo>
                    </m:getPersonByCPR>
               </env:Body>
          </env:Envelope>
     </xsl:template>
</xsl:stylesheet>
h2. NABSCreditEvalPluginRequest.xsl
<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" exclude-result-prefixes="oms java xsl xalan"
     xmlns="http://java.sun.com/products/oss/xml/ServiceActivation"
     xmlns:xsl="http://www.w3.org/1999/XSL/Transform"
     xmlns:oms="urn:com:metasolv:oms:xmlapi:1"
     xmlns:java="http://xml.apache.org/xalan/java"
     xmlns:xalan="http://xml.apache.org/xalan"
     xmlns:mslv-sa="http://www.metasolv.com/oss/ServiceActivation/2003"
     xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
     xmlns:co="http://java.sun.com/products/oss/xml/Common">
     <xsl:param name="automator"/>
     <xsl:param name="log"/>
     <xsl:param name="context"/>
     <xsl:param name="outboundMessage"/>
     <xsl:template match="/">
          <xsl:apply-templates select="oms:GetOrder.Response">
               <xsl:with-param name="SERVICE_SUFFIX" select="'/APILink/CreditServices'"/>
               <xsl:with-param name="OSM_EVENT_TYPE" select="'NABS_CREDIT_EVAL'"/>
          </xsl:apply-templates>
     </xsl:template>
     <xsl:template match="oms:GetOrder.Response">
          <xsl:param name="SERVICE_SUFFIX"/>
          <xsl:param name="OSM_EVENT_TYPE"/>
*<xsl:variable name="void2" select="java:setStringProperty($outboundMessage, '_wls_mimehdrContent_Type', 'text/xml; charset=UTF-8')"/>*
*<xsl:variable name="void3" select="java:setStringProperty($outboundMessage, 'SERVICE_SUFFIX', $SERVICE_SUFFIX)"/>*
*<xsl:variable name="void4" select="java:setStringProperty($outboundMessage, 'OSM_EVENT_TYPE', $OSM_EVENT_TYPE)"/>*
          <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
               <env:Body env:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/">
                    <xsl:choose>
                         <xsl:when test="count(oms:_root/oms:cpr) + count(oms:_root/oms:birthDayPart) >0">
                              <xsl:call-template name="private" />
                         </xsl:when>
                         <xsl:when test="count(oms:_root/oms:cvr) > 0">
                              <xsl:call-template name="business" />
                         </xsl:when>
                    </xsl:choose>
               </env:Body>
          </env:Envelope>
     </xsl:template>
     <xsl:template name="private">
          <m:validatePrivateCustomer xmlns:m="java:dk.tdc.apilink.logic.sessions.interfaces">
               <validateCustomerCreditInput xsi:type="n1:ValidateCustomerCreditInput" xmlns:n1="java:dk.tdc.apilink.logic.datatypes">
                    <accountCategory xsi:type="java1:char" xmlns:java1="java:language_builtins">
                         <xsl:text>I</xsl:text>
                    </accountCategory>
                    <adrLocation xsi:type="xsd:string">
                         <xsl:value-of select="oms:_root/oms:houseNo"/>
                    </adrLocation>
                    <adrStreetName xsi:type="xsd:string">
                         <xsl:value-of select="oms:_root/oms:streetName"/>
                    </adrStreetName>
                    <adrZip xsi:type="xsd:string">
                         <xsl:value-of select="oms:_root/oms:zipCode"/>
                    </adrZip>
                    <xsl:choose>
                         <xsl:when test="count(oms:_root/oms:birthDayPart) > 0">
                              <birthDate xsi:type="xsd:string">
                                   <xsl:value-of select="substring(oms:_root/oms:birthDayPart,1,4)"/><xsl:text>.</xsl:text>
                                   <xsl:value-of select="substring(oms:_root/oms:birthDayPart,5,2)"/><xsl:text>.</xsl:text>
                                   <xsl:value-of select="substring(oms:_root/oms:birthDayPart,7,2)"/>
                              </birthDate>
                         </xsl:when>
                         <xsl:otherwise>
                              <birthDate xsi:type="xsd:string">
                                   <xsl:text>19</xsl:text>
                                   <xsl:value-of select="substring(oms:_root/oms:cpr,5,2)"/><xsl:text>.</xsl:text>
                                   <xsl:value-of select="substring(oms:_root/oms:cpr,3,2)"/><xsl:text>.</xsl:text>
                                   <xsl:value-of select="substring(oms:_root/oms:cpr,1,2)"/>
                              </birthDate>
                         </xsl:otherwise>
                    </xsl:choose>
                    <firstName xsi:type="xsd:string">
                         <xsl:value-of select="oms:_root/oms:firstName"/>
                    </firstName>
                    <lastBusinessName xsi:type="xsd:string">
                         <xsl:value-of select="oms:_root/oms:lastName"/>
                    </lastBusinessName>
               </validateCustomerCreditInput>
          </m:validatePrivateCustomer>
     </xsl:template>
     <xsl:template name="business">
          <m:validateCompanyCustomer xmlns:m="java:dk.tdc.apilink.logic.sessions.interfaces">
               <validateCustomerCreditInput xsi:type="n1:ValidateCustomerCreditInput" xmlns:n1="java:dk.tdc.apilink.logic.datatypes">
                    <accountCategory xsi:type="java1:char" xmlns:java1="java:language_builtins">
                         <xsl:text>B</xsl:text>
                    </accountCategory>
                    <cvrNumber xsi:type="xsd:string">
                         <xsl:value-of select="oms:_root/oms:cvr"/>
                    </cvrNumber>
               </validateCustomerCreditInput>
          </m:validateCompanyCustomer>
     </xsl:template>
</xsl:stylesheet>

I have written an UDF to determine the filename dynamicly:
//write your code here
String str = "SAPDATA-" + a + "ES" + ".xml";
DynamicConfiguration conf = (DynamicConfiguration)
container.getTransformationParameters().get(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey FileName = DynamicConfigurationKey.create("http:/"+"/sap.com/xi/XI/System/File","FileName");
conf.put(FileName, str);
return "";

Jms message filtering with multiple fields

Hi
Can anybody please tell me how to do message filtering with multiple fields. i using jdeveloper11.1.1.4.0 , soa11g suite and weblogic 10.3.
previously i used JMSType property for one field filtering.
and is it possible to invoke jms adapter with our own properties (adding property to jms).
thanks,
Sourbh

thanks atheek
i worked with the same and it helped me a lot i can share one more link that will help.
http://forums.oracle.com/forums/thread.jspa?messageID=9650255&#9650255
Regards,
Sourbh.

How to read JMS message properties from BPEL or BPMN process

Hi all,
I have a JMS Adapter that consumes messages from a remote ActiveMQ queue and I don't find the way the get the properties of the JMS message as I would like to map them in BPEL or BPMN process variable. I only manage to get the content of the message.
I've also read that if using a MapMessage, one of the map entry can be mapped directly and that the other map entries go to jca.jms.Map.xxxx where xxxx is key of the map entry.
But how can I map those "jca.jms.Map.xxxx" properties on process variables ? and how to map JMS Properties (that seem to be mapped on jca.jms.JMSProperty.xxxx) to process variables ?
I use SOA Suite version : 11.1.1.4.0
Thanks for your help

SOA Suite 11g - how to set/get JMS headers ?

Setting additional JMS message properties

Hi ALL,
I have a requirement where I need to create an adapter module to set additional message property for JMS.
The property name has to be Key_String specifically.
I am not sure whether to specify this name in the code written for the module or in the channel configuration.
Please help.
Thanks n regards
Pushpinder Kaur

You can use adapter specific message attributes for this.
See online help, scroll down to "Advanced Tab Page"
http://help.sap.com/saphelp_nw04/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
Hope that helps
Stefan

JMS Message Bridge with MQ, only BytesMessage available ?

I have successfully set up bridging between MQ and JMS, and have an MDB that receives messages via the bridge when a message producer puts messages on the MQ-queue. Ideally, I would like to receive MapMessages and not BytesMessages which seems to be the case. Is this at all possible ? It is not clear to me if this is determined by how messages are delivered to the MQ-queue or if it is a bridge configuration issue. The message producer uses the MQ Java API and not JMS to produce and publish messages.

The bridge uses the standard JMS API to dequeue the messages from MQ and provides no vendor specific tuning, so as long as IBM MQ supplies a map message in the first place things should work. In other words, if there's any special configuration required to get MQ to deliver map messages, you'll need to tune MQ, not WebLogic.
          Tom
          Bridges aren't often required for receiving from non-WebLogic JMS. See
          http://e-docs.bea.com/wls/docs81/faq/interop.html

Specifying additional JMS message attributes in Sender Adapter

Hi,
Iam using sender JMS adapter and I have to use the option " Specify Additional JMS Message Properties" for adding addtionalJMS properties in XI message header.
Once I cselect the option in the below table Iam not able to add new lines to add addtional JMS Message Properties..But In receiver adapter I was able to add the new lines.
Is this option graded in SAP PI 7.3 or relatd to any authorization issue..?
Is anyone faced this issue before.. Please help me out
Thank you

Hi everybody
I'm starting a project where I have to take adptadores JMS and I'm in the same situation kirian, I am need to configure a JMS adapter with version of SAP PI 7.3 and I wonder if anyone can help me or give me manuals leagues where information comes related.
Someone can help me with this information
Regards

How to do service callout with the incoming JMS message in OSB 11g

Hello All,
I have a specific requirement for which I am creating a kind of POC where I need some help in OSB, however am new to OSB.
My Environment:
1> I have a request queue (deployed on a WLS domain) - WFReq_WS
2> I have a response queue (deployed on a WLS domain) - WFRes_WS
3> I have created a ProxyService (request/response type) in OSB 11g which is simply mapping the incoming message in WFReq_WS to WFRes_WS
4> I have a WebService (it is currently a simple hello WebService for testing) which takes a string and returns the same string with an added 'Hi' in front of it (e.g. If you send Jack, it will return 'Hi Jack')
My Requirement:
1> I have to do some mechanism in OSB, by which while mapping the message from WFReq_WS to WFRes_WS (through the proxy service I have), it will pick the JMS message (which will be a string/text) and will make a service callout to the Webservice I mentioned using the message as the input parameter of the WebService.
2>Now when the response of the WebService will come, OSB should send this response as the message in the response queue (WFRes_WS) I mentioned above.
To simplify the requirement using an example:
A> I will send a text/String message (say Jack) to the request queue (WFReq_WS)
B> OSB should pick the message (Jack) and make a service callout to the webservice
C> webservice will return 'Hi Jack'
D> OSB should send this to the response queue (WFRes_WS)
I know the above might look very basic question to the PROs, but please elaborate (step by step) what need to be done, since I do not know OSB.
Thanks a lot for your help !

Your example points A and D are easily done by having a "Proxy Service" which has the following details:
Service Type = Messaging Service
Request and Response type = Text
Protocol = jms
Endpoint URI = your request queue (format like 'jms://localhost:7013/weblogic.jms.XAConnectionFactory/QueueJNDIName')
Checkmark "response" so that the proxy service automatically delivers the response to another queue - your response queue
Response URI = jms://localhost:7013/weblogic.jms.XAConnectionFactory/QueueResponse
Now since your "Hello" webservice is (probably) a SOAP xml service you need to "convert" your text based JMS message to xml before sending it on to the "Hello" service.
Your JMS proxy can do that by just doing a "Assign <whom>{$body/text()}</whom>" to a variable (lets call it 'reqHello')
Now your JMS proxy should actually call the Hello service and since your JMS proxy is text and the Hello service is SOAP you cannot just "pass" on to the Hello service in a "Route to". Instead you can do a Service Callout where you can specify your "reqHello" variable as payload and a "respHello" as response variable.
Now you have the "<whom>Hi jack</whom>" in the response variable and since the JMS response needs to be text format you can "extract" the text value into the body variable of the JMS proxy (use "replace /* in body with $respHello/text()" - replace node contents)
The actual Hello service is a simple "SOAP" based Proxy Service. Add a pipeline and add a stage in the reponse pipeline. Do a ...
Assign fn:concat("Hi ",$body/whom/text()) to $whomVar
Replace whom in body with $whomVar (replace node contents)

Error in JMS message routing

Hi,
I am doing interface which send JMS messages to IDOC. JMS is sending three different messages (three XSD's) and I have created three separate interfaces as a below.
A) Negative.xsd ; to IDOC1
B) Positive.xsd ; to IDOC2
C)Multiple.xsd ; to IDOC3
When I get the Negative.xsd from JMS for the first time, Interface u2018Au2019 is executing and itu2019s creating IDOC1 successfully. When I get the Negative.xsd for the second time then the Interface u2018Bu2019 is executing (Instead of Interface u2018Au2019) and itu2019s trying to send Negative.xsd into IDOC2 and itu2019s getting fail.
When we are getting all the three XSDu2019s at the same time then first interface u2018Au2019 is getting picked up and failed for the second (u2018Bu2019) and third (u2018Cu2019) interfaces and for first one is successful.
Can you please guide me to pick the right interface?
Regards,
Kishore

Hi, Kishore:
In your situation, you need to configure Message Selector for your JMS sender adapter:
1. First you have to work with your JMS Queue system consultant, create a Property name, Saying "MsgType", its value is used to identify type of the message. e.g. the message of Positive Type put into the queue, its Property value "MsgType" can be set to "Positive"
2. In your JMS Communication Channel, Parameter Tab -> Advanced Tab, you need to Check " Adapter Specific Message Attribute"
3. Then Check "Specify Additional JMS Message Properties
Click "+" to add your property name, it should match the property name mentioned in step 1. e.g. "MsgType"
4. In "Process" tab, you specify message Selector:
e.g. MsgType = Positive"
After you have done above step, this JMS adapter only pick message of the Property value "MsgType" equals to "Postive"
You can create additonal JMS commnunication channels that polling from same queue, but only for different type of message: e.g. "Negative"
Regards !
Liang

JMS Message Property

Hello Experts,
we have a JMS to JMS scenario. A third party system sends a message to the JMS Queue (JMS Provider is the J2EE SAP Web AS, XI system). Via JMS Message Selector (configured the JMS Sender Adapter) the right integrationprocess get the message.The integrationsprocess sends the message to another JMS Queue. Because the integrationprocess have lost the JMS Header information (message properties) we configured the JMS Sender Adapter and the JMS Receiver Adapter to copy message properties. Described under help.sap.com:
you want to set additional JMS message attributes, select Specify Additional JMS Message Properties (Maximum of 10).
· In the table, enter the names of the JMS message properties whose values are to be included in the message header of the XI message.
The technical names of the additional attributes are DCJMSMessageProperty0, DCJMSMessageProperty1, ..., DCJMSMessageProperty9.
You can enter more than 10 properties in the table, but only the first 10 are taken into account.
The attribute namespace for the adapter is http://sap.com/xi/XI/System/JMS.
I debug and saw that the message properties was sucessfully copied to the header (receiver queue). But now if I use another selector the message will not found. It doesn't work with a third party system and with SAP XI (I've created another integrationsprocess, to read the queue)
Thanks very much, for your help.
Regards,
Jürgen

Hi there,
there is a way (and a section somewhere in the help) to set adapter specific attributes in java mappings.
The java doc for that can be found here:
https://help.sap.com/javadocs/NW04/current/pi/index.html
Hope that helps sbd who also has that prob.
Cheers,
Helge

JMS Message Headers

Hi,
I have a IDOC -> SAP PI -> JMS scenario. JMS service is an External Party.
I have to populate the JMS message Header with Fields like JMSType, Sender and Receiver. These fields will come from the IDOC. How to populate these?
<JMSType>Notification</JMSType>
<Sender>SAPR3</Sender>
<Receiver>JMSService</Receiver>
If I am not wrong, I have to make use of Dynamic Configuration and populate, but if I look at the available JMS ASMA, I am not able to decide how (which fields to use) to populate. Earlier I had done Dynamic Configuration for FILE and SOAP adapters.
Thank you,
Pankaj.
Edited by: Pankaj Sharma XI on Oct 4, 2010 2:38 PM

Hi Raj and Amol,
Thank you for responding.
anyway you can try to use dynamic configuration UDF, it will work.
Yes I will do it using UDF.
Add AF_Modules/DynamicConfigurationBean and set the value of the above
If I use DynamicConfigurationBean, then the value will be static, the one which I fill in the Communication Channel. So I have to make use of UDF.
What I think is:
1) Create a UDF in message mapping with below logic:
DynamicConfiguration conf = (DynamicConfiguration) container.getTransformationParameters().get
(StreamTransformationConstants.DYNAMIC_CONFIGURATION);
DynamicConfigurationKey key1 = DynamicConfigurationKey.create("http://sap.com/xi/XI/System/JMS","DCJMSMessageProperty0"); //also logic for Property1 and Property2.
conf.put(key1,MessageType); //MessageType comes from IDOC.
return ""; //no need to return a value.
2) Create a Receiver JMS channel with below settings:
Specify Additional JMS Message Properties
Name - MsgType               Java Type - String
Name - Sender               Java Type - String
Name - Receiver               Java Type - String
Now with the above settings I should (hopefully) get the headers like:
<MsgType>AbcValidation</MsgType>
<Sender>SAPR3</Sender>
<Receiver>JMSReceiver</Receiver>
I will try with the above configuration and update the thread accordingly. *If you feel that the approach is wrong/ incomplete, then
please do respond.*
Thank you,
Pankaj.

Trouble using JMS Message Selector and DCJMSMessageProperty0

Hello Experts!
My scenario is Mainframe => MQ => JMS Adapter => XI => SAP
My MQ channel is communicating fine to XI and I've set the JMS adapter to JMS Compliant.
I have multiple message types with consistent headers but varying data layouts that I need to route to different mapping objects. So it seems the best solution for this is JMS Message Selector based on reading a header value from one of the dynamic message properties.
I've read SAP Notes and SAP Library and SDN Wiki articles about this configuration and I think its possible.
http://help.sap.com/saphelp_nw04s/helpdata/en/10/b1b4c8575a6e47954ad63438d303e4/frameset.htm
Note 856346 - J2EE JMS Adapter: Frequently Asked Questions (FAQ)
Note 1086303 - XI JMS Adapter and IBM Websphere MQ: FAQ
https://www.sdn.sap.com/irj/scn/wiki?path=/display/xi/usage%252bof%252bmessage%252bselector%252bfor%252bjms%252bsender%252badapter
My mainframe sends an MQ message that includes some extra header information like
field: ApplType VALUE: 000000002
field: ApplName VALUE: MIS056O
I configured my Communication Channel to set Adapter-Specific Message Attributes and also Additional JMS Message Properties to include ApplType and ApplName.
However, I can only see some of the standard JMS header items such as CorrelationID, none of the additional ones.
In RWB I see "JMS property 'ApplType' that corresponds to dynamic header 'DCJMSMessageProperty0' is missing from JMS message 'ID:f2f0f0f9f0f4f2f1f0f9f1f5f5f3f7f44040404040404040'; consequently it cannot be added to XI message 'e136a6e8-8580-4adc-2007-9ccab93f1ef4' as a dynamic header"
Can anyone with some experience doing this help me see if I'm missing a trick somewhere? How can I see where this information is being dropped? Could it be when MQ is handing to JMS?
Many thanks,
Aaron

After sifting through some IBM documentation I found that the PutApplName field actually maps to JMS name JMSXAppID. So after adding this to my Additional JMS Message Properties list I get the dynamic JMS message property I need for sorting out the messages.
http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/topic/com.ibm.mq.csqzaw.doc/uj25450_.htm

JMS Message Bridge - WLS to MQ

Hi,
Subsequent to my last posts on Foreign JMS Server setup (where I had to receive a msg from a remote MQ Queue), now I have a requirement to post messages to an remote MQ Queue for a diff application.
As a POC, I configured the JMS Message Bridge with bridge source as my local JMS queue and bridge destination as the Remote MQ Queue and it works fine as expected !!
just have couple of questions on that -
1. For a long time, I was struggling with this error on server startup
<BEA-190032> << eis/jms/WLSConnectionFactoryJNDINoTX > ResourceAllocationException thrown by resource adapter on call to ManagedConnectionFactory.createManagedConnection(): "javax.resource.ResourceException: Failed to start the connection ">
Then I realized from the server log that the actual reason was authentication failure in MQ Queue Manager :
JMSWMQ2013: The security authentication was not valid that was supplied for QueueManager '' with connection mode 'Client' and host name '77.40.190.130'. Please check if the supplied username and password are correct on the QueueManager you are connecting to AND
JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').
Since this MQ setup is managed by someone else, when they pass on the .binding file after creating queuemanager, queue, etc, Should I also ask them for the username and password for the QM?? I am not sure if this is a part of the .binding file.
2. Some doubts around the QOS. As I understood, I am using the No-Transaction Adapter. This means I can use QOS as either "Atmost once" or "Duplicate OK". The latter seems to be ok so that I dont lost messages in any case. But I am yet to find out if the other application is ok to handle duplicates.
But is there a restriction/limitation to use "Exactly Once" ?? I noticed that there is also an XA-Transaction Adapter in WLS. Is it not possible to use that with MQ?
Thanks in advance.
best regards,
Murali

In your binding file QCF or XAQCF definition , you will see a Channel field since you are using a client mode to connect to the queue manager. This channel is called a Server Connection Channel [ SVRCONN]. At the queue manager side of things, when this SVRCONN is defined, MQ Admin teams tend to define an attribute called MCAUSER. In this setup the userid used for authorisation at queue manager is the following in the below precedence:
1. If MCAUSER is defined in the channel, that will be the user id and it overrides any security context sent from client application. This user id should have sufficient permissions to connect to queue manager , get , put. The MQ admin teams on certain platforms will be able to get the exact permission that is missed from the queue manager error logs when a 2035 security exception occurs.
2. If no MCAUSER is defined then the userid passed in the createConnection JMS call will be the user context used.
I am not exactly sure of the behaviour when no MCAUSER and no user id in createConnection calls, but i think it takes the user of the MQ Listener process which starts the SVRCONN channel instance when a client initiates the connection.
So for your situation, it will be worth start checking with how the MQ side configuration is. This issue tends to be a very common issue with client applns connecting to qmgr.

Specify JMS message properties with UMS send protocol ?

Similar Messages

Maybe you are looking for