Jini Service Container configuration, provides access to all service definitions and instances. Help messages for expressions introduced at this level. Connector definitions that can be used as general connector by the container. Within this definition each component represents a connector that can be selected at deployment time. Provides configurable objects for container. Internal jar file server for serving the download jar files of deployed services. Provides logger configuration for the container and sets basic logging behaviour for any deployed services. Many third party libraries used within Jini services don't have the notion of the JSC logging API but use fixed named loggers, this allows to control them. Type of connector used by container and services that don't have their own connector configuration. The default connectors don't require additional grants. Provides expressions values for configuration and connector definitions. Collection of OIDs for Jini Service Definitions and Instances. Collection of OIDs for Jini Service Definitions and Instances. 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. 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. URI to root of the location the container will install the service definitions. The URI has to be a file URI, or in case no scheme is provided a filesystem path is assumed. URI to the root of the location the container will dtore log files for the service instances. The URI has to be a file URI, or in case no scheme is provided a filesystem path is assumed. URI to the root of the location the container will install the runtime data for the service instances. The URI has to be a file URI, or in case no scheme is provided a filesystem path is assumed. Time in seconds the configuration files are checked to see whether they have been updated by external means. Defines the deployment unit of a JSC deployment descriptor. Deployment configuration data for service definition group. Has to be decided what the role of name spaces will be within the JSC. Unique identifier of name space. Service instances will refer to the name space they want to be part of. Deployment configuration for service instance. Internal jar file server configuration. If no bind-address is specified the jar server will bind to all interfaces. Addresses the jar server must bind on Aliasses defined for this jar server, allows the serving of jar files for services not being deployed under this container instance. URL path, without the file part, that maps to a local directory and identifies this alias. 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 filesystem path relative to the container installation directory is assumed. Host name, or IPv4/IPv6 number, for the codebase annotation URL to be used when marshalling classes. 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. Port number the jar file server will accept incomming request on. If the port number is '0' or ommitted the container will use a free random port number. IPv4 / IPv6 number or a host name of interface to bind on. Host name, or IPv4/IPv6 number, to be used. If not specified the container will determine the 'primary' IP number in textual representation (IPv4 or IPv6) for the host and use that one. 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 interface. Configuration for service group definition. Help messages for expressions introduced at this level. Connector definitions defined at deployment time and that are supported by the container implementation. Within this definition each component represents a connector that can be selected at deployment time. In case the connector definitions require additional grants these have to be specified at the grant definitions. Grants required for deployment that couldn't be part of the JSC deployment descriptor. Log mechanism configured at service group level, specific logging should be arranged at the service instance level. Important: the name attribute of the configured logger shouldn't be specified, it will be ignored by the container. Configuration for service definition wide elements. Refers to the OID of the JSC deployment descriptor. 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 MD5. 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. Configuration for service instance. Purpose of specific service instance. Help messages for expressions introduced at this level. Grants required for deployment of particular service instance that couldn't be part of the JSC deployment descriptor or service group configuration. Log mechanism configured at service instance level, or any subsystem used by the service. Scope for Lookup Services the service will be registered with. In case no scope is provided here, no joining will take place, this is equivalent to DiscoveryScope.NO_GROUPS. Attributes the service uses to register itself with the Lookup Services. Base 64 encoded data, should not be configured manually, container will take care of this. Connector configuration used to deploy service proxies. If not specified the connector configured at the container level will be used. For the default connectors there are no additional grants required, these are taken care of by the container. Configuration for service instance wide elements. Identifier of service instance, must be unique within context of service group definition. Full qualified class name of object implementing org.cheiron.jsc.JiniService Name Space for grouping service instances that may rune in the same class loader name space. This feature is not implemented yet. Universal Unique Identifier for service instance. The container is responsible for assigning and maintaining this Service ID. indicates whether this service instance has been deployed by the container before, managed by the container. Indicates whether this service instance can be deployed by the container. This attribute can be used to prevent the service from being started. Indicates whether the container should add the life-cycle administration interfaces to the service proxy. Indicates whether the container should add the join administration interfaces to the service proxy. Connector configuration for implementing the RMI programming model. RMI connector based on the JRMP protocol, part of the J2SE platform. Jini Extensible Remote Invocation protocol, provides much more control over the connector. Reference to (free format) connector definition that adheres to the RMI programming model. Network programming model implementation used to communicate between client and service, based on a very limited set of options. This in contrast to the highly flexible connector-def. The JRMP connector is the standard RMI implementation as known to J2SE and allows for interoperability with clients that don't support the new RMI implementations. Note: this connector allows for specifying a single bind address, if not provided the connector will bind on all interfaces the host the container is running on. Addresses this connector must bind on. Host name, or IPv4/IPv6 number, for the service proxy to use for creating 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. Fixed port number to use for exporting the connector, or a random port number in case the value is 0. Note: in case of the JRMP model all services should have a different port number. Network programming model implementation used to communicate between client and service, based on a limited set of options. This in contrast to the highly flexible connector-def. Note: in case no bind-addresses are provided the connector will bind on all interfaces of the host the container is running on. Addresses this connector must bind on. Request/response communication mechanism used for the transport layer of the RMI programming mode. Host name, or IPv4/IPv6 number, for the service proxy to use for creating 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. Fixed port number to use for exporting the connector, or a random port number in case the value is 0. Scope for Lookup Services the service will be registered with. Member group the service will be registered with. Unicast locator URI to Lookup Service. Unicast locator to Lookup Service, based on host and port number. Unicast Lookup Service locator. Host name the Lookup Service is running on. Port number the Lookup Service is listing for unicast request. Resolves grants specified within the JSC deployment descriptor, or can even, for particular cases, assign extra absolute grants. Assign a 'resolved' grant definition to a set of principals. Principal assigned to this grant. Reference to ID of grant or grant definition. Additional grants for those cases it is not possible to create a grant definition for the operation of a particular service group or service instance. This could be for example in the case of plugins that are loaded at deployment time. Represents a configuration object by substitution of expressions and/ or replacing the configuration. Value for expression as defined within the configuration definition. Configuration definition object replacing the definition at the same level (service group definition or service definition). Configures the object used for logging messages of a specific service or component. Loggers are named using a hierarchical dot-separated namespace. Only log records that satisfy the aggregation of filters, to narrow the messages logged. Will only log records that are within the specified log level range. Will only log records that contain a throwable, of a specific type if needed. Configures the various handlers within the logger name space. Publish to console. Publish to file. Publish to network connection. Publish to syslog daemon. Mail to a list of recipients. 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 it will inherit the parent log level. Indicates whether this logger should send its output to it's parent logger. Will only log records that are within the specified log level range. Start level of range to be logged, inclusive. In case no end attribute has been specified this 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. Will only log records that contain a throwable, of a specific type if needed. 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. All log levels defined in J2SE. Abstract log handler to be used for real log handler definitions. Only log records that satisfy the aggregation of filters, to narrow the messages logged. Will only log records that are within the specified log level range. Will only log records that contain a throwable, of a specific type if needed. 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. Some handlers may however ignore this settings, because they have a fixed log format, e.g. syslog. Publish log records to System.err. Publish log records to file. 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. Publish log records to a network stream connection. Host name or IPv4/IPv6 address of host where socket-log daemon is running. Port number the socket-log daemon is listening on. Publish log records to a syslog daemon. Well know syslog facility to use, value must be between 0 - 23. Tag to identify the process writing log messages. If not set the default value is LOG_USER. Host name or IPv4/IPv6 address of host where syslog daemon is running. If not set the default value is localhost. Time zone to use for generating the time stamps in the syslog messages. If not set the default time zone of the platform will be taken. Sends log records to a list of recipients. Tag to identify the process writing log messages. If not set the handler will provide his own valid tag. Host name or IPv4/IPv6 address of host of MTA to deliver messages at. If not set the default value is localhost. Specifies a comma separated list of recipients in the RFC822 address format. Specifies the Reply-To address header in the RFC822 address format.