More about Service SAPJCo rules

External JCo-based SAP client applications communicate with the Pega Platform through a delegate proxy Java archive generated by the service package.

Implementation

Important: Service SAPJco rules are no longer being actively developed. To avoid upgrade issues when these rules are deprecated, use other web-based SAP capabilities.

The service package for a group of SAPJCo service rules generates one or more proxy Java archives. The external client application communicates with Pega Platform through the proxy Java archive, which forwards the messages from the client to the Pega Platform and returns to the client the response.

For more information, see the section "Service-SAPJCo Service" in the Pega Community article Pega Process Extender for SAP Business Suite.

Dynamic system settings

Two dynamic system settings data instances identify the directories that SAPJCo services use. Review these settings and update them as appropriate:

Pega-RULES.compiler/DefaultClasses
Pega-RULES.compiler/DefaultPaths

Performance statistics

Through changes to the prlog4j2.xml file, you can obtain performance statistics on the execution of services. See Performance tool — Statistics for services.

Through changes to the prconfig.xml file, you can be alerted to unusually long service operations. See How to detect lengthy service operations.

As an alternative to updating the prconfig.xml file, you can use dynamic system settings to configure your application. See Dynamic system settings.

Return types

When using Service SAPJCo rules, do not return BigDecimal values unless the calling system also supports this class. Return a String value, or use a transform (identified in a Registry Java Property Transform data instance).