About intranets
Use the Intranets form in the application to define information about your logical intranets. Then use the Sites or Sites/Entities form to assign your sites to an intranet.
(on-premises only) For example, if you have two sites in one datacenter and two sites on a different datacenter, define two intranets, one for each datacenter, and put the sites from each datacenter on those intranets.
External intranet
Create an external intranet if you need to set up replication between sites on one of your SyteLine intranets and an external system or an application.
(on-premises only) For example, you might use an external intranet to connect to the Enterprise Financials application.
For such external systems or applications, the only attributes that matter will be the intranet name (so you can define "sites" on the Sites or Sites/Entities form that represent instances of external systems), the transport method (see below), and the URL. When you have defined sites on such an external intranet, you can then create replication rules. See Frequency of data replication. The replication system will dispatch XML documents to the URL you have specified on the intranet.
An SyteLine site can communicate with an external site when it is on a different intranet, as shown in this example:
MyCORP (Internal) Intranet: SiteA SiteB (master site) SiteC
(on-premises only) SunSystems Intranet (Enterprise Financials): SUNBU1 site
InforBUS Intranet (BOD-enabled applications): InforBUS site
Each of these external sites must be on its own intranet because each application uses a different URL address.
SyteLine SiteB could perform transactional replication with all the internal sites, and could perform non-transactional replication to all the external sites.
Transport method
Most sites on external intranets use HTTP transport protocol to communicate with SyteLine sites. However, Infor BOD-enabled applications use the ESB transport protocol.