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

In addition to the encryption options available during tokenization tasks, you can encode any text string by using the relevant encryption protocol through the Encode Text dialog box or the CLI. This functionality enables you to generate encoded text for use, for example, when manually editing text in a Configuration or when creating a Server Profile through an external tool (typically in preparation for running installation operations through the CLI).

To encode text through the CLI

Within the cli subdirectory of your BMC Middleware Automation installation, execute a command that invokes the runDeliver script with the -mode encode option.

The following options are available for the Encode operation:




(WebLogic or IBM WebSphere) The path to the application server home directory


The type of encryption protocol or application server.

The default value is ARA_3DES, for the BMC-proprietary, middleware-agnostic encryption protocol named PHE1, which is based on the Triple Data Encryption Standard (3DES) protocol.

If you want to use the native WebLogic encryption protocol (the AES protocol), use one of the following values to indicate the version of the WebLogic application server:

  • weblogic11c
  • weblogic12c

If you want to use the native WebSphere encryption protocol (the XOR protocol), use one of the following values to indicate the version of the WebSphere application server:

  • websphere70
  • websphere80
  • websphere85


(WebLogic) The file name of the WebLogic Server Profile

This option is necessary only if you chose a WebLogic server version for encryption using the AES protocol.


Full path tot he file, which contains the location of the application server home directory (the APP_SERVER_HOME variable). You can use this option instead of the -appServerHome option.

-base64For the PHE1 (or ARA_3DES) encryption protocol (only), you can apply the Base64 encoding scheme by specifying this option.


The text string to encode.

-dest(Optional) The path to a destination file where the encoded value will be stored, instead of being returned as output.
For example: -dest /home/user/.proxy_pwd

For example, 

runDeliver -mode encode -applicationServer ARA_3DES -value myPassword

The encoded text is returned as the output from the command line.

The encryption protocol used during encoding appears in curly brackets before the encoded text — {PHE1} for the BMC encryption protocol, {xor} for the WebSphere protocol, or {AES} for the WebLogic protocol.

Related topic

Encoding text for encryption