the BPM freak !!

Home » BPM » Pega PRPC – EAR vs WAR Deployment!!

Pega PRPC – EAR vs WAR Deployment!!

Follow me on Twitter


Choosing between an EAR file deployment or WAR file deployment

Problem Statement :

  • How do the available deployment packages differ?
  • Which deployment package is suitable to your application’s needs, technical requirements, and organizational policies?

Solution / Recommendation :

  • The Pega Product comes shipped with a package of resources like the DB Scripts/Documentation/Archive wars and ears (prweb.war, prpc_j2ee14_ws.ear etc..)
    But, which one to choose as a best practice and under what situation makes life complicated

So, here we go!!

  • The WAR(Web Archive File) is mostly preferred for the deployment in the Tomcat Server which is just a Web Server (Not an Application Server)
  • The EAR(Eneterprise Archive File)is preferred for the most popular App Servers like Weblogic/Websphere.
  • Pega encourages the deployment of the EAR
  • The EAR Deployment provides an option to add advanced J2EE features to the Application as and when it evolves or is migrated to PROD Env
  • Some of the following features can be explored with a EAR Deployment :
    • Two-phase commit
    • JMS message services
    • Service EJB rules (Rule-Service-EJB rule type)
  • Websphere App Server supports only EAR Deployment.

Happy Learning!! 🙂


1 Comment

  1. Bittu says:

    Hi There,

    Thank u for sharing this unique article on Pega PRPC. Definitely a life saver.
    Do we need to restart the server if new index is added to table?
    We are planning to update our system from PRPC 7.2 to PRPC 7.3. Currently, PEGA is running on IBM WebSphere and IBM DB2 LUW.
    But as part our update, we are planning to migrate to IBM WebSphere and Microsoft SQL Server.
    Could your advice on the below queries?
    1) The current PEGA update script will support for migrating rules from DB2 to Microsoft SQL Server?
    2) The current PEGA update script will support for migrating data from DB2 to Microsoft SQL Server?
    3) If the current update script doesn’t support for the above mentioned (1&2), Will there be any special utility where PEGA system provides for the database migration?
    Architects and developers build the Pega/PRPC instance while administrators and even select business analysts select business analysts have the option of changing workflow rules during runtime.
    Once again thanks for your tutorial.


Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: