Contensive Installation and Setup

Server setup

1. Verify the installation of Windows 2008/2003/2000 with the latest MS Service Pack.
2. For Windows 2000/NT, verify Microsoft MDAC_TYPE 2.7 or newer has been installed.
3. If a firewall is being used, open HTTP (80) and SMTP (25) to the mail server being used.

Upgrading Contensive

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

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

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 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, and log monitoring.

Site Monitoring

These are several ways to monitor your site. Contensive includes a status method, and a monitoring service. You can also setup a third-party monitor to hit any dynamic page.

1. Contensive status method with a third party monitor

Contensive includes several special 'methods' from the website URL. One is the status method. To call the status method, use the URL:

http://yourdomain/pagename?method=status

The expected response from the site is an HTTP response "Errors 0". Any other response indicates a problem with the site.

2. Contensive Monitor service

One of the services installed with Contensive is the Monitor Service. The monitor periodically checks the status method of each Contensive site on the server, as well a few other important checks like Contensive log size (an indicator of other site or Database problems) and current drive space availability.

The monitor is controlled by the monitor.txt file in the Contensive program files directory. After changes, the monitor service must be stopped and restarted.

The Monitor can be configured to automatically IISReset the system on error conditions. It also has an HTTP port 80 status screen at port 4532. When the monitor service is running, a hit to this page returns an HTML page with the results of the last checks the monitor ran.

If you have several sites on a server, you can setup a third party monitor or monitoring service to check the Contensive Monitor periodically (every 5 minutes). An error condition two cycles in a row may indicate a problem that IISReset could not recover.

3. Hit any dynamic page with a monitor

Another simple monitor is to setup a website monitor or monitoring service to hit any page on your site. We recommend hitting the status method, as it will report database and other process errors that may occur even when a physical page returns.

Creating a Web Site

Contensive is a content server the runs on Windows Server. Any website hosted on Windows Server can access Contensive.

To create a new site that uses ASP scripting as it's hosting page, you can either use the 'new site' wizard in the Application Manager, or create it manually.

Using the New Site Wizard

The Site Wizard creates a simple site, using MS Access as it's database. If you wish to use another database, you can easily switch after the site is created.

1. Open the Contensive Application Manager, by clicking 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
  • IP Address
  • Domain Name
  • HTML Documents Folder
  • Content Files Folder
  • ODBC DSN File Folder
  • Database File Folder
  • SMTP Email Server
  • Admin Email Address