LiveCycle7: “A system temporary table space with sufficient page size does not exist” error on DB2

Issue

 If you are installing Workflow 7.2.2 onto a DB2 database you may encounter the following error during the bootstrapping process:

A system temporary table space with sufficient page size does not exist

Reason

 This is due to the “CREATE TEMPORARY TABLESPACE” command having failed when you created the LiveCycle Database.

Solution

 This can occur when the DB creation script is invalid, due to missing line breaks, or spaces.  Please consult the appropriate LC installation documentation for your version.  The script for LC7 is as follows:

CREATE TEMPORARY TABLESPACE ADOBE_TEMP_8K IN DATABASE PARTITION GROUP IBMTEMPGROUP PAGESIZE 8192 MANAGED BY SYSTEM USING (‘C:\DB2\ADOBE_TEMP’) EXTENTSIZE 32 PREFETCHSIZE 16 BUFFERPOOL BP8K;

CREATE REGULAR TABLESPACE ADOBE_DATA_8K IN DATABASE PARTITION GROUP IBMDEFAULTGROUP PAGESIZE 8192 MANAGED BY DATABASE USING (FILE’C:\DB2\ADOBE_DATA’1000) EXTENTSIZE 16 PREFETCHSIZE 16 BUFFERPOOL BP8K;

 

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: ALC-LCM-999-022 error running LCM on a localized OS

Issue

 If you are attempting to install LC ES on an Italian operating system, you may receive the following error trying to run LiveCycle Configuration Manager:

Error [ALC-LCM-999-022]

Failed on 'Stopping JBoss Service JBoss for Adobe LiveCycle ES v8.0'

Service shutdown failed for: JBoss for Adobe LiveCycle ES v8.0

Reason

 Installation on a localized OS is supported as long as it is one of the supported OS versions, however, localized operating systems have not been tested and you may encounter issues.

Solution

 Install on an English operating system if possible.  If you only have a localized OS, then proceed with the installation and report any issues to Adobe support.  We can provide patches as necessary to get LiveCycle running on the localized OS you are using.

reference: (1-48812420/1625939)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: ClassNotFoundException: org.jboss.web.jsf.integration.config.JBossJSFConfigureListener

Issue

 If you have manually configured the JBoss4.2.x  application server and installed LiveCycle ES, you may receive the following exception when starting JBoss:

13:36:29,277 INFO [TomcatDeployer] deploy, ctxPath=/, warUrl=.../deploy/jboss-web.deployer/ROOT.war/
13:36:29,793 ERROR [[/]] Error configuring application listener of class 
org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
java.lang.ClassNotFoundException: org.jboss.web.jsf.integration.config.JBossJSFConfigureListener
 at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1358)
 at org.apache.catalina.loader.WebappClassLoader.loadClass(WebappClassLoader.java:1204)
 at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3797)
 at org.apache.catalina.core.StandardContext.start(StandardContext.java:4359)
 at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:761)
 at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:741)
 at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:553)
 at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
 at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
 at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)

Reason

During the manual configuration of JBoss 4.2.x the documentation from prepareinstallsingle.pdf advises you to disable the JSF libraries contained in [appserver root]/server/all/deploy/jboss-web.deployer.  You must disable the JSF libraries, and also remove the related entries from the web.xml, otherwise the above excpetion will occur when starting JBoss.

Solution

Comment out or remove the following entries from [appserver root]/server/<config-name>/deploy/jboss-web.deployer/conf/web.xml:

<!-- Comment/Remove this -->
<!-- Configures JSF for a web application if thejavax.faces.webapp.FacesServlet is declared -->
<!-- in web.xml.-->
<!--
    <listener>
        <listener-class>org.jboss.web.jsf.integration.config.JBossJSFConfigureListener</listener-class>
    </listener>
-->

<!-- Comment/Remove this -->
<!-- Listens to all web app lifecycle events so that @PreDestroy can becalled on -->
<!-- JSF managed beans that go out of scope. You can comment this out if you-->
<!-- don't use JSF or you don't use annotations on your managed beans.-->
<!--
    <listener>
        <listener-class>com.sun.faces.application.WebappLifecycleListener</listenerclass>
    </listener>
-->

<!--
    <init-param>
        <description>JSF standard tlds</description>
        <param-name>tagLibJar0</param-name>
        <param-value>jsf-libs/jsf-impl.jar</param-value>
    </init-param>
-->
VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 3.0/10 (1 vote cast)

Acrobat/Reader: how to close a PDF automatically through Javascript

Issue

 If you are trying to close a PDF automatically using Javascript you may encounter differing behaviour depending on whether you are using Acrobat or Reader, and of course, depending on the version.

Solution

You should use the setTimeOut() method with the action defined as closeDoc().  The setTimeOut() method must be assigned to a variable in a top level object in the form, to prevent it from being garbage collected when a lower level variable goes out of scope.

In the form:ready event you should add the following script:

var discard = soUtils.closeDoc();

and then create a new Script object on the form with the following code:

function closeDoc()
{
    var str = "This document will now close."; 
    app.alert(str); 
    return app.setTimeOut('this.closeDoc();', 1);
}

Then the PDF should automatically close itself when opened in Acrobat/Reader.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 10.0/10 (3 votes cast)