+

Search Tips   |   Advanced Search

Troubleshoot installation: Content Template Catalog

These are some solutions to problems with installing CTC and Site Builder.


Site Builder does not deploy correctly in a cluster

    Issue:

    Site Builder does not deploy correctly when installed in a cluster

    Symptoms:

    We may see something similar to the following message in the ConfigTrace.log or on the command line you ran the install from: 
    [xmlaccess] <request build="wp8001CF07_001_09" type="update" version="8.0.0.1" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PortalConfig_8.0.0.xsd">
[xmlaccess] <status element="[web-app Z1_3H16H8S0J8EE20IVJBAAPN00C6 uid=site-builder.Portlet.webmod]" result="warning">
[xmlaccess] <message id="EJPXA0161W">EJPXA0161W: 
The web module Site Builder could not be activated. Please see previous messages for reasons and possible corrective actions.</message>
[xmlaccess] </status>
[xmlaccess] <status element="[web-app Z1_3H16H8S0J8EE20IVJBAAPN00C6 uid=site-builder.Portlet.webmod]" result="warning">
[xmlaccess] <message id="EJPPH0048W">EJPPH0048W: 
The synchronization mode of all nodes in the portal cluster is not consistently set. 
The portlet application PA_Site_Builder will not be started in the Application Server. 
Manual synchronization is assumed for all nodes. Manually start the application after all nodes were synchronized.</message>
[xmlaccess] </status>
[xmlaccess] <status element="all" result="ok"/>
[xmlaccess] </request>

    Additionally, we may see a message similar to this message later in the log: 

    [wplc-wait-for-sync-to-complete] *********************************************
[wplc-wait-for-sync-to-complete] Distribution of PA_Site_Builder not complete.
[wplc-wait-for-sync-to-complete] *********************************************
[wplc-wait-for-sync-to-complete] Application Binaries for WebSphere_Portal are not yet expanded on node 
[wplc-wait-for-sync-to-complete] Elapsed time : 0 minutes on node 
[wplc-wait-for-sync-to-complete] Max per app time not exceeded

    Additionally, we may also see a message similar to this message in the log: 

    /opt/IBM/WebSphere/wp_profile/paa/wp.ctc.nswiz/components/wp.ctc.nswiz.apppage.base/config/includes/wp.ctc.nswiz.apppage.base_cfg.xml:29: Detected single app deployment time greater than 5 minutes
at com.ibm.wplc.deploy.tasks.impl.ClusterWaitForSyncToCompleteImpl.execute(ClusterWaitForSyncToCompleteImpl.java:289)
at com.ibm.wplc.deploy.tasks.AbstractBaseAdminTask.executeBean(AbstractBaseAdminTask.java:541)
at com.ibm.wplc.deploy.tasks.AbstractBaseAdminTask.executeTask(AbstractBaseAdminTask.java:525)
at com.ibm.wplc.deploy.tasks.AbstractBaseWsAdminWrapperTask.executeTask(AbstractBaseWsAdminWrapperTask.java:376)
at com.ibm.wplc.deploy.tasks.AbstractBaseAdminTask.execute(AbstractBaseAdminTask.java:175)

    Cause:

    These issues can be caused by the cluster not having auto-synchronization enabled, or by having a long synchronization time.

    Solution

    These instructions assume that we have already attempted to install Site Builder .

    1. Go to the WebSphere Application Server administration console of the dmgr node of the cluster.

    2. Go to...

        Applications | Application Types | WebSphere enterprise applications

      ...and search for the application is called PA_Site_Builder.

    3. If this application exists, go to System administration > nodes.

    4. Select the nodes in the system and click Full Resyncronization. Wait for this action to complete.

    5. Go back to Applications > Application Types > WebSphere enterprise applications.

    6. Select PA_Site_Builder and click Start to restart and deploy the application. Wait until it is fully started. This can take several minutes.

    7. Once the application is available on all the nodes in the cluster, edit the ctc.properties file so that it is setup to install everything except the Site Builder application by setting these values:

      • SB_APP=false

      • SB_PAGE_BASE=false

      • SB_PAGE_VP=true

    8. Rerun the Content Template Catalog installation script with these new settings.

    9. Site Builder should now be installed correctly.


Content Template Catalog 4.3 cannot be installed

    Problem

    Content Template Catalog 4.3 can only be installed on a server where the Page Templates page is located under the Hidden Pages page.

    Symptoms:

    We may see something similar to the following message in the ConfigTrace.log or on the command line you ran the install from: 
    [xmlaccess] EJPXB0002I: Reading input file /opt/WebSphere/wp_profile/ConfigEngine/config/work/components/wp.ctc.templates/ctc-template-portlets.xml
[xmlaccess] <?xml version="1.0" encoding="UTF-8"?&gt; 
[xmlaccess] <!-- IBM WebSphere Portal/8.0.0.1 build wp8001CF07_001_15 exported on Tue Aug 13 15:44:38 EST 2013 from min70mig.wcm.lab/127.0.0.1 --&gt; 
[xmlaccess] <request build="wp8001CF07_001_15" type="update" version="8.0.0.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PortalConfig_8.0.0.xsd"&gt; 
[xmlaccess] <status element="all" result="ok"/&gt; [xmlaccess] </request&gt; 
[xmlaccess] EJPXB0020I: The request was processed successfully on the server. 
[echo] EJPCE0150I: Xmlaccess script completed successfully ctc-template-portlets.xml 
[copy] Copying 1 file to /opt/WebSphere/wp_profile/ConfigEngine/config/work/components/wp.ctc.templates 
[xmlaccess] EJPXB0006I: Connecting to URL http://localhost:10039/wps/config/ 
[xmlaccess] EJPXB0002I: Reading input file /opt/WebSphere/wp_profile/ConfigEngine/config/work/components/wp.ctc.templates/ctc-templates.xml [xmlaccess] <?xml version="1.0" encoding="UTF-8"?&gt; 
[xmlaccess] <!-- IBM WebSphere Portal/8.0.0.1 build wp8001CF07_001_15 exported on Tue Aug 13 15:44:42 EST 2013 from min70mig.wcm.lab/127.0.0.1 --&gt; 
[xmlaccess] <request build="wp8001CF07_001_15" type="update" version="8.0.0.1" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation="PortalConfig_8.0.0.xsd"&gt; 
[xmlaccess] <status element="" result="failed"&gt; 
[xmlaccess] <message id="EJPXA0001E"&gt;EJPXA0001E: An error occurred while processing the XML configuration request.</message&gt; 
[xmlaccess] <message&gt;has-system-mapping attribute of the content-mapping-info element must not be true if a system mapping is not specified and the parent page does not have a system mapping</message&gt; 
[xmlaccess] <stacktrace&gt;<![CDATA[ [xmlaccess] com.ibm.wps.command.xml.XmlCommandException: EJPXA0001E: An error occurred while processing the XML configuration request. 
[xmlaccess] at com.ibm.wps.command.xml.items.ContentNodeItem.executeWCMSynchronization(ContentNodeItem.java:1942) [xmlaccess] at com.ibm.wps.command.xml.items.ContentNodeItem.postProcess(ContentNodeItem.java:2138)

    Additionally, we may also see a message similar to this message in the log: 

    [xmlaccess] EJPXB0015E: Server response indicates an error. 
[echo] EJPCE0104E: Error running scripts at: /opt/WebSphere/wp_profile/paa/wp.ctc/components/wp.ctc.templates/xmlaccess/install/ctc-templates.xml. EJPCE0160I: Verify the PortalAdminId and PortalAdminPwd are set correctly in the wkplc.properties file 
[echo] deploy-apps-applySIFeaturePack EJPCE0101E: Extension point implementation task failure on component for the following assembly: wp.ctc, component components/wp.ctc.templates [echo] 
[si-deploy-paa-content] EJPCE0016E: Task has failed to complete with the following arguements: ConfigExtensionList=-applySIFeaturePack, ComponentList=components/wp.ctc.templates,components/wp.ctc.design,components/wp.ctc,components/wp.ctc.sitetemplates,components/wp.ctc.demo, FunctionalArea=featurepackSI 
[echo] [deploy-paa]: wp.ctc /opt/WebSphere/wp_profile/paa.EJPCE0007E: Task failed to complete. Please check logs for further details  

BUILD FAILED 
/opt/WebSphere/PortalServer/solutionInstaller/wp.si/config/includes/SolutionInstaller_cfg.xml:561: [deploy-paa]: wp.ctc 
/opt/WebSphere/wp_profile/paa.EJPCE0007E: Task failed to complete. Please check logs for further details</p>

    Cause:

    This can happen when the Page Templates page is not located under the Hidden Pages page.

    Solution:

    If the Page Templates page is not located under the Hidden Pages page:

    • Update the page templates as described in the portal migration documentation. For instructions, see Updating page templates.

    • We can alternately run the install script again with UPGRADE_CTC_3=true in ctc.properties. This will move the page templates into the hidden pages location.


Parent Troubleshooting Content Template Catalog sites