# Administrator Guide

# Managing HiPer for Retail

## Initial Set Up

There are some steps you must perform after you install HiPer for Retail before users can start using the application. Perform the following steps after you complete the steps in the Installation and Upgrade Guide for AquaLogic HiPer Workspace for Retail:

1. Configure and run a Profile Web Service to import user information into the portal for use by HiPer for Retail. For details, see Configure the Profile Web Service (PWS).
2. Configure activity rights to give users access to HiPer for Retail features. For details, see Assign HiPer for Retail Activity Rights.
3. Create any necessary groups and set security on imported HiPer for Retail portal objects. For a list of portal objects for which you might want to change security, see HiPer for Retail Portal Objects.
4. Create any necessary subportals to display the appropriate HiPer for Retail user interface to your users. There are two sample subportals imported with the HiPer for Retail portal objects. For details on creating a subportal, refer to portal online help.
5. Create rule templates on which to base rules in HiPer for Retail. For details, see Defining Rule Templates in the ALI HiPer BAM System
6. Optionally, you can customize the HiPer for Retail user interface. For details, see Customizing the User Interface

## Configure the Profile Web Service (PWS)

HiPer for Retail depends heavily on user properties. These properties include the hierarchical level of the user, the user's role, and the store name. You must create one or more Profile Web Services (PWSs) to import that information into the portal.

Note: | There is a sample PWS that can import the appropriate properties from an Excel file.

You need to map User Extended Object Data (EOD) to HiPer-for-Retail-specific user properties. HiPer for Retail uses these properties to build the geographic hierarchy and the organizational hierarchy and to complete dynamic group selection. Here are the HiPer for Retail user properties you can map (bolded properties are required):

Table 2-1 HiPer for Retail User Properties
HiPer for Retail User Property | Map to...
--- | ---
HiPer ID | any unique user ID you choose. For example, if your company uses employee IDs, you probably want to map to those. HiPer for Retail uses this value to identify the user.
HiPer Manager ID | the HiPer ID of the person to which this user reports.
HiPer Level 1 | the top level in your company's geographic hierarchy. All HiPer for Retail users must have the same Level 1 value. HiPer for Retail uses the values for the geographic levels to create notification lists. These values display on the Summary page.
HiPer Level 2 | the second level in your company's geographic hierarchy.
HiPer Level 3 | the third level in your company's geographic hierarchy.
HiPer Level 4 | the fourth level in your company's geographic hierarchy.
HiPer Level 5 | the fifth level in your company's geographic hierarchy.
HiPer Level 6 | the sixth level in your company's geographic hierarchy.
HiPer Level 7 | the seventh level in your company's geographic hierarchy.
HiPer Level 8 | the eighth level in your company's geographic hierarchy.
HiPer Role | the role the user plays within the organization (for example, Operations Manager, General Manager). This value displays in the Select Users and Groups dialog box.
HiPer Store Department | the department in which the user works within the store. This value displays in the Select Users and Groups dialog box.
HiPer Store ID | the unique store ID for the store in which the user works. HiPer for Retail uses this value to roll up task information.
HiPer Store Name | the name of the store in which the user works. This value displays the HiPer for Retail user interface.
HiPer Store Type | the type of store in which the user works. HiPer for Retail uses this value for additional categorization in the Select Users and Groups dialog box.

## Assign HiPer for Retail Activity Rights

You must assign the activity rights in the portal to give your users access to HiPer for Retail features.

To assign activity rights:

1. In the portal, click Administration.
2. In the Select Utility menu, select Activity Manager.
3. Click the activity right you want to assign and grant the appropriate groups the right.

The following activity rights are available:

Table 2-2 HiPer for Retail Activity Rights
Activity Right | Description
--- | ---
HiPer: Administer HiPer | Allows users to access the HiPer Administration Utility (with which they can configure HiPer for Retail system settings and migrate objects).
HiPer: Administer Announcement Folders | Allows users to create and modify announcement folders. This right does not affect the ability to create announcements. If a user does not have this activity right the create folder button will not be displayed in the Announcements hierarchy.
HiPer: Administer Object Folders | Allows users to create, edit, and delete object folders (for system notifications, rules, and task list templates). If a user does not have this activity right the create folder, edit, and delete buttons will not be displayed in the associated hierarchy.
HiPer: Administer Rules | Allows users to manage Rules from the notifications page. This includes creating, editing, and deleting rules. If a user does not have this activity right the Rules folder will not be displayed on the Notifications tab page.
HiPer: Administer System Notifications | Allows users to create system notifications. This includes creating, editing, and deleting system notifications. If a user does not have this right the System Notifications folder will not be displayed on the Notifications tab page.
HiPer: Administer Task List Templates | Allows users to create task list templates. This includes creating, editing, and deleting task list templates. If a user does not have this right the Task List Templates folder will not be displayed on the Notifications tab page.
HiPer: Approve Tips | Allows users to approve tips created by users below them hierarchically. If a user does not have this right the Manage Tips folder will not be displayed on the Tips tab page.
HiPer: Create Announcements | Allows users to create and publish announcements. If a user does not have this right the Announcements tab will not be displayed.
HiPer: Create Documents | Allows users to upload documents. If a user does not have this right the Upload button will not be displayed on the Documents tab page.
HiPer: Create Manual Notifications | Allows user to create and send manual notifications. If a user does not have this right the Create Manual Notification button will not be displayed on the Notifications tab page.
HiPer: Create Tips | Allows users to create tips. These tips need to be approved before they display to other users. If a user does not have this right the My Tips folder will not be displayed on the Tips tab page.
HiPer: View Low Resolution Page | Allows users to view pages designed for low resolution displays. If a user does not have this right, the standard display page will be shown.
HiPer: View Summary Page | Allows users to view the Summary page. If a user does not have this right the Summary tab will not be displayed.

## HiPer for Retail Portal Objects

The following are some of the portal objects you might need to work with. They were created in the Application Spaces : HiPer portal folder when you imported the HiPer for Retail .pte files into the portal.

Table 2-3 HiPer for Retail Portal Objects
Object | Description
--- | ---
HiPer Portal Remote Server | Points the portal to the location of the machine that hosts the HiPer for Retail software.
HiPer Dynamic Group Update External Operation and Job | Synchronizes users with the dynamic notification lists in HiPer for Retail. The job runs nightly (it is process intensive). For more information, refer to Synchronize the Dynamic Notification Lists.
HiPer Flat Hierarchy Update External Operation and Flat Hierarchy Update Job | Builds the organizational hierarchy for each user in the HiPer for Retail application. For more information, refer to Synchronize the Flat Hierarchy.
HiPer Notification Delivery External Operation and Send Notifications Job | Sends system and manual notifications. For more information, refer to Send Notifications.
Run Tip Synchronization Job | Searches the Publisher repository and synchronizes the tips with the HiPer for Retail database. For more information, refer to Synchronize Tips.
Communities Folder (contains communities, and their associated community templates and page templates)
The communities in this folder provide the structure and portlets for the HiPer for Retail pages.
Users and Groups Folder
hiperannounceuser | User that performs internal search to display the appropriate announcements to HiPer for Retail users.
All HiPer Users | Group of all users that have access to HiPer for Retail.
HiPer Dynamic Group Administrators | Only the hiperannounceuser should be in this group. This folder must exist to store dynamic groups.
HiPer Store Operations Users | Provides access to all HiPer for Retail features (displays the Summary page and grants all HiPer activity rights).
Dynamic Groups Folder (in the Users and Groups Folder)
When users send announcements to a notification list, dynamic portal groups are created (in the background) and stored in this folder. The HiPer Dynamic Group Administrators group should have edit rights to this folder so it can create these dynamic groups.
Subportal Manager
HiPer Store Manager Subportal | Displays the Notifications page as the home page.
HiPer Store Operations Manager | Displays the Summary page as the home page.

### Celequest Reportlets

Celequest reportlets can be added to the Summary page like any other portlet. Reportlets are Flash objects that can be embedded into a custom portlet. HiPer for Retail includes the following samples to help you create your own reportlets:

- hiperportlets/portlets/reportlets/reportlet.jsp
  This file supplies sample reportlet code.
- hiperportlets/portlets/reportlets/celequest_reportlet_user_prefs.jsp
  This file supplies a sample user preferences page to select a given reportlet and set the Celequest connection information.

For more information on reportlets and how to set up the samples, refer to Celequest documentation.