I would like to create a second infoview entry point for SAP users on the same physical box (single server) as regular InfoView. I know it will be temping to ask why, but it’s a very long story…
I am trying to mock this up and have detailed the following steps below. I suspect I am missing a few steps (for example, where do I specify the entry port?). I am sure step 2 is wrong, as I the desktoplaunch no longer exists in Xi 3.1. I’m also wondering if I need to deploy all the war files, or just the one needed for Infoview.
Copy the InfoView.war file to a new directory ( Program Files/Business Objects/ Business Objects Enterprise 12.0/java/applications/sap). I imagine I would need to rename the war file (say SAPInfoview.war)?
Create a xml file with the following logic :
Save the xml file (what name? does it matter) in Program Files\Business Objects\Tomcat55\conf\Catalina\localhost
Restart Tomcat
Change the web.xml to make SAP security the default. But this should not be the regular infoview web.xml. I’m not sure where this would reside.
Alternate URL to access InfoView
A second URL is available to access InfoView. This URL is provided for the
administrator or a user to access InfoView, without single sign-on, after single
sign-on has been enabled.
Now, I see that there is a logonNoSso.aspx in IIS for .NET Infoview, but I have been unable to get this to work in the 64-bit version of Windows Server 2003 when SSO NTLM is being used.
Sorry aniketp, I didn’t see a topic reply notification on this post.
Steve is correct. The non-SSO pages come pre-packaged. In terms of the client whom we couldn’t get the “no sso” page to work for .NET, they had Tomcat running regardless because we opted not to use the WACS for the CMC, so they just used the Java InfoView for Enterprise logins.
However, I notice as I perform more installations that Java Kerberos SSO w/ Vintela is much kinder when a user who is logged into an AD account that doesn’t have access to Enterprise hits the login screen of Java InfoView - as it kicks them right back to the login screen. Then, should you want to you can edit the web.xml to make the authentication drop down visible if they want to login using an Enterprise account - such as Administrator.
.NET InfoView with SSO enabled with NTLM isn’t as friendly. However, I havn’t tried .NET and Kerberos to see if there is a difference in the way the login screen behaves. I presume not because the behavior is determined at the web tier layer.
But Once the Authentication drop down is made visible using web.xml, wont the Single-Sign On(Auto Login) feasure get disabled and every user has to always go through Infoview Login page?
(BOB member since 2002-08-15)
(BOB member since 2007-10-05)
(BOB member since 2008-12-03)