MCS configuration elements

Compatibility options for the page adaptation process.

The email address of the sender or recipient of the log report.

Creates an anonymous data source from a password protected one. An anonymous data source does not need to be provided with the user name and password in order to connect to the database. A password protected data source must be supplied with a user name and password in order to connect to the database.

Defines applications related to MCS.

Arguments specified as name-value pairs.

Several elements containing default URL values are defined in the assets section of the mcs-config.xsd file. For convenience they are grouped here rather than under individual element names.

Project specific configuration relating to assets.

Defines cache values.

Container for pipeline cache definitions.

Specifies the directory used by MCS for generated chart information.

Identifies a resource that can be found on the class path.

The Client Framework 2 compatibility options.

Security configuration for defining how to encrypt the data that is sent to the server and back to the client. MCS uses a password based encryption mechanism to create a key that is used to both encrypt and decrypt any data that is intended to sent to the server and back to and from the client.

Container for email configuration.

Defines default settings for all remote connections made by pipeline processes. The timeout attribute contains the default value for the following processes.

Creates a pooled connection pool from an anonymous unpooled data source.

Contains configuration options that allow MCS to retain backward compatibility. Many of these options can be overridden for a specific XDIME page using meta properties. Please note that those options that can select deprecated behavior are temporary and will be removed when the deprecated behavior is removed.

Specifies the location of the custom device repository policies.

Container for multiple named datasource definitions.

Enables generation of XDIME comments in rendered pages, and output of rendered pages to the log file.

Defines a directory to contain the pipeline debug output that is specified in the pipeline:serialize element.

Required container for default project information.

Container for device repository definitions.

Container for email information.

Enables or disables email report production. The content is restricted to the values 'enable' and 'disable'. Disabling email does not stop logging.

Prevents MCS from handling responses to requests from one or more devices defined in the servlet-filter section of the mcs-config.xml file. If the device has children in the device tree, all the children are excluded as well as the named device. Excluded requests are passed through.

MCS will generate external style sheets where possible when this element is present. Some protocol/device combinations may not allow this, in which case the style sheet will be generated inline within the page.

Defines an external repository used for holding information about users and their preferences.

The file location of the device policies.

Defines the pipeline configuration for rendering scripts in HTTP sources.

Address details of the sender of the log report.

Defines a project-specific prefix for the chartimages element entry. MCS appends the base-dir value to the web-application element's base-url and page-base attributes, and follows it with the setting in chartimages element's base attribute.

The URI of the SMTP server.

Defines the starting context for resolving JNDI names. The contained parameters element can be used if a particular directory service needs initialization values to be passed to it.

Container for the initialization arguments passed to the initialize method of the plugin class.

Enables a secondary MCS repository.

If this element is present in releases prior to MCS 3.5, MCS will cache internal style sheets in memory using the values in the contained cache element.

Defines part of an internal MCS repository used for information about users and their preferences.

Allows a JDBC driver to be used as a datasource.

Indicates that the project's policies are stored in a JDBC database.

Specifies that the MCS repository is a JDBC repository. The name of the repository is defined in the jdbc-policies element.

Refers to the project containing the device information in a JDBC datasource. This is the same datasource as the one defined in the local-repository element.

Contains the definition of a configuration of one or more JNDI datasources.

Allows a data source to be retrieved from a JNDI service.

Specifies that MCS will register its MBeans with the specified JNDI resource. This element should be used when MCS is deployed on the application server that allows arbitrary objects to be stored in JNDI. This element is mutually exclusive with platform-mbean-server.

Controls the use and behavior of JSP pages.

Container for a list of libraries.

A reference to a library.

Defines the MCS repository to be used.

Contains a reference to the file MCS uses for logging configuration.

Contains the URI of the device log file. If no name is provided, a log file will be created automatically in the same directory as MCS or DRWS configuration file.

Container for logging information for devices that are not known to the device repository.

Container for management information definitions.

Defines a single custom pipeline markup extension that can contain either a process or a rule element.

Container for all custom pipeline markup definitions. This single element may contain multiple markup-extension elements.

Markup plugins are custom Java classes using the com.volantis.mcs.integration.MarkupPlugin interface.

Defines the location the Media Access Proxy web application.

Configures the MCS Server Manager.

The root element of the MCS configuration file. The contained elements follow the xs:all content model, so they may appear once only. The top-level elements local-repository, devices, and projects are required.

Allows access to a database type that is known to MCS.

Container for MCS plugin definitions.

Enables multipart MIME packaging.

Defines one or more MIME types to be matched in an HTTP response by the Servlet Filter. XDIME content is processed by MCS. Excluded content is passed through.

Specifies the directory used by MCS for generated modeset information.

Identifies a script module.

Specifies whether the protocols should pool objects.

Defines the global default page cache setting. Authors may override the default value with an alternative scope value on individual pages, using the cacheScope attribute on the canvas element.

Text added as comments to pages generated by MCS, provided that the output protocol supports comments.

Container for packaging definitions.

The optional password used for the SMTP service.

The reporting interval of the report. Possible values are 'day', 'week' (default), 'month', 'quarter', 'year'.

Container for pipeline configuration elements.

Specifies that MCS will register its MBeans into the platform MBean server. This element should be used when MCS is deployed on the application server that exports a fixed set of MBean servers through JNDI. This element is mutually exclusive with jndi-mbean-server.

Defines the names of custom Java classes that implement plugin interfaces.

Controls the caching of policies in the MCS application.

The optional port number of the SMTP server.

Defines the class that implements a custom pipeline process.

Optional container for project information. If you set the preload attribute to true for a remote-policies element, you must also provide a URL in the associated preload element.

Container for project information. A default project is required. In custom configurations of MCS there may be one or more optional project definitions.

Container for configuration information that applies to specific protocols.

Defines the settings for a proxy server.

Container for remote policy values.

Defines the cache quota for a particular remote server and the policy cache of the containing cache quota type.

Container for the policy quota elements for one or more remote servers.

Defines the rule to be associated with custom pipeline markup.

Defines the pipeline configuration for scripts in HTTP sources.

Specifies the directory used by MCS for generated script information.

Specifies a secondary MCS repository. Policies and variants can be created from external sources at runtime by calling the com.volantis.mcs.imdapi interface from a JSP.

Contains security-related configuration.

Optional container for values that filter XDIME content. The filter identifies device requests that are to be excluded from MCS processing, and ensures that MCS handles only responses with XDIME content.

Identifies a resource that can be found within a servlet context.

Contains SMTP server configuration elements.

Contains the SQL datasource definitions for pipeline operations.

Specifies the location of the standard device repository policies.

Controls the caching of generated stylesheets.

The subject of the email report.

Address details of the recipient of the log report.

Enables page-tracking features.

Configures DCI transform operations.

Identifies a resource by a URI.

The optional username used for the SMTP service.

Enables additional plugins to the repository that hold information about users and their preferences.

Configures MCS with a web application server.

Contains the proxy server and script reference definitions for the pipeline web driver.

Contains web service definitions for the pipeline web services driver.

Defines WML configuration in cases where the XDIME nativemarkup element is being rendered for WML.

Specifies alternative locations for WSDL documents.

Defines a web service. The contained elements point to alternative locations for the resource.

Configuration related to XDIME elements and processing thereof.

Specifies compatibility options for styling XDIME 2 pages.

Indicates that the project's policies are stored as XML.

Specifies that the MCS repository is an XML repository. The location of the repository is defined in the xml-policies element.