Atreus xAuthority™ Dial Accelerator Service Installation...

Dial Accelerator Service Installation GuideRelease 2.0, October 2006

Atreus xAuthority Dial Accelerator Service Installation Guide Table of ContentsRelease 2.0

3

Table of Contents

ForewordOrganization ........................................................................................................ 5Related User Guides ........................................................................................... 6

1. Installing and Configuring the Dial Accelerator Module1.1 Deployment Process Summary ........................................................................... 71.2 Getting Ready To Install ...................................................................................... 8

Meeting Prerequisites ...................................................................................... 8Creating a Directory for Installation Logs ......................................................... 9Creating and Configuring a Policy Distribution Point ....................................... 9

1.3 Copying the Properties Files Required for Installation ....................................... 13To Copy the Properties Files You Need to Install the Dial Accelerator

Module ................................................................................................... 131.4 Configuring the Installation Properties File ........................................................ 15

To Configure the install.properties File .......................................................... 161.5 Configuring the Dial Accelerator Properties File ................................................ 18

To Configure the Dial Accelerator Properties File .......................................... 181.6 Enabling Driver Logging .................................................................................... 19

To Configure the Core Properties File ........................................................... 191.7 Installing the Dial Accelerator Service Provisioning Module .............................. 20

To Install the Dial Accelerator Provisioning Module ....................................... 211.8 Installing the Remedy CSV Daemon ................................................................. 22

To Install the Remedy CSV Daemon ............................................................. 221.9 Configuring Service Drivers ............................................................................... 23

Log in to the System Administration Application ............................................ 23Configure Service Driver Resource Information ............................................ 24

1.10 Installing XSL Stylesheets ................................................................................. 30To Unzip the XSL Stylesheets ....................................................................... 30

2. Post-installation Tasks2.1 Post-Installation Overview ................................................................................. 312.2 Setting Up Customer Hierarchies ...................................................................... 312.3 Assigning Resources ......................................................................................... 32

To Assign Dial Accelerator Resources .......................................................... 322.4 Publication Overview ......................................................................................... 33

Table of Contents Atreus xAuthority Dial Accelerator Service Installation GuideRelease 2.0

4

App A. TroubleshootingApp A.1 Driver Overview ................................................................................................. 35

EBPP ............................................................................................................. 35RegionalLDAP ............................................................................................... 35RemedyCSV .................................................................................................. 36SMTP ............................................................................................................. 36

App A.2 Troubleshooting Errors ...................................................................................... 36

Index 39

Atreus xAuthority Dial Accelerator Service Installation Guide ForewordRelease 2.0

5

Foreword

The Atreus xAuthority Dial Accelerator service provisioning module offers improved internet experience for dial-up customers. Using data compression, Dial Accelerator reduces the amount of time it takes to receive email and view web pages.

The Atreus xAuthority Dial Accelerator Service Installation Guide describes how to install the Dial Accelerator service provisioning module on the Atreus xAuthority Service Fulfillment Center. It also describes how to configure the Dial Accelerator module’s supporting artifacts and systems. This guide is intended for technical personnel within service provider organizations, such as system administrators and operators.

Once you complete the installation and configuration procedures described in this guide, you can begin using the Service Fulfillment Center to provision the Dial Accelerator service on behalf of specific customers. For detailed information on the service provisioning process, see the Dial Accelerator Service Provisioning Guide.

This is the Release 2.0 version of the Dial Accelerator Service Installation Guide.

Organization

Table 1 outlines the organization of chapters in this document.

Table 1: Document Organization

Chapter Description

Installing and Configuring the Dial Accelerator Module

This chapter describes how to install and configure the Dial Accelerator service provisioning module and the applications and systems required to support it.

Post-installation Tasks This chapter describes some basic tasks that you can use to configure the Dial Accelerator module as you prepare to launch the service to your target customer markets.

Troubleshooting This appendix provides a brief description of Dial Accelerator service drivers, common errors and their solutions.

Foreword Atreus xAuthority Dial Accelerator Service Installation GuideRelease 2.0

6

Related User Guides

Users of this guide can find information relating to Atreus xAuthority and the Dial Accelerator service provisioning module in the following guides:

• Dial Accelerator Service Provisioning Guide• Service Fulfillment Center Installation Guide• Service Offering Application User Guide• Service Provisioning Application User Guide• Operations, Administration and Maintenance Guide

The Dial Accelerator Service Provisioning Guide describes how to provision the Dial Accelerator service using the Service Offering Application and the Service Provisioning Application.

The Service Fulfillment Center Installation Guide contains detailed procedures that describe how to install and configure the Service Fulfillment Center software.

The Service Offering Application User Guide describes how to use the Service Offering Application. This application allows service provider system operators and system administrators to create service offerings and make them available to specific customer groups and customers. You can access the online version of the Service Offering Application User Guide directly from the Service Offering Application.

The Service Provisioning Application User Guide describes how to use the Service Provisioning Application. This application gives service provider Customer Service Representatives (CSR) the ability to provision services for their customer accounts through direct interaction with the Service Fulfillment Center. You can access the online version of the Service Provisioning Application User Guide directly from the Service Provisioning Application.

The Operations, Administration and Maintenance Guide describes how to use the System Administration Application to manage equipment, services and users on the Service Fulfillment Center platform. This guide is intended for service provider system administrators and operators. You can access the Operations, Administration and Maintenance Guide directly from the System Administration Application.

Atreus xAuthority Dial Accelerator Service Installation Guide 1. Installing and Configuring the Dial Accelerator ModuleRelease 2.0

7

1. Installing and Configuring the Dial Accelerator Module

This chapter describes how to configure and deploy the Dial Accelerator service provisioning module. It contains the following sections:

• Deployment Process Summary• Getting Ready To Install• Copying the Properties Files Required for Installation• Configuring the Installation Properties File• Configuring the Dial Accelerator Properties File• Enabling Driver Logging• Installing the Dial Accelerator Service Provisioning Module• Installing the Remedy CSV Daemon• Configuring Service Drivers• Installing XSL Stylesheets

1.1 Deployment Process Summary

Table 1-1 describes the primary tasks you need to perform to deploy the Dial Accelerator module and provides links to sections that include detailed information on each of these tasks. If you are using a printed copy of this guide, you can keep track of your progress by putting a check mark in the Done column as you complete each step.

Table 1-1: Dial Accelerator Module Deployment Summary

Task Section Done

1 Get ready to install the Dial Accelerator service provisioning module by ensuring that you have met all prerequisites, created a directory for logs, and created a Policy Distribution Point (PDP).

1.2

2 Copy the Dial Accelerator service properties files from the installation CD-ROM to a working directory on the BEA WebLogic administrative server.

1.3

3 Configure the installation-specific properties file. 1.4

4 Create and configure the Dial Accelerator properties file. 1.5

5 Enable driver logging, if desired. 1.6

6 Install the Dial Accelerator module. 1.7

6 Install the RemedyCSV daemon. 1.8

7 Configure service driver resource information within the Service Fulfillment Center.

1.9

8 Install the XSL stylesheets. 1.10

1. Installing and Configuring the Dial Accelerator Module Atreus xAuthority Dial Accelerator Service Installation GuideRelease 2.0

8

1.2 Getting Ready To Install

The following sections describe the tasks that you need to complete before you install the Dial Accelerator Service Provisioning Module. They include information on:

• Meeting Prerequisites• Creating a Directory for Installation Logs• Creating and Configuring a Policy Distribution Point

Meeting Prerequisites

The following sections describe the prerequisites for installing the Dial Accelerator Service Provisioning Module.

You must meet all of these prerequisites before you begin the installation process.

Atreus xAuthority Service Fulfillment Center

The Dial Accelerator service provisioning module is compatible with Atreus xAuthority Service Fulfillment Center Release 3.3.2 or higher. Before you deploy the Dial Accelerator module, you must install and configure the Service Fulfillment Center software according to the instructions provided in the Service Fulfillment Center Installation Guide for Release 3.3 and ensure that you have installed at least the Release 3.3.2 patch.

For the latest information on Service Fulfillment Center Release 3.3 patches, contact your Atreus representative.

Java Runtime Environment

The Dial Accelerator service provisioning module is compatible with Java Runtime Environment (JRE) version 1.4.2_10. You must ensure that you have installed JRE 1.4.2_10 on each server on which you intend to deploy the Dial Accelerator module.

You can obtain the JRE software from the Sun Microsystems website: http://sun.java.com.

Apache Ant

To install the Dial Accelerator service provisioning module, you require Apache Ant 1.6.5. You can obtain Apache Ant by downloading it from http://ant.apache.org or by installing the apache-ant-1.6.5-bin.zip file contained in the /lib/thirdparty directory on the Dial Accelerator Service Installation CD-ROM.

http://sun.java.com

http://ant.apache.org

http://ant.apache.org


9

Creating a Directory for Installation Logs

When you install the Dial Accelerator service provisioning module, information about the installation is written to log files in the /opt/atreus/logs directory. Before you install the Dial Accelerator module, you must ensure that the /opt/atreus/logs directory has been created on the server from which you are performing the installation process, and that the group and ownership settings for this directory have been set to j2eeadm.

Note

Typically, you install the Dial Accelerator module on the Solaris server that acts as the administrative server for your Service Fulfillment Center-specific J2EE cluster. The following procedure describes how to create the /opt/atreus/logs directory on this server and verify that it has the proper group and ownership settings.

1. As the root user, log in to the server from which you intend to install the Dial

Accelerator module, for example, the administrative server for your Service Fulfillment Center-specific J2EE cluster.

2. Change to the /opt/atreus directory by typing:

cd /opt/atreus ↵

3. List the contents of the /opt/atreus directory by typing:

ls -l ↵

4. Verify that the logs directory is listed and that the group and ownership parameters are both set to j2eeadm.

If the directory exists and its group and ownership parameters are set properly, the output should be similar to the following example:

drwxrwxr-x 2 j2eeadm j2eeadm 2560 Mar 16 12:16 logs

5. Perform the following steps as required:

a. If the logs directory does not exist, create it by typing:

mkdir logs ↵

b. If the group and ownership parameters have not been set to j2eeadm, set them by typing:

chown j2eeadm:j2eeadm logs ↵

Creating and Configuring a Policy Distribution Point

The Dial Accelerator module makes use of software artifacts called service drivers that allow it to manage the resources on which it is to provision Dial Accelerator service activations. These service drivers are installed as part of the Service Fulfillment Center’s Policy Distribution Point (PDP) architecture.


10

By default, the installation script used for the Dial Accelerator module installs the service drivers on a PDP called “local”. To ensure proper installation of these service drivers, you must create and configure a PDP called “local” before you begin the installation process.

Note

If your Dial Accelerator deployment requires use of specific PDP names, you must contact Atreus to obtain a custom service driver installation procedure.

1. Point your browser to the Web address that your administrator has set up for

the System Administration Application.

When you enter the correct Web address, the log-in page of the Administration Application is displayed, as shown in Figure 1-1.

Figure 1-1: Administration Application Login Page

2. Type your login name, domain and password in the fields provided.

3. Click Login.


11

The main page of the System Administration Application is displayed, as shown in Figure 1-2.

Figure 1-2: Main Page of System Administration Application

4. In the Navigator pane at the left side of the main page, expand the Equipment tree.

5. In the Equipment tree, click the PDPs folder.

The properties page for the PDPs folder is displayed, as shown in Figure 1-3.

Figure 1-3: PDPs Folder Properties

6. Choose Add → Add Policy Distribution Point.

A window is displayed that prompts you to enter a name for the PDP you are adding.

7. Type local in the field provided and click OK.


12

The properties page for the PDP is displayed, as shown in Figure 1-4.

Figure 1-4: PDP Properties

8. Enter the properties for the PDP in the fields provided.

Table 1-2 describes the properties you can configure for the PDP. You must provide information for all fields marked with a red asterisk (see Figure 1-4).

Table 1-2: PDP Properties

Property Description

Description An optional description of the PDP

Location An optional description of the physical location of the PDP

Equipment ID An optional identifier for the PDP

Administrative Status Indicates whether the PDP is available for use or taken out of service for administrative purposes. Set to Up when the PDP is required to be operational. Set to Down when maintenance is required on the PDP.

Operational Status Indicates whether the PDP is currently operational (Up) or out of service (Down).

Service Agent URI The Uniform Resource Indicator of the Service Agent. The URI is made up of the IP address of the server that contains the PDP, a port number, and one of two agent processes: agent or xlagent (default).

For example: http://<IP_Address>:4447/xlagent

Typically, the PDP is installed on the server that contains the Service Fulfillment Center’s non-J2EE applications.


13

9. Click Save.

The PDP is now displayed in the Navigator.

1.3 Copying the Properties Files Required for Installation

You install the Dial Accelerator Service Provisioning Module by running an Apache Ant installation script. This script installs the Dial Accelerator module based on the settings in a series of properties files. The default versions of these properties files are stored in subdirectories of the /services/conf directory on the Dial Accelerator Installation CD-ROM.

To ensure that the installation script uses the settings you require for your deployment of the Dial Accelerator module, you need to:

• create a working directory on the server from which you intend to perform the installation process, which is typically the administrative server in your Service Fulfillment Center-specific J2EE cluster (the “BEA WebLogic administrative server”)

• copy the CD-ROM’s /services/conf directory and all of its subdirectories to your working directory

• edit a series of properties files contained within your working directory’s /conf hierarchy

• run the Ant installation script, with your working directory’s /conf directory set as the configuration target for the script.

The following procedure describes how to create a working directory on the BEA WebLogic administrative server and copy the /services/conf directory and all of its subdirectories to this working directory. The configuration procedures for individual properties files are described in sections 1.4 and 1.5.

To Copy the Properties Files You Need to Install the Dial Accelerator Module

1. Log in to the BEA WebLogic administrative server as the root user.

User Name The administrative user name for the PDP (default: pdpadmin)

Password The password for the administrative user for the PDP (for example, adminPWD)

Message Version The version of the messaging protocol used to communicate with the Service Fulfillment Center. Use the default message version (2.0).

Last Driver Synchronization The date the Service Drivers installed on the PDP were last synchronized with the Service Fulfillment Center. For a newly-created PDP, this property is set to “Unknown”.

Driver Synchronization Log A log showing synchronization data for the Service Drivers installed on the PDP. For a newly-created PDP, this log contains no data.

Property Description


14

2. Insert the Dial Accelerator Installation CD-ROM into the server’s CD-ROM drive.

3. If you have not already done so, mount the CD-ROM drive.

For example, the mount /cdrom command mounts the CD-ROM to the /cdrom directory. If you are using the volume manager, the CD-ROM may be mounted to /cdrom/cdrom0.

Do not use an automounter.

4. Create a directory that you can use as a working directory for the installation process.

You can create this directory anywhere on the server. For example, you could create a directory called /opt/dainstall by typing:

mkdir /opt/dainstall ↵

Note

All procedures in this document will use /opt/dainstall as an example working directory.

5. Change to this directory by typing:

cd <working_directory> ↵

where <working_directory> is the path to the directory you created in step 4. For example:

cd /opt/dainstall ↵

6. Copy the contents of the /services/conf directory on the CD-ROM to your working directory by typing:

cp -r <cdrom>/services/conf/ .

where <cdrom> is the mount point for the CD-ROM, for example, /cdrom or /cdrom/cdrom0.

This creates a /conf directory in your working directory, for example, /opt/dainstall/conf. You can now begin configuring the properties files that are required for the installation process, as described in sections 1.4 and 1.5.


15

1.4 Configuring the Installation Properties File

The /conf directory you copied from the Dial Accelerator Installation CD-ROM to your working directory (as described in section 1.3) contains a file called install.properties. Before you run the Ant install script, you need to edit the settings of specific properties in this file to specify information about the operating environment you are using for your Service Fulfillment Center deployment. The Ant install script will use this information to ensure that the Dial Accelerator module is installed properly and can interact with the Service Fulfillment Center and its supporting systems.

To complete this procedure, you will need to collect some specific information about your Service Fulfillment Center deployment. This information is described in Table 1-3. If you are using a printed version of this guide, you can use the space provided in Table 1-3 to record all relevant information.

Table 1-3: Information Required for install.properties File

Information to Collect Record Below for Future Reference

Location of the Service Fulfillment Center EAR files on the BEA WebLogic administrative server

IP address of the BEA WebLogic administrative server

Username and password for the BEA WebLogic default administrator user account

Name of the BEA WebLogic cluster in which the Service Fulfillment Center’s J2EE applications are deployed

Name of the BEA WebLogic domain used for the Service Fulfillment Center

IP address of the Oracle server that contains the Service Fulfillment Center database

Port used to access the Oracle server

Service name used to identify the Service Fulfillment Center database

Username and account for the Service Fulfillment Center-specific Oracle user account

Username and password for the Oracle system user account

IP address of the server that contains the Service Fulfillment Center’s non-J2EE applications

Username, login domain, and password for the Service Fulfillment Center administrator account


16

To Configure the install.properties File

Note

Before you configure the install.properties file, you need to decide where you want the Ant install script to create its output, for example, a location within the working directory you created for your installation. You will specify this directory as you configure the install.properties file.

1. Change to the /conf directory in the working directory you have created for

your Dial Accelerator module installation, as described in section 1.3.

For example, if your working directory is /opt/dainstall, you would change to the /conf directory by typing:

cd /opt/dainstall/conf ↵

2. Open the install.properties file in a text editor by typing:

<editor> install.properties ↵

where <editor> represents the command you use to launch your text editor, for example, vi.

3. Edit the install.properties file, changing property values based on settings that are specific to the environment into which you intend to deploy the Dial Accelerator module.

You will need to specify information about your Service Fulfillment Center deployment, BEA WebLogic servers, and Oracle server, as described above.

Table 1-4 describes the properties that must be set to ensure that the Dial Accelerator module installs properly. You can leave all properties that are not described in Table 1-4 set to their default values.

Table 1-4: Properties to be Updated in install.properties

Property Default Setting Recommended Setting

General Settings

install.out {basedir}/out Specify the directory in which you want the Ant install script to create new Service Fulfillment Center EAR files that include the Dial Accelerator module.

For example, you replace {basedir} with the working directory you have created for your installation, as described in section 1.3. Using the example described in section 1.3, the setting would be /opt/dainstall/out. You do not need to create this directory before you execute the Ant install script.

option.compile.j2ee false Set to true if you want to pre-compile the Java Server Pages (JSP) associated with the Dial Accelerator module during the installation process. By pre-compiling the JSP pages, you can get faster load times when you use these pages for the first time.


17

option.install.j2ee true You must set this property to true to ensure that the EAR files created by the Ant install script are automatically deployed on BEA WebLogic.

EAR Settings

src.xauth.ear ${basedir}/xAuthorityCore.ear Replace {basedir} with the path to the xAuthorityCore.ear file on the BEA WebLogic administrative server, for example, /opt/bea/user_projects/domains/<domain>/applications, where <domain> is the name of your Service Fulfillment Center-specific BEA WebLogic domain.

src.spa.ear ${basedir}/serviceProvisioning.ear Replace {basedir} with the path to the serviceProvisioning.ear file on the BEA WebLogic administrative server, for example, /opt/bea/user_projects/domains/<domain>/applications, where <domain> is the name of your Service Fulfillment Center-specific BEA WebLogic domain.

src.soa.ear ${basedir}/offerings.ear Replace {basedir} with the path to the offerings.ear file on the BEA WebLogic administrative server, for example, /opt/bea/user_projects/domains/<domain>/applications, where <domain> is the name of your Service Fulfillment Center-specific BEA WebLogic domain.

JNDI Properties

java.naming.provider.url t3://127.0.0.1:7011/ Replace 127.0.0.1 with the IP address or fully qualified domain name of the BEA Weblogic administrative server. Replace 7011 with the number of the port that is to be used to access it.

Oracle Properties

oracle.ip 127.0.0.1 Replace 127.0.0.1 with the IP address or fully qualified domain name of the Oracle server that contains the Service Fulfillment Center database.

oracle.port 1521 If applicable, replace 1521 with the port that is to be used to access the Service Fulfillment Center database.

oracle.service eventDB If applicable, replace eventDB with the Oracle service name used for the Service Fulfillment Center database.

oracle.user xauthority Replace xauthority with the unique identifier for the user account that BEA WebLogic uses to access the Service Fulfillment Center database.

oracle.password xauthorityPWD Replace xauthorityPWD with the password for the user account that BEA WebLogic users to access the Service Fulfillment Center database.

oracle.system.user system Replace system with the unique identifier for the Oracle system user account.

oracle.system.password homer1 Replace homer1 with the password associated with the Oracle system user account.

xAuthority Properties

xauth.api http://127.0.0.1/authapi Replace 127.0.0.1 with the IP address or fully qualified domain name of the server that contains the Service Fulfillment Center’s non-J2EE applications.

xauth.username admin Replace admin with the user name for the Service Fulfillment Center administrator user account.

xauth.userpassword adminPWD Replace adminPWD with the password associated with the Service Fulfillment Center administrator user account.



18

4. When you have finished making your changes, save and close the install.properties file.

1.5 Configuring the Dial Accelerator Properties File

A DialAccelerator.properties file must be created to provide settings needed for the service module. You will need to create a /DialAccelerator directory for this file within the /opt/atreus/xlink/conf directory.

The following procedure explains how to create a /DialAccelerator directory, copy the properties file into it, and then modify the properties file.

To Configure the Dial Accelerator Properties File

1. Change to the /opt/atreus/xlink/conf directory by typing:

cd /opt/atreus/xlink/conf ↵

2. Create a directory called DialAccelerator within the /conf directory by typing:

mkdir DialAccelerator ↵

3. Copy the DialAccelerator.properties file from the /properties directory in your working directory to the /DialAccelerator directory by typing:

cp /opt/dainstall/conf/DialAccelerator-package-690e831f/custom/properties/DialAccelerator.properties DialAccelerator ↵

xauth.userdomain admin Replace admin with the login domain used by the Service Fulfillment Center administrator user account.

BEA Properties

bea.url t3://127.0.0.1:7001 Replace 127.0.0.1 with the IP address or fully qualified domain name that identifies the BEA WebLogic administrative server. Replace 7001 with the port number used to access BEA WebLogic on this server.

bea.domain xauthority Replace xauthority with the name of the Service Fulfillment Center-specific BEA WebLogic domain.

bea.targets myserver Replace myserver with the name of the BEA WebLogic cluster used for your Service Fulfillment Center deployment.

bea.username weblogic Replace weblogic with the unique identifier for the default WebLogic administrator user account.

bea.password weblogic Replace weblogic with the password associated with the default WebLogic administrator user account.



19

4. Change to the /DialAccelerator directory in your working directory by typing:

cd DialAccelerator ↵

5. Open the appropriate DialAccelerator.properties file in a text editor by typing:

<editor> DialAccelerator.properties ↵

where <editor> represents the command you use to launch your text editor.

6. Edit the DialAccelerator.properties file, changing property values based on settings that are specific to the environment into which you intend to deploy the Dial Accelerator module.

You will need to specify information about your system administrator account, as detailed in Table 1-5. You can leave all properties that are not described in Table 1-5 set to their default values.

Table 1-5: Properties to be Updated in DialAccelerator.properties

7. Save and close the file.

1.6 Enabling Driver Logging

To enable driver logging, you need to modify the core.properties file. This file is located in the /opt/atreus/xlink/conf directory of your current xAuthority deployment.

To Configure the Core Properties File

1. Change to the /opt/atreus/xlink/conf directory by typing:

cd /opt/atreus/xlink/conf ↵

2. Create a backup copy of the core.properties file in the /opt/atreus/xlink/conf directory by typing:

cp core.properties core.properties.bak ↵

3. Open the core.properties file in a text editor by typing:

<editor> /opt/atreus/xlink/conf/core.properties ↵



username admin Specify the username of your system administrator.

domain admin Specify the domain of your system administrator.

password adminPWD Specify the password of your system administrator.


20

4. Edit the core.properties file by adding the following text:

log4j.category.com.atreus.sl.bb.resource.ebpp=DEBUG, ebpp log4j.appender.ebpp=org.apache.log4j.DailyRollingFileAppenderlog4j.appender.ebpp.DatePattern='.'yyyy-MM-ddlog4j.appender.ebpp.File=/opt/atreus/logs/ebpp.loglog4j.appender.ebpp.layout=org.apache.log4j.PatternLayoutlog4j.appender.ebpp.layout.ConversionPattern=%d %-5p [%t] %m%n

log4j.category.com.atreus.sl.bb.resource.regionalLDAP=DEBUG, regionalLDAPlog4j.appender.regionalLDAP=org.apache.log4j.DailyRollingFileAppenderlog4j.appender.regionalLDAP.DatePattern='.'yyyy-MM-ddlog4j.appender.regionalLDAP.File=/opt/atreus/logs/regionalLDAP.loglog4j.appender.regionalLDAP.layout=org.apache.log4j.PatternLayoutlog4j.appender.regionalLDAP.layout.ConversionPattern=%d %-5p [%t] %m%n

log4j.category.com.atreus.sl.bb.resource.smtp=DEBUG, smtplog4j.appender.smtp=org.apache.log4j.DailyRollingFileAppenderlog4j.appender.smtp.DatePattern='.'yyyy-MM-ddlog4j.appender.smtp.File=/opt/atreus/logs/smtp.loglog4j.appender.smtp.layout=org.apache.log4j.PatternLayoutlog4j.appender.smtp.layout.ConversionPattern=%d %-5p [%t] %m%n

log4j.category.com.atreus.sl.bb.resource.remedyCSV=DEBUG, remedyCSVlog4j.appender.remedyCSV=org.apache.log4j.DailyRollingFileAppenderlog4j.appender.remedyCSV.DatePattern='.'yyyy-MM-ddlog4j.appender.remedyCSV.File=/opt/atreus/logs/remedyCSV.loglog4j.appender.remedyCSV.layout=org.apache.log4j.PatternLayoutlog4j.appender.remedyCSV.layout.ConversionPattern=%d %-5p [%t] %m%n

5. Save and close the file.

1.7 Installing the Dial Accelerator Service Provisioning Module

Once you have configured the installation and Dial Accelerator properties files, you can execute the Ant installation script to install the Dial Accelerator provisioning module.

When you execute the Ant installation script, you will be prompted to provide a working directory. The directory you provide should be the same as the directory you specified for the install.out property in the install.properties file (see Table 1-4 for more information). Atreus recommends that you choose a working directory that is located outside your server’s swap space. The working directory you specify must be created before you execute the installation script.

The installation script creates a series of enterprise archive (EAR) files in the working directory:

• xAuthorityCore.ear• serviceProvisioning.ear• offerings.ear


21

These EAR files are versions of the three Service Fulfillment Center-specific EAR files that are deployed on the BEA WebLogic Application server. These versions include the Dial Accelerator service functionality and incorporate all of the property settings you have specified in the installation and Dial Accelerator properties files.

Note

The following procedure describes how to execute the Ant installation script to install the Dial Accelerator provisioning module. You must have completed the procedures described in sections 1.2 to 1.5 before you perform the following procedure.

To Install the Dial Accelerator Provisioning Module

1. Ensure that you have logged in to the server that contains the working directory you are using for your Dial Accelerator module installation.

2. Ensure that you have inserted and mounted the Dial Accelerator installation CD-ROM, as described in section 1.3.

3. Change to the root directory on the CD-ROM.

4. Execute the install script by typing:

ant install -DCONF_DIR=/opt/<working_directory>/conf/ ↵

where <working_directory> is the working directory into which you have copied the ./conf directory from the Dial Accelerator Installation CD-ROM. For example, if your working directory is /opt/dainstall, you would type:

ant install -DCONF_DIR=/opt/dainstall/conf/ ↵

The script prompts you to specify a working directory for the script. The script will create this directory, use it for temporary storage, then delete the directory.

5. Type the full path to the working directory.

For example:

/opt/dainstall/tmp

Note

For the best performance, specify a directory that is not used for swap space.

6. When the script has finished executing, change to the directory you specified

for the install.out property when you configured the install.properties file (see Table 1-4). For example:

cd /opt/dainstall/out ↵


22

7. List the contents of the directory and verify that it contains the following files:

• xAuthorityCore.ear• serviceProvisioning.ear• offerings.ear

1.8 Installing the Remedy CSV Daemon

The Dial Accelerator Service Installation CD-ROM includes four service drivers that allow the Service Fulfillment Center to manage the resources on which it is to provision Dial Accelerator service activations. These service drivers are automatically installed during the installation of the Dial Accelerator provisioning module. However, to support the Dial Accelerator service provisioning module, the Remedy CSV daemon must be installed on the server supporting CSV files.

Note

Steps 4 - 6 are optional; Atreus recommends these steps to ensure the Remedy CSV daemon process is running.

To Install the Remedy CSV Daemon

1. Create directories for the Remedy CSV data by preforming the following steps:

i. Create a directory called /opt/atreus/custom/csv by typing:

mkdir /opt/atreus/custom ↵

mkdir /opt/atreus/custom/csv ↵

ii. Create another directory called /opt/atreus/services/remedyCSV by typing:

mkdir /opt/atreus/services/remedyCSV ↵

2. Unzip the remedyCSVd package from the CD-ROM to your working directory by typing:

unzip -d /opt/dainstall <cdrom>/services/bin/RemedyCSV-package-3aa1827f.zip ↵


3. Copy the unzipped remedyCSVd file to the /opt/atreus/services/remedyCSV directory by typing:

cp /opt/dainstall/RemedyCSV-package-3aa1827f/remedyCSVd/remedyCSVd /opt/atreus/services/remedyCSV ↵


23

4. Open the initab file in a text editor by typing:

<editor> /etc/initab ↵


5. Append the following on a single line in the/etc/inittab file:

x0:234:respawn:/opt/atreus/services/remedyCSV/remedyCSVd -p 54446 -d /opt/atreus/custom/csv/ >/dev/msglog 2<>/dev/msglog </dev/console

6. Apply the new configuration to the initab file by typing:

# /etc/telinit Q ↵

1.9 Configuring Service Drivers

The Dial Accelerator Service Installation CD-ROM includes service drivers that allow the Service Fulfillment Center to manage the resources with which it provisions Dial Accelerator service activations. These service drivers are automatically installed when the Dial Accelerator provisioning module is installed.

To use the Dial Accelerator service drivers, you need to use the System Administration Application to create and configure objects that will be used to represent the service resources in the Service Fulfillment Center directory.

The following sections describe how to:

• Log in to the System Administration Application• Configure Service Driver Resource Information

Note 1

Before you perform the following procedures, gather the resource configuration information that you collected and recorded when you completed your Dial Accelerator site survey. Having this information on hand will allow you to complete these procedures more efficiently.

Note 2

The following procedures are based on use of the default PDP configuration, described in “Creating and Configuring a Policy Distribution Point”, in section 1.2.

Log in to the System Administration Application

Once you have installed the service drivers required for the Dial Accelerator provisioning module, you need to use the System Administration Application to configure them. The following procedure describes how to access and log in to the System Administration Application.


24

1. Point your browser to the Web address that your administrator has set up for the System Administration Application.

When you enter the correct Web address, the log-in page of the Administration Application is displayed, as shown in Figure 1-5.

Figure 1-5: Administration Application Login Page

2. Type your login name, domain and password in the fields provided.

3. Click Login.

The main page of the System Administration Application is displayed, as shown in Figure 1-6.

Figure 1-6: Main Page of System Administration Application

Configure Service Driver Resource Information

Use the following procedure to create and configure the objects that will be used to represent the service resources in the Service Fulfillment Center directory.

1. In the Navigator pane of the System Administration Application, expand the branch that represents the PDP you intend to use for the Dial Accelerator service, then expand the Drivers object below it.


25

When you expand the Drivers object, you see the EBPP, RegionalLDAP, RemedyCSV, and SMTP service drivers that have been created on this PDP, as shown in Figure 1-7. You also see the AgentLog driver, which is installed on the PDP by default.

Figure 1-7: Dial Accelerator Service Drivers

Creating and Configuring the EBPP Resource

2. Right-click the icon that represents the EBPP service driver and choose the New Custom.Aliant.BuildingBlocks.Resource.EBPP... item.

A dialog box prompts you to specify a name for the new EBPP resource.

3. Type a name for the new resource and click OK.

This adds a new resource object below the EBPP driver object. The Work Area displays the Properties page for this object, as shown in Figure 1-8.

Figure 1-8: Properties Page for EBPP Resource

4. Configure the attributes associated with the EBPP resource object.


26

Table 1-6 describes these attributes.

Table 1-6: EBPP Resource Attributes

5. When you have finished configuring the attributes for the EBPP resource, click Save.

Creating and Configuring the RegionalLDAP Resource

6. Right-click the icon that represents the RegionalLDAP service driver and choose the New Custom.Aliant.BuildingBlocks.Resource.RegionalLDAP... item.

This adds a new resource object below the RegionalLDAP driver object. The Work Area displays the Properties page for this object, as shown in Figure 1-9.

Figure 1-9: Properties Page for RegionalLDAP Resource

Attribute Description

Name The name that was assigned to the EBPP resource when it was created. You cannot rename a resource.

Resource Type The object type that identifies the EBPP resource:

Custom.Aliant.BuildingBlocks.Resource.EBPP.Driver.EBPPResource

You cannot change the object type associated with a resource.

testMode Determines whether the EBPP service driver is running “live” (off) or in test mode (on). If the driver is running in test mode, it will process requests without contacting the EBPP server.

adminStatus This field performs no fuction for Dial Accelerator service.

oracleSID The system identifier for the Oracle database used by the EBPP Application.

oracleHost The IP address of the Oracle database used by the EBPP Application.

oraclePort The port of the Oracle database used by the EBPP Application.

oracleUsername The oracle ID used to access the EBPP Application database.

oraclePassword The password associated with the EBPP Application database account.


27

7. Configure the attributes associated with the RegionalLDAP resource object.


Table 1-7: RegionalLDAP Resource Attributes

8. When you have finished configuring the attributes for the RegionalLDAP resource, click Save.

Note

You must create a Regional LDAP resource for each region for which you plan to provide service. Repeat steps 6 to 8 to create another Regional LDAP resource.

Creating and Configuring the RemedyCSV Resource

9. Right-click the icon that represents the RemedyCSV service driver and choose the New Custom.Aliant.BuildingBlocks.Resource.RemedyCSV... item.


Name The name that was assigned to the RegionalLDAP resource when it was created. You cannot rename a resource.

Resource Type The object type that identifies the RegionalLDAP resource:

Custom.Aliant.BuildingBlocks.Resource.RegionalLDAP.Driver.RegionalLDAPResource


testMode Determines whether the RegionalLDAP service driver is running “live” (off) or in test mode (on). If the driver is running in test mode, it will process requests without contacting the RegionalLDAP server.


ldapHost The IP address of the RegionalLDAP server

ldapPort The port that the service driver uses to access the RegionalLDAP server

ldapUser The user name for the RegionalLDAP administrator account.

ldapPassword The password for the RegionalLDAP administrator account.

ldapBaseDN The distinguished name xAuthority uses to begin a sub-tree search of the LDAP database looking for entries with a matching value of the UID attribute.


28

This adds a new resource object below the RemedyCSV driver object. The Work Area displays the Properties page for this object, as shown in Figure 1-10.

Figure 1-10: Properties Page for RemedyCSV Resource

10. Configure the attributes associated with the RemedyCSV resource object.


Table 1-8: RemedyCSV Resource Attributes

11. When you have finished configuring the attributes for the RemedyCSV resource, click Save.

Creating and Configuring the SMTP Resource

12. Right-click the icon that represents the SMTP service driver and choose the New Custom.Aliant.BuildingBlocks.Resource.SMTP... item.


Name The name that was assigned to the RemedyCSV resource when it was created. You cannot rename a resource.

Resource Type The object type that identifies the RemedyCSV resource:

Custom.Aliant.BuildingBlocks.Resource.RemedyCSV.Driver.RemedyCSVResource


testMode Determines whether the RemedyCSV service driver is running “live” (off) or in test mode (on). If the driver is running in test mode, it will process requests without contacting the RemedyCSV server.


remedyHost The IP or FQDN of the server the remedyCSV daemon must be installed on.

remedyPort The port the remedyCSV daemon must be configured to listen on.


29

This adds a new resource object below the SMTP driver object. The Work Area displays the Properties page for this object, as shown in Figure 1-11.

Figure 1-11: Properties Page for SMTP Resource

13. Configure the attributes associated with the SMTP resource object.


Table 1-9: SMTP Resource Attributes

Note

The SMTP server listed on the SMTP resource must be configured in order to relay messages from the Service Fulfillment Center.


Name The name that was assigned to the SMTP resource when it was created. You cannot rename a resource.

Resource Type The object type that identifies the SMTP resource:

Custom.Aliant.BuildingBlocks.Resource.SMTP.Driver.SMTPResource


testMode Determines whether the SMTP service driver is running “live” (off) or in test mode (on). If the driver is running in test mode, it will process requests without contacting the SMTP server.


smtpHost The hostname or IP address of the SMTP server

smtpPort The port that the SMTP driver is to use to access the SMTP server


30

14. When you have finished configuring the attributes for the SMTP resource, click Save.

1.10 Installing XSL Stylesheets

The Dial Accelerator Service Installation CD-ROM includes a .zip file that contains stylesheets for the email messages sent to customers and billing representatives. The following steps outline how to unzip these stylesheets so that you can use them with the Dial Accelerator service.

Once you have unzipped the stylesheet package, you can modify the stylesheets to suit your email layout standards. You must install the XSL templates into the XSLFORDRIVERS table of the xAuthority database.

To Unzip the XSL Stylesheets

1. Unzip the stylesheets from the CD-ROM to your working directory. For example if your working directory is /opt/dainstall, type:

unzip -d /opt/dainstall <cdrom>/services/bin/DialAccelerator-package-690e831f.zip ↵


2. The unzipped stylesheets are extracted to the following directory within your working directory:

/opt/dainstall/DialAccelerator-package-690e831f/emailTemplates

Atreus xAuthority Dial Accelerator Service Installation Guide 2. Post-installation TasksRelease 2.0

31

2. Post-installation TasksThis chapter describes tasks that you can perform to get your Dial Accelerator deployment up and running once you have completed the installation procedure described in chapter 1. It contains the following sections:

• Post-Installation Overview• Setting Up Customer Hierarchies• Assigning Resources• Publication Overview

2.1 Post-Installation Overview

Once you successfully install the Dial Accelerator module and drivers, you need to establish customer hierarchies and resource assignments so that you can provision the Dial Accelerator service.

After you complete these two steps, you need to follow a specific procedue to publish the Dial Accelerator service. Section 2.4, “Publication Overview” describes this procedure.

2.2 Setting Up Customer Hierarchies

To allow for successful provisioning of the Dial Accelerator service, you need to set up Aliant’s customer hierarchy, as shown in Figure 2-1.

Figure 2-1: Aliant Customer Hierarchy

Set up regional customer groups to allow settings to be configured for unique geographical regions that customers belong to. You must set up the same set of regional groups for businesses.

2. Post-installation Tasks Atreus xAuthority Dial Accelerator Service Installation GuideRelease 2.0

32

Refer to the Operations, Administration and Maintenance Guide for information on how to create customers and customer groups.

Note

You must set up a customer hierarchy before you can assign resources.

2.3 Assigning Resources

The Dial Accelerator service uses four service drivers: EBPP, RegionalLDAP, RemedyCSV, and SMTP. Once you’ve created a resource object to represent each instance of each of the four service drivers, you are ready to assign them to customer groups. To comply with Aliant standards, you need to assign resources to customer groups as follows.

Assign the EBPP, RemedyCSV, and SMTP resources to the Aliant customer group. Because a RegionalLDAP resource is created for each region in which the service will be provided, you must assign a regional resource to each regional business and consumer customer group.

Use the following procedure to assign Dial Accelerator resources to a customer group.

To Assign Dial Accelerator Resources

1. In the Navigator, select the customer group to which you want to assign a resource.

The Manage Properties page for the customer is displayed.

2. Choose Manage → Resources.

The Manage Resources page is displayed, as shown in Figure 2-2. By default, this page displays filtering tools that allow you to find specific resources within the Service Fulfillment Center.

Figure 2-2: Manage Resources Page for Customer

3. Specify the filtering criteria you want.

Atreus xAuthority Dial Accelerator Service Installation Guide 2. Post-installation TasksRelease 2.0

33

For example:

• If you want to assign a specific resource to this customer group, type the name of the resource in the Named field.

• If you want to display only the resources that are currently assigned to the customer group, click Display current resources only.

• If you do not want to apply any filtering criteria, leave all fields and check boxes empty.

4. Click Find.

A list of resources is displayed, as shown in Figure 2-3. The list shows all valid resources for the customer group that match your filtering criteria.

Figure 2-3: List of Resources

5. Enable the check box beside each resource you want to assign to the customer group.

Click Select all if you want to assign all resources in the list to the customer group.

6. Click Save.

2.4 Publication Overview

To provision Dial Accelerator for Aliant, you must create separate offerings for the Business and Consumer customer groups. Publish one offering to the Consumer customer group and the other to the Business customer group.

You must create an additional offering, Aliant Consumer Validation and publish it to the Consumer customer group.

Refer to the Dial Accelerator Service Provisioning Guide for detailed steps and information on publishing a Dial Accelerator offering.

2. Post-installation Tasks Atreus xAuthority Dial Accelerator Service Installation GuideRelease 2.0

34

Atreus xAuthority Dial Accelerator Service Installation Guide App A. TroubleshootingRelease 2.0

35

App A. Troubleshooting

This appendix provides a brief description of Dial Accelerator service drivers, common errors and their solutions. It includes the following sections:

• Driver Overview• Troubleshooting Errors

App A.1 Driver Overview

The Dial Accelerator service uses four service drivers: EBPP, RegionalLDAP, RemedyCSV, and SMTP. Occasionally errors can occur between the drivers and the third party systems they communicate with. The following sections outline the functionality of the Dial Accelerator drivers.

Driver logs are located in /opt/Atreus/logs.

Note

To view driver logs, driver logging must be enabled. See chapter 1.6 to enable driver logging.

EBPP

The EBPP driver communicates with the Aliant electronic billing and payment processing database. The driver provides two methods: Validate and Authenticate. The Validate method looks up the customer’s account number. The customer account number must be entered in the Customer ID field on the Manage Customers page. If the account number exists, the Validate method returns ‘true’. The Authenticate method gathers information from the user and compares it with the current EBPP database content. The information it gathers includes, postal code, region, account number, and amount on last bill.

RegionalLDAP

The RegionalLDAP driver communicates with the LDAP database that authenticates dial-up users. Aliant has four regional LDAP databases. The driver will get the ‘dialacceleratorallowed’ value and set it to ‘y’ to provision Dial Accelerator service or ’n’ to unprovision Dial Accelerator service.

App A. Troubleshooting Atreus xAuthority Dial Accelerator Service Installation GuideRelease 2.0

36

RemedyCSV

The RemedyCSV driver communicates with the C++ daemon by sending UDP packet messages. The daemon processes messages and writes to the CSV file. The daemon is also responsible for nightly rotation of the CSV file. The file is post-processed by customer for integration with the CRM system. Post-processing is preferred because customers may not yet have been added to the CRM system.

SMTP

The SMTP driver sends email using an XSL template stored in the xAuthority database. Templates are stored in the XSLFORDRIVERS table in the OUTPUTXSL column. The parameter list is hard coded in the workflow.

App A.2 Troubleshooting Errors

Table A-1 describes common error messages, their meanings and possible solutions organized by driver type.

Table App A-1: Troubleshooting Errors Organized by Driver

Error Meaning Solution

EBPP

SQL Exception The EBPP resource may be misconfigured Check the EBPP resource configuration

Could not load Driver The EBPP resource may be misconfigured Check the EBPP resource configuration

Failed to create the database connection

The EBPP resource may be misconfigured

The EBPP database is not running

Check the EBPP resource configuration

Start the EPBB database

Customer ID not found The Customer ID is not in the EPBB database

The customer may need to be signed up for the service

Check the CustomerID and EBPP database

Duplicate Customer ID found

There are two or more identical Customer IDs in the EPBB database

Correct the EBPP database

RegionalLDAP

Could not obtain Initial Directory Context to

The LDAP resource may be misconfigured

The LDAP server is not running

Check the LDAP resource configuration

Start the LDAP server

<UID> already set to ’Y’ The LDAP entry is already set to Y Set dialaccleratorallowed to ‘N’

Or

provision the user with the Regional LDAP resource in Test Mode

<UID> already set to ’N’ The LDAP entry is already set to N Set dialaccleratorallowed to ‘Y’

Or

provision the user with the Regional LDAP resource in Test Mode

Atreus xAuthority Dial Accelerator Service Installation Guide App A. TroubleshootingRelease 2.0

37

RegionalLDAP:Driver - UID: <UID> not found

The user ID does not exist in the LDAP directory

The region is incorrect

A user ID needs to be created in the LDAP

Check the region code and check that the UID exists in that Regional LDAP

Too many results found Two or more identical user ID’s exist in the LDAP directory

The LDAP directory needs to be modified

RemedyCSV

Data not written to CSV file

The driver is not writing data to its CSV file Confirm that the resource is configurated properly, the daemon is running, and that the configuration of the daemon matches the resource.

SMTP

SMTP Driver - Address Error

Invalid email address

sendmail problem

Check all email addresses

Look at the sendmail configuration

Check the SMTP resource configuration

Confirm by sending email from the command line

SMTP Driver - Messaging Error

sendmail problem Look at the sendmail configuration

Check the SMTP resource configuration

Confirm by sending email from the command line

XSL Document: … not found.

The XSL document is missing from the Service Fulfillment Center database

The wrong XSL document name was specified during publication

Enter the correct XSL documents into the Service Fulfillment Center database

Check the template name in the Service Fulfillment Center database and in the publication

Republish the service offering with the correct XSL document name

Too many records found for XSL document

There are two or more XSL documents with the same name

Delete one or more of the entries from the Service Fulfillment Center database

XSLTransform Error A problem with the XSL document Edit and correct the XSL document

Error Meaning Solution

App A. Troubleshooting Atreus xAuthority Dial Accelerator Service Installation GuideRelease 2.0

38

39

Atreus xAuthority Dial Accelerator Service Installation Guide IndexRelease 2.0

Index

Symbols

/opt/atreus/logs directory, 9

A

Ant installation scriptabout, 20executing, 20, 21

Apache Antobtaining, 8supported versions, 8

assigning resourcesabout, 32

C

chapters, in this user guide, 5core.properties file

about, 19configuring, 19

customer hierarchiesabout, 31creating, 31

customersassigning resources, 32

D

deployment process summary, 7Dial Accelerator module

configuring properties files, 13configuring service drivers, 23, 24deployment overview, 7getting ready to install, 8installing, 20, 21installing RemedyCSV dæmon, 22installing XSL Stylesheets, 30prerequisites, 8required PDP configuration, 9

Dial Accelerator properties filesabout, 18configuring, 18DialAccelerator.properties, 18

DialAccelerator.properties fileabout, 18configuring, 18

document organization, 5Driver Logging

enabling, 19

I

install.properties fileabout, 15configuring, 16information required for, 15properties to edit, 16

installation properties fileabout, 15configuring, 15, 16properties to edit, 16

installing, Dial Accelerator module, 20, 21

L

logging in, System Administration Application, 23

logs directory for installation process, creating, 9

O

organization, of chapters in guide, 5

P

Policy Distribution Pointconfiguring for Dial Accelerator module, 9prerequisites, 9required configuration, 9

post-installationabout, 31overview, 31

prerequisitesabout, 8Apache Ant, 8Java Runtime Environment, 8PDP configuration, 9Service Fulfillment Center, 8

properties filesabout, 13copying to working directory, 13install.properties, 15

publicationabout, 33creating, 33overview, 33

Index Atreus xAuthority Dial Accelerator Service Installation Guide Release 2.0

40

R

related user guides, 6RemedyCSV dæmon, installing, 22

S

service driversconfiguring, 23, 24required PDP configuration, 9

Service Fulfillment Centerrequired patches, 8supported releases, 8

System Administration Applicationlogging in, 23

T

TroubleshootingEBPP, 35error types, 36overview, 35RegionalLDAP, 35RemedyCSV, 36SMTP, 36

W

working directoryabout, 13creating, 13

X

XSL Stylesheets, installing, 30

Head Office

Atreus Systems, Inc.

1130 Morrison Drive, Suite 300

Ottawa, Ontario, K2H 9N6

Canada

Tel: 613-683-3600

Fax: 613-233-8204

Toll Free: 800-764-5514

Help Desk: 877-922-0722

World Wide Web

www.atreus-systems.com

© 2001 - 2006 Atreus Systems Corporation. All rights reserved.

The use and copying of this product are subject to a license agreement. Any other use is prohibited. No other

part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system or translated

into any language in any form by any means without the prior written consent of Atreus Systems Corporation.

Information in this publication is subject to change without notice and does not represent a commitment on

the part of the vendor. Companies, names and data used in examples are fictitious unless otherwise indicated.

Technical information herein is subject to change without notice.

Atreus xAuthority™ is a trademark of Atreus Systems, Inc. All other trademarks or registered trademarks are

the property of their respective owners.

Atreus Systems, the Atreus logo and all Atreus Systems products are trademarks of Atreus Systems, Inc.

™

Atreus xAuthority™ Dial Accelerator Service Installation...

Documents

Transcript of Atreus xAuthority™ Dial Accelerator Service Installation...