Configuring IBM Cognos Framework Manager for Cognos Analytics

If you are using IBM® Cognos® Framework Manager, complete the following steps to configure your OpenSource project then set your Gateway URI and your Dispatcher URI.

Before you begin

The Cognos Analytics service must be installed and an instance must be provisioned in Cloud Pak for Data.

The Framework Manager that you are using must be at least version 12.0.2.

Procedure

  1. In the OpenShift® Web Console, create another route directly to ca-cpd-rest service on port 9300. Use SSL passthrough.

    Run the following oc command:

    oc project xxxx
    If the Cognos Analytics service is running in a tethered namespace that is called ca1, run the following command to create a route:
    oc create -f route.yaml
    If the Cognos Analytics service is installed in the zen control plane namespace, then use zen instead of ca1.
    kind: Route
    apiVersion: route.openshift.io/v1
    metadata:
      annotations:
        openshift.io/host.generated: 'true'
      name: rest
      namespace: ca1
      labels:
        component: ca-ca-cpd-rest-svc
        release: cognos-analytics
    spec:
      to:
        kind: Service
        name: ca-cpd-rest
        weight: 100
      port:
        targetPort: dispatcher
      tls:
        termination: passthrough
        insecureEdgeTerminationPolicy: Redirect
      wildcardPolicy: None
  2. Run the following command to verify that the route was created in the xxxx namespace:
    oc get route -n xxxx
  3. Start the Framework Manager Cognos Configuration tool from where Framework Manager is installed and set the Gateway URI to the ibm-nginx-svc service route for Cloud Pak for Data.
    For example, https://cpd-zen.apps.robrtp1.cp.example.com:443/cognosanalytics/ca1/bi/v1/disp
  4. Set Dispatcher URI for external applications to the route that was created in step 1 for ca-cpd-rest. Use port 443 and /p2pd/servlet/dispatch at the end of the URI.
    For example, https://rest-ca1.apps.robrtp1.cp.example.com:443/p2pd/servlet/dispatch
  5. Add the local configuration advanced property EnableSSLHostnameVerification and set to False.
  6. Save cogconfig for the Framework Manager client. Click Yes on the prompts to accept the certificates.
  7. Edit the Framework Manager configuration file from where Framework Manager is installed:

    <fm_install_directory>\configuration\fm.ini

    1. Go to the <Section Name="webview2"> element in the file.
    2. If the <Preference Name="logonPage"> element is set to FALSE, change this setting to TRUE.
      The following text shows the proper configuration:
      <!-- use Microsoft Edge WebView2 for logon page -->
       <Section Name="webview2">
       <Preference Name="logonPage">TRUE</Preference>
       </Section>
    3. Save and close the fm.ini file.
  8. Open Framework Manager and create a new project.