Whenever you do a portal server installation, you might have noticed that there are lot of applications which are pre deployed as part of the installation process. On top of that we develop and deploy our custom applications.
Here are the few points that differentiate between the user deployed WAR file and Pre Deployed EAR files of a Portal application. These differences are captured based on the few impacted portal areas.
Portlet application
WAR: The portlet application is provided as WAR file. The portal configuration is read directly from the file stream. The WAR file is deployed into the application server by the portal.
EAR: The portlet application is already extracted and deployed into the application server as part of the EAR file. The portal server reads the available portal configuration information (portlet.xml, etc.) from the location where the contained WAR file was extracted to.
Context Root
WAR: The context root is assigned by the portal during WAR deployment.
EAR: The context root is assigned by the EAR developer and stored in the file application.xml. You must ensure that the context root that you specify when you register the portlet matches the one specified in the EAR application.xml.
Display name
WAR: The display name is assigned by Portal during WAR deployment.
EAR: The display name is assigned by the EAR developer and stored in the file application.xml.
WebSphere Application Server policy for portlet applications
WAR: The policy is stored in the WAR file and promoted to the EAR file by the portal during WAR deployment.
EAR: The policy is stored in the EAR file.
Portlet administration
WAR: You administer WAR files using the XML configuration interface and the administration portlets.
EAR: You can register EAR files only by using an XML script with pre deployed mode. You can remove EAR files by using either the administration portlet or an XML script.
Portlet application
WAR: The portlet application is provided as WAR file. The portal configuration is read directly from the file stream. The WAR file is deployed into the application server by the portal.
EAR: The portlet application is already extracted and deployed into the application server as part of the EAR file. The portal server reads the available portal configuration information (portlet.xml, etc.) from the location where the contained WAR file was extracted to.
Context Root
WAR: The context root is assigned by the portal during WAR deployment.
EAR: The context root is assigned by the EAR developer and stored in the file application.xml. You must ensure that the context root that you specify when you register the portlet matches the one specified in the EAR application.xml.
Display name
WAR: The display name is assigned by Portal during WAR deployment.
EAR: The display name is assigned by the EAR developer and stored in the file application.xml.
WebSphere Application Server policy for portlet applications
WAR: The policy is stored in the WAR file and promoted to the EAR file by the portal during WAR deployment.
EAR: The policy is stored in the EAR file.
Portlet administration
WAR: You administer WAR files using the XML configuration interface and the administration portlets.
EAR: You can register EAR files only by using an XML script with pre deployed mode. You can remove EAR files by using either the administration portlet or an XML script.
No comments:
Post a Comment