TSPM reporting setup corrections

Technote (troubleshooting)


Problem(Abstract)

TSPM 7.1 Setting up the reporting environment corrects/enhancements to documentation.

Resolving the problem

Setting up the reporting environment

To prepare Tivoli® Security Policy Manager to generate operational reports, you must set up the reporting environment properly.

Before you begin

Ensure that you have installed Tivoli Integrated Portal (TIP). Tivoli Common Reporting is installed as part of TIP.

Ensure that you have installed IBM® DB2® Workgroup Server Edition Version 9.5 or 9.7.
About this task
Several of the steps in this process require information from the Tivoli Common Reporting User's Guide. You can find this information in the following locations:

The tcr_users_guide.pdf file on the reporting installation media that is included with Tivoli Security Policy Manager.
The Tivoli Information Center at: http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tivoli.tcr.doc/tcr_users_guide_book.pdf

Procedure
1. Stop the Tivoli Integrated Portal Server.
2. Configure the database. See Configuring the database for reports for information.
3. Install the DB2 database drivers into Tivoli Common Reporting. See Installing the database drivers for the report set for information.
4. Start the Tivoli Integrated Portal server.
5. Log in to Tivoli Common Reporting. See "Administering Tivoli Common Reporting" in the Tivoli Common Reporting User's Guide for information.
6. Import the Tivoli Security Policy Manager report package into Tivoli Common Reporting. See Importing the report package for information.
7. Configure the Tivoli Common Reporting data source to access the report data. See Configuring the data sources for the report set for information.
What to do next
Run the reports. See Running reports for information.

*****************
next appears to be configuringDBReport.html

******************
Configuring the database for reports
To run the Tivoli® Security Policy Manager reports, you must deliver stored procedures to the database. Furthermore, for these procedures to work, you must deploy two additional commands to the database.

Before you begin

Ensure you are using the same database for this task that Tivoli Security Policy Manager uses. For example, if the database you set up is called TSPM, use this same one for the reports.
Ensure you connect to the database using the same DB2® instance owner you specified when you configured the database for Tivoli Security Policy Manager. This is the username specified for the data source with the JNDI name jdbc/tytoxa.
Procedure
1. From your database system, navigate to DB2_installation_directory/bin.
2. For the next steps you'll need to utilize the db2 command for your given OS as DB owner (db2inst for example.) :
AIX®, Linux, and Solaris: db2
Windows: db2cmd.exe
3. Run the following commands to the database:
a. db2 connect to database with user username
Where database is the name of the database being used with Tivoli Security Policy Manager, and username is the username used when configuring the policy database. This user must have DBADM privileges on the database.
b. db2 create bufferpool rmaabp1 immediate size 2000 pagesize 32k
c. db2 create tablespace rmaa_big pagesize 32k managed by system using ('storage_folder') bufferpool rmaabp1
Where storage_folder is a new folder location, which does not already exist, on the file system. Do not use a temporary folder.
d. db2 -td@ -vf TSPMReports.sql
The TSPMReports.sql file is in the TSPM_installation_directory/reports directory.
4. Verify that there are four new stored procedures on your database:
CREATEALL
CREATERELATIONTABLE
ENTITYREPORT
FILLALL
What to do next
Install the database drivers. See Installing the database drivers for the report set .

**********************
and finally dbDriversReport.html
********************
Installing the database drivers for the report set
For the runtime report engine (BIRT) to access data in a DB2® instance, you must install the DB2 JDBC drivers to connect to the database.

About this task
This task describes how to copy the JDBC drivers to the Tivoli® Common Reporting directory. Tivoli Security Policy Manager includes these JDBC drivers as part of the product installation package. Tivoli Common Reporting uses the drivers to connect to the data source.
Procedure

1. Locate the db2jcc.jar and db2jcc_license_cu.jar JDBC driver files. These files are included on the DB2 installation DVD and are installed as part of the DB2 product installation. You can find these two files in the /java directory of the DB2 installation. The following table shows examples of locations for these files:

Operating system
Example directory location
Table 1. Examples of locations for db2jcc.jar and db2jcc_license_cu.jar files
Linux (version 9.5) /opt/ibm/db2/V9.5/java/
Windows C:\Program Files\IBM\SQLLIB\java
2. Copy the db2jcc.jar and db2jcc_license_cu.jar JDBC driver files into the BIRT drivers directory.
This directory is typically located relative to the Tivoli Common Reporting installation directory at: % TIP_installation_directory%/products/tcr/lib/birt-runtime-2_2_1/ReportEngine/plugins/org.eclipse.birt.report.data.oda.jdbc_2.2.1.r22x_v20070919/drivers

3. Copy the db2jcc.jar and db2jcc_license_cu.jar JDBC driver files to % TIP_installation_directory%/products/tcr/lib/. This makes the JDBC drivers available to the classes in TSPMReportsLib.jar.
What to do next
Refer to Setting up the reporting environment for the next step in the process.

Rate this page:

(0 users)Average rating

Add comments

Document information


More support for:

Tivoli Security Policy Manager
Policy Manager

Software version:

7.1

Operating system(s):

AIX, Linux xSeries, Solaris, Windows

Reference #:

1611576

Modified date:

2012-09-19

Translate my page

Machine Translation

Content navigation