B2B Integration 10.5 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Class Loading in Integration Server | Adding Classes to the Server Classpath | How Classes Are Found | How Classes Are Found in Microservices Runtime
 
How Classes Are Found in Microservices Runtime
The locations that Microservices Runtime searches relative to one another is different than Integration Server because Microservices Runtime does not use OSGi and does not haven “\instances\instanceName” directory.
Below is the order in which Microservices Runtime searches the various locations relative to one another:
1. PREPENDCLASSES in Integration Server_directory \bin\server.bat(sh)
2. Software AG_directory \ Integration Server_directory \bin\ini.cnf
Specifically, the application.classpath property in the ini.cnf file. The application.classpath property typically specifies classes in the following directories, in this order:
* Integration Server_directory \lib
* Software AG_directory \common\lib
3. Software AG_directory \ Integration Server_directory \lib\jars
4. Software AG_directory \ Integration Server_directory \lib\jars\custom
5. Software AG_directory \ Integration Server_directory \packages\packageName\code\jars\static
6. APPENDCLASSES in Integration Server_directory \bin\server.bat(sh)
Note: Microservices Runtime handles two or more copies of a class or multiple packages with jar files in its code\jars\static directory the same way in which Integration Server does. For more information, see How Classes Are Found.
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.