Page tree
Skip to end of metadata
Go to start of metadata

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:

  • If you need to add an argument to the JVM command that executes the server interaction (for example, if you are running in a limited memory environment). You can define various properties to be passed on as Java system arguments. Such properties should always have the jvmarg. prefix.
  • To set a non-default location for the JDK used by Oracle WebLogic.


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 or 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>

To define launcher properties

  1. Select Window > Preferences.
  2. Select BMC Middleware Automation > Launcher Properties.
  3. Use the Add and Remove buttons to edit the list of launcher properties.
    After clicking Add, enter a property name and value directly into the Property and Value columns.
  4. Click OK.

The following figure shows several defined launcher properties. These and other useful launcher properties are described in the table that follows the figure.


Launcher property



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 SnapshotInfo element at the end of the Snapshot XML file.


Sets the time in seconds before a transaction times out on an IBM WebSphere server when you install a Configuration.

If you select the Capture full rollback data on install option in the Portal Tasks section of the Portal tab, BMC Middleware Automation begins a transaction when you begin to install a Configuration. If the installation fails, the transaction is rolled back so that the server is returned to its state when the installation began.

This property overrides a WebSphere parameter that defines the maximum time that a transaction can run before WebSphere ends the transaction. The default value in WebSphere is 120 seconds. Installing a BMC Middleware Automation Portal Configuration can take much longer than two minutes, so it is important to set this parameter to a higher value (for example 7200 seconds). This is expressed with the following property value (for example):

Note: The dynamic setting of this timeout value for WebSphere Portal requires a minimum fix-pack level of or

You can alternatively set the timeout value through the WebSphere Administration Console, as follows:

  1. Under Servers, click Application servers and then click the link for your WebSphere Portal server.
  2. Under Container Settings, expand Container Services and click Transaction Service.
  3. Enter a new timeout value in Total transaction lifetime timeout and click Apply.


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, -Xms128m -Xmx512m).

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.
For example, you might set the property value to


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 ( or pznload.bat), which is used in publishing WebSphere Portal Personalization properties.
The value for this launcher property is:

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.
The value for this launcher property is:


Sets the location of the WebLogic license (license.bea) file (for example, a value of Dbea.home=/opt/bea). Using this property ensures a successful secure connection to the WebLogic server.

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.
This is expressed with the following property value (for example):

jvmarg.cajoUse 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:
ph.soapRequestTimeoutUse this property to set the request timeout time. For example:
By default, the request timeout is set to 180 seconds.


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.
The value for this launcher property is:

(depending on WebLogic version)

Enables you to set a non-default location for the JDK used by WebLogic.
For a WebLogic installation, BMC Middleware Automation expects the JDK installation directory to be located within the same directory in which the WebLogic home directory is located. For example, if the WebLogic home directory is /opt/bea/weblogic81, BMC Middleware Automation expects a default JDK installation directory such as /opt/bea/jdk142_11.


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.
The value for this launcher property is:


Enables you to save a local retrieveSigners.log file for tracing the execution of the retrieveSigners command during a WebSphere installation operation. Specify a value of either true or false.


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 RolloutUpdate option is enabled for an IBM WebSphere Application Server application with high availability deployment, the rollout timeout enables you to specify the timeout between rolling out the application update to the next node in the cluster and ensures that the updated application has enough time to start. The default value is 300 seconds.
jboss.connectionTimeout (for JBoss EAP 6.3 only)

Defines the connection timeout to the JBoss instance.