Monday, 19 July 2010

Lotus Web Content Management 6.1.5 - Expressing Myself

Following an earlier experience with WebSphere Portal Enable, where I needed to configure the Express WCM content libraries for Intranet and Internet, I tried, and initially, failed to do the same thing on a clean installation of Lotus Web Content Management, as the task: -

./ConfigEngine.sh configure-express -DWasPassword=passw0rd -DPortalAdminPwd=passw0rd

failed with: -

BUILD FAILED
/opt/IBM/WebSphere/PortalServer/installer/wp.oob.content/packager/config/includes/wp.oob.content_cfg.xml:73: The following error occurred while executing this line:
/opt/IBM/WebSphere/PortalServer/installer/wp.oob.content/packager/config/includes/wp.oob.content_cfg.xml:213: EJPXB0015E: Server response indicates an error.

When I dug back through the ConfigTrace.log file, I found: -

[xmlaccess]     <status element="[component]" result="warning">
[xmlaccess]         <message id="EJPXA0196W">com.ibm.wps.command.xml.XmlCommandException: EJPXA0196W: The component cannot be created, because its type is "control", but it does not contain a portlet instance. [component]</message>
[xmlaccess]     </status>
[xmlaccess]     <status element="[component Content.Root.People_Palette.x-1.x100.x100 uniquename=ibm.portal.People Palette Control]" result="warning">
[xmlaccess]         <message id="EJPXA0196W">com.ibm.wps.command.xml.XmlCommandException: EJPXA0196W: The component cannot be created, because its type is "control", but it does not contain a portlet instance. [component Content.Root.People_Palette.x-1.x100.x100 uniquename=ibm.portal.People Palette Control]</message>
[xmlaccess]     </status>
[xmlaccess]     <status element="[component uniquename=com.ibm.wps.hiddenpage.wcm.control.Authoring_Portlet]" result="warning">
[xmlaccess]         <message id="EJPXA0196W">com.ibm.wps.command.xml.XmlCommandException: EJPXA0196W: The component cannot be created, because its type is "control", but it does not contain a portlet instance. [component uniquename=com.ibm.wps.hiddenpage.wcm.control.Authoring_Portlet]</message>
[xmlaccess]     </status>
[xmlaccess]     <status element="all" result="ok"/>
[xmlaccess] </request>

[xmlaccess] EJPXB0021W: The request was processed successfully on the server, but warnings were encountered during processing.

Then I used my nous, and remembered that I'd performed an Admin-only installation of WCM, so I needed to run the WCM configuration task: -

./ConfigEngine.sh configure-wcm-authoring -DWasPassword=passw0rd -DPortalAdminPwd=passw0rd

as per this blog post from a week or so back.

Once I ran this task, I was able to successfully re-run the configure-express task, and all is good.

For the record, I installed WCM using these images: -

unzip CZ8G9ML.zip -d /tmp/IL-Setup
mkdir /tmp/IL-1
tar xvzf CZ8H5ML.tgz -C /tmp/IL-1
mkdir /tmp/IL-2
tar xvzf CZ8HDML.tgz -C /tmp/IL-2
unzip CZ8IBML.zip -d /tmp/IL-3
unzip CZ8ICML.zip -d /tmp/IL-4
unzip CZ8IDML.zip -d /tmp/IL-5
unzip CZ8IEML.zip -d /tmp/IL-5a

which results in the following in /opt/IBM/WebSphere/PortalServer/wps.properties: -

# Product information for IBM WebSphere Portal Server
product=IBM WebSphere Portal Server
version=6.1.0.3
featurepack=6.1.5
fixlevel=0
mode=standard
buildnumber=wp6103_201_01
WPFamilyName=content
WPInstallType=admin

ProfileName=wp_profile
ProfileDirectory=/opt/IBM/WebSphere/wp_profile


No comments:

TIL - read-only variables in Linux

 A co-worker was seeing an exception: -  line 8: TMOUT: readonly variable when trying to SCP a file from a remote Linux box. I did some digg...