Packaging a Portal Application as Part of a J2EE Application 

Use

A Portal Archive (PAR) file can be packaged as part of an Enterprise Application Archive (EAR). If such an EAR file is deployed using J2EE deployment facilities, the PAR is forwarded to the PRT container. This container stores the PAR file in the Portal Content Directory (PCD) and notifies all portal nodes in the cluster to update the local deployment.

Procedure

So that the J2EE knows about the additional PAR module, list it in the additional application-j2ee-engine.xml deployment descriptor of a J2EE application. This reference, called the deployment reference has the format described below. The reference contains the following tags:

Tag	Tag Value
modules-additional	<none>
module	<none>
entry-name	<name of the portal application (file name including the extension)>
container-name	PortalRuntimeContainer

Usage Reference

If a portal application is deployed as part of an EAR file, it does not automatically mean that the portal application can be used in the SAP J2EE applications that are kept in the EAR file. To enable such usage, the portal application must be stated as reference.

Cluster Considerations

·        Deploy:

If a PAR is deployed as part of an EAR in a cluster, then the mechanism is as follows. Only one SAP J2EE node, the node where the deployment was triggered, will receive the PAR file in its PRT container. This container then will upload the PAR in the PCD and it will trigger the update of the local deployment of all portal nodes. The PRT containers on all other nodes will only be notified about the deployment.

·        Undeploy:

The PRT container on the node on which undeploy was triggered will remove the PAR from the PCD and notify all portal nodes to remove the local deployment. The PRT containers on the other nodes will realize that the PAR was already removed from the PCD and will do nothing.

Multiple File Deployment

If multiple PARs are contained in one EAR, the PARs are uploaded in one step to the PCD. Also the update of the local deployment on all portal nodes is made in one step.

Error Reporting During Deployment

If there are errors during deployment, a message appears in the corresponding tool: SDM, Visual Administrator. For detailed error messages, check the log files of the J2EE deploy service and the portal log.

Example

This is the relevant part of an additional deployment descriptor belonging to an EAR file containing two PAR files.

<modules-additional>    <module>       <entry-name>          PARInEARPortalApp.par       </entry-name>       <container-type>          PortalRuntimeContainer       </container-type>    </module>    <module>       <entry-name>          test.portal.MyPortalTest.par       </entry-name>       <container-type>          PortalRuntimeContainer       </container-type>    </module> </modules-additional>