Prepare the hosting environment for the WIS

Optimizely {user["product-name"]} is a Microsoft .NET website application requiring the presence of a Windows Integration Service (WIS). This document represents both system requirements and recommendations from both a configuration and security standpoint. The {user["product-name"]} Windows Integration Service is installed on a Windows Server that communicates between the Client's ERP or other back-end systems and the Insite Commerce Website.

The Windows Integration Server can be either virtual or physical. A single non-hypervisor physical machine or a single virtual instance shall be referred to as a "Windows Host" for purposes of this document.

The WIS was designed and implemented such that they operate in a wide variety of environments and don't require specific domain knowledge for the ongoing maintenance. Because the client is responsible for hosting this application themselves or engage a third party to provide hosting services, the ongoing maintenance of the environment is ultimately the responsibility of the client. Though the routines described in this and other documents furnished by {user["product-name"]} serve as a baseline, they are no substitute for expertise on server administration and no guarantee that the service will be available and perform optimally.

Windows Integration Service

The Windows Integration Server must communicate with the Web Server over TCP port 80 and 443 for both HTTP and HTTPS traffic. The Windows Integration Server must also have network access to the necessary network locations of the client's ERP or other backend systems to which the Insite Commerce application will integrate.

The {user["product-name"]} application uses standard SMTP mail for sending confirmations, alerts, and so on, and must have access via TCP Port 25 to an SMTP server. This can be in the form of the SMTP service running on the Web or Database Servers, or use an external mail server. Both authenticated and non-authenticated SMTP is supported, in addition to SSL and non-SSL transmission. The configuration of the mail settings would use both {user["product-name"]} Application Settings (within the Insite Commerce Admin Console) and IIS Web Config file settings.

The following scenarios are illustrative and are typical system interactions. These could be changed depending on the hosting environment and client requirements. These are not intended to be exhaustive network protocol or communications flows but rather illustrative and it is acknowledged that such a simple explanation would be insulting to many networking professionals. The purpose is to illustrate "what" communication is occurring rather than "how" the communication is occurring.