CAM-CRP-1085 when running cogconfig.sh on UNIX

IBM Cognos Configuration displays an error when attempting to start on UNIX. The option when receiving the error is to exit the application.

Error Message:

CAM-CRP-1085 An error occurred while verifying that the security provider classes were loaded.
Reason: java.lang.ClassNotFoundException: org.bouncycastle125.jce.provider.BouncyCastleProvider

The error with IBM Cognos 8.4 will be:

CAM-CRP-1085 An error occurred while verifying that the security provider classes were loaded.
Reason: java.lang.ClassNotFoundException: org.bouncycastle134.jce.provider.BouncyCastleProvider

Root Cause:

An Operating System user, other than the one launching IBM Cognos Configuration was used to copy the cryptographic jar files from beneath the /bin/jre/1.X.X/lib/ext directory, to the /lib/ext folder. The files that were copied into the new directory were left with file permissions that prevented read access to anyone but the User that copied the files.

The inability for the user launching IBM Cognos Configuration to access the files, prevents the application from using them.

Solution:

Ensure that all the files and sub-directories referenced by the JAVA_HOME environment variable are readable by the user running cogconfig.sh.

CAM-CRP-1085 when running cogconfig.sh on UNIX

IBM Cognos Configuration displays an error when attempting to start on UNIX. The option when receiving the error is to exit the application.

Error Message:

CAM-CRP-1085 An error occurred while verifying that the security provider classes were loaded.
Reason: java.lang.ClassNotFoundException: org.bouncycastle125.jce.provider.BouncyCastleProvider

The error with IBM Cognos 8.4 will be:

CAM-CRP-1085 An error occurred while verifying that the security provider classes were loaded.
Reason: java.lang.ClassNotFoundException: org.bouncycastle134.jce.provider.BouncyCastleProvider

Root Cause:

An Operating System user, other than the one launching IBM Cognos Configuration was used to copy the cryptographic jar files from beneath the /bin/jre/1.X.X/lib/ext directory, to the /lib/ext folder. The files that were copied into the new directory were left with file permissions that prevented read access to anyone but the User that copied the files.

The inability for the user launching IBM Cognos Configuration to access the files, prevents the application from using them.

Solution:

Ensure that all the files and sub-directories referenced by the JAVA_HOME environment variable are readable by the user running cogconfig.sh.

SDK - Bad version number in .class file

An error occurs trying to implement the SDK sample TrustedSignonSample.

Error Message:

[ ERROR ] CAM-AAA-0064 The function 'CAM_AAA_JniAuthProvider::Configure' failed.
CAM-AAA-0154 Unable to load the Java authentication provider class 'TrustedSignonSample'.
Bad version number in .class file


Root Cause:

This error will occur when compiling with JDK 1.6 when Cognos 8.4 is using 1.5.

Solution:

Use JDK version 1.5 to build the classes and JAR file.

Steps:

example build.bat

@echo off

rem Copyright ? 2008 Cognos ULC, an IBM Company. All Rights Reserved.
rem Cognos and the Cognos logo are trademarks of Cognos ULC (formerly Cognos Incorporated).

rem Build Java files in directory TrustedSignonSample

echo Building TrustedSignonSample

rem Build the CLASSPATH required to build Java files in the directory TrustedSignonSample

set _CLASSPATH=..\lib\CAM_AAA_CustomIF.jar;..\adapters

rem Compile Java files
D:\jdk1.5.0_11\bin\javac -classpath %_CLASSPATH% -d . *.java

rem Create jar file
D:\jdk1.5.0_11\bin\jar cfm0 CAM_AAA_TrustedSignonSample.jar MANIFEST *.class

echo done

SDK - Bad version number in .class file

An error occurs trying to implement the SDK sample TrustedSignonSample.

Error Message:

[ ERROR ] CAM-AAA-0064 The function 'CAM_AAA_JniAuthProvider::Configure' failed.
CAM-AAA-0154 Unable to load the Java authentication provider class 'TrustedSignonSample'.
Bad version number in .class file


Root Cause:

This error will occur when compiling with JDK 1.6 when Cognos 8.4 is using 1.5.

Solution:

Use JDK version 1.5 to build the classes and JAR file.

Steps:

example build.bat

@echo off

rem Copyright ? 2008 Cognos ULC, an IBM Company. All Rights Reserved.
rem Cognos and the Cognos logo are trademarks of Cognos ULC (formerly Cognos Incorporated).

rem Build Java files in directory TrustedSignonSample

echo Building TrustedSignonSample

rem Build the CLASSPATH required to build Java files in the directory TrustedSignonSample

set _CLASSPATH=..\lib\CAM_AAA_CustomIF.jar;..\adapters

rem Compile Java files
D:\jdk1.5.0_11\bin\javac -classpath %_CLASSPATH% -d . *.java

rem Create jar file
D:\jdk1.5.0_11\bin\jar cfm0 CAM_AAA_TrustedSignonSample.jar MANIFEST *.class

echo done

Incorrect Filters When Users Drill Through to Upgraded 8.4 GA Targets in Analysis Studio

If the target of a drill-through definition is an Analysis Studio report with a drill-through filter, and
the application has been upgraded from IBM Cognos 8 version 8.3 to IBM Cognos 8 version 8.4,
then filters may not be correctly passed from the source to the target. Instead, the Analysis Studio
report appears with the authored settings unchanged, or users may be prompted to select a context.
This is true for authored drill-through definitions (created in a Report Studio report) and package
drill-through definitions (created in Cognos Connection) that use parameterized drill through.


Environment:

Drill through reports upgraded from 8.3 to 8.4 GA

Root Cause:

This problem occurs because of changes in how parameters are automatically named in Analysis
Studio.

Solution:

To correct the problem, recreate the mapping in the drill-through definition, and save the
definition.


Steps:

Steps for Authored Drill Through
1. In Report Studio, Professional Authoring, open the source report.
2. Select the report item that contains the drill-through definition.
3. From the Properties pane, open the drill-through definition (Data, Drill-Through Definitions).
4. From the Drill-Through Definitions window, open the Parameters table, and re-select the target
parameter(s).
5. Save the drill-through definition settings and then save the report.
6. Test the drill through to confirm that the problem is resolved.
For more information, see the Report Studio Professional Authoring User Guide.

Steps for Package Drill Through
1. In IBM Cognos Connection, launch Drill-through Definitions.
2. Navigate to the root of the source package, locate the drill-through definition to be updated,
and click Set Properties.
3. In the Target tab, under Parameter mapping, re-select the target parameters.
4. Save the drill-through definition.
5. Test the drill through to confirm that the problem is resolved.
For more information, see the IBM Cognos 8 BI Administration and Security Guide.