UCM Custom Skins and Layouts
By Kyle Hatlestad on Aug 06, 2009
In UCM 10gR3 and in earlier versions of Content Server 7.x, it used to be that you could create a new skin for the interface by taking one of the skins in the [weblayout dir]\resources\layouts\[layout name]\ directory, making a copy, and giving it a new name. Then in the User Profile page, you'd have a new choice in the Skin pull-down list. The same method would hold true for creating custom layouts as well.
In 10gR3, a new publishing architecture was put in place so that you could create a component which would have resources that could be published out to these directories. This is how the standard Oracle and Oracle 2 skins and layouts work now. Anyone who tried to modify the images or stylesheets in those skins within the weblayout\resources structure would have seen them eventually revert back to the default ones. That's because the server was republishing the originals out to those directories.
But custom ones that lived in that directory were left alone and still appeared in the Skin or Layout list. Until, that is, version 10.1.3.3.3 of UCM. Changes where made so that if your skin was not identified in a custom component to be merged with the LmLayoutSkinPairs table, then it wouldn't appear in the list.
Luckily, there are a couple of config flags that allow you to continue using the old method of simply having the folders in the weblayout\resources structure without the need for a component.
To update the configuration settings, go to Administration -> Admin Server. Then click on the button for the instance and go to General Configuration. Add the two configuration entries to the Additional Configuration Variables at the bottom and hit save. Then restart the instance.
For more information on modifying the interface, check out the Create and Modify Layout Sample Component.