File System Import

This option allows channel structures (with pages; service instances; local groups; and access control) to be imported from a file system of the application server.

By default, file system import reads files stored in lumisdata/structure/default. This path can be changed with the system property lumis.portal.structure.sync.default.path. This property also affects the writing of files in the Export to file system.

The import attempts to match the destination structure according to what was generated by the export to file system, adding, updating, and removing elements in the process. The import always maintains known identifiers. 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 identifiers are generated during the import.

The handling of which members of the local groups being imported is treated differently, according to the rules below:

• If the local group is being added by the import:
  • The original members that are local groups will be included as members of the local group being added. If the corresponding group for that member does not exist in the destination, an import error will occur. Members who were local groups in the origin that belong to a channel configured to be ignored by export/import will not be added (they won't even be present in the exported files).
  • The original members that are global groups will be included as members of the local group being added, provided the member exists in the destination. If the corresponding group for that member does not exist in the destination, it will be ignored and the import will continue normally.
• If the local group is being updated by the import:
  • Members that are local groups will be matched with the origin. That is, members that are local groups not present as members in the origin will cease to be members, and members that are local groups in the origin that are not members in the destination will become members (if the corresponding local group for the member does not exist, an import error will occur). But members that are local groups belonging to a channel configured to be ignored by export/import will neither be removed nor added.
  • Members that are not local groups will not be affected. That is, no member that is a global group, local user, or global user will be removed; and no member that is a global group, local user, or global user will be added.

This import process does not generate all the events that a normal structure modification operation would generate. If the solution has any customization that depends on these events, it may be necessary to evaluate if manual adjustments are needed after the import.

Continuing from the previous scenario (in the section Export to file system), it is desired to import the structure “Event Agenda” under the channel "Portal". To do this, by right-clicking on the destination channel (“Portal”), the Import option is selected. Then, a screen will appear to select the origin of the import. There, select the "Structure" option and click "OK".

After this step, a new screen will appear to select the elements to be imported, as follows:

On this screen, the following icons may appear in the element tree:

This allows selection of which elements will be imported. After selecting the elements to be imported and clicking "OK", a progress screen of the operation will be displayed:

Upon completion, a confirmation screen will be displayed: