Filling a Transport Package with Content 

Use

Before being able to export a transport package, it must first be populated with content.

The transport package is not intended for the transport of themes. For more information see Exporting and Importing Themes.

Prerequisites

You created a transport package and are editing it in the Portal Content Studio.

Procedure

...

       1.      Add content objects to the package. You can add objects to a package in the following ways:

¡        You can add individual objects. In the Portal Catalog, click on the object with the secondary mouse button and choose Add <Object> to Transport Package.

¡        You can add entire folder hierarchies with the objects they contain. To do so, click on a folder of a given hierarchy level in the Portal Catalog with the secondary mouse button and choose Add all objects to transport package.

¡        You can add a folder without including the underlying objects. To do so, click on a folder with the secondary mouse button in the Portal Catalog and choose Add object to transport package.

You can also add existing packages to a package and export them.

Use Remove for content objects that do not need to be in the export package.

With the Properties function you can display the properties of objects you added to the package.

With the Object Preview function, you can display the corresponding portal view for pages and iViews.

       2.      Define export properties.

Including dependent objects

If you want to include dependent objects in the export (for example, all objects in a role and their source objects), go to the package Property Editor and set the value of the Resolve References property, under the category Export Settings, to Yes.

Dependent objects are included, i.e. the Yes radio button is selected, by default.

For the Resolve References property to be Yes by default, a namespace was defined for the package upon creation, in the Transport ID Prefix field of the general properties page in the Transport Package wizard. If not, the value of this property is No by default.

Filtering dependent exported objects

When including dependent objects in the export, you can filter them to determine that only objects belonging to a certain namespace are to be exported. In the Property Editor, set the value of the References Filter property, under the category Export Settings, as desired.

By default, the namespace prefix of the package, which was defined in the general properties page of the wizard when the export package was created, is automatically entered in this field followed by an asterisk as a wild card, for example, com.<company_name>*.

Dependent PAR archives are not included when you export iViews. For more information, see Packaging of Portal Transport Archives.

With the arrow icons, , you can also sort the object list by object type, name, and ID.

With the  icon, you can select or deselect all objects in the list.

Determining what to transport—including permissions

You can choose to include object permissions in the export. Go to the package Property Editor, under the category Export Settings, to configure the Transport Mode property. You determine here exactly what you transport:

¡        Content

¡        Text only

¡        Content with its permissions

¡        Permissions only

After the export, you can check the package properties again and change them if necessary. See also Maintaining Properties of a Transport Package.

       3.      Save the package with the corresponding contents.

Note that you can only export language packages. Language packages only contain text, and no objects. For more information see Performing Language Transports.

Result

Your transport package is ready. With the Export function, you go to the Export Preview, where you can again check the objects to be exported. The Export button is at the top of the Export Editor.

From the drop-down list to the right of the Export function, you can also call the Permission Editor to assign permissions for the export package. See also Portal Permissions.