Running the ldifgen utility

When you make changes to your Infor Lawson schema using Schema Editor, the changes are stored in a temporary location and do not affect production data until you run the Infor Lawson ldifgen utility and then import the resulting LDIF. The ldifgen utility creates an ldif file that you import into your LDAP directory (using native LDAP tools). After you run ldifgen and import the ldif file into your LDAP directory, the schema changes you made will take effect.

  1. Open a command prompt in the Infor Lawson Environment and move into the location: LAWDIR/system
  2. Run the command shown in the syntax. A sample command and a table describing the parameters are also shown.:
    Command syntax:
    ldifgen xmltoschemaldif input_file.xml -f schema_output_file.ldif -r reorg_output_file.ldif -m update_output_file.ldif -D DN  
-w password -h hostname -p port# -v
    Command example:
    ldifgen xmltoschemaldif RmMeta_Default.xml -f NewSchema.ldif -r NewSchemaReorg.ldif -m NewSchemaUpdate.ldif -D cn=ldapadmin,o=lsfprod 
-w MyAdminPWD -h MyLDAPServer -p 35000 -v
    Parameter Description
    input_file.xml In the example, this is: RmMeta_Default.xml

    The file is used by Schema Editor to write metadata changes. This file was defined when you installed Infor Lawson Security / Resource Management.
    -f schema_output_file..ldif In the example, this is: NewSchema.ldif

    schema_output_file.ldif is the name of the output file where the schema modification ldif will be written.

    -r reorg_output_file.ldif

    In the example, this is: NewSchemaReorg.ldif

    This is where the data modification ldif will be written.

    Note: In some situations, a reorg file will not be included in the ldifgen output. For example, if you are changing the default value of an attribute or adding a new attribute that has not yet been populated, a data transformation does not occur and, therefore, no reorg file is generated, or, in some cases, a file is generated but has no records.
    -m update_output_file.ldif In the example, this is: NewSchemaUpdate.ldif

    This is where the updated ldif metadata file will be written. Metadata in this case refers to the structure of the Infor Lawson objects in the LDAP.

    -m DN

    In the example this is: cn=ldapadmin,o=lsfprod

    DN is the LDAP Distinguished Name used to bind to the LDAP server.
    -w password password is the password that you use to run the LDAP server.
    -h host host is the hostname of the LDAP server.
    -p port port is the port number that the LDAP server is listening on.
    -v Optional. Use the -v (verbose) parameter to run the command with detailed output turned on.
    When the process completes, the message "Command complete successfully," appears.
  3. Check the resulting output files (reorg_output_file.ldif, schema_output_life.ldif and update_output_file.ldif) to verify that they contain data and look the way you expect. Depending on the changes you made through Schema Editor, an empty output file could be a normal situation. It is not necessary to import an empty file, however, doing so will not cause any issues.
  4. Using the command specified by your LDAP vendor, load the output files in the following order:
    • reorg_output_file.ldif (if it exists)
    • schema_output_file.ldif
    • update_output_file.ldif
    For example, if you use ADAM, the command would be ldide.
  5. Before the new schema can take effect, you must restart the system.
    1. Stop your application server.
    2. Run the Infor stoplaw command.
      When you are ready to restart the Infor Lawson system, run the startlaw command and then start your application server.