web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Using the iastool command-line tools Example The following example shows how to display configuration information. kill iastool -info | more Use this tool to kill a managed object on a specified hub and configuration. Syntax -kill > -cfg -mo -moagent [-mgmtport ] [-realm ] [-user ] [-pwd ] [-file ] Default Output By default, the kill tool lists the managed object that has been killed. Options The following table describes the options available when using the kill tool. Option -hub -host : -cfg -mo -moagent -mgmtport -realm -user -pwd -file Description Specifies the name of the hub on which you want to kill a managed object. Specifies the host name and the listener port of the machine on which the managed object you are interested in is running. The option is enables the iastool utility to locate a hub on a different subnet than the machine on which iastool is running. Specifies the name of the configuration containing the specified managed object. Specifies the name of the managed object. Specifies the managed object agent name. Use this option if the specified hub has more than one agent. Specifies the management port number used by the specified hub. The default is 42424. Specifies the realm used to authenticate a user when the user and password options are specified. Specifies the user to authenticate against the specified realm. Specifies the user's password to authenticate against the specified realm. Specifies a login script file containing the realm, user name, and password used to authenticate a user. The full or relative path to this file must be specified. See “Executing iastool command-line tools from a script file” on page 321 for more information. Examples The following example kills the managed object j2ee-server using the default management port: iastool -kill -hub BES1 -cfg j2ee -mo j2ee-server The following example kills the partition naming service running on the configuration j2ee using the management port 24410: iastool -kill -hub BES1 -cfg j2ee -mo standard_visinaming -mgmtport 24410 Chapter 29: iastool command-line utility 303
Using the iastool command-line tools listpartitions Use this tool to list the partitions running on a specified hub, and optionally on a specified configuration or management port. Syntax -listpartitions [-cfg ] [-mgmtport ] [-bare] [-realm ] [-user ] [-pwd ] [-file ] Default Output By default, the listpartitions tool displays the partitions running on a specified hub, or displays the partitions running on a specified hub on a specified configuration or management port. Options The following table describes the options available when using the listpartitions tool. Option -hub -host : -cfg -mgmtport -bare -realm -user -pwd -file Description Specifies the hub name for which you want to list the running partitions. Specifies the host name and the listener port of the machine on which the partitions you are interested in are running. The option is enables the iastool utility to locate a hub on a different subnet than the machine on which iastool is running. Specifies the name of the configuration on which to list partitions. Specifies the management port number used by the specified hub. The default is 42424. Suppresses the output information, other than the names of the running partitions. Specifies the realm used to authenticate a user when the user and password options are specified. Specifies the user to authenticate against the specified realm. Specifies the user's password to authenticate against the specified realm. Specifies a login script file containing the realm, user name, and password used to authenticate a user. The full or relative path to this file must be specified. See “Executing iastool command-line tools from a script file” on page 321 for more information. Examples The following example lists the partitions running on the hub BES1 using the default management port: iastool -listpartitions -hub BES1 The following example lists the partitions running on the hub BES1 using the management port 24410: iastool -listpartitions -hub BES1 -mgmtport 24100 304 BES Developer’s Guide
- Page 263 and 264: Common Client Interface (CCI) Conne
- Page 265 and 266: Packaging and Deployment Figure 26.
- Page 267 and 268: Resource Adapters Resource Adapters
- Page 269 and 270: Connection management Connection ma
- Page 271 and 272: Security management with the Securi
- Page 273 and 274: Security management with the Securi
- Page 275 and 276: Resource Adapter overview Note Reso
- Page 277 and 278: Deployment Descriptors for the Reso
- Page 279 and 280: Developing the Resource Adapter Con
- Page 281 and 282: Deploying the Resource Adapter Pack
- Page 283 and 284: Application development overview 8
- Page 285 and 286: Application development overview //
- 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: 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 and 338: element ■ ■ ■ element The
- Page 339 and 340: element The Partition statistics ag
- 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
Using the iastool command-line tools<br />
Example<br />
The following example shows how to display configuration information.<br />
kill<br />
iastool -info | more<br />
Use this tool to kill a managed object on a specified hub and configuration.<br />
Syntax<br />
-kill > -cfg <br />
-mo -moagent [-mgmtport ]<br />
[-realm ] [-user ] [-pwd ] [-file ]<br />
Default Output<br />
By default, the kill tool lists the managed object that has been killed.<br />
Options<br />
The following table describes the options available when using the kill tool.<br />
Option<br />
-hub <br />
-host :<br />
-cfg <br />
-mo <br />
-moagent <br />
-mgmtport <br />
-realm <br />
-user <br />
-pwd <br />
-file <br />
Description<br />
Specifies the name of the hub on which you want to kill a<br />
managed object.<br />
Specifies the host name and the listener port of the<br />
machine on which the managed object you are interested<br />
in is running. The option is enables the iastool utility to<br />
locate a hub on a different subnet than the machine on<br />
which iastool is running.<br />
Specifies the name of the configuration containing the<br />
specified managed object.<br />
Specifies the name of the managed object.<br />
Specifies the managed object agent name. Use this option<br />
if the specified hub has more than one agent.<br />
Specifies the management port number used by the<br />
specified hub. The default is 42424.<br />
Specifies the realm used to authenticate a user when the<br />
user and password options are specified.<br />
Specifies the user to authenticate against the specified<br />
realm.<br />
Specifies the user's password to authenticate against the<br />
specified realm.<br />
Specifies a login script file containing the realm, user<br />
name, and password used to authenticate a user. The full<br />
or relative path to this file must be specified. See<br />
“Executing iastool command-line tools from a script file” on<br />
page 321 for more information.<br />
Examples<br />
The following example kills the managed object j2ee-<strong>server</strong> using the default<br />
management port:<br />
iastool -kill -hub BES1 -cfg j2ee -mo j2ee-<strong>server</strong><br />
The following example kills the partition naming service running on the configuration<br />
j2ee using the management port 24410:<br />
iastool -kill -hub BES1 -cfg j2ee -mo standard_visinaming -mgmtport 24410<br />
Chapter 29: iastool command-line utility 303