BAM includes, and makes use, of Cognos Business Intelligence 10.1 ( aka Cognos BI ), which is installed with the product.
Cognos BI runs, in this particular instance, on one of the WebSphere Application Server (WAS) instances that forms the BAM infrastructure.
In my case, I'm following good practice for scalability and resilience by deploying BAM in the so-called "Gold Standard' deployment pattern, similar to IBM Business Process Manager.
This involves BAM ( or BPM ) being clustered across four discrete WAS instances: -
Messaging engine cluster
Business Space application
- Messaging engine for the IBM Business Monitor bus
- Messaging engine for the common event infrastructure (CEI) bus
Support cluster
- CEI event service
- Event emitter services
- Action services
- Monitor scheduled services
- IBM Cognos Business Intelligence service
Application cluster
- Monitor model applications Web cluster
Business Space application
- Business Space widgets
- Representational State Transfer (REST) services application
and is known as the "Remote Messaging, Remote Support, and Web topology pattern".
The IBM documentation: -
explains this, and other topologies, further.
So, as is evident from above, Cognos is deployed onto the Support cluster.
I had assumed that Cognos would be a well-behaved client of WAS, and make use of JNDI and JDBC to connect, via WAS, to it's underlying database - COGNOSCS.
However, now I'm not quite so sure.
I have already blogged about the need to configure WAS to make use of the 32-bit native DB2 drivers: -
and thought that was all I had to do.
However, I spent the best part of a day struggling to work out why Cognos wouldn't fully start.
In terms of logging, apart from the WAS SystemOut.log file: -
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/logs/PCSR011.Support/SystemOut.log
Cognos also has its own set of logs: -
$ ls -al /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/cognos/PCSR011.Support/logs
total 44
drwxr-xr-x 3 wasadmin mqbrkrs 4096 Mar 2 17:08 .
drwxr-xr-x 30 wasadmin mqbrkrs 4096 Feb 8 14:04 ..
-rw-r--r-- 1 wasadmin wasadmins 1401 Mar 3 09:40 cmMetrics_2013-03-02.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:06 cogconfigipf.log
-rw-r--r-- 1 wasadmin wasadmins 1729 Mar 2 17:06 cogconfig_response.csv
-rw-r--r-- 1 wasadmin wasadmins 311 Mar 2 17:07 cogserver_default_55087.log
-rw-r--r-- 1 wasadmin wasadmins 155 Mar 2 17:08 cogserver_default_55441.log
-rw-r--r-- 1 wasadmin wasadmins 6504 Mar 2 17:09 cogserver.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:06 ipfInternal_cpp.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:06 ipfInternal_java.log
-rw-r--r-- 1 wasadmin wasadmins 7870 Mar 3 07:48 pogo_2013-03-02.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:07 pogoMetrics_2013-03-02.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:08 qs_cmMetrics_2013-03-02.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:08 qs_pogo_2013-03-02.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:08 qs_pogoMetrics_2013-03-02.log
drwxr-xr-x 4 wasadmin wasadmins 4096 Mar 2 17:08 XQE
drwxr-xr-x 30 wasadmin mqbrkrs 4096 Feb 8 14:04 ..
-rw-r--r-- 1 wasadmin wasadmins 1401 Mar 3 09:40 cmMetrics_2013-03-02.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:06 cogconfigipf.log
-rw-r--r-- 1 wasadmin wasadmins 1729 Mar 2 17:06 cogconfig_response.csv
-rw-r--r-- 1 wasadmin wasadmins 311 Mar 2 17:07 cogserver_default_55087.log
-rw-r--r-- 1 wasadmin wasadmins 155 Mar 2 17:08 cogserver_default_55441.log
-rw-r--r-- 1 wasadmin wasadmins 6504 Mar 2 17:09 cogserver.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:06 ipfInternal_cpp.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:06 ipfInternal_java.log
-rw-r--r-- 1 wasadmin wasadmins 7870 Mar 3 07:48 pogo_2013-03-02.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:07 pogoMetrics_2013-03-02.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:08 qs_cmMetrics_2013-03-02.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:08 qs_pogo_2013-03-02.log
-rw-r--r-- 1 wasadmin wasadmins 0 Mar 2 17:08 qs_pogoMetrics_2013-03-02.log
drwxr-xr-x 4 wasadmin wasadmins 4096 Mar 2 17:08 XQE
More specifically: -
$ cat cogconfig_response.csv
INFO, "[main]", "Silent Execution Mode (start)"
EXEC, "[main]", "Loading configuration file"
SUCCESS, "[main]", "Completed successfully."
EXEC, "[Validation]", "Checking for errors and configuration integrity"
SUCCESS, "[Validation]", "Completed successfully."
EXEC, "[Cryptography]", "Generating cryptographic information"
SUCCESS, "[Cryptography]", "Completed successfully."
EXEC, "[Data Encryption]", "Checking integrity of encrypted data"
SUCCESS, "[Data Encryption]", "Completed successfully."
EXEC, "[Backup]", "Backing up configuration files"
SUCCESS, "[Backup]", "Completed successfully."
EXEC, "[Save Configuration]", "Saving configuration parameters"
SUCCESS, "[Save Configuration]", "Completed successfully."
EXEC, "[Checking upgrade status]", "Checking upgrade status"
SUCCESS, "[Checking upgrade status]", "Completed successfully."
EXEC, "[Cryptography]", "Generating cryptographic information"
SUCCESS, "[Cryptography]", "Completed successfully."
EXEC, "[''VMMAuth'']", "Testing ''WBM_Provider'' namespace."
SUCCESS, "[''VMMAuth'']", "Completed successfully."
EXEC, "[Trust Root Test]", "Checking for same Trust Root."
SUCCESS, "[Trust Root Test]", "Completed successfully."
EXEC, "[CSK Request Test]", "Checking CSK availability."
SUCCESS, "[CSK Request Test]", "Completed successfully."
EXEC, "[Content Manager database connection]", "Testing Content Manager database connection."
ERROR, "[Content Manager database connection]", "The database connection failed."
ERROR, "[Content Manager database connection]", "Content Manager failed to start because it could not load driver "com.ibm.db2.jcc.DB2Driver"."
FAILURE, "[Content Manager database connection]", "Failed."
INFO, "[main]", "Silent Execution Mode (end)"
and: -
$ cat cogserver.log
127.0.0.1:9081 63902 2013-02-08 16:29:02.408 +0 server.startup : 1 LOGSV 6235 1 server.Audit.IPF StartService LogService Success <parameters><item name="Port"><![CDATA[9381]]></item><item name="Mode"><![CDATA[UDP]]></item><item name="Secure"><![CDATA[FALSE]]></item></parameters>
127.0.0.1:9081 63902 2013-02-08 16:29:22.361 +0 Initialization_SESS Initialization_REQ Thread-54 CM 6235 1 Audit.cms.CM StartService ContentManagerService Info CM-SYS-2057 Creating content store tables (schema version 6.0022).
127.0.0.1:9081 63902 2013-02-08 16:31:56.905 +0 Initialization_SESS Initialization_REQ Thread-54 CM 6235 1 Audit.cms.CM StartService ContentManagerService Info CM-SYS-2215 A Content Manager internal PRECACHEINITACTIONS task started.
127.0.0.1:9081 63902 2013-02-08 16:31:56.967 +0 Initialization_SESS Initialization_REQ Thread-54 CM 6235 1 Audit.cms.CM StartService ContentManagerService Info CM-SYS-2216 A Content Manager internal PRECACHEINITACTIONS task is complete.
127.0.0.1:9081 63902 2013-02-08 16:31:57.103 +0 Initialization_SESS Initialization_REQ Thread-54 CM 6235 1 Audit.cms.CM StartService ContentManagerService Info CM-SYS-2215 A Content Manager internal POSTINITACTIONS task started.
127.0.0.1:9081 63902 2013-02-08 16:31:57.389 +0 Initialization_SESS Initialization_REQ Thread-54 CM 6235 1 Audit.cms.CM StartService ContentManagerService Info CM-SYS-2216 A Content Manager internal POSTINITACTIONS task is complete.
127.0.0.1:9081 63902 2013-02-08 16:32:16.391 +0 Initialization_SESS Initialization_REQ Thread-54 CM 6235 1 Audit.RTUsage.cms.CM StartService ContentManagerService Info CM-SYS-2215 A Content Manager internal CMUPGRADESCRIPT task started.
127.0.0.1:9081 63902 2013-02-08 16:32:17.257 +0 Thread-54 CM 6235 1 Audit.RTUsage.cms.CM StartService ContentManagerService Success CM-SYS-5090 Content Manager build 10.1.6235.601 started (None;20110713180135, schema version 6.0022, implementation: CMDbStore - Java CMCache).
127.0.0.1:9081 63902 2013-02-08 16:32:17.257 +0 Thread-54 CM 6235 1 Audit.RTUsage.cms.CM StartService ContentManagerService InfCM-SYS-5159 Content Manager is running in active mode.
127.0.0.1:9081 63902 2013-02-08 16:32:19.456 +0 pogoStartup na na 0 Thread-54 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService relationalMetadataService Success
127.0.0.1:9081 63902 2013-02-08 16:32:19.588 +0 pogoStartup na na 0 Thread-54 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.contentmanager.coordinator.CMBootstrap getActiveContentManager ContentManager Failure <messages><message><messageString>DPR-CMI-4006 Unable to determine the active Content Manager. Will retry periodically.</messageString></message></messages>
127.0.0.1:9081 63902 2013-02-08 16:32:19.605 +0 pogoStartup na na 0 Thread-54 DISP 6235 1 Audit.Other.dispatcher.DISP.pogo pogo com.cognos.pogo.contentmanager.coordinator.ActiveCMControl Failure <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message><message><messageString>DPR-DPR-1004 Expecting a BI Bus XML response but got: </messageString></message></messages> DPR-CMI-4007 Unable to perform an active Content Manager election on the local IP node. For more information, see the dispatcher and Content Manager detailed logs. Ensure that the local Content Manager service is started.DPR-DPR-1004 Expecting a BI Bus XML response but got: com.cognos.pogo.bibus.CommandExecutionException: DPR-DPR-1004 Expecting a BI Bus XML response but got: at com.cognos.pogo.bibus.BIBusCommand.handleDefaultException(BIBusCommand.java:294) at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:194at com.cognos.pogo.contentmanager.StandbyContentManagerElectionCommand.executeIfLocal(StandbyContentManagerElectionCommand.java:53) at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl.sendElectCommand(ActiveCMControl.java:230) at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl.startTimer(ActiveCMControl.java:175) at com.cognos.pogo.contentmanager.coordinator.ActiveCMControl.startupFindCM(ActiveCMControl.java:142) at com.cognos.pogo.contentmanager.coordinator.RuntimeInfoPublishHandler.start(RuntimeInfoPublishHandler.java:113) at com.cognos.pogo.services.DefaultHandlerService.start(DefaultHandlerService.java:94) at com.cognos.pogo.services.DispatcherServices.startInititalServices(DispatcherServices.java:388) at com.cognos.pogo.transport.PogoServlet$PogoStartup.run(PogoServlet.java:690) at com.cognos.pogo.util.threads.SafeThread.safeRun(SafeThread.java:70) at com.cognos.pogo.util.threads.SafeThread.run(SafeThread.java:61)Caused by: com.cognos.pogo.bibus.CommandExecutionException: DPR-DPR-1004 Expecting a BI Bus XML response but got: at com.cognos.pogo.bibus.BIBusCommand.checkResponseContentType(BIBusCommand.java:326) at com.cognos.pogo.bibus.BIBusCommand.getSinglePartInputStream(BIBusCommand.java:273) at com.cognos.pogo.bibus.BIBusCommand.getInputStream(BIBusCommand.java:259) at com.cognos.pogo.bibus.BIBusCommand.parseResponse(BIBusCommand.java:248) at com.cognos.pogo.bibus.BIBusCommand.processResponse(BIBusCommand.java:242) at com.cognos.pogo.bibus.BIBusCommand.executeCommand(BIBusCommand.java:204) at com.cognos.pogo.bibus.BIBusCommand.execute(BIBusCommand.java:190) ... 10 more
127.0.0.1:9081 63902 2013-02-08 16:49:51.894 +0 na na stopper-runTimeInfoPublisher DISP 6235 1 Audit.Other.dispatcher.DISP.pogo pogo com.cognos.pogo.services.DefaultHandlerService Failure <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message><message><messageString>null</messageString></message></messages> problem stopping handler runTimeInfoPublishernulljava.lang.NullPointerException at com.cognos.pogo.contentmanager.coordinator.RuntimeInfoPublishHandler.stopAciveCMChecking(RuntimeInfoPublishHandler.java:273) at com.cognos.pogo.contentmanager.coordinator.RuntimeInfoPublishHandler.stop(RuntimeInfoPublishHandler.java:124) at com.cognos.pogo.services.DefaultHandlerService.stop(DefaultHandlerService.java:168) at com.cognos.pogo.services.DispatcherServices$ServiceStopper.safeRun(DispatcherServices.java:335) at com.cognos.pogo.util.threads.SafeThread.run(SafeThread.java:61)
127.0.0.1:9081 63902 2013-02-08 16:49:51.894 +0 shutdown na na 0 Non-deferrable Alarm : 2 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StopService CPS Producer Registration Service Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.101 +0 stopper-eventManagementService EMS 6235 1 Audit.ems.EMS StopService EventService Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.103 +0 shutdown na na 0 Non-deferrable Alarm : 2 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StopService MetadataService Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.111 +0 stopper-jobService JOBS 6235 1 Audit..JOBS StopService JobService Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.115 +0 shutdown na na 0 Non-deferrable Alarm : 2 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StopService DimensionManagementService Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.165 +0 stopper-monitorService MS 6235 1 Audit.ms.MS StopService MonitorService Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.169 +0 shutdown na na 0 Non-deferrable Alarm : 2 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StopService ReportService Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.173 +0 shutdown na na 0 Non-deferrable Alarm : 2 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StopService ContentManagerCacheService Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.177 +0 shutdown na na 0 Non-deferrable Alarm : 2 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StopService CacheService Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.177 +0 shutdown na na 0 Non-deferrable Alarm : 2 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StopService camAsyncAA Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.178 +0 shutdown na na 0 Non-deferrable Alarm : 2 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StopService IBM Cognos Enhanced Search Service Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.179 +0 shutdown na na 0 Non-deferrable Alarm : 2 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StopService ReportDataService Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.187 +0 shutdown na na 0 Non-deferrable Alarm : 2 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StopService GraphicsService Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.193 +0 na na stopper-graphicsService DISP 6235 1 Audit.Other.dispatcher.DISP.pogo pogo com.cognos.pogo.services.DefaultHandlerService Failure <messages><message><messageString>DPR-DPR-1035 Dispatcher detected an error.</messageString></message><message><messageString>null</messageString></message></messages> problem stopping handler graphicsServiceHandlernulljava.lang.NullPointerException at com.ibm.cgsBus.service.GraphicsServiceHandler.stop(Unknown Source) at com.cognos.pogo.services.DefaultHandlerService.stop(DefaultHandlerService.java:168) at com.cognos.pogo.services.DispatcherServices$ServiceStopper.safeRun(DispatcherServices.java:335) at com.cognos.pogo.util.threads.SafeThread.run(SafeThread.java:61)
127.0.0.1:9081 63902 2013-02-08 16:49:52.196 +0 shutdown na na 0 Non-deferrable Alarm : 2 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StopService SystemService Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.197 +0 shutdown na na 0 Non-deferrable Alarm : 2 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StopService buxService Success
127.0.0.1:9081 63902 2013-02-08 16:49:52.223 +0 stopper-logService LOGSV 6235 1 server.Audit.IPF StopService LogService Success <parameters><item name="Port"><![CDATA[9381]]></item><item name="Mode"><![CDATA[UDP]]></item><item name="Secure"><![CDATA[FALSE]]></item></parameters>
So, thus far, I've not managed to get to the bottom of why Cognos appears to have an issue with DB2, given that WAS is connecting quite happily using JNDI/JDBC.
As per the aforementioned blog post: -
I thought I'd fixed the core issue of allowing Cognos access to the native 32-bit JDBC driver, by setting LD_LIBRARY_PATH to: -
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/cognos/PCSR011.Support/bin64:/opt/ibm/db2/V9.7/lib32/
but it's still not happy, as can be seen above.
In addition, I was seeing the following exception: -
DPR-ERR-2109 The dispatcher cannot service the request at this time. The dispatcher is still initializing. Contact administrator if this problem persists.
when attempting to access the Cognos Dispatcher URL: -
Despite reading scores of IBM documentation: -
In the end, I looked back through a design document that I'd recently written for an IBM Business Monitor client, who's actually using Oracle rather than DB2, where I'd recommended that they use Dynamic Query Mode, which makes full use of WAS' own JDBC driver, rather than needing a native, client-side driver.
This Technote describes this more fully: -
but, in essence, it's a matter of setting a generic JVM argument ( for the Support cluster member ): -
-Dinit.dqm.enabled=true
and restarting the cluster member.
Having done this, I still see: -
<snip>
EXEC, "[Content Manager database connection]", "Testing Content Manager database connection."
ERROR, "[Content Manager database connection]", "The database connection failed."
ERROR, "[Content Manager database connection]", "Content Manager failed to start because it could not load driver "com.ibm.db2.jcc.DB2Driver"."
FAILURE, "[Content Manager database connection]", "Failed."
</snip>
ERROR, "[Content Manager database connection]", "The database connection failed."
ERROR, "[Content Manager database connection]", "Content Manager failed to start because it could not load driver "com.ibm.db2.jcc.DB2Driver"."
FAILURE, "[Content Manager database connection]", "Failed."
</snip>
in cogconfig_response.csv, but Cognos now behaves itself perfectly, as per conserver.log: -
$ cat cogserver.log
127.0.0.1:9081 55087 2013-03-02 17:07:19.386 +0 server.startup : 0 LOGSV 6235 1 server.Audit.IPF StartService LogService Success <parameters><item name="Port"><![CDATA[9381]]></item><item name="Mode"><![CDATA[UDP]]></item><item name="Secure"><![CDATA[FALSE]]></item></parameters>
127.0.0.1:9081 55087 2013-03-02 17:07:27.722 +0 Initialization_SESS Initialization_REQ Thread-54 CM 6235 1 Audit.cms.CM StartService ContentManagerService Info CM-SYS-2215 A Content Manager internal PRECACHEINITACTIONS task started.
127.0.0.1:9081 55087 2013-03-02 17:07:27.976 +0 Initialization_SESS Initialization_REQ Thread-54 CM 6235 1 Audit.cms.CM StartService ContentManagerService Info CM-SYS-2215 A Content Manager internal POSTINITACTIONS task started.
127.0.0.1:9081 55087 2013-03-02 17:07:27.725 +0 Initialization_SESS Initialization_REQ Thread-54 CM 6235 1 Audit.cms.CM StartService ContentManagerService Info CM-SYS-2216 A Content Manager internal PRECACHEINITACTIONS task is complete.
127.0.0.1:9081 55087 2013-03-02 17:07:28.072 +0 Initialization_SESS Initialization_REQ Thread-54 CM 6235 1 Audit.cms.CM StartService ContentManagerService Info CM-SYS-2216 A Content Manager internal POSTINITACTIONS task is complete.
127.0.0.1:9081 55087 2013-03-02 17:07:28.238 +0 Initialization_SESS Initialization_REQ Thread-54 CM 6235 1 Audit.cms.CM StartService ContentManagerService Info CM-SYS-2215 A Content Manager internal CMUPGRADESCRIPT task started.
127.0.0.1:9081 55087 2013-03-02 17:07:28.911 +0 Thread-54 CM 6235 1 Audit.RTUsage.cms.CM StartService ContentManagerService Success CM-SYS-5090 Content Manager build 10.1.6235.601 started (None;20110713180135, schema version 6.0022, implementation: CMDbStore - Java CMCache).
127.0.0.1:9081 55087 2013-03-02 17:07:28.913 +0 Thread-54 CM 6235 1 Audit.RTUsage.cms.CM StartService ContentManagerService InfCM-SYS-5159 Content Manager is running in active mode.
127.0.0.1:9081 55087 2013-03-02 17:07:29.357 +0 pogoStartup na na 0 Thread-54 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService relationalMetadataService Success
127.0.0.1:9081 55087 2013-03-02 17:07:29.587 +0 BootstrapConfigurePublish na 0 Thread-54 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.contentmanager.coordinator.CMBootstrap StartService dispatcherBootstrap Info DPR-DPR-1002 Successfully registered the dispatcher http://rhel6.uk.ibm.com:9081/p2pd in Content Manager.
127.0.0.1:9081 55087 2013-03-02 17:08:03.321 +0 Thread-76 AAA 6235 1 Audit.cms.CAM.AAA StartService camAsyncService Success
127.0.0.1:9081 55087 2013-03-02 17:08:14.125 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService Fragment Server Service Success
127.0.0.1:9081 55087 2013-03-02 17:08:14.129 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService BatchReportService Success
127.0.0.1:9081 55087 2013-03-02 17:08:14.131 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.async.service.connection.bibustkserver.BIBusTKServerManager Start com.cognos.pogo.reportservice Info Start a External Process because the start count 1 is larger than 0.
127.0.0.1:9081 55087 2013-03-02 17:08:39.399 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService QueryService Success
127.0.0.1:9081 55087 2013-03-02 17:08:39.903 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService SystemService Success
127.0.0.1:9081 55087 2013-03-02 17:08:39.902 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService buxService Success
127.0.0.1:9081 55087 2013-03-02 17:08:46.171 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService GraphicsService Success
127.0.0.1:9081 55087 2013-03-02 17:08:46.281 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService ReportDataService Success
127.0.0.1:9081 55087 2013-03-02 17:08:51.733 +0 Thread-76 xts 6235 1 Audit.ps.xts Upgrade PresentationService Success PRS-ACF-0413 Successfully wrote the upgraded cogadmin/system.xml file.
127.0.0.1:9081 55087 2013-03-02 17:09:00.803 +0 Thread-76 xts 6235 1 Audit.ps.xts StartService PresentationService Success
127.0.0.1:9081 55087 2013-03-02 17:09:00.804 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService IBM Cognos Enhanced Search Service Success
127.0.0.1:9081 55087 2013-03-02 17:09:00.804 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService camAsyncAA Success
127.0.0.1:9081 55087 2013-03-02 17:09:00.808 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService CacheService Success
127.0.0.1:9081 55087 2013-03-02 17:09:00.808 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService ContentManagerCacheService Success
127.0.0.1:9081 55087 2013-03-02 17:09:00.985 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService ReportService Success
127.0.0.1:9081 55087 2013-03-02 17:09:01.008 +0 Thread-76 MS 6235 1 Audit.ms.MS StartService MonitorService Success
127.0.0.1:9081 55087 2013-03-02 17:09:01.008 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService DimensionManagementService Success
127.0.0.1:9081 55087 2013-03-02 17:09:01.009 +0 Thread-76 JOBS 6235 1 Audit..JOBS StartService JobService Success
127.0.0.1:9081 55087 2013-03-02 17:09:01.289 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService MetadataService Success
127.0.0.1:9081 55087 2013-03-02 17:09:01.434 +0 Thread-76 EMS 6235 1 Audit.ems.EMS StartService EventService Success
127.0.0.1:9081 55087 2013-03-02 17:09:13.223 +0 na na Thread-76 DISP 6235 1 Audit.Other.dispatcher.DISP.com.cognos.pogo.services.DispatcherServices StartService CPS Producer Registration Service Success
and I can access the Cognos URLs: -
http://rhel6.uk.ibm.com:9081/p2pd/servlet/dispatch/ext?b_action=xts.run&m=portal/welcome/welcome.xts
and also add/remove/edit Cognos iWidgets within Business Space: -
One final point - it's sometimes necessary to modify the Cognos configuration outside of the WAS/BAM environment.
This can be achieved in one of two ways: -
(1) Use the cogconfig.sh GUI -
$ /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/cognos/PCSR011.Support/bin64/cogconfig.sh
This requires a GUI environment ( X11 or VNC on Linux ), which may be a problem for some Unix boxes.
For me, I accessed my RHEL VM as follows: -
$ ssh -X wasadmin@rhel6
and then started the tool: -
$ source /opt/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/setupCmdLine.sh
$ /opt/IBM/WebSphere/AppServer/profiles/AppSrv01/cognos/PCSR011.Support/bin64/cogconfig.shwhich loads the GUI up via my Mac's X11 client Xquartz.
(2) Use the wsadmin scripts that come with BAM: -
wbmDeployCEIEventService to create and configure the CEI event service and its required resources for receiving and sending events
wbmConfigureEventEmitterFactory to configure the outbound event emitter factory for sending events
wbmDeployMessagingEngine to install and configure the messaging engine and service integration bus
wbmDeployActionServices to install and configure the action services for invoking actions
wbmDeployScheduledServices to install and configure the Monitor scheduled services for scheduling recurring services
wbmDeployEventEmitterServices to install and configure the JMS and REST event emitter services
wbmDeployBPMEmitterServices to install and configure the BPM emitter service for use by IBM BPM
wbmDeployCognosService to install the IBM Cognos® Business Intelligence service for multidimensional analysis, or wbmSetCognosDispatcher to point to an IBM Cognos BI service that is already installed
wbmSetCognosDatabaseUser to set the IBM Cognos BI content store database password, and wbmSetCognosAdminUser to set the IBM Cognos BI administrator password.
as per the following link: -
Of course, there is a third option - one that I would not recommend - to hand-edit the Cognos configuration file: -
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/cognos/PCSR011.Support/configuration/cogstartup.xml
This is, I believe, modified ( and, more importantly, validated ) by options (1) and (2) above.
As I say, this is a W-I-P. Next on my list is to find out whether I can configure the Cognos dispatcher to work with SSL.
I did try changing the dispatcher endpoints to HTTPS URLs, but then got exceptions such as: -
CM-SYS-5157 Content Manager failed to notify the dispatcher "https://rhel6.uk.ibm.com:8443/p2pd/servlet/dispatch" of a running status change. CM-REQ-4128 An input/output error occurred executing an external request to the connector "CM". java.security.cert.CertificateException: CAM-CRP-1072 The certificate with the DN 'CN=rhel6.uk.ibm.com, O=ibm' issued by the Certificate Authority with the DN 'CN=rhel6.uk.ibm.com, O=ibm' is not trusted. Cause: java.security.cert.CertificateException: CAM-CRP-1072 The certificate with the DN 'CN=rhel6.uk.ibm.com, O=ibm' issued by the Certificate Authority with the DN 'CN=rhel6.uk.ibm.com, O=ibm' is not trusted. Runtime Exception stack trace: javax.net.ssl.SSLHandshakeException: java.security.cert.CertificateException: CAM-CRP-1072 The certificate with the DN 'CN=rhel6.uk.ibm.com, O=ibm' issued by the Certificate Authority with the DN 'CN=rhel6.uk.ibm.com, O=ibm' is not trusted.
but that's a problem for another day.
No comments:
Post a Comment