readme.txt 5.5 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122
  1. /**
  2. * Licensed Materials - Property of IBM
  3. *
  4. * IBM Cognos Products: CAMAAA
  5. *
  6. * (C) Copyright IBM Corp. 2005, 2019
  7. *
  8. * US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
  9. * IBM Corp.
  10. */
  11. There are two versions of the JDBC provider sample. The classic version does not support
  12. the new session failover capabilities of IBM Cognos that were introduced in 10.2.1.
  13. The restorable version can handle restoring a session after failover, and demonstrates the changes
  14. necessary to implement failover in your own custom provider.
  15. Before running these samples
  16. ----------------------------
  17. You will need an empty database to populate with users and groups. A database initialization script
  18. is provided for both IBM DB2 and Microsoft SQL server
  19. 1) Initialize your database with the appropriate script. See your database vendors
  20. documentation for the appropriate tool to import and run the script.
  21. - dbInit_db2.sql for IBM DB2
  22. - dbInit_sqlserver.swl for Microsoft SQL Server
  23. 2) Add at least one user to the USERS table. All fields are required and cannot be null.
  24. 3) Optionally, add at least one group to the GROUPS table. All fields are required and cannot be null.
  25. Running the IBM Cognos SDK custom authentication JDBC provider sample
  26. --------------------------------------------------------------------
  27. To configure and run the sample provided, please follow these steps:
  28. 1) Add the Java SDK to your path.
  29. 2) Build the sample using the command build.bat on Windows or
  30. build.sh on Unix.
  31. 3) Add the jar file to your IBM Cognos 10 classpath or copy the jar to
  32. <install>/webapps/p2pd/WEB-INF/lib.
  33. 4) Add the database driver jar file to your classpath or copy the files to
  34. <install>/webapps/p2pd/WEB-INF/lib.
  35. 5) Copy the JDBC configuration file to the <install>/configuration
  36. directory. Ensure that the name contains the namespaceID to be
  37. recognized (namespaceID is case sensitive).
  38. Ex:
  39. namespaceID = Sample1
  40. JDBC configurations file = JDBC_Config_Sample1.properties
  41. 6) Modify the content of the configuration file to point to your
  42. database server and specify the database username and password to use.
  43. 7) In IBM Cognos Configuration, configure the Custom Java namespace
  44. using the configuration tool, (the class name and NamespaceID
  45. are case sensitive):
  46. Type: Custom Java provider
  47. Namespace ID: Sample1
  48. Java class name: JDBCSample
  49. 8) Apply changes and restart IBM Cognos 10.
  50. The new authentication namespace should now appear in IBM Cognos 10 for
  51. logon and security administration tasks within IBM Cognos 10.
  52. NOTE: Should IBM Cognos 10 fail to start up once the new namespace
  53. is configured, please verify your configuration. IBM Cognos 10 will
  54. not start up if it cannot successfully communicate to the
  55. authentication source.
  56. Running the IBM Cognos SDK custom authentication RestorableJDBC provider sample
  57. --------------------------------------------------------------------
  58. To configure and run the sample provided, please follow these steps:
  59. 1) Add the Java SDK to your path.
  60. 2) Build the sample using the command build.bat on Windows or
  61. build.sh on Unix.
  62. 3) Add the jar file to your IBM Cognos 10 classpath or copy the jar to
  63. <install>/webapps/p2pd/WEB-INF/lib.
  64. 4) Add the database driver jar file to your classpath or copy the files to
  65. <install>/webapps/p2pd/WEB-INF/lib.
  66. 5) Copy the JDBC configuration file to the <install>/configuration
  67. directory. Ensure that the name contains the namespaceID to be
  68. recognized (namespaceID is case sensitive).
  69. Ex:
  70. namespaceID = Restorable
  71. JDBC configurations file = JDBC_Config_Restorable.properties
  72. 6) Modify the content of the configuration file to point to your
  73. database server and specify the database username and password to use.
  74. 7) In IBM Cognos Configuration, configure the Custom Java namespace
  75. using the configuration tool, (the class name and NamespaceID
  76. are case sensitive):
  77. Type: Custom Java provider
  78. Namespace ID: Restorable
  79. Java class name: RestorableJDBCSample
  80. 8) Apply changes and restart IBM Cognos 10.
  81. The new authentication namespace should now appear in IBM Cognos 10 for
  82. logon and security administration tasks within IBM Cognos 10.
  83. NOTE: Should IBM Cognos 10 fail to start up once the new namespace
  84. is configured, please verify your configuration. IBM Cognos 10 will
  85. not start up if it cannot successfully communicate to the
  86. authentication source.
  87. Configuring the IBM Cognos SDK custom authentication JDBC provider sample for Multi-Tenancy
  88. -------------------------------------------------------------------------------------------
  89. To configure and run the sample with Multi-Tenancy enabled, please follow these steps:
  90. 1) Configure either the JDBC or RestorableJDBC provider sample as described in steps 1 - 7
  91. above.
  92. 2) In IBM Cognos Configuration, select the Custom Java namespace in the left pane. In the
  93. right pane, click to edit the "Advanced properties". Add the following properties:
  94. multitenancy.TenantPattern ~/parameters/tenant
  95. NOTE: it will be necessary to set the TENANT in the users table to an appropriate value
  96. for each user.
  97. 3) Apply changes and restart IBM Cognos 10.
  98. Please refer to Tenant Patterns within the Multi-Tenancy product documentation for details.