Defining sites

Note: In a multi-tenant cloud environment, users can only modify the Description and Language fields. The rest of the fields can be modified and defined only by a Vendor developer.
  1. Open the Sites form.
  2. Click Filter-In-Place.
  3. Click New.
  4. Specify this information:
    Site
    Specify an ID for the site, up to 8 characters.
    Note:  In existing site records, you cannot change the site ID.
    Site Name
    Specify a descriptive title for the site. For example, if the site ID is ATL, specify the name Atlanta site.
    Description
    Optionally, provide information about the site.
  5. On the System Info tab, specify this information:
    Language
    Select the language code that represents the language for this site.
    System Type
    Select the type of system.

    The system type is either any version of this application or that of another system with which you are integrated. The system type is used by the replication infrastructure to provide XSL transformations on data being replicated between sites.

    Time Zone
    Select the appropriate time zone for this site. The time zone you specify is independent of the time zone for the server.

    Each site can have a different time zone. If the DateTime in Client Time Zone process default is not set, most forms and reports show the time zone of the site, and audit columns such as CreateDate and RecordDate also use the site’s time zone.

    Intranet Name
    Select the name of the intranet. This field is only enabled when no tables are shared in the site's intranet, and if the site is not a master site.
    Intranet Licensing
    Select this check box to enable intranet licensing. This field is enabled only if the current site is associated with an intranet that has a designated master site.
    Database Name
    Specify the application database name used for the site. If the server name or database name contains a dash, enclose the name in brackets. For example, [SL900-DB]

    The application database name specified here is used by system processes such as intranet shared users, and by transactional replication to build appropriate links and relationships to other sites in the same database, or in other databases. You can change the name here. For example, if you have backed up and restored the database with a new name, but be aware that you must also manually change the server and database name in the Configuration Manager.

    Forms Database Name
    Specify the name of the forms database that contains the strings tables this site uses; for example, OH_forms. The value you specify here must match the Runtime Forms Database Name that is specified in the Configuration Manager utility for the primary configuration used to log into this site.

    If the forms database is on a different server than the application database listed in the Database Name field, then indicate the forms database server name as part of this value; for example, OHIO_server.OH_forms.

    Note: The database name must be enclosed in square brackets if it contains periods or begins with a number. For example, if your database is named 10.02.03, then you should specify [10.02.03].
    Message Bus Logical ID
    Specify the string that is used as the logical ID or the identifier for the originating site.

    This value is the identifier by which the site is recognized in all transactions involving business object documents (BODs).

    Tenant ID
    Specify the tenant ID that is used in all BODs to identify the sender of the document. The ID is limited to a maximum of 22 characters.
    Report Output Folder
    Specify a global file system or UNC path, where all report outputs created for this site are directed.
    Configuration Name
    The current site record is mapped to this configuration name. This default configuration name is used as the target configuration in building IDORequest XMLs during replication and AES event handling.

    If your application is running in a multi-tenant cloud environment, specify a default configuration name that is unique across all tenants, which is provided by the Infor cloud team.

    Leave this field blank to use the site name as the default configuration. In this case, you must create a configuration that matches the site name.

    From Email
    Specify a valid email address to be displayed in the From field on each email notification.
    Note: If the AES From Email use Intranet or Site process default is enabled, this value overrides what is defined in the intranet level.
  6. On the Site User Map tab, specify this information:
    From Site
    If the local site will send data to the target site through non-transactional replication, select the local site. Otherwise, leave both this field and the User Name field blank.
    User Name
    Select the user ID for the From Site.

    If non-transactional or XML-based replication will be used between the two sites, the user name and the password for that user must exist and must be the same on both the source and target sites.

    The local site administrator should assign this user the appropriate permissions to allow replication data to complete the transaction. This protects the local site from another site inappropriately adding or modifying data on the local site without permission.

    Although the password is not listed on this form, it is part of the packet of data sent to the remote site. If all your sites are administered by the same person, you can set this value to a user with superuser permissions that exists on all sites. If sites are administered by multiple persons and you want to limit the data each administrator can send into other sites, set this value to a user who exists on all sites and is licensed for the appropriate Automation module.

  7. On the Link Info tab, specify this information:
    To Site
    Select the site to which the data is to be replicated.

    The list shows all sites defined in this form, including sites not in the current site's intranet.

    Disable Replication
    Select this check box to disable replication without having to change replication rules on the Replication Rules form.
    Linked Server Name
    Specify the name of the remote server where the application database for the To Site resides. The linked server name is usually the actual name of the database server for the To Site.

    If you perform transactional replication between the To Site and the current site, the linked server name must be provided.

    If you are performing transactional replication between sites on different database server machines, the server name is verified against the list of linked servers in the current site's SQL server master database. If you get a verification error, you must manually create a linked server definition in the SQL server master database of both the current site and the To Site. You can create a linked server definition in SQL.

    If a transactional replication rule exists that matches the Site and To Site fields shown in the current record, this linked server name cannot be deleted.

  8. Click Save.