12.11.2014 Views

web server - Borland Technical Publications

web server - Borland Technical Publications

web server - Borland Technical Publications

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

element<br />

Table 30.2<br />

Attribute<br />

shutdown.synchronization<br />

shutdown.service_shutdown.max_wait<br />

shutdown.delay<br />

shutdown.phase<br />

Attributes of the service element (continued)<br />

Description<br />

The type of synchronization to be performed when the<br />

service is shutdown. Valid values are:<br />

■ service_shutdown—wait for the service to stop for up to<br />

shutdown.service_shutdown.max_wait milliseconds.<br />

■ delay—always wait for shutdown.delay milliseconds, do<br />

not monitor the service for it to stop.<br />

Default is no synchronization.<br />

Limits the maximum time, in milliseconds, that the<br />

Partition waits for the service to stop when the<br />

shutdown.synchronization value is service_shutdown. A<br />

value of 0 (zero) means no time limit is imposed. Default<br />

value is 0 (zero).<br />

Defines the time, in milliseconds, that the Partition waits<br />

in order to give the service a chance to stop when the<br />

shutdown.synchronization value is delay. A value of 0<br />

(zero) means wait forever. Default is 0 (zero).<br />

This property governs which Partition shutdown phase<br />

the service is shutdown in. A Partition shuts down in 2<br />

phases. In the first phase all services and components<br />

providing user facility are shutdown, and in the second<br />

phase the Partition's own infrastructure is shutdown.<br />

Valid values are 1 (default) and 2.<br />

It is not typical for any Partition service to be shutdown<br />

in phase 2.<br />

element<br />

The properties element lets you supply the specific service's configuration metadata.<br />

element<br />

The archives element contains configuration metadata for the archives that the<br />

Partition can host. A specific archive can have an archive sub-element with attributes<br />

specific to that archive. An archive does not have to have an archive sub-element.<br />

Attribute<br />

ear.repository.path<br />

war.repository.path<br />

ejbjar.repository.path<br />

rar.repository.path<br />

dar.repository.path<br />

lib.repository.path<br />

classes.repository.path<br />

Description<br />

Path to the Partition's EARs directory. All EARs found in that<br />

directory are loaded by the Partition on startup, unless specifically<br />

disabled with an archive element.<br />

Path to the Partition's WARs directory. All WARs found in that<br />

directory are loaded by the Partition on startup, unless specifically<br />

disabled with an archive element.<br />

Path to the Partition's EJB jars directory. All EJB jars found in that<br />

directory are loaded by the Partition on startup, unless specifically<br />

disabled with an archive element.<br />

Path to the Partition's RARs directory. All RARs found in that<br />

directory are loaded by the Partition on startup, unless specifically<br />

disabled with an archive element.<br />

Path to the Partition's DARs directory. All DARs found in that<br />

directory are loaded by the Partition on startup, unless specifically<br />

disabled with an archive element.<br />

Path to the Partition's lib directory. All JAR files found in that<br />

directory are placed on the Partition's system classpath.<br />

Path to the Partition's classes directory. All classes found in that<br />

directory are placed on the Partition's system classpath.<br />

All the paths are relative to the Partition's root directory.<br />

Chapter 30: Partition XML reference 329

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!