Configuration reference

# portofino-custom.properties
#
# This file contains the documentation of the configuration
# properties for ManyDesigsn Portofino 2.0.x
# All properties are listed, together with their default values.
#
# To override the default values you must create a
# portofino-custom.properties
# file and save it in your classpath.
# Typical locations are:
# $TOMCAT_HOME/common/classes
# $PORTOFINO_HOME/WEB-INF/classes
#
# The former location is the preferred choice because it keeps
# the property file separate from the software installation,
# which makes software upgrades easier.
#
# The latter location must be used when multiple instances of Portofino
# run inside a single application server to avoid conflicts between
# the instances.

#---------------------------------
# Database configuration

# Specify database configuration type of 'jdbc' or 'jndi'
database.configurationType=jdbc

# For database configuration type of 'jdbc', these will be used
database.jdbc.driverClass=
database.jdbc.connectionURL=
database.jdbc.username=
database.jdbc.password=

# For database configuration type 'jndi', this will be used
database.jndi.name=jdbc/portofinodb

#----------------------------------
# Mail configuration

# SMTP server for sending notifications
mail.smtp=

#----------------------------------
# Versioning

# The name of the cvs command
versioning.cvs.command=cvs

# The absolute location of the cvs repository
versioning.cvs.repository=

# The absolute location of the cvs working directory
# where modules will be check out
versioning.cvs.workingDirectory=

# The absolute location of mdtemplate-XX-.sql file 
versioning.template.location=

#---------------------------------
# Model configuration
# Portofino uses two levels of modeling (model and meta-model)
# where meta-model provides the metadata for the level below.
# Here we start by defining the lowest level (model),
# which represents the "downstairs" application.

# The name of your application
model.application.name=My Application

# The name of the cvs module for versioning purposes
model.cvs.module=

# The schema that contains the application data
model.schema=model

# Is user management enabled?
# Set to false if you want an system where users do not have
# to login and all permissions are granted to everybody (use with care)
# Set to true if you want user management and permissions to be enforced.
# This setting will fall back to false if the system cannot find
# the required classes (User, UserGrp, User_UserGrp) for user management.
model.users.enabled=false

# Are anonymous users allowed? If set to false, anonymous users
# will be redirected to the login page.
model.users.anonymous.enabled=true

# The email account that appears as the sender of workflow notifications
model.workflow.notifications.sender=

# The locale language
model.locale.language=en

# The locale stylesheet
model.stylesheet=default.css

# The locale date format
model.locale.dateformat=dd-MM-yyyy

#---------------------------------
# Meta-model configuration
# These setting affect the "upstairs" application, i.e., the
# development environment.

# Is the "upstairs" application enabled? Set this to false to disable
# modeling and hide the "go upstairs" link.
# Usually set to true in development, to false in production.
meta.enabled=true

# The schema that contains the application's metadata
meta.schema=meta

# Is user management enabled?
# "Upstairs" user management is completely independent (regarding
# users and settings) from "downstairs" user management.
meta.users.enabled=false

# Are anonymous users allowed?
meta.users.anonymous.enabled=true

# The locale language
meta.locale.language=en

# The locale stylesheet
meta.stylesheet=upstairs.css

# The locale date format
meta.locale.dateformat=dd-MM-yyyy
#---------------------------------
# Security configuration

# The security type:
# 'application' for application-manged security and local authentication
# 'container' for contained managed authentication (LDAP, single sign-on)
security.type=application