Question
Coforge DPA private limited
AU
Last activity: 3 Mar 2017 4:47 EST
Meaning of PRPC intalled as J2EE application or web application
Hi, I am confused about the meaning of PRPC installed as J2EE application or web application.
Can someone please clarify.
Thanks in advance.
***Moderator Edit: Vidyaranjan | Updated Categories***
Accepted Solution
Instellars
IN
Hi Madhusudan,
WAR (Web Archive) is a module that goes into web container of Java EE application server. A JavaEE application server has two containers (runtime environments) - one is a web container and the other is a EJB container.
The Web container hosts web applications based on JSP/Servlets API - designed specifically for web request handling - more of request/response distributed computing. Web container requires the web module to be packaged in WAR file that is a special JAR file with a web.xml file in the WEB-INF folder.
EJB container hosts enterprise java beans based on EJB API designed to provide extended business functionality such as declarative transactions, declarative method level security and multiprotocol support - more of RPC style of distributed computing. EJB container required EJB module to be packaged in JAR file having ejb-jar.xml file in META-INF folder.
Enterprise application may consist of one or more modules that can either be Web modules (packaged in WAR file) or EJB modules (packaged in JAR file) or both of them. Enterprise applications are packaged in EAR file that is a special JAR file containing an application.xml file in the META-INF folder.
Hi Madhusudan,
WAR (Web Archive) is a module that goes into web container of Java EE application server. A JavaEE application server has two containers (runtime environments) - one is a web container and the other is a EJB container.
The Web container hosts web applications based on JSP/Servlets API - designed specifically for web request handling - more of request/response distributed computing. Web container requires the web module to be packaged in WAR file that is a special JAR file with a web.xml file in the WEB-INF folder.
EJB container hosts enterprise java beans based on EJB API designed to provide extended business functionality such as declarative transactions, declarative method level security and multiprotocol support - more of RPC style of distributed computing. EJB container required EJB module to be packaged in JAR file having ejb-jar.xml file in META-INF folder.
Enterprise application may consist of one or more modules that can either be Web modules (packaged in WAR file) or EJB modules (packaged in JAR file) or both of them. Enterprise applications are packaged in EAR file that is a special JAR file containing an application.xml file in the META-INF folder.
Basically EAR file is a superset containing WAR files and JAR files. Java EE application servers allow deployment of standalone web modules in WAR file though internally they create EAR file as wrapper around WAR files. Standalone web container such as Tomcat and Jetty do not support EAR files - these are not full fledged application servers. Web applications in these containers are to be deployed as WAR files only.
In application servers - EAR file contains configuration such as application security role mapping, EJB reference mapping and context root url mapping of web modules.
Apart from Web modules and EJB modules EAR files can also contain connector modules packaged as RAR files and Client modules packaged as JAR files.
So, basically if your PRPC application is limited to web specific operations, you can achieve that with a war deployment but if you need enterprise level operations along with the web operations, you will have to go with ear deployment.
OCBC Bank
SG
Hi MadhuSudhan,
The Pega Media archive has Pega ear and war. Pega can be deployed as war file or ear file based on the type of server you are using(Webserver or an App server)
If the war file is deployed, then it is web application. If the ear file is deployed, then then it is an Enterprise application(J2EE)
Hope this helps.
Thanks,
Sandeep G.
Coforge DPA private limited
AU
Thanks Sandeep. But I am still not much clear. What I know is that we always have webserver and appserver( for load balancing). and how do we decide that we need to deploy ear or war file.
Thanks,
Madhusudan
Accepted Solution
Instellars
IN
Hi Madhusudan,
WAR (Web Archive) is a module that goes into web container of Java EE application server. A JavaEE application server has two containers (runtime environments) - one is a web container and the other is a EJB container.
The Web container hosts web applications based on JSP/Servlets API - designed specifically for web request handling - more of request/response distributed computing. Web container requires the web module to be packaged in WAR file that is a special JAR file with a web.xml file in the WEB-INF folder.
EJB container hosts enterprise java beans based on EJB API designed to provide extended business functionality such as declarative transactions, declarative method level security and multiprotocol support - more of RPC style of distributed computing. EJB container required EJB module to be packaged in JAR file having ejb-jar.xml file in META-INF folder.
Enterprise application may consist of one or more modules that can either be Web modules (packaged in WAR file) or EJB modules (packaged in JAR file) or both of them. Enterprise applications are packaged in EAR file that is a special JAR file containing an application.xml file in the META-INF folder.
Hi Madhusudan,
WAR (Web Archive) is a module that goes into web container of Java EE application server. A JavaEE application server has two containers (runtime environments) - one is a web container and the other is a EJB container.
The Web container hosts web applications based on JSP/Servlets API - designed specifically for web request handling - more of request/response distributed computing. Web container requires the web module to be packaged in WAR file that is a special JAR file with a web.xml file in the WEB-INF folder.
EJB container hosts enterprise java beans based on EJB API designed to provide extended business functionality such as declarative transactions, declarative method level security and multiprotocol support - more of RPC style of distributed computing. EJB container required EJB module to be packaged in JAR file having ejb-jar.xml file in META-INF folder.
Enterprise application may consist of one or more modules that can either be Web modules (packaged in WAR file) or EJB modules (packaged in JAR file) or both of them. Enterprise applications are packaged in EAR file that is a special JAR file containing an application.xml file in the META-INF folder.
Basically EAR file is a superset containing WAR files and JAR files. Java EE application servers allow deployment of standalone web modules in WAR file though internally they create EAR file as wrapper around WAR files. Standalone web container such as Tomcat and Jetty do not support EAR files - these are not full fledged application servers. Web applications in these containers are to be deployed as WAR files only.
In application servers - EAR file contains configuration such as application security role mapping, EJB reference mapping and context root url mapping of web modules.
Apart from Web modules and EJB modules EAR files can also contain connector modules packaged as RAR files and Client modules packaged as JAR files.
So, basically if your PRPC application is limited to web specific operations, you can achieve that with a war deployment but if you need enterprise level operations along with the web operations, you will have to go with ear deployment.