websphere for livecycle

August 19, 2014, 1:16 pm

≫ Next: Reader Extensions: How to Modify Header/Footer?

Greetings,

We are trying to evaluate ES4 to see if it will work for our business. I downloaded the ES4 Server trial and started installing on a Windows 7 64-bit VM. My question is, does WebSphere come in the install package or is that something that you have to have installed already? If you have to have it in place already, what do you do if you don't have a WebSphere license?

↧

Reader Extensions: How to Modify Header/Footer?

September 9, 2014, 11:43 am

≫ Next: compatibility with old version

≪ Previous: websphere for livecycle

Product: Adobe Livecycle ES4 Reader Extensions

Operating Systems: Windows

Question: I need to figure out how to modify the each web page within Reader Extensions and the Administration Console in order to add text (HTML) to the header and footer of each page. I figure that there should be one or two files that control this, but I am unable to find it.

How can I accomplish this? What files do I need to modify?

↧

compatibility with old version

September 11, 2014, 7:42 am

≫ Next: Current installation of Adobe Livecycle with JDBC driver version 5.1.14 - How can one go back to JDBC driver version 3.0?

≪ Previous: Reader Extensions: How to Modify Header/Footer?

Hi,

I need to connect with LiveCycle Server version 9.0. I tried to do with LiveCycle Workbench ES4, but I couldn't, because this version of workbench is incompatible with this LiveCycle Server. I research in the web for a workbench version ES2, but I didn't find it. Are there a way to get this workbench version? Are there a way to connect with LiveCycle Server 9.0 from LiveCycle Workbench ES4?

I couldn't update LiveCycle Server and I need to modify a service inside.

Thanks on advance.

Rodrigo

↧

Current installation of Adobe Livecycle with JDBC driver version 5.1.14 - How can one go back to JDBC driver version 3.0?

September 17, 2014, 2:11 pm

≫ Next: Cannot login to JBoss Livecycle Installation

≪ Previous: compatibility with old version

I currently have JDBC driver 5.1.14 installed and would like to go back to JDBC driver version 3.0 to test out if that is the cause of a memory issue on another server. Can someone tell me how I can revert back to driver 3.0. I have the driver file.

Thanks!

↧

Cannot login to JBoss Livecycle Installation

April 12, 2009, 7:53 pm

≫ Next: ES3 deployment problem

≪ Previous: Current installation of Adobe Livecycle with JDBC driver version 5.1.14 - How can one go back to JDBC driver version 3.0?

I cannot figure out how to login through workbench. I have configured it for port 8080 and can see the JBoss 4.0 page. The help files say: If you cannot log in successfully, configure the user accounts. To do this, log in to LiveCycle Administration Console as the administrator and click Settings > User Management > Users and Groups. For more information about creating user accounts, see User Management Help.

None of which tells me how to access the server. I have never seen such lousy documentation for a server product that sells for this price. I am evaluating this for my Team to use on a system that will support 20k users for the first year and right now, I'm about to call Rob Tarkoff and tell him that without specialized training, his product is unusable for many. I am well versed in Server technology, and neither the web console nor the jmx-console is accessable for configuring. And I am not a fan of either JBoss (especially 4.0) or high priced WebLogic. Why couldn't they have bundled with Glassfish?

So what next? I need something that works out of the box without $250/hr Deloitte consultants to get it working. Is there a blog or something that someone can point me to where I can get this thing working from?

XP Installation for development.

Thanks,

Curtis Fisher

↧

ES3 deployment problem

February 20, 2013, 6:33 am

≫ Next: LC Configuration Manager problem, port 8080 still in use?

≪ Previous: Cannot login to JBoss Livecycle Installation

I am trying to install ES3 and ES3 SP2 (it's a fresh install).

When I run "LiveCycle ES3 Component Deployment" many of the jar files fail to deploy. Here are log excerpts from the server log, access.log and the configuration manager log.

The main highlights:

server log: the account lockout for _lc_saml_login_ account
Configuration Manager log: 401 error, Unauthorized
access.log: 401 errors abound

Any help will be appreciated. I am also opening a ticket with Adobe support and will report back here if I get any information.

Thanks!

serverlog:

####<Feb 17, 2013 11:48:00 AM PST> <Info> <ServletContext-/CoreSystemConfigComponent> <mrsblapp00637.np.water.ca.gov> <LCES3dev> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <> <48b26ee9a37422c2:-201e99a8:13ce9a80dad:-8000-0000000000000055> <1361130480655> <BEA-000000> <JspServlet: param workingDir initialized to: /opt/wls/user_projects/domains/LCES3/servers/LCES3dev/tmp/_WL_user/adobe-livecycle-weblog ic/h5vcq2>

####<Feb 17, 2013 11:51:15 AM PST> <Info> <JDBC> <mrsblapp00637.np.water.ca.gov> <LCES3dev> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361130675218> <BEA-001128> <Connection for pool "IDP_DS" has been closed.>

####<Feb 17, 2013 11:57:45 AM PST> <Notice> <Security> <mrsblapp00637.np.water.ca.gov> <LCES3dev> <[ACTIVE] ExecuteThread: '1' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361131065068> <BEA-090078> <User _lc_saml_login_ in security realm myrealm has had 5 invalid login attempts, locking account for 30 minutes.>

####<Feb 17, 2013 11:57:45 AM PST> <Notice> <Security> <mrsblapp00637.np.water.ca.gov> <LCES3dev> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1361131065069> <BEA-090078> <User _lc_saml_login_ in security realm myrealm has had 5 invalid login attempts, locking account for 30 minutes.>

####<Feb 17, 2013 11:57:46 AM PST> <Info> <Common> <mrsblapp00637.np.water.ca.gov> <LCES3dev> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0A9E8817856A57175524> <48b26ee9a37422c2:-201e99a8:13ce9a80dad:-8000-0000000000000079> <1361131066945> <BEA-000628> <Created "1" resources for pool "IDP_DS", out of which "1" are available and "0" are unavailable.>

Configuration Manager Log:

[2013-02-17 11:51:18,645], INFO, AWT-EventQueue-0, com.adobe.livecycle.lcm.feature.deployment.DeployDSCsDialog, onEntry()

[2013-02-17 11:57:43,028], INFO, AWT-EventQueue-0, com.adobe.livecycle.lcm.feature.deployment.DeployDSCsDialog, Starting processing

[2013-02-17 11:57:43,033], INFO, AWT-EventQueue-0, com.adobe.livecycle.lcm.feature.lcServer.LCServerConnector, LC Connection properties: {DSC_DEFAULT_SOAP_ENDPOINT=http://mrsblapp00637:7001, DSC_TRANSPORT_PROTOCOL=SOAP, DSC_CREDENTIAL_PASSWORD=********, DSC_CREDENTIAL_USERNAME=administrator, }

[2013-02-17 11:57:43,033], INFO, AWT-EventQueue-0, com.adobe.livecycle.lcm.feature.lcServer.LCServerConnector, Validating connection...

[2013-02-17 11:57:43,129], INFO, AWT-EventQueue-0, com.adobe.livecycle.lcm.feature.deployment.DeployDSCsTask, Starting task: com.adobe.livecycle.lcm.feature.depl

oyment.DeployDSCsTask@18af9b4a

[2013-02-17 11:57:43,386], INFO, Thread-7, com.adobe.livecycle.lcm.feature.deployment.DeployDSCsDialog, Progress: [0%, Loading state from service container ]

[2013-02-17 11:57:43,473], INFO, Thread-7, com.adobe.livecycle.lcm.feature.deployment.DeployDSCsDialog, Progress: [0%, Deploying DSC adobe-pdfservices-dsc.jar]

[2013-02-17 11:57:43,478], INFO, Thread-7, com.adobe.livecycle.lcm.feature.deployment.DeployDSCs, Installing DSC [/opt/adobe/adobe_livecycle_es3/deploy/adobe-pdf

services-dsc.jar, com.adobe.PDFServices, 10.0.4.20120926.1.323123]

[2013-02-17 11:57:43,478], INFO, Thread-7, com.adobe.livecycle.lcm.feature.deployment.DeployDSCs, DSC not installed. DSC will now be installed: com.adobe.PDFServ

ices /opt/adobe/adobe_livecycle_es3/deploy/adobe-pdfservices-dsc.jar

[2013-02-17 11:57:43,719], SEVERE, Thread-7, com.adobe.idp.Document, DOCS001: Unexpected exception. See the stack trace for details.

com.adobe.idp.DocumentError: 401: Unauthorized

at com.adobe.idp.DocumentManagerClient.clientSidePush(DocumentManagerClient.java:363)

...

at java.lang.Thread.run(Thread.java:662)

[2013-02-17 11:57:43,722], SEVERE, Thread-7, com.adobe.idp.Document, DOCS001: Unexpected exception. See the stack trace for details.

com.adobe.idp.DocumentError: 401: Unauthorized

at com.adobe.idp.DocumentManagerClient.clientSidePush(DocumentManagerClient.java:363)

access.log

10.2.68.74 - - [17/Feb/2013:11:51:13 -0800] "POST /soap/sdk HTTP/1.0" 200 265560

10.2.68.74 - - [17/Feb/2013:11:57:43 -0800] "POST /soap/sdk HTTP/1.0" 200 274944

10.2.68.74 - - [17/Feb/2013:11:57:43 -0800] "POST /soap/sdk HTTP/1.0" 200 265560

10.2.68.74 - - [17/Feb/2013:11:57:43 -0800] "PUT /dsc/upload?serviceName=system.component_registry HTTP/1.1" 401 1468

10.2.68.74 - - [17/Feb/2013:11:57:44 -0800] "POST /soap/sdk HTTP/1.0" 200 4588

10.2.68.74 - - [17/Feb/2013:11:57:44 -0800] "POST /soap/sdk HTTP/1.0" 200 5844

10.2.68.74 - - [17/Feb/2013:11:57:44 -0800] "POST /soap/sdk HTTP/1.0" 200 5564

10.2.68.74 - - [17/Feb/2013:11:57:44 -0800] "POST /soap/sdk HTTP/1.0" 200 7776

10.2.68.74 - - [17/Feb/2013:11:57:44 -0800] "POST /soap/sdk HTTP/1.0" 200 54952

10.2.68.74 - - [17/Feb/2013:11:57:44 -0800] "POST /soap/sdk HTTP/1.0" 200 12816

10.2.68.74 - - [17/Feb/2013:11:57:44 -0800] "POST /soap/sdk HTTP/1.0" 200 11672

10.2.68.74 - - [17/Feb/2013:11:57:44 -0800] "PUT /dsc/upload?serviceName=system.component_registry HTTP/1.1" 401 1468

10.2.68.74 - - [17/Feb/2013:11:57:44 -0800] "POST /soap/sdk HTTP/1.0" 200 13176

10.2.68.74 - - [17/Feb/2013:11:57:44 -0800] "PUT /dsc/upload?serviceName=system.component_registry HTTP/1.1" 401 1468

10.2.68.74 - - [17/Feb/2013:11:57:45 -0800] "PUT /dsc/upload?serviceName=system.component_registry HTTP/1.1" 401 1468

10.2.68.74 - - [17/Feb/2013:11:57:45 -0800] "POST /soap/sdk HTTP/1.0" 200 30676

10.2.68.74 - - [17/Feb/2013:11:57:45 -0800] "PUT /dsc/upload?serviceName=system.component_registry HTTP/1.1" 401 1468

10.2.68.74 - - [17/Feb/2013:11:57:46 -0800] "PUT /dsc/upload?serviceName=system.component_registry HTTP/1.1" 401 1468

10.2.68.74 - - [17/Feb/2013:11:57:46 -0800] "POST /soap/sdk HTTP/1.0" 200 20860

10.2.68.74 - - [17/Feb/2013:11:57:46 -0800] "PUT /dsc/upload?serviceName=system.component_registry HTTP/1.1" 401 1468

↧

LC Configuration Manager problem, port 8080 still in use?

September 27, 2009, 12:26 am

≫ Next: Connection to cloudfront.com always times out

≪ Previous: ES3 deployment problem

I'm installing a trial version of the Adobe LiveCycle ES server using JBoss on my system for some development. I'm running Windows Vista Ultimate 64-bit. I did a turnkey installation. That goes fine. When I run the configuration manager, it gets to the deployment step and the "Verifying ports required by service JBoss for Adobe LiveCycle ES are available" step, and I get this error:

"The following ports required by JBoss for Adobe LiveCycle ES are still in use 8080.

Another instance may be running or another application may be using some of the required ports."

Nothing has port 8080 bound. I've checked with a netstat -a -o command. I can run tomcat and it binds port 8080 just fine. I've disabled UAC (I'm logged in as an administrator), disabled windows firewall, and even uninstalled and reinstalled livecycle. One thing that happens if I restart my computer and try again is that it fails for a different error about being unable to stop the JBoss service. If I stop the service manually and retry, it just reverts to the port error above.

This error is really confusing and I can't seem to figure out how to fix it. I need to get this up and running so I can develop and test my application. Anyone have any insights or suggestions?

-Sam Fahmie

↧

Connection to cloudfront.com always times out

February 21, 2011, 6:57 pm

≫ Next: adobe-livecycle-weblogic.ear will NOT deploy

≪ Previous: LC Configuration Manager problem, port 8080 still in use?

I'm trying to download the VMWare workstation LiveCycle appliance using http://d2x45prcet210j.cloudfront.net/LiveCycleES2.5-0.0.5.zip

After several tries, it continues to time out. Is this file still available?

↧

adobe-livecycle-weblogic.ear will NOT deploy

January 30, 2014, 2:57 pm

≫ Next: Errors in jboss log after installing ADEP

≪ Previous: Connection to cloudfront.com always times out

System setup:

Weblogic 12c

Jrockit (latest version)

Windows Server 2008 R2 Standard 64bit (32GB RAM)

SQL server 2012

Livecycle ES4

I have tried various methods to deploy the adobe-livecycle-weblogic.ear file.

I followed the guide for installation, configuration of both weblogic AND Livecycle EXACTLY.

It will not deploy through the LCES4 configuration tool, in fact none of the others would either. I was able to deploy all the other ear files manually through weblogic admin page. This last one however will not deploy. Searching on Google has been totally useless.

Below is an excerpt from the log file of just the error lines.

####<Jan 30, 2014 5:08:45 PM EST> <Error> <com.adobe.idp.dsc.registry.component.impl.ComponentStoreImpl> <MCO04-DPC-01> <Server1> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<anonymous>> <BEA1-0021AAC9C8B4601DDAB8> <ca5fd3c1-636a-4117-8a04-3a5a9dbe5f73-000006bc> <1391119725737> <BEA-000000> <ComponentStoreImpl:getComponents:Exception:EJB Exception: >

a little further down

####<Jan 30, 2014 5:08:48 PM EST> <Error> <Deployer> <MCO04-DPC-01> <Server1> <[ACTIVE] ExecuteThread: '9' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <ca5fd3c1-636a-4117-8a04-3a5a9dbe5f73-000006bc> <1391119728873> <BEA-149265> <Failure occurred in the execution of deployment request with ID "1391119557672" for task "13". Error is: "weblogic.application.ModuleException: java.util.ServiceConfigurationError: javax.servlet.ServletContainerInitializer: Provider com.sun.xml.ws.transport.http.servlet.WSServletContainerInitializer not found"

weblogic.application.ModuleException: java.util.ServiceConfigurationError: javax.servlet.ServletContainerInitializer: Provider com.sun.xml.ws.transport.http.servlet.WSServletContainerInitializer not found

at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java: 140)

at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java :124)

at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:213)

at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:208)

at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)

at weblogic.application.internal.flow.ModuleStateDriver.start(ModuleStateDriver.java:70)

at weblogic.application.internal.flow.StartModulesFlow.activate(StartModulesFlow.java:25)

at weblogic.application.internal.BaseDeployment$2.next(BaseDeployment.java:730)

at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)

at weblogic.application.internal.BaseDeployment.activate(BaseDeployment.java:258)

at weblogic.application.internal.EarDeployment.activate(EarDeployment.java:61)

at weblogic.application.internal.DeploymentStateChecker.activate(DeploymentStateChecker.java :165)

at weblogic.deploy.internal.targetserver.AppContainerInvoker.activate(AppContainerInvoker.ja va:80)

at weblogic.deploy.internal.targetserver.operations.AbstractOperation.activate(AbstractOpera tion.java:586)

at weblogic.deploy.internal.targetserver.operations.ActivateOperation.activateDeployment(Act ivateOperation.java:148)

at weblogic.deploy.internal.targetserver.operations.ActivateOperation.doCommit(ActivateOpera tion.java:114)

at weblogic.deploy.internal.targetserver.operations.StartOperation.doCommit(StartOperation.j ava:151)

at weblogic.deploy.internal.targetserver.operations.AbstractOperation.commit(AbstractOperati on.java:339)

at weblogic.deploy.internal.targetserver.DeploymentManager.handleDeploymentCommit(Deployment Manager.java:846)

at weblogic.deploy.internal.targetserver.DeploymentManager.activateDeploymentList(Deployment Manager.java:1275)

at weblogic.deploy.internal.targetserver.DeploymentManager.handleCommit(DeploymentManager.ja va:442)

at weblogic.deploy.internal.targetserver.DeploymentServiceDispatcher.commit(DeploymentServic eDispatcher.java:177)

at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.doCommi tCallback(DeploymentReceiverCallbackDeliverer.java:195)

at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer.access$ 100(DeploymentReceiverCallbackDeliverer.java:13)

at weblogic.deploy.service.internal.targetserver.DeploymentReceiverCallbackDeliverer$2.run(D eploymentReceiverCallbackDeliverer.java:69)

at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.jav a:550)

at weblogic.work.ExecuteThread.execute(ExecuteThread.java:295)

at weblogic.work.ExecuteThread.run(ExecuteThread.java:254)

Caused By: java.util.ServiceConfigurationError: javax.servlet.ServletContainerInitializer: Provider com.sun.xml.ws.transport.http.servlet.WSServletContainerInitializer not found

at java.util.ServiceLoader.fail(ServiceLoader.java:214)

at java.util.ServiceLoader.access$300(ServiceLoader.java:164)

at java.util.ServiceLoader$LazyIterator.next(ServiceLoader.java:348)

at java.util.ServiceLoader$1.next(ServiceLoader.java:428)

at weblogic.jaxrs.onwls.deploy.util.JaxRsDeployer.getJaxRsInitializerFromUserApp(JaxRsDeploy er.java:133)

at weblogic.jaxrs.server.portable.servlet.JerseyServletContainerInitializer.onStartup(Jersey ServletContainerInitializer.java:75)

at weblogic.servlet.internal.WebAppServletContext.initContainerInitializer(WebAppServletCont ext.java:1339)

at weblogic.servlet.internal.WebAppServletContext.initContainerInitializers(WebAppServletCon text.java:1276)

at weblogic.servlet.internal.WebAppServletContext.initContainerInitializers(WebAppServletCon text.java:1263)

at weblogic.servlet.internal.WebAppServletContext.preloadResources(WebAppServletContext.java :1781)

at weblogic.servlet.internal.WebAppServletContext.start(WebAppServletContext.java:2808)

at weblogic.servlet.internal.WebAppModule.startContexts(WebAppModule.java:1661)

at weblogic.servlet.internal.WebAppModule.start(WebAppModule.java:823)

at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleMod uleWrapper.java:360)

at weblogic.application.internal.ExtensibleModuleWrapper$StartStateChange.next(ExtensibleMod uleWrapper.java:356)

at weblogic.application.utils.StateMachineDriver.nextState(StateMachineDriver.java:42)

at weblogic.application.internal.ExtensibleModuleWrapper.start(ExtensibleModuleWrapper.java: 138)

at weblogic.application.internal.flow.ModuleListenerInvoker.start(ModuleListenerInvoker.java :125)

at weblogic.application.internal.flow.ModuleStateDriver$3.next(ModuleStateDriver.java:214)