| Author |
Message
|
| NSJ |
 Posted: Wed Jul 06, 2005 7:42 am Post subject: ICS 4.3 and WebSphere MQ Adapter 2.7.0 |
 |
|
Novice
Joined: 06 Jul 2005
Posts: 12
|
Hi
I am trying to configure ICS4.3 and MQ Adapter 2.7 with adapter framework 2.6.0. The MQ Connector shows as running when i deploy and with the Test Connector i am able to bind to the connector controller and send business objects to the adapter. But when i use the MQ Connector startup bat file ie the actual agent.It is not able to connect to the connector controller. Has anyone experienced this problem before ? .I am pasting the output in my startup script.
Note:I am using the same connector configuration file when running the test connector(when it runs fine) and the real connector.
ers\bin\start_adapter" -nWebSphereMQ -sWINICS -lcom.crossworlds.connectors.WebSphereMQ.ConnectorAgent -cC:\IBM\MQConnector.cfg
[Thread: wbia_main (#693512346)] [Type: Info] [MsgID: 17000] [Mesg: Initialization started. Name: WebSphereMQ. ConfigFileName: C:\IBM\MQConnector.cfg. Implementation DLL/Class Name: com.crossworlds.connectors.WebSphereMQ.ConnectorAgent.class.]
[Thread: wbia_main (#693512346)] [Type: Warning] [MsgID: 14212] [Mesg: Connector Controller property ControllerTraceLevel value in the local configuration file will be ignored.]
[Thread: wbia_main (#693512346)] [Type: Internal Warning] [MsgID: 14212] [Mesg: Connector Controller property ControllerStoreAndForwardMode value in the local configuration file will be ignored.]
2346)] [Mesg: Privacy is NOT initialized. Reason: The privacy is NOT turned on.]
[Thread: wbia_main (#693512346)] [Type: Trace] [Mesg: Using protocol IIOP to get the metadata. ]
[Thread: wbia_main (#693512346)] [Mesg: getController called]
[Thread: wbia_main (#693512346)] [Mesg: Binding to WINICS]
[Thread: wbia_main (#693512346)] [Mesg: [Type: Info] [MsgID: 17021] [Mesg: No response from connector controller. It is probably not running yet. Reason: WebSphereMQ. Retrying...] ]
[Thread: wbia_main (#693512346)] [Mesg: Binding to WINICS]
[Thread: wbia_main (#693512346)] [Mesg: [Type: Info] [MsgID: 17021] [Mesg: No response from connector controller. It is probably not running yet. Reason: WebSphereMQ. Retrying...] ] |
|
| Back to top |
|
 |
| vennela |
| Posted: Wed Jul 06, 2005 8:58 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
The usual way of starting the adapter is
start_WebSphereMQ WebSphereMQ ICSServer -c"Full path of ConfigFile".
Also, did you configure the required meta objects? |
|
| Back to top |
|
|
| RocknRambo |
| Posted: Wed Jul 06, 2005 1:38 pm Post subject: |
|
|
Partisan
Joined: 24 Sep 2003
Posts: 355
|
to Check whether u have loaded all the MetaBO's.. try running it in standalone Mode...
-RR |
|
| Back to top |
|
|
| djeripo |
| Posted: Wed Jul 06, 2005 7:54 pm Post subject: |
|
|
Master
Joined: 25 Jan 2004
Posts: 225
|
| Quote: |
| [Thread: wbia_main (#693512346)] [Mesg: [Type: Info] [MsgID: 17021] [Mesg: No response from connector controller. It is probably not running yet. Reason: WebSphereMQ. Retrying...] ] |
Start your connector controller. |
|
| Back to top |
|
|
| NSJ |
| Posted: Wed Jul 06, 2005 9:13 pm Post subject: |
|
|
Novice
Joined: 06 Jul 2005
Posts: 12
|
Thank you all for posting the replies i was half expecting help on ICS as there are less people working on ICS as compared to Message Broker.
I am running the connector by giving the path to the config file.
..\WebSphereMQ\start_WebSphereMQ.bat WebSphereMQ WINICS -cC:\IBM\MQConnector.cfg.
I use the same configuration file to run the Visual Test Connector(Is this what you mean by standalone mode?) which is able to bind to the connector correctly and i am able to pass business objects.
I am running this on Windows XP professional and i am using IDL as the transport.You may be right about the Meta objects.I have the Following Business Object:
(1) CUST Simple business object.Four Attributes all string with one Key
(2)WebSphereMQ_MO_Config
This has for Four attributes:
(a) Default-- This has value InputQueue=queue://ICSQM/CUST.IN;OutputQueue=queue://ICSQM/CUST.OUT;DataEncoding=Text
(b) CUST_Update value InputFormat=CUST;OutputFormat=CUST
(c) CUST_Delete value InputFormat=CUST;OutputFormat=CUST
(d) CUST_Create value InputFormat=CUST;OutputFormat=CUST
I have defined the queues in MQ.
(3)WebSphereMQ_MO_DataHandler_DelimitedConfig which has the following attributes.
(a) CxIgnore value CxIgnore
(b) CxBlank value CxBlank
(c) Delimiter value ;
(d) Escape value \
(e) Class value com.crossworlds.DataHandlers.text.delimited
(f) DummyKey value 1
(4)WebSphereMQ_MO_DataHandler .This has only one attribute which is a Child Metaobject of type WebSphereMQ_MO_DataHandler_DelimitedConfig
The connector controller is shown as running in the System Manager view. And i can connect it using the Test connector. Is there anything else that needs to be explicitly started.
Please let me know if you need any more information.
Thanks
NSJ |
|
| Back to top |
|
|
| vennela |
| Posted: Thu Jul 07, 2005 7:13 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
You should turn on the agent trace (maybe 4 or 5) and then start your agent and see what errors are being logged. If you can't figure out e-mail me the trace and I can take a look at it.
If you are using VTC, then your connector speicific properties and datahandlers will be ignored I guess. That also localizes the problem that the error is with either connector specific propertis or datahandlers.
I have not messed a lot with DataHandlers, but last I configured WMQ adapter, I added all the datahandlers to the connector that were under the DataHandlers directory. For me it is
C:\IBM\WebSphereICS\DataHandlers\repository\DataHandlers
Most likely you might have not created all the queues. If you did, check the caps/lowercase. |
|
| Back to top |
|
|
| NSJ |
| Posted: Thu Jul 07, 2005 10:25 am Post subject: |
|
|
Novice
Joined: 06 Jul 2005
Posts: 12
|
Hi All
Thanks for all the replies. I finally figured out the problem.It was to do with the mismatch of the connector name.In the startup script the -n option is the name of the connector instance.In my case my start up script was:
...............
..\webSphereAdapters\bin\start_adapter" -nWebSphereMQ -sWINICS -lcom.crossworlds.connectors.WebSphereMQ.ConnectorAgent -cC:\IBM\MQConnector.cfg
Whereas my connector name was WebSphereMQConnector.
There is another property in the conector configurator called "Application Name"(what is it actually used for??) i had set the value in that property as 'WebSphereMQ'.
When i first used the Visual Test Connector while configuring the profile for connection i specified the connector name as WebSphereMQConnector therefore i was able to bind. When i was running the connector using the startup script the name in the -n option was being searched by the agent hence it was not able to connect.
I thank you all again for the help .
NSJ |
|
| Back to top |
|
|
| Ratan |
| Posted: Thu Jul 07, 2005 12:30 pm Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
| Quote: |
| There is another property in the conector configurator called "Application Name"(what is it actually used for??) i had set the value in that property as 'WebSphereMQ'. |
That is the name of your connector.
The fact that adding 'Connector' to 'WebSphereMQ' looks wierd to me.
My connector names are usually XYZConnector and I use the Connector name as XYZ on my adapter startup script.
What version are you on?
_________________
-Ratan |
|
| Back to top |
|
|
| RocknRambo |
| Posted: Thu Jul 07, 2005 12:57 pm Post subject: |
|
|
Partisan
Joined: 24 Sep 2003
Posts: 355
|
This is the of the change in V4.3 of ICS from previous version..
the start up scripts for the Adapter have been updated. now, the word "connector" is NOT by default. |
|
| Back to top |
|
|
| recallsunny |
| Posted: Thu Jul 07, 2005 1:25 pm Post subject: |
|
|
Disciple
Joined: 15 Jun 2005
Posts: 163
Location: Massachusetts
|
What NSJ has noticed might sound ridiculous but that is what exactly occured with me too. The new startup scripts shipped with latest version of Adapter framework seem to be missing the Keyword "Connector" in the Exec command. And this is also random with the type of adapters you use, The last i know of: JText and MQ contain this bug.
I did not look at this post till now or else I could have saved some trouble for NSJ, it took about half a day for me to figure out this problem when I upgraded my ICS.
Another piece of Info which might save time for people configuring adapters with Message Broker: If you are configuring the above adapters for Message broker the error you would see is: " No Meta Objects subscribed! The connector won't be able to process any BOs...!! Please subscribe some MOs and restart connector". If you see this message please do check the startup scripts for the above mentioned bug
Cheers  |
|
| Back to top |
|
|
| RocknRambo |
| Posted: Thu Jul 07, 2005 1:34 pm Post subject: |
|
|
Partisan
Joined: 24 Sep 2003
Posts: 355
|
| Quote: |
| recallsunny - The last i know of: JText and MQ contain this bug. |
I'm not sure .. u call it as a bug, as I found this as interesting.. as no point in appending the word "connector" for each instance u create.
btw.. this is all in adapters I believe, we have JDBC, PSFT, SAP, EMAIL
-RR |
|
| Back to top |
|
|
| djeripo |
| Posted: Thu Jul 07, 2005 4:58 pm Post subject: |
|
|
Master
Joined: 25 Jan 2004
Posts: 225
|
| Quote: |
| Another piece of Info which might save time for people configuring adapters with Message Broker: If you are configuring the above adapters for Message broker the error you would see is: " No Meta Objects subscribed! The connector won't be able to process any BOs...!! Please subscribe some MOs and restart connector". If you see this message please do check the startup scripts for the above mentioned bug |
This error shows up in the connector log file when you try to start a JText Connector.
| Quote: |
# Call the base start_adapter.sh to start the connector
exec start_adapter.sh ${CONNECTOR_TYPE}${CONNECTOR_AGENT} -n${CONNAME} -s${SERVER} ${CON_START_OPTIONS} $3 $4 |
The fix for the above problem would be to add the word 'Connector' after
{CONNAME}
Is there any relation between the error it throws and the fix you have?
| Quote: |
| I'm not sure .. u call it as a bug, as I found this as interesting.. as no point in appending the word "connector" for each instance u create |
Some people think it as an interesting phenomenon which IBM has improvised which keeps you engaged biting your nails until a PMR person from China comes after 48 hours and says this is the fix. |
|
| Back to top |
|
|
| jefflowrey |
| Posted: Fri Jul 08, 2005 3:31 am Post subject: |
|
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
| djeripo wrote: |
| Some people think it as an interesting phenomenon which IBM has improvised which keeps you engaged biting your nails until a PMR person from China comes after 48 hours and says this is the fix. |
Only 48 hours?
I waited three days for no response to a sev1 production is down ticket against Process Choreographer in a WAS cluster.
And resolved the problem myself.
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
|
| djeripo |
| Posted: Fri Jul 08, 2005 9:47 pm Post subject: |
|
|
Master
Joined: 25 Jan 2004
Posts: 225
|
| I was lucky enough to get such an express response for that case.I have one other PMR opened for the WebServices adapter 3.4.2 .It has been more than 3 weeks with sev.2 .It kept swaying all accross the globe but no solution yet.'DUNCAN' ,are you hearing ICS Help whinings?Yet again the old request,ICS Forum please. |
|
| Back to top |
|
|
| PeterPotkay |
| Posted: Sat Jul 09, 2005 7:23 am Post subject: |
|
|
Poobah
Joined: 15 May 2001
Posts: 7722
|
| jefflowrey wrote: |
| djeripo wrote: |
| Some people think it as an interesting phenomenon which IBM has improvised which keeps you engaged biting your nails until a PMR person from China comes after 48 hours and says this is the fix. |
Only 48 hours?
I waited three days for no response to a sev1 production is down ticket against Process Choreographer in a WAS cluster.
And resolved the problem myself. |
After 4 hours of no response on a Sev1 Production down ticket against a plain Windows Queue Maanger of all things, we finally call and are told "We have to wait for the tech in India to wake up and drive in".
We then proceeded with the shotgun approach of trying anything and everything, and resolved the problem ourselves.
We made our displeasure known. Hopefully it won't happen again.
_________________
Peter Potkay
Keep Calm and MQ On |
|
| Back to top |
|
|
|
|
