We’ve developed some resources to help you work effectively from home during COVID-19 Click here to learn more

Prototype SQL Express

In this article
    The computer used to generate prototype must have full SQL server or SQL Express installed..

     

    Configuration

    Paths and configuration variables

    The prototype is generated on a database server, and the actual database file must reside on the same server. If the archivepath file store and the database server run on different computers, the prototype will have to be created on the database server and not the archivepath file server – this is how SQL Server works.

    Two new variables have been added to superoffice.ini in the [SuperOffice] section for this purpose:

    ProtoServerPath=c:\SOProto

    ProtoClientPath=\\NAME_OF_SAME_COMPUTER_AS_PROTOSERVERPATH\SOProto

    These two items has to be inserted into the Superoffice.INI manually, and they are read at start-up, so you need to restart SOAdmin if you just added it and it's still complaining that the ProtoServerPath is missing.
    When prototype is finished, the database files will be automatically zipped and copied to the ARCHIVEPATH, like \\SERVER\SO_Arc\Template\travel

    Note: From 7.0 SR1 these are ONLY necessary for clients who are going to generate prototypes. The normal travel user does not need any of these paths to do a local update.

    ProtoServerPath

    Is the full path (without filename) to the place you want the prototypes to be created, as viewed from the server. So this should always be a local path, like c:\so_proto or something similar. This path is going to be used when SOAdmin or the travel gateway service tells the SQL Server to create a new database; the statement will be processed by the database server and must therefore refer to a file path local to the server machine.

    ProtoClientPath

    Is the full path (without filename) to the central SO_arc\template\travel folder where the prototype will be zipped and copied too so the client finds it late. So this should always be a network path (UNC path), or a mapped drive if you are sure all clients have it mapped the same way.

    From SR1 these are only required on clients who are also going to generate prototypes.

    AREA data source

    The AREA odbc data source must be configured on the machine(s) used for generating prototypes. It need not be configured on normal Travel clients. This is just as usual.

    When creating the AREA data source, you only need to go through the first page of the Wizard.

    On the first page, fill in the name AREA and choose the correct SQL Server.

     

    Also from 7.0 SR1: We no longer create separate AreaX odbc datasources during prototype generation. This means you are no longer required to be local administrator to generate a prototype.