web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
element Table 30.1 The http.adaptor element contains the following sub-element: ■ Attribute socket.factory.name processor.name Attributes of http.adaptor element (continued) Description Replaces the default socket factory with another using an ObjectName, the pointed MBean has to have a public ServerSocket createServerSocket(int port, int backlog, String host) throws IOException method. This sets the MBean's ObjectName to be used as XML processor. The MBean has to implement the mx4j.tools.adaptor.http.ProcessorMBean interface. element The xslt.processor element configures the XSLT processor for the HTTP adaptor. The XSLT processor transforms the raw XML into presentable HTML for the Web browser. If this property is not enabled and you try to use the MX4J Web console you will get raw XML in your Web browser. Attribute enable File PathInJar LocaleString UseCache Description Enables or disables the XSLT processor. Valid values are true (default) or false. Determines where to look for XSL files. If the target file is a directory, it assumes that XSL files are located in the directory. Otherwise if it points to a JAR or ZIP file, it assumes that the files are located inside. Pointing to a file system is especially useful for testing. Sets the directory in the JAR file where XSL files reside. Sets the locale by using a String. Default is en. Indicates whether to cache the transformation objects. This speeds-up the transformation process. It is usually set to true, but you can set it to false for easier testing. Default is true. element The rmi-iiop.adaptor element configures the JMX agent's RMI-IIOP adaptor. The RMI- IIOP adaptor is based on the client framework, which helps managers or managing applications to communicate with the MBean Server through RMI. Attribute enable Description Enables or disables the RMI-IIOP adaptor. Valid values are true (default) or false. element The statistics.agent element configures the Partition's statistics agent. The Partition statistics agent consists of two components: ■ ■ A statistics collector that periodically collects statistics data on the Partition and saves that data onto disk. These periodic data samples build up on disk enabling the product tools to provide current, and historical current statistical data on a Partition. A statistics reaper that periodically reaps (cleans up) the historical data from disk. Chapter 30: Partition XML reference 325
element The Partition statistics agent is intended for collecting short term statistical data. However, it is only physically limited by the amount of disk space it is allowed to consume. Attribute enable level snapshot.period_secs reap.enable reap.older_than_secs reap.period_secs Description Enables or disables the statistics agent. A disabled statistics agent will not collect or reap statistics data. Valid values are true (default) or false. Sets the level of detail of statistics collected from a Partition. Valid values are: none, minimum (default), and maximum. Specifies how often (in seconds) Partition statistics are collected and written to the disk. The default is 10 seconds. Enables or disables the reaping (clean up) of Partition statistics data on disk. Valid values are true (default) or false. If reap_enable is true, sets the threshold for the age (in seconds) of statistics data kept on disk before being deleted. The default is 600 seconds (10 minutes). If reap_enable is true, sets the time period (in seconds) between sweeps to clean up statistics data older than reap.older_than_secs from disk. The default is 60 seconds (1 minute). element The security element lets you configure the security settings for a given Partition. This empty element contains the attributes described in the following table. Attribute enable manager policy Description Enables or disables security for a Partition. Valid values are true (default) or false. Specifies the name of the security manager used by a Partition. Valid values are any available security provider names, for example com.borland.security.provider.CertificateWallet. Specifies the name of the security policy file that defines the security rules of a Partition. Valid values are any fully qualified security policy file names, for example /va/\security/profile/\management/java_security.policy element The container element specifies how the Partition works with classloading. Attribute system.classload.prefixes verify.on.load classloader.policy classloader.classpath Description This is a comma separated list of resource prefixes that the custom classloader will delegate to the system classloader prior to attempting to load itself. When true runs verify on JARs as they are loaded. Default is true. Determines the type of classloader to be used by the Partition. Valid values are per_module or container. The per_module classloader policy will create a separate application classloader for each deployed module. This policy is required if you want to be able to hot deploy. The container policy will load all deployed modules in the shared classloader. You cannot hot deploy if this policy is selected. Contains a semicolon (;) separated list of JAR files to be loaded by each instance of the application classloader. This has the same logical effect as bundling these jars in every module. 326 BES Developer’s Guide
- Page 287 and 288: Application development overview
- Page 289 and 290: Other Considerations Other Consider
- Page 291 and 292: Other Considerations To illustrate,
- Page 293 and 294: Other Considerations } } { cf = new
- Page 295 and 296: General syntax and usage General sy
- Page 297 and 298: Syntax and usage for iastool Table
- Page 299 and 300: Syntax and usage for java2iiop Exam
- Page 301 and 302: Syntax and usage for appclient Tabl
- Page 303 and 304: Building and running the BES exampl
- Page 305 and 306: Using the iastool command-line tool
- Page 307 and 308: Using the iastool command-line tool
- Page 309 and 310: Using the iastool command-line tool
- Page 311 and 312: Using the iastool command-line tool
- Page 313 and 314: Using the iastool command-line tool
- Page 315 and 316: Using the iastool command-line tool
- Page 317 and 318: Using the iastool command-line tool
- Page 319 and 320: Using the iastool command-line tool
- Page 321 and 322: Using the iastool command-line tool
- Page 323 and 324: Using the iastool command-line tool
- Page 325 and 326: Using the iastool command-line tool
- Page 327 and 328: Using the iastool command-line tool
- Page 329 and 330: Using the iastool command-line tool
- Page 331 and 332: Using the iastool command-line tool
- Page 333 and 334: Executing iastool command-line tool
- Page 335 and 336: 324 BES Developer’s Guide
- Page 337: element ■ ■ ■ element The
- Page 341 and 342: element element The services eleme
- Page 343 and 344: element element The archive elemen
- Page 345 and 346: EJB Container-level Properties Tabl
- Page 347 and 348: EJB Container-level Properties Tabl
- Page 349 and 350: EJB Customization Properties: Deplo
- Page 351 and 352: Complete Index of EJB Properties Co
- Page 353 and 354: Complete Index of EJB Properties Ta
- Page 355 and 356: Complete Index of EJB Properties Ta
- Page 357 and 358: Complete Index of EJB Properties Ta
- Page 359 and 360: Java Session Service (JSS) Properti
- Page 361 and 362: Java Session Service (JSS) Properti
- Page 363 and 364: Partition Transaction Service (Tran
- Page 365 and 366: Borland-specific web DTD 33, 36 bra
- Page 367 and 368: ejb.mdb.maxMessagesPerServerSession
- Page 369 and 370: J J2EE VisiClient 97 VisiClient env
- Page 371 and 372: optimistic concurrency 130 SelectFo
- Page 373 and 374: Sonic clustered service 228 SonicMQ
- Page 375: X XML DTD 99 VisiClient 98 grammar
element<br />
Table 30.1<br />
The http.adaptor element contains the following sub-element:<br />
■<br />
Attribute<br />
socket.factory.name<br />
processor.name<br />
<br />
Attributes of http.adaptor element (continued)<br />
Description<br />
Replaces the default socket factory with another using an<br />
ObjectName, the pointed MBean has to have a public<br />
ServerSocket createServerSocket(int port, int backlog, String<br />
host) throws IOException method.<br />
This sets the MBean's ObjectName to be used as XML<br />
processor. The MBean has to implement the<br />
mx4j.tools.adaptor.http.ProcessorMBean interface.<br />
element<br />
The xslt.processor element configures the XSLT processor for the HTTP adaptor. The<br />
XSLT processor transforms the raw XML into presentable HTML for the Web browser.<br />
If this property is not enabled and you try to use the MX4J Web console you will get raw<br />
XML in your Web browser.<br />
Attribute<br />
enable<br />
File<br />
PathInJar<br />
LocaleString<br />
UseCache<br />
Description<br />
Enables or disables the XSLT processor. Valid values are true (default)<br />
or false.<br />
Determines where to look for XSL files. If the target file is a directory, it<br />
assumes that XSL files are located in the directory. Otherwise if it points<br />
to a JAR or ZIP file, it assumes that the files are located inside. Pointing<br />
to a file system is especially useful for testing.<br />
Sets the directory in the JAR file where XSL files reside.<br />
Sets the locale by using a String. Default is en.<br />
Indicates whether to cache the transformation objects. This speeds-up<br />
the transformation process. It is usually set to true, but you can set it to<br />
false for easier testing. Default is true.<br />
element<br />
The rmi-iiop.adaptor element configures the JMX agent's RMI-IIOP adaptor. The RMI-<br />
IIOP adaptor is based on the client framework, which helps managers or managing<br />
applications to communicate with the MBean Server through RMI.<br />
Attribute<br />
enable<br />
Description<br />
Enables or disables the RMI-IIOP adaptor. Valid values are true<br />
(default) or false.<br />
element<br />
The statistics.agent element configures the Partition's statistics agent. The Partition<br />
statistics agent consists of two components:<br />
■<br />
■<br />
A statistics collector that periodically collects statistics data on the Partition and<br />
saves that data onto disk. These periodic data samples build up on disk enabling the<br />
product tools to provide current, and historical current statistical data on a Partition.<br />
A statistics reaper that periodically reaps (cleans up) the historical data from disk.<br />
Chapter 30: Partition XML reference 325