How to Obtain Ingestion Classpaths Used by Hangman in Infoworks

Issue

Obtaining ingestion classpath used/being used by Hangman in Infoworks.

Solution

The classpath used by a Hangman is required to debug the class not found exceptions and other classpaths issues.

When a job is executed, Infoworks uses an internal job executor, Hangman, which will source the iw_jobs_classpath in the conf.properties file in the $IW_HOME/conf/ folder.

Following are the steps for Hangman to obtain the classpath when the job is running:

• Modify the classpath setting in conf.properties, save and exit the file.

• Ensure no job is running. Verify the job queue in the Admin page.

• Navigate to the $IW_HOME/bin directory.

• Source the env file using the following command:

source env.sh

• Stop the Hangman services using the following command:

./stop.sh hangman

• Start the Hangman services using the following command:

./start.sh hangman

• Verify that the Hangman services are running using following command:

./status.sh

• Login to the Infoworks ADE and run the job.

• Navigate to the $IW_HOME/logs/hangman directory and tail the Hangman logs using the following command:

tail -f hangman.log

• Hangman log prints the respective jars/classpath picked/sourced by the Hangman for the respective job which is being executed.

• To share the logs, run the following command:

tail -f 150 hangman.log > /home/username/hangman_logs_150_lines.log

Applicable Versions

• v2.3.x,v2.4.x,2.5.x