Backing up a profile on i5/OS

After installing WebSphere Portal on IBM i5/OS, you can create a backup copy of your profile, which can then be used to restore your profile should something happen to your system.

To backup the profile, have a user profile with the following authorities:

To backup your profile using the appropriate task from the QShell session:

This script does not save any remote database schemas associated with the profile.

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

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

  3. Change to the /QIBM/ProdData/PortalExpress/V61/Tools directory.

  4. Enter one of the following tasks to back up your profile:

    Option Description
    Base profile, including profiles federated into a cluster saveProfile.sh parameters
    Network Deployment profile saveProfile.sh parameters

    Use the following parameters listed in the table with the above tasks; the following parameters are required:

    -profileName (-p)

    Name of the 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.

    -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.


    Table 1. Optional parameters for use with the script saveProfile

    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 /savRstWp60.

    -schemaList (-t)

    Specifies a list of schemas to save with the profile. By default, the command saves all Workplace schemas associated with the profile.

    If this parameter is used, the script will ONLY save the schemas listed.

    Separate listed schemas with commas and no spaces.

    -noHttp (-n)

    Do not save external HTTP data.

    -cancelRestart (-c)

    Cancel restart of Workplace servers. By default, all Workplace servers are restarted after the command is run.

    -propFilePath (-r)

    Path to the savRstWp.properties file to be used for parameter input to this command. To use this parameter, first copy the file /QIBM/ProdData/PortalExpress/V61/Tools/sh_utils/savRstWp.properties to a new location in the Integrated File System (IFS) on which you are backing up the profile, and then edit it to include the parameters you want to use.

    You must save the file with the name savRstWp.properties. .

    -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.

    When the command is run, a message displays indicating the backup operations being performed. For a remote database, this message includes information on the remote system and the remote database schemas being used. The saveProfile.sh script does NOT back up remote database schemas. You must run an additional script to back them up. Look for a message similar to the following to determine which remote system and remote database schemas are being used:

    Remote iSeries database server is being used. List of libraries (schemas)              to save on myserver.myco.com:                                                 
                                                                                            WCS34JHB WCS34JHB1 WCS34JHB2 WCS34JHB3 WCS34JHB4 WCS34JHB5   
    


Examples

saveProfile.sh -profileName wcs01 -mediaDevice tap01 -logDir /mylog -forceDown

In this example, profile wcs01 is backed up to media device tap01. Log files are saved to the /mylog directory. Because the -f parameter is specified, all servers associated with the profile are stopped.

saveProfile.sh -v -p wcs01 -m tap01 -l /mylog -f

This example is the same as the previous example, except that short parameter names are used and the -v parameter is specified to verify what the command will do before running it.

saveProfile.sh -p wcs01 -s mysavlib -t wcs01,wcs01lms,wcs01lds,wcs01msg,wcs01com,wcs01wps,mylib01

In this example, the -t parameter is used to back up the profile with a list of schemas specified by the user. In this example, the command does not save any schemas other than those listed.

saveProfile.sh -r /myprops -l /mylog

In this example, the command pulls parameter information from the savRstWp.properties file, which the user has previously saved in the /myprops directory.

The path does NOT include the file name. You can override parameters in the savRstWp.properties file by specifying them on the command line.

ADDJOBSCDE JOB(WPSBACKUP) CMD(QSH CMD('/qibm/proddata/portalexpress/v61/tools/sh_utils saveProfile.sh -p wcs01 -s mysavlib')) FRQ(*WEEKLY) SCDDATE(*NONE) SCDDAY(*SUN) SCDTIME('23:30:00')

In this example, the i5/OS command Add Job Schedule Entry (ADDJOBSCDE) is used to make the saveProfile.sh script run on a regular schedule. The ADDJOBSCDE command must be run from an i5/OS command line. In this example, the script is run with a job name (JOB) of WPSBACKUP on a frequency (FRQ) of once per week with a schedule day (SCDDAY) of Sunday and a schedule time (SCDTIME) of 11:30 p.m.

For information on the ADDJOBSCDE command and its parameters, see the IBM eServerâ„¢ i5 Information Center.


Parent topic:

Backing up and restoring profiles