The second version of the Qdabra DBXL Migration Tool (aka Document Deployer) has been released as a public Beta and can be downloaded here: http://www.infopathdev.com/files/folders/dbxldownload/entry24682.aspx

Here are new features in v2:

1.       Authentication: in v1, Document Deployer would fail if the currently logged in user failed to authenticate with DBXL. As of v2, Document Deployer will detect this situation and will prompt the user to enter the credentials (caching the username only).

This unblocks scenarios where a user connects via RAS/VPN when the machine is not joined to the domain.

2.       Built-in variables support. Now several system values are available anywhere in the system:

a)      DocumentDeployerPath – specifies the root of the Document Deployer installation

b)      ScenariosPath – specifies the folder that contains the out-of-the-box scenarios

c)       DBXLUrl – Defaults to the configuration setting, can be changed dynamically

d)      DocServiceTimeout – Defaults to .NET setting, can be changed dynamically

e)      EnumDBTimeout - Defaults to .NET setting, can be changed dynamically

Built-ins enable scenarios where you can switch DBXL location mid-flight and tweak the parameters such as timeout.

3.       Global variables and command-line variables: you can finally provide arbitrary arguments via command-line and you can use global variables to provide defaults. With command-line arguments, you can specify the DBXL location, the database name etc... this allows much greater reuse of existing scenarios – no more need to modify the scenario file to change 5 to 10!

4.       New Core methods:

a.       Trace (for debugging purposes)

b.      SetVariable – allows to set xpath variables dynamically in a declarative way

5.       Importing previous runs: Document Deployer v2 allows importing XML files from previous runs enabling abort-and-resume scenarios. Importing XML files also enables very generic input mechanisms.

6.       Minor tweaks:

a.       Actions can now fail without failing the entire run

b.      A few additional checks to prevent faulty scenarios from crashing later

c.       File version changed to 2.0

New Migration Tool Features

In addition to Document Deployer changes, the Migration Tool has been updated to use the new features. The Migration Tool features include:

1.       Ability to specify timeouts via command-line (including sql timeout)

2.       Ability to specify different source/target DBXL paths via command-line. This allows performing migration in one run. It is no longer needed to modify the configuration of the tool.

3.       Ability to resume the download of the documents.

4.       Ability to resume the upload of the documents.

5.       Most methods got another, richer, version (see the documentation for details)

User interface

The  Migration Tool has been augmented with a graphical user interface which makes running scenarios much easier.