Configure MemoryLifter clients

Before MemoryLifter clients can access to your server, you have to create a configuration file.  This file must be placed on all clients, so that they "know" how to access the server.

1. Create MemoryLifter Configuration File (MLCFG file)

MemoryLifter Server provides several methods of access to a server. Select one of the following cases and create the corresponding "MemoryLifter Configuration File". Just enter the XML code into an empty text file and save it with any filename but the extension .mlcfg.

1.1   Direct Database Access – NotSynchronized:

In this mode, all clients have direct database access, and it requires the following XML code:

<?xml version="1.0" encoding="utf-8"?>             
<Configuration>
    <Connections>
        <PostgreConnection>
            <Name>MemoryLifter Server</Name>
            <Server>172.22.2.240</Server>
            <Port>5432</Port>
            <UserId>mlifterUser</UserId>
            <Password>mlifter</Password>
            <Ssl>false</Ssl>
            <Database>memorylifter</Database>
            <SyncType>NotSynchronized</SyncType>
            <SyncURI></SyncURI>
            <MediaURI></MediaURI>
            <OtherProperties />
        </PostgreConnection>
    </Connections>
</Configuration>
  • Name: This is the name of the connection that will be displayed to clients. You could enter a name like "<<Institution Name>> – ML Server".
  • Server: The DNS-resolvable server name or IP-address of the server.
  • Port: The port number on the server ("5432" is the default port for a PostgreSQL database server).
  • UserId: The PostgreSQL user, which you setup in Section 3.3: "Create a new database user" (or the default "postgres" super user).
  • Password: The corresponding password here.
  • SSL: Enter "false" as default.
  • Database: The name of the database, which you setup in Section 3.4: "Initialize the MemoryLifter Database" ("memorylifter" is the default).
  • SyncType: Enter "NotSynchronized".

1.2   Half Synchronized – Without Database Access

Using this mode, all clients synchronize the Learning Modules on their local hard disk with the MemoryLifter Web Service. In this mode, media data is synchronized through the Web Service on demand. Use the following XML code:

<?xml version="1.0" encoding="utf-8"?>             
<Configuration>
    <Connections>
        <WebConnection>
            <Name>MemoryLifter Server</Name>
            <SyncType>HalfSynchronizedWithoutDbAccess</SyncType>
            <LearningModulesURI>
                http://172.22.1.249/MLifterWebService/MLifterLearningModulesService.asmx
            </LearningModulesURI>
            <SyncURI>
                http://172.22.2.240/MemoryLifterWebService/PgSyncService.asmx
            </SyncURI>
            <MediaURI>
                http://172.22.2.24/MemoryLifterWebService/MediaFileHandler.ashx
            </MediaURI>
<ExtensionURI>
http://172.22.2.24/MemoryLifterWebService/ExtensionFileHandler.ashx
</ExtensionURI>
        </WebConnection>           
    </Connections>            
</Configuration>
  • SyncType: Enter "HalfSynchronizedWithOutDbAccess".

1.3   Full Synchronized

Using this mode, all clients synchronize the Learning Modules on their local hard disk completely with the MemoryLifter Web Service. In this mode the clients can disconnect from the server after they have synchronized the Learning Modules on their disk. They only need access when they want to synchronize their learning progress back to the server. Use the following XML code:

<?xml version="1.0" encoding="utf-8"?>  
<Configuration>
    <Connections>
        <WebConnection>
            <Name>MemoryLifter Server</Name>
            <SyncType>FullSynchronized</SyncType>
            <LearningModulesURI>
                http://172.22.1.249/MLifterWebService/MLifterLearningModulesService.asmx
            </LearningModulesURI>
            <SyncURI>
                http://172.22.2.240/MemoryLifterWebService/PgSyncService.asmx
            </SyncURI>
            <MediaURI>
                http://172.22.2.24/MemoryLifterWebService/MediaFileHandler.ashx 
            </MediaURI>
<ExtensionURI>
http://172.22.2.24/MemoryLifterWebService/ExtensionFileHandler.ashx
</ExtensionURI>
        </WebConnection>            
    </Connections>            
</Configuration>
  • SyncType: Enter "FullSynchronized".   

2. Publish the MLCFG file

After you have created the MemoryLifter configuration file, copy this file to each client. Now every client must run MemoryLifter and drag the MLCFG file onto the learning window or start page:

clip_image002

After you drop the MLCFG file into MemoryLifter, click on "Import" and open the start page again. Now you see that two connections are listed in the start page:

clip_image002[5]

An alternative would be to deploy the MLCFG-File to the config-Folders of all MemoryLifter installations or each config-Folder of each User (see the path below).

3. Troubleshooting

If you want to update the MLCFG file of some clients, you have to do this manually for each one.
    • Windows 2000, Windows XP:
      C:\Documents and Settings\<<UserName>>\Application Data\LearnLift\MemoryLifter2.3\Config\
    • Windows Vista, Windows 7:
      C:\Users\<<UserName>>\AppData\Roaming\LearnLift\MemoryLifter2.3\Config\

Tip 1: If you have a custom folder structure on your computer, or you can't find the directory, press [WIN] + [R], enter following command and press OK:

  • %AppData%

Afterwards Windows Explorer appears within a new window. The window represents your Application Data folder. Now you can add following folder structure to your AppData:

  • LearnLift\MemoryLifter2.3\Config

Tip 2: The same server can support have several connection types (with an MLCFG for each connection on the client). For example, a teacher could have a "NotSynchronized" and a "FullSyncronized" connection to the same server.

For any further questions or issues please contact us at support@memorylifter.com.

Last edited Mar 20, 2012 at 1:19 PM by CFI, version 9

Comments

No comments yet.