You must have unzipped the ssoDiagnosticTools.zip file and set your JAVA_HOME environment variable, as described in Getting Started With the OpenSSO Diagnostic Tool.
Log in to the system where OpenSSO Enterprise is deployed and change to the directory where you unzipped the ssoDiagnosticTools.zip file.
Invoke the Diagnostic Tool. For example, in GUI mode on Solaris Systems: ./ssodtool.sh
Under Category, select Tamper-Detection.
In Configuration Directory, specify one of the following paths:
OpenSSO Enterprise server configuration path. For example: /opensso
Web container directory path where the OpenSSO Enterprise server bits are deployed. For example, for Sun Java System Application Server 9.1:
Under Select Test, specify Create Checksum.
Click Run Selected.
The Diagnostic Tool creates a checksum file named _configdir-pathname.checksum in the diagnostic-tool-zip-root/services/tamperdetection/backup directory.
Caution. The Tamper Detection test relies on the operating system security permissions to protect the checksum files. Depending on the requirements of your deployment, you might need to copy these files to a more secure location.
To save the results as an HTML file, click Save All Results.
The Diagnostic Tool logs all test results in the diagnostic-tool-zip-root/ssodtool.log file. Optionally, as required by your deployment, check and save this log file.
Repeat this procedure to create a checksum file for the other path in Step 4.