Reporting tab
Use the Reporting tab to configure the settings to collect reporting data in the System Automation Application Manager database.
After you configure the reporting database, you need to start the reporting data publisher.
Note:
- The reporting function, like report generation, is provided as part of the System Automation Application Manager product up to version 3.2.2.
- Make sure to disable reporting before you uninstall System Automation Application Manager from
the end-to-end automation management host.
Local database installations of System Automation Application Manager are dropped during uninstallation. In this case, stop the reporting data publisher.
For starting or stopping the reporting data publisher, see Controlling the automation adapter and publishers or use the
following commands:
samctrl -e JDBC or samctrl -d JDBCIf you want to collect reporting data in the DB2® database of System Automation Application Manager, select the Enable report data collection check box. Otherwise, deselect the check box, which disables the entry fields on this tab.
Fields on the Reporting tab:
- DB2 server name or IP address
- The host name or IP address of the DB2 server that hosts
the reporting data database. The actual reporting function, like report generation, is
provided as part of the System Automation Application Manager product. The DB2 server must be the same system where the DB2 database of System Automation Application Manager is located. If you omit this value, the value that you specify for the System Automation Application Manager host in the Host Using Adapter tab is used as the default. If you are using a remote DB2 for the System Automation Application Manager database, specify the host name or IP address of that remote DB2 system.Note: If the DB2 server runs on z/OS®, make sure that the file
db2jcc_license_cisuz.jaris available on each node in your System Automation for Multiplatforms cluster. This file contains the license to connect to DB2 on z/OS from non-z/OS system.You can find this file in the WebSphere Application Server directory that is used for System Automation Application Manager. Search the following directory tree for the file:
Copy the file into the directory<WAS_INSTALL_ROOT>/deploytool/itp/plugins/opt/IBM/tsamp/sam/libon each node in your System Automation for Multiplatformscluster. Make sure that you have a DB2 license agreement. - Alternate DB2 server
- A value for this field is optional. If you configured a disaster recovery setup with two
different sites for the System Automation Application Manager, the
end-to-end automation manager can run on either site. To support such a setup, specify the
host name or IP address of System Automation Application Manager on
the second site in this field. In case of an Application Manager site switch, the adapter
automatically switches to the new active end-to-end automation manager instance as the target
for collected report data. The values of all following settings are used for both DB2 servers.
If the database is on the same system as the end-to-end automation manager, specify the same
value that you used for the alternate System Automation Application Manager host that is using the adapter. If you are using a remote DB2 for the System Automation Application Manager database, leave this field empty.Note: If you specify an alternate DB2 server, you need to configure the DB2 Automatic Client Reroute feature. Then, the reporting function is enabled to always feed the reporting data to the DB2 HADR primary instance. Refer to the DB2 documentation for a description of how to set up this feature.
Example:
DB2 HADR is set up for databaseeautodbon the two hostslnxcm5xandlnxcm6x. The DB2 port is 50000 on both hosts. To configure Automatic Client Reroute for the two hosts, run the following commands:- On lnxcm5x:
db2 update alternate server for database eautodb using host name lnxcm6x port 50001 - On lnxcm6x:
db2 update alternate server for database eautodb using host name lnxcm5x port 50001
- On lnxcm5x:
- DB2 database name
- The name of the DB2 database of System Automation Application Manager, where reporting data is stored.
- DB2 schema name
- The name of the schema that is used for the database tables where reporting data is stored. Change the value of this parameter only if the DB2 database of System Automation Application Manager is on a z⁄OS system. You might need to control the schema name to uniquely identify database tables in your DB2 installation.
- DB2 port
- The number of the port that is used to access the DB2 database of System Automation Application Manager, where reporting data is stored. The default port is 50001.
- User ID
- The user ID that is used to access the DB2 database of System Automation Application Manager, where reporting data is stored.
- Password
- The password that is used to access the DB2 database of
System Automation Application Manager, where reporting data is
stored.
Click Change to change the password.
Note: Ensure that you update the configured password whenever the DB2 database password is changed. If the configured password does not match the DB2 database password, events are not written to the database.