Example 1: Creating a loadusers XML Input File for Self-Service Center Users

The users in this example input file have the following characteristics:

  • They make use of the default user identity. None of the users in the file runs batch jobs or has special access needs that require them to have unique IDs on the operating system and unique identities on the Lawson Environment service.

  • They use only Lawson Self-Service centers. This is for the sake of simplicity in the example.

Global attributes to be populated through loadusers

Global attributes are assigned to all users unless the user's entry contains an override. This information appears at the top of the XML input file.

The global attributes used in the example installation are shown in the sections that follow.

ROLEDATA node

  • ROLE ID: The name of a role that you want to create through loadusers. Roles must exist before you can assign users to them. You can create a role and assign it to users through the same XML input file but the ROLEDATA node must appear above the USER node in the file.

  • Description: The description of the new role that you are creating.

  • ParentRole: If the new role that you are creating is based on an existing, or parent role, declare the name of the parent role in the input file. (The parent role must already exist.)

GROUPDATA node

  • GROUP ID: The name of a group that you want to create through loadusers. Groups must exist before you can assign users to them. You can create a group and assign it to users through the same XML input file but the GROUPDATA node must appear above the USER node in the file.

  • Description: The description of the new group that you are creating.

User attributes to be populated through loadusers

In the example installation, loadusers populates the attributes shown in the sections that follow. The attributes are, for the most part, determined locally, but a few attributes are required by Lawson.

USERDATA node

  • SSOPPASSWORD: A global attribute, all user entries will be populated with the same password which they can then change through their user interface.

  • ProductLine: A global attribute that will assign the same product line to all users unless the individual user entry contains an overriding attribute.

  • ID: This is the SSOP ID that this user will use to log into the Lawson system.

  • RMID: This attribute is the key unique identifier for the Lawson system. However it does not need to be populated in this case. This is because the sample installation, like most Lawson customers, wants the ID (SSOP ID) and the RMID to be the same. If you leave RMID blank with two double-quote marks as placeholder, the attribute will be populated with the same data as in ID (SSOP ID).

    Note: It is not a requirement for the SSOP ID and RMID to be the same. However, because this is useful for administration purposes, most customers want them to be the same.

  • Name: First and last name separated by a space

  • First Name

  • Last Name

  • CheckLS: Does the user use Lawson Security, YES or NO? (Default is NO.) In this example installation, all users should have this attribute set to YES.

  • Role: Any roles that you want to assign to this user. Separate multiple role names with commas.

  • Group: Any groups that you want this user to be a member of. Separate multiple group names with commas.

IDENTITIES node

  • ID: The user's identity on this service. For Self-Service centers, this must be the same as the RMID.

  • SERVICE: The name of the service that you are populating for the user. In the example installation, this is LAWAPP_EMPLOYEE for the Employee/Manager application and LAWAPP_REQUESTER for the Requisition Center application.

  • COMPANY: For applications that require Company for each user (for example, the Employee/ Manager Self-Service center), populate Company for the user.

  • EMPLOYEE: The user's ID on the Employee/Manager Self-Service centers.

  • REQUESTER: The user's ID on the Requisition Center application.