Backing up the HTTP server

This topic provides instructions on backing up instance data for HTTP servers associated with a profile on IBM i5/OS using the saveHttpInstance script.

To back up HTTP server data:

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

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

  3. Enter the saveHttpInstance.sh parameters command to back up the HTTP data associated with a particular profile. Use the following parameters listed in the table with the above task; the following parameters are required:

    -profileName (-p)

    Name of the profile whose HTTP server data you want 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 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 saveHttpInstance

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

    -nd

    Indicates that the profile is a Network Deployment profile.

    -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

saveHttpInstance.sh -profileName wps01 -mediaDevice tap01

In this example, HTTP servers associated with profile wps01 are saved to media device tap01.

saveHttpInstance.sh -v -p wps01 -m tap01

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.


Parent topic:

Backing up and restoring profiles