| Author |
Message
|
| tsrisudh |
 Posted: Fri Dec 16, 2005 3:25 am Post subject: [SOLVED]Java and Client Communication |
 |
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
Hi have made the folowing setup
Windows box 1 :
Win2K
MQ 5.3
MQWF 3.6
DB28.2
Windows box 2:
MQ 5.3 Client
MQWF 3.6 client components and java
I copies the MQWFCHL.tab file from server and put it in the client machine and then created the configuration in the client machine with the default values.
I opened the MQWF Runtime client and it connected properly to the server and showed me all the work items
I ran the admin utility and that too logged in properly
Now i wrote a sample java program to connect to workflow
| Code: |
Agent agent = new Agent();
agent.setLocator(Agent.LOC_LOCATOR);
agent.setName("MyAgent");
service = agent.locate("FMCGRP", "FMCSYS");
service.logon2( "ADMIN", "password", SessionMode.PRESENT_HERE,
AbsenceIndicator.LEAVE);
|
This throws the follwoing error
| Code: |
FMC38009E MQSeries Workflow API Error :
API Return Code : 13
Error Origin : FmcSession.java:460
Error Message : FMC00013E Communication error - Failing Action: connect, Reason Code: 2059, Failing Object: FMCQM.
Nested Exception : None
at com.ibm.workflow.client.api.FmcSession.CallSync(FmcSession.java:460)
at com.ibm.workflow.client.api.FmcSession.Logon(FmcSession.java:953)
at com.ibm.workflow.client.api.FmcExecutionService.logon2(FmcExecutionService.java:798)
at com.mdb.test.GetWorkListSample.getWorkItems(GetWorkListSample.java:58)
at com.mdb.test.GetWorkListSample.main(GetWorkListSample.java:31)
|
Doing some search on the MQ forums, i tried the follwint
SET MQSERVER
and amqputc
and it worked fine
I have also checked that the config name, system, group and queue name are the same as the server and also the port name
Also checked in the environment variable that it is set to MQClient
I need urgent help as to why i am getting this error from Java code?
_________________
Srisudhir Tadepalli
Last edited by tsrisudh on Sat Dec 17, 2005 1:48 am; edited 1 time in total |
|
| Back to top |
|
 |
| jmac |
| Posted: Fri Dec 16, 2005 5:16 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
I see you are running 3.6. Are you using the Native Java API or the classic API. If you are using the Native Java API did you set the fmcrc file properly?
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| tsrisudh |
| Posted: Fri Dec 16, 2005 5:19 am Post subject: |
|
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
I have no idea which one i am using, how do i find it out?
And i also have no idea as to where and how do i set the fmcrc file property
Help 
_________________
Srisudhir Tadepalli |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Dec 16, 2005 5:26 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Which jar file is in your classpath?
Native Java API is fmcjapi.jar
Classic API is fmcojagt.jar or fmcojapi.jar.
Use of fmcrc file is documented in install guide and possibly programming guide
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| tsrisudh |
| Posted: Fri Dec 16, 2005 6:43 am Post subject: |
|
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
i am using Native java API.
I am little confused with fmcrc, how can i include it in the classpath in WSAD
i tried to put it in lib but it did not work
i made it into a jar file
but still no luck
One more question, should i give the Queue manager name same as that of the server or different while configuring the mqwf client
Here is the fmcrc file
| Code: |
Configuration/FMC/ConfiguredComponents=ARUK
Configuration/FMC/SystemGroup=FMCGRP
Configuration/FMC/System=FMCSYS
Configuration/FMC/MQPrefix=FMC
Configuration/FMC/MQQueueManager=FMCQM
Configuration/FMC/MQConnectionType=MQClient
Configuration/FMC/FMLClientChannelTable=e:\\program files\\ibm\\websphere mq workflow\\chltabs\\mqwfchl.tab
Configuration/FMC/FMLConnectName=FMC.FMCGRP.FMCSYS,FMCQM
Configuration/FMC/FMLSegmentation=0
Configuration/FMC/RTIconDirectory=e:\\program files\\ibm\\websphere mq workflow\\bin\\iconinst
Configuration/FMC/MQCommunicationAddress=test4
Configuration/FMC/MQPort=5010
|
test 4 is my client machine
_________________
Srisudhir Tadepalli |
|
| Back to top |
|
|
| tsrisudh |
| Posted: Fri Dec 16, 2005 9:53 pm Post subject: |
|
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
Any help on this issue?
_________________
Srisudhir Tadepalli |
|
| Back to top |
|
|
| vennela |
| Posted: Sat Dec 17, 2005 12:41 am Post subject: |
|
|
Jedi Knight
Joined: 11 Aug 2002
Posts: 4055
Location: Hyderabad, India
|
can you run fmczccd on the client machine and post the results.
Also fmczchk -y ConfigID
fmczccd -y ConfigId
Both on the client machine.
| Quote: |
| One more question, should i give the Queue manager name same as that of the server or different while configuring the mqwf client |
Same as the server. |
|
| Back to top |
|
|
| tsrisudh |
| Posted: Sat Dec 17, 2005 1:02 am Post subject: |
|
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
Here is the output
The channel table in the profile is: e:\program files\ibm\websphere mq workflow\
chltabs\mqwfchl.tab
The connect name found in the profile : FMC.FMCGRP.FMCSYS,FMCQM
The channel table exists.
The current user has read access to channel table file.
The channel table contains the following information:
Queue manager : FMCQM
Protocol : TCP/IP
Connection name : specstest1(5010)
TCP/IP-addr : specstest1
TCP-Port : 5010
Status : ok
---------------------
Queue manager : FMCQM
Protocol : TCP/IP
Connection name : specstest1(5010)
TCP/IP-addr : specstest1
TCP-Port : 5010
Status : ok
---------------------
You are using the MQSeries Client API for the queue manager communication.
Checking system identifier FMC.FMCGRP.FMCSYS,FMCQM .
Ping to server specstest1 was successful.
Connecting to the queue manager FMCQM was successful.
There are no checks with this utility to verify that the MQSeries Workflow Serve
r is running on your server.
Fmczchk output
C:\Documents and Settings\Administrator>fmczchk -y FMC
FMC34010I: Configuration checker version 3.6.0.118 started.
FMC34012I: ===> General checks.
FMC34011I: Performing WebSphere MQ Workflow Version 3.6.0 checks.
FMC34014I: ===> Admin Server (fmcamain.exe) is not installed.
FMC34014I: ===> Server message device (fmccdfms.dll) is not installed.
FMC34014I: ===> Execution Server (fmcemain.exe) is not installed.
FMC34013I: ===> Client message layer (server API) found, checks started.
FMC34013I: ===> Client message layer (client API) found, checks started.
FMC34013I: ===> WebSphere MQ Workflow C/C++ API found, checks started.
FMC34013I: ===> Java API found, checks started.
FMC34014I: ===> Buildtime (fmcbmain.exe) is not installed.
FMC34013I: ===> Runtime Client found, checks started.
FMC34100I: Messages have been written to c:\documents and settings\administrator
\fmczchk.log.
FMC34999I: Configuration checker ended: 0 error(s), 0 warning(s), rc = 0.
_________________
Srisudhir Tadepalli |
|
| Back to top |
|
|
| tsrisudh |
| Posted: Sat Dec 17, 2005 1:50 am Post subject: |
|
|
Centurion
Joined: 11 Aug 2005
Posts: 113
|
Finally solved it, the fmcrc file which gets generated put the local machine name in the MQConnectionName, but this has to be manually changed to the MQWorkflow server name.
The runtime client was working because it uses the mqwfchl.tab details to log in, Java uses the values in the fmcrc file and that wa the problem.
Thanks jmac for pointing to the correct place to look for
_________________
Srisudhir Tadepalli |
|
| Back to top |
|
|
|
|
