Web Server

• MS Windows Server 2012 through to 2019
• Microsoft .NET Framework 4.0 through to 4.7 
  • Microsoft .NET Framework 4.5.2 is required for CMO Version 14.07 and above
  • Microsoft .NET Framework 4.7 is required for CMO Version 16 and above
• Roles activated for IIS and Application Server. See details on the Powershell Script to Enable IIS Feature to automate this
• SMTP server for outgoing notifications
• Microsoft Office 64bit Runtime
  • See the Official Microsoft Site to download
• POP3 or IMPA Server access (To allow users the ability to close out events/actions via their email notifications. APOP3 server will need to be set up, so that CMO Compliance can read email responses from users via a mailbox.
  • Note that CMO Compliance does not currently support MAPI Mail
• A domain name (A-Record) to point to the new CMO Compliance application - this can be an internal domain only and does not need to point to an external IP.
• Optional Microsoft Office (preferably 2010 - CMO Compliance allows documents to be presented to end-users in a read-only format, via the user of Google Docs. If Google Docs cannot access your server, then you have the option of purchasing our alternative document converter which uses a PDF conversion tool to show your documents in PDF format. This tool requires MS Office to be installed so that documents may be converted from standard MS Office formats by the tool).

Database Server

• Microsoft SQL Server 2012 or 2016, Standard or Enterprise Editions
• Microsoft SQL Server Reporting Services 2008 R2 SP2, 2012, 2014 or 2016, Standard or Enterprise Editions. (To allow use of our Custom Reporting module - Note that this is an additional module that must be purchased).
• Reporting Services can be installed on the same machines as the Database Engine, however, it's required that it is accessible from the Web (the same as the Web Server). Alternatively, you can install Reporting Services on a Web-facing server - as long as it can access the SQL Server Database engine.
• SQL traffic needs to be open between Database Server and Application Server. 

Application Files

All application files will be provided by Mitratech in a single archived folder. For example, CCLive1404_50341_PreCompiled.zip.

1. Extract this archive then copy the contents to a folder on your Application (IIS) Server which will store the website files (for example: E:\CC\Site\[ExtractFilesHere].
2. Once you've copied and extracted this folder to your server, right click and select Properties. Click on the Security tab then click Edit.
3. In the 'Site' folder (e.g. E:\CC\Site\), grant Read Only rights to the IUSR and NETWORK SERVICE users on the 'Site' Folder
   
   
   
   To edit these assignments, click the Edit button, then click Add and search for names. 
    
4. Add Read/Write permissions on E:\CC\Site\Upload
   
   
   
   The same Read / Write permission need to be set within the host file system on the below directories:
   %windows%\Temp'
   %windows%\Microsoft .NET\fRAMEOWRK64\V4.0.30319\Temporary ASP.NET files'
   
   If you are using a legacy 32bit version of CMO Compliance, you should use the 32bit folder location. If you are unsure, then use the above location - 32bit temporary folder-  %windows%\Microsoft .NET\fRAMEOWRK64\V4.0.30319\Temporary ASP.NET files'

Database Files

The Database file will be provided as a MS SQL Server backup file (.bak). This file can be restored to the Database server by following the steps below. Note, the instructions below are for SQL Server 2008 R2. The SQL 2012 and 2014 has a slightly different interface. 

1. Open MS SQL Server Management Studio and connect to the DB Server.
2. Right click on the Databases folder in the object explorer panel and select Restore Database.
3. Locate the To Database field in the Destinations for Restore section and enter the preferred name of your new database that you are restoring (e.g. CMOCOMPLIANCE).
4. In the Source for Restore section, select the From Device option and select the (.bak) file that you were provided with.
   
   When you have selected the file to restore, ensure the Restore option is selected in the table next to the database backup, then click Ok (detailed in the image below).
   

Now you must create a new user that CMO Compliance can use to connect to the database. Follow the steps below:

1. Expand the Security folder in Management Studio's Object's explorer panel.
2. Right click on the Logins sub-folder and select New Login.
3. Enter a login name for the user (e.g. cmologin).
4. Check/select the SQL Server authentication option and enter a password for the user. Ensure the option for Enforce password expiration and User must change password at next login are checked.
5. Select your newly restored CMOCOMPLIANCE database as the 'Default Database' that the user has access to, then click on the User Mapping page in the left panel.
6. Click the Map checkbox in the new CMO COMPLIANCE database, then click the db_owner role to assign the user to the database with that role. 
7. Click Ok to save the user.
8. Expand the Databases folder in the 'Object Explorer' panel of Management Studio, then expand the newly restored CMOCOMPLIANCE Database.
9. Expand the Security folder under the CMOCOMPLIANCE database, then expand the Users sub-folder.
10. Double click on the new user that you created and ensure that the db_owner role is selected in the Database role Membership table.

The database has now been set up and a user with db access has been created.

Creating the Website

As CMO Compliance is access via website, you will ne to create a website via IIS - Follow the steps below:

1. Open IIS and expand the web server instance in the Connections panel on the left.
2. Right click on Sites and select Add Web Site.
3. Enter the site name then browse for the physical location of the site (e.g. E:\CC\Site). Point the site to the folder which stores all of the physical site files.
   • if you are using folder naming provided by CMO, then you will need to point to the folder named Site, which is part of the Site files archive.'
4. In the Binding section, add any domains/host names that are reserved for the application in the Host name field. 
   • If users are accessing the site via https: Select this from the Type drop-down, then select the relevant SSL certificate to be used. It is recommended to have three bindings: you.hostname.com:443, your.hostname.com:80, and 127.0.0.1.80xx.
     
      
5. Click Close. 

Configuring the Website

 Some of the values will need to be modified in the configuration file once the website is set up. This is to ensure that it can connect to the database correctly.

To access the configuration file, click on the website in the left hand Connections panel, then double-click on the Application Settings icon. 

In the application settings, there are a number of fields that you will need to modify to ensure that your CMO application functions correctly. 

• Double-click on a setting to change it's value - click OK when finished editing.
• This can also be edited through the GUI in IIS Manager or through the web.config file (if you prefer).
• The main settings that you will be required to set up initially are detailed below:

Setting up the Notification Center

• Email notification in CMO are sent out via a standard web service, available at http://<ApplicationURL>/Webservice/Scheduler.asmp
• To configure the Email Task Scheduler, open the application's physical location (to easily access this from IIS, right click on the website in the left panel then click Explore), then navigate up one directory. For example if the Site Folder is E:\CC\Site, navigate to E:\CC\.
• Create a folder called Scheduler and add RunSchedulerCommand_Jan2014.exe within the Scheduler folder. In the RunSchedulerCommand, create a file named start_sched.cmd. Open this file in a text editor and add 4-6 lines of text based on the example below - these lines of text are used to invoke a tool which calls the web services and passes a parameter.
  
• Use the following parameters:
  • Audit
  • Action
  • Email
  • Cleanup

The format of the web service call is as follows:
<PhysicalWebsitePath>\bin\Scheduler\RunSchedulerCommand.exe<WebsiteURL>\Webservice\Scheduler.asmx <parameter>

You should modify both the <PhysicalWebsitePath> and <WebsiteURL> values to match those of your CMO application. The <parameter> values should remain as they are.

An example of what the file should look like after editing is below:

Ensure you save your changes when you have finished editing the file.

Now, if you run the start_sched.cmd bat file, any queued notifications will be sent out by the application. 

To automate the process of sending notifications, you will need to set up a Windows Scheduler task. Follow the steps below to do this:

• In the application server: click start, hover over administrative tools then click Task Scheduler.
• Click Create Task in the right Actions panel.
• In the General tab, enter a name for the task (e.g. CMO Scheduler). Ensure the Run whether users is logged on or not option is checked. 
• In the Triggers tab, click New. Create a new trigger to match the settings as shown below (ensure you set the start date to a time in the past).
  
• Click Ok when all settings are configured.

In the Actions tab, click New, then click Browse, then locate your start_sched.cmd bat file as shown in the example below:

Click Ok when complete.

On the Settings tab, ensure the If the running task does end when requested, force it to stop option is NOT selected.

No other default settings need to be changed for the task - Click Ok to save the task.

You can also manually run, end, or disable the task from the Task Schedule Library at any time by selecting the task and clicking one of the options in the right panel.

Create .bat Files

Create file Install.bat with the following contents and save it to the WinService folder in Service parent folder.

• Set installUtil=="C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe"
  • installUtil: path to InstallUtil.exe utility. It is a part of .net framework so it is not necessary to install anything.
• Set serviceName="CMOCompliance-WinService"
  • serviceName: name of Win Service. It should be a unique name, so if you have only one instance of this service then you can leave it as "CMOCompliance-WinService", otherwise you should add a prefix or postfix to identify it (e.g. CMOCompliance-WinService-Prod).
• Set servicefilePath="<path to win service\CMOCompliance.WinService.exe"
  • serviceFilePath: path to Win service. In this example it is F:\CMOCompliance\<instancename>\WinService\Service\CMOCompliance.WinService.exe
• %installUtil% /servicename=%serviceName% %servicefilePath%

Create start.bat with the following contents and save it to the WinService folder in Service parent folder.

• Set serviceName="CMOCompliance-WinService"
  SC start %serviceName%
  • serviceName: Name of the Win Service. It must be exactly the same as it is in the .bat file.

Create uninstall.bat with the following contents and save it to the WinService folder in Service parent folder. 

• Set installUtil="C:\Windows\Microsoft.NET\Framework\v4.0.30319\InstallUtil.exe"
• Set serviceName="CMOCompliance-WinService"
• Set servicefilePath="<path to win service\CMOCompliance.WinService.exe"
• %installUtil% /servicename=%serviceName% /u %servicefilePath%

Parameters InstallUtil, serviceName, and serviceFilePath must be exactly the same as install.bat file. 

Create stop.bat with the following contents and save it to the WinService folder in Service parent folder.

• Set serviceName="CMOCompliance-WinService"
  SC stop %serviceName%
  • serviceName: Name of the Win Service. It must be exactly the same as it is in the .bat file.

Edit CMOCompliance.WinService.exe.config

Find the CMOCOMPLIANCE.WinService.exe.config file and edit it. In the <appsettings> section you will find a connection string key. You need to place the connection string key from the CMO application here.

Install WinService

Either double-click the install.bat file in the WinService folder or run it via CMD prompt (as an admin). If the install is successful, InstallUtil.InstallLog will be created in the WinService folder. The below log entry would indicate a successful install:

Running a transacted installation.

Beginning the Install phase of the installation

See the contents of the log file for the
F:\CmoCompliance\<instance name>\WinService\Service\CMOCompliance.WinService.exe assembly's progress.

The file is located at:
F:\CmoCompliance\<instance name>\WinService\Service\CMOCompliance.WinService.InstallLog.
The Install phase completed successfully, and the Commit phase is beginning.

See the contents of the log file for the
F:\CmoCompliance\<instance name>\WinService\Service\CMOCompliance.WinService.exe assembly's progress.

The file is located at:
F:\CmoCompliance\<instance name>\WinService\Service\CMOCompliance.WinService.InstallLog.
The Commit phase completed successfully

Start WinService

Either start the WinService by double-clicking the start.bat file you created (you can also do this via CMD prompt) or by opening services.msc and starting the service manually.

If your application is connecting to the SQL database via Trusted_Authentication then you need to set  the service account for the service in Properties. For example: Website runs as svc-cmo-prod, you would need to set the CMOCOMPLIANCE-WinService to run under svc-cmo-prod as well.

Restoring the Application

If you need to restore the application from a backup, first obtain the backed files from your backup storage and copy them to a new IIS and SQL server. Then follow the instructions from Step 3 to reconfigure the application.

Dev Environment

Test Environment

 Production Environment