+

Search Tips   |   Advanced Search

RepositoryCheckpointCommands using wsadmin.sh

Use Jython or Jacl with wsadmin to create, restore, delete, and administer checkpoints. Repository checkpoints represent saved images of the repository before configuration changes are made. The commands in the RepositoryCheckpointCommands group support the repository checkpoint functions in wsadmin local and connected modes.

A full checkpoint is a complete copy of the entire configuration repository. A delta checkpoint is a subset snapshot of the configuration repository made when we change a product configuration. Use a checkpoint to restore the configuration repository back to a prior state.

To enable automatic checkpoints, use the setAutoCheckpointEnabled command and set -autoCheckpointEnabled to true. Whenever a change is made to the configuration repository, the product creates a delta checkpoint. Actions such as creating an application server and saving the configuration change results in creation of a delta checkpoint. The checkpoint preserves an image of the repository before the configuration change is made.

We do not need to restart the server after running the command. When any configuration change is made and saved to the configuration repository the product creates a delta checkpoint automatically in...

The product stores the configuration repository in...

After running commands that change the configuration repository, the product automatically saves the configuration changes. We do not need to run AdminConfig.save() after running commands such as createFullCheckpoint, deleteCheckpoint, restoreCheckpoint, setAutoCheckpointDepth, setAutoCheckpointEnabled, or setCheckpointLocation.


createFullCheckpoint

Create a full checkpoint. Provide a -checkpointName value to name the full checkpoint.

Target object: None

Required parameters:

Optional parameters:

Batch mode example usage

Interactive mode example usage


deleteCheckpoint

Delete the checkpoint specified by the -checkpointName value. We can delete any full checkpoint. As to delta checkpoints, we can only delete the oldest delta checkpoint.

Target object: None

Required parameters:

Optional parameters: None

Batch mode example usage

Interactive mode example usage


extractRepositoryCheckpoint

Extract a delta repository checkpoint. Provide a -checkpointName value to identify the repository to extract and an -extractToFile value to specify the full path name of the compressed file to hold the extracted checkpoint files.

Target object: None

Required parameters:

Optional parameters: None

Batch mode example usage

Interactive mode example usage


getAutoCheckpointDepth

Get the number of automatic delta checkpoints that the product keeps. After the number of delta checkpoints is reached, the product deletes the oldest delta checkpoint each time a new delta checkpoint is made. The command returns the number of automatic delta checkpoints to keep.

Target object: None

Required parameters: None

Optional parameters: None

Example usage


getAutoCheckpointEnabled

Find out whether automatic creation of delta checkpoints is enabled. The command returns true if automatic checkpoints are enabled and false if automatic checkpoints are disabled.

Target object: None

Required parameters: None

Optional parameters: None

Example usage


getCheckpointLocation

Get the directory path where checkpoints are stored. The command returns the directory path. The product stores checkpoints in the profile_root/checkpoints directory.

Target object: None

Required parameters: None

Optional parameters: None

Example usage


getConfigRepositoryLocation

Get the directory path where the configuration repository is stored. The command returns the directory path. The product stores the configuration repository in the profile_root/config directory.

Target object: None

Required parameters: None

Optional parameters: None

Example usage


listCheckpoints

Get a list of existing checkpoints.

Target object: None

Required parameters: None

Optional parameters: None

Example usage

Example output


listCheckpointDocuments

Get a list of documents in a checkpoint repository. Provide a -checkpointName value to identify the checkpoint from which to get the list of documents.

Target object: None

Required parameters:

Optional parameters: None

Batch mode example usage

Interactive mode example usage

Example output


restoreCheckpoint

Restore the configuration repository back to the state it was in at the time a checkpoint was made. Provide a -checkpointName value to identify the full or delta checkpoint to restore.

Use a full checkpoint to restore the entire configuration repository back to the state it was in at the time the full checkpoint was made.

Use delta checkpoints to undo recent changes. Restore delta checkpoints only in the reverse order in which they were created. Each delta checkpoint has a sequence number. The highest sequence number represents the most recent delta checkpoint. Thus, restore delta checkpoints in descending sequence number only.

After the configuration repository is restored from a delta checkpoint, the product creates a checkpoint containing the configuration before restoration.

If the delta checkpoint we want to restore is the oldest saved checkpoint, we might need to increase the number of delta checkpoints. Run the getAutoCheckpointDepth command to find out how many delta checkpoints that the product keeps. After the number of delta checkpoints is reached, the product deletes the oldest delta checkpoint each time a new delta checkpoint is made. To increase the number of saved delta checkpoints, use the setAutoCheckpointDepth command.

When we restore a checkpoint, save conflicts occur if we have uncommitted changes in your workspace. The checkpoint gets restored, but the uncommitted changes are flagged as a save conflict when we attempt to save them. Also, if more than one user is working on configuration changes to the repository, then other users with uncommitted changes get save conflicts as well if one user performs a checkpoint restoration.

Target object: None

Required parameters:

Optional parameters: None

Batch mode example usage

Interactive mode example usage


setAutoCheckpointDepth

Specify the number of delta checkpoints to keep. If the number of saved delta checkpoints exceeds the specified checkpoint depth, the product deletes the oldest delta checkpoints, keeping no more than the specified checkpoint depth.

Target object: None

Required parameters:

Optional parameters: None

Batch mode example usage

Interactive mode example usage


setAutoCheckpointEnabled

Enable or disable automatic delta checkpoints. If automatic repository checkpoints are enabled, the product creates a delta checkpoint whenever a change is made to the configuration repository. A delta checkpoint compressed file contains the before and after versions of configuration files that have changed. We can extract the contents of the compressed file and then examine the extracted files to determine what has changed in the configuration.

After running setAutoCheckpointEnabled, we do not need to restart the server for the setting change to take effect.

Target object: None

Required parameters:

Optional parameters: None

Batch mode example usage

Interactive mode example usage


setCheckpointLocation

Set the directory path where checkpoints are stored. By default, the product stores checkpoints in the profile_root/checkpoints directory.

Target object: None

Required parameters:

Optional parameters: None

Batch mode example usage

Interactive mode example usage


  • Configure checkpoints
  • Restore checkpoints