web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Running Partitions Figure 3.1 Partition Footprint Running Partitions Partitions are typically run under the control of a management agent within a configuration, but they can also be run directly from the command line as unmanaged Partitions. In both cases the Partition requires that a Smart Agent (osagent) be running in the same sub-net on the same Smart Agent port. See the Management Console User's Guide section, for information about managing Partitions within a configuration. Running unmanaged Partitions Note To run an unmanaged Partition (not managed by SCU), use the following command: partition [-path ] If no -path is specified, then the current directory is used. The full list of Partition arguments is available in the following tables. Many of these arguments are for use by the management agents and not by a user. partition [] [-path ] [-management_agent [-management_agent_id ]] [-no_user_services] [-unique_cookie ] are the usual Java options and VM system properties recognized by the Partition. Options that are typically static, and pertinent to both managed and unmanaged Partitions, are best encapsulated in the Partition's configuration files. Table 3.1 Partition command options Option -Dlog4j.configuration -Dlog4j.configuration.update.delay Description Path to the Partition's log4j configuration file. Default is /adm/properties/logConfiguration.xml Specifies the period, in milliseconds, between checks for updates to the log4j configuration file. Default is 60000 milliseconds (1 minute). Chapter 3: Partitions 17
Running Partitions Table 3.1 Option - Dpartition.ignore_shutdown_on_signal= -Dpartition.default.smartagent.port -Dpartition.default.smartagent.addr -Dvbroker.agent.port -Dvbroker.agent.addr -Dpartition.management_domain.port -DTomcatLoaderDebug Table 3.2 Arguments Partition command available arguments -path -management_agent -management_agent_id -unique_cookie Partition command options (continued) -no_autostart_user_services Running managed Partitions Description Use this property to decide whether to ignore shutdown signals and wait for a shutdown request via the Partition's management interface(s). Note that UNIX sends a Ctrl-C signal to all processes in a process group. A Partition in control of its own life cycle would not set this. When the Partition is invoked by some parent controlling process, such as the SCU, then this would be set to true to ensure that the Partition does not immediately exit when the parent is issued a shutdown signal. Overrides the User ORB Smart Agent port and overrides all Partition configuration. This property is only overridden by -Dvbroker.agent.port. Typically used by a parent controlling process, such as the SCU. Overrides User ORB Smart Agent addr property and overrides all Partition configuration. Is only overridden by -Dvbroker.agent.addr. Typically used by a parent controlling process, such as the SCU. Ultimate override for the User ORB Smart Agent port. This is typically never used by a parent controlling process, but it may be used by a command-line user. Ultimate override for the User ORB Smart Agent addr. Typically never used by a parent controlling process, but it may be used by a command-line user. Sets the Management ORB Smart Agent port. Default 42424. Typically used by a parent controlling process, such as the SCU. Sets the Web Container debug level. Default 0 (zero). Description Partition footprint path. The default is false which disables the Partition management agent and runs a standalone Partition. To enable the Partition management agent, set to true. Sets the identity to be used for the Partition's management interface object name. Sets the cookie to be used to construct unique identities in the Partition. In particular, used to construct default external interface names. The default is: . If set to true, disables the autostart of user domain Partition services that are configured to be started. Managed Partitions are started when the configuration to which they belong starts. Typically the Partition starts according to a default mechanism, but you can configure additional command-line options to be passed at creation-time. Or, you can edit configuration.xml file. Open the file, search for , and find the data block. Insert new command-line arguments within tags. 18 BES Developer’s Guide
- Page 1 and 2: Developer’s Guide Enterprise Serv
- Page 3 and 4: Contents Chapter 1 Introduction to
- Page 5 and 6: Entity beans . . . . . . . . . . .
- Page 7 and 8: Chapter 23 Using JMS 209 Configurin
- Page 9 and 10: Entity Bean Properties (applicable
- Page 11 and 12: Figures 0.1 Borland Enterprise Serv
- Page 13 and 14: BES Products and Editions overview
- Page 15 and 16: Documentation conventions Important
- Page 17 and 18: Contacting Borland support World Wi
- Page 19 and 20: BES services overview Figure 0.1 Bo
- Page 21 and 22: The Partition and its services ■
- Page 23 and 24: Borland Enterprise Server and J2EE
- Page 25 and 26: 14 BES Developer’s Guide
- Page 27: Creating Partitions Creating Partit
- Page 31 and 32: Configuring Partitions You can also
- Page 33 and 34: JMX support in Partitions ■ ■ A
- Page 35 and 36: JMX support in Partitions Figure 3.
- Page 37 and 38: Thread pools Partition properties r
- Page 39 and 40: 28 BES Developer’s Guide
- Page 41 and 42: Apache web server implementation Fo
- Page 43 and 44: Borland web container implementatio
- Page 45 and 46: Borland web container implementatio
- Page 47 and 48: Borland web container implementatio
- Page 49 and 50: Smart Agent implementation Smart Ag
- Page 51 and 52: 40 BES Developer’s Guide
- Page 53 and 54: Apache web server to Borland web co
- Page 55 and 56: Apache web server to Borland web co
- Page 57 and 58: Apache web server to Borland web co
- Page 59 and 60: Large data transfer Downloading lar
- Page 61 and 62: Large data transfer Uploading large
- Page 63 and 64: IIS web server to Borland web conta
- Page 65 and 66: IIS web server to Borland web conta
- Page 67 and 68: IIS web server to Borland web conta
- Page 69 and 70: Session management with JSS If an i
- Page 71 and 72: Managing and configuring the JSS Co
- Page 73 and 74: The Borland IIOP connector BES supp
- Page 75 and 76: Setting up your web container with
- Page 77 and 78: 66 BES Developer’s Guide
Running Partitions<br />
Table 3.1<br />
Option<br />
-<br />
Dpartition.ignore_shutdown_on_signal=<br />
<br />
-Dpartition.default.smartagent.port<br />
-Dpartition.default.smartagent.addr<br />
-Dvbroker.agent.port<br />
-Dvbroker.agent.addr<br />
-Dpartition.management_domain.port<br />
-DTomcatLoaderDebug<br />
Table 3.2<br />
Arguments<br />
Partition command available arguments<br />
-path <br />
-management_agent <br />
-management_agent_id <br />
-unique_cookie <br />
Partition command options (continued)<br />
-no_autostart_user_services <br />
Running managed Partitions<br />
Description<br />
Use this property to decide whether to ignore shutdown<br />
signals and wait for a shutdown request via the<br />
Partition's management interface(s). Note that UNIX<br />
sends a Ctrl-C signal to all processes in a process<br />
group.<br />
A Partition in control of its own life cycle would not set<br />
this. When the Partition is invoked by some parent<br />
controlling process, such as the SCU, then this would<br />
be set to true to ensure that the Partition does not<br />
immediately exit when the parent is issued a shutdown<br />
signal.<br />
Overrides the User ORB Smart Agent port and<br />
overrides all Partition configuration. This property is<br />
only overridden by -Dvbroker.agent.port.<br />
Typically used by a parent controlling process, such as<br />
the SCU.<br />
Overrides User ORB Smart Agent addr property and<br />
overrides all Partition configuration. Is only overridden<br />
by -Dvbroker.agent.addr.<br />
Typically used by a parent controlling process, such as<br />
the SCU.<br />
Ultimate override for the User ORB Smart Agent port.<br />
This is typically never used by a parent controlling<br />
process, but it may be used by a command-line user.<br />
Ultimate override for the User ORB Smart Agent addr.<br />
Typically never used by a parent controlling process,<br />
but it may be used by a command-line user.<br />
Sets the Management ORB Smart Agent port. Default<br />
42424.<br />
Typically used by a parent controlling process, such as<br />
the SCU.<br />
Sets the Web Container debug level. Default 0 (zero).<br />
Description<br />
Partition footprint path.<br />
The default is false which disables the Partition<br />
management agent and runs a standalone<br />
Partition. To enable the Partition management<br />
agent, set to true.<br />
Sets the identity to be used for the Partition's<br />
management interface object name.<br />
Sets the cookie to be used to construct unique<br />
identities in the Partition. In particular, used to<br />
construct default external interface names. The<br />
default is: .<br />
If set to true, disables the autostart of user domain<br />
Partition services that are configured to be started.<br />
Managed Partitions are started when the configuration to which they belong starts.<br />
Typically the Partition starts according to a default mechanism, but you can configure<br />
additional command-line options to be passed at creation-time. Or, you can edit<br />
configuration.xml file. Open the file, search for , and find the<br />
data block. Insert new command-line arguments within tags.<br />
18 BES Developer’s Guide