Contensis database access
Contensis has a distributed publishing architecture with no specific need for connectivity back to the CMS database for front-end websites, essentially the CMS server and database can be turned off and your website will continue to function without any issue.
There are some exceptions, in areas such as personalisation and authentication. If you want to authenticate users and have them log on to your website, or use any of the modules which rely on this functionality you will require database access between your webserver and your CMS database server. This access will be on port 1433 and will use the database credentials and host name used for your Contensis installation.
By default this type of access is not enabled, this ensures that you don't use a feature in test before you have deployed to live, not realising that it won't work (maybe you are hosting the site outside of your network and there is no VPN back for database access).
Modules and features that require Contensis database access
- Who's Who
- Document Channels
- Log on / Log off Controls
Enable Contensis database access
If you need to enable Contensis database access for one of the modules you must:
- ensure with your systems team that they are happy to connect back to the cms database in the front end production environment
- ensure you are happy to have potential issues during an upgrade with your front-end website
- ensure you are happy with the level of resilience that your CMS database provides.
If you are happy with the items highlighted, enabling access is very straightforward.
You simply need to:
- Press on the Management Console icon.
- Choose Project Setup.
- Choose Publishing Servers.
- Press on the CMS Config link listed against the relevant publishing server.
- Update the Setting Contensis_Data_HasContensisDatabaseAccess from false to true.
- Press Save and publish.
Was this article helpful?