Introduction

The Import LAMS 1 Users screen allows you to import users (and their accompanying organisations and classes) from a LAMS 1 server, into your LAMS 2 server.

Things to Consider

• Since user passwords in LAMS 1 were md5 encrypted, we cannot use the same passwords in LAMS 2, which does not use md5. Every user that is imported will have their password set to their username; they will be prompted to update their password when they first login.
• LAMS 1 users whose username already exists will not be imported - you'll be notified of these users when the import is complete.
• You can choose to view users and organisations created as part of a LAMS 1 integration, if your LAMS 1 server was integrated with an LMS. However importing these is not recommended.
• Only users and their organisations and classes are imported; lesson data and saved sequences are not.
• All LAMS 1 organisations and classes are imported as groups in LAMS 2. It's preferable to carefully select which organisations you wish to import, rather than import every organisation, child organisation, and session class.

Preparation

Before you start the import, you will need access to your LAMS 1 database in order to make a dump of the necessary data.

1. Login to LAMS 2
2. Click Sys Admin
3. Click Import LAMS 1 Users
4. Download the file lams1_user_org_export.sql
5. At the command/shell prompt of your LAMS 1 database server, run the above script on your LAMS database:
   shell> mysql DBNAME < /path/to/lams1_user_org_export.sql \-u DBUSER \-p > /path/to/lams1_users_orgs.txt

   Replace DBNAME and DBUSER with the database name and user of your LAMS database. You'll be prompted for the password. If you don't remember these details, you can gather them from your LAMS 1 installation:

   /path/to/jboss/server/default/deploy/mysql-service.xml

   Look under

   <attribute name="ManagedConnectionFactoryProperties"> <properties> <config-property name="ConnectionURL" type="java.lang.String">jdbc:mysql://localhost/lams</config-property>

   Here the database name is 'lams', and the username and password will be specified below this line.

6. Your LAMS 1 users (contained in lams1_users_orgs.txt) are ready to be imported.

Import Options

Loading lams1_users_orgs.txt

Include integration users and organisations

This option is unchecked by default, and it is recommended to leave it this way. These users and organisations are used by the LAMS 1 modules/plugins of various LMS' such as Moodle; they aren't compatible with LAMS 2. However checking this option will allow you to view the data if you wish.

Selecting Organisations and Session Classes

Check the boxes of the LAMS 1 organisations and classes you want to import. Each one will be created as a new group in LAMS 2.

Only import users that are members of organisations/session classes to be imported

This option is checked by default. Uncheck it if you want to import all user accounts, whether or not they are part of a group that you've selected to import.

Exporting from LAMS <= 1.0 The export script (lams1_user_org_export.sql) is intended for LAMS 1.0.1 and upwards; if you have LAMS 1.0 or earlier, then it will fail on the first line. Just comment out this line and you'll be fine. Details: the first line searches for the existence of external servers integrated with your LAMS installation, in order to filter their users from the list of 'native' LAMS users. Before 1.0.1 LAMS did not have this feature.