Back up the Deployment Manager profile on IBM i

Back up the Deployment Manager profile on IBM i

Back up the Deployment Manager profile in a clustered environment on IBMi using the saveNdDm script.
To back up the Deployment Manager profile:
Restriction: You can only use this task if you created the dmgr profile using the default /QIBM/UserData/Websphere/AppServer/V7/ND/profiles directory.

Write down the current WebSphere Portal administrator password as you will need to supply this information if you restore to this backup.

Type STRQSH on the command line to start the QShell Interpreter.

Change to the /QIBM/ProdData/WebSphere/PortalServer/V7/product_offer/Tools directory. product_offer is either Server or Content, depending on the product offering that you purchased.

Enter the saveNdDm.sh parameters command to back up the Deployment Manager profile.
Use the following parameters listed in the table with the above task; the following parameters are required:
-profileName (-p)
Name of the Deployment Manager profile to save

-mediaDevice (-m) or -saveFileLib (-s)
Specifies a media device to save to or a library where saved files are created to save the data The library name must be 10 characters are less.

-userName (-u)
Enter the user name for the WAS Administrative account. This is required to stop the server1 server.

-password (-w)
Enter the password for the WAS Administrative account user name. This is required to stop the server1 server.

-forceDown (-f)
Stops the servers associated with the profile; for example WebSphere_Portal and the HTTP server If you do not enter this parameter, manually stop the servers before running this task.
Parameter names are case-sensitive.

Parameter Description
-help (-h) Displays help for the command.
-logDir (-l) Specifies where to save log files for this command. If a log directory is not specified using this parameter, logs are created by default in /savRstWp7/profile/logs, where profile is the name of the profile whose data is being saved. If you specify a path using this parameter, the command will create only the last directory in the path. The other directories in the path must already exist. For example, if you specify -l /wcs01/logs, the /wcs01 directory must already exist.
-cancelRestart (-c) Cancel restart of servers. By default, all the servers will be restarted.
-verify (-v) Verifies the command. If this parameter is used, the command outputs what would be done according to the parameters being used, without actually performing the backup.

Examples

saveNdDm.sh -profileName wp01 -mediaDevice tap01 -cancelRestart
In this example, Deployment Manager profile wp01 is saved to media device tap01. Servers are not restarted after saving the profile.

saveNdDm.sh -v -p wp01 -m tap01 -c
This example is the same as the previous one, except the parameter short names are used and the -v parameter is specified to verify what the command will do before running it.

Related tasks

Prepare the WAS Deployment Manager on IBM i January 4, 2012
2012/01/04 v7. Edition 2: Second edition includes corrections a... 2011/12/17 v7. Edition 2: Second edition includes corrections a... 2011/12/15 documentation refresh

+
Search Tips | Advanced Search

Parameter	Description
-help (-h)	Displays help for the command.
-logDir (-l)	Specifies where to save log files for this command. If a log directory is not specified using this parameter, logs are created by default in /savRstWp7/profile/logs, where profile is the name of the profile whose data is being saved. If you specify a path using this parameter, the command will create only the last directory in the path. The other directories in the path must already exist. For example, if you specify -l /wcs01/logs, the /wcs01 directory must already exist.
-cancelRestart (-c)	Cancel restart of servers. By default, all the servers will be restarted.
-verify (-v)	Verifies the command. If this parameter is used, the command outputs what would be done according to the parameters being used, without actually performing the backup.