B2B Integration 10.4 | 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 | Additional Information about How the Microservices Runtime Classpath Is Set
 
Additional Information about How the Microservices Runtime Classpath Is Set
The Microservices Runtime classpath is set in much the same way as the Integration Server classpath. However, there are two significant differences:
*Microservices Runtime does not use instances. References to Software AG_directory \ Integration Server_directory \instances\instance_name for Integration Server in the table in How the Integration Server Classpath Is Set correspond to just Integration Server_directory for Microservices Runtime.
*Microservices Runtime does not use OSGi and, therefore, does not use information from the custom_wrapper.conf file to build the classpath. Instead, Microservices Runtime uses information from Integration Server_directory /bin/setenv.bat(sh), specifically from the PREPENDCLASSES and APPENDCLASSES properties.
Note: In some cases, the Microservices Runtime About page will display the names of files that do not exist. Specifically, if filenames specified in the PREPENDCLASSES and APPENDCLASSES variables for the Microservices Runtime classpath do not exist, they will still be displayed on the Microservices Runtime About page.
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.
Innovation Release