JR51149 IBM Business Monitor 8.0.1.3 interim fix dependency information and installation instructions:


1. Interim fix dependencies
===========================

Prerequisite APARs:
None

Superseded APARs:
None


2. Interim fix installation order (Installation Manager)
========================================================

JR51149
                               
                                                            
3. Interim Fix installation instructions                                   
==========================================

a. Stop the stand-alone server or network deployment environment.

b. Install JR51149 using steps that are documented in http://www-01.ibm.com/support/docview.wss?uid=swg21417656.

Note: Both 8.0.1.3-WS-WBM-IFJR51149 and 8.0.1.3-WS-MONCC-IFJR51149_MONCC must be applied to IBM Business Monitor installations.  
Only 8.0.1.3-WS-MONCC-IFJR51149_MONCC is required for Business Process Manager installations.

c. Start the stand-alone server or network deployment environment. 

          
4. Uninstall instructions
=========================

a. Stop the stand-alone server or network deployment environment.

b. Using IBM Installation Manager, uninstall JR51149.

c. Start the stand-alone server or network deployment environment.


5. Activating the change
========================

Note:  This solution only supports users.  Fine Grained Security filters defined as groups will be reported as errors 
and will not be applied to the Cognos security filters.

The table based fine grained security for Cognos solution requires no procedural changes in the creation of fine grained security
filters or in publishing cubes.   A JVM property is used to make the change from storing filters in the Cognos model to storing the
security filters in the new database table.

Set the following JVM property in the Admin Console to specify storing Cognos filters in the FGS_COGNOS_FILTER_T table:

	monitor.admin.cognos.finegrainedsecurity.tablebasedusers=true

A second JVM property is also provided for a use case of allowing the customer to maintain the FGS_COGNOS_FILTER_T manually or with 
an automated process.   Publishing cubes will update the Cognos model without making changes to the filter in the table:

	monitor.admin.cognos.finegrainedsecurity.tablebasedusers_nomaint=true

Note:  Only one of the JVM properties should be set.


6. Database Changes Required
=============================

JR51149 requires a new database table to be created.  The new table should be created in the MONITOR database and the schema created for the Monitor tables (not the model schema).

a.  DB2

	CREATE TABLE @SCHEMA@.FGS_COGNOS_FILTER_T
	(
	  USER_ID                            VARCHAR(128)                      NOT NULL ,
	  MODEL_ID                           VARCHAR(128)                      NOT NULL , 
	  MCID                               VARCHAR(128)                      NOT NULL , 
	  SECURITY_PREDICATE                 VARCHAR(4000)                     NOT NULL ,
	  PRIMARY KEY ( USER_ID, MODEL_ID, MCID )  
	) IN DSTS32K;

b.  DB2 z/OS
   
	CREATE TABLESPACE WBMON092 IN @DB_NAME@ 
	   USING STOGROUP @STOGRP@ 
	   BUFFERPOOL BP32K 
	   SEGSIZE 32
	   DEFINE NO
	   LOCKSIZE ROW
	   CCSID UNICODE;   

	CREATE TABLE @SCHEMA@.FGS_COGNOS_FILTER_T
	(
	  USER_ID VARCHAR(128) NOT NULL ,
	  MODEL_ID VARCHAR(128) NOT NULL , 
	  MCID VARCHAR(128) NOT NULL , 
	  SECURITY_PREDICATE  VARCHAR(4000) NOT NULL ,
	  PRIMARY KEY ( USER_ID, MODEL_ID, MCID )  
	) IN @DB_NAME@.WBMON092;

	CREATE UNIQUE INDEX
	  @SCHEMA@.FGS_COGNOS_FILTER_P ON
	  @SCHEMA@.FGS_COGNOS_FILTER_T
	( 
	  USER_ID, 
	  MODEL_ID, 
	  MCID
	) 
	USING STOGROUP @STOGRP@;

c.  Oracle

	CREATE TABLE @SCHEMA@.FGS_COGNOS_FILTER_T
	(
	  USER_ID                            VARCHAR(128)        NOT NULL ,
	  MODEL_ID                           VARCHAR(128)        NOT NULL , 
	  MCID                               VARCHAR(128)        NOT NULL , 
	  SECURITY_PREDICATE                 VARCHAR(4000)       NOT NULL 
	) TABLESPACE MONDSTS
	  LOGGING;

	ALTER TABLE @SCHEMA@.FGS_COGNOS_FILTER_T ADD
	(
	  PRIMARY KEY ( USER_ID, MODEL_ID, MCID )
	  USING INDEX TABLESPACE MONIDXTS
	);

d.  SQL Server

	CREATE TABLE @SCHEMA@.FGS_COGNOS_FILTER_T
	(
	    USER_ID                            NVARCHAR(128)                      NOT NULL ,
	    MODEL_ID                           NVARCHAR(128)                      NOT NULL , 
	    MCID                               NVARCHAR(128)                      NOT NULL , 
	    SECURITY_PREDICATE                 NVARCHAR(4000)                     NOT NULL ,
	    PRIMARY KEY ( USER_ID, MODEL_ID, MCID )  
	)