We're building a WP installation and have installed it on WAS 6.020 (as the 
documentation says is supported from WP 5.101).

I was wondering if anyone out there has encountered this problem - I don't k
now whether the statement in the Infocenter about WAS 6 support is optimisti
c or whether I've missed something...

Portal seems to run fine and I have done configuration tasks to configure th
e data repository, WCM and WMM.

However when portlets try to produce a URI to an image or other resource tha
t resides within the portlet, the portal is returning a URI relative to the 
portal. This is happening with the administration portlets, the blurb portle
t, the IWWCM authoring port
let ... The problem is cosmetic for portlets such as the Page Manager but ca
uses portlets such as the IWWCM authoring portlet to fail because (I think) 
it can't find some javascript files that it needs.

For example, in the Welcome portlet, the line of code in welcome.jsp :

portletResponse.encodeURI("/images/WelcomeBlurb.jpg")

returns an URI
/wps/images/WelcomeBlurb.jpg
and not
/{portlet_unique_id}/images/WelcomeBlurb.jpg

Has anyone seen anything like this before?

The OS is RHEL 3. Data store is DB2 v8.17.
User repository is OpenLDAP on RHEL 3 (I know it's not supported officially,
 but it works and it doesn't seem to be related to this problem).

[ Post a follow-up to this message ]

Try iFix PK07993.

<david.strachan@csiltd.co.uk> wrote in message
news:1946358064.1127291421932.JavaMail.wassrvr@ltsgwas007.sby.ibm.com...
> We're building a WP installation and have installed it on WAS 6.020 (as
the documentation says is supported from WP 5.101).
>
> I was wondering if anyone out there has encountered this problem - I don't
know whether the statement in the Infocenter about WAS 6 support is
optimistic or whether I've missed something...
>
> Portal seems to run fine and I have done configuration tasks to configure
the data repository, WCM and WMM.
>
> However when portlets try to produce a URI to an image or other resource
that resides within the portlet, the portal is returning a URI relative to
the portal. This is happening with the administration portlets, the blurb
portlet, the IWWCM authoring portlet ... The problem is cosmetic for
portlets such as the Page Manager but causes portlets such as the IWWCM
authoring portlet to fail because (I think) it can't find some javascript
files that it needs.
>
> For example, in the Welcome portlet, the line of code in welcome.jsp :
>
> portletResponse.encodeURI("/images/WelcomeBlurb.jpg")
>
> returns an URI
> /wps/images/WelcomeBlurb.jpg
> and not
> /{portlet_unique_id}/images/WelcomeBlurb.jpg
>
> Has anyone seen anything like this before?
>
> The OS is RHEL 3. Data store is DB2 v8.17.
> User repository is OpenLDAP on RHEL 3 (I know it's not supported
officially, but it works and it doesn't seem to be related to this problem).
>

[ Post a follow-up to this message ]

Hi David, Could you fix this problem? I have the same scenario: Portal 5.1.0
.1 with WAS 6.0.2 on SUSE ES 8.

[ Post a follow-up to this message ]