When WOW first starts, it reads a number of init parameters which contain initialization data. These init parameters are stored in the file system on the server which is running WOW, not in the database. Here we will describe the different ways WOW’s init parameters can be configured and some more information about init parameters.

Init parameter syntax

When an init parameter is set in the web.xml file, it needs to be set using the init parameter XML syntax defined by Java's servlet specification. For example this XML sets the "wow.metadata.schema.system" init parameter to "PJSYS75"

<init-param id="WOW_Metadata_Library">

<param-name>wow.metadata.schema.system</param-name>

<param-value>PJSYS75</param-value>

</init-param>

When an init parameter is set in a property file, it should use Java's property file syntax. For example, this text (on its own line) sets the "wow.metadata.schema.system" init parameter to "PJSYS75"

wow.metadata.schema.system = PJSYS75

Init parameters

These are some of the init parameters used by WOW

• • wow.connection.url - The JDBC URL of system containing the WOW metadata

  • wow.connection.user - User ID used to sign onto the DB containing WOW metadata

  • wow.connection.password - Password used to sign onto the DB containing WOW metadata

  • wow.connection.jdbcdriver - JDBC driver class used to sign onto the DB containing WOW metadata

  • wow.metadata.schema.system - Name of schema/library which contains WOW system metadata

  • wow.metadata.schema.project.default - Name of schema/library which contains WOW user/project metadata.

• wow.replacement.schemas - List of WOW replacement schemas. Format is: oldSchema1=newSchema1,oldSchema2=newSchema2

Location of init parameters

There are a number of locations which WOW can read its init parameters from. In the simplest cases, all init parameters can be read from a single file. In more complex deployments, WOW may read init parameters from several different files.

The exact files which WOW will read its init parameters from can depend on the servlet context running WOW, and/or the WOW Environment Mode. This allows two different WOW deployments to use identical .war files, but read init parameters from different files within the .war file (and therefore use different init parameters).

The list below is an example of all possible different files which WOW could check for an init parameter (not all of these files need to be present in a single deployment; they are an illustration of all possible file locations). The list is ordered from the highest precedence to lowest, meaning if the same init parameter was defined in multiple files then the value from the lowest numbered file would be used. The file names in parentheses are the file names which would be used if the WOW environment were set to TEST and if WOW were deployed to the "wow75" context. If WOW were deployed to a different context or if WOW were running in a different environment mode then the specific file names would be different.

• 1. web.xml (/webapps/wow75/WEB-INF/web.xml)

  2. Environment and context specific property file (/webapps/wow75/WEB-INF/wowconf/wow75/TEST_wow.properties)

  3. Environment specific property file (/webapps/wow75/WEB-INF/wowconf/TEST_wow.properties)

  4. Context specific property file (/webapps/wow75/WEB-INF/wowconf/wow75/wow.properties)

  5. Non-specific property file (/webapps/wow75/WEB-INF/wowconf/wow.properties)

1. Shared property file (/webapps/wow.properties)

For example, if these files were defined:

File /webapps/wow75/WEB-INF/wowconf/wow75/wow.properties

wow.metadata.schema.system = PJSYS70

wow.metadata.schema.project.default = WOW_CE

wow.connection.user = root

File /webapps/wow75/WEB-INF/wowconf/TEST_wow.properties

wow.metadata.schema.system = PJSYS71

wow.metadata.schema.project.default = WOW_CE_2

File /webapps/wow75/WEB-INF/wowconf/PROD_wow.properties

wow.metadata.schema.project.default = WOW_CE_3

(Assume none of the above init parameters are located in any other configuration files.)

When WOW is running in the TEST environment mode, the values used would be PJSYS71 for the metadata library, WOW_CE_2 for the user metadata library, and root for the metadata user id.

If the environment mode were PROD, then the values used would be PJSYS70 for the metadata library, WOW_CE_3 for the user metadata library, and root for the metadata user id.

Any other environment mode would use PJSYS70 for the metadata library, WOW_CE for the user metadata library, and root for the metadata user id.

Viewing init parameters

From the WOW Builder, you can view the init parameters which WOW is using. Choose the “View Init Parameters” menu item from the “Development Tools” menu.