Have you don’t the extra step of running the command that updates the OSGi profile as described in the “Adding Custom JAR Files” section of the MWS admin guide?
MWS runs inside of an OSGi runtime, so you must do extra work to convert plain jar files (that are not already OSGi bundles) into OSGi bundles and provision those OSGi bundles to the OSGi profile to make them available. The “Software AG_directory
/MWS/bin/mws.[bat | sh] update” command does that work for you after you have copied new jar files to the MWS/lib folder.
Alternatively, MWS 9.12 also supports autodeploy of jar files by copying them to the MWS\server\default\deploy folder, so that may be more convenient than those other steps and wouldn’t require a restart of the server.
#webMethods#MWS-CAF-Task-Engine#webMethods-BPMS