Information Systems:Integrator Tips, Tricks and Issues

Tips and Tricks

Processing a file again for a Folder Watcher job

This depends somewhat on the particular job configuration, but the convention has been for the root folder of the Folder Watcher job to be structured like such:

Therefore:

Determine this root folder for the job in question
Navigate to the temp\hash\ folder
Because the filenames of these files are hashes of the actual filenames, it is not obvious which one correlates to the file you want to delete, so you'll need to go by the date. Depending on the job, it might be ok to delete a few surrounding ones. For example for Carrier Interface import jobs.

Issues

Template:note

Deployed code won't run (NoClassDefFoundError)

You may encounter a NoClassDefFoundError when deploying/re-deploying code. The stack trace for these kinds of errors will appear as such:

When this happens, check that any "accompanying" classes are also deployed to the server. Upon close inspection, the class it is complaining about is TForceCSVInvoice$1. This is a class that gets generated during the build, but is hidden from the IDE (you'd only see the TForceCSVInvoice, which is the actual class).

Code runs in IDE but not from Integrator

As always, check the logs. The issue may be related to the following:

Integrator needs a default constructor. (Expand on this, as I think it also needs to call super() and not this()) -norwizzle (talk)

Code changes not propagating

Stop/start the Integrator job in question, or restart the Integrator service on xtgui.unipharm.local.