This content has been marked as final. Show 4 replies
First of all, this is a WebCenter Portal forum question.
I have seen something similar (from Spaces, not from a WebCenter app, though). The reason was that the link has not resolved properly ports - for instance, if WebCenter Portal ran on http://server:port1/webcenter and WebCenter Content on http://server:port2/CS_instance, the link lead to http://server:port1/CS_instance). It was a VM prepared by an engineer in the US, and he resolved the issue by configuring the web server so that the port info was not necessary in the URL - http://server/webcenter worked as well as http://server/CS_instance and the issue with ports simply disappeared.
Apologies for posting it in the wrong forum.But i would like to add here that i have deployed my application on the WC_Spaces server and then tried ,but it dod not worked.
I tried to deploy it on the same admin server on which UCM was running ,but it did not help either...
I think there was a bug filed for this scenario .
CAn you please tell me whether or not it has been resolved?And whether there is a patch available for the same.