Information Systems:Integrator Tips, Tricks and Issues

From uniWIKI
Jump to navigation Jump to search

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:

2021-03-19 12 02 54- xtgui.unipharm.local c$ Integrator Data in carrier interface invoices atlas.png

Therefore:

  1. Determine the location of the root folder for the job in question
  2. Navigate to the temp\hash\ folder
  3. 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

Most of these refer to non-Integrator-developed Java code being run in Integrator. If you're using Design Studio to create programs, these may not apply.

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:

2021-05-13 13 00 28-Window.png

When this happens, check that any "accompanying" classes are also deployed to the server. For example, the stack trace above is complaining about not being able to find TForceCSVInvoice$1. This is a additional class that gets generated during the build, but is hidden from the IDE (you'd only see the TForceCSVInvoice, which is the actual class). Not 100% this is correct - but I believe that this is because this class inherits from CarrierCSVInvoice, which defines an inner class. Whatever the reason, both TForceCSVInvoice and TForceCSVInvoice$1 (and there was also a TForceCSVInvoice$2) are needed for the program to work. The $ classes just need to exist on the server, they don't need to be specified in the Integrator job (i.e. "Classes to Execute").

Code runs in IDE but not from Integrator

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

  • The class needs something specific when it comes to the default constructor. (Expand on this, as I can't remember the details. I think the default constructor 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.

Retrieved from "https://owl.unipharm.com/mediawiki/index.php?title=Information_Systems:Integrator_Tips,_Tricks_and_Issues&oldid=13849"