Before you begin
To edit configuration files, use the IBM
® Application Server wsadmin client. See Starting the wsadmin client
for information about how to start the wsadmin command-line tool.
About this task
Configure Metrics using scripts accessed with the wsadmin client. These scripts use the AdminConfig
object, available in the WebSphere
Application Server wsadmin client, to modify the Metrics configuration file. Changes to Metrics configuration settings require node synchronization and a restart of the Metrics server before they take effect.
To edit Metrics configuration properties, complete the following steps:
Check in the changed configuration property keys using the following wsadmin client command: MetricsConfigService.checkInConfig()
Update the value of the version stamp configuration property in the LotusConnections-config.xml file to force browsers to pick up this change.
- Start the wsadmin client.
- Start the Metrics Jython script interpreter.
- Use the following command to access the Metrics configuration file:
If you are asked to select a server, you can select any server.
- Check out the Metrics configuration files using the following command:
- working_directory is the temporary working directory to which the configuration XML and XSD files are copied. The files are kept in this working directory while you make changes to them.
Note: AIX® and Linux™ only: The directory must grant write permissions or the command will not run successfully.
- cell_name is the name of the WebSphere Application Server cell hosting the IBM Connections application. This argument is required. If you do not know the cell name, you can determine it by typing the following command in the wsadmin command processor:
- Optional: To view a list of the valid Metrics configuration settings and their current values, use the following command: MetricsConfigService.showConfig()
Here is some sample output from the MetricsConfigService.showConfig()
Metrics configuration properties:
cognos.namespace = IBMConnections
cognos.secsPerRequest = 1200
communitiesMetricsDateRange.all.enabled = true
communitiesMetricsDateRange.last12months.enabled = true
communitiesMetricsDateRange.last4weeks.enabled = true
communitiesMetricsDateRange.last7days.enabled = false
communitiesMetricsDateRange.lastquarter.enabled = true
db.dialect = DB2
Only properties in metrics-config.xml
are printed by the MetricsConfigService.showConfig()
command. Configurations of custom reports are not listed.
- Modify configuration properties using the appropriate method:
See Required post-customization step for more details.
Exit the wsadmin client by running the exit command.
Restart the server to apply your changes.
What to do next
After updating the Metrics properties with new values, you can use the MetricsConfigService.showConfig()
command to display the list of properties and their updated values.
Parent topic: Managing Metrics configurations