Troubleshooting buildomatic failures: Unable to locate tools.jar and Keystore Creation errors in CABI

Products

• Network Observability
• Spectrum

Issue/Introduction

When running js-export.sh or js-import.sh scripts in the buildomatic folder of your JasperReports Server (CABI) installation, you may encounter warnings regarding missing tools.jar files or errors related to Keystore creation. This article outlines how to distinguish between ignorable warnings and critical configuration failures.

Symptoms

• Warning: "Unable to locate tools.jar. Expected to find it in [path/to/java/lib/tools.jar]"
• Error: "Keystore creation was canceled" or "Failed to create the keystore"
• Error: "Keystore may have been tampered with"

Environment

• Product: CA Business Intelligence (CABI) / JasperReports Server
• Environment: Linux/Windows Server

Cause

1. tools.jar warning: This is a common environmental warning. The script expects tools.jar in a specific location within the Java installation. If the script functions otherwise, this can be safely ignored.
2. Keystore creation error: This is typically a permissions issue. The user executing the script (e.g., a non-root user) does not have sufficient privileges to write the keystore file to the required system directory (often /root/.jrsks or similar).

Resolution

1. Handling "Unable to locate tools.jar"

If the script proceeds to execute after this message, this warning can be safely ignored and does not indicate an import/export failure. No action is required.

2. Handling Keystore Creation Errors

If the script fails with a "Keystore creation was canceled" error, follow these steps to resolve permissions:

1. Ensure root/administrator access: Run the command with root privileges (Linux) or "Run as administrator" (Windows).
2. Verify Keystore Path: If the issue persists, the script may be looking for the keystore in a location inaccessible to your current user.
   • Check the keystore.init.properties file located in the buildomatic folder.
   • Configure the correct path for the keystore to ensure the utility can write to it.
3. Alternative Execution: If you do not have root access to the target machine, consider executing the command from a machine where you have full administrative or root permissions, such as an OBM Gateway or an authorized management server, if applicable to your deployment architecture.