Set Up the Web Server

For load balanced configurations with multiple web hosts

The application files should be placed in a shared directory that is accessible by all of the web servers. An example of this configuration would be to create a Windows Directory Share or use a shared directory on a NAS. The IIS application pool's identity (whether a domain service account, or ApplicationPoolIdentity) must have full permissions over this directory.

Setting permissions is dependent on the myEvolv application pool's identity:

• Network share level permissions
  • If using AppPoolIdentity - read/write access must be given to the web host machine names
  • If using a domain service account - read/write access must be given to that account
• NTFS security permissions
  • If using AppPoolIdentity - read/execute and write must be given to the web host machine names
  • Domain Service Account - read/execute and write must be given to the domain service account

Confirm Windows Server Version

myEvolv is approved to run in Microsoft Windows Server 2012 R2. Your IIS version should be version 8.5 or above.

1. To check your Server and IIS versions, in the Run dialog, type winver.

Note: To open the Run dialog, (press the Windows logo key + R).

System result: The About Windows dialog displays.

Confirm IIS Settings Version

myEvolv requires IIS version 8.5 or higher.

1. Open IIS Manager.

Note: To open the IIS Manager, open the Run dialog (press the Windows logo key + R) and type inetmgr.

2. In the IIS Manager, in the toolbar, click Help > About Internet Information Services.

System Result: The About dialog displays the IIS information:

Confirm ASP is Allowed

1. In the IIS Manager, click ISAPI and CGI Restrictions.

Create the Application Pool

1. From the IIS Manager, in the Connections pane, expand the myEvolv server.
2. Right-click Application Pool and select Add Application Pool.

3. In the Add Application Pool dialog, complete the information.

Confirm Advanced Settings of the Application Pool

1. From the IIS Manager, in the Connection pane, expand the myEvolv server and select Application Pools. 
2. In the Application Pools list, right-click the appropriate application pool and select Advanced Settings.

3. In the Advanced Settings dialog, ensure the settings are configured per the example below.

Note: The Enable 32-Bit applications setting is important for Wiley Imports and other automated functions employing Office libraries.

In this example the myEvolv application is configured to run under the 'myEvolvService' service account. 

Configure Recycling

This recycles the IIS application pool and launches a new worker process on a schedule. In this example, the application pool is recycled at 7:00 am and 12:00 am.  
Note: Recycling initiates a new IIS worker process for new requests. It will not disconnect active sessions.

1. From the IIS Manager, in the Connection pane, expand the server and select Application Pools.
2. From the Application Pools list, right-click an application pool and select Recycling.

3. In the Recycling Conditions dialog, select the specific times option, enter times in the field, and click Next. 

4. Click Finish.

Configure Rewrite at Site Level

1. Create a new folder to contain the redirect (e.g. E:\websites\redirect). Note: E:\websites is the directory containing your myEvolv applications
2. Create a web.config file in the redirect folder with the contents below. The file must be named web.config.

Note: If you use Notepad to create the file, you may end up with a file named web.config.txt. The simplest method to create this file without changing your view settings or editing the extension afterward is to navigate to E:\websites\redirect, then type notepad web.config in the Windows Explorer address bar. 

3. The system prompts you to create the file. Click Yes.

4. In the new web.config file, place the following text and save the file:

<?xml version="1.0" encoding="UTF-8"?>
<configuration>
    <system.webServer>
        <directoryBrowse enabled="false" />
        <rewrite>
            <rewriteMaps>
                <rewriteMap name="StaticRewriteDefault">
                    <add key="/" value="/classic" />
                </rewriteMap>
            </rewriteMaps>
<rules>
                <rule name="Rewrite Rule">
                    <match url=".*" />
                    <conditions>
                        <add input="{StaticRewriteDefault:{REQUEST_URI}}" pattern="(.+)" />
                    </conditions>
                    <action type="Rewrite" url="{C:1}" appendQueryString="false" />
                </rule>
</rules>
        </rewrite>
    </system.webServer>
</configuration>

This example will redirect all traffic from https://localhost to https://localhost/classic. Replace "classic" with the name of your EvolvCS application if necessary.

5. Create an IIS web application /classic pointing to the application folder (for example, E:\Websites\evolv_cs).
6. Point the Default Website to the new redirect path (E:\Websites\Redirect).

Add the myEvolv Application to IIS

This will add the myEvolv applications to the Default Web Site in IIS.  A default website responds on HTTP port 80; default HTTPS site is port 443.  Alternate ports are not covered in this guide.

The default settings allow IIS to present the myEvolv applications as sub-sites within the main site.  For example, for a website located at https://healthcare.com, the myEvolv applications would appear at https://healthcare.com/evolv_cs, https://healthcare.com/evolv_xb and so on.

Note: If the application is installed at the default website instead of beneath it, your site will exhibit inheritance issues. The Microsoft URL Rewrite Module for IIS remedies this issue. The URL Rewrite module is not covered in this installation guide.

1. In the IIS Manager, in the Connections pane, right-click default website and click Add Application.

2. Complete the Add Application form. Select the EvolvCS Application pool.
3. Assign the intended Alias for this site in the Alias field.  This is the <site_name> where a site is accessed, for example, https://healthcare.com/<site_name.

Note: You can name your sites differently for mnemonic or practical purposes.  Some organizations prefer to name the application according to the containing folder (evolv_cs, evolv_xb); others prefer the application’s friendly name (/classic or /xb).

4. Repeat the above step for evolv_xb.  Select the EvolvCS Application pool.

5. Repeat the above step for evolv_mobile. Select the EvolvCS application pool.  

Update the ASP Limits

Change the ASP limits in the server properties.

1. In the IIS Manager, in the Connections pane, select the server.
2. In the Server Home page, under IIS, select ASP.

3. Change the ASP limits in the server properties as follows:

• Maximum Requesting Entity Body Limit to: 20000000
• Response Buffering Limit to: 41943040 
• Script Time-Out: 00:10:00

Run Folder Permissions

On a new installation of myEvolv, you must assign 'modify' permissions in the myEvolv folders for specific service accounts:

•    IUSR
•    IIS_IUSRS
•    <application_pool_identity> (Network Service)
 
The <application_pool_identity> is the identity under which your EvolvCS Application pool runs. 

The Windows batch file named folder_permissions.bat inside the evolv_cs application folder must be run from an administrative command prompt.

This instructional resumes with EVSETUP.exe after the myEvolv CS database has been installed and configured.

Note: If you need assistance from a Netsmart System Engineer please contact your client alignment executive (CAE) for technical consulting services.