web server - Borland Technical Publications
web server - Borland Technical Publications web server - Borland Technical Publications
Using the iastool command-line tools pservice Use this tool to enable, disable, or get the state of a partition service. Syntax -pservice -cfg -partition -moagent -service [-force_restart] [-mgmtport ] [-realm ] [-user ] [-pwd ] [-file ] Default Output The default output returns nothing to standard output (stdout). Options The following table describes the options available when using the pservice tool. Option -hub -host : -partition -moagent -service -enable | -disable | -status -force_restart -mgmtport -realm -user -pwd -file Description Specifies the hub where the partition service you are interested in is located. There is no default. Specifies the host name and the listener port of the machine on which the partition service you are interested in is running. The option is enables the iastool utility to locate a partition service on a different subnet than the machine on which iastool is running. Specifies the name of the partition. Specifies the managed object agent name. Use this option if the specified hub has more than one agent. Specifies the name of the service. Specifies the operation you would like to perform on the partition service. Restarts the specified Partition after completing the enable, disable, or status operation. If this option is not specified, you will need to restart the Partition manually to initialize the module. 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. Example The following example shows how to enable the partition naming service on the standard partition. iastool -pservice -hub BES1 -cfg j2ee -partition standard -service standard_visinaming -enable -force_restart -mgmtport 24431 Chapter 29: iastool command-line utility 313
Using the iastool command-line tools removestubs Use this tool to remove all stub files from a JAR file. Syntax -removestubs -jars [-targetdir ] Default Output The default output returns nothing to standard output (stdout). Options The following table describes the options available when using the removestubs tool. Option -jars -targetdir Description Specifies the JAR file(s) from which you want to remove one or more stub files. To specify more than one JAR file, enter a comma(,) between each JAR file (no spaces). The full or relative path to the JAR file(s) must be specified. There is no default. Specifies the directory in which the stub files that were removed will be stored. A full or relative path must be specified, if this option is specified. There is no default. If no target directory is specified, the stub files will be removed, but not saved. Example The following example shows how to remove stub files located from the EJB JAR files proj1.jar, proj2.jar, and proj3.jar located in the current directory and copy them to c:\examples\proto: iastool -removestubs -jars proj1.jar,proj2.jar,proj3.jar -targetdir c:\examples\proto restart Use this tool to restart a hub or managed object. The hub must already be running in order for the restart tool to work with a hub. Syntax -restart [-mgmtport ] [-realm ] [-user ] [-pwd ] [-file ] or -restart [-cfg ] -mo -moagent [-mgmtport ] [-realm ] [-user ] [-pwd ] [-file ] Default Output The default output displays the hub or managed object that has been restarted. If the restart tool fails (for example, when a managed object cannot be shutdown or restarted), an error is displayed with a status code which is returned to standard error output (stderr). 314 BES Developer’s Guide
- 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 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: 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
- 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
Using the iastool command-line tools<br />
removestubs<br />
Use this tool to remove all stub files from a JAR file.<br />
Syntax<br />
-removestubs -jars [-targetdir ]<br />
Default Output<br />
The default output returns nothing to standard output (stdout).<br />
Options<br />
The following table describes the options available when using the removestubs tool.<br />
Option<br />
-jars <br />
-targetdir <br />
Description<br />
Specifies the JAR file(s) from which you want to remove one or more<br />
stub files. To specify more than one JAR file, enter a comma(,)<br />
between each JAR file (no spaces). The full or relative path to the JAR<br />
file(s) must be specified. There is no default.<br />
Specifies the directory in which the stub files that were removed will be<br />
stored. A full or relative path must be specified, if this option is<br />
specified. There is no default. If no target directory is specified, the<br />
stub files will be removed, but not saved.<br />
Example<br />
The following example shows how to remove stub files located from the EJB JAR files<br />
proj1.jar, proj2.jar, and proj3.jar located in the current directory and copy them to<br />
c:\examples\proto:<br />
iastool -removestubs -jars proj1.jar,proj2.jar,proj3.jar<br />
-targetdir c:\examples\proto<br />
restart<br />
Use this tool to restart a hub or managed object. The hub must already be running in<br />
order for the restart tool to work with a hub.<br />
Syntax<br />
-restart [-mgmtport ]<br />
[-realm ] [-user ] [-pwd ] [-file ]<br />
or<br />
-restart [-cfg ]<br />
-mo -moagent [-mgmtport ]<br />
[-realm ] [-user ] [-pwd ] [-file ]<br />
Default Output<br />
The default output displays the hub or managed object that has been restarted.<br />
If the restart tool fails (for example, when a managed object cannot be shutdown or<br />
restarted), an error is displayed with a status code which is returned to standard error<br />
output (stderr).<br />
314 BES Developer’s Guide