Maximo 7.6 and Cognos 10.2.1 Integration · PDF fileMulti-server architecture List of the activitiesfor installationin a multi-server environment • Cognos Server – InstallDatabase

Maximo 7.6 and Cognos 10.2.1

integration

Agenda

• 1. Overview

• 2. Oracle client installation & setup

• 3. Cognos installation & setup

• 4. Cognos Framework installation & setup

• 5. Configure Maximo Integration

• 6. Import packages in Cognos

Architectural consideration

• In this tutorial the components are installed in a single server in whichMaximo is already installed on Oracle & WAS and we use the MaximoOracle installation for the Cognos repository and the same HTTP Server (IBM HTTP Server)

• The server is a Windows 2012 server

• The hostname is mx7vm. Username and password used are the default for every product

• The authentication method used for Cognos is MXCSP (authentication via Maximo users)

• The required software packages are located in C:\Users\ibm\Desktop\SW\*

• If you use a different architecture please refer to the following document for details: http://www-01.ibm.com/support/docview.wss?uid=swg21692347&aid=1

Multi-server architecture

List of the activities for installation in a multi-server environment• Cognos Server

– Install Database or Schema for Content Store (check the Cognos product compatibility report for more detail)

– Install and configure HTTP Server

– Create tablespace and cognos user (grant priviledges)

– Install and configure IBM Cognos BI

– Configure security

• Maximo Server– Create cognos user on Maximo DB (grant read access to Maximo table)

– Configure Maximo integration

• Laptop/Desktop of user that designs new report– Install Oracle client 32 bit / (db2 client)

– Install IBM Cognos Framework

– Publish packages ( only during the first framework installation )

Reference documentation

• Maximo76_Cognos102_Install_Guide_rev4.pdf:

http://www-01.ibm.com/support/docview.wss?uid=swg21692347

• Maximo76CognosFeatureGuide_rev3.pdf:

http://www-01.ibm.com/support/docview.wss?uid=swg21697011&aid=1

• Maximo76CognosDimensions_HowToExample.pdf:


• Maximo76_Cognos_ContentBIPacks.pdf:

http://www-01.ibm.com/support/docview.wss?uid=swg21693618

• Maximo76_Cognos_ProductArchitectureLicenseEntitlement_rev1.pdf:


Reference site

• IBM developerWorks: Maximo 76 BI Documentationhttps://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset%20Management/page/Maximo%2076%20BI%20Documentation

• IBM developerWorks: Cognos reporting https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset%20Management/page/Cognos%20Reporting

• IBM developerWorks: Maximo 7.6 report integration with Cognos BI Server 10.2https://www.ibm.com/developerworks/community/wikis/home?lang=pt_br#!/wiki/Anything%20about%20Tivoli/page/Maximo%207.6%20report%20integration%20with%20Cognos%20BI%20Server%2010.2

• IBM developerWorks: Maximo 76 Cognos BI Recordingshttps://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset%20Management/page/Maximo%2076%20Cognos%20BI%20Recordings

Agenda

• 1. Overview






Setup the installation configuration file

• Change the installation configuration file (due to an oracle client 32 bit

bug):

– In the Oracle client installation package open the “Oracle client

10.2.0.1\winnt_12102_client32\client32\install\oraparam.init” file

– Change the MSVCREDIST_LOC value. Set the parameter to the value:

vcredist_x86.exe

Modify the windows registry (to resolve an error during

the Oracle client Installation)

• Launch the regedit winsows program

• Perform and export (for backup purpose): File -> Export

• Execute the following instructions (see picture in next slides for detailed

instruction):

– In HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node create a new key with

name ORACLE

– Inside the ORACLE KEY create a “string value”:

• Value name: inst_loc

• Value Data: C:\\Program Files (x86)\\Oracle\\Inventory

• Search the nearly created Key

• Right click the Key and select Rename

• Insert ORACLE as new name

• Click on the new key ORACLE and move on the right panel

• Right click and select “

Setup the key

• C:\Users\ibm\Desktop\SW\Oracle client

10.2.0.1\winnt_12102_client32\client32

• Run as administrator setup.exe

Launch the installation

Configure Oracle client listener

• Copy the tnsnames.ora file from the network\admin folder of the Oracle

installation (C:\Oracle\product\12.1.0\dbhome_1\NETWORK\Admin) to

the network/admin folder of the Oracle client installation

(C:\Oracle\product\12.1.0\client_1\NETWORK\admin).

NOTE: if the Oracle client is installed in a server that is different from the

Oracle database ones open the tnsnames.ora file in the network\admin folder

of the Oracle client installation and manually configure hostname and port

Launch the Services Program on windows and restart

the Oracle listener (OracleOraDB12Home1TNSListener)

Test listener connectivity

• Open a windows command line

• Execute: tnsping mx7vm

Agenda

• 1. Overview






Steps

• 3.1 Check Prerequisites

• 3.2 Check Oracle configuration

• 3.3 Create Oracle tablespace for Cognos

• 3.4 Create Oracle User for Cognos

• 3.5 Install Cognos BI

• 3.6 Configure Cognos

3.1 Check prerequisites

• Check the HW & SW prerequisite for the chosen operative systems

Detailed instruction may be found at the following link:

https://www.ibm.com/support/knowledgecenter/SSEP7J_10.2.0/com.ibm.sw

g.ba.cognos.cbi.doc/welcome.html

3.2 Check database configuration

• Ensure that the parameter for the database instance compatibility level of the content store database is set to 9.0.1 or higher. Check the COMPATIBLE initialization parameter setting by issuing the following SQL statement:

SELECT name, value, description FROM v$parameter WHERE name='compatible';

• Determine if the database is UnicodeSELECT * FROM NLS_DATABASE_PARAMETERS where parameter = 'NLS_CHARACTERSET';

(if the result set returns an NLS_CHARACTERSET that is not Unicode, create a new database and specify AL32UTF8 for the database character set parameters)

NOTE: in the following slide the sample screenshot on how use the SQL Developer tools to perform the required actions

Detailed instruction may be found at the following link:

https://www.ibm.com/support/knowledgecenter/SSEP7J_10.2.0/com.ibm.swg.ba.cognos.vvm_ag_guide.10.2.0.doc/t_vv_crt_oracle_repos.html

Create new connection

• Connection name: system

• Username: system

• Password: manager

• SID: max1

Set new connection parameter

3.3 Create tablespace for cognos

Sample instruction:

CREATE TABLESPACE COG_REPO

DATAFILE

'C:\ORACLE\ORADATA\MAX1\COG_REPO.DBF' SIZE 2849505280

AUTOEXTEND ON NEXT 160 MAXSIZE 34359721984

BLOCKSIZE 8192

DEFAULT NOCOMPRESS

ONLINE

SEGMENT SPACE MANAGEMENT MANUAL

EXTENT MANAGEMENT LOCAL AUTOALLOCATE;

Detailed instruction may be found at the following links:

https://www.ibm.com/support/knowledgecenter/SSEP7J_10.2.0/com.ibm.sw

g.ba.cognos.vvm_ag_guide.10.2.0.doc/t_vv_crt_oracle_repos.html

3.4 Create user for cognos

Sample instruction:

CREATE USER cognos

PROFILE "DEFAULT"

IDENTIFIED BY cognos

DEFAULT TABLESPACE "COG_REPO"

TEMPORARY TABLESPACE "TEMP"

QUOTA UNLIMITED

ON COG_REPO

ACCOUNT UNLOCK;

Detailed instruction may be found at the following links:

https://www.ibm.com/support/knowledgecenter/SSEP7J_10.2.0/com.ib

m.swg.ba.cognos.vvm_ag_guide.10.2.0.doc/t_vv_crt_oracle_repos.html

GRANT CONNECT TO cognos;

GRANT CREATE ANY INDEX TO cognos;

GRANT DROP ANY INDEX TO cognos;

GRANT DROP ANY TABLE TO cognos;

GRANT ALTER ANY PROCEDURE TO cognos;

GRANT ALTER ANY SEQUENCE TO cognos;

GRANT ALTER ANY TABLE TO cognos;

GRANT ALTER ANY TRIGGER TO cognos;

GRANT CREATE ANY DIRECTORY TO cognos;

GRANT CREATE ANY TABLE TO cognos;

GRANT CREATE ANY TRIGGER TO cognos;

GRANT CREATE PROCEDURE TO cognos;

GRANT CREATE SEQUENCE TO cognos;

GRANT CREATE SESSION TO cognos;

GRANT CREATE SYNONYM TO cognos;

GRANT CREATE TABLE TO cognos;

GRANT CREATE TYPE TO cognos;

GRANT CREATE VIEW TO cognos;

GRANT DELETE ANY TABLE TO cognos;

GRANT DROP ANY PROCEDURE TO cognos;

GRANT DROP ANY SEQUENCE TO cognos;

GRANT DROP ANY TRIGGER TO cognos;

GRANT DROP ANY VIEW TO cognos;

GRANT EXECUTE ANY PROCEDURE TO cognos;

GRANT INSERT ANY TABLE TO cognos;

GRANT QUERY REWRITE TO cognos;

GRANT SELECT ANY DICTIONARY TO cognos;

GRANT UNLIMITED TABLESPACE TO cognos;

GRANT UPDATE ANY TABLE TO cognos;

Grant priviledge to new user

Optional: Test new user

Optional: set paramenter for test

• Connection name: system

• Username: system

• Password: manager

• SID: max1

• C:\Users\ibm\Desktop\SW\Cognos\bi_svr_64b_10.2.1_win_ml.tar\winx64h

• run as administrator issetup

Link to Cognos installation manual: http://public.dhe.ibm.com/software/data/cognos/documentation/docs/en/10.2.1/inst_cr_winux.pdf.html

3.5 Install Cognos BI

3.6 Configure Cognos

• 3.6.1 Configure the HTTP Server

• 3.6.2 Configure the Oracle library

• 3.6.3 Restart the HTTP server

• 3.6.4 Check that the Oracle Listener is started

• 3.6.5 Run Cognos Configuration tool

3.6.1 Configure the HTTP Server

• Navigate to the folder conf in the HTTP install path (on the Cognos installation server)

• Open the file httpd.conf

• Insert the following lines after the alias definition (see next slide for sample screenshots):

####################### Added for Cognos ########################

ScriptAlias /ibmcognos/cgi-bin "C:\Program Files\ibm\cognos\c10_64\cgi-bin"

<Directory "C:\Program Files\ibm\cognos\c10_64\cgi-bin">

Options FollowSymLinks

AllowOverride FileInfo

Order Allow,Deny

Allow from All

</Directory>

Alias /ibmcognos "C:\Program Files\ibm\cognos\c10_64\webcontent"

<Directory "C:\Program Files\ibm\cognos\c10_64\webcontent">

Options FollowSymLinks

AllowOverride FileInfo

Order Allow,Deny

Allow from All

</Directory>

####################### Added for Cognos ########################

• Insert the following lines after </IfModule>:

<IfModule mod2_2_cognos.c>

CGIBinDir "C:\Program Files\ibm\cognos\c10_64\cgi-bin"

</IfModule>

• Save the file

3.6.2 Configure the Oracle library

• Copy the ojdbc6.jar file from the lib folder of the Oracle installation (

C:\Oracle\product\12.1.0\dbhome_1\jdbc\lib ) to the lib folder of the

Cognos installation ( C:\Program

Files\ibm\cognos\c10_64\webapps\p2pd\WEB-INF\lib )

3.6.3 Restart the HTTPServer

• Open the Services program

• Stop the “IBM HTTP Server V8.5” service

• Start the “IBM HTTP Server V8.5” service

3.6.4 Check that the Oracle listener is started


• Locate the ”OracleOraDB12Home1TNSListener” service

• Check that is running

3.6.5 Run Cognos Configuration tool

Set the appropriate value for hostname and port in the field marked with a

icon in the picture below:

Configure Cognos Environment

Configure Security

• Delete default content store (only if DB is different from DB2)

Set Database Connection Properties

• Create new content store (only if DB is different from DB2)

Create new content store

• Configure content store:

Port number: 1521 User ID: cognos Password: Cognos SID: max1

Set Database Connection Properties

Save Database Connection Properties

• Save configuration

• Check save results

Check results

Start Cognos Service

Agenda

• 1. Overview






• C:\Users\ibm\Desktop\SW\Cognos\fm_10.2.1_win_ml.tar\win32

• run as administrator issetup

Run Cognos Framework installation

• Lauch “IBM Cognos Configuration” under ‘’IBM Cognos 10’’

Configure Cognos Framework

Configure Cognos Framework parameters

Set the appropriate value for hostname and port in the fields as shown in the

picture below:

Agenda

• 1. Overview






5. Configure Maximo Integration

• 5.1 Configure maxdatasources property file

• 5.2 Grant to Cognos the access to Maximo tables

• 5.3 Copy the jar file from Maximo to Cognos

• 5.4 Create a namespace in Cognos configuration

• 5.5 Configure Maximo System Properties

• 5.6 Configure Cognos datasource & folders

• 5.7 Configure Maximo Integration Framework

• 5.8 Import predefined Cognos Packages

• Connect to your Maximo Administration workstation

• Open the Maximo installation folder

• Navigate to reports\cognos\c10\configuration (

C:\maximo\maximo\reports\cognos\c10\configuration )

• Edit mxcognosdatasources.properties file

• Insert configurtion data (use appropriate value for the installation):

maximoDataSource.url=jdbc:oracle:thin:@mx7vm:1521:max1

maximoDataSource.driver=oracle.jdbc.driver.OracleDriver

maximoDataSource.username=cognos

maximoDataSource.password=cognos

maximoDataSource.schemaowner=maximo

5.1 Configure maxdatasources property file

Encrypt mxcognosdatasources.properties

• Connect to the Maximo Administration workstation


• Navigate to reports\cognos\tools ( C:\maximo\maximo\reports\cognos\tools )

• Run encryptproperties.cmd (or encryptproperties.sh on unix/linux)

• Copy the mxcognosdatasources_enc.properties file from the reports\cognos\c10\configuration folder in the Maximo installation directory ( C:\maximo\maximo\reports\cognos\c10\configuration) to the configuration folder on the Cognos installation server ( C:\Program Files\ibm\cognos\c10_64\configuration )

• Connect to the Cognos installation server

• Open the Cognos installation server

• Navigate to the configuration folder ( C:\Program Files\ibm\cognos\c10_64\configuration )

• Rename the copied mxcognosdatasources_enc.properties file to mxcognosdatasources.properties

• Launch an SQL tool or command line

• Access as user system (pwd: manager)

• Provide the following grant:

grant select on MAXIMO.MAXUSER to cognos;

grant select on MAXIMO.GROUPUSER to cognos;

grant select on MAXIMO.PERSON to cognos;

grant select on MAXIMO.MAXGROUP to cognos;

grant select on MAXIMO.MAXPROPVALUE to cognos;

5.2 Grant to Cognos the access to Maximo tables



• Navigate to applications\maximo\lib (

C:\maximo\maximo\applications\maximo\lib )

• Copy the oraclethin.jar and CAM_AAA_MXCSP.jar the to the lib folder of

the Cognos installation ( C:\Program

Files\ibm\cognos\c10_64\webapps\p2pd\WEB-INF\lib )

• Restart the Cognos Server

5.3 Copy the jar file from Maximo to Cognos

5.4 Create a namespace in Cognos configuration

Select Authentication

Create a namespace

• Configure the namespace with the following values:

– Type: Custom Java Provider

– Namespace ID: maximo

– Java Class Name: MXCSP

– Selectable for Authentication: True

Configure the namespace

• Enter in Maximo with the user maxadmin (password maxadmin)

• Go to ‘’System Configuration -> Planform Configuration -> System properties’’

• Set the appropriate value for the following properties value (case sensitive) –for a description of the parameter see the link https://www.ibm.com/support/knowledgecenter/SSLKT6_7.6.0.7/com.ibm.mbs.doc/propmaint/r_report_integration_properties.html: – Property name: mxe.report.cognos.datasource Property value: MXDB

– Property name: mxe.report.cognos.db.schemaName Property value: MAXIMO

– Property name: mxe.report.cognos.db.type Property value: OR

– Property name: mxe.report.cognos.maxappurl

Property value: http://mx7vm/maximo

– Property name: mxe.report.cognos.namespace Property value: maximo

– Property name: mxe.report.cognos.querymode Property value: compatible

– Property name: mxe.report.cognos.serverURL

Property value: http://mx7vm:9080/ibmcognos/cgi-bin/cognos.cgi

– Property name: mxe.rest.webappurl

Property value: http://mx7vm/maxrest

• Save all of the changed properties (by selecting them before click on save)

• Perform a Live Refresh of all of the changed properties (by selecting thembefore click on ‘’Live Refresh’’) or restart the Maximo Server

5.5 Configure Maximo system properties

Sample screenshot of the Cognos’s properties setting

Sample screenshot of the Rest API’s property setting

Save and perform live refresh• In Property Name enter “cognos,rest.web”

• Check all properties

• Click Save

• Recheck all properties

• Perform Live Refresh

• Go to next page

Save and perform live refresh

• Check all properties

• Click Save

• Recheck all properties

• Perform Live Refresh

• 5.6.1 Check that the Cognos services are started

• 5.6.2 Launch Cognos Administration from the Maximo UI

• 5.6.3 Check security configuration

• 5.6.4 Configure the cognos datasource

• 5.6.5 Create the required folders in IBM Cognos Connection

• 5.6.6 Copy SDK files for metadata publishing

5.6 Configure Cognos datasource and folders

5.6.1 Check that the Cognos service is started


• Locate the ”IBM Cognos” service

• Check that is running

• Log into Maximo as maxadmin (password maxadmin)

• Go to “Administration -> Report Administration”

• In ”More action” click on ”Launch Cognos Administration”

5.6.2 Launch Cognos Administration

from the Maximo UI

• Go to the Security tab

5.6.3 Check security configuration

• Click on maximo

• Check that the list of the Maximo users is displayed

Check that Cognos may access to the maximo users list

5.6.4 Configure the Cognos data source

• Go to the Configuration tab

Create new data source

Test the connection

Click on Test

Check that no error are displayed and finish the test

5.6.5 Launch Cognos Connection

• Go to “Launch -> IBM Cognos Connection”

Create new folder

• On the Cognos installation server open Windows Internet Explorer

• In the Cognos installation directory create the folder My project\Metadata

(C:\IBM\cognos\My Projects\Metadata)

• In the IBM Cognos Connection console click on the ‘’New Folder’’ button

as shown in the picture below

Create the PUBLIC folder

• Stop the Cognos services



• Navigate to reports\cognos\C10\sdk (

C:\maximo\maximo\reports\cognos\C10\sdk )

• Copy the following jar files to the application server lib directory (

C:\IBM\WebSphere\AppServer\lib ):– cognos-axis.jar

– cognosClient.jarrestart websphere

• Start the Cognos services

5.6.6 Copy SDK files for metadata publishing

• 5.7.1 Set Maximo End Point properties

• 5.7.2 Publish Maximo Report Object Structures as Cognos

Metadata

• 5.6.3 Check security configuration

• 5.6.4 Configure the cognos datasource

• 5.6.5 Create the required folders in IBM Cognos Connection

• 5.6.6 Copy SDK files for metadata publishing

5.7 Configure Maximo Integration Framework

• Log into Maximo with the user maxadmin (password maxadmin)

• Go to ‘’Integration -> End Point’’

• Open the MXCOGNOS endpoint

• Set the appropriate properties value (case sensitive) – for a detaileddescription of the properties see the link https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM+Maximo+Asset+Management/page/Cognos+End+Point+Property+Settings :– Property name: CONTENT_STORE_PACKAGE_LOCATION Property value: PUBLIC

– Property name: DATA_SOURCE_NAME Property value: MXDB

– Property name: NAMESPACE_ID Property value: maximo

– Property name: PROJECT_BASE_DIR

Property value: C:\IBM\cognos\My Projects\Metadata

– Property name: URL

Property value: http://mx7vm:9300/p2pd/servlet/dispatch

– Property name: USENAME Property value: cognos

– Property name: PASSWORD Property value: cognos

• Save

5.7.1 Set Maximo End Point properties

Sample of End Point’s properties

• Log into Maximo as maxadmin (password maxadmin)

• Go to “Integration -> Object Structures”

• Filter list per “Consumed By” REPORTING

• Enter the REP_PERSON Report Object Structure record

• In “More action” click on “Publish as Cognos Package” (see screenshot on

next slide). Depending on the size of the ROS and the Network

Connection, the publishing time of the package will vary. Once it has been

completed successfully, a message will display (BMXAA7415E - Succeeded

in publishing the Object Structure as Cognos Package).

• Repeat the publishing action for all of the Object Structure consumed by

cognos (or by reporting if you don’t know which object structure are

dedicated to cognos and which to other reporting features)

5.7.2 Publish Maximo Report Object Structures

as Cognos Metadata

Publish as Cognos Package

Agenda

• 1. Overview






• Connect to the Maximo Administrative Workstation server


• Navigate to reports\cognos\Packages (

C:\maximo\maximo\reports\cognos\Packages )

• If you are using DB2 or Oracle, open the DB2_Oracle folder, If you are using

Sql Server, open the Sql Server folder

• Copy the zip file PublicMX76.zip in the deployment folder of Cognos (

C:\Program Files\ibm\cognos\c10_64\deployment ) on the Cognos

installation server

Copy packages data

• Open the Cognos adminstration console from the browser

(http://mx7vm:9080/ibmcognos)

• Enter a maximo administration user/password (e.g. maxadmin)

• Click on “Administer IBM Cognos Content”

Open the Cognos administration console

• Go To “Content Administration”

• Click on “New import”

Import content

Select Deployment archive

Description: Maximo 76 Reports and Workspaces - Workorder, Asset, Asset

Failure and Inventory

Insert Description

Select the folder

Confirm default paramenter

Confirm default paramenter

• Select “Save and run once”

• Click on “Finish”

Finish

Run Import

Click Ok to run the Import

Verify import results and click on close (verify that there are no failed objects )

• Verify that the nearly created folder exists and open it

Open IBM Cognos Connection

Verify folders presence

• Connect to your Maximo Administration workstation server


• Navigate to reports\cognos\images (

C:\maximo\maximo\reports\cognos\images )

• Copy the image folder to the webcontent\samples folder in Cognos

installation folder on the Cognos installation server (C:\Program

Files\ibm\cognos\c10_64 webcontent\samples )

• From the Maximo installation directory navigate to

reports\cognos\Models\Application Models(

C:\maximo\maximo\reports\cognos\Models\Application Models )

• If you are using DB2 or Oracle, open the DB2_Oracle folder, If you are

using Sql Server, open the Sql Server folder

• Unzip here all of the zip file in the folder

Copy Image file and Meta data model

Launch IBM Cognos Framework

Open a project

Navigate the Maximo Cognos Application models Asset unzipped folder to

open the *.cpf file

Select the project

Enter the credentials of a Maximo’s administrator user (maxadmin)

Insert credentials

• Select Data Sources -> MXDB in Project Viewer

• In the Properties enter MXDB in Content Manager Data Source and

MAXIMO in Schema

• Save

Configure Data Sources

• Right click on MXDB in Data Sources

• Select Test

• Check the result

Test the Data Sources

• Select Packages -> Asset Metric Details in Project Viewer

• Right click and select “Publish Packages”

Publish the package

Select folder location

Define security access

Check the flag for the package verification

Check the flag for errors view

Save

• Repeat the steps starting from “Open a project” for the following

packages:

– Asset Failure

– Inventory

– Work order

Additional packages to be published

There are two ways to launch the Cognos report from the Maximo UI:

• From th “Go to” menu “Go to -> Analytics -> Cognos Reporting”

• From the “More Action” menu of every application

Launch Cognos report from Maximo

• Navigate into the publicMX76 folder and then into the “Lauching Pages” folder

• Choose the desired set of reports

Navigate Cognos Report

Documents

Maximo 7.6 and Cognos 10.2.1 Integration · PDF fileMulti-server architecture List of the activitiesfor installationin a multi-server environment • Cognos Server – InstallDatabase