Export in File System

This option allows channel structures (with pages; service instances; local groups; and access control) to be exported to the application server's file system. The structural elements are organized into files and folders according to the channel hierarchy.

By default, the export to the file system stores the data in lumisdata/structure/default. This path can be changed with the system property lumis.portal.structure.sync.default.path. If the property refers to a directory outside lumisdata/structure, the exported files will not be replicated to other servers in a multi-server environment. This property should only be used in development environments, for example, to allow direct export/import in a version-controlled area.

The following are exported: channels, pages, service instances (without content), interface instances, ACLs, property bags, local groups and their members (only the reference to the member, not their properties) that are local groups (provided the member's channel is not configured to be ignored in import/export), styles of interface instances that have been registered in the build, types of transformations, and portal access permissions for local groups.

In the case of styles, only the style registrations are exported, the XSL files are not included. Public and shared styles that could be used by exported service instances are exported; and the styles isolated to any interface instance that is also being exported.

The following are not exported: global groups or users, local users, members of local groups that are users, referenced files (e.g.: XSL, CSS, etc.), service content, global registrations made in the Configuration areas of the portal administration.

Not all elements have their identifiers exported. Identifiers of important elements (channels, pages, service instances, interface instances, groups, styles) are exported. Other identifiers are not exported and new ones will be generated during import.

As an example, consider the export of the channel "Event Agenda," as shown below:

With a right-click on the channel "Event Agenda," select the Export option. Then, the export type selection screen will be displayed. In it, select the "Structure" option, as follows:

A screen showing the export progress will be presented, as below:

After the export, checking the file system, we can see the following structure (inside the lumisdata folder):

In this case, we can see that the channels "Portal," "Event Agenda," and "Administration" generated a folder for each during the export with their friendly identifier as the name. Opening the folder "event-agenda," we can see:

In this folder, we can find the files related to the channel "Event Agenda," the pages "Details," "List," and "Quick List," and the service instance "Event Agenda."