Using the same objects data for multiple sites

Consider this information:

  • By default, all SyteLine databases are defined as "all-in-one" databases that have at least one site, one set of forms data, and one set of objects data.
  • In most cases, we recommend that you use the standard, all-in-one database, and just use group-level customizations and permissions if you want to assign particular objects data to certain users. However, you can optionally set up a separate all-in-one database that you use only for personalized objects data.
  • For example, you might want to share an instance of the objects database across sites in different databases if any IDO patches, add-ons, or customizations are shared. In that case, you could just create the customizations, add-ons, or patches in one database.
  • IDO editor forms in Infor SyteLine are used to create and maintain the IDO metadata, which is then stored as objects data and used by the IDOs at run time.

    In versions of SyteLine previous to version 8.00, IDO creation and maintenance was done through the ObjectStudio application, and the IDOs were stored as DLLs.

    More information about the use of the IDO editor forms is available in the online help. Use of these forms is tracked with a separate "development" license.

  • You might not want to share an instance of the objects database across sites in different databases if the databases are in different data centers, and you do not want to pay the performance cost of accessing the objects database across a slow internet at run time.
  • If you have multiple sites in the same database, all of the sites in that database must use the same set of objects data.
  • By default, the database that stores object data for a configuration is the same as the application database. If you want all of the sites in your database to point to a separate database for objects, specify it in the Configuration Manager utility, Objects Metadata tab.
  • If a separate database to use for objects data is specified for a configuration in the Configuration Manager, the application database contains views into the objects database, so the runtime environment does not directly access the objects database.