Sunday, 10 November 2013

Procedure to Backing up Websphere Application Profiles

Open the command prompt.
Browse to the <was_home>\bin directory. For example, you can type the following: cd <was_home>\bin For example:
cd c:\Program Files\IBM\WebSphere\AppServer\bin

Use the WebSphere Application Server manageprofiles command with the backupProfile parameter.
manageprofiles.bat -backupProfile -profileName <profile_name> -backupFile <backupFile_name>

Stand-alone

manageprofiles.bat -backupProfile -profileName AppSrv01 -backupFile c:\backup\AppSrv01.zip
for example

C:\ProgramFiles\IBM\WebSphere\AppServer\profiles\AppSrv01\bin>backupConfig.bat C:\was-setup\AppSrv01_backup.zip -logfile backup.log

Network deployment

manageprofiles.bat -backupProfile -profileName Dmgr01 -backupFile c:\backup\Dmgr01.zip


Parameters
The following options are available for the backupConfig command:

-nostop
Tells the backupConfig command not to stop the servers before backing up the configuration

-quiet
Suppresses the progress information that the backupConfig command prints in normal mode

-logfile file_name
Specifies the location of the log file to which trace information is written
By default, the log file is named backupConfig.log and is created in the logs directory.


-profileName profile_name
Defines the profile of the application server process in a multi-profile installation
The -profileName option is not required for running in a single-profile environment. The default for this option is the default profile.

-replacelog
Replaces the log file instead of appending to the current log

-trace
Generates trace information into the log file for debugging purposes

-username user_name
Specifies the user name for authentication if security is enabled in the server

-user user_name
Specifies the user name for authentication if security is enabled in the server; acts the same as the -username option

-password password
Specifies the password for authentication if security is enabled in the server

No comments:

Post a Comment