Retrieving the Configuration Parameters
The ACL Application Arbortext PE can call the following routines to retrieve the names and values of the configuration parameters maintained by the Sous-processus Arbortext PE Application Context.
Table 7. ACL Functions for Obtaining Configuration Parameters
Function
Purpose
PEAppConfig::addIntermediateFile( fileName, contentType, description )
copies the file whose absolute path is provided by the fileName parameter into the transaction directory as an intermediate file. The contentType and description parameters are included as comments.
PEAppConfig :: getInitParameter( name )
Returns the value of parameter name or the null string if there is no such parameter.
PEAppConfig :: getInitParameterNames( names[] )
Places the name of each defined parameter in the ACL array names and returns the number of parameters defined.
PEAppConfig::debug( message )
Places messages in the servlet log if the application log level is set to display messages of this severity.
PEAppConfig::error( message )
Places messages in the servlet log if the application log level is set to display messages of this severity.
PEAppConfig::fatal( message )
Places messages in the servlet log if the application log level is set to display messages of this severity.
PEAppConfig::info( message )
Places messages in the servlet log if the application log level is set to display messages of this severity.
PEAppConfig::trace( message )
Places messages in the servlet log if the application log level is set to display messages of this severity.
PEAppConfig::isDebugEnabled()
Returns1 if the specified log level is enabled, 0 if it’s not.
PEAppConfig::isInfoEnabled()
Returns1 if the specified log level is enabled, 0 if it’s not.
PEAppConfig::.isTraceEnabled()
Returns1 if the specified log level is enabled, 0 if it’s not.
Est-ce que cela a été utile ?