Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Supported Operations

Import/Export provides IMPORT, EXPORT and DELETE operations for supported portal entities.

Import

Adds the entity defined in the specified XML to the portal database. If the specified entity is already present – determined by Id, Name, or primary key, as appropriate – this operation will update the existing entity to match the information provided in the XML.

Usage
  >ant crn-import -Ddir={path-to-directory} [-Dpattern={regex}]

Where path-to-directory is a file system directory, absolute or relative, containing uPortal Import/Export XML; and regex is an (optional) Java Regular Expression specifying a file name pattern that candidate files must match or be ignored by the importer.

The -Dpattern Argument

Regex special characters overlap heavily with OS/Shell special characters. It's often better to avoid the -Dpattern argument altogether. You can always place desired files into a new directory for import.

Export

Creates XML representations of the requested entities and writes them to the specified file system location.

Usage
  >ant crn-export [-Ddir={path-to-directory}] -Dtype={entity-type} [-Dsysid={entity-identifier}]

Where path-to-directory is a file system directory, absolute or relative, wherein XML will be written; and entity-type is any supported entity type (see table below); and entity-identifier is the Id or Name of a single entity of the specified type. The -Dsysid argument is not required for entity types that begin with "all-."

Named Sub-directories

On export, XML documents will be organized into sub-directories by entity type: e.g. channel, layout, user, etc.

Table of Entity Types

entity-type

sysid

export

delete

notes

all

(error)

All portal entities

(error)

 

all-layouts

(error)

All user layouts

(error)

Normal users generate .layout files on export; fragment owners generate .fragment-layout

all-permissions

(error)

All permissions

(error)

A permission entity is one owner, target, activity, type, and principal

all-permission_sets

(error)

All permission_sets

(error)

A permission_set entity is one owner, target, activity, and type, but zero or more principals

all-memberships

(error)

All local (RDBMS) memberships

(error)

 

all-channels

(error)

All channels

(error)

 

all-channel-types

(error)

All channel types

(error)

 

all-groups

(error)

All local (RDBMS) groups

(error)

 

all-group_memberships

(error)

All local (RDBMS) group_memberships

(error)

 

all-users

(error)

All users

(error)

 

all-themes

(error)

All themes

(error)

 

all-structures

(error)

All structures

(error)

 

all-entity-types

(error)

All entity types

(error)

"Entity types" here refers to the UP_ENTITY_TYPES table; these are not the same as Import/Export entity types

all-fragment-definitions

(error)

All fragment definitions

(error)

Requires the RDBMConfigurationLoader

layout

username

 

 

 

channel

fname

 

 

 

channel-type

name

 

 

 

group

name

 

 

 

group_membership

name

 

 

 

user

username

 

 

 

theme

name

 

 

 

structure

name

 

 

 

entity-type

name

 

 

 

fragment-definition

name

 

 

 

(error) =not specified or not supported

Import/Export

  • No labels