software training classes for pega prpc with expert trainers in INDIA,USA,CANADA,AUS. FOR More details email to : pegabpm99@gmail.com

1. Pega Test Topics
Integration % of Exam: 5%
■ Services and Connectors
0 Understand the difference between a service and a connector
1 Add an integrator SmartShape to a process rule
2 Create a connector to a relational database
3 Create a connector to a SOAP service
4 List the most common service and connector protocols
Basic Defintions.
A connector is a component which defines and implements an interface between a PRPC
application (which is the client) and an external system (which is the server).
A service is a component which defines and implements an interface between an external
application (which is the client) and a PRPC system (which is the server).
Connectors:
1. Encapsulate logic used to communicate with a service. How it is done:
a. Assemble and send outbound messages to the external system.
b. Receive the response
c. Write the values from response to the clipboard.
2. Connectors are listed in the Integration-Connectors rule category.
Example of a Connector:
Used to connect to a relational database.
Basic path of execution:
Clipboard values are (maybe) used in a activity which calls a Connect SQL rule which
send sql over to a database and executes a query. The response is sent back to the
clipboard which are then picked up from the activity. Done.
Other things may also be needed to process and send the request to external system. For
example, parse/stream rules for XML. And connector information like database info for
db connectors, host info for SOAP requests, queue info for MQ requests.
Integrator shape: is used in a flow to call an activity which calls a connector rule.
Other standard connectors:
1. Web services (SOAP and .net) Connector rule types are Rule-Connect-SOAP and
Rule-Connect-dotNet
2. HTTP (Allows us to send XML, text etc to other apps. Is an alternative to SOAP).
Connector type is Rule-Connect-HTTP

2. 3. EJB (Allows server type integration with Java apps). Connector rule type is Rule-
Connect-EJB
4. JCA (“J2EE Connector Architecture”. connect PRPC app to an external
application using Common Client Interface which is part of JCA specs.)
Connector type is Rule-Connect-JCA
5. Java (Connect to external Java class or Java application). Connector type is Rule-
Connect-Java
6. RDB (Allows sql executions against an external database). Connector type is
Rule-Connect-RDB
7. BPEL (Communicate with other rules engines). Layered on top of the SOAP
integration interface. Connector type is Rule-Connect-BPEL
8. IBM Web Sphere MQ (Messaging). Connector type is Rule-Connect-MQ
9. JMS (Industry standard messaging model). Connector type is Rule-Connect-JMS
Services.
A service is a software component that can be accessed by other applications. Services
are usually implemented with web services and EJB.
Service Method in PRPC:
1. A service method is a rule which invokes a specific service activity
2. It is listed in the Integration-Services category.
Service Package in PRPC:
1. Several service method rules may be needed to form a service. These may be
grouped together to form a “service package”. Such service packages are listed in
the Integration-Resources category.
2. Deployment tab in the Service package has a “Generate Deployment Files” button
which create deployment files for appropriate service types.
Services in PRPC represent individual published functions or methods accessible by
external systems. Four step process:
1. Receives inbound messages from external system to service method on PRPC.
2. The messages are converted to clipboard properties
3. Activity (defined in the method form) consumes these clipboard values and
assembles an appropriate response
4. Response is then sent to external system.
Examples of standard service types which are deployed as files:
1. COM (Allows interaction with Windows-based apps). Service rule type is Rule-
Service-COM. Deployment in service package generates .dll file.
2. CORBA. Allows cross-platform application interaction. Service rule type is Rule-
Service-CORBA. Deployment in service package generates .dll file.

3. 3. EJB. Allows service-side interaction with Java apps. Service rule is Rule-Service-
EJB. Deployment in service package generates .jar file
4. Web Services (Standard SOAP and .net). Allows cross-platform, industry-
standard integration. Rule types are Rule-Service-SOAP and Rule-Service-
dotNet. Service package deployment generates .wsdl file.
5. Portlets. Provides web portal conforming to Java Portlet Specification (JSR 168).
Rule type is Rule-Service-Portlet. Deployment generates .war file.
6. BPEL. Allows interoperability among business rules engines. Rule type is Rule-
Service-BPEL. Is deployed directly from the service as a WSDL file.
Examples which are NOT deployed as files and may require listener rules and other
server connection facilities:
1. MQ. Provides messaging model. Service rule type is Rule-Service-MQ
2. JMS. Provides industry standard messaging model. Rule type is Rule-Service-
JMS.
3. Inbound email. Allows PRPC to receive email. Service rule type is Rule-Service-
Email
4. File import. Allows PRPC to import files. Service rule type is Rule-Service-File
There are 2 distinct APIs available for calling service rules from a Java program: Rule-
Service-Java and Rule-Service-JSR94
1. In order to use the former, PRPC should be deployed as an EJB
2. In order to use the latter PRPC should be deployed as an EJB or a web
application.
Data mapping (relevant for both connectors as well as services).
A data mapping is a table or array that associates data fields (received from or sent to an
external application) to properties within PRPC. Data mapping is defined in service and
connector rule forms.
When PRPC talks to an external system, at run time, the outgoing call/message as well as
incoming call/message needs to be interpreted. The data mapping decides this
interpretation using the instructions in the rule forms.