P. 1
Cog Nus

Cog Nus

|Views: 33|Likes:
Published by gokhancantas

More info:

Published by: gokhancantas on Jul 05, 2011
Copyright:Attribution Non-commercial


Read on Scribd mobile: iPhone, iPad and Android.
download as PDF, TXT or read online from Scribd
See more
See less





This section discusses Java Management Extensions and JConsole.

Java Management Extensions

Java Management Extensions (JMX) is a Java technology that supplies tools for
managing and monitoring applications and service-orientated networks. These
resources are represented by objects called MBeans. MBeans, which stands for
Managed Bean, represent a resource running in the Java Virtual Machine (JVM).

How this translates to the IBM Cognos topology is that the dispatcher component
stores the raw metrics in an MBean within the JVM running the IBM Cognos BI
application. Besides the administration console, the metrics are accessible
externally by using the industry-standard JMX. Thus, for tools such as IBM Tivoli
Monitoring to connect to the IBM Cognos metrics, a JMX agent must be created
to interface with the IBM Cognos MBean.

Connecting to metrics using JConsole

This section describes the steps required to view the metrics externally using the
JConsole application, which is available as part of the Java V1.5 JDK package.
Before the metrics can be exposed to external sources, the Java MBean must
first be made available for external access. To accomplish this, a parameter must
be added to one of files within the application server.

Chapter 10. IBM Cognos system administration 499

For a default Tomcat installation, complete the following steps:

1.Navigate to the \webapps\p2pd\WEB-INF directory and open the
p2pd_deploy_defaults.properties file in a text editor. Uncomment the
existing rmiregistryport line by removing the # symbol (and modify the port
number if required) (Figure10-57).

Figure 10-57 Enabling the rmi registry port for JMX support

2.Save the file.

It is important to note that there is no security associated with the JMX
implementation, so after the entry has been added to the file, anybody can
connect to the MBean if the proper connection string is known. That is, product
access to the metrics can be locked down through the security policies in IBM
Cognos Connection and the administration console, but these policies do not
apply when connecting externally.

To enforce user name and password externalaccess:

1.Open IBM Cognos Configuration.

2.In the explorerframe, select Environment.

3.Locate the External JMX Portproperty in the Environment - Group Properties
dialog box and type 9999(to match the port number used for the
rmiregistryport entry from a previous step).

4.Click the value field of the External JMX credentialproperty, and then click the
pencil icon.

Port number note: The number specified in the added string pertains to a
port number. Ensure that the port number specified is available for use and
is not being occupied by another application.


IBM Cognos Business Intelligence V10.1 Handbook

5.On the “Value - External JMX credential” dialog box, specify the user ID and
password that will be used to secure the IBM Cognos MBeans (see

Figure 10-58 Securing the IBM Cognos JMX interface

6.Click OK.

7.Save the new configuration parameters.

Because this is a setting that is read when the application is started, a restart is
required if the IBM Cognos BI application is already running.

After you start or restart the application:

1.Locate the jconsole.exe executable in the bin directory of the Java JDK and

launch it.

JMX implementation note: The JMX implementation does not allow for
spaces in the install path when using a JRE other than the default IBM JRE
provided with the IBM Cognos installation. If there are spaces in the
installation path and the non-default IBM JRE is being used, JConsole
must be executed using the following command line:

Jconsole -J-Djava.rmi.server.useCodebaseOnly=true

Chapter 10. IBM Cognos system administration 501

2.When presented with the JConsole: Connect to Agent dialog box, switch to
the Advanced tab (see Figure10-59). Connect to the following JMX URL:


Figure 10-59 Connecting to IBM Cognos using JMX

3.Supply the proper credentials if the External JMX credentialvalue was
supplied in IBM Cognos Configuration.

4.Click Connect to connect to the system metrics using JMX.

5.Ensure that the MBeans tab is selected (if not selected by default).

6.Expand the com.cognossection of the tree. This is the location of all of the
metrics that reside in the administration console.

7.View the metrics for a service, for example, report service, by expanding the
reportService entry to expose the objects beneath.

8.If more than one dispatcher is present in the environment, select one of them
and expand the dispatcher name entry in quotation marks.

9.Click the Metrics option beneath the dispatcher, which displays all of the
metric names and values in the right frame.

Connection note: The machine_name entry must be the server name and
cannot be localhost.


IBM Cognos Business Intelligence V10.1 Handbook

To compare the metrics displayed in the IBM Cognos administration console and

1.Open a web browser session, launch IBM Cognos BI, and navigate to the
System task within the administration console.

2.Drill into the same dispatcher as used in the JConsole interface.

3.Keep drilling down until the ReportService entry is located.

4.Click ReportService to filter the metrics in the upper-right frame.

Providing that no additional report service requests were made, the values
displayed in the Metrics - ReportServiceframe are identical to the values
displayed in JConsole, although there might be slight formatting differences
(Figure10-60 and Figure10-61).

Figure 10-60 Report service metrics in IBM Cognos administration console

Figure 10-61 Identical report service metrics in JConsole

Chapter 10. IBM Cognos system administration 503

You're Reading a Free Preview

/*********** DO NOT ALTER ANYTHING BELOW THIS LINE ! ************/ var s_code=s.t();if(s_code)document.write(s_code)//-->