Packaging Portal Transport Archives 

Use

You have the following two scenarios for creating archives for transporting portal content:

Scenario	Procedure
I. You do little Java development and do not want to use the Java Development Infrastructure. In this case you only need to use the export and import function of the portal.	You pack your portal content objects together with the PAR files into an EPA archive. You export objects to an EPA archive with the portal export function. See also Creation of an EPA Archive for the Portal Export. You import the objects with the portal import function.
II. You develop a lot of custom portal applications and J2EE applications, such as Web Dynpro. You therefore also want to use the Java Development Infrastructure.	You export portal content objects to an EPA archive within portal administration, where PAR files are excluded from the export. PAR archives are created in the development environment. To combine the two archive formats in one archive, they must be converted to other formats. Command line tools are available for this purpose. See also Creating SCA and SDA Archives. You can deploy these archives to the portal with the SAP Software Deployment Manager. This replaces the import function in the portal.

Configuration of the Export Behavior in the Portal

Depending on the scenario you choose, you get the following mechanism in the portal for the export:

·        In scenario I, the EPA archives contain PAR files.

·        In scenario II, PAR files are excluded from the export and are not contained in the EPA archives.

You can configure the export behavior of PAR files in the PCD configuration in the configuration file PCDStartup.Properties.

To prevent the export of PAR files, insert the following value for parameter Pcd.TransportApplication.Export.ExcludeObjectTypesAfterRuleProcessing: com.sapportals.portal.application.applicationrepository.Archive.

The setting causes the associated resource bundles to be transported as well. For more information see Configuring Transport.

To enable PAR files to be exported, leave the value empty. In this way you define that no object type should be excluded from the export.

 

It is important that you decide which export mechanism you want to use: either the PAR to EPA or PAR to EAR mechanism. If you choose the second one, you must prevent PAR files from being included in the EPAs. This could cause inconsistent transports because the PAR files could for example depend on other parts of the EAR file (e.g. logging configuration) that are not contained in the EPA file. Once you have decided on one scenario, you should not change to another scenario.

See also Note 725797.