Adding a site to an existing database

To initiate a request to add a site (or entity-type site) to an existing database, use the Site Management utility form. The request includes information about the site as well as a contact email. If the request is successful, you are notified by email, and the site is added to the database associated with the configuration where you accessed the Site Management form. If the request fails, an email that describes the errors is sent. You can correct the errors and try again to add the site.
Note: Running this utility during regular business hours could cause decreased system performance or deadlocks with other activities. We recommend that you run this utility as a scheduled background task during times of reduced business activity, so that system performance is not affected.

Create one site at a time, and wait for the confirmation email before you create another site.

  1. Review the information in the Infor SyteLine Multi-Site Planning Guide (cloud or on-premises edition) to determine what sites you need to add.
    If you decide to add more sites to an existing database that already includes at least one site, use these steps.

    Alternatively, users in on-premises environments can create a new, different database to hold another site, using the steps in the Infor SyteLine Installation Guide.

  2. Log into an existing configuration for SyteLine in the database where you want to add a site.
  3. Open the Site Management form and specify this information for a site that you want to add:
    Site ID
    Specify the site ID, which is a shorter version of the Site Name. The site ID can be 8 characters, maximum.

    This ID will be used as the default configuration name.

    Site Name
    Specify the full site name. You might want to include the site type as part of the name, for example DALS Site or CORP Entity.
    Site Description
    Optionally, provide a short description of the site environment. For example, you could indicate whether it is a production or test environment.
    Site Type
    In most cases, accept the default value of SiteEntity if you are setting up a financial entity to consolidate data from the sites.
    Site Time Zone
    Select the time zone for the site. The time zone you specify is independent of the time zone for the server. Each site can have a different time zone. 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.

    During replication, as date and time values are exchanged between sites, the values are adjusted by the difference between time zones. For example, an order entered at 8:00 AM in Los Angeles would show up as having been entered at 11:00 AM when the data is copied to New York. This adjustment also occurs during APS planning.

    Site Group
    Specify a group name for the environment that is being created. The group name should be descriptive of the sites in the group. For example, you might have a group name of NoAm for North America if all the sites in that group are in North America.

    You can select from a list of existing site groups or add a new one.

    Notification Email Address
    Specify a contact email. This defaults to your Primary Email Address from the Users form, if it exists. However, you can specify any valid email address.

    The Add Site process sends a notification email to this address if the request is successful. If the request to add a site fails, an email that describes the errors is sent to this address. You can correct the errors and try again to add the site.

  4. Click Add Site.
    A task is submitted to process the request using the information from the form.

    An email is sent to the Notification Email Address defined above and to your SyteLine Inbox form, indicating whether the request was successful. If the request failed, error information is provided. You can correct the errors and re-enter the information on the Site Management form.

    For cloud environments, if the request is successful, these areas are preconfigured for the new site through automation:

    • One configuration was set up for the site.
    • The site was added to the CORP intranet.
    • Replication was set up between the site and ION and Infor Ming.le.
    • A Users record was set up on the new site with the Primary Email Type that is contained in the Notification Email Address, if it does not already exist.
    • A system administrator account was set up for the new site.
    • The tax interface and APS parameters were set up for the new site.
    • Cached information was discarded for all relevant existing configurations, so the new configuration can be recognized.
    • A replication rule was created for the new site to replicate to the Data Lake.
    • An IMS connection point was created for the site in ION Desk. This connection point is used with the Data Lake.

    These updates will be available soon after job submission.

  5. For on-premise environments, go to the Sites/Entities form and specify the Intranet for each of the new sites.
  6. For cloud environments, if SyteLine is already integrated with the Data Lake, you must perform these additional steps to set up communication between the new site and the Data Lake.
    For more information about these steps, see the Infor CloudSuite Industrial Configuration Guide.
    1. Enable the DATALAKE replication rule for the site, and regenerate replication triggers.
      See Enabling or disabling replication to the Data Lake.
    2. In ION Desk, refresh the IMS connection point for the site and then click Save. This discovers the documents (tables) that are being sent from the site to the Data Lake.
    3. In ION Desk, add the IMS connection point for the site to the erp_datalake flow.
    4. In ION Desk, deactivate and then reactivate the erp_datalake flow.
  7. Also for cloud environments only, during the initial site add process, an email notification is also sent to Cloud Ops. This email contains all the necessary information for Cloud Ops to submit an update through CSP to create an ION IMS connection point. The name of the new connection point in ION Desk is csi_ appended with the value from the Site field. Cloud Ops can take several business days to create the new connection point. If the connection point does not show up in your ION Desk application within a reasonable timeframe, open an Infor support ticket.
  8. For on-premise only: If SyteLine is integrated with Infor OS, complete steps 7-10 to set up the new site's connection point and add it to document flows.
  9. When the ION IMS connection point for the new site is available in ION Desk, edit the connection point to add the required documents. To do this, select Connect > Connection Points and select the new csi_sitename connection point.
    The documents to add to the connection point depend on the applications that will be integrated with the site. See BODs used in integrations with this application for the list of available inbound and outbound documents.

    At a minimum, you must add these documents to the new connection point so that users and roles can be shared across applications:

    Document Receive in Application Send from Application
    Process.SecurityUserMaster X
    Sync.SecurityRoleMaster X
    Sync.SecurityUserMaster X

    When done, save your changes.

  10. In ION Desk, select Connect > Data Flows, choose the erp_mingle data flow, and add the new connection point to the ERP_1 box.
  11. In ION Desk, add or update other data flows to include the new connection point, as needed based on the integrations used with this site.
    See the appropriate integration guides for more information.
  12. In ION Desk, reactivate the data flows that you changed.
  13. Follow the steps in the Infor SyteLine Multi-Site Implementation Guide (cloud or on-premises version) to complete setup of the new site.
    Note: For cloud environments, when you further define the sites, be aware that you should never select the Intranet Licensing option for a site in a cloud environment.
Related topics