Installing tasks

In addition to the tasks that come already installed with Services Framework, several components and features provide Services Framework tasks as JAR files. These tasks must be added to Services Framework before they are available to be used. Services Framework looks in a specific directory for the task JAR files to load. All the JAR files in this location are loaded by the Services Framework engine, which then makes the tasks available to be registered and configured.

Services Framework looks in the /opt/ibm/ftm/iybsfEngine/java directory to find task JAR files. Because it is mounted in the Services Framework container at /opt/ibm/ftm, you can use the pv-ftm-application persistent volume to add, remove, or update the JAR files for your tasks. Copy the JAR files to the /iybsfEngine/java directory in the root directory of the pv-ftm-application persistent volume. By using the persistent volume, you can manage your Services Framework task JAR files from outside of the container instead of updating them from inside the container.

The JAR files for many of the Services Framework tasks that are provided by Common Services components and features can be retrieved from the artifacts container for your offering.

When you are adding a task, ensure that all the JAR files that are needed by the task are in the directory where the Services Framework engine is looking for task JAR files.
Notes:
  1. To ensure that new or updated tasks are available in Services Framework, stop and restart the Services Framework pods after files are added or updated in the library directory.
  2. The util.jar file is already part of the Services Framework engine. It is only used to compile tasks and does not need to be copied to the directory where Services Framework looks for task JAR files.