Role of JRE in aem architecture
Java Runtime Environment [JRE]:
AEM is pretty much a blend of or gathering of containers, jsps [Java Server Pages], servlets, Java classes alongside static assets, for example, HTML, pictures, resources and so forth. To drive this design, it needs JRE.
This makes AEM good with any OS that supports required JRE.
Rock Platform:
Rock stage is key job player in AEM stack. Rock is Adobe's open web stack.
As you can see from picture above, Granite stage comprises of beneath recorded modules:
CQSE Servlet Engine
CRX Content Repository
Sling Content Delivery
OSGi Framework
CQSE Servlet Engine: AEM requires an application server that supports Java Servlets API 2.4 or later. The AEM programming bundle is accessible in two structures:
cq-quickstart.jar: it incorporates everything expected to get fully operational (additionally called as an "independent executable container"). Quickstart Standalone container record contains an inherent servlet motor. As the name "Independent" proposes client can basically double-tap the container record to introduce an AEM occurrence with worked in servlet-motor. You don't require any devoted outside application server for servlet taking care of. For this situation, you just need a JRE and an independent quickstart JAR record.
cq-quickstart.war: for sending in an outsider application server. WAR document doesn't contain worked in servlet motor. For this situation, you need a JRE, a WAR record and an outsider application server for servlet taking care of.
At last AEM come with its own architecture generally aem developers search about aem architecture so using the aem architecture aem developer can understand easily about the aem technology stack.
AEM is pretty much a blend of or gathering of containers, jsps [Java Server Pages], servlets, Java classes alongside static assets, for example, HTML, pictures, resources and so forth. To drive this design, it needs JRE.
This makes AEM good with any OS that supports required JRE.
Rock Platform:
Rock stage is key job player in AEM stack. Rock is Adobe's open web stack.
As you can see from picture above, Granite stage comprises of beneath recorded modules:
CQSE Servlet Engine
CRX Content Repository
Sling Content Delivery
OSGi Framework
CQSE Servlet Engine: AEM requires an application server that supports Java Servlets API 2.4 or later. The AEM programming bundle is accessible in two structures:
cq-quickstart.jar: it incorporates everything expected to get fully operational (additionally called as an "independent executable container"). Quickstart Standalone container record contains an inherent servlet motor. As the name "Independent" proposes client can basically double-tap the container record to introduce an AEM occurrence with worked in servlet-motor. You don't require any devoted outside application server for servlet taking care of. For this situation, you just need a JRE and an independent quickstart JAR record.
cq-quickstart.war: for sending in an outsider application server. WAR document doesn't contain worked in servlet motor. For this situation, you need a JRE, a WAR record and an outsider application server for servlet taking care of.
At last AEM come with its own architecture generally aem developers search about aem architecture so using the aem architecture aem developer can understand easily about the aem technology stack.
Comments
Post a Comment