Record WLST scripts

To help automate the task of configuring a domain, you can record your configuration actions in the Administration Console as a series of WebLogic Scripting Tool (WLST) commands and then use WLST to replay the commands.

WLST is a command-line scripting environment that you can use to create, manage, and monitor WebLogic Server domains. It is installed on your system when you install WebLogic Server.

The Administration Console does not record WLST commands for the following:

Changes to the security data that is maintained by a security provider. For example, you cannot record the commands to add or remove users, roles, and policies.
Changes to deployment plans.
Deployment operations: install, uninstall (delete), redeploy (update), start, stop.
Runtime operations found on Control or Monitoring pages, such as starting and stopping applications or servers.

The main steps for recording WLST scripts are as follows:

(Optional) Specify the name of the file in which you want to record WLST commands and set other preferences. See Set preferences for WLST recording.
While setting preferences, you can specify WLST commands that the Administration Console inserts before and after the commands that you record. For example, you can insert a series of commands that connect WLST to an Administration Server and append commands that terminate the connection. Unless you add such commands, you cannot run your recorded commands as a WLST script.

For examples of WLST scripts, see WLST Online Sample Scripts.
Start WLST recording.
You cannot remove or undo a command once it has been recorded. Instead, you can edit the script file after you stop recording or you can set your preferences to overwrite the script file and re-record the commands.
(Optional) View the commands that have been recorded. See View recorded commands.
Stop WLST recording.
If you choose the Append To File preference, you can start and stop recording several times before moving to the next steps.
If you record commands that get or set the values of encrypted attributes (such the password for a server's Java Standard Trust keystore), the Administration Console creates two files in addition to the script file: a user configuration file that contains the encrypted data and a key file that contains the key used to encrypt the data. Use the file system to limit read and write access to the key file. Users who can read the key file can read all of the encrypted data that you recorded.
The key file and user configuration files are created in the same directory as the recorded script file and are named recording-fileConfig and recording-fileSecret where recording-file is the name of the recorded script file.
(Optional) Open the script file in a text editor and modify the recorded commands. You specify the name and location of the script file when you set your recording preferences.
Run the script in WLST. When you use WLST to run the commands, WLST must be connected an Administration Server. See Main Steps for Using WLST for more information.
If you recorded commands that get or set the values of encrypted attributes, the user configuration and key files must be in the same directory as the script file. If you move the script file, you must also move the user configuration and key files. Only the key file that was used to encrypt the data can be used to unencrypt the data.

Administration Console Online Help

Record WLST scripts