Restrict message volume through JMS adapter (not individual message size)

Hi, does anyone know of a way to restrict the flow of messages through a JMS adapter? For example, If I wanted to only allow up to 1000 messages to be sent in an hour to a particular system. The rest should just be queued in the Adapter Engine until the next hour begins in order to smooth out the load on the recieving system.
I know this is poor design but there is a system that is getting overwhelmed and cannot be easily changed right away. I'd like a way to control this from the middleware using standard PI (no ccBPM).
Any ideas?
Thanks in advance,
Aaron

Stefan, thank you for the idea, that is a good one.
I'm going to assume there is nothing specific we can do in the SAP JMS adapter to control the flow, and look to a solution in the queueing software like you suggested or the 3rd party application.
-Aaron

Similar Messages

Jms adapter not polling messages from jms topic

Hi
We have a jms adapter configured in BPEL process which need to poll messages from JMS topic.Unfortunately its not polling message from JMS Topic if we add Message Selector and Durable Subscriber properties in jca file.Please find jca file content below
<adapter-config name="SyncCustomerPartyListCDHJMSConsumer" adapter="JMS Adapter" wsdlLocation="oramds:/apps/AIAMetaData/AIAComponents/ApplicationConnectorServiceLibrary/CDH/V1/ProviderABCS/SyncCustomerPartyListCDHProvABCSImpl.wsdl" xmlns="http://platform.integration.oracle/blocks/adapter/fw/metadata">
<connection-factory location="eis/jms/aia/syncCustomerParty_cf" UIJmsProvider="WLSJMS" UIConnectionName="Dev"/>
<endpoint-activation portType="Consume_Message_ptt" operation="Consume_Message">
    <activation-spec className="oracle.tip.adapter.jms.inbound.JmsConsumeActivationSpec">
      
      <property name="PayloadType" value="TextMessage"/>
      
      <property name="UseMessageListener" value="true"/>
      <property name="DestinationName" value="jms/aia/Topic.jms.COMMON.CustomerParty.PUBLISH"/>
    </activation-spec>
</endpoint-activation>
</adapter-config>
If we remove Durable subscriber and message selector properties,its able to poll messages.
Any pointer will help
thanks in advance
Baji

After changing below property in jca file.JMS adapter is able to poll messages from JMS Topic.
<property name="UseMessageListener" value="false"/>
But if i un comment below line and deploy my code again, it stop pulling the messages from topic.
<property name="DurableSubscriber" value="XYZ"/>
If i bounce the server after above change and deployment ,it will start polling the message.I am not sure why i need to restart my server after adding above property.
Thanks
Baji

Is there a way in which you can deliver messages only through iMessages and not text messages . If the other iphone user has switched off the data services then the message gets delivered when the user switches on the data services.

I want messages to be delivered to the other person only through iMessages . Is there a way to disable text messages being sent to the other iphone .

In message settings, disable the send as SMS setting. That does mean any message sent to a non-iMessage enabled device will just not get sent.

JMS Adapter Supports below message

Hi Frnds,
I am working on one scenario i have to read and write RFH2 Message from MQ,we decided to use jms adapter.
JMS Adapter supports below Message to put in MQ,
<Data>
     <MQRFH2>
          <usr>
               <TransactionType>GL_Update</TransactionType>
               <Environment>LIVE</Environment>
               <SourceScheme>EANCM</SourceScheme>
               <SourceApplicationId>5051150003606</SourceApplicationId>
               <DestScheme>EANCM</DestScheme>
               <DestinationRouting>5051150003330</DestinationRouting>
               <OriginalRouting/>
               <MessageRecordCount>1</MessageRecordCount>
               <BusinessTransactionId>20090405193001</BusinessTransactionId>
               <ParentBusTID/>
               <ParentBusId/>
               <EECode>Y</EECode>
          </usr>
          <mcd>
               <Msd>xml</Msd>
          </mcd>
     </MQRFH2>
     <Message>
          <GL_Update>
               <header>
                    <SourceEAN>5051150003606</SourceEAN>
                    <DestinationEAN>5051150003330</DestinationEAN>
               </header>
               <detail>
                    <AuthorisedUser/>
                    <HeaderText/>
                    <HeaderReference/>
                    <PostingItem>
                         <ProfitCentre>7027101000</ProfitCentre>
                         <CostCentre/>
                         <AccountCode>0001413150</AccountCode>
                         <GlobalBusinessIdentifier>AU10</GlobalBusinessIdentifier>
                         <MonetaryAmount>0000000100.00</MonetaryAmount>
                         <GlobalCurrencyCode>AUD</GlobalCurrencyCode>
                         <RunDate>20080725</RunDate>
                         <Description>IV006270M000000000000000000001</Description>
                         <WorkBreakdownStructureElement/>
                         <BudgetRequest/>
                         <TransactionType/>
                         <TransactionNumber/>
                         <PostingKey>50</PostingKey>
                         <SalesTax>
                              <SalesTaxCode/>
                              <SalesTaxAmount/>
                         </SalesTax>
                         <PersonnelNumber/>
                         <Assignment/>
                         <CalculateTaxBase/>
                         <BaselineDate/>
                         <PaymentTerms/>
                         <MedicalReference/>
                    </PostingItem>
                    <PostingItem>
                         <ProfitCentre/>
                         <CostCentre/>
                         <SalesTax>
                              <SalesTaxCode>P3</SalesTaxCode>
                         </SalesTax>
                    </PostingItem>
                    <PostingItem>
                         <ProfitCentre>7022001001</ProfitCentre>
                         <CostCentre/>
                         <AccountCode>0001701001</AccountCode>
                    </PostingItem>
               </detail>
               <trailer>
                    <thisDocumentGenerationDateTime>20090405T072928Z</thisDocumentGenerationDateTime>
                    <thisDocumentIdentifier>20090405T072928Z</thisDocumentIdentifier>
               </trailer>
          </GL_Update>
     </Message>
</Data>
please help me on this
it possible to achieve using JMS adapter or not?? what is the alternative solution ??
Regards,
raj

Hi RSR,
JMS is the better way to connect sonic MQ.below iam attaching you few points while using JMS.
1.for the JMS adapter an external driver is needed (java archive)
2.this archive is provided by the respective provider of the queuing system
3.the driver has to be deployed via SDM , see XI configuration guide for details
4.Routing rules and sender has to be specified as for any other channel in the directory
    object model
5.the message header information is determined from the appropriate sender
   agreement for the communication channel
6.the communication channel defined must be used in exactly one sender agreement
7.at least the interface name and the sender service must be qualified in the
    sender agreement ,other fields are optional
Depending on the transport protocol selected, specify the following :
8.For Sonic MQ JMS Provider :
·        Java class QueueConnectionFactory
·        Java class queue
·        IP address or server name
·        Server port
·        JMS queue
9.JNDI JMS Provider Lookup
·        JNDI name of QueueConnectionFactory
·        JNDI name of JMS queue
·        Name of JNDI Initial Context Factory
·        Address of JNDI server
·        JNDI users
·        JNDI password with confirmation
10.
For WebSphereMQ (MQ Series) JMS Provider
·        Java class QueueConnectionFactory
·        Java class queue
·        IP address or server name
·        Queue manager name
·        Channel name
·        JMS queue
·        Character set for non-ASCll names
·        Transport/network protocol
·        Target client
11.
JMS Provider Administered Objects via File
   File name of serialized object QueueConnectionFactory
   File name of serialized object Queue
With Rgds,
MF.Haq

MDB,MDB container or JMS adapter stops processing messages from JMS queue

Hi guys,
we have created a component using Enterprise Java Beans, let's say a product catalog, deployed it on a Glassfish v2 instance, and connected it to a legacy system using JMS and Sun MQ v4.1 as messaging system. The catalog component thus starts one MDB that listens on a JMS queue, let's say a queue named catalog_business_events_in, and waits for incoming messages, i.e. in our case update events. The problem is, that in general this approach works well, but sometimes the MDBs/JMS adapter stops for some reason fetching and processing messages from the JMS queue. We don't know why - no exceptions, etc.. Seems to be a Glassfish EJB container, JMS adapter or Sun MQ configuration issue. It seems to be that our component is not the problem.
The messages are compressed/uncompressed by Sun MQ automatically. We actually have 2 Sun MQ instances in clustered mode running to have some kind of failover - no HA cluster, yet. Sun MQ instances are accessed from Glassfish instances running in different Glassfish clusters - so we have a dedicated Sun MQ cluster not a Sun MQ instance per Glassfish instance. Each Glassfish instance is configured such that it knows both Sun MQ instances to allow automatic failover.
Has someone an idea, why the MDBs/ MDB container/ JMS adapter - stops processing messages? We are kind of puzzled as it happens more often now and apparently when traffic is (very) low not high!
Thanks for your help.
Cheers,
Martin
Edited by: east1979 on Jan 13, 2009 8:06 AM

Hi Manoj,
I have a very similar if not identical issue,
Error while running realtime jobs that read from JMS tables via JMS MQ adapter:
15/11/12 09:10:08 JMS GET OPERATION ERROR : TIMEOUT.UNABLE TO RECEIVE RESPONSE FROM THE INVOKED DATA SERVICES SERVICE.ADAPTER OPERA
TION TO CONTINUE.
15/11/12 09:10:15 Communication Error. See real time job log for details.
Dump available:
https://sapmats.wdf.sap.corp/download/download.cgi?id=5C0KZAHA3RSXBJW3ABLMUUT2P5UUKWO2TM3EJDM5W2HGDZUDID
Version of DS:14.0.3.273
Any comments?
Thansk and kind Regards,
Kenneth

How to hanlde breaked large messages in sender JMS adapter

Hi,
I have been asked like 'how can we handle breaked large messages in sender JMS adapter?'and lets say I am getting some messages as it is and some are breaked into small segements for the mesaages that are large....
do we need to use module,if so is there any standard module that we can use to hanlde this type of scenarios?
thank you in advance.
babu

http://biemond.blogspot.com/2009/10/jms-request-reply-interaction-pattern.html
if you check the blog of edwin, see his comments at the bottom
there he gives a suggestion how to add the selector properties to filter on
and this one is maybe helpfull
http://blogs.oracle.com/adapters/2010/05/configuring_request-reply_in_jmsadapter.html

JMS Adapter not appearing in Adapter Monitor, How to Fix ?

JMS Adapter not appearing in Adapter Monitor screen when choosing "Only Installed and Started Adapters" option. What need to do to install and start the JMS adapter.
Thanks in advance

Hi,
Only JMS adapter is not seen in the adapter monitor or other adapters are not listed in the same.
Have you checked whether the JMS drivers are installed on XI or not?
First would be to deploy drivers for JMS scenarios - https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
Thnx
Chirag

Message flow between advanced adapter engine and messaging system for ICO scenarios

Dear all,
I'm working on a PI 7.31 AEX box and created an ICO object for one interface with HTTP_AAE2IDoc scenario. The interface works quite well. When I looked in to message log of messages for this interface in PI monitor, I noticed that the internal XI message are put totally 5 times into the send queue and retrieved from send queue. In some steps I only see after retrieving a message from send queue and immediately put it back into send queue. Can someone please kindly explain the message flow between advanced adapter engine and messaging system and what exactly happens after each retrieving a message from send queue?
Below is an example of message log for one message:
12/08/2014 09:26:06.472    Information    MP: processing local module localejbs/CallSapAdapter
12/08/2014 09:26:06.472    Information    Application attempting to send an XI message asynchronously using connection HTTP_AAE_http://sap.com/xi/XI/System
12/08/2014 09:26:06.478    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.499    Information    Message successfully put into the queue
12/08/2014 09:26:06.499    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.499    Information    The application sent the message asynchronously using connection HTTP_AAE_http://sap.com/xi/XI/System. Returning to application
12/08/2014 09:26:06.500    Information    HTTP adapter successfully processed interface PlantResponse_Out
12/08/2014 09:26:06.501    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.501    Information    Message status set to DLNG
12/08/2014 09:26:06.513    Information    Message successfully put into the queue
12/08/2014 09:26:06.513    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.515    Information    Message status set to DLNG
12/08/2014 09:26:06.533    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.548    Information    Message successfully put into the queue
12/08/2014 09:26:06.548    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.550    Information    Message status set to DLNG
12/08/2014 09:26:06.551    Information    Executing Request Mapping "http://styrolution.com/pi/Integration/PlantMaintenance/PlantResponse/PlantResponse_to_Zcol_Basf_Inotif02_Inotif01_Zeupm_Inotif01_Ludwigshafen" (SWCV 085d2320fb3b11e2cc0bf4d50aea8c33)
12/08/2014 09:26:06.563    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.571    Information    Message successfully put into the queue
12/08/2014 09:26:06.571    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.573    Information    Trying to put the message into the send queue
12/08/2014 09:26:06.573    Information    Message status set to DLNG
12/08/2014 09:26:06.580    Information    Message successfully put into the queue
12/08/2014 09:26:06.580    Information    The message was successfully retrieved from the send queue
12/08/2014 09:26:06.582    Information    Message status set to DLNG
12/08/2014 09:26:06.583    Information    Delivering to channel: IDOC_R
12/08/2014 09:26:06.583    Information    MP: processing local module localejbs/IDocOutboundModuleBean
12/08/2014 09:26:06.583    Information    XI message received for processing
12/08/2014 09:26:06.587    Information    Sender Party: Sender Service:SXX Receiver Party: Receiver Service:RXXCLNT200 Communication Channel:IDOC_R
12/08/2014 09:26:06.588    Information    IDOC metadata repository is RXX
12/08/2014 09:26:06.589    Information    Control record is not mandatory - control record will be added if not available
12/08/2014 09:26:06.590    Information    XML Payload parsed to idoc document list with number of idocs: 1
12/08/2014 09:26:06.595    Information    Sending idoc message to receiver R/3 system with TID XIh{lsRI824UITC0009OalmW
12/08/2014 09:26:06.813    Information    IDOC message sent to receiver R/3 system
12/08/2014 09:26:06.817    Information    TID XIh{lsRI824UITC0009OalmW confirmed
12/08/2014 09:26:06.819    Information    Message was successfully transmitted to endpoint <local> using connection HTTP_AAE_http://sap.com/xi/XI/System
12/08/2014 09:26:06.821    Information    Message status set to DLVD
Thanks & regards
Dingjun

Hello All,
Thanks for the prompt responses and with best information, But apart from this,I need how an adapter(File/JDBC) works along
with AAE in PI 7.1. When does the job of File/JDBC adapter is completed and resumed in a synchronous case. That is,
File Location --> file adapter -
> XI(AAE) --> JDBC adapter --> database.
In file sender, lets suppose we have synchronous settings(Best Effort). Now when File adapter's job is finished and when it
gets back the response back from XI. Please explain step by step from starting(file adapter polling the location) to getting the response coming back to XI.
Regards,
Achari.

Sending Msg From HTTP client to XI through JMS Adapter using WebSphereMQ

Hello
I am trying to send some msg from Http client
I configured JMS adapter as receiver
Transport Protocol :WEBsphereMQ JMS provider
Message protocol :JMS1.x
I have given the Ip address of my machine where I installed WEB Sphere MQ
Server Port :1416
Transport Protocol :WebSphere MQ
JMS compliant: JMS-compliant
In SXMB_MONI
Http client sends message without any error.
But while tracing I got message
<Trace level="1" type="T">Async barrier reached. Bye-bye !</Trace>
Can anybody tell me the solution..
Thnaks

Hi,
I have not directly faced this but i may suggest ,
1. What do you see in sxmb_moni, do you have a queue problem?
2. see this File-to-File Scenario Stopped Working the reply from Shravan and the last message.
<i>The XBTO que was the problem. I deleted all LUWs in it and now new transactions are working again</i>
3. You may also use this /people/sap.user72/blog/2005/11/29/xi-how-to-re-process-failed-xi-messages-automatically
Regards,
Anirban.

JMS adapter not picking the file

Hello,
I am working jms to jms scenario on PI7.0 Service Pack13. file is not able to pick up sendar JMS Channel. I am using WebSphereMQ Transport Protocol. JMS drivers are installed.
I checked all parameters of JMS Adapter. no mistake in parameters. What is the problem. Please suggest as soon as possible.
Thanks

Hi,
Whether the Driver file has been mentioned in Provider XML file and check the messages are in the right sender Queue.
Check the Port and Protocol are right one.
Regards
Agasthuri Doss

Distributed topic - JMS adapter consuming duplicate messages

We have distributed topic thats consumed by a composite (JMSadpter in mediator).
We see for every one message sent the composite consumes the message twice. (With forwarding policy set to partitioned)
Is this an expected behavior? and how do we make the consumer (JMS adapter) consume only once per message
Thanks
Vijay

From the documentation (provided here: http://download.oracle.com/docs/cd/E21764_01/integration.1111/e10231/adptr_jms.htm)
The JMS API specifies three types of acknowledgments that can be sent by the JMS publisher:
- DUPS_OK_ACKNOWLEDGE, for consumers that are not concerned about duplicate messages
- AUTO_ACKNOWLEDGE, in which the session automatically acknowledges the receipt of a message
- CLIENT_ACKNOWLEDGE, in which the client acknowledges the message by calling the message's acknowledge method
Could you check in the weblogic-ra.xml what acknowledge mode has been configured:
<property>
<name>AcknowledgeMode</name>
<value>AUTO_ACKNOWLEDGE</value>
</property>
...Note that when DUPS_OK_ACKNOWLEDGE is used it can happen that a message is consumed more than once.
Are you also sure that the message is not produced twice?
Seminar on Cloud Computing - http://middlewaremagic.com/weblogic/?p=7387

Sender JMS Adapter - NOT Working

Hello Everybody - We are on SP13, also installed JMS Driver files on the system. We are running, Central Adapter Engine.
We configured the Sender JMS Adapter for WBI MQ->XI->SAP scenario. We need to JMS Adapter to be configured to connect to WBI from XI. Everything looks great in configuration but in the Adpater Monitoring, JMS Adapter is with Error Status and Message says "Sender channel. Details: (No detail information set.)".
Does anybody has any idea about this error ?
I checked SAP Help link as well on this. Based on this link http://help.sap.com/saphelp_nw04/helpdata/en/ca/e7673c86d19b35e10000000a11402f/frameset.htm. Do we need to configure this JMS Adapter somewhere on teh server as well ? If yes, then where ? Pls respond if you have any clue about it.
Thanks in anticipation...

Hello Stefan - Thanks for response.
Here are the Parameters.......
Adapter Type: JMS
Sender Type Clicked
Transport protocol:WebSphereMQ (non-JMS)
Message protocol:JMS 1.x
Adapter Engine:Integration Server
Queue ConnectionFactory Java Class:com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class:com.ibm.mq.jms.MQQueue
IP Address or Server Name:10.9.48.154
Server Port:1414
Queue Manager Name:WBIDEV
Channel Name:WBI.XI.SVRCONN
JMS Queue:XI_REQUEST
Transport/Network Protocol:TCP/IP
JMS-Compliant:JMS-Compliant
Transactional JMS Session:Check box Set
JMS Queue User:XIUSER
JMS Queue Password:********
Set XI message ID(MessageID) to:GUID(recommended value)
Set XI cenversation ID(conversationID) to:No value
Mapping of Message:Message Payload=JMS Payload
Quality of Service:Exactly Once
Time Period for duplicate check for EO(IO)(secs):86400
Wait After Message Error(msecs):1000
Wait before Reconnect(msecs):1000
Status:Active
The Error Message I see in the Adapter Monitor is "Sender Channel. Details: (No detail information set.)
Pls advice If I am missing anything ?
Thanks....
Amrish.

Message Conversion in JMS adapter

Hello Friends,
I have a scenario where in I will be getting the message from MQ, and the message will look like
<b>SOURCE</b>
<Root><MessageHeader><MessageID><MessageIDSystem>SCV</MessageIDSystem><MessageIDType>FE</MessageIDType><MessageIDIdentifier>CUSTOMER_MASTER</MessageIDIdentifier></MessageID><MessageReleaseNo>0004</MessageReleaseNo><MessageVersionNo>00</MessageVersionNo><MessageOrigApplID>SCV</MessageOrigApplID><MessageDestApplID>BROKER</MessageDestApplID><MessageInterfaceID>IDD088</MessageInterfaceID></MessageHeader><MessageBody><SCVData>53435646453030340130303030303401323030372d31312d31362031393a34303a343401313336333938323401330130010154414730303101574542555345525f52454c4154494f4e0155504441544501323030372d31312d31362031393a34303a343301544147303138013836373134013332353030303039343239013332353030303035323338013332353030303035323339010131014e014e01494e41435449564501350154414730303101504552534f4e01494e414354495641544501323030372d31312d31362031393a34303a343401544147303032013332353030303039343239015941553b56414e4553534101333235013301494e41435449564501323030352d30342d30332031383a34363a3136015343563234324d4947524154494f4e01323030372d31312d31362031393a34303a3433014a43473031370133515955493630554b36355136015041015441473031390131013332353030303039343239015041303030303934323901013101544147303033015941550156414e455353410156590101014601013530372d34333032383838013530372d363736383332380149544350545940435750414e414d412e4e4554013201013530372d343330323839310101544147303031014c494e4b01494e414354495641544501323030372d31312d31362031393a34303a3434015441473030360130303432013332353030303035323338013332353030303039343239015343563234324d4947524154494f4e013530372d34333032383838013530372d343330323839310101323030352d30342d30332031383a34363a313601393939392d31322d33312030303a30303a3030015343563234324d4947524154494f4e01494e41435449564501323030372d31312d31362031393a34303a3433014a43473031370149544350545940435750414e414d412e4e4554013530372d343330323839310154414730313901320133323530303030353233380150413b494e5445524558503b48454144510101320154414730313901310133323530303030353233380150413030303035323338010131015441473031390134013332353030303035323338013832373032313030010134015441473031390131013332353030303039343239015041303030303934323901013101</SCVData></MessageBody></Root>
and the ascii data in this message needs to be converted into XML format.
JMS Adapter is picking this message from MQ and posting it to XI.
Also there is an adapter module develped for this conversion and it is working fine for most of the messages, but it failing for this above message.
Can you please help me out in this issue and how to test that adapter module.
Thanks & Regards,
Kumar

hi kumar,
>>Can you please help me out in this issue and how to test that adapter module.
put brek points in ur adapter module and then run ur scenario and debug. this is how u test ur adapter module.
this will also help u to see why is it running for certain msgs n failin for others. at different steps/points check the value for variables etc while debugging.
Also put some statements to write audit log entries in ur code for module. this will also help in debugging.
[reward if helpful]
regards,
latika.

JMS adapter not registered

We are integrating Weblogic JMS with SAP using JMS adapter in XI and in communication Channel we are getting message as "JMS_SENDER - n/a - No adapter registered for this channel " , How to register the JMS adapter ??

Sorry,
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/70ffd890-0201-0010-708f-d5dad2dfcf3a
or try it other:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/a05b2347-01e7-2910-ceac-c45577e574e0
Edited by: Carlos Ivan Prieto Rubio on Dec 17, 2007 5:17 PM

JMS Adapter not picking file in PI7.0

Hello,
I am working jms to jms scenario on PI7.0 Service Pack13. file is not able to pick up sendar JMS Channel. I am using WebSphereMQ Transport Protocol. JMS drivers are installed. ports and protocals are correct.
I checked all parameters of JMS Adapter. no mistake in parameters. What is the problem. Please suggest as soon as possible.
Thanks
venkat

Hi San ,
Please checke the status of JMS communication channel. In Runtime work bench , U will get the adapter monitoring there if any activity happens it shows the event details .
I hope picking the file is initial event so you can get some idea with those event log for Communication channel .
Cheers,
Reddy

Restrict message volume through JMS adapter (not individual message size)

Similar Messages

Maybe you are looking for