# Administrator Guide

# Maintaining HiPer for Retail

This chapter describes the tasks you might have to perform to maintain your HiPer for Retail deployment.

## Create Additional Custom Categories

You might need to create additional categories for notifications and tips in the HiPer for Retail database as your HiPer for Retail deployment matures. For details, refer to the Installation and Upgrade Guide for AquaLogic HiPer Workspace for Retail.

## Update the Mapping of Your Company's Hierarchical Levels

If your company's hierarchical structure changes, you might have to update the mappings in the HiPer for Retail database. For details, refer to the Installation and Upgrade Guide for AquaLogic HiPer Workspace for Retail.

## Synchronize Tips

Occasionally the tips that display in HiPer for Retail might not match the tips that are stored in Publisher. If this occurs, you can run the Run Tip Synchronization job to synchronize the systems again.

The Run Tip Synchronization job is located in the Application Spaces : HiPer portal folder. It is not set to run on a regular basis because you should rarely have to run the job. Here are some of the reasons you might need to run the Run Tip Synchronization job:

- You rescript your HiPer for Retail database but do not rescript Publisher. Because tips are stored in both locations, this job will synchronize the Publisher tips into HiPer for Retail.
- You import Publisher tips from a development system to a production system and the HiPer for Retail production system does not have the newly imported tips in the system. You will lose all associated comments and ratings when importing these tips because there is no reference to them in the Publisher import package.
- Publisher publishing of content items might result in errors with the Search Service that may not be indexed properly. These discrepancies may be cleared up by running the synchronizer.

## Synchronize the Flat Hierarchy

If you change the configuration setting for Top Level Manager (refer to HiPer Configuration Settings), you must perform the following steps to make sure that your users receive correct hierarchy information:

1. In the HiPer for Retail database, delete all rows from the RTFLATHIERARCHY table.
2. Run the Flat Hierarchy Update Job (located in the Application Spaces : HiPer portal folder).

Running the job without deleting all rows performs a simple update. However, changing the Top Level Manager changes the entire organization hierarchy, so by deleting all rows from the table, you are essentially forcing a resynchronization of the entire Flat Hierarchy.

## Synchronize the Dynamic Notification Lists

The notification lists in HiPer for Retail are dynamic lists of users created by filtering user lists by selected user properties. Notification lists must occasionally be updated, adding and removing users as appropriate. The update is accomplished through the HiPer Dynamic Group Update Job (located in the Application Spaces : HiPer portal folder). Because this job is resource intensive, it is set to run every two hours.

## Send Notifications

When a user sends a manual notification or a system notification is triggered, the notification is put into a queue. The queued notifications are sent when the Send Notifications job runs. The Send Notifications job is located in the Application Spaces : HiPer portal folder. By default, the job is set to run every thirty minutes.

## HiPer Administration

When you run the HiPer for Retail installer on the machine that hosts HiPer for Retail, a new option displays in the Select Utility menu in the Administration area of the portal—HiPer Administration. HiPer Administration allows you to configure certain global settings for HiPer for Retail and allows you to migrate HiPer for Retail information from one system to another.

### HiPer Configuration Settings

The HiPer Configuration Settings page allows you to configure certain global settings for HiPer for Retail.

To display the HiPer Configuration Settings page:

1. Click Administration.
2. In the Select Utility menu, select HiPer Administration.

#### Main Settings

After initial set up, you will only need to change these settings if your organization hierarchy changes.

1. In the Top Level Manager box, type the HiPer Manager ID (this is not the same as the HiPer ID) of your company's highest level employee (for example, your CEO). A user with this manager ID has no managers and is considered the 'root' of the organization.

Caution: | Changing the Top Level Manager changes the entire organization hierarchy. Therefore, you must update the database when you change this setting. For details, see Synchronize the Flat Hierarchy.

2. In the Level 1 Value box, type the name of the Level 1 user property. All HiPer for Retail users must have this value set.

#### Celequest Administrative Preferences

You must configure these settings after you install HiPer for Retail. You will only need to change them if you change the location of the ALI HiPer BAM System (Celequest) or change the ALI HiPer BAM System user or password.

1. In the Celequest Server box, type the location of the ALI HiPer BAM System (for example, http://servername:8083/bam).
2. In the User Name box, type the user name for the ALI HiPer BAM System.
3. In the Password and Confirm Password boxes, type the password for the ALI HiPer BAM System user.

#### Document Administrative Preferences

These settings determine what the document hierarchy looks like on the Documents page of HiPer for Retail. You will only need to change these settings if you want to change the Documents hierarchy in HiPer for Retail.

1. In the Document Folder UUID box, type the UUID for the top level document folder in the Documents hierarchy.
2. In the Max Number of Folders box, type the maximum number of folders that should display in the Documents hierarchy.
3. In the Max Number of Files box, type the maximum number of documents that should display in the Documents hierarchy.
4. In the Minutes box, type the number of minutes the Documents hierarchy should display before requesting updated information from the portal.

#### Announcements

You will only need to change these settings if you change the Announcements user or password.

1. In the User Name box, type the user name for the Announcements user (the default is
   hiperannounceuser). For more information, refer to HiPer for Retail Portal Objects.
2. In the Password and Confirm Password boxes, type the password for the Announcements user.

#### Archive Preferences

HiPer for Retail can automatically move closed notifications from a user's Manage folder to the Archive folder. By default, any closed notifications with a due date older than six months are archived. To change the duration before archiving, in the Archive notifications older than box and drop-down list, type a number and select a period specifying the new duration.

#### Pagination Preferences

If a list in HiPer for Retail spans multiple pages, users see page links at the bottom of the list to access more items. The number of page links that display depends on the pagination preferences. By default, 10 page links display. To change the number of links displayed, in the Display pages to a maximum of box, type a number corresponding to the number of page links you want to display. For example, assume there are 15 pages of items, if you specified that you want to display a maximum of 10 pages, users will see links for pages 1 through 10 and a Next link to display the next group of pages.

### HiPer Migration Utility

The HiPer Migration Utility allows you to migrate objects from one HiPer for Retail system to another.

To display the HiPer Migration Utility:

1. Click Administration.
2. In the Select Utility menu, select HiPer Administration.
3. Click the HiPer Migration Utility tab.

#### Important Migration Considerations

Before you migrate HiPer for Retail objects, consider the following:

- You must migrate dependent objects (for example, a system notification needs a rule and it might also include tasks or tips). When you select an object that has dependent objects, the dependent objects are automatically selected.
- The HiPer Migration Utility only migrates the association between a tip and a system notification. Tips themselves must be migrated with the Portal Migration Utility or the Portal Export Utility. You must import the tips before you import the tip associations if you want to preserve the associations.
- Tasks can only be migrated as dependencies of system notifications or task list templates.
- Users cannot be migrated. You must reassociate users with system notifications after import.

#### Migrating an Entire HiPer for Retail System

HiPer for Retail makes use of its own objects as well as other portal objects. Therefore, you must migrate those additional portal objects for the migrated HiPer for Retail objects to work correctly.

To migrate an entire HiPer for Retail system, perform the following steps:

1. Migrate content items and dynamic groups used by HiPer for Retail. You must migrate the Hiper Content Items folder from Publisher and the following portal groups folder from the portal administrative objects directory: Application Spaces : HiPer : Users and Groups : Dynamic Groups.

- If you are running Plumtree Content Server 6.1, use the Portal Migration Utility. Refer to the migration instructions in the Administrator Guide for Plumtree Content Server 6.1.
- If you are running Plumtree Publisher 6.2, use the Portal Export Utility. Refer to the migration instructions in the Administrator Guide for Plumtree Publisher 6.2.

The migration package will contain a .zip file with the content items and a .pte file with the dynamic groups. Follow the migration instructions to import the content into the target portal.

2. In the destination portal, run the Tip Synchronizer job to synchronize any new and existing tips.
3. In the source portal, use the HiPer Migration Utility to export the HiPer for Retail objects. Refer to online help for instructions on using the HiPer Migration Utility.
4. In the destination portal, use the HiPer Migration Utility to import the HiPer for Retail objects. After the objects have been imported, the import status displays. Read through the status carefully to understand what actions were taken and if there is anything more you must do (for example, if you import a rule that does not exist in the target system, the HiPer Migration Utility attempts to create the rule from the associated rule template in the target ALI HiPer BAM System. If the associated rule template is not found, the import status informs you that you must manually create the rule template in the BAM system and repair the rule in HiPer for Retail. Remember that you must reassociate users with any imported system notifications.

Caution: | If any objects fails, the entire import is aborted.

5. In the destination portal, run the Hiper Dynamic Group Update job.

Note: | If you are only migrating HiPer for Retail objects, no portal objects (no tips or announcements) you can skip steps 1, 2, and 5.