PPM Setup with TAM WebSeal SSO Works well except for Package "View Log"
Our HTTPS traffic runs through a TAM WebSeal server, which manages the SSO and SSL components of the session. Everything seems to work OK, Dashboards, Reports, Opening Workbench, except for one thing: when we deploy a package from a Demand Request, using References--> Add Existing Package (as Predecessor), we can execute the steps in the Package Workflow OK, but when we click on "View Log" for the Package Line, the URL that comes up is of the Apache server, not the WebSeal server, even though BASE_URL points to the TAM server (plus the URL is not valid...)
-- and then the log does not get displayed.
has anyone else seen this issue?
where should BASE_URL point, WebSeal or Apache?
Why does "View Log" function not follow the BASE_URL like the other functions?
Re: PPM Setup with TAM WebSeal SSO Works well except for Package "View Log"
Hi Derek...yeah, there are a couple of places that seem to hard-code the URL in ways that don't work.We've found that exporting results from a request list portlet to Excel causes the links to have the port ":8080" appended to the URL even though we don't specify that.
BASE_URL should be pointed to WebSeal, I think, ours is pointed to our NAM server and the package logs display fine. (9.11)