Eclipse APDE ERROR - Failed to run workflow compiler

Technote (troubleshooting)


Problem(Abstract)

Working with the APDE to compile workflows you encounter a compile error. You are able to run existing TPM workflows, but not compile any new ones.

Symptom

INFO - Generating E:\APDE\workspace\testpkg\generated\com\ibm\tivoli\tpm\wkf\testpkg\wkf1.java
ERROR - Failed to run workflow compiler
java.lang.NullPointerException
at com.ibm.tivoli.tpm.workflow.compiler.JavacCompiler.getCompileClasspath(JavacCompiler.java:112)
at com.ibm.tivoli.tpm.workflow.compiler.JavacCompiler.buildCompilerArguments(JavacCompiler.java:66)
at com.ibm.tivoli.tpm.workflow.compiler.JavacCompiler.compile(JavacCompiler.java:34)
at com.ibm.tivoli.tpm.workflow.compiler.Workflow2JavaCompiler.compile(Workflow2JavaCompiler.java:69)
at com.ibm.tivoli.orchestrator.tcdriverdevelopment.resources.TDEWorkflowCompiler.compileWorkflow(TDEWorkflowCompiler.java:118)
at com.ibm.tivoli.orchestrator.tcdriverdevelopment.resources.TDEWorkflowCompiler.compile(TDEWorkflowCompiler.java:236)
at com.ibm.tivoli.orchestrator.tcdriverdevelopment.resources.nature.TCDriverBuilder.compileWorkflows(TCDriverBuilder.java:214)
at com.ibm.tivoli.orchestrator.tcdriverdevelopment.resources.nature.TCDriverBuilder.build(TCDriverBuilder.java:89)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:629)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:172)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:203)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:255)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.BuildManager.basicBuild(BuildManager.java:258)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop(BuildManager.java:311)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:343)
at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:144)
at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:242)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)


Cause

The APDE configuration files may not correctly reference the file locations for the locally included bundles, java path, etc.

1. APDE\config\deploymentengine.xml file may not correctly reference the location to the tpm-bundles.
2. APDE\config\dcm.xml file may not correctly reference the location to the database client jar files.
3. APDE\eclipse\eclipse.ini file may not correctly reference the location to the config and logs directories.
4. APDE\eclipse\eclipseLauncher.bat file may have inconsistencies.


Diagnosing the problem

Check the error and see if it references a NullPointerException when attempting to getCompileClasspath.

Resolving the problem

1. Edit the deploymentengine.xml file and correct the invalid path. It should point to the top level of your APDE installation location, eg E:\APDE. It does not need any trailing slash or additional punctuation.

  <tpm-bundle-home>E:\APDE</tpm-bundle-home>

2. Edit the dcm.xml file and ensure the location of the db2 or oracle connection jar files are correct. eg, for Db2:
  <pathelement location="c:\APDE/config/db2jcc.jar" />
  <pathelement location="c:\APDE/config/db2jcc_license_cu.jar" />


3. Edit the eclipse.ini file and confirm the proper locations for config file, logs, and log4j properties file. eg,:
  -Dkanaha.config=file:c:\APDE/config
  -Dkanaha.logs=c:\APDE/logs
  -Dlog4j.configuration=file:c:\APDE/config/log4j.prop

4. The eclipseLauncher.bat file should look like this:
  set APDE_INSTALL_DIR=c:\APDE
  set JAVA_HOME=c:\APDE
  set PATH=%JAVA_HOME%\bin;%PATH%
  %echo off
  set ECLIPSE_HOME=%~dsp0
  set SPEDITOR_DLL=%ECLIPSE_HOME%\plugins\newSPEditor_4.0.0\swd_cli\lib
  set SPEDITOR_BIN=%ECLIPSE_HOME%\plugins\newSPEditor_4.0.0\swd_cli\bin
  set PATH=%SPEDITOR_DLL%;%SPEDITOR_BIN%;%PATH%
  set TISDIR=%ECLIPSE_HOME%\plugins\newSPEditor_4.0.0\swd_cli
  start /B %ECLIPSE_HOME%\eclipse.exe

After making the config file changes, restart the APDE and try to compile your workflow again.

Related information

Installing Automation Package Developer Environment aut

Rate this page:

(0 users)Average rating

Document information


More support for:

Tivoli Provisioning Manager

Software version:

7.2, 7.2.0.1, 7.2.0.2, 7.2.1

Operating system(s):

Linux, Windows

Reference #:

1631904

Modified date:

2014-02-17

Translate my page

Machine Translation

Content navigation