
Get a Complete Picture of Your Java Environment
Upload a ZIP archive collected from your production servers for the most accurate licensing and security analysis.
Drag & drop ZIP or properties file here, or click to browse
Supports .zip and .properties files · Max 100MB

Why Full Audit?
Full Audit captures every installation — version and vendor included. Nothing gets missed and the licensing results are accurate to act on.
How to Collect
the Right Files
Get instruction to you email
Need IT's help? Send them the instructions, get a file back to upload here.
Step 1: Collect Java Runtime Info from Production Servers
Run JavaRuntimeInfo.java on every server for every Java installation in production. Use random file names to avoid conflicts.
For each production server:
# Generate a random filename
RANDOM_NAME="java-info-$(hostname)-$(date +%s)-$RANDOM.properties"
# Compile and run JavaRuntimeInfo
$JAVA_HOME/bin/javac JavaRuntimeInfo.java
$JAVA_HOME/bin/java JavaRuntimeInfo --out="$RANDOM_NAME"For Docker containers:
# Generate a random filename
RANDOM_NAME="java-info-$(hostname)-$(date +%s)-$RANDOM.properties"
# Run in container
docker run -v ./JavaRuntimeInfo.java:/JavaRuntimeInfo.java --rm -it bash -c "cd / && javac JavaRuntimeInfo.java && java JavaRuntimeInfo --out=$RANDOM_NAME && cat $RANDOM_NAME" > "$RANDOM_NAME"
Automated collection script example:
#!/bin/bash
mkdir -p java-runtime-collection
cd java-runtime-collection
# For each Java installation
for JAVA_HOME in /usr/lib/jvm/* /opt/java/* /usr/java/*; do
if [ -x "$JAVA_HOME/bin/java" ]; then
RANDOM_NAME="java-info-$(basename $JAVA_HOME)-$(hostname)-$(date +%s)-$RANDOM.properties"
$JAVA_HOME/bin/javac ../JavaRuntimeInfo.java
$JAVA_HOME/bin/java -cp .. JavaRuntimeInfo --out="$RANDOM_NAME"
fi
done
Step 2: Create ZIP Archive
Collect all .properties files from all servers and create a single ZIP archive.
Basic ZIP creation:
# Create archive with all properties files
zip -r java-runtime-archive-$(date +%Y%m%d-%H%M%S).zip *.properties
Advanced: Organize by server/environment:
# Create directory structure
mkdir -p archive-staging/production archive-staging/staging archive-staging/development
# Move files to appropriate directories
mv *prod*.properties archive-staging/production/
mv *staging*.properties archive-staging/staging/
mv *dev*.properties archive-staging/development/
# Create organized archive
cd archive-staging
zip -r ../java-runtime-archive-$(date +%Y%m%d-%H%M%S).zip .
Verification:
# List contents of the archive
unzip -l java-runtime-archive-*.zip
# Test archive integrity
unzip -t java-runtime-archive-*.zip
Step 3: Upload Archive to Service
Open this page and upload your ZIP archive using the form above.
- Use the drag & drop area above to select your ZIP file
- Click "Analyze Java Versions" to upload and process
- Review the analysis results
Best Practices:
- Include server/environment information in filenames
- Keep archives under 100MB for optimal processing
- Document the collection date and scope
- Store archives for compliance and historical analysis