
  SyncML Conformace Test Suite(SCTS) DM V1.2


  INSTALLATION
  ------------

  * System Requirement
    Windows 95/98/2000/XP or compatible operating system. At least 64 mega bytes of memory 
    is required. 50 mega bytes or more disk space is required. 
  * Setup Steps
    Note: If SCTS 1.1 already exists on the system, there is no need to uninstall SCTS 1.1. 
    However, it is recommended that SCTS 1.2 be installed at a different location. 

    1. Execute the setup file SCTS3DevMan1.2.exe. 
    2. Click next and installation location dialog shows up. Enter the location correctly 
    and click next.  
    3. After installation completes the release information is displayed. 
    4. Click finish to exit installation. 

  DESCRIPTION
  -----------

  The SyncML Conformance Test Suite is a SyncML conformance test tool,
  fully featured, and Open Source toolkit implementing the SyncML device
  management(DM) protocol as well as full ETS test cases. 

  SyncML Conformace Test Suite V1.2 is based on open sourced sourceforge
  project SCTS which provides the implementastion of SyncML DM 1.1.2. 
  According to the change between SyncML DM 1.1.2 and 1.2, new features
  have been added and test cases have been updated. 

  OVERVIEW
  --------

  The SCTS 1.2 includes:

  SCTS3DevMan1.2.exe  -- The SCTS main program. 
  libeay32.dll, ssleay32.dll -- The SSL support library of OpenSSL. 
  client.pem, cacert.pem -- The certificates used by SSL. 
  uninstall.exe -- Uninstallation program. 
  ReadMe.txt -- Desctiption document. 

  SCTS 1.2 FEATURES
  -----------------

  * Update to support SyncML 1.2 protocol. 
      Changed SyncML namespace to SYNCML:SYNCML1.2, changed SyncHdr VerDTD to 1.2. 

  * Update to support SyncML DM 1.2 protocol. 
      Changed SyncHdr VerProto to DM/1.2. 

      Changed to support DM 1.2 stdobj protocol. Support the standard DevInfo, 
      DevDeatil objects. Support specifying any interior node as DMAcc object. 

      Support DM 1.2 TNDS protocol: client device can get, add and replace whole
      subtree on the management tree(Client side). 

      Support DM 1.2 protocol generic alert and execution correlator. 

      Support transport layer security protocol SSL/TLS(Only client side). 
      The client side certificate and private key are stored in file "client.pem". 
      The certificate authority signed certificate is stored in file "cacert.pem". 
      (For how to generate the certificate and private key please find more information at
       http://www.openssl.org/)

  * Test cases have been updated according to SyncML DM 1.2 ETS test specification. 
      Removed the test case for basic authentication verification. 
      Changed the test case for DMAcc stdobj verification. 
      Added cases for DM Exec command verification. 

  * Some minor changes: 
      Changed to support multi choice alert. 
      Some memory corruption bugs have been fixed. 

  USAGE NOTE
  ----------

  * When adding a new device, the "Account URI" text field of DeviceInformation should 
  be filled with an URI in management tree which will be treated as an interior node of 
  DMAcc and the account information will be stored in the subtree under it. For example, 
  "." if you want to add the accounts under root, or "./InnoPath" if you want to add all
  accounts under "./InnoPath". 

  * When discovering server device, the "Device Account URI" text field of DeviceInformation 
  should input the fully qualified URI of the node that contains authentication data in device 
  management tree. For example, "./InnoPath/DMAcc0"

  * Server device test case 1203 has been updated to check the DM account standard object 
  (e.g.DMAcc) more completely. It will check not only mandatory but also optional subnodes.  

  * Server device test case 2101, 2102 have been added to verify DM Exec command. 

  * When use SSL/TLS, just config client to use “https://” address type in address text field of 
  client authentication information, client will auto use SSL/TLS as transport protocol. 


DISCLAIMER
----------

InnoPath Software is submitting the SCTS DM 1.2 tool to OMA and the open source community in an AS IS condition under the Terms and Conditions of the Common Public License 1.0. InnoPath is strongly committed to the OMA standards process but shall not be responsible for addressing future change requests against the tool. InnoPath SHALL NOT be responsible for any incidental or consequential damages (including damages for loss of business, profits or the like) arising out of the use or inability to use the software even if InnoPath or its representatives have been advised of the possibility of such damages

