Dynamic class loading can be enabled or disabled by two methods:
Setting the following value for the property in bpserver.conf
bpserver.classloader.dynamic=true/false
If this property is changed at runtime, after the server has been started, then "reload" needs to be called for BP Server so that the new property value is loaded.
Using the command in BP Server Admin
setDynamicCL true/false
The current value of dynamic class loading can be queried using the following BP Server Admin command:
isDynamicCL
BP Server considers only those JAR files for loading the classes that exist at the time of server startup. If new JAR files are placed after server startup, then the class loader needs to be refreshed so that it can pick the newly added JAR files. This feature is very useful to place the JAR files dynamically at runtime.
The refresh can be carried out by the following commands in BP Server Admin:
refreshClassLoader <ptName>
This command reloads the JAR files from all the common paths as well as the process template specific path, OEBPS_HOME\ebmsapps\<ptName>\lib, where <ptName> is the process template name.
refreshClassLoader
This command reloads the JAR files from all the common paths as well as the process template specific path OEBPS_HOME\ebmsapps\<ptName>\lib (where <ptName> is the process template name), for all the process templates whose adapters are loaded.
Setting the following value for the property in bpserver.conf