| Author |
Message
|
| rscher |
 Posted: Fri Jun 06, 2003 12:16 am Post subject: MQWf 3.4 Web-client with WebLogic |
 |
|
Newbie
Joined: 05 Mar 2003
Posts: 2
Location: Walnut Creek, CA
|
We have tried to deploy the MQWf 3.4 Web-client EAR/WAR files
within BEA WebLogic App Server. It gives a Workflow API error after authenticating the login. Has anybody successfully done this with BEA or any other app server outside of WAS ?
IBM will not comment on this. |
|
| Back to top |
|
 |
| Ratan |
| Posted: Fri Jun 06, 2003 8:41 am Post subject: |
|
|
Grand Master
Joined: 18 Jul 2002
Posts: 1245
|
| Quote: |
Has anybody successfully done this with BEA or any other app server outside of WAS ?
|
I believe people said they succesfully deployed webclient on other Application servers in this forum. Search this forum, might be helpful.
_________________
-Ratan |
|
| Back to top |
|
|
| jet |
| Posted: Tue Jun 10, 2003 7:59 am Post subject: |
|
|
Apprentice
Joined: 04 Dec 2002
Posts: 49
Location: New York
|
Did u add the MQWF java Agent jar file to the runtime classpath in weblogic?
What exactly the API errors are? wat is the error messages? |
|
| Back to top |
|
|
| rscher |
| Posted: Tue Jun 10, 2003 10:47 pm Post subject: MQWf 3.4 Web-client with WebLogic 8.1b failure |
|
|
Newbie
Joined: 05 Mar 2003
Posts: 2
Location: Walnut Creek, CA
|
Yes we deployed the jar file into WebLogic 8.1b correctly ...
it brings up the Web Client logon, but when trying to authenticate the ADMIN user, it fails.
Perhaps we need to modify the WebClient.properties file for WebLogic ?
Here's the WebLogic console error:
<Jun 10, 2003 11:33:39 PM PDT> <Error> <HTTP> <BEA-101046> <[ServletContext(id=1
6348303,name=/MQWFClient-EC01,context-path=/MQWFClient-EC01)] IllegalStateExcept
ion caught: Stopped processing request to avoid loop
java.lang.IllegalStateException: Document root not initialized
at com.ibm.workflow.servlet.client.ApplicationContextImpl.getDocumentRoo
t(Unknown Source)
at com.ibm.workflow.servlet.client.Main.sendResponse(Unknown Source)
at com.ibm.workflow.servlet.client.Main.doGet(Unknown Source)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:740)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:853)
at weblogic.servlet.internal.ServletStubImpl$ServletInvocationAction.run
(ServletStubImpl.java:1047)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:383)
at weblogic.servlet.internal.ServletStubImpl.invokeServlet(ServletStubIm
pl.java:301)
at weblogic.servlet.internal.WebAppServletContext$ServletInvocationActio
n.run(WebAppServletContext.java:6319)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(Authenticate
dSubject.java:317)
at weblogic.security.service.SecurityManager.contact admin(SecurityManager.java:
97)
at weblogic.servlet.internal.WebAppServletContext.invokeServlet(WebAppSe
rvletContext.java:3525)
at weblogic.servlet.internal.ServletRequestImpl.execute(ServletRequestIm
pl.java:2553)
at weblogic.kernel.ExecuteThread.execute(ExecuteThread.java:178)
at weblogic.kernel.ExecuteThread.run(ExecuteThread.java:151)
> |
|
| Back to top |
|
|
| jet |
| Posted: Wed Jun 11, 2003 1:32 pm Post subject: |
|
|
Apprentice
Joined: 04 Dec 2002
Posts: 49
Location: New York
|
| Yeah, I will think you need to modify the webclient properties file. The Webclient EAR file was developed using WebSphere. I dont think that both of Websphere and Weblogic implement the same J2EE spec exactly the same. |
|
| Back to top |
|
|
|
|
