Customizing configuration files

The default configuration files used for a server, and also for the launchpad server used to generate it's files, can be overridden by creating alternate launchpad-specific template files.

For a server that will be deployed from the Controller, the config files are copied as follows:

        /Controller/custom-config-files/p_tooltwist.conf-phil_tmp
            --> ~servername/server/tooltwist.conf

        /Controller/custom-config-files/p_wdb.conf
            --> ~servername/server/files/webdesign/config/wbd/wbd.conf

        /Controller/custom-config-files/p_web.xml
            --> ~servername/server/tomcat/webapps/ttsvr/WEB-INF/web.xml

Similar files can be used to override the config files for the launchpad. These might be needed to rectify errors while generating the CI web pages:

        /Controller/custom-config-files/p_tooltwist.conf-phil_tmp
            --> /Controller/launchpads/phil_tmp/image/tooltwist.conf

        /Controller/custom-config-files/p_wdb.conf
            --> /Controller/launchpads/phil_tmp/image/files/webdesign/config/wbd/wbd.conf

        /Controller/custom-config-files/p_web.xml
            --> /Controller/launchpads/phil_tmp/image/tomcat/webapps/ttsvr/WEB-INF/web.xml)

These files all provide some variable substitution, and are best copied initially from the directory named /Controller/custom-config-files/examples.

Commonly, these files are modifed for these purposes:

        web.xml - to define servlets
        tooltwist.conf - to define database connection URLs, and to define technology layers
        wbd.conf - to define application specific parameters, and parameters for the ToolTwist Designer.