LinkedIn
Copied!

Table of Contents

Service SAPJCo rules

Using the SAP Java Connector Architecture (JCo), the SAPJCo service interface makes service rules available to external, JCo-based SAP applications as if the service rules were public methods of a Java class.

Service SAPJCo rules are no longer being actively developed and will be deprecated in Pega Platform 8.7. To avoid upgrade issues when these rules are deprecated, use Service Java rules instead. For more information, see Service Java rules.

Important: SAPJCo services require prerequisite software provided by SAP. See "Before You Begin" in the Connect SAPJCo Connectors section of the Pega Community article Pega Process Extender for SAP Business Suite.

To use SAPJCo service rules, the Pega Platform must be deployed as an enterprise application, not as a Web application.

SAPJCo services generally process service requests synchronously. That is, they immediately perform their requested processing and return a configured return value while the calling application waits. However, you can configure Java-based services to process service requests asynchronously, which means the service queues the request for asynchronous execution and the calling application calls back later for the results. Additionally, you can configure synchronous services to check for specific error conditions that you expect will be temporary — work item locks, for example — and then queue service requests that fail for those reasons for another attempt at a later time.

Access

Use the Application Explorer to see Service SAPJCo rules in your application. Use the Records Explorer to list all Service SAPJCo rules that are available to you.

Category

Service SAPJCo rules belong to the Integration-Services category. A Service SAPJCo rule is an instance of the Rule-Service-SAPJCo rule type.

Did you find this content helpful?

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.