RMApiInit properties descriptions

CreateUser

This property sets the API's permission to create user objects in the LDAP directory. Set this to false only when you are using RM's mapping feature for lwsnRMResource and People objects. When this parameter is set to false, Lawson APIs are tolerant of the inability to create user objects directly in the LDAP server. The APIs will, however, be able to consume any existing user objects. You can create an underlying object for each user with your third party LDAP tool, and then, by creating a user with the same Id in the RM system, RM will simply add its objectclasses and attributes to the externally created user object.

DeleteUser

This parameter sets the API's permission to delete user objects in the LDAP directory. Set this to false only when you are using RM's mapping feature for lwsnRMResource and People objects. When this parameter is set to false, Lawson APIs are tolerant of the inability to delete user objects from the LDAP server. With the property set to false, the API doesn't remove an object from LDAP, it simply removes all of Lawson's attributes and auxiliary objectclasses. When removal of attributes and auxiliary objectclasses is complete, the object is no longer visible to the Lawson system, but it remains in the LDAP server.

ChangeMappedAttrs

This parameter further restricts the APIs when dealing with customer-owned data. Set this to false to keep RM APIs from altering any attributes that are mapped to attributes in your structural class. This assumes that if an attribute such as FirstName is really mapped to sn that the control of the content in that attribute is external to the Lawson system. This affects how the API treats all mapped attributes and its behavior will only be noticeable if you have mapped objects.

UseLsLogging

Set this to true to enable logging in RM. There are limited log statements in RM, so this won't provide significant information. The logging levels are controlled by $LAWDIR/system/ls_logging.properties.