UCM server Configuration Variables

Content management systems are just frameworks that can be customised to once CM needs. All business requirements can be put into different baskets like:

• Out of the Box
• Configuration or Settings Change
• Customisation

If we need to do global configuration changes the best method is Configuration Variables. UCM has lot of config variables that can be used to change the behaviour of Content Server. These varibales should be put under Admin Server--> General Configuration --> Additional Configuration Variables.

Below are some of the variables and a short description of the behavioural changes that they bring to Content Server.

1. AutoContributorAdvancesOnUnlock=true, AutoContributorAllowsReview=true these two config variables should be used when you want to trigger workflow process automaticlly when you add content through webdav folders.Content checked in using a WebDAV client enters the first autocontribution step of the workflow process. This requires the author to manually initiate the workflow by performing a check out / check in to force the item into the first defined step.

2.DefaultAccounts=#none(R),#all(R): This configuration variable is used for annonymous access to SiteStudio websites running on Oracle Content Server outside DMZ. DefaultAccounts=#none(R) variable makes all content items checked in without any accounts readable for all users. DefaultAccount=#all(R) variable makes all content items checked in under any account readonly for all users.

3.DisableSiteStudioContributor=true, Usual deployment architecture to have a dynamic SiteStudio site is you will have one contribution server inside the corporate network and clustered consumption servers in DMZ. Here we should disable any type of contribution capabilities. In that case we should use this config variable.

4.AllowAllRedirectUrl=true, Lets look at this scenario. You have site studio website and a section of the website has an external URL as a primary layout page. When you do this and click on the link you will be first redirected to a standard page and there you have to click on the link to your final destination. By adding the config variable at the config.cfg file you will bypass this behaviour.

This is not the end of this blog i will add more variables as and when i use them.