![]() | |
|
manageprofiles command
Use the manageprofiles
command to create, delete, augment, back up, and restore profiles, which define runtime environments. Using
profiles instead of multiple product installations saves disk space and simplifies updating the product because a single set of core
product files is maintained.
The manageprofiles
command and its graphical user interface, the "Profile Management Tool", are the only ways to create runtime
environments.
The command file is located in the app_server_root/bin
directory. The command file is a script named manageprofiles.sh
.
The manageprofiles.sh
command is used to perform the following tasks:
create a profile (-create
)
delete a profile (-delete
)
augment a profile (-augment
)
unaugment a profile (-unaugment
)
unaugment all profiles that have been augmented with a specific augmentation template (-unaugmentAll
)
delete all profiles (-deleteAll
)
list all profiles (-listProfiles
)
list augments for a profile (-listAugments
)
get a profile name (-getName
)
get a profile path (-getPath
)
validate a profile registry (-validateRegistry
)
validate and update a profile registry (-validateAndUpdateRegistry
)
get the default profile name (-getDefaultName
)
set the default profile name (-setDefaultName
)
back up a profile (-backupProfile
)
restore a profile (-restoreProfile
)
perform manageprofiles command tasks that are contained in a response file (-response
)
Parameters:
-backupProfile
Performs a file system backup of a profile folder and the profile metadata from the profile registry file. Any
servers using the profile that you want to back up must first be stopped prior to invoking the manageprofiles command
with the -backupProfile
option. The -backupProfile
parameter must be used with the
-backupFile
and -profileName
parameters, for example:
manageprofiles.sh -backupProfile -profileName profile_name -backupFile backupFile_name
When you back up a profile using the -backupProfile
option, you must first stop the server and the
running processes for the profile that you want to back up.
-backupFile backupFile_name
Backs up the profile registry file to the specified file. You must provide a fully qualified file path for the backupFile_name
.
-restoreProfile
Restores a profile backup. Must be used with the -backupFile
parameter, for example:
manageprofiles.sh -restoreProfile -backupFile file_name
To restore a profile, perform the following steps:
Stop the server and the running processes for the profile that you want to restore.
Manually delete the directory for the profile from the file system.
Run the -validateAndUpdateRegistry
option of the manageprofiles.sh
command.
Restore the profile by using the -restoreProfile
option of the manageprofiles.sh
command.
backupConfig command
The backupConfig.sh
command is a simple utility to back up the configuration of your node to a file.
By default, all servers on the node stop before the backup is made so that partially synchronized information is not saved. If you do not have root authority, you must specify a path for the backup file in a location where you have write permission. The backup file will be in zip format and a .zip extension is recommended.
In a UNIX or Linux environment, the backupConfig.sh
command does not save file permissions or ownership information. The
restoreConfig.sh
command uses the current umask
and effective user ID (EUID) to set the permissions and ownership when restoring
a file. If it is required that the restored files have the original permissions and ownership, use the tar
command (available on all UNIX or
Linux systems) to back up and restore the configuration.
Issue the command from the profile_root/bin
directory.
The command syntax is as follows:
backupConfig.sh [backup_file] [-nostop] [-quiet] [-logfile <filename>] [-replacelog] [-trace] [-username <username>] [-password <password>] [-profileName <profile>] [-help]
The backup_file
parameter specifies the file where the backup is to be written. If you do not specify a backup file name, a unique name is
generated and the file is stored in the current directory. If you specify a backup file name in a directory other than the current directory, the
specified directory must exist.
restoreConfig command
Use the restoreConfig.sh
command to restore the configuration of your node after backing up the configuration using the
backupConfig.sh
command.
The restoreConfig.sh
command is a simple utility to restore the configuration of your node after backing up the configuration using the
backupConfig.sh
command. By default, all servers on the node stop before the configuration restores so that a node synchronization does
not occur during the restoration. If the configuration directory already exists, it is renamed before the restoration occurs.
The backupConfig.sh
command does not save file permissions or ownership information. The restoreConfig.sh
command uses the current
umask
and effective user ID (EUID) to set the permissions and ownership when restoring a file. If it is required that the restored files have
the original permissions and ownership, use the tar
command (available on all UNIX or Linux systems) to back up and restore the configuration.
Issue the command from the profile_root/bin
directory.
The command syntax is as follows:
restoreConfig.sh backup_file [-location restore_location] [-quiet] [-nostop] [-nowait] [-logfile <filename>] [-replacelog] [-trace] [-username <username>] [-password <password>] [-profileName <profile>] [-help]
If the configuration to be restored exists, the config
directory is renamed to config.old
(then config.old_1
, etc.) before the restore begins. The command then restores the entire contents of the
profile_root/config
directory.
![]() ![]() ![]() |