Problem setting a provider specific property : JMS adapter

Hi Experts:
I need to set a provider specific property as required by the third party in a IDoc to JMS scenario.
The property name starts with JMS_ and is offcourse a property specific to the JMS provider.
The way I am setting it is I have declared a Additional JMS message property by the same name as desired by the third party say
JMS_XXX
and then using the DynamicConfigurationBean I assign a value to this in the reciever channel.
The problem that we have observed is, all other properties are set as desired, only this one for which the name starts with JMS_ is not set correctly.
Is it possible to set such a provider specific property using XI or not?

Hi Amol,
Adapter-Specific Message Properties
·        To store adapter attributes in the message header of the XI message, select Set Adapter-Specific Message Properties.
·        To apply the following attributes in XI message headers, set the corresponding indicators:
       Name                                           Technical Name
JMS Message Correlation ID               DCJMSCorreleationID
JMS Message Delivery Mode               DCJMSDeliveryMode
JMS Message Destination                   DCJMSDestination
JMS Message Expiration                     DCJMSExpiration
JMS Message ID                                DCJMSMessageID
JMS Message Priority                         DCJMSPriority
JMS Message Redelivered Flag            DCJMSRedelivered
JMS Message ReplyTo Destination      DCJMSReplyTo
JMS Message Time Stamp                   DCJMSTimestamp
JMS Message Type                              DCJMSType
Used JMS Message Selector                 DCJMSMessageSelector
Used JMS Message Queue                    DCJMSMessageQueue
JMS User                                                DCJMSUser
        If you want to set additional JMS message attributes, select Specify Additional JMS Message Properties (10 Maximum).
·        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.
if found worth pls do the req
Thanx
Sampath

Similar Messages

How to set ApplIndentityData header field in JMS adapter

Hi Guys ,
    I have one requirement for update the field in SAP JMS header. I am using transport protocol for IBM Websphere MQ in JMS adapter.
While sending data to IBM Websphere MQ Queue via JMS Adapter, need to set the field called ApplIndentityData with the appropriate value which is populate to a MQHRF2 header of a message.
So, regarding that where will do it? Means JMS receiver adapter or IBM MQ level. If JMS receiver adapter, I think using ASMA, So please guide me how to set this filed value in JMS adapter or share any document you have.
Thanks & regards
Vijaykumar S

Hi RejaSekar,
       I reffered your blog and did the below settings in JMS module and ASMA settings.
1) Changed the mode for u201CJMS-Complaintu201D instead of u201CWebsphere MQ(non JMS)u201D
2) Additional JMS message properties tab created below property name and java type.
       LocalName    --> String
       Partname      --> String
3) In module parameter tab added the below module name and key
    AF_Modules/DynamicConfigurationBean   --> LocalEnterpriseBean --> RFH2HEADER
4) Under parameter Tab
     RFH2HEADER       -->   key.0      -->     insert http://sap.com/XI/System/JMS DCJMSMessageProperty0
     RFH2HEADER       -->   key.1      -->     insert http://sap.com/XI/System/JMS DCJMSMessageProperty0
     RFH2HEADER      --> value.0    -->    LocalName
     RFH2HEADER      --> value.1    -->    PartnerName
Kindly check the above settings whether this is correct or wrong. If anything wrong please let me know what we need to change JMS receiver adapter.
Actually my requirement is need to set these parameters and set the value to that parameters and pass in to /usr folder of a WebsphereMQ message.
Kindly check and help me out.
Thanks & regards
Vijayakumar S

Problem setting up connection with 2wire USB adapter (BT Home Network 1200)

I keep on running into a brick wall setting up my internet connection on my newly purchased MacBook (I have never used a mac before, having used a PC for years). I am trying to set up my macbook as an additional computer on my BT Home Network 1200, and I have installed the drivers given on the 2wire CD, but even when I plug in the USB adapter, the Macbook does not seem to recognise it. The adapter looks something like this:
Anyway, the instructions given in the BT Home Network PDF manual seem to suggest that it is relatively straightforward, and that it is simply a matter of clicking the apple menu, selecting "control panels", selecting "TCP/IP", and then in the "connect via" box, clicking on the pulldown menu and selecting 2Wire PC Port. However, I am using 10.4.9 and it seems to me that this guide must have been written for an outdated version of Mac OS X because none of these instructions seem to make sense or work in the context of my macbook. At the moment, it seems like I won't be able to get my macbook online. Could someone please help explain to me how to get around this?

Any reference to 'Control Panels' will, indeed, be for Mac OS 9.x, the last version of which (9.2) was released in 2001.
My advice would be to return it to BT and ask them for an ethernet-based modem, not a USB one.
USB DSL modems have varying levels of support in Mac OS X ranging from poor to none. The fact that 2Wire doesn't include Mac OS X instructions implies that this model is at the lower end of that scale.
By comparison, an ethernet-based modem will connect to your Mac via ethernet, have the option of sharing the connection with multiple machines, typically be faster, and has an almost 100% compatibility rate.

How to set property for Cluster Environment for JMS Adapter

Hi All,
I am moving from DEV to Prod environment which is cluster.
Can you Please explain me what property I need to Set for Cluster Environment for JMS Adapter, so that I could avoid race condition for Dequeue/enqueue.
I am using soa suite 10.1..3.4
Thanks in Advance.
Edited by: vikky123 on Jul 12, 2010 7:03 AM

put something like this
<activationAgents>
      <activationAgent className="oracle.tip.adapter.fw.agent.jca.JCAActivationAgent" partnerLink="PARNERLINKNAME">
        <property name="clusterGroupId">SOMEUNIQUEVALUE</property>
        <property name="portType">PARTNERLINK_PORTTYPE</property>
      </activationAgent>
    </activationAgents>

Reveiver JMS Adapter error

Hi All,
we are getting the folowing error in Receiver JMS adapter.
Delivery of the message to the application using connection JMS_http://sap.com/xi/XI/System failed, due to: com.sap.aii.af.ra.ms.api.RecoverableException: The JMS channel with channel ID 88259a4ea44537c6b7f6c08de5630e2a is errornous. Details:Problem with JMS queue connection; provider error code: C4002, provider error message: [C4002]: Read packet failed. - cause: java.net.SocketException: Connection reset: com.sap.aii.af.service.jms.XIJMSException: The JMS channel with channel ID 88259a4ea44537c6b7f6c08de5630e2a is errornous. Details:Problem with JMS queue connection; provider error code: C4002, provider error message: [C4002]: Read packet failed. - cause: java.net.SocketException: Connection reset
I look forward to hearing from you.
Thanks,
Jag

Hi,
Please see if the JMS channel is open and have mentioned properly.
along with it look if the Queue manager is fine.
Threads that have the same issues:
connection with the JMS provider
configuration of JMS adapter Using WebSphereMQ
Thanks
Swarup

JMS adapter insufficient

Hi,
I'm implementing a connection from MQ to SAP, through XI.
The simple things work, but I do have some problems with the more complex scenario's.
I think the JMS-adapter isn't sufficient enough for my implementation :
     - performance : a load off messages takes ages => multithreading ?
     - multiple IDoc types:
          I have 4 IDoc types that should be processed in the right order. If one adapter could read them all, the order would be right,
          but the adapter can't read different sorts of IDocs so I had to split them over 4 queues, in which case the order becomes a problem.
     - when there is a connection problem (network drop or so), the JMS adapter doesn't recover.
My question is :
     should I go for a java proxy to get the messages from the queue and into XI (in effect write my own JMS-code) ?
     If so, since I've never created a proxy, does anyone have some sample code with an MQ-connection ?
Regards
T

Hi Tom,
I don't have specific code for proxy. However, I will explain the steps:-
ABAP proxies are created in SPROXY transaction. This is executed on the Application System (not the integration server). As part of the config of the WAS, an HTTP destination to the IS is maintained in SM59. This allows the Appl system to retrieve the WSDL desc of the interface as the basis of proxy generation.
Use SPROXY transaction on the application system. Right click on your relevant interface and choose Create. Enter the Prefix and Package to generate unique names. The system generates methods --> EXECUTE_SYNCHRONOUS and EXECUTE_ASYNCHRONOUS based on the interfaces. Once you are done with this you can apply your code.
To generate proxies for java applications, right click on the interface in the IR and choose Java Proxy Generation. The wizard will get started. Specify if this is a new proxy or a regenerated proxy (if the interface is changed after a proxy has been generated, you must regenerate and recompile). Select the software comp version that contains the interfaces. Select the message interface to use as the basis of proxy generation. Click Finish to generate the java classes.
Regards.
Praveen

Language support in JMS adapter with Oracle JDev 10.1.3.1

Hi,
I' using JDeveloper 10.1.3.1 with Oracle SOA Suite - ESB 10.1.3.1 in the following scenario:
1) Use Database adapter with "on insert" condition to read Student record with Chinese name (Unicode format) - ESB process
2) Use JMS adapter to push this data into "DemoTopic" as string - ESB process
3) Use Message Driven Bean's (EJB 3.0) "onMessage" method to fetch the data from JMS topic - J2EE app
4) Use JDBC executeUpdate to update this Chinese name into another database table - J2EE app
5) Finally, verify the updated Chinese name in ADF application - J2EE app
Prerequisites
1) The database charset on both sides of the flow is UTF8
2) The ADF application JSF page encoding is UTF8
3) The SOA Suite is installed on DB repository (UTF8 charset)
Result
1) The flow from Step 1-5 works.
2) But, the println of the JMS message (holding the Chinese name) gives "????" when checked with Wordpad (Unicode readable word processor)
3) Junk characters are inserted into the database
Please let me know where I'm going wrong. Also, let me know if I need to configure/set the character encoding in OC4J, or the JMS adapter and how.

Hi all,
This is been resolved by using the AL32UTF8 character set in the database. JMS adapter by default supports UTF-8. No setting/configuration needs to be done.

Provider-specific properties

Hi Experts,
What is the effect on authorization if value is set in provider-specific properties screen? For example, I set a constant value to the dimension element.
Regards
YHogan

Hi Friends,
Any side effects encountered on authorization when this is set and then unset?
regards
YHogan

How to Set JMS property and Read JMS property in BPEL using JMS adapter

Does any one know how to set or read more than one JMS property in BPEL using JMS adapter. My queue server is Oracle JMS server.
Any help and sample is well appreciated

Hi Van
I have noted that only the attribute "type" is missing. It seems that when you create a "string" property, the attribute "type" is droped from the XML. If you use another type (as "integer" or "double") it stays there.
If you try to read your properties, except for the "type" attribute, you should be successful, as I am. If you need, please tell me your email, I can send you my code.
Source Code:
in ASSIGN activity (process which SENDS the JMS message):
<assign name="TESTES">
<copy>
     <from expression="'string'"/>
     <to variable="HeaderJms" part="outboundHeader"
     query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[1]/@type"/>
</copy>
<copy>
     <from expression="'name'"/>
     <to variable="HeaderJms" part="outboundHeader"
     query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[1]/@name"/>
</copy>
<copy>
     <from expression="'value1'"/>
     <to variable="HeaderJms" part="outboundHeader"
     query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[1]/@value"/>
</copy>
<bpelx:append>
     <bpelx:from>
     <Property name="" type="" value=""
          xmlns="http://xmlns.oracle.com/pcbpel/adapter/jms/"/>
     </bpelx:from>
     <bpelx:to variable="HeaderJms" part="outboundHeader"
          query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties"/>
</bpelx:append>
<copy>
     <from expression="'string'"/>
     <to variable="HeaderJms" part="outboundHeader"
     query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[2]/@type"/>
</copy>
<copy>
     <from expression="'name2'"/>
     <to variable="HeaderJms" part="outboundHeader"
     query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[2]/@name"/>
</copy>
<copy>
     <from expression="'value2'"/>
     <to variable="HeaderJms" part="outboundHeader"
     query="/ns5:JMSOutboundHeadersAndProperties/ns5:JMSOutboundProperties/ns5:Property[2]/@value"/>
</copy>
</assign>
in ASSIGN activity (process which READS the JMS message)
<assign name="Assign_1">
<copy>
<from variable="Variable_1" part="inboundHeader"
query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[10]/@name"/>
<to variable="temp"/>
</copy>
<copy>
<from variable="Variable_1" part="inboundHeader"
query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[10]/@value"/>
<to variable="temp"/>
</copy>
<copy>
<from variable="Variable_1" part="inboundHeader"
query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[12]/@name"/>
<to variable="temp"/>
</copy>
<copy>
<from variable="Variable_1" part="inboundHeader"
query="/ns3:JMSInboundHeadersAndProperties/ns3:JMSInboundProperties/ns3:Property[12]/@value"/>
<to variable="temp"/>
</copy>
</assign>
Note that I do not try to read the "type" attribute, otherwise it will fail.
Here is the JMS Header Message received:
<inboundHeader>
<JMSInboundHeadersAndProperties xmlns="http://xmlns.oracle.com/pcbpel/adapter/jms/">
<JMSInboundHeaders>
<JMSCorrelationID>
bpel://localhost/pi_lms-c001e/BpelPiAtualizacaoC001E~1.0/3200025-BpInv0-BpSeq1.6-2
</JMSCorrelationID>
<JMSDeliveryMode>2</JMSDeliveryMode>
<JMSExpiration>0</JMSExpiration>
<JMSMessageID>ID:467DFA1FA1ED459EBF37F51F596C3F12</JMSMessageID>
<JMSPriority>4</JMSPriority>
<JMSRedelivered>false</JMSRedelivered>
<JMSType>com.mercurio.lms.integration.c001eip.c001EIntegrationPoint</JMSType>
<JMSTimestamp>1201552046253</JMSTimestamp>
</JMSInboundHeaders>
- <JMSInboundProperties>
<Property name="JMSXDeliveryCount" type="integer" value="1"/>
<Property name="JMSXRecvTimestamp" type="long" value="1201552046698"/>
<Property name="JMSXUserID" value="lms_dev_int_v1_user"/>
<Property name="JMS_OracleDeliveryMode" value="2"/>
<Property name="JMS_OracleTimestamp" type="long" value="1201552046253"/>
<Property name="JMS_OracleDelay" type="long" value="0"/>
<Property name="JMSXState" type="integer" value="0"/>
<Property name="IAS_VERSION" value="10.1.3"/>
<Property name="JMS_OracleDeliveryMode" value="2"/>
<Property name="name" value="value1"/> ("type" attribute was droped!!!)
<Property name="JMS_OracleTimestamp" type="long" value="1201552046253"/>
<Property name="name2" value="value2"/> ("type" attribute was droped!!!)
</JMSInboundProperties>
</JMSInboundHeadersAndProperties>
</inboundHeader>
Regards
Marcelo

How to set JMS user property in JMS Adapter.

I am using Jdeveloper and SOA 11g. I want to filter some JMS messages from a topic based on a JMS user property. It is consumed using (JMS Adapter) consumer --> Mediator---> DBAdapter.
My Question is how to define a JMS user property using Jdeveloper 11g.
Thanks
Edited by: user5108636 on 24/06/2010 16:10

In Mediator mplan Assign Values use a property expression in the "to" side like:
jca.jms.JMSProperty.XXX
where XXX is the name of the property you would like to have created and populated. In source it will look like:
<Mediator name="A03QueueWFeedMediator" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns="http://xmlns.oracle.com/sca/1.0/mediator"
wsdlTargetNamespace="http://www.oracle.com/integration/b2b/A03QueueWFeedFromB2B/">
<operation name="receive" deliveryPolicy="AllOrNothing" priority="4"
validateSchema="false">
<switch>
<case executionType="direct" name="A03QueueWFeedToJMS.Produce_Message">
<action>
<transform>
<part name="$out.body"
function="xslt(xsl/ADT_AXX_To_ADT_AXX.xsl, $in.body)"/>
</transform>
<assign>
<copy target="$out.body/imp1:ADT_AXX/imp1:MSH/@Type"
value="$in.property.b2b.documentDefinitionName"
xmlns:imp1="NS_64FCBED013AA409D933F624674E67BF220070423183755"/>
<copy target="$out.body/imp1:ADT_AXX/imp1:MSH/@ID"
value="$in.property.b2b.fromTradingPartnerId"
xmlns:imp1="NS_64FCBED013AA409D933F624674E67BF220070423183755"/>
<copy target="$out.body/imp1:ADT_AXX/imp1:MSH/@Name"
value="$in.property.b2b.toTradingPartnerId"
xmlns:imp1="NS_64FCBED013AA409D933F624674E67BF220070423183755"/>
<copy target="$out.property.b2b.conversationId"
value="$in.property.b2b.conversationId"/>
<copy target="$out.property.b2b.documentDefinitionName"
value="$in.property.b2b.documentDefinitionName"/>
<copy target="$out.property.b2b.documentProtocolName"
value="$in.property.b2b.documentProtocolName"/>
<copy target="$out.property.b2b.documentProtocolVersion"
value="$in.property.b2b.documentProtocolVersion"/>
<copy target="$out.property.b2b.documentTypeName"
value="$in.property.b2b.documentTypeName"/>
<copy target="$out.property.b2b.fromTradingPartnerId"
value="$in.property.b2b.fromTradingPartnerId"/>
<copy target="$out.property.b2b.fromTradingPartnerIdType"
value="$in.property.b2b.fromTradingPartnerIdType"/>
<copy target="$out.property.b2b.toTradingPartnerId"
value="$in.property.b2b.toTradingPartnerId"/>
<copy target="$out.property.b2b.toTradingPartnerIdType"
value="$in.property.b2b.toTradingPartnerIdType"/>
*<copy target="$out.property.jca.jms.JMSProperty.conversationId"*
value="$in.property.b2b.conversationId"/> <copy target="$out.property.jca.jms.JMSProperty.documentDefinitionName"
value="$in.property.b2b.documentDefinitionName"/>
<copy target="$out.property.jca.jms.JMSProperty.documentProtocolName"
value="$in.property.b2b.documentProtocolName"/>
<copy target="$out.property.jca.jms.JMSProperty.documentProtocolVersion"
value="$in.property.b2b.documentProtocolVersion"/>
<copy target="$out.property.jca.jms.JMSProperty.documentTypeName"
value="$in.property.b2b.documentTypeName"/>
<copy target="$out.property.jca.jms.JMSProperty.fromTradingPartnerId"
value="$in.property.b2b.fromTradingPartnerId"/>
<copy target="$out.property.jca.jms.JMSProperty.fromTradingPartnerIdType"
value="$in.property.b2b.fromTradingPartnerIdType"/>
<copy target="$out.property.jca.jms.JMSProperty.toTradingPartnerId"
value="$in.property.b2b.toTradingPartnerId"/>
<copy target="$out.property.jca.jms.JMSProperty.toTradingPartnerIdType"
value="$in.property.b2b.toTradingPartnerIdType"/>
</assign>
<invoke reference="A03QueueWFeedToJMS" operation="Produce_Message"/>
</action>
</case>
</switch>
</operation>
</Mediator>
The runtime will see something like:
[2010-09-09T11:48:06.353+10:00] [AdminServer] [TRACE] [] [oracle.soa.adapter] [tid: weblogic.work.j2ee.J2EEWorkManager$WorkWithListener@60ddbc76] [userId: weblogic] [ecid: 0000Ifo9olH2zGWjLxmJOA1CY0sg0001jY,0] [SRC_CLASS: oracle.integration.platform.blocks.adapter.fw.log.LogManagerImpl] [APP: soa-infra] [dcid: 02d1ff4621073810:26418f01:12af379c141:-7fd3-0000000000000219] [SRC_METHOD: log] Jms Adapter A03QueueWFeed:A03QueueWFeedToJMS [ Produce_Message_ptt::Produce_Message(body) ] XMLHelper_convertJmsMessageHeadersAndPropertiesToXML: <JMSInboundHeadersAndProperties xmlns="http://xmlns.oracle.com/pcbpel/adapter/jms/">[[
<JMSInboundHeaders>
<JMSCorrelationID></JMSCorrelationID>
<JMSDeliveryMode>2</JMSDeliveryMode>
<JMSExpiration>0</JMSExpiration>
<JMSMessageID>ID:<911867.1283996886119.0></JMSMessageID>
<JMSPriority>4</JMSPriority>
<JMSRedelivered>false</JMSRedelivered>
<JMSType></JMSType>
<JMSTimestamp>1283996886119</JMSTimestamp>
</JMSInboundHeaders>
<JMSInboundProperties>
<Property name="documentProtocolVersion" value="2.3"/>
<Property name="toTradingPartnerIdType" value="Name"/>
*<Property name="conversationId" value="C0A83C0712AF42D840E0000074BA3CCC"/>* <Property name="documentTypeName" value="ADT"/>
<Property name="tracking_conversationId" value="C0A83C0712AF42D866F0000074BA3CD9"/>
<Property name="tracking_ecid" value="C0A83C0712AF42D866F0000074BA3CDA"/>
<Property name="tracking_compositeInstanceId" value="60019"/>
<Property name="documentProtocolName" value="HL7"/>
<Property name="documentDefinitionName" value="QH_ADT_Generic"/>
<Property name="tracking_parentComponentInstanceId" value="mediator:45E076D0BBB411DFAF05817F5F0DD1A1"/>
<Property name="fromTradingPartnerIdType" value="Name"/>
<Property name="fromTradingPartnerId" value="HOMER"/>
<Property name="toTradingPartnerId" value="Self"/>
<Property name="JMSXDeliveryCount" type="integer" value="1"/>
</JMSInboundProperties>
</JMSInboundHeadersAndProperties>
Edited by: Michael.Czapski on 8/09/2010 18:58

JMS adapter: Adapter specific message attributes

Hi,
I have a synchronous SOAP to JMS (MQ series) scenario where Im using sync/async bridge (without BPM).
I need to correlate the message being put on JMS queue (JMS receiver adapter) and the response (JMS sender adapter).
The standard receiver JMS adapter only allows the JMS correlation ID to be set to one of three different values (excluding NULL). 2 of these (reference and conversation ID) will be empty in my scenario, leaving me with only the XI message ID. This ID however exceeds the length of ie. the JMS correlation ID and thus isnt suitable for correlating anything using the field JMS Correlation ID.
NB: it is of no use to try and set the conversation ID at mapping time (using container object) since the changed value only is available during mapping execution.
Surely one way of setting the conversation ID would be to use an adapter module in SOAP sender, but this is not an option. Also the sender system will not provide one either.
Now the problem isnt setting the JMS correlation ID dynamically at runtime (this is achieved without trouble using the dynamic configuration API with the key DCJMSCorreleationID). The problem is to actually have XI correlate the request with the response.
Since the JMS collelation ID is smaller than the XI message ID and the conversation and reference ID isnt available, what I figure is that I need to find a MQ message property to use and then use the Set MSProperty to part instead this property surely needs to be large enough to contain the XI message ID.
So what I did was I looked in http://publib.boulder.ibm.com/infocenter/wmqv6/v6r0/index.jsp?topic=/com.ibm.mq.amqwak.doc/js50938.htm
where a list of fields in the message descriptor is available figuring I can just use one of these. Looking through the list I notice the field MDRQ (Name of reply queue, 48-byte character string) should be able to hold the XI message ID. So I add MDQR in the Specify additional JMS message properties and set the Java Type to String and also enter this field in the Correlation Setting of the receiver JMS adapter.
Runtime:
When looking in MDT I see:
New JMS message will be correlated with the XI message. Correlation rule: XI_MESSAGEID, correlated property: JMS property MDRM, correlation value: 36158680-5a0c-11dc-8c14-000f203cd3c8
I looks like a success! No data is however set in the field when looking at messages being put on MQ.
If I increase the trace level of the JMS adapter I can see (in defaultTrace) the following:
Cannot read the switch setting for property name DCJMSStringProperty0, switch name dynConfigDCJMSStringProperty0. It is switched off.
What does this error mean?
I have of course clicked Use adapter Specific Message-Attributes and also the Specify additional. In other words everything look ok in configuration.
Since Ive also put a check mark in Fail if adapter specific message attributes is missing I can see that I successfully put a value (using dynamic conf. at mapping time) in the field... but still something isnt right the value of the property never reached MQ.
Now Ive tried with a couple of fields in the message descriptor from the previous URL. XI complains all the time.
Anybody got some ideas?
Best Regards,
Daniel

Hi Vijay,
Thanks for your replay,as per your input i creted dynamic configuration method,
i taget structure luks like this
   <Data>
       <Mesage>
             <gl_update>
                  <header>
                        <ean1>
                        <ean2>
                  </header>
              <gl_update>
       <Message>
i written UDF and mapped to header element gl_update,
but i am getting below error message in MONI
SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="">
<SAP:Category>Application</SAP:Category>
<SAP:Code area="MAPPING">EXCEPTION_DURING_EXECUTE</SAP:Code>
<SAP:P1>com/sap/xi/tf/_MM_ ffjms_</SAP:P1>
<SAP:P2>com.sap.aii.mappingtool.tf7.IllegalInstanceExcepti</SAP:P2>
<SAP:P3>on: Cannot create target element /ns0:MT_jms_ _a</SAP:P3>
<SAP:P4>sync_out/Data/Message/ GLUpdate. Values missi~</SAP:P4>
<SAP:AdditionalText />
<SAP:Stack>Runtime exception occurred during application mapping com/sap/xi/tf/_MM_ ffjms_; com.sap.aii.mappingtool.tf7.IllegalInstanceException: Cannot create target element /ns0:MT_jms_ asyncout/Data/Message/ GLUpdate. Values missi~</SAP:Stack>
<SAP:Retry>M</SAP:Retry>
</SAP:Error>
i want to know i mapped to UDF to GL_Update is is correct, to which element i have to map.
i think there is no prob with UDF,its executing ,giving warning messages
help me on this,
Regaards
Raj

JMS Adapter - Set Additional JMS Parameters or Replace Default Settings

Hi colleagues,
We are using PI/XI 7.0 (SP 12).
In trying to set up a Communication Channel using JMS Adapter to connect to Oracle AQ, I do not see the checkbox "Set Additional JMS Parameters or Replace Default Settings" , nor is the table for the parameters / value visible.
We have deployed the driver file as described in the How-to- guide: How To Install and Configure External Drivers for JDBC & JMS Adapters
[http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/f04ce027-934d-2a10-5a8f-fa0b1ed4d88f?quicklink=index&overridelayout=true]
In setting up the Communication Channel so far:
Type: Sender
Transport Protocol: Access JMS Provider Generically
Message Protocol: JMS 1.x
Adapter Engine:      Integration Server
After this I expect to see the checkbox "Set Additional JMS Parameters or Replace Default Settings", but it is not there.
Therefore I am not able to select it in order to enter parameters like:
JMS.QueueConnectionFactoryImpl.classname
JMS.QueueConnectionFactoryImpl.method.setHostName
JMS.QueueImpl.classname
JMS.QueueImpl.constructor.... etc
Can someone please share if this because we are on too low SP or do we need to do something additional before it becomes visible? Is this a feature that only became available as of PI/XI 7.0 SP 13 or 14 ?
I checked both Sender and Receiver channel type, and it does not appear for both.
Thanks & Cheers,
Jodie

Hi experts,
We are using PI 7.1 and I've set up a communication Channel using JMS Adapter to send
messages to a Sonic MQ queue.
I need to send some values as JMS parameters, two of which are constants and two are values
from the Sender message. I tried defining and setting up the parameters with constants values
in the Communication Channel under the Advanced tab by selecting the check-box
set Adapter-specific Message Attributes as follows:
Name     TYPE
ContentType     String
ReturnValue     boolean
Name     VAlue
Contenttype     CompanyCode
ReturnValute     true
This however lead to an error in the Adapter Engine (RWB).
My problem is:
1. Can anyone please instruct me as to how to go about defining and setting up
   additional JMS parameters?
2. How to go about defining/setting up variables that will get their values from
   the sender message?
Thanks & Cheers,
Joe

Problem with JMS Adapter after upgrade to 7.1

Hi All,
After an upgrade the JMS adapter connecting IBM Websphere MQ gives the following error:
Error connecting due to missing class: com.ibm.mq.jms.MQQueueConnectionFactory. Ensure that all resources required are present in the JMS provider library: aii_af_jmsproviderlib.sda
Since we are now on PI 7.1, the directory the JMS adapter should be looking for the libraries should be com.sap.aii.adapter.lib.sda. Has anyone else come across this problem after an upgrade? Should we remove the old aii_af_jmsproviderlib.sda?
Edited by: Luqman on Oct 31, 2008 5:39 PM

does following JAR files in place in aii_af_jmsproviderlib.sda.
●      com.ibm.mq.jar
●      com.ibm.mqbind.jar
●      com.ibm.mqjms.jar
●      connector.jar (use the JAR file from the J2EE client directory)
can u check n confirm.
i hopw u have followed the proper deployement process.
chirag

PI 7.1 JMS Adapter Correlation ID problem

Hi,
I try to get rid of the Correlation ID generated by the JMS Adapter (receiver).
In the adapter configuration, processing tab, I choose Set Correlation ID To: NO VALUE.
But still, in the message's details I can see a Correlation ID like this:
62656263343530362D633765652D346435652D323166392D
Any idea how to force a NO VALUE or a specific value? (hardcoded)
Thanks,
Martin

Hi,
I try to get rid of the Correlation ID generated by the JMS Adapter (receiver).
In the adapter configuration, processing tab, I choose Set Correlation ID To: NO VALUE.
But still, in the message's details I can see a Correlation ID like this:
62656263343530362D633765652D346435652D323166392D
Any idea how to force a NO VALUE or a specific value? (hardcoded)
Thanks,
Martin

Problem in JMS-Adapter with CharacterSet Websphere MQ

Hi,
we have the following scenario:
JMS -> PI -> File
We have a local Websphere MQ Queue Manager and the follwoing configuration in our sender adapter:
Transport-Protocol: WebSphere MQ (non JMS)
Message-Protocol: JMS 1.x
ConnectionFactory: com.ibm.mq.jms.MQQueueConnectionFactory
Java-class Queue: com.ibm.mq.jms.MQQueue
CCSID: 819
Transport: TCP/IP
JMS-conform: WebSphere MQ (non JMS)
In the local queue manager the messages (XML-Messages with header <?xml version="1.0" encoding="ISO-8859-1"?>) have characterSet 819 (ISO-8859-1). That's correct. You can open the files with XMLSpy and it works.
When we receive the messages by our JMS Sender Adapter all the character seems to be in UTF-8 and I don't know why. All the special characters are wrong cause the header of the XML-message shows ISO-8859-1 but all the signs are decoded in UTF-8.
In the other direction (JMS Receiver adapter, File -> PI - JMS) we have the same problem.
We create a ISO-8859-1 message in mapping (and it is really ISO-8859-1) and send it via JMS Receiver Adapter to the local message queue. But there the message arrives in UTF-8 encoding. I don't understand this.
Does anybody know what could be the cause for this?
Does the JMS adapter convert the messages from ISO-8859-1 into UTF-8?
Are there any parameters we have to set?
I hope anybody has an idea what's wrong.
Regards
Thorsten
Edited by: Thorsten Hautz on Oct 12, 2010 5:42 PM

Hi,
thanks a lot for your replies.
our driver settings are correct (as I can see).
I removed value 819 from CCSID, but we have the same effect.
The messages in the local queue manager are TextMessages in XML.
Does anybody know, if we need the standard modules (ConvertJMSMessageToBinary and ConvertBinaryToXMBMessage) in this case?
Is it possible to set the CCSID for the message payload anywhere in the configuration?
The CCSID in the Source tab doesn't have any influence to the encoding of the payload message, only to the header data.
Regards
Thorsten

Problem setting a provider specific property : JMS adapter

Similar Messages

Maybe you are looking for