Depending on the version, the TOPICA framework may or may not contain configurations after initial installation:

• Release 4.25 and newer:

  • These releases contain a number of demo/test configurations. That is, the folder Configuration will exist, and it will contain a number of subfolders (one subfolder = one configuration).

  • To run these configurations, all you need to do is create a database for each of them. Refer to Creating a Database.

  • Alternatively, these configurations may be deleted. They will not be needed in production scenarios, for example.

• Release 4.24 and earlier.

  • In these releases, the framework does not come with any configurations. The folder Configuration will not exist after initial installation.

  • If you have a configuration, you may create the Configuration folder manually (using Windows Explorer) and place the configuration in a subfolder.

  • Alternatively, you may start the framework - it will automatically create the Configuration folder. Then you may create subfolder for your configuration.

Remember that a configuration is actually just a folder below the Configuration folder. So creating a new configuration first of all requires creating such a new sub-folder.

How this may be done depends on the TOPICA framework version:

• Release 4.25 and newer:

  • Use the Administration Module to create a new configuration from the web user interface.

    Caution
    The Windows user, that is set up in the Application Pool in IIS, must have full control over the Configuration folder. Refer to the Windows documentation on how to manage NTFS permissions.

    In this web user interface, it is possible to create a new, empty configuration, or copy an existing configuration (e.g. one of the supplied demo configurations).

• Release 4.24 and earlier:

  • Create a subfolder by navigating to the web home folder in Windows Explorer and "manually" create the configuration subfolder in Windows Explorer.

    Obviously it is both possible to create a new, empty configuration, or copy an existing configuration.

    Caution
    Copying an existing configuration might require some "cleaning up" afterwards. For example, folders containing temporary files or log files should NOT exist in the new configuration! Also, any database references (or other environment specific settings) in the Server.config file must be edited.

    The folder structure must adhere to the standard configuration folder structure. For example, when a web home (framework instance) contains 2 configurations OldConfig and NewConfig, the folder structure must be:

    Copy

    <web home>
        Configuration
            OldConfig
            NewConfig

    Each configuration folder MUST contain an Application.config file.

Next logical step after creating a configuration would be to create a database and connect the configuration to the database.