Where can existing 3rd-party Java (.jar) libraries already included in an IFS Cloud installation be found (to know what's already available to use), and separately, where does a genuinely new 3rd-party jar need to be placed so the automated Build Place/topic-environment build process picks it up correctly for a custom Java-based projection action — given a jar placed under fndbas\source\fndbas\framework hirdparty works fine in Developer Studio locally but breaks the automated topic-environment build?

Question

Where can existing 3rd-party Java (.jar) libraries already included in an IFS Cloud installation be found (to know what's already available to use), and separately, where does a genuinely new 3rd-party jar need to be placed so the automated Build Place/topic-environment build process picks it up correctly for a custom Java-based projection action — given a jar placed under fndbas\source\fndbas\framework	hirdparty works fine in Developer Studio locally but breaks the automated topic-environment build?

Accepted Answer

Already-included 3rd-party jars shipped with IFS Cloud can be found in Build Home under source\fndbas\server\lib and source\fndbas\framework	hirdparty — that's where to look to see what's already available before assuming you need to add something new. For adding your own new 3rd-party jar so it's correctly included by the automated build process (not just working locally in Developer Studio), place it under source\fndbas\projection\lib\ instead of the framework	hirdparty directory — the thirdparty directory works for local development but isn't picked up the same way by the automated topic-environment build pipeline.

Answer