This content has been marked as final. Show 2 replies
the port you should be using for your collector should NOT be the same port as the one the Wc_Utilities Managed Server is running on, it is a specifict port the analytics collector is listening on for event to register. Port 31314 is a good one to use, since it's the default one, but actually any unused port can be used.
Make sure you register the collector as a Portal Services for your custom portal as well (see chapter 13 of the Administrator's Guide for Oracle WebCenter PortaL). This chapter gives a good overview of the this you have to do in order to get analytics gathering information of your portal.
I am not sure what you mean with your second question, but I'll try to answer it in the way I understand it.
When you undeploy an application, the analytics data (in the ACTIVITIES database schema) is not purged. So after redeploying your application, the old analytics data is still present.
When you undeploy an application, the MDS is not purged, so any run-time customization made to your portal are still present (eg. pages created at run-time, customizations made to task-flows etc).
Thank you Harold.
One more query.
If i try to access the URL http://<hostname>:<analyticsserver port>/collector will the application be visible or not?
Am getting 403 Forbidden error when attempted to access the application.
Also my task flow shows error - "Analytics Service is not available: datasource could not be found."