Ektron CMS300 Readme
A database upgrade is required if you are moving from version 4.5x or 4.7x.
You must create a backup of your existing database before
running the upgrade against it.
The database upgrade utility is non-transactional and can only be run
once per upgrade. If it fails, you must restore your database from
a recent backup. Please see the setup manual for more information
regarding the upgrade process.
For detailed information on the new features added in CMS300 see
- Custom Fields
Custom search fields can be defined and assigned to content and library items. These are
the types of custom fields which can be defined:
- Free Text
- Single Select
- Multiple Select
- Yes/No Checkbox
A defined field can be marked as accessible to unauthenticated users, otherwise it can
only be searched when the user is logged into the CMS
- Extended Search
Custom field data assigned to content or library items can be searched through the
search functionality. Both authenticated and unauthenticated users have the ability
to use the custom fields for searches.
- Simplified Library
The library UI is modified to make the selection of images for content easier. Images can quickly
and easily be search by the custom field data assigned to them. Any found images can easily be
placed into the document with a couple of mouse clicks.
- DMS400 PDF Conversion
When a DMS400 v1.1 or later is installed the CMS300 offers the ability to publish the document
assets stored in the DMS as PDF documents. If the folder is configured to publish its documents
as PDF then when the document completes the approval process it is converted to PDF and
made accessible for general viewing.
- Support for MySQL
The MySQL database is supported in this version.
- DMS Work Off-Line Support
Support for the "Work_Offline" feature in the DMS is now supported.
- Oracle Support
The Oracle database is supported with this release.
- Search on DMS
Issues with the Search not allowing more than one parameter are resolved.
- Macintosh Safari Support
The Workarea functionality now supports the Macintosh Safari browser.
Integrators can either use the HTML editing or encorporate their own Macintosh HTML editors.
- Client Side Installation
The client side installation, when the DMS is installed, performs a smoother installation process
for the end user.
- Asset Management Support
Asset Management functionality, such as the
Document Management System,
is supported. This allows both
authenticated users and unauthenticated users to interact with complex assets, such as MS Office
documents. Authenticated users can create, edit, and publish assets. Assets go through the defined
approval process before publication. Links can be made to published assets.
Unauthenticated users can view published assets.
- Asset Search
The search functionality has been extended to also search the metadata on active and published
assets. Unauthenticated users can only search published assets.
- Automatic Task by Folder
The automatic task creation is now based on folders. Each folder is configured to create tasks
when content is submitted. Sub-folders inherit the folder settings or they can have their own
settings. A task's state can change automatically to track the progress of work
on that content. Users can also use the tasks to hold discussions and communicate information.
- Task Categorization
Categories and sub-categories can be created for tasks. This offers a high level of organization
of multiple tasks.
- Firefox Support
The Mozilla Firefox 1.0 browser is supported.
- eWebEditPro+XML v4.2
CMS300 now includes eWebEditPro+XML V4.2.
This adds powerful capabilities to easily create, collect and validate XML data via internal-facing forms, and display
it in multiple outputs. V4.2 includes spreadsheet-like math capabilities, support for XP SP2, and other valuable
features and benefits.
- Improved Content User Interface
A new and less intrusive Workarea content user interface is offered.
When logged into a site hosted by CMS300, the borders and menus for content editing do not
interfere with the formatting of the content and only appear when the mouse moves over the content.
A right mouse click brings up a floating toolbar at the mouse location. The "Classic"
interface from previous versions is still available and can be selected through a setup option.
Configuring New CMS
- Database Upgrade
The database upgrade can only be run once on an older version of the database. Once this is done,
an upgrade will be unsuccessful.
There are a number of modifications to the database schema in the Ektron CMS300.
This requires changes to some existing triggers.
Disable any triggers which exist on any modified tables before running the Ektron dbupgrade utility.
The dbupgrade utility is run when installing Ektron CMS300 to upgrade from
an older version, e.g., 4.6 to a newer version, e.g., 4.7 or 4.8. Any existing database triggers prevent
the dbupgrade utility from successfully updating the database to be compatible with CMS300 v4.8.
Modify the triggers to match the new database schema after updating the database.
Then reenable the triggers.
Below is the list of modified tables from version 4.5 or later to 4.8.
If any triggers reference these tables then please modify the triggers accordingly.
- Enabling Multi-Language Content
If upgrading a database, the default behavior is for the support of multiple languages to be disabled. On a new database
the behavior is to have the multiple language support enabled. This feature can be enabled or disabled by modifying
the EnableMultilingual variable in setup.asp. A value of '1' enables the functionality;
of '0' disables it.
- Selecting Default Site Language
The default language for the site is selected in the setup.asp file. The DefaultContentLanguage variable specifies
which language to use when there is no translation for a page. The value in this is the language code.
- Acrobat Reader Required
Adobe Acrobat Reader is required to view the CMS300 manuals. You can acquire and install a copy of Acrobat Reader
- NTFS Considerations
If your file system is NTFS and you are running ASP, you need to ensure that IIS has write permissions to the upload
directories in your CMS300 site. These include uploaded files, uploaded images and databases (only if you are using MS Access).
In most systems the c:\inetpub\wwwroot directory has unique user permissions for security reasons. When you create a directory
in this path, the default permissions are often limiting.
The CMS300 installation now automatically sets write permissions to the NTFS Everyone group for uploaded files, uploaded images,
and database directories. Note: These should be reset prior to production use to your desired model on your
- MSSQL User Required
If you are using a MS SQL Server database, you need to ensure that a user from IIS can access the database. By default, the
account is usually SystemName\IUSR_SystemName. Depending on your configuration, you need to either set up an account that has
read and write privileges to the CMS300 database or set the user in IIS to a user that already has permissions in the
- WINDOWS 2003 USERS
- ASP Services - In IIS6, ASP scripting is turned
off by default. Because our application uses .ASP, it needs to be turned on.
- Enable Parent Pathing In
IIS - By default, Windows 2003 Server may have
this disabled by default. Some functionality of CMS may require this to be enabled, such as the loading of the
content and image editors.