Livecycle ES 8.2 Form Java API question - Adobe Livecyle ES running in Weblogic 9.2

[Former Community Member]

not sure what forum to post this message in, so I will try here. Hopefully, someone can either assist me with the question, or point me to a better location to post. We are using the Java API (via EJB) to communicate with our Adobe Livecycle ES server (8.2). We only have two services installed (Forms and Output service) on our server. Our Adobe server environment is Solaris 10 and Weblogic 9.2. I am running a sample client app to make the calls to the adobe livecycle server. I am running my sample app in Jboss (the same server that comes with the turnkey install). I intially tested my sample app communicating with my local turnkey install (same JBOSS - so my client app and the adobe livecycle server were running on the same machine and were local to each other). everything was working perfect. then I tried to connect my same client app (running in jboss) to our remote adobe livecyle es server (again, weblogic running on solaris). I am getting a completely useless error in the jboss logs (see below). Here is a list of my jar files in my classpath:

adobe-forms-client.jar

adobe-livecycle-client.jar

adobe-output-client.jar

adobe-usermanager-client.jar

adobe-utilities.jar (weblogic specific)

wlclient.jar

I am not really sure what else I need to do to get my client app to remotely connect via EJB to our Adobe Livecycle ES server.

I have the following connection info:



Properties connectionProps = new Properties();

connectionProps.setProperty(ServiceClientFactoryProperties.DSC_DEFAULT_EJB_ENDPOINT, "t3://182.11.44.222:7001");

connectionProps.setProperty(ServiceClientFactoryProperties.DSC_SERVER_TYPE, ServiceClientFactoryProperties.DSC_WEBLOGIC_SERVER_TYPE);

connectionProps.setProperty(ServiceClientFactoryProperties.DSC_TRANSPORT_PROTOCOL,ServiceClientFactoryProperties.DSC_EJB_PROTOCOL);

connectionProps.setProperty("DSC_CREDENTIAL_USERNAME", "tester1");

connectionProps.setProperty("DSC_CREDENTIAL_PASSWORD", "testerpswd");

ServiceClientFactory adobeServiceClient = ServiceClientFactory.createInstance(connectionProps);



just below is my error from the server.log ....I have pretty much no idea where to go from here. I know that I have a classpath issue (although, I am not sure why I didn't have the same problem when connecting to the jboss adobe livecycle server). I also wasn't able to locate this class in question (org/apache/log/format/Formatter) in any of the adobe jar files. I tried dropping in logkit.jar in my classpath, but still didn't work. Any help would be greatly appreciated:



thanks



regards,

jp



2008-08-27 15:48:58,542 INFO [STDOUT] java.lang.NoClassDefFoundError: org/apache/log/format/Formatter

2008-08-27 15:48:58,542 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.ejb.EjbMessageDispatcher.doSend(EjbMessageDispatcher.java:163)

2008-08-27 15:48:58,542 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispatcher.java:57)

2008-08-27 15:48:58,542 INFO [STDOUT] at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)

2008-08-27 15:48:58,542 INFO [STDOUT] at com.adobe.livecycle.formsservice.client.FormsServiceClient.invokeRequest(FormsServiceClient.java:429)

2008-08-27 15:48:58,542 INFO [STDOUT] at com.adobe.livecycle.formsservice.client.FormsServiceClient.renderHTMLForm(FormsServiceClient.java:125)

2008-08-27 15:48:58,542 INFO [STDOUT] at com.adobe.livecycle.forms.RenderHTMLForms.doPost(RenderHTMLForms.java:32)

2008-08-27 15:48:58,542 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)

2008-08-27 15:48:58,542 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)

2008-08-27 15:48:58,542 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)

2008-08-27 15:48:58,542 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)

2008-08-2

[chetanm_oct]

The class mentioned above is from logkit.jar which is used by Weblogic also. So it may be happening that the EJB response sent by Weblogic is referring to some logkit classes.



Is there any exception stack trace logged on weblogic server side?



Also can you try the same with SOAP protocol

[Former Community Member]

chetan,<br /><br />thanks for the reply. I took the logkit.jar from the weblogic directory (C:\bea92mp3\weblogic92\server\lib\logkit) and had to place it in the jboss server lib directory (C:\Adobe\LiveCycle8.2\jboss\server\all\lib) which is where my client app is running. even though i have weblogic installed locally, I am trying to connect to a remote solaris box running weblogic - this is our adobe livecycle es server. Now I get the following error. Is there something else I need to do in order to get my client app to make a remote ejb call? I know that I am missing something big here, I just have no idea what it is.<br /><br />also, I am bit reluctant to use the soap as we are running a strictly Java environment, and I don't want to have to deal with the web service proxy classes (and the overhead, performance hit, with soap).<br /><br />thanks again<br /><br />regards,<br />jp<br />2008-08-28 10:26:07,765 INFO [STDOUT] com.adobe.livecycle.formsservice.exception.RenderFormException: ALC-DSC-031-000: com.adobe.idp.dsc.net.DSCNamingException: Remote EJBObject lookup failed for ejb/Invocation provider<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.livecycle.formsservice.client.FormsServiceClient.renderHTMLForm(FormsServiceClient.java:142)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.livecycle.forms.RenderHTMLForms.doPost(RenderHTMLForms.java:32)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at java.lang.Thread.run(Thread.java:595)<br />2008-08-28 10:26:07,765 INFO [STDOUT] Caused by: ALC-DSC-031-000: com.adobe.idp.dsc.net.DSCNamingException: Remote EJBObject lookup failed for ejb/Invocation provider<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.ejb.EjbMessageDispatcher.initialise(EjbMessageDispatcher.java:97)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.ejb.EjbMessageDispatcher.doSend(EjbMessageDispatcher.java:130)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispatcher.java:57)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.livecycle.formsservice.client.FormsServiceClient.invokeRequest(FormsServiceClient.java:429)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.livecycle.formsservice.client.FormsServiceClient.renderHTMLForm(FormsServiceClient.java:125)<br />2008-08-28 10:26:07,780 INFO [STDOUT] ... 22 more<br />2008-08-28 10:26:07,780 INFO [STDOUT] Caused by: javax.naming.InvalidNameException: Couldn't resolve initial reference: NameService [Root exception is org.omg.CORBA.ORBPackage.InvalidName]<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:52)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:574)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:534)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:85)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:31)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at javax.naming.InitialContext.init(InitialContext.java:223)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at javax.naming.InitialContext.<init>(InitialContext.java:197)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.ejb.EjbMessageDispatcher.initJndiContext(EjbMessageDispatcher.java:213)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.ejb.EjbMessageDispatcher.getJndiContext(EjbMessageDispatcher.java:226)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.ejb.EjbMessageDispatcher.initialise(EjbMessageDispatcher.java:87)<br />2008-08-28 10:26:07,780 INFO [STDOUT] ... 27 more<br />2008-08-28 10:26:07,780 INFO [STDOUT] Caused by: org.omg.CORBA.ORBPackage.InvalidName<br />2008-08-28 10:26:07,780 INFO [STDOUT] at org.jacorb.orb.ORB.resolve_initial_references(Unknown Source)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:563)<br />2008-08-28 10:26:07,780 INFO [STDOUT] ... 38 more

[Former Community Member]

chetan,<br /><br />thanks for the reply. I took the logkit.jar from the weblogic directory (C:\bea92mp3\weblogic92\server\lib\logkit) and had to place it in the jboss server lib directory (C:\Adobe\LiveCycle8.2\jboss\server\all\lib) which is where my client app is running. even though i have weblogic installed locally, I am trying to connect to a remote solaris box running weblogic - this is our adobe livecycle es server. Now I get the following error. Is there something else I need to do in order to get my client app to make a remote ejb call? I know that I am missing something big here, I just have no idea what it is.<br /><br />also, I am bit reluctant to use the soap as we are running a strictly Java environment, and I don't want to have to deal with the web service proxy classes (and the overhead, performance hit, with soap).<br /><br />thanks again<br /><br />regards,<br />jp<br />2008-08-28 10:26:07,765 INFO [STDOUT] com.adobe.livecycle.formsservice.exception.RenderFormException: ALC-DSC-031-000: com.adobe.idp.dsc.net.DSCNamingException: Remote EJBObject lookup failed for ejb/Invocation provider<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.livecycle.formsservice.client.FormsServiceClient.renderHTMLForm(FormsServiceClient.java:142)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.livecycle.forms.RenderHTMLForms.doPost(RenderHTMLForms.java:32)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:717)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:159)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at java.lang.Thread.run(Thread.java:595)<br />2008-08-28 10:26:07,765 INFO [STDOUT] Caused by: ALC-DSC-031-000: com.adobe.idp.dsc.net.DSCNamingException: Remote EJBObject lookup failed for ejb/Invocation provider<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.ejb.EjbMessageDispatcher.initialise(EjbMessageDispatcher.java:97)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.ejb.EjbMessageDispatcher.doSend(EjbMessageDispatcher.java:130)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.base.AbstractMessageDispatcher.send(AbstractMessageDispatcher.java:57)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.idp.dsc.clientsdk.ServiceClient.invoke(ServiceClient.java:208)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.livecycle.formsservice.client.FormsServiceClient.invokeRequest(FormsServiceClient.java:429)<br />2008-08-28 10:26:07,765 INFO [STDOUT] at com.adobe.livecycle.formsservice.client.FormsServiceClient.renderHTMLForm(FormsServiceClient.java:125)<br />2008-08-28 10:26:07,780 INFO [STDOUT] ... 22 more<br />2008-08-28 10:26:07,780 INFO [STDOUT] Caused by: javax.naming.InvalidNameException: Couldn't resolve initial reference: NameService [Root exception is org.omg.CORBA.ORBPackage.InvalidName]<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.corba.j2ee.naming.Utils.wrapNamingException(Utils.java:52)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:574)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.corba.j2ee.naming.ORBHelper.getORBReference(ORBHelper.java:534)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:85)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.corba.j2ee.naming.InitialContextFactoryImpl.getInitialContext(InitialContextFactoryImpl.java:31)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.jndi.WLInitialContextFactory.getInitialContext(WLInitialContextFactory.java:41)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:667)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:247)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at javax.naming.InitialContext.init(InitialContext.java:223)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at javax.naming.InitialContext.<init>(InitialContext.java:197)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.ejb.EjbMessageDispatcher.initJndiContext(EjbMessageDispatcher.java:213)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.ejb.EjbMessageDispatcher.getJndiContext(EjbMessageDispatcher.java:226)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at com.adobe.idp.dsc.provider.impl.ejb.EjbMessageDispatcher.initialise(EjbMessageDispatcher.java:87)<br />2008-08-28 10:26:07,780 INFO [STDOUT] ... 27 more<br />2008-08-28 10:26:07,780 INFO [STDOUT] Caused by: org.omg.CORBA.ORBPackage.InvalidName<br />2008-08-28 10:26:07,780 INFO [STDOUT] at org.jacorb.orb.ORB.resolve_initial_references(Unknown Source)<br />2008-08-28 10:26:07,780 INFO [STDOUT] at weblogic.corba.j2ee.naming.ORBHelper.getORBReferenceWithRetry(ORBHelper.java:563)<br />2008-08-28 10:26:07,780 INFO [STDOUT] ... 38 more

[chetanm_oct]

Hi Pollock,



The root exception indicates that "org.omg.CORBA.ORBPackage.InvalidName ". Which indicates there is some issue in looking up the Invocation EJB which is responsible for executing remote method invocation for ServiceClients.



-- Is the weblogic server running fine and you can access any of the web ui like AdminUI

-- Try to access the server from a simple java client say by just perform a simple authentication as explained in http://livedocs.adobe.com/livecycle/8.2/programLC/programmer/help/wwhelp/wwhimpl/common/html/wwhelp....



Once we get these inputs we can probably then pin point the root cause.



Unfortunately I cannot provide much inputs just from this exception stcktrace :(

[Former Community Member]

Chetan,

thanks again for your help. I tried the sample (which was of great help in debugging my connection issue). There did end up being a minor issue on the adobe livecycle server. After I got that to work, I ported the code into a simple test web app that I deployed to a local weblogic instance. And from there, everything worked fine. I was never really able to connect from my local jboss to the remote adobe livecycle es server, but that's ok as it was only really for testing.



thanks again..



regards,



jp