Portlet deployment

The more you are familiar with the portal server, the more you will realize that there are different options for the deployment of portal applications. Portlets can be deployed as standard EAR through the deployment manager administrative console, using the GUI or via the wsadmin scripting interface. This allows for the cluster to notify each node of the deployment and allows portlets to be combined with different EAR-level resources such as EJBs, web services, or other web modules. This pre-deployed application must be updated via the EAR file in the WebSphere Application Server and the WAR file in portal using the XML configuration interface. There are some restrictions such as cross-updates of a pre-deployed EAR file with WAR are not possible yet under documented tasks. The other common way to deploy a portlet is to install it on the primary node of a portal cluster using the portal administration scripting languages such as Jacl; via GUI, or via XMLAccess interface...