Version number for schema that defines this container configuration.

Identifier of container service instance.

In case the container installation is shared between multiple configurations, as allowed by the start scripts. Each configuration must have a container service with an identifier that is unique within the context of the installed container.

Time in seconds the configuration files are checked to see whether they have been updated by external means.

Checking the configuration file for updates by external means can be disabled by setting the poll time to 0 seconds.

URI to root of the location the container will install the service definitions and that can be used to place SAR files in that needs to installed when Seven starts.

The URI has to be a file URI, or in case no scheme is provided a file system path is assumed. In case of a relative filepath the directory the configuration file is in is consider the root directory for resolving purposes.	

URI to the root of the location the container will store log files for the service instances.

The URI has to be a file URI, or in case no scheme is provided a file system path is assumed. In case of a relative filepath the directory the configuration file is in is consider the root directory for resolving purposes.	

URI to the root of the location the container will write the runtime data for the service instances.

The URI has to be a file URI, or in case no scheme is provided a file system path is assumed. In case of a relative filepath the directory the configuration file is in is consider the root directory for resolving purposes.	

Platform API expected to be available at clients using services deployed by the container.

Controls the security level used when grants are configured by the XML configuration plugin when new service group definitions and service instances are created.

This attribute doesn't control inherent security of the container, only the default values for the configuration elements created by the plugin.

Controls whether a cryptographically strong pseudo-random number generator will be used for creating unique IDs.

The main reason to set this attribute to false is to minimize startup times for development purposes in case the OS doesn't have a random device.

Time in seconds the container is willing to wait to let the shutdown sequence finish in case of a container destroy.

In case the shutdown sequence hasn't finished within time a forced JVM exit will take place.

Absolute URI prefix used for the codebase annotation URL when marshalling objects and when not overridden at another level.

The service specific part will be added to the prefix provided. If the prefix doesn't end with a path separator the container will add one before adding the service specific part.

If not specified the codebase annotation will be based on the data provided for the configured JAR file server, if any.

Protocol used in codebase annotation when marshalling objects.

Setting this value to httpmd enables JAR file integrity verification to be performed by the receiving party. When the codebase-uri-prefix is set this attribute will enable httpmd for codebase annotations when the scheme of the codebase-uri-prefix equals 'http'.

Name of message digest algorithm used for calculating of a message digest for the download JAR files.

The default algorithm being used in case of httpmd is SHA-1. The container will support all algorithms listed in the Java Cryptography Architecture API Specification and Reference, others can be obtained by installing the right crypto plugins for your J2SE platform.

Note: algorithm names are not case-sensitive.

Language used for content, defaults to 'en' (English).

Identifier refering to element this is a help message for.

Unique identifier for the connector definition, can be used as ID for help messages.

Port number the JAR file server will accept incomming request on, if the port number is '0' the container will use a free random port number.

Note that a random port number won't provide durable codebase annotations, i.e. download JAR files won't be accessible after a restart of the container. You are advised to pick a fixed and free port number for long lived deployments.

Host name, or IPv4/IPv6 number, for the codebase annotation URL to be used when marshalling classes and when not overridden at another level.

If not specified the container will determine the 'primary' IP number in textual representation (IPv4 or IPv6) for the host and use that for the codebase annotation URL. It is wise to provide here a DNS alias, as this would ease building security policies for Java clients that needs to connect to this JAR file server and for non LAN environments.

Port number to use in the codebase annotation URL to be used when marshalling classes.

If not specified the container will use the port number the JAR file server has been bound to. This option can be used in case JAR file serving must be performed by a proxy web server that proxies to the internal JAR file server.

Name for this logger, if not specified it will serve as the root logger within the context this logger is being used.

Minimum log level this logger should take care of.

In case no level is specified the level of the logger must be inherited from its nearest ancestor with a specific (non-null) log level.

Indicates whether this logger should send its output to it's parent logger.

Indicates whether the log record tested must match all optional filters, or that it has to match only one filter.

The default is to match any optional filter.

Indicates whether the logger accepts forwarded log records from a forward handler or is protected.

True doesn't allow for forwarding from a forward handler in another namespace, only allows forwarding from within the same namespace. False does allow for forwarding from another namespace.

Indicates whether the connector is durable, meaning that even after restarts of the service clients that have a reference are able to talk to that service.

This attribute only has a meaning effect when the port number is fixed, or in general when existing endpoints will be able to connect to the server endpoint when the service restarts.

Indicates whether to verify if proxies are trusted.

Controls the version of the multicast request and unicast discovery protocol used, if not specified the protocol version used will depend on whether there are any required or preferred constraints specified.

Setting the protocol version is only recommended in case the lookup services to contact don't support particular versions of the discovery protocol, otherwise the most efficient protocol will be selected.

The host name to include in multicast requests if participating in version 2 of the multicast request protocol.

The time to live (TTL) value set on outgoing multicast request packets.

The read timeout in milliseconds set on sockets over which unicast discovery is performed.

The connection timeout in milliseconds set on sockets over which unicast discovery is performed.

Unique identifier for the connector definition, can be used as ID for help messages.

Refers to the OID of the JSC deployment descriptor.

Version number for schema that defines the JSC unit configuration.

Identifier of service group, must be unique within context of JSC unit.

Identifier of security domain the service group is associated with.

Version number of service group definition this service group is associated with.

If this attribute is not specified this latest version will be determined at start-up time and written to file.

Protocol used in codebase annotation when marshalling objects.

Setting this value to httpmd enables JAR file verification to be performed by the receiving party.

Name of message digest algorithm used for calculating of a message digest for the download JAR files.

The default algorithm being used in case of httpmd is SHA-1. The container will support all algorithms listed in the Java Cryptography Architecture API Specification and Reference, others can be obtained by installing the right crypto plugins for your J2SE platform.

Note: algorithm names are not case-sensitive.

Unique identifier for the connector definition, can be used as ID for help messages.

Indicates whether this configuration is disabled, i.e. is not taken into account for the aggregated configuration.

Indicates whether this configuration is disabled, i.e. is not taken into account for the aggregated configuration.

Indicates whether the connector is durable, meaning that even after restarts of the service clients that have a reference are able to talk to that service.

This attribute only has a meaning effect when the port number is fixed, or in general when existing endpoints will be able to connect to the server endpoint when the service restarts.

Host name, or IPv4/IPv6 number, for the service proxy to use for setting up a socket connection.

If not specified the container will determine the 'primary' IP number in textual representation (IPv4 or IPv6) for the host and use that for establishing a client-server connection. It is wise to provide here a DNS alias, as this would ease building security policies for Java clients that needs to connect to the service dispatcher and for non LAN environments.

Port number the connector will listen on for inbound requests, if the port number is '0' the container will use a free random port number.

If set a custom server socket factory will be part of the ServerEndpoint that controls whether the socket created is based on NIO or is a blocking type. If this attribute is not set the type of socket created will depend on the seven.jeri.nio system property.

If true a NIO based socket will be created by the server socket factory, if set to false a blocking socket will be created.

If set a custom socket factory will be part of the Endpoint that controls whether the socket created is based on NIO or is a blocking type. If this attribute is not set the type of socket created will depend on the implementation/configuration of the Jini Platform of the client.

If true a NIO based socket will be created by the server socket factory, if set to false a blocking socket will be created. In most cases one should not specify this attribute.

Host name, or IPv4/IPv6 number, for the service proxy to use for setting up a socket connection.

If not specified the container will determine the 'primary' IP number in textual representation (IPv4 or IPv6) for the host and use that for establishing a client-server connection. It is wise to provide here a DNS alias, as this would ease building security policies for Java clients that needs to connect to the service dispatcher and for non LAN environments.

Port number the connector will listen on for inbound requests, if the port number is '0' the container will use a free random port number.

Absolute URI used for the Endpoint to connect back to the server, setting this attribute will override host:port combination derived from the inbound-host and port attribute.

The scheme of the absolute URI must be 'http', if the URI contains a path the HttpRequestUriEndpoint will be used.

If set a custom server socket factory will be part of the ServerEndpoint that controls whether the socket created is based on NIO or is a blocking type. If this attribute is not set the type of socket created will depend on the seven.jeri.nio system property.

If true a NIO based socket will be created by the server socket factory, if set to false a blocking socket will be created.

If set a custom socket factory will be part of the Endpoint that controls whether the socket created is based on NIO or is a blocking type. If this attribute is not set the type of socket created will depend on the implementation/configuration of the Jini Platform of the client.

If true a NIO based socket will be created by the server socket factory, if set to false a blocking socket will be created. In most cases one should not specify this attribute.

Sets the level specifying which messages will be logged, messages lower than this level will be ignored.

By setting the level to OFF the handler can be disabled, by setting the level to ALL every message will be logged.

Sets the character encoding to be used.

If not specified the default character encoding of the platform will be used.

Formatter used for formatting the log records, supported are simple, plain and xml.

Some handlers may however ignore this settings, because they have a fixed log format, e.g. syslog.

Indicates whether context information should be displayed when it is available.

The context information is the OID of the service group definition and the identifier of the service group in which the entity performed the logging.

If enabled protects this handler from log flooding. Only the first log event will be published, and a summary for the repetition events.

Currently only log flooding is detected for events one frame deep.

Indicates whether the log record tested must match all optional filters, or that it has to match only one filter.

The default is to match any optional filter.

Indicates whether the result of the expression represented by this filter must be negated.

Unique OID (Object Identifier) for the service group definition to apply the filter to.
						

Optional identifier of service group to apply the filter to, in case filtering at the service level is required use the instance-id attribute.

If the instance-id attribute is set this attribute will be ignored, as the combination of the OID with the instance-id uniquely identifies a service instance.

Optional identifier of service instance identifier to apply the filter to.

Controls the version of the multicast request and unicast discovery protocol used, if not specified the protocol version used will depend on whether there are any required or preferred constraints specified.

Setting the protocol version is only recommended in case the lookup services to contact don't support particular versions of the discovery protocol, otherwise the most efficient protocol will be selected.

The host name to include in multicast requests if participating in version 2 of the multicast request protocol.

The time to live (TTL) value set on outgoing multicast request packets.

The read timeout in milliseconds set on sockets over which unicast discovery is performed.

The connection timeout in milliseconds set on sockets over which unicast discovery is performed.

Indicates whether to verify if proxies are trusted.

Sets the level specifying which messages will be logged, messages lower than this level will be ignored.

By setting the level to OFF the handler can be disabled, by setting the level to ALL every message will be logged.

Sets the character encoding to be used.

If not specified the default character encoding of the platform will be used.

Formatter used for formatting the log records, supported are simple, plain and xml.

Some handlers may however ignore this settings, because they have a fixed log format, e.g. syslog.

Indicates whether context information should be displayed when it is available.

The context information is the OID of the service group definition and the identifier of the service group in which the entity performed the logging.

If enabled protects this handler from log flooding. Only the first log event will be published, and a summary for the repetition events.

Currently only log flooding is detected for events one frame deep.

Indicates whether the log record tested must match all optional filters, or that it has to match only one filter.

The default is to match any optional filter.

Indicates whether log files will be appended between restarts of a service or that they are overwritten.	

Maximum size of file in KBytes before rotating the log files.

Maximum number of files used for rotating, after reaching the limit it will start to overwrite old log files.

Name of the logger on which the log record must be logged as well. The scope of the loggers is that of the enclosed logger, it is possible to redirect to fixed named loggers (as defined at the container level) by preceding it with the '/' character. Only loggers that have their 'unprotected' attribute set to true are able to accept redirected log records from another namespace.

Indicates whether the log record tested must match all optional filters, or that it has to match only one filter.

The default is to match any optional filter.

Indicates whether the result of the expression represented by this filter must be negated.

Start level of range to be logged, inclusive.

In case no end attribute has been specified the start value will serve as the singel level this filter will allow the records to be published of.

End level of range to be logged, inclusive.

Indicates whether a log record has to be rejected or logged when the conditions are met for this filter.

		By default the filter will return true if the conditions are met.

Indicates whether the result of the expression represented by this filter must be negated.

Class name of Throwable or subclass that will be filtered.

All records for which instanceof 'class' returns true will be filtered. If not provided all records containing a Throwable will be filtered.

Indicates whether the result of the expression represented by this filter must be negated.

Unique OID (Object Identifier) for the service group definition to apply the filter to.
						

Optional identifier of service group to apply the filter to, in case filtering at the service level is required use the instance-id attribute.

If the instance-id attribute is set this attribute will be ignored, as the combination of the OID with the instance-id uniquely identifies a service instance.

Optional identifier of service instance identifier to apply the filter to.

If true the grant only applies to the protection domains that are associated with the class loader of the JSC Service. If false then the grant applies across all protection domains that are associated with the JSC Service.

Full qualified class extending the java.security.Permission object or one of its subclasses.

Action list telling the actions permitted.

Port number the JAR file server will accept incomming request on, if the port number is '0' the container will use a free random port number.

Note that a random port number won't provide durable codebase annotations, i.e. download JAR files won't be accessible after a restart of the container. You are advised to pick a fixed and free port number for long lived deployments.

Host name, or IPv4/IPv6 number, for the codebase annotation URL to be used when marshalling classes and when not overridden at another level.

If not specified the container will determine the 'primary' IP number in textual representation (IPv4 or IPv6) for the host and use that for the codebase annotation URL. It is wise to provide here a DNS alias, as this would ease building security policies for Java clients that needs to connect to this JAR file server and for non LAN environments.

Port number to use in the codebase annotation URL to be used when marshalling classes.

If not specified the container will use the port number the JAR file server has been bound to. This option can be used in case JAR file serving must be performed by a proxy web server that proxies to the internal JAR file server.

Absolute URL path, without the file, part, that maps to a local directory and identifies this alias.

An absolute URL path should have a leading '/' character.

File URI to directory containing the files to be served by the webserver.

The URI has to be a file URI, or in case no scheme is provided a file system path is assumed. In case of a relative filepath the directory the configuration file is in	is consider the root directory for resolving purposes.	

Request/response communication mechanism used for the transport layer of the RMI programming model.

Port number the connector will listen on for inbound requests, if the port number is '0' the container will use a free random port number.

Host name, or IPv4/IPv6 number, for the service proxy to use for setting up a socket connection.

If not specified the container will determine the 'primary' IP number in textual representation (IPv4 or IPv6) for the host and use that for establishing a client-server connection. It is wise to provide here a DNS alias, as this would ease building security policies for Java clients that needs to connect to the service dispatcher and for non LAN environments.

Indicates whether the connector is durable, meaning that even after restarts of the service clients that have a reference are able to talk to that service.

This attribute only has effect when the port number is fixed, that is not the 0 wildcard port number.

Host name, or IPv4/IPv6 number, for the service proxy to use for setting up a socket connection.

If not specified the container will determine the 'primary' IP number in textual representation (IPv4 or IPv6) for the host and use that for establishing a client-server connection. It is wise to provide here a DNS alias, as this would ease building security policies for Java clients that needs to connect to the service dispatcher and for non LAN environments.

Port number the connector will listen on for inbound requests, if the port number is '0' the container will use a free random port number.

Absolute URI used for the Endpoint to connect back to the server, setting this attribute will override host:port combination derived from the inbound-host and port attribute.

The scheme of the absolute URI must be 'http', if the URI contains a path the HttpRequestUriEndpoint will be used.

If set a custom server socket factory will be part of the ServerEndpoint that controls whether the socket created is based on NIO or is a blocking type. If this attribute is not set the type of socket created will depend on the seven.jeri.nio system property.

If true a NIO based socket will be created by the server socket factory, if set to false a blocking socket will be created.

If set a custom socket factory will be part of the Endpoint that controls whether the socket created is based on NIO or is a blocking type. If this attribute is not set the type of socket created will depend on the implementation/configuration of the Jini Platform of the client.

If true a NIO based socket will be created by the server socket factory, if set to false a blocking socket will be created. In most cases one should not specify this attribute.

Host name, or IPv4/IPv6 number, for the service proxy to use for setting up a socket connection.

If not specified the container will determine the 'primary' IP number in textual representation (IPv4 or IPv6) for the host and use that for establishing a client-server connection. It is wise to provide here a DNS alias, as this would ease building security policies for Java clients that needs to connect to the service dispatcher and for non LAN environments.

Port number the connector will listen on for inbound requests, if the port number is '0' the container will use a free random port number.

If set a custom server socket factory will be part of the ServerEndpoint that controls whether the socket created is based on NIO or is a blocking type. If this attribute is not set the type of socket created will depend on the seven.jeri.nio system property.

If true a NIO based socket will be created by the server socket factory, if set to false a blocking socket will be created.

If set a custom socket factory will be part of the Endpoint that controls whether the socket created is based on NIO or is a blocking type. If this attribute is not set the type of socket created will depend on the implementation/configuration of the Jini Platform of the client.

If true a NIO based socket will be created by the server socket factory, if set to false a blocking socket will be created. In most cases one should not specify this attribute.

Host name the Lookup Service is running on.

Port number the Lookup Service is listing for unicast request.

Identifier for entry, can be useful in case of exception when unmarshalling the entry.

Indicates whether the result of the expression represented by this filter must be negated.

Start level of range to be logged, inclusive.

In case no end attribute has been specified the start value will serve as the singel level this filter will allow the records to be published of.

End level of range to be logged, inclusive.

Host name the Lookup Service is running on.

Port number the Lookup Service is listing for unicast request.

Indicates whether the result of the expression represented by this filter must be negated.

Sets the level specifying which messages will be logged, messages lower than this level will be ignored.

By setting the level to OFF the handler can be disabled, by setting the level to ALL every message will be logged.

Sets the character encoding to be used.

If not specified the default character encoding of the platform will be used.

Formatter used for formatting the log records, supported are simple, plain and xml.

Some handlers may however ignore this settings, because they have a fixed log format, e.g. syslog.

Indicates whether context information should be displayed when it is available.

The context information is the OID of the service group definition and the identifier of the service group in which the entity performed the logging.

If enabled protects this handler from log flooding. Only the first log event will be published, and a summary for the repetition events.

Currently only log flooding is detected for events one frame deep.

Indicates whether the log record tested must match all optional filters, or that it has to match only one filter.

The default is to match any optional filter.

Indicates whether the result of the expression represented by this filter must be negated.

Start level of range to be logged, inclusive.

In case no end attribute has been specified the start value will serve as the singel level this filter will allow the records to be published of.

End level of range to be logged, inclusive.

Indicates whether a log record has to be rejected or logged when the conditions are met for this filter.

		By default the filter will return true if the conditions are met.

Indicates whether the result of the expression represented by this filter must be negated.

Class name of Throwable or subclass that will be filtered.

All records for which instanceof 'class' returns true will be filtered. If not provided all records containing a Throwable will be filtered.

Indicates whether the result of the expression represented by this filter must be negated.

Unique OID (Object Identifier) for the service group definition to apply the filter to.
						

Optional identifier of service group to apply the filter to, in case filtering at the service level is required use the instance-id attribute.

If the instance-id attribute is set this attribute will be ignored, as the combination of the OID with the instance-id uniquely identifies a service instance.

Optional identifier of service instance identifier to apply the filter to.