Configuring IBM Business Monitor and Business Space to use an existing IBM Cognos BI service

If you already have IBM® Cognos® Business Intelligence installed, you can use your existing IBM Cognos BI service with IBM Business Monitor.

About this task

To connect IBM Business Monitor to your IBM Cognos BI server, you must connect IBM Business Monitor administration processes and Business Space reports with IBM Cognos BI.

Important: The remote IBM Cognos BI must be running on a WebSphere Application Server, and when administrative security is enabled, the user repository must be the same on the IBM Business Monitor server and the IBM Cognos BI server.

Make sure that the database client is running and has access to the IBM Business Monitor database on the remote IBM Cognos BI server. Also be sure the IBM Business Monitor database has been cataloged with the remote IBM Cognos BI server with the same name as the catalog entry on the IBM Business Monitor server.

If you created a deployment environment by using the monConfig script, a new IBM Cognos BI was installed for you. To remove it, use the wbmRemoveCognosService command. (If you ran the wbmSetCognosDispatcher command before creating a deployment environment, the IBM Cognos BI service was not deployed and therefore does not require removal.)

Procedure

To connect IBM Business Monitor administrative processes and set up Business Space to work with your existing IBM Cognos BI, complete the following steps:

Connect the IBM Business Monitor administrative processes to your existing IBM Cognos BI service in either of the following ways.
- Run the IBM Business Monitor configuration wizard from the administrative console.
- Run the wbmSetCognosDispatcher wsadmin command.
Configure single sign-on between the WebSphere® Application Server running Business Space and the WebSphere Application Server running IBM Cognos BI. See Enabling single sign-on.
Configure IBM Cognos BI for single sign-on. See Configuring an existing IBM Cognos BI service for single sign-on.
Add the IBM Cognos BI host name and port number to the list of trusted servers in IBM Cognos BI. Otherwise, you will not be able to view the pages in Business Space.
1. Open the IBM Cognos BI Configuration client. To open the client, run the cogconfig.bat or cogconfig.sh file located in cognos_installation_root/bin64 .
2. Select Local Configuration > Security > IBM Cognos Application Firewall.
3. Click the pencil icon next to Valid domains or hosts and add the IBM Cognos BI host and port number configured in the endpoint from Business Space. For example, add lc2d266009.example.com:9080. If you have multiple hosts, click Add to add more entries.
4. Click OK. Click Save.
5. Restart the server that is running IBM Cognos BI.
Because Business Space end points for IBM Cognos BI are configured when the IBM Cognos BI remote URL is configured, verify that the custom properties of the Mashups Endpoints resource environment provider are correct:
1. From the WebSphere administrative console, click Resources > Resource Environment > Resource Environment Providers > Mashups Endpoints > Custom properties.
2. Verify the following custom properties for the Mashups Endpoints resource environment provider:
```
{com.ibm.cognos}cognosServiceRootId.url
{com.ibm.cognos}cognosDispatcherRootId.url 
{com.ibm.cognos}cognosWebContentRootId.url 
```

If the properties you checked in step 5 are not correct, complete the following steps:

Update the following service endpoint file.

install_root/BusinessSpace/registryData/WBM/endpoints/cognosEndpoints.xml

In each of the three <tns:url> sections, add the IBM Cognos BI server host name and port at the beginning of the line.

For example, if your host name is lc2d266009.example.com and your port number is 9080, the completed file would look like:

<tns:Endpoint>
<tns:id>{com.ibm.cognos}cognosServiceRootId</tns:id>
<tns:type>{com.ibm.cognos}cognosServiceRootId</tns:type>
<tns:version>1.0.0.0</tns:version>
<tns:url>http://lc2d266009.example.com:9080/p2pd/servlet/dispatch/ext/</tns:url>
<tns:description>Location of backing services for Cognos widgets</tns:description>
</tns:Endpoint>

<tns:Endpoint>
<tns:id>{com.ibm.cognos}cognosDispatcherRootId</tns:id>
<tns:type>{com.ibm.cognos}cognosDispatcherRootId</tns:type>
<tns:version>1.0.0.0</tns:version>
<tns:url>http://lc2d266009.example.com:9080/p2pd/servlet/dispatch/ext/</tns:url>
<tns:description>Location of Cognos Dispatcher</tns:description>
</tns:Endpoint>

<tns:Endpoint>
<tns:id>{com.ibm.cognos}cognosWebContentRootId</tns:id>
<tns:type>{com.ibm.cognos}cognosWebContentRootId</tns:type>
<tns:version>1.0.0.0</tns:version>
<tns:url>http://lc2d266009.example.com:9080/p2pd/servlet/</tns:url>
<tns:description>Location of Cognos web content</tns:description>
</tns:Endpoint>
</tns:BusinessSpaceRegistry>

For more information about modifying the endpoints files, see Enabling widgets for cross-cell environments.

Run the updateBusinessSpaceWidgets command for the cognosEndpoints.xml file. Follow the instructions in Enabling widgets for cross-cell environments.