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 migrates the file myj1_2.jar from J2EE version 1.2 to J2EE version 1.3 into new file called myj1_3.jar: iastool -migrate -src myj1_2.jar -target myj1_3.jar newconfig Use this tool to create a new configuration from a configuration template. The command takes the name of a new configuration, the filename and path of a template file relative to the installation's configuration template directory, and an optional property file that overrides the properties in the template used to create the new configuration. Syntax -newconfig (-hub | -host :) -cfg -template [-property ] [-mgmtport ] [-realm ] [-user ] [-pwd ] [-file ] Default Output The default output returns nothing to standard output (stdout). Options Option -hub -host : -cfg -template -property -mgmtport -realm -user -pwd -file Description Specifies the name of the hub in which to create the new configuration. Specifies the host name and the listener port of the machine on which the hub is running to create the new configuration. This option 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 new configuration. Specifies the path where the configuration template is located. template_path can be either a full path of a configuration template XML file or a path relative to the configuration template directory (i.e. /var/ templates/configurations/). Specifies the path to an optional property file that overrides the properties used in the template to create the new configuration. 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. Chapter 29: iastool command-line utility 309
Using the iastool command-line tools Example iastool -newconfig -hub myhub -cfg SimpleProcessConfig -template native.xml -property c:\simple.properties patch Use this tool to apply one or more patches to a JAR file and produce a new JAR file with the applied patches. Syntax -patch -src -patches -target Default Output The default output displays the patches that were applied. Options The following table describes the options available when using the patch tool. Option -src -patches -target Description Specifies the JAR file to which you want to apply one or more patches. The full or relative path to the JAR file must be specified. There is no default. Specifies one or more JAR files that contain the patches you want to apply. To specify more than one file, enter a comma (,) between each file name (no spaces). The full or relative path to the files must be specified. There is no default. Specifies the name of the new JAR file to be created. The full or relative path to the JAR file must be specified. There is no default. Example The following example applies the patches contained in the files mypatch1.jar and mypatch2.jar to the file myold.jar which are all located in the current directory and creates a new file called mynew.jar in the same location: iastool -patch -src myold.jar -patches mypatch1.jar,mypatch2.jar -target mynew.jar 310 BES Developer’s Guide
- 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 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: 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
- 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
Using the iastool command-line tools<br />
Example<br />
The following example migrates the file myj1_2.jar from J2EE version 1.2 to J2EE<br />
version 1.3 into new file called myj1_3.jar:<br />
iastool -migrate -src myj1_2.jar -target myj1_3.jar<br />
newconfig<br />
Use this tool to create a new configuration from a configuration template. The<br />
command takes the name of a new configuration, the filename and path of a template<br />
file relative to the installation's configuration template directory, and an optional<br />
property file that overrides the properties in the template used to create the new<br />
configuration.<br />
Syntax<br />
-newconfig (-hub | -host :) -cfg <br />
-template [-property ] [-mgmtport ]<br />
[-realm ] [-user ] [-pwd ] [-file ]<br />
Default Output<br />
The default output returns nothing to standard output (stdout).<br />
Options<br />
Option<br />
-hub <br />
-host :<br />
-cfg <br />
-template <br />
-property <br />
-mgmtport <br />
-realm <br />
-user <br />
-pwd <br />
-file <br />
Description<br />
Specifies the name of the hub in which to create the new<br />
configuration.<br />
Specifies the host name and the listener port of the machine<br />
on which the hub is running to create the new configuration.<br />
This option enables the iastool utility to locate a hub on a<br />
different subnet than the machine on which iastool is<br />
running.<br />
Specifies the name of the new configuration.<br />
Specifies the path where the configuration template is<br />
located. template_path can be either a full path of a<br />
configuration template XML file or a path relative to the<br />
configuration template directory (i.e. /var/<br />
templates/configurations/).<br />
Specifies the path to an optional property file that overrides<br />
the properties used in the template to create the new<br />
configuration.<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 name,<br />
and password used to authenticate a user. The full or<br />
relative path to this file must be specified. See “Executing<br />
iastool command-line tools from a script file” on page 321 for<br />
more information.<br />
Chapter 29: iastool command-line utility 309