OSB + IBM MQ v.7.5 (messaging)

Greetings!
I need to publish and subscribe to a topic hosted at IBM WebSphere MQ ver. 7.5. Using instruction at oracle.com I copied client library (com.ibm.mq.jar) into domain lib and tried to create MQConnection resource, but failed. Menu Resources/Utils/MQ Connections still not exists in sbconsole.
Then I tried another way, I copied a mq client library of ver. 7.0. The desired menu appeared, I managed to create a connection, but... It didn't work. The error message is telling me, that connection channel can't give me a connection.
So, my first question: Is there a way to connect OSB with MQ v.7.5?
If it is possible, what should i read or do?
Thanks in advance.

Hi,
According to this document (table 1-4), OSB 11g only supports up to version 7.0.1.8 of MQ. That's up to date with PS6 (11.1.1.7) which is, at the time of writing, the latest patch set for OSB. This doesn't mean that it definitely won't work, but, from your experience, it certainly seems like something crucial has changed between MQ 7.0 and 7.5.
Mike Croft
C2B2 Expert Support

Similar Messages

OSB proxy - MQ transport - return the message to MQ, on Business Service down/unavailable

My proxy is using MQ protocol to get the messages from MQ and processing the message and connecting the Business Service.
Is there anyway to send the message to back to MQ, If the Business Service is down. So the proxy will keep on try the message to processes until the BS is up
thanks

The problem is that the consumer application is picking up all files that appear in the directory. It doesn't matter what you put in.
We suggested that they use a file mask on the types of files that need to be picked up, but that seems to be a problem.
So all I want to know is, what is the behaviour of the file transport protocol as a business server and if there is any way to influence this.
And if my assumption is correct that the .a suffix is usd by the OSB while processing files.
Any extra documentation about the file transport protocol is welcome.
Thanks
Henk

OSB 11g JMS minimum Delay Between Messages

Hi ,
We are consuming messages asynchronously from Weblogic JMS Queue using OSB BS. We want to add time delay between messages consume. It is kind of sequential messages, one after another, with time delay 1 sec. How to achieve this ?
Thanks,
Sri

ps1(jms)->ps2(sb)->ps3(sb)->ps4(sb)From my understanding, the code for ps2, ps3 and ps4 should also get executed in the thread in which ps1 is executed. So if you put a constraint on the first then you are effectively putting a constraint on the entire flow.
The number 16 for jms comes from weblogic mdb container's internal. I believe it is fixed and cant change . Doc says
Default work manager or unconstrained work manager : Thread varies due to self-tuning, up to Min(max-beans-in-free-pool,16) If you are on non polling transports like http, then the max thread constraint available should be restricted only by the size of the self tuning execute thread pool. All requests coming for the proxy will be placed in the execute queue which will be further serviced by a thread in the execute thread pool.
Refer to weblogic tuning docs on fine tuning default exceute queue and threads.

OSB: Proxy doesn't consume JMS messages

Guys, I'm getting stuck with this one ...
I've got four JMS proxy services. One of them uses Publish to enqueue a message into the three others. This way I get three copies of a single message, each in dedicated JMS queue. The same three JMS proxies are supposed to consume messages from JMS queues and process them. The configuration is the same for all three proxies and all three JMS queues. In fact all was cloned and the difference is only in suffix. So, I've got QueueA, QueueB, QueueC and ProxyA, ProxyB and ProxyC. So if I stick to these names, ProxyMain uses 3x Publish actions to enqueue a message into ProxyA, ProxyB and ProxyC at the same time. This is a proved solution and it has worked for years flawlessly!
However, something weird happened a couple of days ago. All of a sudden, one of those three consuming JMS proxies doesn't consume anything. There's no issue on producing side (the first proxy) as the numbers of messages in all three queues are still increasing. Still, only messages from QueueA and QueueB are being consumed by ProxyA and ProxyB. The third queue (QueueC) doesn't have any consumer attached from ProxyC and I don't know why.
I've already checked everything I know - proxy is enabled, there are no errors in logs related to the proxy or JMS, the issue is not reproducible in test environment with the same configuration, there are no JMS Quota or connection factory restrictions, consuming flag is enabled on queue ...
The lack of errors in logs makes me feel like the ProxyC is connected to something else. However, the same proxy is used for producing messages (from ProxyMain) and messages are incoming to the queue so the endpoint set in proxy must be correct!
Any help, hint or idea is appreciated ...

The third queue (QueueC) doesn't have any consumer attached from ProxyC and I don't know whyTry renaming ProxyC to say ProxyC1 and activate the session. This will create a new underlying MDB for the jms proxy and you will see consumers getting set on the queue.. Faced this issue many times in our production environment and easiest workaround we found was to rename the proxy service [ toggling enable/disable proxy doesn't seem to have ny effect).. you can change the name to the original proxy once the consumers are set..

How to get invalid message in OSB?

Hi,
I have OSB Proxy Service which reads XML messages from JMS Queue.
Is it possible to handle non xml bad messages in my proxy service ? I want to get them, write into log
and put it another queue which contains all buggy messages? I use validate, but non XML messages don't fall
into my Proxy Service from JMS, and stay in jms queue.

Create the messaging type proxy service with input type as "Text" to read messages from JMS queue. Then in it's message flow route the message to your existing proxy. In the route node of first proxy put an error handler and add a check for XML validation failure. From inside the error handler call a business service which will put that message into buggy queue. You may also log the message in error handler.
Regards,
Anuj

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

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

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

JMS messaging with OSB

Hi Forum, So far I have not been able to find any useful information hence the question:
1. Is OSB an implementation of JMS?
2. To use JMS with OSB do I need to install separate JMS? If not does JMS install by itself when installing OSB?
Thanks!

JMS (Java Messaging Service) is a transport protocol (like File, FTP, email, HTTP etc.) which is supported by OSB (Oracle Service Bus - which is a service bus product used for transport protocol mediation).
Once you have installed OSB, you may use it to configure services which use JMS transport. Please refer to know more -
http://download.oracle.com/docs/cd/E14571_01/doc.1111/e15866/jms.htm#i1051082
http://en.wikipedia.org/wiki/Java_Message_Service
Regards,
Anuj

Separating logs in OSB based on project - is this possible?

Hi,
I'm using OSB 11.1.1.3.0 and I'd like log messages generated from the log action to go to a different log file based on OSB project. I've found messages on the forum that discuss this, for example:
alsb logging
These posts only explain how to log messages from ALL OSB projects in a domain to a SINGLE log file, which I already have working using a LogFilter, but I'd like to take it a step further and log messages to a different log file depending on the specific project where the log action was invoked.
I want to use a method that involves LogFilters rather than explicit OSB Reporting or File business services, to keep it unobtrusive from the perspective of the application developer.
I've checked the output of the LogRecord methods and I don't see anything that will let me get a handle on the specific project a log originates from, but I've noticed that at the start of each log message information is logged inside [], for example:
[raiseEvent Operation, raiseEvent Operation_request, stage1, REQUEST]
This looks promising but unfortunately it doesn't always contain the OSB project name (sometimes it does, but not in this example).
So my questions are:
1. Has anyone successfully split logs based on OSB project using the WLS/JDK logging system?
2. Is there a way to specify what is logged in the [] at the start of each log message?
Any help is much appreciated.
Thanks,
Jason

It has been done in a previous client by the then BEA in a different manner. Instead of using any java callouts or log4j code within osb, that task has been shifted to a weblogic startup class. So this is how it works:
At OSB
Use Log action to record log messages. Put appropriate annotation based on the project to categorize the log messages into different files later.
Example: Log : Request Message Processed succesfully. Annotation: OSB_LOG: <Project_Name> Severity: Info. Note Annotation has 2 parts : a hard coded OSB_LOG and a variable +<Project_Name> part+
This log message gets recorded in the manged server log file as : Info: OSB_LOG:<Project_Name> Request Message Processed successfully
At WLS
You have to configure the logging settings of the server so that this log message reaches the domain logger. For e.g. server should be configured to broadcast to domain logger at severity info and above if you want to get the above message
Startup class
This startup class will be deployed to the admin server. What it does is in the startup method gets the domain logger and registers a custom handler to it. The custom handler is implemented to inspect each LogRecord it gets from domain logger to check for the presence of hard coded string (OSB_LOG) . If the record has this string then it understands this log record has come from OSB application and not from any WLS subsystem and hence this message is important to it. Next step is to determine the logger name by getting the <Project_Name> from the Log Record. It creates a new logger with the same name as that of Project_Name and logs the message with the same severity as in the original message.
One key advantage of this is that is if your OSB is deployed to a cluster, you will get log messages from all managed servers for that particular project ( or a proxy service) at one location.

Sender JMS adapter configuration for IBM MQSeries

Dear All,
i am doing a IBM MQSeries 5.2.x Message ->sender JMS adapter -> XI server -> receiver RFC adapter -> R/3.
i have deployed the JMS adapter with the required jar files of IBM MQSeries 5.2.x in XI server.
in Sender JMS adapter configuration for IBM MQSeries 5.2.x, i have put following data:
1. Transport Protocol: Websphere MQ - is it okay?
in JMS provider settings:
2. in channel name - what should be there?
3. Transport Network protocol should be TCP/IP or WebsphereMQ - how to decide this thing.
4. JMS Complaint - whether WebsphereMQ or JMS API.
in JMS Settings:
5. JMS Queue user - is this IBM MQSeries 5.2.x Queue User or someother user?
6. JMS Message Selector - what data to take here.
So if anybody has connected IBM MQSeries 5.2.x to XI via JMS adapter, please answer my above queries.
Regards,
Rajeev Gupta

Hi Swaroop,
you can send me those documents at my gmail-id : [email protected]
Hi All,
one more question - to connect XI server to IBM MQSeries via JMS adapter in ID, do we need to have a MQSeries Client installed on XI server - or - just by configuring JMS adapter, we can send messages from IBM MQSeries to XI server without any MQSeries client on XI server?
Why Channel name is required in JMS configuration data?
Thanks,
Rajeev Gupta

Mediator not detecting faults when WS-Security Message Encryption enabled

We are using a SOA 11g composite to call a set of OSB proxy/business pairs which in turn call further web services and return the responses. The OSB proxy services are trivial: they each expose the WSDL of the downstream web service and route all messages without any transformation to a business service that also uses the downstream WSDL.
The SOA composite is composed largely of a mediator that accepts requests, transforms payloads, routes to the correct OSB service, transforms the response, and replies to the caller.
I have configured my OSB services, in case of a SOAP fault returned from downstream, to simply "Reply with Failure", which causes the body received from the downstream web service (a SOAP fault) to be returned to the SOA composite along with an HTTP 500 error. I have created a Fault processing section in each of my routing rules that maps the downstream fault to a fault that the mediator returns to the caller.
In my local test instance, this works fine; OSB receives a custom SOAP fault from the downstream service, sends it back to SOA where the mediator recognizes the fault and maps it, and throws a SOAP Fault back to the caller.
In our formal testing environment, however, it does not work. I have validated that the response comes back to the Mediator in the same way as it does in my local environment, but the Mediator attempts to use the standard response transformation configured for that routing rule rather than the fault transformation. The fundamental difference between my local environment and the formal test environment is that WS-Security has been enabled between SOA and OSB using the wss10_username_token_with_message_protection via OWSM.
I have a workaround, namely to add a choose clause in my reply transformation XSL file that looks for a SOAP fault and sends it back to the caller if one is found, however this is a nasty hack.
Has anyone had experience with this scenario, where implementing WS-Security causes SOAP Faults to no longer be recognized? My best guess at this point is that when "Reply with Failure" is used, OSB returns the SOAP Fault body in an encrypted form and SOA assumes that the call succeeded (despite the HTTP 500 error). I have not found a way to tell OSB not to encrypt the response message in the case of "Reply with Failur", but it doesn't encrypt responses when it throws its own faults (BEA-380001, for instance).

X509V1 is not a valid value for "Valuetype". So I guess this should not be the problem.

Error Message with Installing Java Add in Component 640

We are trying to install a JAVA Add-in for ABAP using the Installation
Master CD 51031149. From SAPINST, SAP Netweaver '04 Support
release 1 > JAVA Add-in for ABAP > IBM DB2 UDB for iSeries >
Central System > JAVA Finalization, we are getting the error message
on the screen JAVA System - General Parameters: Cannot find the default
profile for the SAP system SDS (where we are trying to install the
addinat the default location "\ac4sap02.nmhg.com/sapmnt/SDS/profile/
DEFAULT.PFL. Make sure the installation step 'Preparation of Central
Instance Host' has run successfullyon the central instance host for the
SAP system SDSand that the profile directory is mounted at
'undefined/SDS/profile'.
From our install server @ '/usr/sap'SDS/SYS/profile' I have a
DEFAULT.PFL, DEFAULT.1.PFL, (2) SDS_DVEBMGS86_ac4sap files.
We are on an iSeries 570 4-way, installing SRM4.0, XI3.0 with SUS, CCM, TREX LAC and IPC.
Thanks
Chris Sugg
NACCO Inc.

Hi Chris,
I am also getting the same error while installing the SAP Web AS 6.40 SR1 on IBM iSeries OS.
Error Message:"Cannot find the default profile for the SAP system <SID> at the default location /sapmnt/SDS/profile/
DEFAULT.PFL Make sure the installation step 'Preparation of Central
Instance Host' has run successfullyon the central instance host for the
SAP system SDSand that the profile directory is mounted at
'undefined/SDS/profile'."
I already apply Note: 789188
Can U Guide me the solution...
Regards

Problem with Xquery transformation in OSB

hi,
My scenario is that I have to break the data in a single tag of xml A, to populate multiple tags of xml B.I am using Xquery transformation and substring function to achieve this. The problem comes when i import the xquery resource in OSB and try to do the transformation in a proxy service it gives the following error
<con:fault xmlns:con="http://www.bea.com/wli/sb/context">
<con:errorCode>BEA-382510</con:errorCode>
<con:reason>
*OSB Assign action failed updating variable "message": com.bea.wli.common.xquery.XQueryException: Error parsing XML: {err}XP0006: "element {http://schemas.xmlsoap.org/soap/envelope/}Body { {http://www.w3.org/2004/07/xpath-datatypes}untypedAny }": bad value for type element {http://www.example.org/data}data { {http://www.w3.org/2001/XMLSchema}anyType }*
</con:reason>
<con:location>
<con:node>PipelinePairNode1</con:node>
<con:pipeline>PipelinePairNode1_request</con:pipeline>
<con:stage>stage1</con:stage>
<con:path>request-pipeline</con:path>
</con:location>
</con:fault>
the configuration i have done in the proxy service is this::_
Assign: [XQuery resource..] to [message]
Delete: [.] in [body]
Insert [$message] [as first child of][.] in [body]
The Xquery resource is the .xq file that i have generated for Xquery transformation.
and i m routing this proxy service to a business service that wud take the XML and dump it to my D drive using file protocol.
Edited by: rahulc on Oct 12, 2010 12:40 AM
Edited by: rahulc on Oct 12, 2010 12:41 AM

My Xquery is this::
(:: pragma bea:global-element-parameter parameter="$data1" element="ns0:data" location="data.xsd" ::)
(:: pragma bea:global-element-return element="note" location="note.xsd" ::)
declare namespace ns0 = "http://www.example.org/data";
declare namespace xf = "http://tempuri.org/OSB_Try/tag_break/";
declare function xf:tag_break($data1 as element(ns0:data))
as element(note) {
<note>
<to>
fn:substring(data($data1),
1 ,
6)
</to>
<from>
fn:substring(data($data1),
7 ,
6)
</from>
<heading>
fn:substring(data($data1),
13 ,
6)
</heading>
<body>
fn:substring(data($data1),
19 ,
11)
</body>
</note>
declare variable $data1 as element(ns0:data) external;
xf:tag_break($data1)
and my data is this::
<?xml version="1.0"?>
<ns0:data xmlns:ns0="http://www.example.org/data">DON'T FORGET ME THIS WEEKEND!</ns0:data>
and i have tested this zquery for the above data and this is the transformation its doing::
<note>
<to>DON'T </to>
<from>FORGET</from>
<heading> ME TH</heading>
<body>IS WEEKEND!</body>
</note>
Edited by: rahulc on Oct 12, 2010 1:57 AM

Need Help:Handling CLOB in OSB Proxy Service

Hello All-
We have created an AQ in Oracle DB which will have the following message Structure:
CREATE OR REPLACE TYPE enqueue_payload AS OBJECT
( field1 VARCHAR2(100),
field2 VARCHAR2(100),
field3 DATE,
field4 VARCHAR2(100),
field5 NUMBER,
payload CLOB,
In the Payload field we are enqueing an XML message.
We have to use a OSB proxy service to dequeue the message from the AQ, transform it to another format and send to a SOA Composite.
We created a AQ Adapter in Jdeveloper 11g and imported the WSDL, XSD and .jca jca binding file into the OSB project. And configured the OSB proxy service using the WSDL imported.
However in OSB proxy service message flow when I try to create an XQUERY transformation, I see that the Payload field does not expose the structure of the XML message that is being enqueued. I even changed the message structure definition to have the payload field as XMLType. But it didn't help.
On analyzing the XSD created by AQ Adapter, I see that the payload is being defined as "string" in the XSD.
Inputs Needed
=========
1. How can we parse the payload field defined as CLOB/XMLType in OSB so that I can see the structure of the XML message it holds ?
2. Is there any in-built function in OSB to convert it to XML ?
3. Any other inputs in order to transform the XML message coming in the payload field as CLOB/XMLType
Please provide your inputs and I hope that I have clearly explained my use case.
Thanks in advance for your time and help!!
Regards,
Dibya

Hi Atheek-
Please find the logs below:
Payload:: Indicates the actual payload with all the headers fields coming from AQ
Payload After Applying the Function:: Indicates the data that is logged after applying the fn-bea:inlinedXML function.
The function fn-bea:inlinedXML is extracting the data from the XML tags :(
####<Dec 20, 2010 12:14:26 PM GMT+05:30> <Info> <ALSB Logging> <vhydaiavm-03> <osb_server1> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-000A464703C2C06A4338> <6751713a0ce9f61d:-6e70b631:12d02855fef:-7ff4-0000000000000002> <1292827466595> <BEA-000000> < [PipelinePairNode1, PipelinePairNode1_request, stage1, REQUEST] Payload:: <apps:ORA_FUSION_LOAD_XMLTYPE xmlns:soap-env="http://schemas.xmlsoap.org/soap/envelope/" xmlns:apps="http://xmlns.oracle.com/xdb/APPS">
*<RICE_ID>PRJ_INT_30</RICE_ID>*
*<SOURCE_SYSTEM>ORACLE</SOURCE_SYSTEM>*
*<DATETIME>2010-12-20T10:49:17.000Z</DATETIME>*
*<TRANSACTION_ID>PRJ_INT_30-1</TRANSACTION_ID>*
*<RECORD_COUNT>1</RECORD_COUNT>*
*<PAYLOAD><![CDATA[<ALTPPSEGHIERARCHY><sgmt_name>Company</sgmt_name><include_parent_child>C</include_parent_child><parent_flex_value>P</parent_flex_value><child_flex_value_low>03</child_flex_value_low><child_flex_value_high>03</child_flex_value_high><start_date_active></start_date_active><end_date_active></end_date_active></ALTPPSEGHIERARCHY>]]></PAYLOAD>*
*<ATTRIBUTE1 NULL="TRUE"/>*
*<ATTRIBUTE2 NULL="TRUE"/>*
*<ATTRIBUTE3 NULL="TRUE"/>*
*<ATTRIBUTE4 NULL="TRUE"/>*
*<ATTRIBUTE5 NULL="TRUE"/>*
*</apps:ORA_FUSION_LOAD_XMLTYPE>>*
####<Dec 20, 2010 12:14:26 PM GMT+05:30> <Info> <ALSB Logging> <vhydaiavm-03> <osb_server1> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-000A464703C2C06A4338> <6751713a0ce9f61d:-6e70b631:12d02855fef:-7ff4-0000000000000002> <1292827466595> <BEA-000000> < [PipelinePairNode1, PipelinePairNode1_request, stage1, REQUEST] Payload After Applying the Function:: PRJ_INT_30ORACLE2010-12-20T10:49:17.000ZPRJ_INT_30-11>
####<Dec 20, 2010 12:14:26 PM GMT+05:30> <Info> <JDBC> <vhydaiavm-03> <osb_server1> <[ACTIVE] ExecuteThread: '3' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <6751713a0ce9f61d:-6e70b631:12d02855fef:-7ff4-0000000000000002> <1292827466688> <BEA-001128> <Connection for pool "EBS_DHAARA_DataSource" closed.>

Remote queue in XI server for IBM MQSeries

Dear All,
my scenario is IBM MQSeries -> message via sender JMS adapter -> XI -> receiver RFC adapter -> R/3.
now for IBM MQSeries to send a message to XI via a transmission queue in MQSeries - it needs a remote queue name and queue manager name in XI server.
So now where can i find these information regarding remote queue name and queue manager name in XI server. I currently do not know whether in XI server, currently is there any remote queue or not? So how to find this information. If we do not have remote queue manager in XI currently, then how to install a remote queue name and queue manager in XI server.
It is slightly urgent. So i request you all to please reply quickly.
Thanks and Regards,
Rajeev Gupta

Dear Sebastin,
Thanks for your inputs.
I have to connect to MQSeries 5.2.1 to XI server.
am getting the below error in Communicatin Channel Monitoring for my sender JMS adapter:
Error during channel initialization; exception trace: javax.jms.JMSException: MQJMS2005: failed to create MQQueueManager for '<IP_ADRESS>:<MQ_QUEUE_MANAGER>'
at com.ibm.mq.jms.services.ConfigEnvironment.newException(ConfigEnvironment.java:546)
at com.ibm.mq.jms.MQConnection.createQM(MQConnection.java:1137)
at com.ibm.mq.jms.MQConnection.createQMNonXA(MQConnection.java:799)
com.ibm.mq.MQException: Message catalog not found
at com.ibm.mq.MQManagedConnectionJ11.<init>(MQManagedConnectionJ11.java:171)
at com.ibm.mq.MQClientManagedConnectionFactoryJ11._createManagedConnection(MQClientManagedConnectionFactoryJ11.java:228)
i have written '<IP_ADRESS>:<MQ_QUEUE_MANAGER>' just to hide the data - i am getting <IP_ADRESS> as IP Adress i gave in JMS adapter and <MQ_QUEUE_MANAGER> as Queue Manager i gave in JMS adapter.
i am using the correct IP and 1414 port of MQSeries server. I have used a MQQueueManager defined in MQSeries. i have deployed JMS adapter properly in XI server.
So can anybody suggest what could be the possible reason of this error and how to rectify it. It is slightly urgent.
One more question - should the queue manager in MQSeries server be a local or remote queue manager..........i was not able to create a remote queue manager in MQSeries 5.2.1 as by default it is creating a local queue manager.......
Thanks and Regards,
Rajeev Gupta

JMS Message Bridge with MQ, only BytesMessage available ?

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

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

OSB + IBM MQ v.7.5 (messaging)

Similar Messages

Maybe you are looking for