Using the Deployment Wizard

The SQL Anywhere Deployment Wizard is the preferred tool for creating 32-bit deployments of SQL Anywhere for Windows. The Deployment Wizard can create installer files that include some or all of the following components:

  • Client interfaces such as ODBC
  • SQL Anywhere server, including remote data access, database tools, and encryption
  • UltraLite relational database
  • MobiLink server, client, Monitor, and encryption
  • QAnywhere messaging
  • Administration tools such as Interactive SQL and Sybase Central

The Deployment Wizard does not include support for creating deployments of the 64-bit software components.

You can use the Deployment Wizard to create a Microsoft Windows Installer Package file or a Microsoft Windows Installer Merge Module file:

  • Microsoft Windows Installer Package file   A storage file containing the instructions and data required to install an application. An Installer Package file has the extension .msi.

  • Microsoft Windows Installer Merge Module file   A simplified type of Microsoft Installer Package file that includes all files, resources, registry entries, and setup logic to install a shared component. A merge module has the extension .msm.

    A merge module cannot be installed alone because it lacks some vital database tables that are present in an installer package file. Merge modules also contain additional tables that are unique to themselves. To install the information delivered by a merge module with an application, the module must first be merged into the application's Installer Package (.msi) file. A merge module consists of the following parts:

    • A merge module database containing the installation properties and setup logic being delivered by the merge module.
    • A merge module Summary Information Stream describing the module.
    • A MergeModule.CAB cabinet file stored as a stream inside the merge module. This cabinet contains all the files required by the components delivered by the merge module. Every file delivered by the merge module must be stored inside of a cabinet file that is embedded as a stream in the merge module's structured storage. In a standard merge module, the name of this cabinet is always: MergeModule.CAB.

Note

Redistribution of files is subject to your license agreement. You must acknowledge that you are properly licensed to redistribute SQL Anywhere files. Check your license agreement before proceeding.

To create a deployment file

  1. Start the Deployment Wizard:

    • From the Start menu, choose Programs » SQL Anywhere 11 » Deploy SQL Anywhere For Windows.

      or

    • From the Deployment subdirectory of your SQL Anywhere installation, run DeploymentWizard.exe.
  2. Follow the instructions in the wizard.

To install a deployment file

  • Use the Microsoft Windows Installer to install the deployment file. Here is a sample command:

    msiexec /package sqlany11.msi 
    

    A silent install can be performed using a command like the following:

    msiexec /qn /package sqlany11.msi SQLANYDIR=c:\sa11
    
    • /package <package-name>   This parameter tells the Microsoft Windows Installer to install the specified package (in this case, sqlany11.msi).

    • /qn   This parameter tells the Microsoft Windows Installer to operate in the background with no user interaction.

    • SQLANYDIR   The value of this parameter is the path to where the software is to be installed.

To uninstall a deployment

  • It is also possible to perform a silent uninstall. The following is an example of a command line that would do this.

    msiexec /uninstall sqlany11.msi 
    

    Alternately, a product code can be specified.

    msiexec.exe /qn /uninstall {19972A31-72EF-126F-31C7-5CF249B8593F}
    • /qn   This parameter tells the Microsoft Windows Installer to operate in the background with no user interaction.

    • /uninstall <package-name> | <product-code>    This parameter tells the Microsoft Windows Installer to uninstall the product associated with the specified MSI file or product code.

For more tips on how to do silent installs, see Using a silent install for deployment.