Creating additional client configurations

You must add a client configuration for each site database that you want to access through this application/web server.

Caution: 
If you have multiple application servers, only one of them should be designated as the configuration server, and the Configuration Manager utility should be run only on that configuration server. The resulting MongooseConfigs.xml file should then be copied to the other servers so they have access to the defined configurations. See the Infor SyteLine Multi-Site Planning Guide for information about the configuration server.

For each site, create one configuration name that exactly matches the site ID, including case, and that uses the site’s application database. This is required unless you specify a different default Configuration Name on the Sites or Sites/Entities form. (You can create additional configurations for the site, with different names.)

  1. On the application server, find and open the Configuration Manager, under Apps (Run as Administrator).

    The Configuration Manager displays the initial configuration that was created during installation and setup of the application/web server.



  2. Click New to create a new configuration.
  3. Specify the new configuration name and click OK
  4. In the Runtime (Client) tab, specify the application and forms database connection information for the new configuration.
    Note: For an all-in-one database, the specifications for the application, forms, and objects databases will be the same.


    Use the information from your SiteEntity and Configurations planning spreadsheets to help you fill in access information (SQL server name, login, password, and database name) for the application, forms, and objects databases.

  5. In the Objects Metadata tab, click Set Objects DB Specification and then specify the Objects database name.

    You can associate only one Objects database with an application database.

    By default, if you have multiple sites in one application database, all configurations for sites in that database should point to the same Objects database.



  6. Click OK. A confirmation message displays; click OK again.
  7. If you use FormControl or a source control system, set up information on those tabs as needed.
  8. Click the OK button at the bottom of the Edit Configuration screen to save the configuration and return to the Configurations tab, where the new configuration displays.
  9. Repeat steps 2-8 until all configurations are defined.
Note: If a new configuration definition will be very similar to an existing one, you might want to use Copy instead of New. This creates a copy with a new configuration name and you then select Edit to modify the definition.