On every installed instance of IBM Cognos ReportNet in your system which runs

On every installed instance of ibm cognos reportnet

This preview shows page 17 - 21 out of 26 pages.

On every installed instance of IBM Cognos ReportNet in your system which runs Content Manager component open Cognos Configuration and adjust configuration using the following steps. 1.Open Cognos Configuration and locate your LDAP namespace. 2.Enable External Identity mapping by setting the following fields: Use external identity mapping True External identity mapping (uid=${environment("REMOTE_USER")}) or (uid=${environment("USER_PRINCIPAL")})Important:Do not forget the parentheses around the external identity mapping value. Using USER_PRINCIPAL is kind of obsolete since REMOTE_USER is populated too but is mentioned for the sake of completeness. 3.Save the Configuration and restart IBM Cognos ReportNet for these changes to take effect. Appendix C – Enabling Identity Mapping for AD Namespaces2Enabling Identity Mapping is required if IBM Cognos ReportNet is using an AD namespace. This is a namespace of type ADand not IBM Cognos Series 7 or LDAP. 2Enabling Identity Mapping is available as of CRN 1.1.MR2 only
Background image
Enabling Single-Sign-On on WebSphere Portal in IBM Cognos ReportNet 18 Cognos Proprietary Information On every installed instance of IBM Cognos ReportNet in your system which runs Content Manager component open Cognos Configuration and adjust configuration using the following steps. 1.Open Cognos Configuration and locate your AD namespace. 2.Under “Advanced Properties”, click edit.
Background image
Enabling Single-Sign-On on WebSphere Portal in IBM Cognos ReportNet 19 Cognos Proprietary Information 3.Type in “singleSignonOption” for the name and “IdentityMapping” for value. 4.Save the Configuration and restart IBM Cognos ReportNet for these changes to take effect. Appendix D – The Connection Server URIThe “Connection Server URI” is the server connection between the Enterprise Portal and IBM Cognos ReportNet. This is the value to be set for each Cognos Portlet or iView in the Portlet properties. The connection URI will differs depending on the type of Gatewayand the type of PortletGateway Type Connection Server URI Example URI CGI Gateway >/<alias>/cgi-bin/cognos.cgi/cps2/nav -bin/cognos.cgi/cps2/navMOD Gateway >/<alias>/cgi-bin/mod_cognos.dll/cps2/nav -bin/mod_cognos.dll/cps2/navMOD2 Gateway >/<alias>/cgi-bin/mod2_cognos.dll/cps2/nav -bin/mod2_cognos.dll/cps2/navISAPI Gateway >/<alias>/cgi-bin/cognosisapi.dll/cps2/nav-bin/cognosisapi.dll/cps2/navServlet Gateway >/<contextroot>/cps2/naveway/cp2/nav
Background image
Enabling Single-Sign-On on WebSphere Portal in IBM Cognos ReportNet 20 Cognos Proprietary Information Type of Portlet Each portlet group has a different entry point for the WSDL address. In the examples below, the /nav?... section of the URI needs to be changed accordingly: Portlet Type End Point Example Cognos Navigator Cognos Search Cognos Viewer /nav? Metric Manager Watchlist
Background image
Image of page 21

You've reached the end of your free preview.

Want to read all 26 pages?

  • Fall '19
  • IBM WebSphere Application Server, IBM Cognos, IBM WebSphere

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture

  • Left Quote Icon

    Student Picture