This section contains additions and corrections that will appear in the next version of the Metric Studio User Guide.
If you must contact customer support for assistance, attaching the support bundle will help expedite your case. This support bundle is a zip file generated by a tool called cmm_support_bundle.
The command is located in installation_location/bin and is invoked as follows:
cmm_support_bundle databaseServer databaseName databaseUser databasePassword databaseType output_filename
where
databaseServer is the hostname of the database server (default: localhost). For Oracle you can add an optional port by appending ':port' to the hostname (default = 1521). For example: localhost:1234. The databaseServer parameter is ignored for database type 'db2'
databaseName is the name of the database (default: cmm). This is the 'database file' entry for database type 'db2'
databaseUser is the database user name (default: sa)
databasePassword is the database password (default: cmm)
databaseType is the database type. Values can include sqlserver, oracle, db2 (default: sqlserver)
output_filename is the fully qualified name of the zip file to create (defaults to the _SUPPORT_FILES directory)
For example, if a SQL Server database contains your metric store, issue a command such as
cmm_support_bundle dbserver1 prod_db sa topsecret sqlserver
or on UNIX
sh cmm_support_bundle.sh dbserver1 prod_db sa topsecret sqlserver
By default, this will create output in the installation location/_SUPPORT_FILES directory.
By default, email notification about changes to a metric in the watch list is not selected when you add a metric to the watch list. However, you can override the default. You must be logged on to the namespace to add email notification.
At the bottom of the left pane, click My Folders.
Your watch list and accountability scorecard appears in the left pane.
Click Watch List and click the metric for which you want to add email notification.
In the right pane, click the button named click to turn on email alerts for this metric.
A history chart is a graph that appears for each metric. You can use the history chart to analyze the relationships between target values and actual values.
The history chart shows target values, actual values, target tolerance, and any specified user-defined columns. Tolerance is the acceptable range that a result can deviate from the target. In the history chart, a green diamond represents the target value, and yellow lines represent the tolerance.
A user-defined column is a comparative measurement for a metric. For example, revenue per month is a metric that you monitor. Although this is an important metric, you are also interested in comparing revenue to analyst forecasts. To compare revenue to analyst forecasts, the Metric Studio author creates a user-defined column for analyst forecasts and then adds the column to the Revenue metric type.
You can choose to view actual values and user-defined columns as line graphs or bar graphs.
A history chart shows the business calendar level that you selected.
The previous arrow shifts the graph one business calendar level left. The next arrow shifts the graph one business calendar level right. For example, if months and quarters are shown along the bottom of the graph, the previous arrow shifts the graph left by one month. The fast-previous arrow shifts the graph one quarter to the left. The fast-next arrow shifts the graph one quarter to the right.
You must specify the metric deployment location for the metric store. The metric deployment location is the location of all the import source directories or folders for the current metric store.
You also select the import sources that are used by this metric package. You must define an import source before you can select it.
In the Tools list, click Import Sources.
Specify the metric deployment location by clicking Change the deployment location and then one of the following
Choose this option if the location of your import source is installation _location\cognos\c8\deployment.
This option should only be used in a single-server installation. In distributed installations, a deployment location that is available on all servers should be specified using the Specify another location option.
Choose this option if the location of your import source is not installation _location\cognos\c8\deployment.
In a distributed installation, a deployment location that is available on all servers must be specified.
In a Windows environment, you use a UNC path pointing to a share accessible by all servers. You must use a UNC path and not a mapped drive to specify the metric deployment location.
In Unix environments, an identical mount must be created on all servers.
Click OK.
Select the check box next to the import sources for this package.
Tips:
You can exclude import sources by selecting the check box under the Exclude from the import column.
You can choose all import sources by selecting the check box next to Name.
You can exclude all import sources by selecting the check box next to Exclude from the import.
Click OK.