Parallels H-Sphere Documentation System Administrator Guide

 

Creating User Migration XMLs Outside H-Sphere

(updated for version 2.5)
 
 

Related Docs:   Migrating Users Into H-Sphere Migrating Users Into H-Sphere (before 2.5) Creating User Migration XMLs in H-Sphere Creating User Migration XMLs in H-Sphere (before 2.5)

Last modified: 27 Dec 2007

 

WARNING: This documentation covers Parallels H-Sphere versions up to 3.1. For the latest up-to-date Parallels H-Sphere documentation, please proceed to the official Parallels site.

This document explains how to format user data for migration from third party hosting systems into H-Sphere. Use it to:
- migrate direct end users, resellers, and resellers' end users;
- migrate only direct end users if you don't have resellers.

 

Files

Create the following files:

For H-Sphere before 2.5 For H-Sphere 2.5 and up
resellers.dtd - data type definitions for resellers
example | explanation
resellers.dtd - data type definitions for resellers
example | explanation
users.dtd - data type definitions for end users
example | explanation
users.dtd - data type definitions for end users
example | explanation
migrate_resellers.xml
XML file containing both reseller and end user data
example
migrate_resellers.xml
XML file containing reseller data solely
example | explanation
migrate_users.xml
XML file containing user data only
example | explanation

You may have data for hundreds and thousands of users in the xml file.

Alternatively, You may define DTD definitions directly within the XML file:

    <?xml version="1.0" encoding="utf-8"?>
    <!DOCTYPE users [
        // DTD rules as in users.dtd
        . . .
    ]>
    <users>
    . . .

We recommend defining DTD externally, using our latest DTD:

<!DOCTYPE users SYSTEM "users.dtd">
<!DOCTYPE resellers SYSTEM "resellers.dtd">
DTD files help ensure that all XMLs are formatted the right way. But please note that XML files will be created no matter DTD file exists or not.

Warning: If you make a mistake in DTD definitions, migration may fail.

 

XML Validation

Once you have created the XML, please do the following:

  1. Validate the user data xml files with any xml validation software.
  2. Make sure the xml file does not contain user with the login "admin".
  3. Make sure that mail sections of each user don't contain mail loops.
  4. Ensure that the billing period starting date has the MM/DD/YY format.
  5. Make sure that in the user tag the value of the login attribute is unique and doesn't begin with a number (this value will be used as the H-Sphere control panel login name).

Now you are ready to create the accounts.


Related Docs:   Migrating Users Into H-Sphere Migrating Users Into H-Sphere (before 2.5) Creating User Migration XMLs in H-Sphere Creating User Migration XMLs in H-Sphere (before 2.5)



© Copyright 2017. Parallels Holdings. All rights reserved.