Problem with Weblogic Commerce Personalization

Question

We're having problem that we have not been able to pin point yet. Originally
when we started we were fine and our public view and personal view of
portals/portlets was o.k. Somehow within a day, before logging to the
personalization, in public view, all the colors are messed up and we're
missing the borders and titles. One of our developers was missing a portlet
until he logged on.
The problem may have to do with the directories specified in the properties
file. I'm guessing that there maybe loopholes in the instructions. The
folders that need to be specified in the properties, i.e. ../repository or
.../portlet, seems to be mixed up a bit.
Thanks for your help,
Farah

Answer 1

Hello Farah,
All of the problems you describe could have been caused by configuring your
portlets in the Administraton Tool to behave as you have described.
Particulary:
Somehow within a day, before logging to the
personalization, in public view, all the colors are messed up and we're
missing the borders and titles.Missing borders is caused by using the Admin Tool --> Portal Management -->
Colors tool to set "Portlet borders" to "off". Messed up colors could be caused
by someone using the admin tool to change colors for a group associated with
your user.
The JSP page for the titlebar is specified in the portlet definition, using
the Admin Tool --> Portal Management tool. You specify it when you create or
edit the properties for a portlet definition. A default titlebar.jsp is
supplied with WLCS 2.0. If you leave the Titlebar URL field blank, then no
titlebar will show up. If the path to the titlebar is incorrect, then it will
not show up. The path you specify is relative to the portal workingdir or the
portal repositorydir, which are specified in weblogic.properties. The portal
workingdir and repositorydir are relative to the documentRoot, also specified in
weblogic.properties. The server looks for portal files in the workingdir first
and then in the repositorydir.
The exampleportal ships with the titlebar.jsp in the
<install-dir>/server/public_html/portals/repository directory and you would fill
in the Titlebar URL field with "titlebar.jsp" because
documentRoot=<install-dir>/server/public_html and the exampleportal
repositorydir=/portals/repository/ (the exampleportal
workingdir=/portals/example/, and this directory does not come with the
installation)
One of our developers was missing a portlet
until he logged on.Such a portlet is called a "Login Required" portlet and it is specified in the
Admin Tool using the portlet definition tool.
Ture Hoefner
BEA Systems, Inc.
1655 Walnut Street; suite 200
Boulder, CO 80302
www.beasys.com