B2B Integration 10.2 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Class Loading in Integration Server | How Class Loading Works in Integration Server | Classpaths | How the Integration Server Classpath Is Set
 
How the Integration Server Classpath Is Set
When you start Integration Server, a script file named startup.bat (on Windows) or startup.sh (on UNIX) runs. Among other things, the startup.bat/sh file builds an Integration Server classpath variable, which consists of the following:
Directory or variable
Description
The wrapper.java.additional.202= -Dwatt.server.prepend.classes property of the
Software AG_directory
/profiles/
IS_instance_name/configuration/
custom_wrapper.conf
Variable defined in custom_wrapper.conf that defines directories and files to prepend to the beginning of the classpath.
The wrapper.java.additional.203= -Dwatt.server.append.classes property of the
Software AG_directory
/profiles/
IS_instance_name/configuration/
custom_wrapper.conf
Variable defined in custom_wrapper.conf that defines directories and files to append to the end of the classpath.
Software AG_directory \ Integration Server_directory \instances\ instance_name\bin\ini.cnf
The application.classpath property from Integration Server_directory \instances\instance_name\bin\ini.cnf. This typically specifies classes in the following directories, in this order:
Integration Server_directory \lib
Software AG_directory \common\lib
Software AG_directory \ Integration Server_directory \instances\instance_name\lib\jars\custom
All custom or third party .jar and .zip files in this directory.
Note: Use this directory to store your custom or third party .jar and .zip files that you want to make available to a server specific instance.
Software AG_directory \ Integration Server_directory \instances\instance_name\packages\package_name\code\jars\static
All .jar and .zip files from this directory in each package. The files are added to the classpath in the order returned by the File.list() method.
Note: Jars contained in this directory will be loaded even if the associated package is disabled.
Software AG_directory \ Integration Server_directory \instances\instance_name\packages\package_name\code\classes
If this directory exists, it is added to the classpath.
Software AG_directory \ Integration Server_directory \instances\instance_name\packages\package_name\code\classes.zip
If this file exists, it is added to the classpath.
Software AG_directory \ Integration Server_directory \instances\instance_name\updates
Valid, and non-voided updates and fixes.
Software AG_directory \ Integration Server_directory \lib\jars
All .jar and .zip files in this directory.
Software AG_directory \ Integration Server_directory \lib\jars\custom
Common custom and third party .jar and .zip files in this directory.
Note: Use this directory to store your custom and third party .jar and .zip files that you want to make available to all server instances.
Software AG_directory \ Integration Server_directory \updates
Common valid, and non-voided updates and fixes.
Note: The updates and fixes in this directory are available to all server instances.
Note: In some cases, the Integration Server Administrator About page will display the names of files that do not exist. If filenames specified in the wrapper.java.additional.202=-Dwatt.server.prepend.classes and wrapper.java.additional.203=-Dwatt.server.append.classes properties for the Integration Server classpath do not exist, they will still be displayed on the Integration Server About page. If the ini.cnf file refers to jar files that do not exist, they will also be displayed on the About page and, if the watt.debug.warnOnClasspathError server configuration parameter is set to true, the following error will be written to the standard out for each non-existent jar file: Classpath entry in ini.cnf not found: <jar_file_name>. Standard out is directed to Software AG_directory /profiles/IS_instance_name/logs/wrapper.log.
Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.