Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Integration methods - SOAP, .Net, JDBC, JSR-94, and PoJo

Updated on September 10, 2021

 This presentation is part of the Services and Connectors Self-Study Course.

Transcript

There are multiple ways to integrate one application with another.

Web services use SOAP for its messaging.  SOAP messages are most commonly sent using an HTTP transport, but SOAP with other transports, such as JMS, is gaining traction. The web services recommendation does not identify a specific transport.

Integration via .NET uses web services as its core means of communication between applications.  Therefore, .NET integration is implemented in the same manner as other web services.

You can integrate Java applications with different relational database products in a generic fashion by using a JDBC (Java Database Connectivity) driver.  ODBC (Open Database Connectivity) exists similarly in the Windows world.   There are also ADO.NET drivers to support database integration specifically in .NET applications.

BPEL (Business Process Execution Language) is used to orchestrate a set of services together as a business process.  BPEL was designed to orchestrate a set of system to system communications. Human interaction is not defined in the BPEL standard.  Many SOAs support BPEL integration.

There are also several different ways of integrating with Java applications in the Java world:

  • EJBs (Enterprise Java Beans)
  • POJOs (Plain Old Java Object), which allows one to integrate with simple java classes
  • JSR-94 protocol to communicate between java-based applications

There is support in PRPC for all these integration methods and more.

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us