The Stardust runtime engine is configured by a set of parameters. Those parameters can be specified in several ways, depending on the operating mode.
When operating in Spring local mode (direct connection of the client with the database), the runtime properties are obtained from two distinct places: carnot.properties and the Java system properties. Stardust runtime is always searching for the carnot.properties file in the JVM classpath. The Java system properties can be specified using the -D option of the Java virtual machine.
When operating inside an application server, in addition to the
previous configuration mechanisms, the Stardust runtime is using the EJB
or the Web environment to get the necessary properties. In the current
implementation, the EJB/Web environment has precedence over the
properties specified in carnot.properties or system properties.
The EJB environment is specified in the deployment descriptors of the
Stardust Enterprise Beans or in the deployment descriptor (web.xml)
of your Web application. You can manually edit the descriptors, which
are located in the
The client configuration always uses carnot.properties and the Java system properties.
The client side properties are used for enabling the Stardust client tools. They include in the first instance parameters for security, audit trail, JNDI, license and logging settings. For instance security parameters entail authenticating the client on the server side. These properties reside in the carnot.properties file, which is by default located in the /etc folder of your work directory, but the user can specify alternative search locations.
side properties have to be available in the Stardust runtime
environment. They include among others parameters for security, audit
trail, concurrency and daemon settings. The server side carnot.properties
file is located in the root directory of the