Show TOC

Background documentationImport Format for UME Principals Locate this document in the navigation structure

 

You can define user, group, and role data in the user management engine (UME) import format. You can then import this data into SAP NetWeaver Application Server (AS) Java. This enables you to perform mass import or even update operations on your user management data.

For more information, see Importing User Management Data.

Prerequisites

The UME import function supports Unicode Transformation Format-8 (UTF-8) encoding.

Structure

Each principal is defined by a record consisting of  a list of attributes listed each on a separate line. Each data field appears on a separate line as follows:

Syntax Syntax

  1. <name>=<value>
End of the code.

Use delimiter tags to separate each record: [User], [Group], or [Role]. You must include a delimiter tag as the first line of each record.

Attributes are either required or optional. You can omit optional attributes or assign no value, for example, Country=.

Recommendation Recommendation

Always include the equal sign (=) after an attribute name, even if the attribute is not assigned any value.

End of the recommendation.

All attribute names, but not attribute values, are case insensitive.

For more information, see:

Assignment Attributes

With the assignment attributes, role, group, action, and user, you can make multiple entries to improve readability. If the principal listed in the assignment attribute does not exist, an error occurs and the UME does not create the corresponding record you were trying to import. Assignments are exclusive lists. When updating a principal and overwrite is enabled, the UME adds the listed assignments to the principal and deletes any other assignments. The system does not keep a record of previous values.

Example Example

role=rolea; roleb; rolec

The UME assigns the roles listed to the principal and removes any other roles previously assigned.

End of the example.

With the plus (+) and minus (-) signs you can change the behavior of the import of assignments.

  • A plus before or after the assignment directs the UME to add the assignment to the principal.

  • A minus before or after the assignment directs the UME to remove the assignment.

Example Example

user=+aglenn, mhaddem+, -bkapilsky

The UME assigns users aglenn and mhaddem to the principal and removes the assignment of bkapilsky.

End of the example.
Portal Roles

There is limited support for the import of portal roles. You can only import portal role assignments. You can only update the role assignments of existing portal roles with the import function. You cannot use this function to create portal roles.

  • Use the unique name to designate portal roles.

    Example Example

    role=pcd:portal_content/test_role/roleA

    End of the example.

    Example Example

    [role]

    rid=pcd:portal_content/test_role/roleA

    user=Giovanni.Ricci; Roberta.Esposito;

    End of the example.

  • You can import and export remote role assignments, if the remote role exists with the same name in the same producer portal. Use the following syntax:

    Syntax Syntax

    1. gp:/<producer_alias>/<PCD_URL>
    End of the code.

    Example Example

    role=gp:/ProducerA/pcd:portal_content/test_producer_a/roleA;

    End of the example.