| Author |
Message
|
| mrlazy |
 Posted: Wed Jul 12, 2006 10:32 am Post subject: Custom web client not working properly |
 |
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Hi all,
I need somone's help badly.
Recently, I installed MQ WorkFlow V 3.6 on AIX 5.3 and MQ Workflow Web Client v 3.6 on AIX 5.2. The default configuration was working fine. We were able to deploy the ear file generated during installation and every thing looked fine(as given in the IBM document).
But one of my colleagues has given me a new ear file (custom client) to deploy on to the WebSphere Application Server 6. We made the two jar files 'fmcochli.jar & fmcjapi.jar' as shared libraries and deployes, but something seems to be wrong. This is the error msg being displayed in the log file:
2006-07-12 15:35:03.27 SoapConnectorThreadPool : 2: Binding agent 'MQWFAGENT' for FMC
2006-07-12 15:35:03.117 SoapConnectorThreadPool : 2: Get configuration of default agent failed: FMC
2006-07-12 15:38:51.725 Thread-1: Binding agent 'MQWFAGENT' for FMC
2006-07-12 15:38:51.810 Thread-1: Get configuration of default agent failed: FMC
2006-07-12 15:39:14.236 WebContainer : 0: Charset for en is ISO-8859-1
Someone kindly help me soving this issue.
Thanks every one. |
|
| Back to top |
|
 |
| jmac |
| Posted: Wed Jul 12, 2006 11:15 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
It seems that maybe the fmcrc file can not be located.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| mrlazy |
| Posted: Wed Jul 12, 2006 11:28 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Thanks for you reply.
Could you please tell me where exactly should I check and make sure that the fmcrc file is accessible? |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Jul 12, 2006 11:45 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
It has to be accessible in the classpath... Look at the Install doc and it should help
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| mrlazy |
| Posted: Wed Jul 12, 2006 12:08 pm Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
But jmac, I beilieve the fmcrc file is embedded in the 'ear' file itself. I did a search and found that both the default client and custom client have 'fmcrc' packed in the ear file.
Default Ear file: /fmcohcli.war/WEB-INF/classes/fmcrc
Custom Ear file: /MQWFClient-Custom.war/WEB-INF/classes/fmcrc
I also did:
$ set $CLASSPATH=/usr/lpp/fmc/bin/fmcjapi.jar
$ export $CLASSPATH
But still get the same error. Before I go further, I would like to ask you one basic thing. Do I need to make any additional changes before the custom cleitn is deployed?Because my colleague who gave teh new ear file said that nothing else should be made, ubt deploy the ear file. The only thing to take care is the two jar files generated during installation : 'fmcochli.jar & fmcjapi.jar' should be assigned as shared libraries. |
|
| Back to top |
|
|
| jmac |
| Posted: Wed Jul 12, 2006 12:17 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
I believe you need to look at this custom application and see what configuration it is using. the fact that this message
2006-07-12 15:38:51.810 Thread-1: Get configuration of default agent failed: FMC
is displayed leads me to believe that there is some issue in the fmcrc file being used.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| hos |
| Posted: Wed Jul 12, 2006 11:20 pm Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
| In J2EE resource bundles need to be located in the CLASSPATH of the class loader that loads the class that loads the resource. If you define the jar files to be shared libraries you change their class loader. Make yourself familiar with the class loader hierarchy of an AppServer architecture. |
|
| Back to top |
|
|
| mrlazy |
| Posted: Thu Jul 13, 2006 7:39 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Hi,
I have declared the java api jar file(fmcjapi.jar) and other MQ JMS files (com.ibm.mq.jar etc) in the $CLASSPATH variable. But as said by jmac, when I noticed the 'fmcrc' files in the 'default ear file' and the 'custom ear file', I see a difference.
Default ear file's fmcrc:
Configuration/WC/DefaultConfigurationID=WebClient
Configuration/WC/FMLConnectName=FMC.FMCGRP.FMCSYS,WCQM
Configuration/WC/MQCommunicationAddress=App-Server
Configuration/WC/MQConnectionType=MQServer
Configuration/WC/MQPort=5010
Configuration/WC/MQQueueManager=WCQM
Configuration/WC/SystemGroup=FMCGRP
Custom ear file's fmcrc:
Configuration/DefaultConfigurationID=FMC
Is this the reason why it shows in the log file:
Get configuration of default agent failed: FMC?
Thanks for your help. |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Jul 13, 2006 8:28 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
| mrlazy wrote: |
Is this the reason why it shows in the log file:
Get configuration of default agent failed: FMC? |
That would be my guess
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| mrlazy |
| Posted: Thu Jul 13, 2006 12:12 pm Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Hi,
Even after changing the fmcrc file to exactly same as the one defined in the default ear file, we get the same error.
Here are the websphere system logs when started this application. Hope this might be helpful for someone to help me in troubleshooting this problem:
[7/13/06 14:48:08:979 CDT] 0000000a ApplicationMg A WSVR0200I: Starting application: MQWFClient
[7/13/06 14:48:09:181 CDT] 0000000a WebGroup A SRVE0169I: Loading Web Module: MQWFClient-Custom.
[7/13/06 14:48:09:766 CDT] 0000000a WebApp A SRVE0180I: [MQWFClient-Custom] [/MQWFClient-Custom] [Servlet.LOG]: Get configuration of default agent failed: FMC
[7/13/06 14:48:09:784 CDT] 0000000a WebExtensionP W Servlet Main is currently unavailable: Could.not.load.Web.Application
[7/13/06 14:48:09:803 CDT] 0000000a WebExtensionP E SRVE0026E: [Servlet Error]-[javax.servlet.UnavailableException: Could.not.load.Web.Application
at com.ibm.workflow.servlet.client.ApplicationContextImpl.<init>(ApplicationContextImpl.java:99)
at com.ibm.workflow.servlet.client.Main.init(Main.java:66)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.init(ServletWrapper.java:274)
at com.ibm.ws.webcontainer.servlet.ServletWrapper.initialize(ServletWrapper.java:1398)
at com.ibm.wsspi.webcontainer.extension.WebExtensionProcessor.createServletWrapper(WebExtensionProcessor.java:86)
at com.ibm.ws.webcontainer.webapp.WebApp.getServletWrapper(WebApp.java:763)
at com.ibm.ws.webcontainer.webapp.WebApp.initializeTargetMappings(WebApp.java:506)
at com.ibm.ws.webcontainer.webapp.WebApp.initialize(WebApp.java:395)
at com.ibm.ws.webcontainer.webapp.WebGroup.addWebApplication(WebGroup.java:115)
at com.ibm.ws.webcontainer.VirtualHost.addWebApplication(VirtualHost.java:128)
at com.ibm.ws.webcontainer.WebContainer.addWebApp(WebContainer.java:905)
at com.ibm.ws.webcontainer.WebContainer.addWebApplication(WebContainer.java:858)
at com.ibm.ws.runtime.component.WebContainerImpl.install(WebContainerImpl.java:167)
at com.ibm.ws.runtime.component.WebContainerImpl.start(WebContainerImpl.java:391)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:1228)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.fireDeployedObjectStart(DeployedApplicationImpl.java:1067)
at com.ibm.ws.runtime.component.DeployedModuleImpl.start(DeployedModuleImpl.java:547)
at com.ibm.ws.runtime.component.DeployedApplicationImpl.start(DeployedApplicationImpl.java:751)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplication(ApplicationMgrImpl.java:892)
at com.ibm.ws.runtime.component.ApplicationMgrImpl$AppInitializer.run(ApplicationMgrImpl.java:2003)
at com.ibm.ws.runtime.component.ComponentImpl.contact admin(ComponentImpl.java:159)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.startApplications(ApplicationMgrImpl.java:745)
at com.ibm.ws.runtime.component.ApplicationMgrImpl.start(ApplicationMgrImpl.java:524)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
at com.ibm.ws.runtime.component.ApplicationServerImpl.start(ApplicationServerImpl.java:149)
at com.ibm.ws.runtime.component.ContainerImpl.startComponents(ContainerImpl.java:820)
at com.ibm.ws.runtime.component.ContainerImpl.start(ContainerImpl.java:649)
at com.ibm.ws.runtime.component.ServerImpl.start(ServerImpl.java:406)
at com.ibm.ws.runtime.WsServerImpl.bootServerContainer(WsServerImpl.java:187)
at com.ibm.ws.runtime.WsServerImpl.start(WsServerImpl.java:133)
at com.ibm.ws.runtime.WsServerImpl.main(WsServerImpl.java:387)
at com.ibm.ws.runtime.WsServer.main(WsServer.java:53)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:85)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:5
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:60)
at java.lang.reflect.Method.invoke(Method.java:391)
at com.ibm.ws.bootstrap.WSLauncher.run(WSLauncher.java:219)
at java.lang.Thread.run(Thread.java:568)
]: {1}
Kindly help me out... |
|
| Back to top |
|
|
| hos |
| Posted: Fri Jul 14, 2006 12:35 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Hi,
the fmcrc file that comes with the ear is a 'summary' of all web configurations
known to fmczutil. When you make a configuration FMC with fmczutil on
box 1 the resulting ear file will contain a profile with configurationID FMC. When you make a different configuration WebClient on box2 , the ear's profile will contain an entry WebClient, but not FMC.
You can't share neither the ear file of box1 nor the one of box2. Because both contain only one configuratioID. You have to create both configurationIDs on the same client installation in a single ear file. The Installation Guide has a chapter how to setup the WebClient to support multiple configurations. |
|
| Back to top |
|
|
| mrlazy |
| Posted: Fri Jul 14, 2006 6:43 am Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
Thanks for your reply hos,
Yes, we do have different configurations on different boxes. Box 1 'FMC'(config id), is the server and box 2 'WC'(config id), is the web client. The default 'fmcrc' file on box 2 has information about the WC. This default web client is working perfectly fine. All I was trying to do is to deploy a custom client on box 2 (given by my lead.)
Since the error message says 'Get configuration of default agent failed: FMC', when noticed in the 'fmcrc' file of the custom ear, I noticed that it is referring to 'FMC', not 'WC' like in default client's fmcrc. So we changed the 'fmcrc' of custom client ear to be same as that of default client. But seeing the error that I posted before it seems like the main servlet itself is not loading properly, which i guess is the java application is unable to find the 'fmcjapi.jar' file or something like that.
If this is not the case, please advise me what elkse can be wrong? |
|
| Back to top |
|
|
| mrlazy |
| Posted: Fri Jul 14, 2006 1:16 pm Post subject: |
|
|
Centurion
Joined: 19 Apr 2006
Posts: 144
|
The problem is solved now.
Thanks a lot for your help guys.
 |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Jul 14, 2006 1:31 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
What did you do to solve the problem?
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
