Post-Installation

This chapter describes the following basic steps you take to configure and customize your AquaLogic HiPer Workspace for Retail deployment:

Create a connection between the BAM stem and the back-end systems you want to monitor. For details, see Integrate Your Back-End Systems with the ALI HiPer BAM System.
Configure the delivery profile in the ALI HiPer BAM System so that alerts are correctly sent to HiPer for Retail. For details, see Configure the ALI HiPer BAM System to Communicate with HiPer for Retail.
Set up the HiPer for Retail database:

Run the database scripts to create the HiPer for Retail tables and load seed data into them. For details, see Run the HiPer for Retail Database Scripts.
Create categories for notifications and tips to help users find what they need. For details, see Create Custom Categories for Notifications and Tips.
Show HiPer for Retail how the information returned by the ALI HiPer BAM System relates to your company's hierarchical levels. For details, see Map ALI HiPer BAM System Levels to Your Company's Hierarchical Levels.

Import the HiPer for Retail information into Publisher. For details, see Migrate HiPer for Retail Information Into (Publisher).
Configure HiPer for Retail in the Administrative Portal:

Import the portal objects needed by HiPer for Retail. For details, see Import HiPer for Retail Portal Objects.
Configure the ALI HiPer BAM System connection information. For details, see Configure the ALI HiPer BAM System Connection Information.
Add the HiPer folder to the Automation Service to run HiPer for Retail jobs. For details, see Configure the Automation Service to Run HiPer for Retail Jobs.
Grant data source access to HiPer for Retail users so they can upload documents. For details, see Grant Data Source Access to HiPer for Retail Users.

Perform the initial set up described in the Administrator Guide for AquaLogic HiPer Workspace for Retail.

Configure and run a Profile Web Service to import user information into the portal for use by HiPer for Retail.
Configure activity rights to give users access to HiPer for Retail features.
Create any necessary groups and set security on imported HiPer for Retail portal objects.
Create any necessary subportals to display the appropriate HiPer for Retail user interface to your users.
Create rule templates on which to base rules in HiPer for Retail.
Optionally, you can customize the HiPer for Retail user interface.

Integrate Your Back-End Systems with the ALI HiPer BAM System

You must set up the ALI HiPer BAM System (Celequest) to communicate with your back-end systems (for example, an inventory database). The ALI HiPer BAM System can be integrated using several methods including TIBCO, JMS, and Web Services, but the following example describes the ALI HiPer BAM System communicating with a SQL database via a JDBC connection.

Create a context-ds.xml file in the <BAM_system_home>\jboss\server\default\deploy directory. Here is an example of the contents of that file:

<?xml version="1.0" encoding="UTF-8"?>

<datasources>

 <no-tx-datasource>

	   <jndi-name>com.bea.context</jndi-name>

	   
<connection-url>jdbc:microsoft:sqlserver://hiper:1433;SelectMethod=curs
or;databaseName=CFPortalDB;user=portaldbuser;password=portalpassword</c
onnection-url>

	   
<driver-class>com.microsoft.jdbc.sqlserver.SQLServerDriver</driver-clas
s>

      <!-- The login and password -->

      <user-name>portaldbuser</user-name>

      <password>portalpassword</password>

      <min-pool-size>5</min-pool-size>

      <max-pool-size>20</max-pool-size>

      <idle-timeout-minutes>5</idle-timeout-minutes>

      <track-statements>false</track-statements>

      <application-managed-security/>

   </no-tx-datasource>

</datasources>

After you create the context, restart the JBoss server. After restarting the server, the data source will appear in the ALI HiPer BAM System user interface. Next, you need to create an agent.
Log in to the ALI HiPer BAM System. For more information on any of the following steps, refer to Celequest documentation and online help.
Click the Administration Console tab.
Under Name, click Agents.

Figure 4-1 Agents

Agents

Click New Agent.
In the Edit Agent dialog box, create an agent that can talk to the back-end system.

Figure 4-2 Edit Agent Dialog Box

Edit Agent Dialog Box

Click OK to save your agent definition.
Repeat Steps 1-8 to create an agent for each back-end system that you want to monitor with the ALI HiPer BAM System.

Configure the ALI HiPer BAM System to Communicate with HiPer for Retail

When a rule is triggered within the ALI HiPer BAM System (Celequest), a SOAP message is sent. You must configure a delivery profile in the ALI HiPer BAM System so that HiPer for Retail receives the message. When HiPer for Retail receives a message, it determines if there are any notifications associated with the triggered rule. If there are associated notifications, they are sent to the appropriate users.

Perform the following steps on the machine that hosts the ALI HiPer BAM System to configure the delivery profile:

Log in to the ALI HiPer BAM System as "system." For more information on any of the following steps, refer to Celequest documentation and online help.
Click Account Settings.
In the Edit User dialog box, click the Delivery Profiles tab.
Click Create Additional Profiles.
Select web service as the profile type.
In the Profile Name box, type a name such as "<hiperserver> Web Server."
In the Web Service URL box, type a URL of "http://<hiperserver>:<port>/hiperportlets/faces/portlets/webservice/web_service_endpoint.jsp."
In the Method box, type "post."
Leave the Username and Password boxes blank, but select automatically add the profile to new alerts.
Delete the existing E-mail delivery profile.

Set Up the HiPer for Retail Database

Perform the steps in this section to set up and customize your HiPer for Retail database.

Run the HiPer for Retail Database Scripts

Run the database scripts that were installed on the machine that hosts HiPer for Retail. The scripts are located in the HiPer for Retail install directory (for example, C:\Program Files\plumtree\pthiper\1.1\sql).

If you are using Oracle, you must set the NLS_LANG variable:

In Windows, set NLS_LANG=<oracle defined locale>.<charset>. For example:
set NLS_LANG=AMERICAN_AMERICA.UTF8
In Linux, export NLS_LANG=<oracle defined locale>.<charset>. For example:
export NLS_LANG=AMERICAN_AMERICA.UTF8

Run the scripts appropriate for your database software:

For Microsoft SQL Server, run the scripts in \mssql.
For Oracle on Windows, run the scripts in \oracle_nt.
For Oracle on Linux, run the scripts in \oracle_unix.

Run the scripts in the following order:

If you are using Oracle, review the path and variables used in create-tablespace.sql, then run the script as a user that has sysdba rights. You must run this script before you run any other scripts.
create-tables.sql
load-seed-info.sql
triggers.sql

Create Custom Categories for Notifications and Tips

When users create notifications and tips they can choose categories that help other users understand what the notification or tip is regarding. In the RTBUSCATEGORIES table, you must create categories that are appropriate for your company. Use the Installation and Planning Worksheets for HiPer for Retail to plan your categories.

Map ALI HiPer BAM System Levels to Your Company's Hierarchical Levels

When the ALI HiPer BAM System sends an alert to HiPer for Retail, HiPer for Retail needs to understand how the information in the alert relates to HiPer for Retail users so that it can correctly determine which users to notify. HiPer for Retail determines the appropriate users by querying users' EOD (Extended Object Data) properties in the portal.

For example, create a notification to send to all General Managers when a region's profit dips below 5%. If the West region profit dips, the ALI HiPer BAM System alerts HiPer for Retail of the change, including the fact that the change occurred in the West region. HiPer for Retail refers to the notification and determines that in this situation a message should be sent to all General Managers, limited by the region.

To allow HiPer for Retail to understand how the EOD properties in the portal relate to the levels in the ALI HiPer BAM System, you must modify the BAMNAME column values in the RTPROPERTYMAPPING table to match your company's hierarchical levels (for example, Level 2=Region). Use the Installation and Planning Worksheets for HiPer for Retail to plan your levels.

Migrate HiPer for Retail Information Into (Publisher)

Copy the .zip file from the computer that hosts HiPer for Retail, in pthiper\1.1\serverpackages, to the appropriate migration folder:

For Content Server 6.1, place the .zip file in ptcs\6.1\settings\migration.
For Publisher 6.2, place the .zip file in ptcs\6.2\settings\migration.

Configure HiPer for Retail on the Administrative Portal

Import HiPer for Retail Portal Objects

During the install an import package (hiper_package.pte) was created in
pthiper\1.1\serverpackages. You must import the package to create the portal objects needed by HiPer for Retail.

Configure the ALI HiPer BAM System Connection Information

Use the HiPer Configuration Utility in the portal to set up the ALI HiPer BAM System (Celequest) information:

In the portal, click Administration.
In the Select Utility menu, click HiPer Administration.
On the HiPer Configuration Settings page, under Celequest Administrative Preferences:

In the Celequest Server box, type the URL for your ALI HiPer BAM System (for example, http://<bamserver>:<port>/bam).
In the User Name, box, type the name of the user who will control the ALI HiPer BAM System (for example, system).
In the Password and Confirm Password boxes, type the password for the ALI HiPer BAM System user (for example, manager).

When you are done, click OK.

Configure the Automation Service to Run HiPer for Retail Jobs

To learn about these jobs, refer to the Administrator Guide for AquaLogic HiPer for Retail.

Add the HiPer folder to the Automation Service, so that HiPer for Retail jobs will run:

In the portal, click Administration.
In the Select Utility menu, click Automation Service.
Add the HiPer folder to an existing Automation Service or create a new one (refer to Portal online help for details) and register the following folder: Admin Objects Directory : Application Spaces : HiPer.

Grant Data Source Access to HiPer for Retail Users

Grant read access to data sources for HiPer for Retail users so they can submit documents to HiPer for Retail:

In the portal, click Administration.
Navigate to and open a data source to which you want to grant access (for example, Administrative Resources : World Wide Web).
On the Security page, add the All HiPer Users group (found in Application Spaces : HiPer : Users and Groups) to the Security Settings list and change the Privilege to Read or higher.
When you are done, click Finish.

Note:

If you create new data sources, remember to grant access to HiPer for Retail groups when appropriate.

You have completed the install, but you must now perform the initial set up described in the Administrator Guide for AquaLogic HiPer Workspace for Retail before your users can start using HiPer for Retail.

Installation and Upgrade Guide