JMS - MQ Series

Hello,
we try to set up a receiving JMS adapter to connect to MQ series, but so far we are unsuccessful. In the dapter framework monitor we get a "MQJMS2008: failed to open MQ queue" error message. In the RWB not much useful information exists. Our Configuration is as follows:
QueueConnection Java Class com.ibm.mq.jms.MQQueueConnectionFactory
Queue Java Class   com.ibm.mq.jms.MQQueue
Queue Manager Name QM00191
Channel Name       CQM00191.CLSAPCM
JMS Queue          AQG.CREDITINFO.SOPIC.R3.3530
JMS Compliant      WebSphereMQ (non-JMS)
The IBM JMS JAR files are deplyed according to the SAP How To guide.
Any suggestions on how to proceed?
Kind regards Johan

Hi Johan,
could you explain the different between the WebSphereMQ (not JMS) and JMS-konform. Why and when should use which mode?
When you configure the JMS-Adapter which how to guide do you mean? Where to find it?
Thanks,
Ly-Na Phu

Similar Messages

JMS-MQ Series error( MQJMS2002)

Hi,
I have an MDB listening to a queue. I am using MQ Series instead of Jboss mq. It has been working fine but I have faced the below error a fews days back and i am unable to solve it.
For a particular message , I get an error javax.jms.JMSException: MQJMS2002: failed to get message from MQ queue , when I remove it from the queue , it works fine i.e the messages starts being processed by the MDB. But if i again place the message back in the queue the same error keeps appearing again and again in the log and no further messages gets proceesed by the MDB.
In our application the length of the message is more than 4mb so we have modified all the queues to 10mb in mqseries and it has been working fine from a long time. But for this particular message the above situation is occuring. Note size of dead letter queue is still 4mb.
Can the below be happening:-
For some reason the queue manager cannot deliver a message and so it attempts to put the message on its dead-letter queue , but since the DLQ max size is 4mb , it goes into a loop.....may not sound very convincing thought...........but if i change the size of DLQ to 10mb ...will it help my cause.....below is the full stack trace ..........
44526 2007-07-25 09:16:24,162 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected:
44527 javax.jms.JMSException: MQJMS2002: failed to get message from MQ queue
44528 at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:567)
44529 at com.ibm.mq.jms.MQSession.consume(MQSession.java:3113)
44530 at com.ibm.mq.jms.MQSession.run(MQSession.java:1612)
44531 at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:182)
44532 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:748)
44533 at java.lang.Thread.run(Thread.java:534)
44534 2007-07-25 09:16:24,162 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] innerStop
44535 2007-07-25 09:16:24,162 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] unset exception listener
44536 2007-07-25 09:16:29,138 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] connection stopped
44537 2007-07-25 09:16:29,138 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] destroyService
44538 2007-07-25 09:16:29,162 DEBUG [org.jboss.jms.asf.StdServerSessionPool] Clearing 1 from ServerSessionPool
44539 2007-07-25 09:16:29,163 DEBUG [org.jboss.jms.asf.StdServerSession] closed
44540 2007-07-25 09:16:29,164 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Stopping DLQHandler
44541 2007-07-25 09:16:29,164 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Stopped DLQHandler
44542 2007-07-25 09:16:29,164 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Destroying DLQHandler
44543 2007-07-25 09:16:29,166 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Destroyed DLQHandler
44544 2007-07-25 09:16:29,166 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Waiting for reconnect internal 10000 ms
44545 2007-07-25 09:16:39,164 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Trying to reconnect to JMS provider
44546 2007-07-25 09:16:39,164 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Initializing
44547 2007-07-25 09:16:39,164 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Looking up provider adapter: java:/WSMQ JMSProvider
44548 2007-07-25 09:16:39,164 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Provider adapter: org.jboss.jms.jndi.JN DIProviderAdapter@15e0638
44549 2007-07-25 09:16:39,165 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Creating DLQHandler
44550 2007-07-25 09:16:39,165 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using factory: com.ibm.mq.jms.MQQueueConnectionF actory@895ab1c7
44551 2007-07-25 09:16:39,187 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created connection: com.ibm.mq.jms.MQQueueConnec tion@bd7301
44552 2007-07-25 09:16:39,187 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Using Queue: queue://OMNT031P/SYSTEM.DEAD.LETTER .QUEUE
44553 2007-07-25 09:16:39,187 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Created DLQHandler
44554 2007-07-25 09:16:39,187 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] context: javax.naming.InitialContext@1c 95c92
44555 2007-07-25 09:16:39,187 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] jndiSuffix: ossToNpgQueue
44556 2007-07-25 09:16:39,187 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Got destination type Queue for OssJmsMd bOm
44557 2007-07-25 09:16:39,187 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using connection factory: com.ibm.mq.jms.MQQueu eConnectionFactory@895ab1c7
44558 2007-07-25 09:16:39,188 DEBUG [org.jboss.jms.ConnectionFactoryHelper] using username/password: null/null
44559 2007-07-25 09:16:39,190 DEBUG [org.jboss.jms.ConnectionFactoryHelper] created QueueConnection: com.ibm.mq.jms.MQQueue Connection@dcb4bb
44560 2007-07-25 09:16:39,190 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Using client id: null
44561 2007-07-25 09:16:39,190 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Could not find the queue destination-jn di-name=ossToNpgQueue
44562 2007-07-25 09:16:39,190 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] looking up session pool factory: java:/ StdJMSPool
44563 2007-07-25 09:16:39,190 DEBUG [org.jboss.jms.asf.StdServerSessionPool] initializing with connection: com.ibm.mq.jms.M QQueueConnection@dcb4bb
44564 2007-07-25 09:16:39,191 WARN [org.jboss.jms.asf.StdServerSessionPool] Using a non-XA QueueConnection. It will not b e able to participate in a Global UOW
44565 2007-07-25 09:16:39,191 DEBUG [org.jboss.jms.asf.StdServerSession] initializing (pool, session, xaSession, useLocalTX ): org.jboss.jms.asf.StdServerSessionPool@1dd92ab, com.ibm.mq.jms.MQQueueSession@1c8363b, null, false
44566 2007-07-25 09:16:39,191 DEBUG [org.jboss.jms.asf.StdServerSessionPool] added server session to the pool: org.jboss.jm s.asf.StdServerSession@1605c66
44567 2007-07-25 09:16:39,191 DEBUG [org.jboss.jms.asf.StdServerSessionPool] Server Session pool set up
44568 2007-07-25 09:16:39,191 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Server session pool: org.jboss.jms.asf. StdServerSessionPool@1dd92ab
44569 2007-07-25 09:16:39,195 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Connection consumer: com.ibm.mq.jms.MQC onnectionConsumer@1526ddf
44570 2007-07-25 09:16:39,195 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Initialized with config org.jboss.ejb.p lugins.jms.JMSContainerInvoker@9ba786{ maxMessagesNr=1, maxPoolSize=1, reconnectInterval=10000, providerAdapterJNDI=j ava:/WSMQJMSProvider, serverSessionPoolFactoryJNDI=java:/StdJMSPool, acknowledgeMode=1, isContainerManagedTx=false, i sNotSupportedTx=false, useDLQ=true, dlqHandler=org.jboss.ejb.plugins.jms.DLQHandler@ab5354{ destinationJNDI=queue/WSM Q/DLQ, maxResent=1, timeToLive=0 }, destinationJNDI=ossToNpgQueue }
44571 2007-07-25 09:16:39,195 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Starting DLQHandler
44572 2007-07-25 09:16:39,195 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Started DLQHandler
44573 2007-07-25 09:16:39,196 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Reconnected to JMS provider
44574 2007-07-25 09:16:39,226 WARN [org.jboss.ejb.plugins.jms.JMSContainerInvoker] JMS provider failure detected:
44575 javax.jms.JMSException: MQJMS2002: failed to get message from MQ queue
44576 at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:567)
44577 at com.ibm.mq.jms.MQSession.consume(MQSession.java:3113)
44578 at com.ibm.mq.jms.MQSession.run(MQSession.java:1612)
44579 at org.jboss.jms.asf.StdServerSession.run(StdServerSession.java:182)
44580 at EDU.oswego.cs.dl.util.concurrent.PooledExecutor$Worker.run(PooledExecutor.java:743)
44581 at java.lang.Thread.run(Thread.java:534)
44582 2007-07-25 09:16:39,226 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] innerStop
44583 2007-07-25 09:16:39,226 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] unset exception listener
44584 2007-07-25 09:16:44,204 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] connection stopped
44585 2007-07-25 09:16:44,204 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] destroyService
44586 2007-07-25 09:16:44,204 DEBUG [org.jboss.jms.asf.StdServerSessionPool] Clearing 1 from ServerSessionPool
44587 2007-07-25 09:16:44,205 DEBUG [org.jboss.jms.asf.StdServerSession] closed
44588 2007-07-25 09:16:44,205 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Stopping DLQHandler
44589 2007-07-25 09:16:44,205 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Stopped DLQHandler
44590 2007-07-25 09:16:44,205 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Destroying DLQHandler
44591 2007-07-25 09:16:44,206 DEBUG [org.jboss.ejb.plugins.jms.DLQHandler] Destroyed DLQHandler
44592 2007-07-25 09:16:44,206 DEBUG [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Waiting for reconnect internal 10000 ms
44593 2007-07-25 09:16:54,211 INFO [org.jboss.ejb.plugins.jms.JMSContainerInvoker] Trying to reconnect to
Thanks

Hi,
This is with reference to your CV Posted in jobsite. Let me introduce myself Kranti, working with Techpoint Solutions! as IT Recruiter. We have job opening matching your profile.
Send your update Resume to
[email protected]
Note:
1. Check list below is mandatory, without the check list we cannot process your CV.
Full Name:
DOB:
Current CTC:
Exp CTC:
Notice Period:
Current Location:
Ready to relocate to Hyderabad :
Job Location : Hyderabad
Once your profile gets short-listed, you would be called for a face to face interview.
JOB SPECIFICATION �
Senior Developer/ Lead
Experience Required:
Total Years of Experience: 4+years experience in IT
At least 1 -2 years experience leading a team.
Education: Should be a BE/ B Tech/ ME/ M Tech/ ! MCA/ M Sc in IT/ Systems/ Computers.
- Consistent 60% academic record is a must.
- Candidates interviewed by us in the last 6 months are not eligible.
- Correspondence / Part time Courses does not qualify.
- Gaps in Education / Career should not be more than 2 yrs (If any).
- At least 50% of yo! ur Post Qualification experience should be relevant to IT or to the skill set that we are looking at.
Description
Develop web pages and backend programs
Technical Skills
Must haves:
Operating System worked on: Experience on Unix at least 3 years.
Scripting language: Worked on She ll and Perl scripts minimum 3 years.
Database exposure/Worked on : Experience on Sybase development. WebLogic Server or WebSphere. Java J2EE, JMS
MQ, VSS (should on Application side)
Actuate Reporting is a plus.
Domain: Investment Banking
Job! Location: Hyderabad
Thanks & Regards,
Kranti Punjala
Executive (Recruitments)
Techpoint Solutions.
[email protected]

Mdb w/ non jms mq series

Hi,
          I have several legacy java daemons that communicates with a vendor via MQ Java using MQSeries hosted at a vendor site. The daemons were poorly written and are always dying (that is when production support remembers to start them at all). :D
          I'd like to rewrite the application using MDBs. Is there any way to support this without requiring the vendor to change to MQSeries JMS (i.e. set up MQSeries JNDI, configure a Java Channel, etc)? I don't have any JMS transactional requirements. I just want to move to an in-server process.
          thanks,
          Laphroaig

If you had the time, you could write your own version of the javax.jms.* interfaces that wraps the MQ java APIs sufficient for MDB or bridge purposes, and then register instances of the CF and destination wrappers in WebLogic's JNDi via a startup class or load-on-start servlet. I've seen various customers use this approach for non-JMS (and even non-java) queueing systems, and personally, I think this is one of the most elegant, flexible, and maintainable solutions.
          Another alternative is to write your own version of a bridge. You might be able to use the "MQSeries JMS Support" code sample (meant for 6.x) as an example:
          http://dev2dev.bea.com/codelibrary/code/mqseries.jsp
          Tom

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

How to set message id for JMS

Hi All,
I set up the JMS connection with JBoss, and send the message asynchrously to JBoss successfully.
But right now, Jboss need to use the incoming message ID as correlation ID in Jboss.
How could i set the message id from payload (not PI message ID, not PI Conversation ID) for JMS receiver adapter?
thanks a lot
already check the following links:
https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/docs/library/uuid/5059f110-0d01-0010-7c8b-fdc983be70c0
Re: jms message id in jms sender channel
JMS Correlation ID
XI JMS mq series correlation id
cannot find any about set JMS Message ID from payload
Edited by: Lawrence on Dec 24, 2009 2:21 PM

Hi Lawrence,
I am not sure how jboss will store message,But i had done similar requirement but my system is MQ,Standard JMS adapter not supports to chnage the value or set mesage id in MQ,we can change the PI Message ID Value but not JBOSS/MQ Message ID.
Writng module is the one option.
Regards,
Raj

JMS adapter receiver - converion to text without any end-of-line character

Hi everybody,
We have the scenario
RFC -> PI7.11 -> JMS (MQ Series)
I want to convert the XML document of PI into a text format.
In destination MQSeries, we can't have any end-of-line separator because the destination of MQS target is a Mainframe .
How can we suppress this character End-of-line ?
Can anybody help me top solve this issue, please ?
Thank you for you help in advance.
Kind Regards
E. Koralewski

I solved my issue
I used the module AF_Modules\StrictXml2PlainBean
and I put the parameter field.endSeparator without any value.
Kind Regards

Sample scienario on JMS to JDBC/File

Hi,
Can any one send me the sample scenario on JMS to JDBC or FILE. Any suggestions for how to configure JMS with MQ will be helpful for me .
Thanking you with anticipation
Regards
Ramesh.

Hi Ramesh,
Go thru these links :
http://help.sap.com/saphelp_nw04/helpdata/en/ca/e7673c86d19b35e10000000a11402f/frameset.htm
http://help.sap.com/saphelp_nw04/helpdata/en/33/e6fb40f17af66fe10000000a1550b0/frameset.htm
And these threads
JMS and MQ Series (sender and receiver)
SAP XI and JMS for WebSphere MQ
JMS - MQ Series
Hope these will be helpful.
Regards
Suraj

RWB not working

Currently I 'm working in XI 3.0
My RWB is not working just after I deployed JMS MQ Series 7.0 files and changed the SDM password. But my Integration Repository and Integration directory is working fine.
The error in RWB,
component monitoring is :
com.sap.engine.services.servlets_jsp.server.exceptions.WebServletException: Error in dispatching request to servlet [/sub/componentmonitoringpageprocessor].
performance monitoring :
10 Message(s) : SLD agent unable to specify domain - Error class com.sap.aii.rwb.exceptions.BuildLandscapeException: No System Landscape Directory registered - Attempt to create JCo connection object failed for domain null - Integration Server unable to specify a JCo client - No component names available from Integration Server - SLD agent unable to specify domain - Error class com.sap.aii.rwb.exceptions.BuildLandscapeException: No System Landscape Directory registered - Attempt to create JCo connection object failed for domain null - SLD agent unable to specify domain - Error class com.sap.aii.rwb.exceptions.BuildLandscapeException: No System Landscape Directory registered
configuration :
Cannot read PI domain from the SLD; monitoring cannot therefore be configured. Error message: com.sap.aii.rwb.exceptions.BuildLandscapeException: No System Landscape Directory registered
Please help me!!!!

Hi,
I have checked with the SAP notes 768456 , 764176 , 924721 , and also tried refresing the CPACaches. But nothing seems to work.
I have checked for the XIRWBUSER and all the other users in SU01 and none of them is locked.
Please help !!!!!!

---==== Gilbert's POP QUIZ #03(종료)====---

이미 정답이 나와서 정확한 용도를 맞추신 한 분을 선정합니다.
앞으로는 재치있고 기발한 아이디어만 올려주세요.
당첨자는 MidNigt (RYUL LEE<--영문이름 인정)님입니다.
아이디어 당첨자는 letsko (도도<-- 실명 맞나요? 아니면 실명으로 변경 부탁드립니다.)님입니다.
아이디어의 경우 한 분만 올려주셔서 실명 확인 후 당첨이라는 조건부 당첨으로 처리해 드리겠습니다.
좋은 답을 올려주셨지만 닉네임 수정과 이름 공개를 안하신 분(user639977
, user613138, jinikr, 해피맨)은 안타깝게도 당첨자에서 제외되었습니다.
이번 기회를 놓치셨다고 실망하지 마세요. 다~~~ 운이죠 ^^ 다음 퀴즈에 도전하세요~! 금방 나갑니다.
=========================================================
Oracle SOA Suite을 구성하는 component는 크게 6개로 표현할 수 있습니다.
SOA Suite Components
Oracle JDeveloper
Oracle Business Rules
Oracle BPEL Process Manager
Oracle Business Activity Monitoring
Oracle Web Services Manager
Oracle Enterprise Service Bus
위의 component를 가지고 기업 시스템을 SOA로 구성한다고 할 때, 각각의 component들은 어떤 용도로 활용될까요?
6월 6일 12시까지 정확한 용도를 적어주시는 한 분과 기발하고 재치있는 아이디어를 내주시는 한 분께 스타벅스 상품권을 드립니다.
주의 : 언제나 그렇듯이 닉네임이 userXXXX이고, 이름이 공개되지 않은 분은 당첨자에서 제외됩니다.
==========================================================

SOA Suite Components
가장 널리 사용되고 있는 오라클의 최고의 기술들로 구성된 SOA 스위트
Oracle SOA Suite는 SOA의 개발, 구축, 관리를 위한 포괄적인 서비스 인프라 컴포넌트 솔루션입니다. Oracle SOA Suite를 이용하여 서비스를 생성, 관리하고 복합 애플리케이션 및 비즈니스 프로세스에 통합할 수 있습니다. Oracle SOA Suite의 핫플러거블 컴포넌트들을 이용하여 기존 투자를 교체하지 않고도 아키텍처를 손쉽게 확장, 발전시킬 수 있습니다.
생산성의 개선— 단 한 번의 클릭으로 설치를 완료하고, 편리하고 통합적인 SOA 개발 및 관리를 수행할 수 있는 환경을 제공하는 업계 유일의 포괄적 SOA 플랫폼입니다.
서비스 품질의 개선—독자적인 그리드 아키텍처와 뛰어난 확장성/성능 관련 기능을 활용하여 서비스 가용성과 안정성을 개선할 수 있습니다.
핫 플러그인 지원—IBM, BEA, Microsoft 등의 벤더가 제공하는 소프트웨어와 함께 Oracle SOA Suite를 구축하고 기존 IT 투자 자원의 활용도를 개선할 수 있습니다.
1. Oracle JDeveloper
SOA(Service-Oriented Architecture) 및 Java 개발을 위한 포괄적인 IDE 솔루션으로, Forrester TechRanking에서 주요 Java 벤더 중 가장 높은 평가를 획득한 제품입니다. Oracle Fusion Middleware에서 일부로 제공되는 JDeveloper는 오라클 및 써드 파티 환경에 대한 "핫-플러그인"을 지원하며, 업계 주요 J2EE 애플리케이션 서버 및 데이터베이스와 호환합니다. .
독보적인 유연성—JSP, Struts, JavaServer Faces(JSF), BPEL(Business Process Execution Language) 등을 위한 비주얼 및 선언적 툴을 제공합니다.
저렴한 비용—JDeveloper는 완전 무료로 제공되는 상용 IDE 솔루션입니다. 다른 무료 Java IDE에 비해 월등한 기능을 제공할 뿐 아니라, 개발자들의 비용 부담을 최소화합니다.
2. Oracle Business Rules
Oracle Business Rules는 비즈니스 분석가 및 개발자가 아닌 사람들이 프로그래밍 작업 없이 쉽게 비즈니스 로직을 정의하고 수정할 수 있도록 함으로써, 프로세스 및 애플리케이션을 보다 유연하게 해줍니다. 관련 프로세스 및 애플리케이션 외부의 비즈니스 규칙을 정의, 관리하고, 개별적이고 보다 직관적인 웹 기반 인터페이스를 사용함으로써, Oracle Business Rules는 보다 빠르고 간편한 규칙 수정을 가능하게 하고 후속 재배치 비용을 줄입니다.
고성능—경량, 고성능 규칙 엔진을 사용하여 규칙을 신속하게 평가합니다.
SOA 최적화—Java, XML 및 Oracle SOA Suite 기술과의 강력한 통합으로 이들 환경에서 비즈니스 규칙을 완벽하게 사용할 수 있도록 합니다.
확장성—개방형 아키텍처라 어떤 유형의 인터페이스에도 사용할 수 있는 맞춤형 규칙 저작 툴을 제공합니다.
3. Oracle BPEL Process Manager
Oracle Fusion Middleware제품군을 구성하는 요소의 하나인 Oracle BPEL Process Manager는 서로 다른 애플리케이션과 웹 서비스를 비즈니스 프로세스에 통합하기 위한 기능을 제공합니다. Oracle BPEL Process Manager는 표준 기반 환경에 프로세스들을 신속하게 구축, 적용하는데 필요한 SOA 개발을 위한 핵심 기능을 구현하고 있습니다. (SOA)
사용 편리성—InfoWorld평가에서 "현재 출시 제품 중 가장 포괄적이고 사용하기 편리한 제품"으로 평가된 Oracle SOA Suite의 일부인 생산적 개발 및 관리 툴을 사용한 프로세스 디자인 및 배치"
진보된 확장성—오라클 그리드 기술을 사용하여 고가용성 및 신뢰성 있는 미션 크리티컬 프로세스 실행
핫플러거블—기존 투자된 IT 자원을 활용하여, Oracle BPEL Process Manager를 IBM, BEA 및 JBoss 등의 소프트웨어와 함께 배치
4. Oracle Business Activity Monitoring
Oracle Business Activity Monitoring(Oracle BAM)은 비즈니스 프로세스 및 서비스의 모니터링을 위한 실시간 인터액티브 대시보드 및 사전예방적 경고 기능을 구현하는데 필요한 포괄적인 솔루션을 제공합니다. 비즈니스 임원과 매니저들은 Oracle BAM으로부터 비즈니스 의사 결정에 필요한 정보를 수집하고 환경 변화에 따라 적절한 조치를 수행할 수 있습니다.
강력한 비주얼 대시보드—강력한 비주얼의 대시보드가 매우 얇은 브라우저 기반 클라이언트를 통해 실시간 정보를 제공합니다
강력한 실시간 분석—첨단 복합 이벤트 처리 기술을 사용하여 이벤트 데이터를 처리하고 분석합니다
기업 사용자용으로 구축—기업 사용자들이 코드 변경이 거의 없이 대시보드를 개인화하여 자신만의 보고 및 알림 기능을 구축할 수 있습니다
5. Oracle Web Services Manager
웹 서비스 및 애플리케이션 상호 작용의 안전한 관리
Identity Management가 일반적으로 사용자와 애플리케이션 간의 상호 작용을 보호하고 관리하는 데 중점을 두고 있지만 대부분의 기업들은 애플리케이션 간의 상호 작용도 관리해야 합니다. 웹 서비스는 인터넷상에서 애플리케이션을 연결하는 단순하고 표준화된 방법을 제공하지만, 보다 효과적으로 운영하기 위해서는 보안과 기타 런타임 운영에 대한 관리가 필요합니다. Oracle Web Services Manager— Oracle Fusion Middleware 제품군 중 하나—는 웹 서비스의 운영을 관리하고 이들 서비스 간의 상호 작용을 관리하기 위한 소프트웨어 솔루션입니다.
보안 강화—새로운 또는 기존 애플리케이션과 웹 서비스상에 보안 및 운영 정책 구축
비즈니스 정책 자동화—애플리케이션으로 송수신되는 요청을 가로챈 다음, 이들 정책을 실행하기 위한 런타임 기능 설정
서비스 레벨 보장—이들 정책의 실행을 모니터링하여 서비스 레벨을 보장하고 잠재적인 문제를 피할 수 있도록 지원하는 대시보드
6. Oracle Enterprise Service Bus
OOracle Enterprise Service Bus는 조직 내부는 물론 거래 파트너들과의 데이터 및 엔터프라이즈 애플리케이션의 완벽한 통합을 위해 필요한 모든 것을 제공합니다. Oracle Enterprise Service Bus는 SOA(Service-Oriented Architecture)의 핵심 컴포넌트로, 폭넓은 IT 유연성 및 대응성을 위한 시스템 사이의 저비용, 표준 기반 통합을 가능하게 합니다. SOA는 벤더별 전용 기술에 의존하지 않고 이기종 환경의 복잡성을 보다 손쉽게 관리할 수 있도록 해줍니다.
핫플러거블, 최적화 메시징—다중 프로토콜 메시징 버스가 JMS, MQ Series, Tibco 및 Oracle메시징 기술과 상호 운영되고 최적화된 인메모리 라우팅 및 안전한 전송을 제공합니다.
탁월한 접속성—Connect with IT systems or business partners using support for over 250개 이상의 애플리케이션 어댑터 및 EDI, EDI/AS2, RosettaNet, UCCnet 등을 포함한 표준 B2B 프로토콜을 지원하는 시스템 혹은 비즈니스 파트너와 접속할 수 있습니다.
강력한 확장성—오라클 그리드 기술 기반의 엔터프라이즈급 성능, 확장성 및 관리성

JMS Sender Channel Error with MQ Series

Hi,
I am trying to send a message from MQ Series to XI via JMS Adapter. I am getting this error message, and I have searched the forums for this error message with no luck. Can someone please help? I have asked the BASIS team to double check and make sure the JMS drivers have been deployed. I am still waiting for their reply.
Thanks in advance
Zeshan Anjum

Sorry, I forgot to append the error message.
Here it is:
0 XI inbound processing failed for message at 2006-10-19|09:54:30.925-0500. JMS and XI identifiers for the message are ID:414d51205a3153505420202020202020448dda5420003f01 and b9be54c0-5f81-11db-a551-001125a6015a respectively. The JMS adapter will rollback the database and JMS session transactions. If the session is transacted, the message is not lost and will be retried later. The exception stack trace is java.lang.Exception: Value with name enableDynConfigSender not available
at com.sap.aii.af.service.jms.WorkerJMSReceiver.onMessage(WorkerJMSReceiver.java(Compiled Code))
at com.ibm.mq.jms.MQQueueReceiver.receiveAsync(MQQueueReceiver.java(Compiled Code))
at com.ibm.mq.jms.SessionAsyncHelper.run(SessionAsyncHelper.java(Compiled Code))

JMS and MQ series load balancing.

We have an interface that utilizes the JMS adapter and MQ series from websphere. From a high level, i wanted to ask , when you have additional cluster instances of the adapter framework running. How do the communication channels on these (say 2) instances know which one is to process the message. Or in the scenario, say one comm channel is already bottlenecked, how does the adapter engine know to forward the next JMS message to the other adapter.
I would be most appreciative of any help in this regard. IE docs, website or tools to configure.
Thanks
Jeremy Baker

Hi,
Your JMS adapter is just like your standalone JMS (java) program that puts and retrieves ur messages from the Queues. So u don't need to create any local Queues and QManagers on XI Server. U need to configure the Parameters as mentioned in ur Sender Adapter( WebsphereMQ (MQSeries) and u will be successfully able to retrieve the messages from MQSeries.
Make sure u have deployed the necessary jar's on ur XIServer to connect to WebsphereMQ.
Cheers,
Siva Maranani.

Integrating Messaging system like MQ Series or JMS with SIM

Hi,
I am working with Integrating Messaging system Integration with SIM.
Can anyone tell me in detail how we can integrate Messaging system like MQ Series/JMS with Sun Identity Manager?
Thanks & Regards
Chitarm

Hi,
I am working with Integrating Messaging system Integration with SIM.
Can anyone tell me in detail how we can integrate Messaging system like MQ Series/JMS with Sun Identity Manager?
Thanks & Regards
Chitarm

Drivers for different Queuing series in JMS Adapter , Secutity Level..

Plz can any one provide me JMS Adapter, drivers of different queuing series inTransport protocol.And also security levels in JMS
Also tell me whn to use the particular queuing series.........

Hi,
The queuing series to be is based on the circumstances. If the client is already using MQ, then we need to go for MQ. Similarly for others too.
For deploying the drivers, go thro this How To guide:
https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/3867a582-0401-0010-6cbf-9644e49f1a10
About security levels, i think normal Message Level and Network level securities can be handled with JMS adapters.
Regards,
P.Venkat

JMS over MQ Series (how?)

Hi All,
I am trying to use JMS over MQ series 5.2. Can anyone tell me how to configure the Server for the JMS.
Also in mq series 5.2 JMS jars (javax.jms.* etc or its wrappers) for client programs are not available.
Can some one help me out?
Awaiting your replies....
Regards,
Lee.

There are java classes for MQSeries that you can download:
http://www-4.ibm.com/software/ts/mqseries/txppacs/ma88.html
This page includes a tutorial/manual which tells you (nearly) everything you need to know about using JMS over MQSeries.
Steve.

How to send jms message to mq series

Hi all,
I'm new to JMS and I've been asked to send an xml file to a IBM MQ series message queue.
I need to send this message from an application running on a tomcat webserver.
Basically, what packages do I need to start with that?
Is that possible without installing an MQ client on the webserver?
What parameters would I need to make a connection? I currently only know the QUEUE name and that the MQ is running on a different machine than the webserver is.
Thank you!
Steven

This can help u writing to MQueue
==================================================================
// Program Name
// MQWrite
// Last date of modification
// 1 Oct 2000
// Description
// This java class will read a line of input from the keyboard
// and send it as a message. The program will loop until the
// user presses CTL^Z.
// Sample Command Line Parameters
// -h 127.0.0.1 -p 1414 -c CLIENT.CHANNEL -m MQA1 -q TEST.QUEUE
// Copyright(C), Roger Lacroix, Capitalware
import com.ibm.mq.*;
import java.io.IOException;
import java.util.Hashtable;
import java.io.*;
public class MQWrite {
private MQQueueManager _queueManager = null;
private Hashtable params = null;
public int port = 1414;
public String hostname = "127.0.0.1";
public String channel = "CLIENT.TO.MQA1";
public String qManager = "MQA1";
public String outputQName = "SYSTEM.DEFAULT.LOCAL.QUEUE";
public MQWrite()
super();
private boolean allParamsPresent()
boolean b = params.containsKey("-h") &&
params.containsKey("-p") &&
params.containsKey("-c") &&
params.containsKey("-m") &&
params.containsKey("-q");
if (b)
try
port = Integer.parseInt((String) params.get("-p"));
catch (NumberFormatException e)
b = false;
// Set up MQ environment
hostname = (String) params.get("-h");
channel = (String) params.get("-c");
qManager = (String) params.get("-m");
outputQName = (String) params.get("-q");
return b;
private void init(String[] args) throws IllegalArgumentException
params = new Hashtable(5);
if (args.length > 0 && (args.length % 2) == 0)
for (int i = 0; i < args.length; i+=2)
params.put(args, args[i+1]);
else
throw new IllegalArgumentException();
if (allParamsPresent())
// Set up MQ environment
MQEnvironment.hostname = hostname;
MQEnvironment.channel = channel;
MQEnvironment.port = port;
else
throw new IllegalArgumentException();
public static void main(String[] args)
MQWrite write = new MQWrite();
try
write.init(args);
write.selectQMgr();
write.write();
catch (IllegalArgumentException e)
System.out.println("Usage: java MQWrite <-h host> <-p port> <-c channel> <-m QueueManagerName> <-q QueueName>");
System.exit(1);
catch (MQException e)
System.out.println(e);
System.exit(1);
private void selectQMgr() throws MQException
_queueManager = new MQQueueManager(qManager);
private void write() throws MQException
String line;
int lineNum=0;
int openOptions = MQC.MQOO_OUTPUT + MQC.MQOO_FAIL_IF_QUIESCING;
try
MQQueue queue = _queueManager.accessQueue( outputQName,
openOptions,
null, // default q manager
null, // no dynamic q name
null ); // no alternate user id
DataInputStream input = new DataInputStream(System.in);
System.out.println("MQWrite v1.0 connected");
System.out.println("and ready for input, terminate with ^Z\n\n");
// Define a simple MQ message, and write some text in UTF format..
MQMessage sendmsg = new MQMessage();
sendmsg.format = MQC.MQFMT_STRING;
sendmsg.feedback = MQC.MQFB_NONE;
sendmsg.messageType = MQC.MQMT_DATAGRAM;
sendmsg.replyToQueueName = "ROGER.QUEUE";
sendmsg.replyToQueueManagerName = qManager;
MQPutMessageOptions pmo = new MQPutMessageOptions(); // accept the defaults, same
// as MQPMO_DEFAULT constant
while ((line = input.readLine()) != null)
sendmsg.clearMessage();
sendmsg.messageId = MQC.MQMI_NONE;
sendmsg.correlationId = MQC.MQCI_NONE;
sendmsg.writeString(line);
// put the message on the queue
queue.put(sendmsg, pmo);
System.out.println(++lineNum + ": " + line);
queue.close();
_queueManager.disconnect();
catch (com.ibm.mq.MQException mqex)
System.out.println(mqex);
catch (java.io.IOException ioex)
System.out.println("An MQ IO error occurred : " + ioex);
// Description
// This java class will read a line of input from the keyboard
// and send it as a message. The program will loop until the
// user presses CTL^Z.
// Sample Command Line Parameters
// -h 127.0.0.1 -p 1414 -c CLIENT.CHANNEL -m MQA1 -q TEST.QUEUE
import com.ibm.mq.*;
import java.io.IOException;
import java.util.Hashtable;
import java.io.*;
public class MQWrite {
private MQQueueManager _queueManager = null;
private Hashtable params = null;
public int port = 1414;
public String hostname = "127.0.0.1";
public String channel = "CLIENT.TO.MQA1";
public String qManager = "MQA1";
public String outputQName = "SYSTEM.DEFAULT.LOCAL.QUEUE";
public MQWrite()
super();
private boolean allParamsPresent()
boolean b = params.containsKey("-h") &&
params.containsKey("-p") &&
params.containsKey("-c") &&
params.containsKey("-m") &&
params.containsKey("-q");
if (b)
try
port = Integer.parseInt((String) params.get("-p"));
catch (NumberFormatException e)
b = false;
// Set up MQ environment
hostname = (String) params.get("-h");
channel = (String) params.get("-c");
qManager = (String) params.get("-m");
outputQName = (String) params.get("-q");
return b;
private void init(String[] args) throws IllegalArgumentException
params = new Hashtable(5);
if (args.length > 0 && (args.length % 2) == 0)
for (int i = 0; i < args.length; i+=2)
params.put(args[i], args[i+1]);
else
throw new IllegalArgumentException();
if (allParamsPresent())
// Set up MQ environment
MQEnvironment.hostname = hostname;
MQEnvironment.channel = channel;
MQEnvironment.port = port;
else
throw new IllegalArgumentException();
public static void main(String[] args)
MQWrite write = new MQWrite();
try
write.init(args);
write.selectQMgr();
write.write();
catch (IllegalArgumentException e)
System.out.println("Usage: java MQWrite <-h host> <-p port> <-c channel> <-m QueueManagerName> <-q QueueName>");
System.exit(1);
catch (MQException e)
System.out.println(e);
System.exit(1);
private void selectQMgr() throws MQException
_queueManager = new MQQueueManager(qManager);
private void write() throws MQException
String line;
int lineNum=0;
int openOptions = MQC.MQOO_OUTPUT + MQC.MQOO_FAIL_IF_QUIESCING;
try
MQQueue queue = _queueManager.accessQueue( outputQName,
openOptions,
null, // default q manager
null, // no dynamic q name
null ); // no alternate user id
DataInputStream input = new DataInputStream(System.in);
System.out.println("MQWrite v1.0 connected");
System.out.println("and ready for input, terminate with ^Z\n\n");
// Define a simple MQ message, and write some text in UTF format..
MQMessage sendmsg = new MQMessage();
sendmsg.format = MQC.MQFMT_STRING;
sendmsg.feedback = MQC.MQFB_NONE;
sendmsg.messageType = MQC.MQMT_DATAGRAM;
sendmsg.replyToQueueName = "ROGER.QUEUE";
sendmsg.replyToQueueManagerName = qManager;
MQPutMessageOptions pmo = new MQPutMessageOptions(); // accept the defaults, same
// as MQPMO_DEFAULT constant
while ((line = input.readLine()) != null)
sendmsg.clearMessage();
sendmsg.messageId = MQC.MQMI_NONE;
sendmsg.correlationId = MQC.MQCI_NONE;
sendmsg.writeString(line);
// put the message on the queue
queue.put(sendmsg, pmo);
System.out.println(++lineNum + ": " + line);
queue.close();
_queueManager.disconnect();
catch (com.ibm.mq.MQException mqex)
System.out.println(mqex);
catch (java.io.IOException ioex)
System.out.println("An MQ IO error occurred : " + ioex);

JMS - MQ Series

Similar Messages

Maybe you are looking for