On the Launcher Properties preferences page, you can enter command-line options to include when the BMC Middleware Automation engine is launched to perform an action on an application server. The BMC Middleware Automation engine, which executes the server interaction, runs in a new JVM. You can create properties on this Preferences page for the following example scenarios:
To include JVM arguments in installation operations that you perform through the command-line interface (CLI), you must define your JVM arguments through the JVMARGS property in the setupDeliver.properties or setupPortal.properties file. In the .properties file, enter only the text string used in the Value column on the Launcher Properties page (and not the property name from the Property column).
To set a non-default location for the JDK used by WebLogic through the .properties file (for use with operations that your perform through the CLI), add another line in the .properties file (separate from the JVMARGS property). Include both the property name and the value (as you would enter them on the Launcher Properties page), with an equals sign (=) between them. For example:
jdk.weblogic81=<path to JDK>
The following figure shows several defined launcher properties. These and other useful launcher properties are described in the table that follows the figure.
Enables you to force communication through an IPv4 socket or through an IPv6 socket in an IPv4/IPv6 mixed environment (that is, an environment that has two network adapters, one IPv4 and another IPv6). Use one of the following property values, as necessary:
Instructs BMC Middleware Automation to save metadata about the Snapshot when it creates the Snapshot. The value for this property is
The metadata, which includes information such as the time the Snapshot was taken, is saved in a
Sets the time in seconds before a transaction times out on an IBM WebSphere server when you install a Configuration.
Sets the minimum and maximum sizes for the JVM heap memory to use during product startup. The value of the property is the set of command-line properties to add to the JVM command line (for example,
Your JVM might have different properties that you can define to tune for your environment. Check the JVM provider's documentation for details.
Enables you to increase the time that BMC Middlware Automation will wait for an application installation on a WebSphere Application Server or WebLogic Server to complete. The default value is 120000 milliseconds (2 minutes).
You will need to increase this value when large EAR files are being uploaded or installed.
Enables BMC Middleware Automation to base a secure connection on the default certificate from any WebSphere server (version 6.1 or 7.0). The value for this property is
Enables you to set a non-default location for the pznload script (pznload.sh or pznload.bat), which is used in publishing WebSphere Portal Personalization properties.
Enables you to skip the upload of WAR files from the Portlets directory on the client (as specified on the Portal tab in the Server Profile) during the installation or preview of a WebSphere Portal Configuration.
Sets the location of the WebLogic license (license.bea) file (for example, a value of
Enables you to specify the location of your private keystore if you set up a secure connection with WebLogic using a private keystore that was configured through the WebLogic Admin Console.
|Use this property to troubleshoot a the test connection to the target application server that does not work through the user interface (UI), while working through the command-line interface (CLI). The cause of the issue may be the use of Cajo for the Java Virtual Machine (JVM) processes created through the user interface. For example:|
|Use this property to set the request timeout time. For example:|
Enables you to modify the query string used by BMC Middleware Automation to retrieve the WebSphere Application Management MBean. Use this launcher property to troubleshoot and resolve performance issues that might occur during the retrieval of the MBean on a multi-node system.
Enables you to set a non-default location for the JDK used by WebLogic.
Provides the option of using the WebSphere Portal profile directory instead of the WebSphere Application Server home directory when running wsadmin commands on the server.
Enables you to save a local retrieveSigners.log file for tracing the execution of the
If you use the %i wildcard to auto-increment the cluster member name (for example: ClusterMemberName_%i), the numbering starts from 1 by default. To customize the start number, set the ph.wildcardClusterMemberStartNum value. Ensure that you use a positive integral number.
|When the |
Defines the connection timeout to the JBoss instance.