Another controversy: Where to store common application parameters?

Question

For higher flexibility, application parameters are usually set. For intranet applications, I used to store these parameters with my Oracle database. Now I'm developing a web-based internet applications, would you please advise for the following questions:
1) The place to store common application parameters (How to set and how to retrieve?)
(Currently, I have put such application parameters into a class file. Although it should be faster than retrieval from database, it means that I need to re-compile in case of any changes are made for those parameters. Can I set up some global constant for my application with my JDeveloper? How to set and how to retrieve?).
2) The place to store the application configuration and application package string
(As you see, if you have many Jsp page, it's not convenient to change the <jbo:ApplicationModule ... Configuration="MyConfig"... /> all the time. It may be better if it could be generalized by a variable. I have found the configuration in the "web.xml" file, but i don't know how to retrieve the value from it. Currently, I have made use of my old approach mentioned in Question 1 - place the configuration string in a common class ... the drawback has already been mentioned as above ... any better solutions?)
Thanks for replying!

Answer 1

Curt,
To create an AM using the definition in the cpx file:
   JUApplication app = JUMetaObjectManager.createApplicationObject("Project2.am");
   ApplicationModule am = app.getApplicationModule();.
This is the same call used by JClient application.
Here is the story with BC4J runtime params:
jbo.default.language
This parameter is used in localization.
jbo.default.country
This parameter is used in localization.
DeployPlatform
The platform on which the business components are deployed:
LOCAL - The web module of Oracle 9iAS
EJB_IAS - The EJB module or Oracle 9iAS
VB - A VisiBroker CORBA server
WLS - a WebLogic application server
Connection Mode
For business components deployed to VisiBroker, the connection
mode used:
1 - colocate mode
2 - remote mode
3 - IOR mode
4 - bind mode
For more information, see the VisiBroker documentation.
HostName
For all deployment platforms except LOCAL, the name of the
application server hosting the business components.
ConnectionPort
For all deployment platforms except LOCAL, the port of the
application server hosting the business components.
ApplicationPath
For all deployment platforms except LOCAL, the JNDI path to the
business components.
java.naming.security.principal
For all deployment platforms except LOCAL, the username for the
IIOP connection to the business components.
jbo.use.pers.coll
Setting this to true enables view row spillover. If you are working
with large rowsets and memory is a problem, this property should be
true. For more information, see the Oracle JDeveloper documentation.
jbo.pers.max.rows.per.node
The maximum size of a node for view row spillover.
jbo.pers.max.active.nodes
The maximum number of nodes that will be cached in memory for view
row spillover.
jbo.fetch.mode
AS.NEEDED causes view objects to only fetch rows when they are
requested. ALL causes them to fetch the entire results of their
queries.
MetaObjectContextFactory
The default value uses the business components framework's
MetaObjectContext Factory, which stores business components metadata
in XML. If you want to use a different format for business components
metadata, you can implement your own MetaObjectContext Factory.
IsLazyLoadingTrue
For all deployment platofrms except LOCAL, setting this property to
true will cause business componetns metadata to be loaded into memory
only as needed, whereas setting it to false will cause all metadata
to be loaded into memory immediately. Lazy loading is mandatory in
LOCAL mode.
Factory-Substitution-List
The list of business components to substitute out. See the Oracle
JDeveloper documentation for more information on substituting
business components.
jbo.project
The project containing business components to be substituted for old
ones, if Factory-Substitution-List is not empty.
jbo.max.cursors
The maximum number of cursors the business components may have open.
The framework will clean up free JDBC statements as the number of
cursors approaches this number.
do.failover
This property is true if application module failover is enabled.
Setting this property to false provides better performance at the
expense of reliability.
jbo.doconnectionpooling
This property is true if application modules are allowed to share
connections. For more information about connection pooling, see the
Oracle JDeveloper documentation.
jbo.recyclethreshold
The recycle threshold for application module pooling. When the number
of application modules in the pool reaches this level, the pool
begins to recycle application modules in stateful mode. Monitoring
the application module pool statistics may help you decide on a good
value for this field.
jbo.ampool.highwatermark
The maximum number of application modules allowed in the pool. If
this high-water mark is reached, clients must wait for the next
available application module.
jbo.ampool.resetnontransactionalstate
If this property is false, application modules will preserve their
non-transactional state (properties and dynamically added view
object, view link, and nested application module members) even when
they are checked in in stateless mode. If the property is true,
non-transactional state will be reset.
jbo.ampool.sessioncookiefactoryclass
This class creates the session cookies that allow clients to retrieve
application modules in stateful mode. Change this value only if you
need to implement your own custom session cookie factory. See the
Oracle JDeveloper documentation for more information.
jbo.ampool.connectionstrategyclass
This class manages the connection strategy for the application module
pool. Change this value only if you need to implement your own custom
connection strategy. See the Oracle JDeveloper documentation for
more information.
jbo.passivationstore
When an application module is released in stateful mode, its state is
saved when the application module is recycled (or immediately if
failover is enabled). If this property is 'null' or 'database', the
state is saved to the database. If the property is 'file', the state
is saved to a local file.
RELEASE_MODE
The release mode--Stateless, Stateful, or Reserved--used by data web
beans. Other clients specify their own release mode.
jbo.maxpoolcookieage
The maximum age of the browser cookies used to help clients retrieve
stateful application modules. If these cookies do not time out, the
value is -1.
PoolClassName
The class that implements the application module pool. Do not change
this value unless you are using a custom application module pool
implementation. For more information, see the Oracle JDeveloper
documentation.
jbo.maxpoolsize
The maximum size of the JDBC connection pool. If this number is
exceeded, an application module will have to wait for a connection if
none is available.
jbo.initpoolsize
The number of JDBC connections automatically created in the
connection pool, before any requests.
jbo.poolrequesttimeout
The amount of time, in milliseconds, an application module will wait
for an available connection before failing.
jbo.assoc.consistent
If this property is true, the entity rowsets retrieved through
association accessors will include rows that have been added, even if
these changes have not been posted to the database. This property can
reduce performance and so should be turned off if not needed.
jbo.viewlink.consistent
If this property is true, the view object rowsets retrieved through
view link accessors will include rows that have been added, even if
these changes have not been posted to the database. This property can
reduce performance and so should be turned off if not needed.
jbo.SQLBuilder
The SQL flavor generated by view objects:
Oracle - for the Oracle8i or Oracle9i database
OLite - for the Oracle Lite database
SQL92 - for any SQL92-compliant database
DB2 - IBM DB2 Universal Database
jbo.ConnectionPoolManager
The class that manges the connection pool. Do not change this value
unless you are using a custom application module pool manager
implementation. For more information, see the Oracle JDeveloper
documentation.
jbo.TypeMapEntries
The type mappings used by business components:
Oracle - for the Oracle8i or Oracle9i database
OLite - for the Oracle Lite database
SQL92 - for any SQL92-compliant database
oracle.jbo.defineColumnLength
If this is false, business components will not by default define
column length for CHAR and VARCHAR2 columns. In general, this should
only be set to false for NLS applications.
jbo.tmpdir
You can use this parameter to specify a directory for temporary files.
jbo.server.internal-connection
Specifies a connection to use when application module state is saved
to the database. By default, the application module pool will use the
application module's JDBC connection.
SessionClass
The class which implements the oracle.jbo.Session interface, used to
load and store session context throughout a client's lifetime. By
default, the framework uses oracle.jbo.server.SessionImpl. Do not
change this value unless you have implemented a custom session
implementation class.
TransactionFactory
The class responsible for creating database transactions. By default,
the framework uses oracle.jbo.server.DatabaseTransactionFactory. Do
not change this value unless you have implemented a custom
transaction factory class.
jbo.debugoutput
If this property is set to 'console', debug information is displayed
on the console. If the property is set to 'silent', debug information
is not displayed.
jbo.logging.show.timing
Whether to show the time elapsed between debug calls.
jbo.logging.show.function
Whether to show the name of the method that triggered a debugger
call. Setting this property to true will degrade performance.
jbo.logging.show.level
Show the trace level of debugger messages. The lower the trace level,
the more important the message.
jbo.logging.show.linecount
Number the lines of debugger output.
jbo.logging.trace.threshold
Lower this number to display only the most important debugger
messages; raise it to display a larger portion of debugger messages.
jbo.jdbc.driver.verbose
If this property is true, the JDBC driver will run in verbose mode.
For more information, see the JDBC documentation.
jbo.ejb.txn.timeout
For EJB deployment configurations, the number of seconds after the
last database access before the EJB transaction expires.
jbo.ejb.txntype
For EJB deployment configurations, the transaction type:
global - use the JTA UserTransaction interface
local - use straight JDBC
jbo.xml.validation
If true, the XML parser uses strict XML validation.
Charles.