I find that Vignette DPM 8 for WebSphere Portal released yesterday, is it V8.0 or V8 SP1?
According to the release note name, it looks like for V8.0 rather than V8.0 SP1?
Thank you in advance.
And also, in dpm for websphere portal, TAS.ear has a war file requires content root: contentapi, but this context has been occupied by websphere portal content_j2ee.war, how could this conflict be solved?
Alex
It is for V8.0.
Regards,
Alberto.
Which functionality problem do you find in preview when you deploy TAS.ear?. V8 has the same context and in preview there is not workaround to move it to other context. As this problem will only happen in preview (in delivery you don't deploy the TAS.ear) we don't detect any important functionality that is missed in WebSphere Portal.
Alberto
Generally, with this context conflct, you still be able to deploy TAS.ear, but not able to start TAS except you remove the contentapi.war module. I remove the contentapi.war in TAS.ear and start it, there are some issues, like the workspace on preview does not work, float menu disappeared etc. I am trying to stop the WebSphere Portal content_j2ee.war and deploy full TAS.ear to see what would happen.
Alberto,
Thank you very much.
I stoped IBM WebSphere Portal content_j2ee.war and deployed full TAS.ear, in this case, 10040/content works fine on preivew stage and I can see float menu and edit pencil for portlet, as same as in Vignette Dynamic Portal Module 8.0 for Websphere Portal Server 6.1 Installation and Configuration Guide.pdf page 30.
But I am not clear about the consequence of stop IBM WebSphere Portal content_j2ee.war, do you guys have any idea about it? Or maybe I should ask how do you get the preview display correctly as the page 30 in DPM document, without contentapi.war, it does not work on my sandbox.
Alex,
contentapi.war is needed in the preview environment. One consequence is that the style/theme editor doesn't work in preview. And I think that the consequence of stop IBM WebSphere Portal content_j2ee.war depends on the extensions that you have developed.
When we deploy the TAS.ear IBM WebSphere stop automatically the content_j2ee.war and TAS.ear deploys just with a warning.
