09-03-04 03:56 PM
quote: Originally posted by Keith Picthall
James,
Never mind. I just figured it out.
On the content portlet, under the "Links" tab, I had set the "Receive
Links From" variable to "None". By switching it to "This portlet" or
"Other portlets and this portlet" the image appears. A view of the
source code shows that the image path is now explicitly defined under
this setting.
So the lesson learned here is to make sure that the "Receive Links From"
variable is set to "This portlet" if your portlet content references an
external file like an image or PDF document.
Thanks for your help!
-Keith
Keith Picthall wrote:
> James,
>
> Which specific setting are you referring to? When I open up the ILWWCM
> portlet to edit it, under the Settings tab, I have:
>
> Web Content Management Server Host:
> http://mds34493.us.dci.discovery.com
>
> Web Content Management Server Path:
> /ilwwcm/connect/
>
> A snippet of the source of the rendered page in portal (with the broken
> image) shows this:
>
> <iframe style="display:none"
> src="http://mds34493.us.dci.discovery.com/ilwwcm/connect/?mod=AJEPortletMo
dule&action=setAptrixCookie& AptrixSessionCookie=JSESSIONID=0000wiYCs
vDW1GY9s
Z3PGTTomnz:-1"></iframe>
>
>
> <span class="oTitle">Test Title</span><br><br><IMG
> SRC="/ilwwcm/resources/image/468000042b54fc08/testimage.jpg"
> HEIGHT="140" BORDER="0" WIDTH="219" ><br><br>Test Content<br><br><a
> href="http://www.discovery.com/" target="_blank">> Test Link</a>
>
>
> You will notice that the iFrame reference is fine as it is an explicit
> call out to the remote ILWWCM server (mds34493). Unfortunately, the
> image reference is relative when I need it to be explicit. If I change
> either of the two settings above, the portlet does not render as the
> iFrame call gets hosed. The portlet expects the ILWWCM server to be
> local else it would not just put out a local reference to the image. If
> there is something in the portlet edit mode that you can edit to get
> around this, I am obviously missing it. If you could provide a bit more
> detail to you initial response, that would be of great help. Thanks.
>
> -Keith
>
>
> news.software.ibm.com wrote:
>
>
Keith,
We have a slightly different situation here for aptix.
The content links work but the
session cookie link does not.
The session link on the browser is
<iframe style="display:none" src="http://10.194.163.246:9084/ilwwcm/connect/
?mod=AJEPortletModule&action=setAptrixCookie&AptrixSessionCookie=JSESSIONID=
0000mrmPEgQYF-YdStNhM_3rdEu:-1"></iframe>
where as the link to the content is
<p align="left"> <a class=contrastHeading href='/wps/myportal/!ut/p/_s.7_0_A
/7_0_AAM/.cmd/ad/.ar/1345295282/.c/6_0_32N/.ce/7_0_AAP/.p/5_0_3CM/.d/0?Aptri
xContext=http://10.194.163.246:9084/ilwwcm/connect/Public+Portal/MSF+Home/Po
sition+Vacancies/Accountant'>
The problem with the session cookie linkis that the aptix server is in a 10
dot subnet and of course is not accessible directly from the internet.
Do you have any idea on how we might solve this?
Thanks for any info on this,
Tim
[ Post a follow-up to this message ]
|