Re: WAS 7.0 and WebSphere MQ 7 Connection

[Santhosh Nair]

Thanks for your reply and suggestion. Could you please refer some reference guid or step-step configuration to setup the WMQ Message provider for Remote WMQ Server

[LEMI...@uk.ibm.com]

Hi.

The relevant info-centre sections are here:

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/tmm_ep.html

Configuration is here:

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/tmj_admrm.html

A good dev works article is here:

http://www.ibm.com/developerworks/websphere/techjournal/0901_leming/0901_leming.html

Cheers, Matt.

[Santhosh Nair]

New and created new bus with two destinations mapped to my remote Queues QIN and QOUT.

Then i created a New Bus Member of type MQ Server it asks me a virtual Q Manager name which i provided and Finish.

Then i change Connection Factories, Q Connection Factories, Queues and Activation Specifications all using the newly created above Bus.

_But when I am running my application it gives me following output on log console... (In bold I am concern)_

[3/19/09 15:49:50:699 GMT] 00000028 PrivExAction W J2CA0144W: No mappingConfigAlias found for ConnectionFactory or DataSource jms/t24CxFactory.
[3/19/09 15:49:50:711 GMT] 00000028 PrivExAction W J2CA0114W: No container-managed authentication alias found for ConnectionFactory or DataSource jms/t24CxFactory.
[3/19/09 15:49:56:784 GMT] 00000028 DMAdapter I com.ibm.ws.ffdc.impl.DMAdapter getAnalysisEngine FFDC1009I: Analysis Engine using data base: /usr/IBM/WebSphere/AppServer/profiles/AppSrv01/properties/logbr/ffdc/adv/ffdcdb.xml
[3/19/09 15:49:56:843 GMT] 00000028 FfdcProvider I com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /usr/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/ffdc/server1_61ad61ad_09.03.19_15.49.56.75256422.txt com.ibm.ws.sib.api.jmsra.impl.JmsJcaManagedConnectionFactoryImpl.createManagedConnection 1
[3/19/09 15:49:56:913 GMT] 00000028 FfdcProvider I com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /usr/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/ffdc/server1_61ad61ad_09.03.19_15.49.56.87356423.txt com.ibm.ejs.j2c.poolmanager.FreePool.createManagedConnectionWithMCWrapper 199
[3/19/09 15:49:56:983 GMT] 00000028 FfdcProvider I com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /usr/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/ffdc/server1_61ad61ad_09.03.19_15.49.56.92956424.txt com.ibm.ws.sib.api.jmsra.impl.JmsJcaConnectionFactoryImpl.createConnection 1
[3/19/09 15:49:57:030 GMT] 00000028 FfdcProvider I com.ibm.ws.ffdc.impl.FfdcProvider logIncident FFDC1003I: FFDC Incident emitted on /usr/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/ffdc/server1_61ad61ad_09.03.19_15.49.57.00356425.txt JmsManagedConnectionFactoryImpl.createConnection JmsManagedConnectionFactoryImpl.createConnection#3
*[3/19/09 15:49:57:049 GMT] 00000028 JMSConnector E com.temenos.t24browser.comms.JMSConnector CWSIA0241E: An exception was received during the call to the method JmsManagedConnectionFactoryImpl.createConnection: com.ibm.websphere.sib.exception.SIResourceException: CWSIT0088E: There are currently no messaging engines in bus MQServerBus running. Additional failure information: CWSIT0103E: No messaging engine was found that matched the following parameters: bus=MQServerBus, targetGroup=null, targetType=BusMember, targetSignificance=Preferred, transportChain=InboundBasicMessaging, proximity=Bus..*

The funny thing is that when i go into my Bus member and try to craete new Message engine there is no option to create new engine??? what should i do...

Thanks for your help...:)

[LEMI...@uk.ibm.com]

Hi.

The problem you are experiencing is the fact that the MQ server construct that is part of the SIBus requires a messaging engine in order to work. So you need at least two bus members:

1) the MQ server you already have
2) an application server bus member which will host the ME

HOWEVER:

If you are interested in using WMQ I would suggest not using the MQ server SIBus construct at all and instead just use the WMQ messaging provider. You can create queues, connection factories etc using this and they will connect you to WMQ directly.

Cheers, Matt.

[LEMI...@uk.ibm.com]

Hi.

No problem. They seem to have developed arbitrary spaces. Lets try again:

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/tmm_ep.html

http://publib.boulder.ibm.com/infocenter/wasinfo/v7r0/index.jsp?topic=/com.ibm.websphere.express.doc/info/exp/ae/tmj_admrm.html

Cheers, Matt.

[Santhosh Nair]

I am sorry for bothring you but none of the above topics are working ...i mean links giving me following error.

The topic that you have requested is not available. The link may be wrong, or you may not have the corresponding product feature installed. This online help only includes documentation for features that are installed.

Thanks again

[STEWAR...@principal.com]

This is a common problem with posting urls in the forums here. Basically if you look through the URL as it comes up in your browser...just take out any %20 that is added into the url and it should work fine.

[Santhosh Nair]

I am trying what you suggested from yesterday but My MQ Server's Server Connection Channel is constantly in Inactive state I have tried to satart it but it ends up with the message that 'start command accepted' but never get into Start state becaue of that when I am trying to create anything from application server which include Activation spec, connection fac, q conn fac anbd queues everytime I end it up with the following error message on 'Test Connection' panel menu.

A connection could not be made to WebSphere MQ for the following reason: JMSCMQ0001: WebSphere MQ call failed with compcode '2' ('MQCC_FAILED') reason '2035' ('MQRC_NOT_AUTHORIZED').

What should i do. On IBM website it says

Server connection channel
Optional. The WebSphere MQ server connection channel name used when connecting to *WebSphere MQ queue manager* or queue-sharing group.

I am using MQ Queue Manager????

[Graham Hopkins]

"Santhosh Nair" <csan...@temenos.com> wrote in message
news:1343546858.123753981...@ltsgwas009.sby.ibm.com...

Hi,

The server conn channel staying in inactive is expected, it will only show
as running state when a client has connected into it.

The 2035 error code you are receiving means that the user id you are trying
to connect with is not authorized to do so, by default this user id is the
one under which the application server is running, either authorize this
user to connect to the queue manager or provide an authentication alias on
the connection factory which specifies a user that is authorized to connect
to the queue manager

[Brian S Paskin]

Hi, Quick question...If you are going to use WMQ is there any reason to use the SIBus?

Regards,
Brian

[LEMI...@uk.ibm.com]

Hi.

Typically that error means that the user id you are connecting as (probably the userid which WAS is running under) is not a member of the mqm group on your queue manager box. There are many ways you can fix this but the quickest is to add the userid to the mqm group or use an auth alias on your connection factory/activation spec.

I'm not sure I entirely follow your last question but the "Server connection channel" field should contain the name of the server conn channel defined on your queue manager unless you are using the default in which case it can be left blank.

Cheers, Matt.

[mallikarjunas...@emc.com]

Even I got the same kind of error , It got resolved after adding the user to mqm group.