Server configuration files

Since a few people asked me this question already, I thought I'd just blog the answer. Curam uses the following configuration files.

• Application.prx
• Bootstrap.properties
• AppServer.properties
• .bindings

Application.prx Contains settings that are changable during runtime. Bootstrap.properties Contains settings that are required to run the server in development mode. AppServer.properties Contains settings used by the build scripts which deal with the application server and is used for initial configuration of the application server, deploys and server startup and shutdown. Although it is not documented in the Documention Center (or at least I couldn't find it), you can add all the properties that you need to deal with in that file (e.g. ear.file, server.name). This saves you a bit of typing since you do not need to specify those values in the command line any more. Also Curam allows you to have an alternate property file loaded so you can specify a different AppServer.properties for different environments. .bindings This is not really a settings file, but it does contain settings. This is only used in the development environment and not the deployed application. In a deployed application you have JNDI's default InitialContext which contains all the server resources such as the database, JMS queues, etc. all configured. However, in development you do not have such an InitialContext. So what Curam does is it uses the fscontext which is an implementation of the JNDI Context that stores the data in the file system. That file is the .bindings file. The path to the .bindings file is actually put in BootStrap.properties as curam.environment.bindings.location. One other note, this file is updated while the server is running, so make sure it is not version controlled. What I do is create a Sample.bindings file which I store in version control and copy it over to .bindings.