Contensive Installation and Setup

From Contensive Wiki
Jump to: navigation, search


Installation (v4.1)

Server Setup and Configuration (v4.1)

Amazon AWS (v4.1)

For Amazon AWS, create an instance from the AMI Contensive41. This AMI is built from the latest version of these instructions.

  1. Login with the new administrator account and update the account password (contensive) for
    • administrator - We recommend you not regularly use this account. If you leave Windows Remote Desktop open in your firewall, you should disable it. Otherwise you can leave it as an emergency login.
    • contensive - change the password, and update the new password in DcomCnfg for the ccKrnl.exe execution (see full installation for details)
    • kmaAdmin - This is the account used by administrators day-to-day and can be renamed or replaced. We recommend against using the administrator account.
  2. Configure an SMTP server for use by the server. We recommend using Amazon SES, but any SMTP server will work. If you use the IIS SMTP server on Windows 2008R2, Amazon does not provide a way to reverse the server's IP address and may be a deliverability issue. When you have it configured, log in to the admin site and enter it in the email tab of preferences.
  3. Add an elastic ip to ec2 instance

Non-Amazon Server (v4.1)

This instruction prepares a Windows Server 2008 R2 for Contensive 4.1.636.

  1. Establish a domain name for the server unrelated to the possible website.
  2. Windows Web Server 2008 R2-64
  3. Install the latest Windows Updates$
  4. Setup external firewall
    • 80
    • 21
    • 443
    • 3389 allow during setup, then disable after RDP 5901 setup in registry
    • 5900 for Contensive Monitor
    • 5901, for remote desktop, point-to-point if possible to
    • ICMP
  5. reverse map the server’s domain to the primary IP address
  6. Disable User Access Control
    • Control Panel > users > Left Pane
    • Set the warnings all the way off
  7. Create accounts
    • Administrative tools > Computer Management > Local User and Groups
      • If you have an external firewall, leave the administrator account and save it for emergencies, else disable it
      • Create a user admin account (not administrator), password never expires
      • Create a user for contensive, un:contensive, password never expires
  8. Windows Firewall. If you access the server remotely, we recommend you use an external firewall and disable the windows firewall to descrease the possibility of losing access to your machine.
    • Administrative Tools > Windows Firewall > Inbound Rules
    • World Wide Web Services, ports 80 + 443, allow
    • Remote Desktop + Remote DesktopFX, 3389. allow. If server access is limited to only a remote connection, leave this open. If you direct access to the machine, limit 3389 to your local IP(s)
    • add rule for Contensive Monitor, 5900, allow
    • add rule for Remote Desktop, 5901, allow
    • ICMPv4 (ping), allow
  9. Networking
    • Control Panel, set small icons, Network and Sharing Center
    • Local Area Connection > Properties > dbl click IP4
    • Verify all IP addresses are entered with mask, gateway and DNS. If no DNS available, use Google's 8.8.8.8, 8.8.4.4
  10. Local Security Policy
    • Administrative Tools > Local Security Policy > LocalPolicies
    • Local Policies > User Rights Assignment > Allow login through remote desktop
    • + Administrators
    • Security Options > “interactive Login: do not display last user name”=enable
    • Account policies > Account Lockout Policy
    • 3 invalid attempts
    • 3 minute lockout
  11. Remote Desktop Change Port (optional to increase security if you only have remote server access and no external firewall)
    • Regedit
    • HLM > System > Current Control Set > Control > Terminal Server > Winstations > RDP_TCP > PortNumber, set to 5901.
  12. Install IIS
    • Server manager → Roles → Install WebServer IIS
    • Administrative Tools > Server Manager > Root screen
    • Configure IE ESC > Turn off
    • Check “Do not show me this consol at login”
    • Add Roles and Features
    • Administrative Tools > Server Manager > Roles > Add Role Services
    • Check ASP.NET, agree to add required roles
    • Check ASP
    • Check CGI
    • Security, Basic Authentication
    • Management Tools, IIS 6 management compatibility
    • Administrative Tools > Server Manager > Features
    • Check SMTP Server, agree to add required roles
  13. Windows Settings
    • Set timezone (typically for your customer's timezone)
    • Turn on Automatic Windows Updates
  14. Create Working Folders and permission
    • set administrators full control for hosts files
    • D:\Archive
    • D:\InetPub
      • users: full control
    • D:\Db
      • users: full control
    • D:\DbBackup
    • users: full control
    • C:\windows\temp
      • users: list + read
      • IIS_User: List + read
  15. Create Folder on Desktop for frequent shortcuts
    • ODBC32 - Windows\sysWow64\odbcad32.exe
    • dcomcnfg shortcut
    • IIS shortcut
    • Services shortcut
  16. Software Installation
    • Microsoft Web platform Installer
      • PHP Manager
      • PHP 5.5.11 (previously 5.3.5)
    • Firefox or Chrome
    • Optional backup provider like Carbonite. Backup stores:
      • \DbBackup (daily database backup files)
      • \inetpub (content files, wwwRoot for each site)
      • \program files (x86)\kma\contensive\config (server configuration)
      • \program files (x86)\kma\contensive\addons (addons used by all sites)
    • Sql Server 2008 R2 SP2. If Db size anticipated under 20G use Express Edition. Over 20G requires Web Edition
      • Google search, “Microsoft® SQL Server® 2008 R2 SP2 - Express Edition”
      • for 32-bit machines - use x86
      • for 64-bit machines - use x64
      • Install instance features, but check Default Instance during install
      • Account provisioning: mixed mode authentication
      • Set sa password
    • 7Zip, 64 bit windows version
    • Contensive, get latest version at http://clib.io
  1. Set Dcom permissions for Contensive
    • run "DComCnfg/32 - MMC comexp.msc /32" then add
    • Then open fdcomcnfg and locate cckrnl.exe
    • Right click, click permissions, set everyone/all for all three sections
    • identity, contensive/-pw-
    • if ccKrnl does not show in dcomcnfg (make sure you are in the 32-bit view MMC comexp.msc /32), run 2 registry files found in the folder for this document (ccKrnl.reg, ccKrnl2.reg)(Note: on 64bit machines this has to run: at the command Line run “MMC comexp.msc /32”)
  2. Folder Permissions
    • kma/contensive - user/all
  3. Run configWizard
  4. Server Service, verify it starts OK
  5. Run Application Manager
  6. Verify attach to local server
  7. Add Root Site, named for the server’s domain (s00.kma.net)
  8. Change Contensive config (MonitorConfig.txt) to use port 5900 for monitor, restart Contensive Monitor service
  9. Setup backup tools
    • If you need a Sql Server backup script, download kmaBackupTools.zip, unzip and create a scheduled task for backupSql.cmd. It backups all Sql Server catalogs to a file in d:\DbBackup
      • Verify the d:\DbBackup folder matches in the Sql file
      • Verify the source programs files are correct in the cmd file
      • Run a test of the cmd file
      • Setup a scheduled task to run it routinely (we typically run everyday at 8pm,)
  10. IIS PHP Manager
    • Open from root of IIS Manager
    • Enable php_com_dotnet extension
    • Add max_input_vars 2000
    • upload_max_filesize = 50M
    • post_max_size = 50M
  11. IIS Manager
    • Application Pools > set applicaiton pool default
    • Enable 32-bit = true
    • Recycling
      • Private Limit = 40,000
      • Virtual Limit = 200,000
      • Requests = 100
    • Click on top node, set default in right-hand pane
      • ASP
      • Max Requesting Entity Body Limit = 10M
      • Session Properties, Enable Session State = false
      • Default Document list, only
        • Index.php
        • index.asp
      • Error Pages
        • Edit feature settings - custom error pages
        • 404 set to /index.php (for each site)
  12. Setup SMTP
    • Start IIS6 Manager
    • go to SMTP Virtual Server 1, properties
    • Leave IP set to all unassigned
    • go to Access Tab
    • Connect - grant only 127.0.0.1
    • Relay Restrictions - grant only 127.0.0.1
    • go to Delivery Tab, click advanced
    • Set masquerade to server name i.e. s13.kma.net
    • set FQN to server name i.e. s13.kma.net
    • Domain node under Virtual Server, rename to this server's domain
  13. Run windows Updates
    • auto install at 3am (while v42 does not start correctly, set to manual install)
  14. Services
    • administrative Tools → Services
    • SMTP - Start and set to automatic
    • Contensive Monitor - Start and set to automatic
    • Contensive Server - Start and set to automatic
    • IIS Admin Services - Start and set to automatic
    • SQL Server - Start and set to automatic

Upgrading Contensive Software (v4.1)

Upgrading Contensive requires you first uninstall the current version, then install the new version. When the software upgrade is complete, open the Contensive application manager, right click on your server node and click the "Upgrade all running applications". This process upgrades your database schema and content to support the newer build It takes about five to ten minutes per site.

Uninstalling Contensive Software (v4.1)

1. Click ccStop.cmd in the Contensive Program Files Directory. This stops the Contensive and IIS Services.
2. Open Task Manager to verify the following services have been stopped. If they have not after a minute, manually kill them

  • cckrnl.exe
  • ccprocessemail.exe
  • ccservice.exe
  • ccmonitor
  • cchousekeep.exe

3. Use the Add/Remove Programs in Control Panel to remove Contensive.
4. After removal, restart necessary IIS services. Running the IISReset command from the command prompt (run as administrator) will do this.

Installing Contensive (v4.1)

1. You should have the following information available before beginning installation

a. Contensive Content Server Installation CD or download.
b. A Windows user login account for contensive with username and password. This account should have user privileges and read/write access to the wwwRoot and content files folders.

2. If a previous version of Contensive is installed backup all content, both database and content files.

3. Verify that the Service Control Manager (Services under Administrative tools) is closed. If left open, this may prevent windows from correctly installing the services.

4. Run the Contensive installation program.

5. When complete, the Configuration Wizard will start. It describes and tests your DCom settings that follow:

a. Open DComCnfg from the wizard, or at the run prompt, navigate to Component Services > Computers > My Computer > dcomcnfg.
b. Locate ccKrnl.KernelServices object.
c. Right click and go to Properties.
d. Under the General Tab, Use “Default” authentication type.
e. Under the Security, Select "Use Custom Access Permissions", and add Everyone allow access. Select Use Custom Launch Permissions, and add Everyone allow launch.
f. Under the Identity Tab, select “This User”, and enter the local Contensive user account.
g. When you continue, Contensive will start.

6. Go to the Program Files\kma\Contensive folder, and make sure:

a. Email Out folder has Read/Write permissions for Everyone.
b. Log folder has Read/Write permissions for Everyone

Installation (v5.0)

This information is for the Contensive v5.0 Library available open source at http://www.github.com/contensive/contensive50. The latest binaries are available at http://clib.io.

Server Setup and Configuration (v5.0)

This process is under development. Please provide any feedback on issues you had to support@contensive.com

Amazon AWS (v5.0)

For Amazon AWS, create an instance from the AMI Contensive50. This AMI is built from the latest version of these instructions.

  1. Login with the new administrator account and update the account password (contensive) for
    • administrator - We recommend you not regularly use this account. If you leave Windows Remote Desktop open in your firewall, you should disable it. Otherwise you can leave it as an emergency login.
    • contensive - change the password, and update the new password in DcomCnfg for the ccKrnl.exe execution (see full installation for details)
    • kmaAdmin - This is the account used by administrators day-to-day and can be renamed or replaced. We recommend against using the administrator account.
  2. Configure an SMTP server for use by the server. We recommend using Amazon SES, but any SMTP server will work. If you use the IIS SMTP server on Windows 2008R2, Amazon does not provide a way to reverse the server's IP address and may be a deliverability issue. When you have it configured, log in to the admin site and enter it in the email tab of preferences.
  3. Add an elastic ip to ec2 instance

Non-Amazon Server (v5.0)

This instruction prepares a Windows Server 2016 for Contensive 5.0.0.

  1. Establish a domain name for the server unrelated to the possible website.
  2. Windows Web Server 2016
  3. Install the latest Windows Updates (settings > windows updates)
  4. Setup external firewall
    • 80
    • 21
    • 443
    • 3389 allow during setup, then disable after RDP 5901 setup in registry
    • 5900 for Contensive Monitor
    • 5901, for remote desktop, point-to-point if possible to
    • ICMP
  5. If a local SMTP server will be used, reverse map the server’s domain to the primary IP address
  6. skip - Disable User Access Control
    • Control Panel > users > Left Pane
    • Set the warnings all the way off
  7. Create accounts
    • Windows Administrative tools > Computer Management > Local User and Groups
      • If you have an external firewall, leave the administrator account and save it for emergencies, else disable it
      • Create a user admin account (not administrator), password never expires
      • If the server will run a workerRole, create a user for the workerRole, un:contensive, password never expires
  8. Windows Firewall. If you access the server remotely, we recommend you use an external firewall and disable the windows firewall to descrease the possibility of losing access to your machine.
    • Administrative Tools > Windows Firewall > Inbound Rules
    • World Wide Web Services, ports 80 + 443, allow
    • Remote Desktop + Remote DesktopFX, 3389. allow. If server access is limited to only a remote connection, leave this open. If you direct access to the machine, limit 3389 to your local IP(s)
    • add rule for Contensive Monitor, 5900, allow
    • add rule for Remote Desktop, 5901, allow
    • ICMPv4 (ping), allow
  9. Networking
    • Control Panel, set small icons, Network and Sharing Center
    • Local Area Connection > Properties > dbl click IP4
    • Verify all IP addresses are entered with mask, gateway and DNS. If no DNS available, use Google's 8.8.8.8, 8.8.4.4
  10. Local Security Policy
    • Administrative Tools > Local Security Policy > LocalPolicies
    • Security Options > “interactive Login: do not display last user name”=enable
    • Account policies > Account Lockout Policy
    • 3 invalid attempts
    • 3 minute lockout
  11. Remote Desktop Change Port (optional to increase security if you only have remote server access and no external firewall)
    • Regedit
    • HLM > System > Current Control Set > Control > Terminal Server > Winstations > RDP_TCP > PortNumber, set to 5901.
  12. Install IIS
    • Server manager → Roles → Install WebServer IIS
    • Administrative Tools > Server Manager > Root screen
    • Configure IE ESC > Turn off
    • Check “Do not show me this consol at login”
    • Add Roles and Features
    • Administrative Tools > Server Manager > Roles > Add Role Services
    • Check ASP.NET, agree to add required roles
    • Check ASP
    • Check CGI
    • Security, Basic Authentication
    • Management Tools, IIS 6 management compatibility
    • Administrative Tools > Server Manager > Features
    • Check SMTP Server, agree to add required roles
  13. Windows Settings
    • Set timezone (typically for your customer's timezone)
    • Turn on Automatic Windows Updates
  14. Create Working Folders and permission
    • set administrators full control for hosts files
    • D:\Archive
      • users: full control
    • D:\InetPub
      • users: full control
    • D:\Db
      • users: full control
    • D:\DbBackup
    • users: full control
    • C:\windows\temp
      • users: list + read
      • IIS_User: List + read
  15. Create Folder on Desktop for frequent shortcuts
    • ODBC32 - Windows\sysWow64\odbcad32.exe
    • dcomcnfg shortcut
    • IIS shortcut
    • Services shortcut
  16. Software Installation
    • Microsoft Web platform Installer
      • PHP Manager
      • PHP 5.5.11 (previously 5.3.5)
    • Firefox or Chrome
    • Optional backup provider like Carbonite. Backup stores:
      • \DbBackup (daily database backup files)
      • \inetpub (content files, wwwRoot for each site)
      • \program files (x86)\kma\contensive\config (server configuration)
      • \program files (x86)\kma\contensive\addons (addons used by all sites)
    • Sql Server 2008 R2 SP2. If Db size anticipated under 20G use Express Edition. Over 20G requires Web Edition
      • Google search, “Microsoft® SQL Server® 2008 R2 SP2 - Express Edition”
      • for 32-bit machines - use x86
      • for 64-bit machines - use x64
      • Install instance features, but check Default Instance during install
      • Account provisioning: mixed mode authentication
      • Set sa password
    • 7Zip, 64 bit windows version
    • Contensive, get latest version at http://clib.io
  1. Set Dcom permissions for Contensive
    • run "DComCnfg/32 - MMC comexp.msc /32" then add
    • Then open fdcomcnfg and locate cckrnl.exe
    • Right click, click permissions, set everyone/all for all three sections
    • identity, contensive/-pw-
    • if ccKrnl does not show in dcomcnfg (make sure you are in the 32-bit view MMC comexp.msc /32), run 2 registry files found in the folder for this document (ccKrnl.reg, ccKrnl2.reg)(Note: on 64bit machines this has to run: at the command Line run “MMC comexp.msc /32”)
  2. Folder Permissions
    • kma/contensive - user/all
  3. Run configWizard
  4. Server Service, verify it starts OK
  5. Run Application Manager
  6. Verify attach to local server
  7. Add Root Site, named for the server’s domain (s00.kma.net)
  8. Change Contensive config (MonitorConfig.txt) to use port 5900 for monitor, restart Contensive Monitor service
  9. Setup backup tools
    • If you need a Sql Server backup script, download kmaBackupTools.zip, unzip and create a scheduled task for backupSql.cmd. It backups all Sql Server catalogs to a file in d:\DbBackup
      • Verify the d:\DbBackup folder matches in the Sql file
      • Verify the source programs files are correct in the cmd file
      • Run a test of the cmd file
      • Setup a scheduled task to run it routinely (we typically run everyday at 8pm,)
  10. IIS PHP Manager
    • Open from root of IIS Manager
    • Enable php_com_dotnet extension
    • Add max_input_vars 2000
    • upload_max_filesize = 50M
    • post_max_size = 50M
  11. IIS Manager
    • Application Pools > set applicaiton pool default
    • Enable 32-bit = true
    • Recycling
      • Private Limit = 40,000
      • Virtual Limit = 200,000
      • Requests = 100
    • Click on top node, set default in right-hand pane
      • ASP
      • Max Requesting Entity Body Limit = 10M
      • Session Properties, Enable Session State = false
      • Default Document list, only
        • Index.php
        • index.asp
      • Error Pages
        • Edit feature settings - custom error pages
        • 404 set to /index.php (for each site)
  12. Setup SMTP
    • Start IIS6 Manager
    • go to SMTP Virtual Server 1, properties
    • Leave IP set to all unassigned
    • go to Access Tab
    • Connect - grant only 127.0.0.1
    • Relay Restrictions - grant only 127.0.0.1
    • go to Delivery Tab, click advanced
    • Set masquerade to server name i.e. s13.kma.net
    • set FQN to server name i.e. s13.kma.net
    • Domain node under Virtual Server, rename to this server's domain
  13. Run windows Updates
    • auto install at 3am (while v42 does not start correctly, set to manual install)
  14. Services
    • administrative Tools → Services
    • SMTP - Start and set to automatic
    • Contensive Monitor - Start and set to automatic
    • Contensive Server - Start and set to automatic
    • IIS Admin Services - Start and set to automatic
    • SQL Server - Start and set to automatic

Software Initialize and Configuration (v5.0)

Contensive 5.0 runs applications in a cluster. A cluster is a collection of servers that all host the same application(s). There can be one or more servers in a cluster, and one or more application in a cluster. A server can only belong to one cluster.

After creating a server with all software installed, the next step is to configure the software to run your application architecture. In version 5.0 there are a few options:

  1. File Locations
    • CdnFiles - This is the root directory of your primary static content source. This may be the same location as your application, as it would be typically for a website. If, on the other hand, you wanted to deliver all static resources like css files, images, uploaded content, etc from an Amazon AWS S3 bucket, you would point the CdnFiles to that bucket.
    • AppRoot - This is the root directory of the application server. If your application is a website, this would be the folder where your website (html,php,aspx,etc) files are stored. if this is the application server for a mobile app, this would be location where the server REST calls are made. For multiserver hosting, this location is a mirror of your remote file store.
    • privateFiles - This is a location where your can store files that do not map to a public Internet address. For multiserver hosting, this location is a mirror of your remote file store.
  2. Sql Server connection - You must setup an instance of SQl Server either on the local machine, on a remote server, or use Amazon AWS RDS.
  3. Cache Server - Setup an instance of Amazon Elasticache with MemCacheD.

Use the clib.exe command line program to setup and configure the cluster and applications.

Install the Windows Service on a server

The windows service hosts two optional features, the task scheduling and task running. You only need to install and run the service is these features are needed

  1. Open a command line shell
  2. change directories to the installation folder (c:\program files (x86)\Contensive\clib)
  3. Run installutil clibservice.exe, if installUtil is not found, either add its path to your program path or include the path in the command line. installUtil can be found under \Microsoft.NET\Framework64\v4.0.30319, or whichever is appropriate for your installation. Go to the Windows Service Manager (in administration tools), set the service to automatic start, and start the service.
installUtil cclibservice.exe

clib.exe Command line configuration tool

Initialing the cluster for a server

Prepare the following:

  1. A unique name for the application, no spaces, under 16 characters
  2. The drive letter for the data store
  3. Sql Server Database
    • The endpoint of a local instance is (local)
    • Only port 1433 is currently supported
  4. Cache Configuration Endpoint on Amazon Elasticache
clib -n

When the cluster is configured, it will being the new application wizard

Adding an application

Prepare the following:

  1. A application name unique on within cluster
  2. A domain name for the application server.
  3. The programming framework you will be using (Aspx, Node, IIS Module)
clib -n

Upgrading an application

Run 

clib -upgrade applicationname

or 

clib -upgradeall

Enable/Disable the Task Scheduler

The task scheduler polls each application for addons that need to be run. You should only have one instance of the task scheduler running in each cluster. For the task scheduler to run automatically, you must first configure the clibService as a windows service.

To run the task scheduler from the console directly 

clib -taskscheduler run

To enable the task scheduler in the windows service. 

clib -taskscheduler on

To enable the task scheduler in the windows service. 

clib -taskscheduler off

Enable/Disable the bot the Task Scheduler and Task Runner

To run the Task Scheduler and Task Runner from the console directly 

clib -tasks run

To enable the Task Scheduler and Task Runner in the windows service. 

clib -tasks on

To enable the Task Scheduler and Task Runner in the windows service. 

clib -tasks off

Enable/Disable the Task Runner

The task runner takes tasks from the task queue and executes them. You can have as many instances of task runner as you need in a cluster. For the task runner to run automatically, you must first configure the clibService as a windows service.

To run the task runner from the console directly 

clib -taskrunner run

To enable the task runner in the windows service. 

clib -taskrunner on

To enable the task runner in the windows service. 

clib -taskrunner off

Server Build Version

clib -version

Cluster and Application Status

clib -status

Installation Problem Isolation

1. Check Web server functionality

If the web site is returning an error and not a web page, check that the server is running correctly. A simple HelloWorld.htm page is provided in the Admin site at the following address. (http://YourDomain.com/admin/HellowWorld.htm). You should expect a page with “Hello World”. If this returns an error, verify the IIS configuration. This is not a Contensive error, but a server configuration problem.

2. Check ASP functionality

A simple HelloWorld.asp page is provided in the Admin site at the following address. You should expect a page with “ASP Hello World”. (http://YourDomain.com/admin/HellowWorld.asp) If this returns an error, verify the IIS configuration. This is not a Contensive error, but a server configuration problem.

3. Check Contensive functionality

If the previous tests passed, test the Contensive status method (http://YourDomain.com/admin/Index.asp?method=status). This should return “Contensive OK”. If it returns any other response, check the page source for an error comment. The most common issues are:
a. Contensive Application Not Found - Open the Contensive Application Manager and verify your application is running. If it is, the problem may be DCom permissions.
b. Connection Error opening Datasource Default or Audit - There is a problem with the database, the connection string, or the connection to the machine holding the database.

4. Check the Contensive Trace Log.

A trace log is created for all internal Contensive errors. The log is located at [Program Files]\kma\contensive\logs\Tracexxxxx.log. There may be several lines for each error, grouped together by the time of the error. Check the first line of each error group. Generally, the information most likely to assist you will be at the end of the line.

5. Windows 2003 - If you can not upload, IIS may be limiting the upload size. Use the IIS Metabase editor to set the upload size limit.

6. Windows 2003 - If ASP/ASPX pages will not run, IIS may be blocking them.

Site Lifecycle Considerations

When Contensive has been installed and the website integration is complete, you need to consider site lifecycle issues. These include site monitoring, database management, file system management, log monitoring, and disaster recovery.

Site Monitoring

Two suggestions for monitoring:

  1. Setup a monitor to check site status, available at urls ending with ?method=status. The site will return "Contensive OK" when the site is running correctly.
  2. Turn on the Contensive Monitor service and setup a monitor to check its response, available typically on http://serverDoamin:4532/status. The monitor periodically checks the status method of each Contensive site on the server, as well as other checks like Contensive log size (an indicator of other site or Database problems) and current drive space availability. Configure the monitor service by editing the monitorConfig file in the \program files (x86)\kma\contensive\config folder. Restart the monitor service after changing the file. The Monitor can be configured to automatically IISReset the system on error conditions.

Database Management

We recommend you have a DBA for sql Server.

File System Management

The monitor tracks available drive space. Within you application take care not to over-tax file folders.

Log Monitoring

The monitor tracks and housekeeps log size, setting an alarm on a threshold. Review your logs frequently.

Site Migration

To move or copy a site, transfer these file stores:

  1. A copy of the content files, typically d:\inetpub\appName\files
  2. A copy of the application root files, typically d:\inetpub\appName\wwwRoot
  3. A database backup, typically d:\DbBackup
  4. A copy of the addons folder, typically c:\program files (x86)\kma\contensive\addons
  5. The configuration file, typically c:\program files (x86)\kma\contensive\config\config.xml

Copy these files in place and restore the Db from the backup. Start the contensive service.

You can manually create the IIS application, or use the Contensive Manager, right click on the application, stop the application, then click "Start with Upgrade".

Disaster Recovery

Restoring a server is straight forward if you have properly prepared. We recommend always keeping a newly constructed server ready. If you use a service like Amazon AWS you can just keep an image available.

Performing a periodic recovery dry-run is also recommended.

There are five file stores needed to restore a server. They should be backed up periodically.

  1. Each site's database Backup file (typically \DbBackup folder)
  2. Each site's content files (typically \InetInfo\siteName\files)
  3. Each site's wwwRoot files (typically \InetInfo\siteName\wwwRoot)
  4. The server's addon installation store (typically \Program Files(x86)\kma\contensive\addons folder)
  5. The server's contensive config file (typically \Program Files(x86)\kma\contensive\config folder)

In the event of a server loss, on a new server, stop Contensive services, restore the above files, restore the database from the DbBackup and restart the services.

Creating a New Web Site or Application

To create a new site start the Contensive Application Manager. It creates a Microsoft Access database by default. Use Microsoft SQL Server Migration Assistant (SSMA) to create an Sql Server application.

  1. Open the Contensive Application Manager, Start > Programs > Contensive > Application Manager
  2. Click on the server where you want to add your site. When the Application Manager connects to the server, the server's icon will turn green.
  3. Right click on the server, and click Add Site. You will be prompted for the following:
Site Name 
The unique name you give for this application. (no spaces)
IP Address 
Used for IIS bindings during build. Leave 127.0.0.1 for development site
Domain Name 
Used as the default domain for the application, and the IIS binding.
HTML Documents Folder 
IIS will be set to this folder. Contensive will use it as the physicalWwwRoot property. Typically \InetPub\appName\wwwRoot
Content Files Folder 
Contensive will use this folder for all VirtualFile saves, and for the \files\appName
f. ODBC DSN File Folder
g. Database File Folder
h. SMTP Email Server
i. Admin Email Address

Creating a new site using other programming environments

Contensive is a server that can deliver the entire site from a single API call. It uses an activex object to interface with the webserver's scripting environment.

You can use Contensive to manage content delivery form any programming language that can work with an instance of an activex object. The process is as follows:

  1. Create the object from the program id ccweb3.mainclass
  2. Initialize several contensive properties from the server context (an asp vb example is included here)
  3. Call any Contensive method to deliver the site content. The simplest is "GetHTML()"

Contensive Installation and Setup

1. Installing Contensive on the Server

To configure Contensive, first run the installation program. This installs the softare, configures the Windows Services to start Contensive on reboot, and optionally installs a Sample website.

2. Creating a site

To create a website that uses Contensive, Open the Contensive Application Manager, right click on the server node where you want to create the site and click the Create Site link. Follow the wizard instructions.
This process creates a default MS Access database. To switch to another ODBC supported Db, create an empty Database and an ODBC data source to it. Open the Contensive Application Manager and right click on the site you wish to setup for your database. Stop the Contensive application, switch the Database Connection String, and Start with Upgrade. This will create the necessary tables to run your site.
Retrieved from "http://wiki.kmacloud.net/index.php?title=Contensive_Installation_and_Setup&oldid=2974"