JCo
Client Service
Portal applications that use the JCo-API can create unexpected spikes in the memory consumption. Especially the method JCO.createRepository() creates a lot of temporary objects causing increased garbage collection overhead and even OutOfMemory exceptions when used carelessly. To minimize the usage of this expensive operation, the caching-facilities introduced with the latest JCo Client-Service should be used.

JCo is deprecated.
Please note that JCo has been replaced by the SAP Connector Framework (based on JCA) as of EP 6.0. It is only included for compatibility reasons. For new developments Connector Frame/JCA must be used.
The call of method JCO.createRepository(0) should be replaced by the method IJCOClientService.getRepository().
Example of a not recommended implementation:
String sysId = myProfile.getProperty("SystemIdentifier"); |
Example of recommended implementation:
String sysId = myProfile.getProperty("SystemIdentifier"); |
More details about SAP JCo can be found on the SAP Help Portal at:
SAP Library → SAP NetWeaver by Key Capability → Application Platform by Key Capability → Connectivity → Components of SAP Communication Technology → Communication Between ABAP and Non-ABAP Technologies → SAP Java Connector