PrePay in 10-0-1 Upgrade and Conversion Guide

Upgrade and Conversion Guide

Release 10.0.1

825-0735-010 Rev 01

PrePay IN

To order additional copies of Lightbridge documentation, or to request documents in electronic (read-only) format, please contact your Lightbridge account manager or relationship manager.

The information used as examples in this document, including consumer or business names, identification numbers, addresses, and telephone numbers, is fictitious. Any resemblance to actual names, addresses, telephone numbers, or other forms of identification is unintentional and purely coincidental.

LIGHTBRIDGE, and the Lightbridge logo are registered trademarks of Lightbridge, Inc. PrePay IN is a trademark of Lightbridge, Inc.

All other trademarks or registered trademarks are the property of their respective owners.

Software Version: Release 10.0.1

Order Number: 825-0735-010, Revision 01

Print Date: October 13, 2005

© 2005 by Lightbridge, Inc. All rights reserved.

This Updated Guide Book and the software described in it are the property of Lightbridge, Inc., and its licensors and contain their confidential trade secrets. Use, examination, copying, transfer and disclosure to others, in whole or in part, are prohibited except with the express prior written consent of Lightbridge, Inc.

Lightbridge, Inc. 30 Corporate Drive Burlington, MA 01803 USA TEL: +1-781-359-4000 FAX: +1-781-359-4500 http://www.lightbridge.com

Lightbridge Proprietary and Confidential Upgrade and Conversion Guide All rights reserved. Lightbridge Inc. 825-0735-010, Revision 01

3

Contents Chapter 1. Preface.......................................................................................................10

1.1 Upgrading from Earlier Releases ............................................................ 10 1.2 Required Materials .................................................................................. 10 1.3 Disk Space Requirements ....................................................................... 12 1.4 Time Estimate for Upgrading to PrePay 10.0.1 ....................................... 12

Chapter 2. Pre-Upgrade Procedures .........................................................................15 2.1 Review the PrePay ReadMe Notes ........................................................ 15 2.2 Preparation of Solaris 2.8 ........................................................................ 15

2.2.1 Kernel 29 ........................................................................................ 15 2.2.2 Recommended and Required Patches........................................... 15 2.2.3 64-bit Mode Solaris......................................................................... 16

2.3 Preparation for Veritas 4.x Upgrade ........................................................ 16 2.4 Pre-upgrade Database Conversion Analysis........................................... 17 2.5 Prepare the Upgrade Staging Directory .................................................. 17

2.5.1 Load the Upgrade Toolkit and Application Files ............................. 17 2.5.2 Pre-Stage CD Contents to Disk ...................................................... 18

2.6 Confirm the Directory Locations for Application Packages...................... 19 2.6.1 Create the /udr File System............................................................ 20

2.7 Estimate the Upgrade Space Requirements ........................................... 20 2.7.1 Estimating the Space for PrePay 10.0.1 Operation ........................ 21

2.8 Estimating the Space for Database Table Changes................................ 21 2.8.1 Table Changes Requiring a Review of Tablespaces...................... 22 2.8.2 Determine Freespace in Each Tablespace..................................... 22

2.9 Acquire the PrePay 10.0.1 License Files for Optional Features.............. 23 2.10 Note on configuration files in PrePay 10.0.1 ........................................... 24 2.11 Prepare the Switch Configuration Files ................................................... 24

2.11.1 All Interfaces ................................................................................... 25 2.11.1.1 switchInterface.cfg.sample ........................................................ 25 2.11.1.2 capSwitchInterface.cfg.sample.................................................. 25


4

2.11.1.3 profileFile.prf.sample ................................................................. 26 2.11.1.4 denyAnnouncementTable.cfg.sample ....................................... 26

2.11.2 IS-41EE .......................................................................................... 26 2.11.3 WIN-II.............................................................................................. 27 2.11.4 GSM................................................................................................ 27 2.11.5 ISUP ............................................................................................... 27 2.11.6 IS-41P............................................................................................. 27

2.12 Review and Prepare D7 Configuration .................................................... 28 2.12.1 NOTE: PrePay 10.0.1 requires D7 version 1.4.0.2........................ 28 2.12.2 Upgrading from Distributed7 1.3.1.x ............................................... 28 2.12.3 Prepare New D7 Configuration Files .............................................. 28

2.13 Note on the Emergency Number Table (Lucent Only) ............................ 29

Chapter 3. Upgrading to PrePay Release 10.0.1 ......................................................30 3.1 Review the PrePay 10.0.1 ReadMe Notes ............................................. 30 3.2 Backup Current PrePay and Oracle ........................................................ 30 3.3 Miscellaneous backup ............................................................................. 31 3.4 Shutdown and Disable PrePay, Oracle and SS7 .................................... 31

3.4.1 Shutdown PrePay ........................................................................... 32 3.5 Disable CRON Jobs ................................................................................ 32 3.6 Create a Link for Perl Scripts................................................................... 32 3.7 Upgrading to SS8 Networks D7 1.4.0.2................................................... 33

3.7.1 Review /var/sadm/install/admin/default for pkgadds....................... 33 3.7.2 Set the System to Boot in 64-bit mode ........................................... 33 3.7.3 Update the /etc/system file ............................................................. 34 3.7.4 Upgrading from a Previous Version of D7 ...................................... 35 3.7.5 Copy apmconfig file ........................................................................ 39 3.7.6 Monitoring D7 Process States ........................................................ 39

3.8 Truncate PEG_COUNTER and DAILY_REVENUE ................................ 40 3.9 Upgrade to Oracle 9.2.0.6 ....................................................................... 40 3.10 Start the Upgrade Using the ppupgrade Script........................................ 41 3.11 Backing Up the PrePay Application Directories....................................... 42 3.12 Upgrading Configuration Files ................................................................. 43


5

3.13 Update the serviceDirectory file............................................................... 44 3.14 Apply the Application Upgrade Package ................................................. 44 3.15 Execute setupMultAccessRaters.ksh ...................................................... 45 3.16 Reconfigure Database Rollback Segments............................................. 46

3.16.1 Save Current Rollback Configuration ............................................. 46 3.16.2 Convert to One Large Rollback Segment ....................................... 46

3.17 Upgrade the Database Schema to PrePay 10.0.1 .................................. 47 3.17.1 Known Issues ................................................................................. 48

3.18 Review the Upgrade Log Files ................................................................ 49 3.19 Restore Original Rollback Segment Configuration .................................. 49 3.20 Install the License File ............................................................................. 49 3.21 Restore startup files................................................................................. 50 3.22 Apply Any Required Patches for PrePay 10.0.1...................................... 51 3.23 Install any Tailored Switch Configuration Files........................................ 51 3.24 Rerun setupSoftLinks.ksh........................................................................ 51 3.25 Verify Non-Standard PPADM or Oracle passwords ................................ 53 3.26 Update SMS Configuration (if used)........................................................ 54 3.27 Install the PrePay Client Application........................................................ 55 3.28 Configure Emergency Number Table (Lucent Only) ............................... 55

3.28.1 Potential Impacts ............................................................................ 56 3.29 Application Startup .................................................................................. 57 3.30 status_ppay Application Testing.............................................................. 57

Chapter 4. Notes for 922 users on major changes introduced with PrePay 10.0 ..58 4.1 New startup, shutdown, status, list, and restart scripts ........................... 58 4.2 Obsolete configuration files (prepay.cfg, prepay.default, etc.) ................ 59 4.3 New configuration files introduced in $PPHOME/etc .............................. 59 4.4 Existing ini, prf, cfg, and dat configuration/data files ............................... 60 4.5 Modifications to prepay_profile................................................................ 60 4.6 Configuration of XML file prepay_process_control_entities.xml.............. 61 4.7 Configuration of XML file prepay_global_entities.xml.............................. 65


6

4.8 Converting from old rating configuration to new XML rating configuration66 4.9 Modified Default Entity Variables............................................................. 67

4.9.1 Username/Password for ppadm (prepay_global_entities.xml) ....... 67 4.9.2 System Phone Length (prepay_system_entities.xml)..................... 67 4.9.3 Launcher......................................................................................... 68 4.9.4 Specifying Number of Client Funnel Processes (prepay_system_entities.xml)........................................................................ 68 4.9.5 Specifying PPAS ID (prepay_system_entities.xml) ........................ 69 4.9.6 Specifying Minimum Card Number Width (prepay_system_entities.xml)........................................................................ 69 4.9.7 Specifying Phone Card Access Code Width (prepay_system_entities.xml)........................................................................ 69 4.9.8 Specifying Host Entities (prepay_global_entities.xml, prepay_host_entities.xml) ............................................................................. 69 4.9.9 Specifying Service Entities (prepay_services_entities.xml)............ 71 4.9.10 Obsoleted Priority Variables ........................................................... 71 4.9.11 CC Network Variables .................................................................... 71 4.9.12 PreRater Entities (prepay_voice_rating_entities.xml)..................... 71 4.9.13 Configure Dialing Plan Entity Variables .......................................... 71 4.9.14 IVR Entities (prepay_ivr_entities.xml)............................................. 72 4.9.15 IVR-ROUTER Entities (prepay_ivr_entities.xml) ............................ 72 4.9.16 IPM Entities (prepay_provision_entities.xml).................................. 72 4.9.17 BulkActivation Variables (prepay_api_entities.xml) ........................ 73 4.9.18 Extracts Entities (prepay_ivr_entities.xml)...................................... 73 4.9.19 Card Expiration Variables (prepay_phone_card_entities.xml)........ 73

4.10 Review purging parmeters in purgeCreditCardTables.xml, purgeDataTables.xml, and purgeMNPTables.xml .................................................... 73 4.11 Mapping of prepay.cfg sections to XML entity files ................................. 74 4.12 Modifying Tracing/Logging Levels ........................................................... 78 4.13 Reconfigure /etc/services file................................................................... 79 4.14 Incorporate New ppadm Crontab File...................................................... 79 4.15 New alarmCollectors.cfg configuration file .............................................. 79 4.16 Sample Configuration Files ..................................................................... 79

4.16.1 serviceDirectory.sample ................................................................. 79 4.16.2 switchInterface.cfg.sample ............................................................. 79 4.16.3 winDefault.prf.sample ..................................................................... 79


7

4.17 New Features/Functionality in PrePay 10.0 ............................................ 79 4.17.1 Credit Card processing configuration parameters .......................... 79 4.17.2 API AutoPayment Feature .............................................................. 79 4.17.3 API PaymentAwards Feature ......................................................... 79 4.17.4 API EmailNotify Feature ................................................................. 79 4.17.5 Multiple Funds/Included Usage ...................................................... 79 4.17.6 Rewritten Access Rater .................................................................. 79 4.17.7 Mobile Number Portability............................................................... 79 4.17.8 System Startup/Shutdown Architecture .......................................... 79 4.17.9 Nortel TDMA HLR Provisioning ...................................................... 79 4.17.10 CTPv3.6.......................................................................................... 79 4.17.11 Subscriber Awards.......................................................................... 79

4.17.11.1 Credit Awards based on single payments ............................ 79 4.17.11.2 Discount Awards based on cumulative payments ................ 79 4.17.11.3 prepay_process_control_entities.xml variables: ................... 79 4.17.11.4 PrePay license browser option: ............................................ 79 4.17.11.5 Process in API subsystem: ................................................... 79 4.17.11.6 prepay_voice_rating_entities.xml (for awdDaemon)............. 79

4.17.12 INAP/CS1R Interface...................................................................... 79 4.17.13 GUI/Crystal Reports........................................................................ 79 4.17.14 API XML Username/Passwords ..................................................... 79

4.18 Log files in 10.0.x..................................................................................... 79 4.19 Installation and configuration of 10.0.1 EAM ........................................... 79 4.20 Start up PrePay, Oracle, and SS7........................................................... 79 4.21 Back up the New PrePay and Oracle ...................................................... 79

Chapter 5. Configuration for Data Billing using the General Charging Interface79

Chapter 6. Post-Upgrade Steps..................................................................................79 6.1 Tailor File and Table Purging Scripts ...................................................... 79 6.2 Review other sample files........................................................................ 79 6.3 Restore CRON Entries ............................................................................ 79 6.4 Purge Obsolete Configuration Files......................................................... 79 6.5 Roll Out the Client Workstation ............................................................... 79


8

6.6 Delete Work Area Files............................................................................ 79

Appendix A. Upgrading Veritas Volume Manager and File System to 4.x ..............79 A.1 Preface .................................................................................................... 79 A.2 Required Materials .................................................................................. 79 A.3 Upgrade Veritas VxVM and VxFS to 3.5 ................................................. 79 A.4 Save the Veritas Volume information for safekeeping............................. 79 A.5 Load the Volume Manager (VxVM) 3.5 CD ............................................. 79

6.6.1 Unencapsulate the boot disk and save the VxVM info ................... 79 A.6 Remove the Veritas File System (VxFS) packages................................. 79 A.7 Remove the VxVM packages .................................................................. 79 A.8 Load the Volume Manager (VxVM) 3.5 CD ............................................. 79 A.9 Individual patches for VxVM with MP2 and VxFS with MP2.................... 79

Appendix B. Changes to PrePay XML Configuration Files.......................................79

Appendix C. Changes to PrePay Database Tables ......................................................79

Appendix D. Switch Interface Configuration Files .....................................................79 D.1 switchInterface.cfg.sample ...................................................................... 79 D.2 capSwitchInterface.cfg.sample................................................................ 79 D.3 denyAnnouncementTable.cfg.sample ..................................................... 79 D.4 profileFile.prf.sample ............................................................................... 79 D.5 is41eeDefault.prf.sample......................................................................... 79 D.6 CapDefault.prf.sample............................................................................. 79 D.7 isupDefault.prf.sample............................................................................. 79 D.8 winDefault.prf.sample .............................................................................. 79 D.9 pplError.English.Sample.......................................................................... 79


9

Appendix E. Performing a Solaris Rollback................................................................79

Appendix F. Upgrading from Oracle 9.2.0.4 to version 9.2.0.6 on Solaris 8 ............79 F.1 Preparation Steps for Oracle 9.2.0.6 ....................................................... 79

F.1.1 Check Solaris is Running in 64-bit Mode........................................ 79 F.1.2 Check Available Space in $ORACLE_HOME File System............. 79 F.1.3 Record the Database Character Set............................................... 79 F.1.4 Record the Database Block Size .................................................... 79 F.1.5 Check for use of N-type Columns................................................... 79 F.1.6 Check for Corruption in the Dictionary............................................ 79 F.1.7 List All Objects that are not VALID ................................................. 79 F.1.8 Create a Script to Compile All Invalid Objects ................................ 79 F.1.9 List the Grants ................................................................................ 79 F.1.10 Ensure No Files Need Media Recovery.......................................... 79 F.1.11 Ensure No Files are in Backup Mode ............................................. 79 F.1.12 Prepare the System Rollback Segment.......................................... 79 F.1.13 Ensure Freespace in Rollback Tablespace .................................... 79 F.1.14 Ensure SYS and SYSTEM have ‘SYSTEM’ as Default Tablespace79 F.1.15 Record the Locations of All Control Files........................................ 79 F.1.16 Ensure NLS_LANG Variable is Set Correctly ................................. 79 F.1.17 Disable All Oracle Related Batch and Cron Jobs ........................... 79

F.2 Upgrade Oracle to 9.2.0.6 ....................................................................... 79 F.3 PreParation Tasks ................................................................................... 79

F.3.1 Maintenance window tasks............................................................. 79

Appendix G. initppay.ora...............................................................................................79 G.1 Obsolete parameters for Oracle 9i .......................................................... 79

Appendix H. Rolling Back the PrePay Application.....................................................79 H.1 Rolling Back PrePay 10.0.1..................................................................... 79 H.2 Rolling Back Oracle from 9.2.0.6 to 9.2.0.4............................................. 79 H.3 Rolling Back from Distributed7 1.4.0.2 to 1.3.1.5 .................................... 79


10

Preface

The upgrade to PrePay release 10.0.1 requires that your system be at PrePay Release 9.2.22P1, 9.2.2P2, 9.2.2P3 or 10.0. This document does not lay out the steps to upgrade to any of those versions. If needed, please see the appropriate upgrade documents to get your system to one of these versions. Additionally, see the note below.

1.1 Upgrading from Earlier Releases Customers upgrading from PrePay 5.5.8, 5.5.9, or 6.0 to release 10.0.1 must first upgrade their servers to release 7.0 or release 8.0 on Solaris 2.8. From there you can upgrade to PrePay 10.0.1.x.

The only upgrade paths for 10.0.1 is from 9.2.2X and 10.0 . Not sure of whether the above will be relevant.

1.2 Required Materials The following materials are required to upgrade to PrePay 10.0.1

• PrePay 10.0.1 Client Software CD, P/N ????.


11

• PrePay 10.0.1 Server Upgrade Software CD that contains the application upgrade package and upgrade toolkit, P/N ????

• PrePay 10.0.1 Server Software Distribution CD, P/N ????

• SS8 Networks Distributed7 version 1.4.0.2 Software license conversion is required when upgrading from NewNet Access Manager to SS8 Distributed7. Contact Lightbridge support to convert your existing license.

• Suggestion: All customers would be already on Distributed 7 when upgrading to 10.0.1 so no migration from Access manager to D7 will take place

Note: the SS8 Networks Distributed7 software package is included on the PrePay 10.0.1 Server Software Distribution CD, P/N 870-0584-001.

• Oracle 9.2.0.6 Upgrade CD, P/N ???.

• Solaris Patches Feb. 18, 2004 CD. This would need to be changed to the Solaris kernel patch May 2005

Note: Kernel patch 108528-29 is the highest level supported by D7 and PrePay 10.0.1. This could need to be changed as Kernel patch for May 2005 is 117350-25

Note: The Solaris Recommended Patches and kernel patch 108528-29(patch id should be changed to 117350-25) are on the Solaris Patches CD and the document 'Solaris Patch Upgrade – Kernel 29.pdf' should be used to install them. If desired, a separate maintenance window can be scheduled to install Solaris patches. Be sure to have the local system administrator check for other patches that may be required for system-specific hardware support.

• Solaris 8 patch 117000-05 or later. (This lines needs to be updated if 117350-25 is going to be recommended)

• Veritas Volume Manager and File System Version 4.x, P/N ???.

Note: The Veritas software CDs may also be used: Veritas Storage Solutions V4.x CD containing Volume Manager and File System, P/N ???, ???.

• SS8 Distributed7 User Manual, P/N ??? dated ???

• PrePay 10.0.1 license file for any licensed features.

• Tape cartridges for backup


12

1.3 Disk Space Requirements To install PrePay 10.0.1, you must meet the following minimum disk space availability requirements.

Disk Space Requirements

/<temparea>/work 150 MB available for the PrePay 10.0.1 Upgrade Package and

500 MB minimum (depending upon the size of /prepay)

Instructions for calculating temporary working space are provided in the section Estimating the Upgrade Space Requirements in this document.

/<temparea>/cd_sw 2GB available

/oracle Approximately 2GB available is required for the uncompressed Oracle 9.2.0.6 package.

An additional 2GB available is required for the installed 9.2.0.6 Oracle Home.

1.4 Time Estimate for Upgrading to PrePay 10.0.1 The estimate for installing the PrePay 10.0.1 package is listed in the table below.

Task Time Estimate

Test DB Conversion (I don’t think there is a DB conversion in this upgrade).

As long as needed, no downtime required.


13

Recommend that several days, at a minimum, before upgrade are scheduled to test, review, and correct data.

Backups System dependent

Preparation time 3-4 hours

Start of application downtime

Shut down application System dependent. Shutdown time depends on the number of processes on the PPAS platform.

Upgrade to Solaris 8.0, Feb. 2004 (Solaris version may need to be changed as Chirag’s suggestion below)w/ patches, and Veritas Volume Manager 4.x, Veritas File System 4.x

Note: These upgrades can be scheduled to be performed in a maintenance window before the PrePay upgrade, if desired.

Approx 1-2 hours

Upgrade Oracle to version 9.2.0.6 60 minutes

Upgrade to SS8 Distributed7 1.4.0.2 60 minutes

Perform PrePay 10.0.1 Application Upgrade 30 minutes

Perform PrePay 10.0.1 Schema Upgrade (option 4) 60 minutes

Perform 9.2 DB Data Conversion will it be 9.2? (Is there really a DB conversion from 9.2.2.X to 10.0.1?)

Varies depending on size of database. Plan on at least 2-3 hours.

Test period/go-no go point for release. Minimum 1 hour


14

End of application downtime

Upgrade training environment (no application downtime) (What is training environment? We don’t have the training/training user anymore in 10.0.1)

30 minutes

Perform post-upgrade cleanup steps. 30 minutes


15

Pre-Upgrade Procedures

2.1 Review the PrePay ReadMe Notes Obtain and review the readme notes accompanying the PrePay software for any known issues that were documented after the publishing of this document. There may be manual changes or patches required before performing the upgrade and/or conversion.

You may need to review the ReadMe notes for Release 9.2.2P1, 9.2.2P2, 9.2.2P3, 10.0 and then 10.0.1 depending on your current PrePay version.

2.2 Preparation of Solaris 2.8

2.2.1 Kernel 29 Solaris kernel level 29 is the supported version for PrePay 10.0.1 and beyond. Patch 108528-29 updates the operating environment to level 29 and is included in the Feb. 18th, 2004 Solaris recommended patches We would need to put the May 2005 Kernel patch here . patch id is 117350-25

2.2.2 Recommended and Required Patches Using the Solaris Patches CD, execute the instructions found in the Solaris Patch Upgrade Guide.pdf.

For recommended patches, select only the 8_Recommended_20040218.zip. Do NOT install any 8_Recommended patch file other than this one. (If 117350-25 is going to be


16

recommended then this paragraph needs to be updated and next paragraph omitted because 117350-25 obsoletes 1117000-05.)

Install Solaris 8 patch 117000-05 or later. This corrects a problem where vmstat reports the incorrect number of ‘blocked’ processes with kernel level 29. This patch must be installed in single-user mode and requires a reboot immediately after installation.

Install the SAN Foundation Kit if not already installed.

If using a Sun A5x00 disk array then install the individual patches following the same guide.

2.2.3 64-bit Mode Solaris The SS8 D7 software should be ran using a booted Solaris 64-bit kernel if the physical SS7 boards are PCI and not SBUS. Prior to installing D7, the system should be checked to see if PCI cards are being used and the Solaris 64-bit packages are installed. If PCI boards are being used but the 64-bit packages are not installed, install them but continue to boot the 32-bit kernel until D7 is installed. During the D7 installation, the NVRAM setting will be modified to boot the 64-bit kernel.

To confirm if 64-bit packages are installed, use the pkginfo command and filter on 64-bit. At a minimum, the core packages should be installed. Contact your local Sun Support to determine if others packages are required. pkginfo | grep 64-bit system SUNWcarx Core Architecture, (Root) (64-bit) system SUNWcslx Core Solaris Libraries (64-bit) system SUNWcsxu Core Solaris (Usr) (64-bit)

When PrePay is upgraded to 10.0.1, the Solaris Operating Environment must be booted in 64-bit mode. This is required because the 64-bit version of Oracle will be installed.

2.3 Preparation for Veritas 4.x Upgrade If needed, Veritas Volume Manager and File System can and should be upgraded before PrePay 10.0.1 and in a separate maintenance window.


17

For the procedures needed to upgrade Veritas Volume Manager and File System, see Appendix A, (As of verification, there is no procedure created yet to upgrade to Veritas 4.x. We only have straight Veritas 4.x installation procedure.)

2.4 Pre-upgrade Database Conversion Analysis Prior to scheduling the actual 10.0.1 upgrade, perform database conversion analysis according to the instructions in Appendix B – Pre-Upgrade Database Conversion Analysis. This will require the unloading of scripts from the PrePay 10.0.1 Maintenance CD. (Is there really a DB conversion for this upgrade? Appendix B is not relevant to this procedure.)

2.5 Prepare the Upgrade Staging Directory Identify a file system and directory with sufficient space for upgrade working files (application, table exports). Create a working directory called work in that file system. This directory path will be referenced as /<temparea>/work in all installation instructions.

WARNING: Do not use the /prepay or /tmp file system.

Example:

If you are using the file system /spare, the working directory /<temparea> would refer to /spare.

su – ppadm cd /spare mkdir work

2.5.1 Load the Upgrade Toolkit and Application Files 1. Copy the upgrade toolkit tar file and the PrePay 10.0.1 application tar.gz file from

the CD-ROM to the file system upgrade work directory by typing the following: cp -pf /cdrom/cdrom0/* /<temparea>/work


18

2. Untar the upgrade tool kit by executing the following commands as user ppadm. Note that the build and revision references on the tar package may vary. cd /<temparea>/work tar –xvf PrePay100_1.upgrade_tool.<buildid>.<rev>.tar

Example: tar xvf PrePay100_1.upgrade_tool.tar

2.5.2 Pre-Stage CD Contents to Disk The purpose of this task is to copy the contents of all required CDs to disk so that downtime during the production upgrade can be minimized.

1. Copy the PrePay 10.0.1 Upgrade CD :

Insert the CD labeled PrePay 10.0.1 Upgrade CD mkdir –p /<temparea>/cd_sw/prepay100_1_upgrade cd /<temparea>/cd_sw/prepay100_1_upgrade cp –r /cdrom/cdrom*/* .

2. NOTE: The Oracle 9.2.0.6 package requires Solaris 8 64-bit kernel. If the result of running “isainfo –vn” does not return “64-bit sparcv9 applications” then installation can not continue until the system is running in 64-bit mode.

If Oracle server is to be upgraded to 9.2.0.6 then:

The oracle information mentioned below needs to be modified below for 9.2.0.6

Insert the CD labeled Lightbridge Oracle 9.2.0.6 into the CD drive Su - oracle mkdir –p $ORACLE_BASE/patches cd $ORACLE_BASE/patches cp /cdrom/cdrom*/*.zip .

3. Veritas Volume Manager or File System are to be upgraded to 4.x then:

Insert the CD labeled PrePay Veritas VXVM4.x/VXFS4.x mkdir –p /<temparea>/cd_sw/veritas cd /<temparea>/cd_sw/veritas tar xvf /cdrom/cdrom*/VOLUME_MANAGER/VOLUME_MANAGER.TAR


19

tar xvf /cdrom/cdrom*/FILE_SYSTEM/FILE_SYSTEM.TAR

4. Copy the Solaris patches to disk:

Insert the CD labeled Solaris Patch Upgrade – Kernel 29 this should be the solaris version needed if it is 117350-25 then it will be 25 mkdir –p /<temparea>/cd_sw/solaris_patches cd /<temparea>/cd_sw/solaris_patches cp –r /cdrom/cdrom*/* .

2.6 Confirm the Directory Locations for Application Packages The following are the standard directory locations that should be confirmed before starting the installation. Check the target system and confirm these locations. If they are different, some configuration files may need to be changed as part of the upgrade.

Directory Locations for Applications Packages

Directory Description If not the same, then review and change the following files:

/newnet Directory where NewNet Access Manager or SS8 D7 software is installed.

There are no files to change, but the actual directory name must be used when installing the D7 application.

/home/ss7admin

Home directory for administrative user of the NewNet or D7 software (ss7admin).

There are no files to change, but the actual directory name must be used when installing the D7 application.

/cdr Directory where bytestream data for call data is kept.

There are no files to change, but must use the actual directory name when deleting bytestream files

/udr Directory where There are no files to change, but must use the


20

Directory Locations for Applications Packages

Directory Description If not the same, then review and change the following files:

bytestream data for data billing is kept.

actual directory name when deleting bytestream files

/logs All log files All errors and warnings generated from the PrePay application are stored here.

/prepay Directory where PrePay application is installed.

$PPHOME/etc/prepay_profile

/oracle Directory where Oracle software is installed.

$PPHOME/etc/prepay_profile

~oracle/cfg/oracle_profile

/etc/init.d/oracle

/var/opt/oracle/*

2.6.1 Create the /udr File System If data billing is to be implemented then a separate file system called /udr should be created to hold byte-stream files similar to the /cdr file system. This new file system should have its mountpoint owned by the ppadm Unix user and prepay group. Create this file system prior to upgrading to PrePay 10.0.1.

2.7 Estimate the Upgrade Space Requirements Space is required in the upgrade working directory to store the application and upgrade toolkit tar files.

Application upgrade: 150MB

Upgrade toolkit: 2.5MB


21

To estimate the amount of space required in the working directory (/<temparea>/work for saving $PPHOME directories, use the following commands:

su - ppadm cd /<temparea>/work ./calc_saveprepay.ksh

Executing this command will return a report of the amount of space required, and a message stating whether or not there is currently sufficient space to save the $PPHOME directories.

The total working space required in the working directory (/<temparea>/work) is:

Save copy of $PPHOME: ___ MB

If there is not sufficient space in the current working directory, either clear sufficient space, or else move the upgrade packages to a different location.

2.7.1 Estimating the Space for PrePay 10.0.1 Operation The size of the $PPHOME/bin, $PPHOME/libs, and $PPHOME/inqload directories increased between the 9.2.2.x and 10.0.1 releases. An additional 40 MB of space will be used in the $PPHOME directory for binaries and libraries.

Verify that the $PPHOME file system has sufficient space to support the increased program sizes.

The following command can be used to determine the space available in the $PPHOME file system. The df command lists used and available space in kilobytes.

df -k $PPHOME

2.8 Estimating the Space for Database Table Changes This upgrade makes minor table changes. Columns are added to some existing tables, indexes are dropped and created. Many of these changes are of minimal impact.

Tablespaces are categorized as follows:

DDATA01, IINDEX01 –Used for ACCESS_NUMBER table and indices


22

DDATA02, IINDEX02 –Used for CALL_CHARGE, CALL_DETAIL tables and indices

DDATA03, IINDEX03 –Growing tables

DDATA04, IINDEX04 –Reference tables

2.8.1 Table Changes Requiring a Review of Tablespaces There are no significant table growth areas in this release.

The largest potential impact comes from optional use of “Fund Bundles” in Prepay 10.0.1. If you plan to use Fund Bundles, potential storage increases will be based on a “percentage of subscribers who use Fund Bundles” basis. Please consult with Lightbridge support to estimate any storage increases.

2.8.2 Determine Freespace in Each Tablespace Review the amount of freespace currently available in each tablespace. The query below will show total freespace within each tablespace but does not show the number or size of freespace segments within the total. Adequate freespace to fit the initial extent of new tables and indexes must be made available prior to the production database conversion. sqlplus system/{system_password} set echo on; select b.tablespace_name "Tablespace name", b.bytes "# bytes ", (b.bytes - sum(nvl(a.bytes,0))) "# used ", sum(nvl(a.bytes,0)) "# free ", round((sum(nvl(a.bytes,0))*100)/(b.bytes), 1) "%free" from sys.dba_free_space a, sys.dba_data_files b where a.file_id(+) = b.file_id group by b.tablespace_name, b.file_id, b.bytes order by b.tablespace_name;


23

2.9 Acquire the PrePay 10.0.1 License Files for Optional Features There are several new feature options that can be enabled in PrePay 10.0+.

These are: MobileToMobileCustom False CreditCardProcessing False CS1R False CTP False

The following features can be specified in the PrePay license file: PhoneCardOwnRegion False RegionalPhoneCards False CallingCircleCustom False DatabaseRetrievalInterval 300 SubscriberAward False CallingPartyPays False IntelligentCallingCard False SubscriberLimit 1000000 SmsCreditBalance False CallingCircle False SubscriberHistoryAPI False MobileToMobileCustom False CreditCardProcessing False ActiveSubscriberStates 1 2 3 4 SubscriberWarningPercentage 10 SubscriberProfileAPI False GlobalPhoneCards False SubscriberAccountAPI False PrePaySNMPMonitor False ProvisionSubscriptionAPI False

Note: The CallingCircleCustom option is a billable option that requires additional software. Further installation and configuration are required for this licensed feature.

Prepare the 10.0.1 license file before the 10.0.1 upgrade and install into /prepay/data post upgrade.

The host Id of the server must be provided for generating the license file. The files will be installed in the appropriate directory during the upgrade.


24

Important: If the customer has purchased or changed any licensed features as part of upgrading to PrePay 10.0.1 or wishes to use Credit Card Processing, a new / replacement license file is required.

This file must be built and installed by Lightbridge Technical Support before these features can be enabled. Type the licenseBrowser command to get the license details.

2.10 Note on configuration files in PrePay 10.0.1 NOTE: See Section 4 for more information.

PrePay 10.0.x and beyond no longer use the older format configuration files in the /prepay/etc directory. In their place, XML configuration files are used in /prepay/etc/xml. These files are created during the upgrade and are set to a pre-defined standard set of values.

A utility program (/prepay/bin/cmpcfg) is provided in 10.0.1 which will list old configuration values (and where they are located) and compare the equivalent value in the xml configuration files. To use this utility most effectively, post-upgrade, you should type the following command:

su – ppadm cd /prepay/bin cmpcfg | more

The “more” component is needed since this listing will be very large.

2.11 Prepare the Switch Configuration Files The following files should be reviewed and edited for correctness, depending upon the type of switch interface being used. Compare the .sample file to the .prod file copied in an earlier step. Create a .new file by copying a .sample and then manually adding in customizations identified in the .prod file.


25

2.11.1 All Interfaces

2.11.1.1 switchInterface.cfg.sample

This is a sample master switch interface configuration file. Configurations for individual or wild-carded point codes are configured in this file. Point codes may be configured within profile files that are referenced within this file.

For each MSC that interfaces with an ss7Interface process, add an entry for its point code and a corresponding profile file that matches its protocol. For example, if the MSC at point code 2-1-2 uses IS-41EE then an entry would appear as: 2-1-2 profile is41eeDefault.prf

Assuming a IS-826 MSC interfaces with PrePay at point code 2-3-1, an entry in this file would appear as: 2-3-1 profile winDefault.prf

MSC entries can override the values defined in their xxxDefault.prf file by adding them as arguments such as: 10-20-135 profile isupDefault.prf profile isupSingleSwitch.prf

For GSM, if the PrePay server connects first to an STP to access an MSC, then enter the point code of the STP and it’s protocol profile file instead of the MSC.

2.11.1.2 capSwitchInterface.cfg.sample

This is a sample master switch interface configuration file for Camel protocol. This file needs to be configured if camelIntf is going to be used. Configuration is the same as the switchInterface.cfg above but using capDefault.prf profile. All switches that are going to be interfacing with the camelIntface need to be defined in this file.

There are three ways to configure this file. Using point code, E.164, and wild card. Examples below:

Point Code Based Configurations

0-57-1 profile capDefault.prf

E.164 (GT Address) based configurations


26

16003005001 profile capDefault.prf

Wild Card configuration

0-57-* profile capDefault.prf

*-*-* profile capDefault.prf

* profile capDefault.prf

1600300* profile capDefault.prf

2.11.1.3 profileFile.prf.sample

This a sample profile file for the switch configuration. The values defined in this file are picked up as default values if they are not defined in a switch-specific configuration file. For example, this file might be used to define error routing actions for specific failure cases that would be used, regardless of the switch protocol in use.

2.11.1.4 denyAnnouncementTable.cfg.sample

This file contains the announcement IDs for configured denial reasons. Review and change if required for the switch configuration.

.

The format of this file has changed and must be edited if the file $PPHOME/etc/denyAnnouncementTable.cfg currently exists.

This file has an additional column added to support switch-based and IVR-based announcements. Compare this to your previous release and set the column “Announcement Type” to an appropriate value for your installation.

The current file $PPHOME/etc/denyAnnouncementTable.cfg must be edited such that an additional column is provided for each denial reason. The value in the third column may be set to '0' for no announcement, 1 for switch-based announcement, or 2 for IVR-based announcement. The settings must match what is defined with the customer's switch.

2.11.2 IS-41EE is41eeDefault.prf.sample


27

This file contains default error routing actions and announcement IDs for IS41EE signaling. Review and change if required for the switch configuration.

2.11.3 WIN-II winDefault.prf.sample

Caution: Changes have been made to the sample file in this release. If you are using the WIN II/IS-826 protocol, review this new file carefully and update your existing file with new parameters.

This file contains default information for the WINII configuration, including announcement IDs and error routing actions. Review and change if required for the switch configuration.

2.11.4 GSM capDefault.prf.sample

This file contains sample default setup information for GSM configuration, including announcement IDs and error routing actions. Review and change if required for the switch configuration.

2.11.5 ISUP isupDefault.prf.sample

This file contains sample default setup information for ISUP signaling, including switch ID, other miscellaneous setup parameters, announcement IDs, and trunk block configurations. At a minimum, switch IS and trunk block information must be modified/defined if this protocol is being used. pplError.english.sample

This file contains the English text of error messages for the ppl server. It should not normally require modification.

2.11.6 IS-41P is41pDefault.prf.sample


28

This file contains sample default setup information for IS-41P signaling, including switch ID, and other miscellaneous setup parameters. At a minimum, switch IDs must be modified/defined if this protocol is being used.

2.12 Review and Prepare D7 Configuration

2.12.1 NOTE: PrePay 10.0.1 requires D7 version 1.4.0.2

2.12.2 Upgrading from Distributed7 1.3.1.x 1. Save the current D7 database by using the db2text command. This step may

require Distributed7 be stopped in order to run. If so, schedule a maintenance window to complete this task.

Note: Ignore errors having the form "cannot open /newnet/access/RUNn/DBfiles/" where the "n" in "RUNn" could be 0 through 7. su - ss7admin mkdir /newnet/db2text_beforeD71402 $EBSHOME/access/bin/db2text /newnet/db2text_beforeD71402

2.12.3 Prepare New D7 Configuration Files Review your current SS7 configuration and create mml files for the Distributed7 configuration using the following instructions. Sample files are contained on the PrePay Server Upgrade CD in the tar file ‘D7_samples.tar’, and may be modified to create production configuration files.

There are 3 separate files where components of the stack are configured. One of the files varies depending on protocol.

For ANSI configurations the required files are listed with their editing requirements.

pci3xpq.mml -change the value of the HOSTNAME parameter

ppas_ansi.mml -change the value of the HOSTNAME, SCP, and DPC parameters, add/change links and link sets


29

sccp.mml -change the value of the SCP and SSN parameters

For ITU/CCITT configurations, the required files are listed with their editing requirements.

pci3xpq.mml -change the value of the HOSTNAME parameter

ppas_itu.mml -change the value of the HOSTNAME, SCP, and DPC parameters, add/change links and link sets

sccp.mml -change the value of the SCP and SSN parameters

2.13 Note on the Emergency Number Table (Lucent Only) The Emergency Number Table (emergencyNumberTable.cfg) introduced in 9.2 has not been converted to xml format.


30

Upgrading to PrePay Release 10.0.1

The following activities should be performed only within a maintenance window when the PrePay application can be shut down.

3.1 Review the PrePay 10.0.1 ReadMe Notes Obtain and review the readme notes accompanying the PrePay software for any known issues that were documented after the publishing of this document.

There may be manual changes or patches required before performing the upgrade and/or conversion.

3.2 Backup Current PrePay and Oracle To support a rollback of the PrePay or Oracle upgrades, a complete backup of both subsystems must be completed.

For PrePay, backup all file systems owned or used by the ppadm UNIX user.

For Oracle, backup all file systems used for tablespaces, redos, rollbacks, archive, temp, /var/opt/oracle, etc. Ensure the backup is valid in terms of being a recoverable backup set with archived redo logs.


31

3.3 Miscellaneous backup 1. Save a copy of current PrePay license configuration for 922 upgrades.

licenseBrowser > licenseBrowser.922.txt

2. For 922 upgrades, capture a snapshot of the current rating configuration to be used in configuring the new XML files after the installation of the PrePay 10.0.1 software. /prepay/bin/ratingConfig –t \

/<temparea>/cd_sw/prepay101_upgrade/ prepay922.rating.config.txt

3. Enable write privileges on the $PPHOME/phonecard directory. chmod –R u+w /prepay/phonecard chmod –R u+w /prepay/conversion chmod –R u+w /prepay/oracle/cfg chmod –R u+w /prepay/sql

4. Add privileges to the prepay database user (by default ppadm). You must do this as the Oracle system user. sqlplus system/manager SQL> GRANT EXECUTE ON DBMS_AQADM TO ppadm; SQL> GRANT EXECUTE ON DBMS_AQ TO ppadm; SQL> exit

3.4 Shutdown and Disable PrePay, Oracle and SS7 *** Beginning of Downtime ***

As root, shutdown the PrePay subsystems and prevent it from restarting during a reboot. The Oracle database instance is left up and running to support schema changes that will be made during the PrePay upgrade procedure. Distributed7 will be upgraded passively so there is no need to bring it down.

su – cd /etc/init.d mv prepay .prepay.pre101


32

mv oracle .oracle.pre101 mv ss7 .ss7.pre101

3.4.1 Shutdown PrePay If upgrading from a 9.2.2.X system:

su – ppadm ppstop system ps –ef | grep ppadm kill –9 {any remaining PrePay processes that may not have

shut down}

If upgrading from a 10.0 system: su – ppadm stop_ppay ps –ef | grep ppadm kill –9 {any remaining PrePay processes that may not have

shut down}

3.5 Disable CRON Jobs Save the current cron entries before removing them. They will be restored after the upgrade has passed acceptance testing.

cd /<temparea>/work crontab –l > ppadm.crontab.pre10_0_1 crontab –r

3.6 Create a Link for Perl Scripts 1. Create a link for execution of Perl scripts.

2. Execute the following command for creating the link for Perl. su –

3. Check for any links by typing the following command: ls -l /usr/local/bin/perl

4. If a file or link exists, skip the rest of the link step.


33

5. Look for Perl in other directories by typing the following command: ls -l /bin/perl /usr/bin/perl

6. If not found, try the following command: which perl

7. If /bin/perl exists, type: ln -s /bin/perl /usr/local/bin/perl

8. If /usr/bin/perl exists, type: ln -s /usr/bin/perl /usr/local/bin/perl

WARNING: If Perl is not installed on the system, contact Lightbridge Technical Support for assistance in acquiring and installing Perl.

3.7 Upgrading to SS8 Networks D7 1.4.0.2

3.7.1 Review /var/sadm/install/admin/default for pkgadds The upgrade to D7 uses the pkgadd command. It may have problems installing the new software if the contents of /var/sadm/install/admin/default do not have the following line:

Instance=unique

Review the contents of this file and add/modify the above line as the root user if it is not already present.

3.7.2 Set the System to Boot in 64-bit mode During the preparation phase, the system should have been checked to verify it has the Solaris 64-bit versions of the Core packages. If the system does not have these, then do not continue with this process until Solaris has been updated with these packages.

1. Use the eeprom command to set the system to boot in the 64-bit mode.


34

If the eeprom command does not return a value for the boot-file it is already set for 64-bit mode and this section can be skipped.

su - eeprom boot-file boot-file: data not available.

If the eeprom command returns a value for boot-file:

eeprom boot-file boot-file=kernel/unix

Use the following commands to clear the boot-file value.

eeprom boot-file= eeprom boot-file

3.7.3 Update the /etc/system file Note: This section is not talking about a /prepay/etc/system file. Such a file does not exist.

Note: These changes should already have been made if Oracle has been upgraded to version 9 previously. Use these values to confirm your settings in this event.

The following entries should be checked in /etc/system. Based upon the Lightbridge installation process, all of these values should be equal to or higher than the values required by the third-party software packages installed in this release. If changes are required, notify Lightbridge support, as there may be other related system impacts. A reboot is required if changes are made to this file.

Settings: * * Shared Memory (shm) * set shmsys:shminfo_shmmax=4294967295 set shmsys:shminfo_shmmin=1 set shmsys:shminfo_shmmni=512 set shmsys:shminfo_shmseg=512 * * Semaphores (sem) *


35

set semsys:seminfo_semmni=4096 set semsys:seminfo_semmns=4096 set semsys:seminfo_semvmx=32767 set semsys:seminfo_semmsl=512 set semsys:seminfo_semopm=128 set semsys:seminfo_semmnu=4096 set semsys:seminfo_semume=256 * Obsolete *set semsys:seminfo_semmap=128 * * Message Parameters (msg) * set msgsys:msginfo_msgmax=4096 set msgsys:msginfo_msgmnb=16384 set msgsys:msginfo_msgmni=1024 set msgsys:msginfo_msgtql=1024 * Obsolete *set msgsys:msginfo_msgssz=16 *set msgsys:msginfo_msgseg=1024 * * Other * * "Hard" limit on file descriptors (ulimit -Hn) set rlim_fd_max=1024 * "Soft" limit on file descriptors (ulimit -n) set rlim_fd_cur=1024 set maxusers=1024 set pt_cnt=256 * Streams setting for D7 set strctlsz=4096 set sq_max_size=32

3.7.4 Upgrading from a Previous Version of D7 Use these steps to upgrade to the 1.4.0.2 version of Distributed7 if Distributed7 was previously installed.


36

Pre-upgrade instructions: 1. Obtain D7 1.4.0.2. It is named as

Distributed7_1.4.0.2.tar.gz. 2. unzip and untar the file. Untarring will create a folder

named "packages" which contains D7 1.4.0.2 packages.

3. As user ppadm, issue command "/newnet/access/bin/getcfg" and collect the output for later verification of instance number of D7 boards.

Backup license and configuration: NOTE: The upgrade process will not overwrite the license or

configuration files. Making backup copies of up these files is

only required if you intend to remove the previous version of D7. As Root: 1) cd /newnet 2) mkdir -p backup/1_4_0_1/etc 3) cp access/etc/license.dat backup/1_4_0_1/etc 4) mkdir -p backup1_4_0_1/RUN/config/PMGR 5) cp access/RUN/config/PMGR/apmconfig

backup/1_4_0_1/RUN/config/PMGR Live Upgrade of Distributed7 User Considerations The following list describes system operations and user

choices at the time of installation of the new release of the Distributed7

software: pkgadd results in the full installation/activation of

the Distributed7 software the very first time it installed. No

additional action is necessary.


37

If a version of Distributed7 is already installed on the target machine,

pkgadd results in a passive installation of the new release. The release

that is already installed on that machine is not removed or deactivated.

In this case, users are required to run the ebs_setrelease command to

activate the newly installed release. The ebs_setrelease command allows

users to switch between different Distributed7 releases installed on the

same machine When multiple versions of Distributed7 system software are

installed on one machine, an access tree is created under the base product

installation directory for each new version, e.g., access.1.3.1.5,

access.1.4.0, access.1.4.0.1, access.1.4.0.2. To make it easy to switch between the

different versions of Distributed7, $EBSHOME/access entry is maintained as a

symbolic link, i.e., to the Distributed7 version that is currently in use. When multiple versions of a Distributed7 software

package co-exist: The pkginfo command lists all such packages. Users

should issue the ebs_setrelease -i command to find out which

Distributed7 version is currently running. It is possible to remove obsolete versions using the pkgrm

command. Alternately, the ebs_pkgrm command removes all software

packages associated with a particular Distributed7 version. Procedure Note: You must run this procedure as 'root'


38

1. Use the pkgadd utility to install version 1.4.0.2 of

Distributed7 software on one of the host machines. Note that since version 1.3.1.x is already in use,

installation of this new version is passive, i.e., the newly installed

version is not activated until the ebs_setrelease is run to explicitly choose

it. 2. After installing the new release, use pkginfo to

list all UNIX software packages installed on that host, and verify that

both version 1.3.1.x and version 1.4.0.2 are listed. This ensures that

the passive installation process was successful. 3. Run the ebs_setrelease utility to activate the newly

installed version of software on that host: $EBSHOME/access/install/ebs_setrelease 1.4.0.2 Answer "Y" (yes) when asked to convert databases. This shuts down the Distributed7 software on that host,

and upgrades all necessary system components, i.e., drivers,

executables, configuration/database files, to version 1.4.0.2. 4. Run the ebs_setrelease command again to confirm

which software release is currently in use: $EBSHOME/access/install/ebs_setrelease -i 5. Run "start_ppay D7" to start up the 1.4.0.2 release

software. Wait until all appropriate Distributed7 daemons are started

before starting any


39

application layer software. Note: ===== The ebs_setrelease script will copy and convert the runtime

databases and license files as necessary. No action is required on your

part. However, it does not copy the apmconfig file. To complete the

upgrade: 1) cd /newnet/backup/1_4_0_1/RUN/config/PMGR 2) cp apmconfig /newnet/access/RUN/config/PMGR

3.7.5 Copy apmconfig file If this is DA installation, on SPT nodes, copy /prepay/allhome/ss7admn/config/apmconfig.d7.1.2.0.dist to /newnet/access/RUN/config/PMGR directory as apmconfig. $ cd /newnet/access/RUN/config/PMGR $mv apmconfig apmconfig.{mmddyyy} $ cp -p $PPHOME/allhome/ss7admn/config/apmconfig.d7.1.2.0.dist /newnet/access/RUN/config/PMGR/apmconfig For non-DA installations, copy /prepay/allhome/ss7admn/config/apmconfig.d7.1.2.0 to /newnet/access/RUN/config/PMGR directory as apmconfig. $ cd /newnet/access/RUN/config/PMGR $mv apmconfig apmconfig.{mmddyyy} $ cp -p $PPHOME/allhome/ss7admn/config/apmconfig.d7.1.2.0 /newnet/access/RUN/config/PMGR/apmconfig

3.7.6 Monitoring D7 Process States A monitoring tool is provided with Distributed7 that can be used to monitor the status of the Distributed7 stack as it is started. This tool is further described in the SS8 Distributed7 User Manual.


40

Usage (Korn shell): su - ss7admin exec ksh –o vi export DISPLAY=IPaddress:0.0 AccessMonitor <signalingpt>

Example: (of monitoring signaling point 0 from IP address 1.2.3.4): su - ss7admin ksh export DISPLAY=192.168.3.4:0.0 AccessMonitor 0

3.8 Truncate PEG_COUNTER and DAILY_REVENUE These two tables can become extremely large, but will not be changed during the PrePay upgrade. To reduce upgrade time, the data within these two tables may be removed. The most efficient approach is to use the TRUNCATE statement. Following this, their respective tablespaces should be coalesced to reduce fragmentation of extents.

su – ppadm sqlplus ppadm/{ppadm_password} truncate table peg_counter; truncate table daily_revenue; alter tablespace ________ coalesce; alter tablespace ________ coalesce; quit

3.9 Upgrade to Oracle 9.2.0.6 See Appendix F, for instructions for upgrading Oracle


41

3.10 Start the Upgrade Using the ppupgrade Script

1. Start a script to record the session. Consider appending a date or date/time stamp on the script log name (yymmddhhmm). script ~/ppupgrade.log.yymmddhhmm

2. Running the script ppupgrade.ksh brings up the PrePay Upgrade menu. Login as “ppadm” user and execute the following commands in the Korn shell.

3. If you are upgrading from a PrePay 9.2.2 release, type the following: cd /<temparea>/work ./ppupgrade.ksh 922

4. If you are upgrading from a PrePay 10.0. release, type the following: cd /<temparea>/work ./ppupgrade.ksh 100

5. Five options will be displayed on the screen. Choose the appropriate option and you will be prompted for further actions when input is needed. The PrePay Upgrade menu will be displayed as follows (with only one of the title lines displayed):

**************************************************************

Prepay Upgrade from 9.2.2 to 10.0.1 OR

Prepay Upgrade from 10.0 to 10.0.1 ************************************************************** 1. Backup application directories & files of current version 2. Upgrade Prepay to 10.0.1 3. Upgrade Database to 10.0.1 4. Rollback Prepay to previous version 5. Quit

Please enter your option: **************************************************************

The PrePay Upgrade options are explained in greater detail in subsequent sections of this guide.


42

WARNING: DO NOT run Option 4 unless you have run Options 2 and 3. Otherwise, you will have fatal failures when you run the Options 2 and 3.

3.11 Backing Up the PrePay Application Directories

1. NOTE: If you wish to reduce backup time and space requirements, and IF you have no need for the old log files, you should flush the /prepay/logs directory before this step. Do so with the recursive option (“rm –rf *”) to ensure cleanest removal.

2. Select Option 1 from the PrePay Upgrade menu to run the pre-upgrade procedure and back up the current PrePay version. Running the pre-upgrade procedure stops the PrePay processes and performs several preparation steps.

3. Execute Option 1 in the PrePay Upgrade menu. You will be prompted with the following message. Note that the default answer for this question may vary depending on system configuration. Do you want to stop the application now? [default=Y ]

4. Type 'y' followed by the Enter key.

5. Check the log file: /<temparea>/work/<version>/logs/backup_app.YYYYMMDD

for any error messages where YYYYMMDD is the system date.

6. After the pre-upgrade procedures are completed in Option 1, the script starts to back up the application. If the Pre-upgrade procedures fail, the application will not be backed up. The backup of the previous PrePay version will be stored in /<temparea>/work/<version>.

7. Depending upon the size of the $PPHOME file system, this process can take up to 20 minutes for slower server platforms. Review the log file for any errors or warnings that may have occurred by executing the following command. more /<temparea>/work/<version>/logs/backup_app.YYYYMMDD

You may also examine the contents of this file with the vi editor looking for the following keywords (capital sensitive):

Error


43

ERROR Unable Warning cannot create

8. The following files and directories are backed up under /prepay ($PPHOME):

bin data etc inqload ppadm aeenv libs

9. These directories should exist on customer systems. If they do not exist, the following error message will display:

‘tar command failed’

The backup will still be successful and contain the other existing directories.

10. Review the log file for any warnings.

3.12 Upgrading Configuration Files Option 2 automatically installs a pre-defined, standard set of XML configuration files. These are NOT updated to contain the equivalent values from the prior configuration files (.cfg in 9.2.2 and other xml files in 10.0). The old configuration files should be saved by renaming each of them with a “.save” (or similar) extension (e.g. “mv prepay.cfg prepay.cfg.save”) for reference. Consider the following minimum set of configuration files for “saving.”

prepay.cfg prepay.default serviceDirectory

You may also look for any files with “sample” as part of the file name in the /prepay/etc directory. If the non-“.sample” version of any of those files are used in your configuration, consider saving a copy of those, also.


44

3.13 Update the serviceDirectory file The /prepay/etc/serviceDirectory file will remain in the PrePay 10.0.1 release. Manually make any desired changes to this file after careful review.

3.14 Apply the Application Upgrade Package Since most of the binaries and libraries in /prepay/inqload, /prepay/lib and /prepay/bin directories are obsolete, all of the files under these directories must be removed from $PPHOME during the PrePay upgrade to 10.0.1. Choosing Option 2 from the PrePay Upgrade menu will purge the binaries and libraries from the following directories:

$PPHOME/bin $PPHOME/libs $PPHOME/inqload

1. To start the upgrade script, type the following command, replacing the string ‘<fromversion>’ with either ‘922’ or ‘100’, depending on whether you are upgrading from the PrePay 9.2.2 or 10.0 release. cd /<temparea>/work ./ppupgrade.ksh <fromversion>

2. Execute Option 2 in the PrePay Upgrade menu, which will upgrade PrePay to 10.0.1. Check the file, /<temparea>/work/<version>/logs/upgrade_prepay.YYYYMMDD

for any error messages.


Error ERROR Unable Warning cannot create

3. The default Upgrade tar.gz file will be displayed on the screen. If you want to change the default tar.gz file, press “n” at the prompt. Or, if you want to use the existing tar file, press “y” at the prompt. This process takes approximately 4


45

minutes to complete. Review the log file for any errors or warnings that may occur. more /<temparea>/work/<version>/logs/

upgrade_prepay.YYYYMMDD

3.15 Execute setupMultAccessRaters.ksh In PrePay 9.2.2 the desired number of access rater processes was specified in the ACCESS-RATER section of the prepay.cfg configuration file with the following variable:

Access-Rater Number of instances 4

In PrePay 10.0, the script setupMultAccessRaters.ksh should be executed to setup the ACCESS_RATER_STATE table correctly for multiple access rater processes.

The new form of usage is shown below:

setupMultAccessRaters.ksh count

where count is the number of access rater processes that should be executed.

For example, setupMultAccessRaters.ksh 4

will result in 4 access rater processes being executed the next time the access_rater is launched either directly or from cron.

It is recommended that a minimum of 4 access rater processes be configured.

You can verify the distribution of subscribers across the total of instances declared by querying the ACCESS_RATER_STATE table.

The below example was run on a system with 667 subscribers with a command line argument of 4 supplied to setupMultAccessRaters.ksh: SQL> select * from access_rater_state; INSTANCE START_SEQUENCE END_SEQUENCE RESTART_D RESTART_SEQUENCE ---------- -------------- ------------ --------- ---------------- 0 1 166 26-OCT-04 1 1 167 332 26-OCT-04 167 2 333 498 26-OCT-04 333


46

3 499 999999999 26-OCT-04 499

The last instance defines that all subscribers with a sequence number > 499 will be handled by the fourth instance.

3.16 Reconfigure Database Rollback Segments The schema upgrade and data conversion steps require a tremendous amount of freespace within the rollback tablespace. The amount of rollback generated during each step of the upgrade process varies by size of table and task. To avoid unnecessary problems during the upgrade, the rollback tablespace will be modified to only one large rollback segment on-line with unlimited extents. Current rollback segments will be dropped to maximize free space within the tablespace.

After the upgrade and conversion has completed, the original rollback configuration will be restored.

3.16.1 Save Current Rollback Configuration Generate a script to restore the client’s current settings. The SQL script produced from the commands below will be run after the database upgrade and data conversion has been completed.

su – ppadm cd /<temparea>/work create_reset_rbs_script.ksh {system password} vi reset_rbs_config.sql (remove non-SQL statements if any) :wq!

3.16.2 Convert to One Large Rollback Segment Generate a script to drop non-SYSTEM rollback segments and create a single large rollback segment. The SQL script produced from the commands below should be run before continuing on to the PrePay 9.x database conversion.

su – ppadm


47

cd /<temparea>/work create_upgrade_rbs_script.ksh {system password}

Modify the generated script for the following items:

• Remove non-SQL statements if any.

• Set initial and next extent so that a multiple of this value fits into the smallest datafile used for the rollback tablespace.

• Set initial and next extent to be of equal values.

• Set minextents to a multiple of the initial extent and large enough to use as much of the rollback tablespace as possible.

For example, if the RBS tablespace uses 10 datafiles and the smallest is 2000MB then a workable CREATE ROLLBACK SEGMENT statement would appear as:

create rollback segment HUGE tablespace RBS storage

(initial 900m next 900m minextents 18 maxextents unlimited );

Make the changes: vi upgrade_rbs_config.sql (make changes noted above) :wq!

Run the modified script to create one large rollback segment. sqlplus system/{system password} < upgrade_rbs_config.sql

> upgrade_rbs_config.lst

3.17 Upgrade the Database Schema to PrePay 10.0.1 The Oracle database schema is upgraded from the previous version to 9.2 by executing Option 3 in the PrePay Upgrade menu.

1. To start the upgrade script, type the following commands, replacing the string ‘<fromversion>’ with either ‘922’ or ‘100’, depending on whether you are upgrading from the PrePay 9.2.2 or 10.0 release.


48

cd /<temparea>/work ./ppupgrade.ksh <fromversion>

2. Execute Option 3 in the PrePay Upgrade menu. The post-upgrade procedures are also automatically executed by this option.

3. Review the error log file in: /<temparea>/work/<version>/logs/ convert_schema.YYYYMMDD

for any errors where YYYYMMDD is the system date. Execute the following command to review the log file for any errors or warnings that may have occurred. more /<temparea>/work/<version>/logs/

convert_schema.YYYYMMDD


Error ERROR Unable Warning cannot create

4. To enable the user to choose the appropriate amount of tablespace, the script displays the available tablespaces and their associated free space on the screen..

5. Answer the prompts that follow according to the values in the figures below. The list of tables to be upgraded will differ depending on whether the application is being upgraded from PrePay 9.2.2 or PrePay 10.0 to PrePay 10.0.1.

3.17.1 Known Issues None at time of publication.

***End of database conversion.


49

3.18 Review the Upgrade Log Files Before continuing, review all of the upgraded log files for errors and correct the errors before continuing.

End any session recording scripts. exit . . . exit

3.19 Restore Original Rollback Segment Configuration Using the script reset_rb_segments.sql created before the database upgrade and conversion, reset the rollback segments back to their original settings.

cd /<temparea>/work sqlplus system/{system_password} < reset_rbs_config.sql >

reset_rbs_config.lst

3.20 Install the License File If the license file was updated to include new license items, install the new license file in the directory '$PPHOME/data' at this point. The following example assumes that a new license file was temporarily placed in the ‘/home/ppadm’ directory.

Example: su - ppadm cd /home/ppadm cp -p license.data $PPHOME/data


50

3.21 Restore startup files 1. Manually copy new ss7 startup/shutdown script to /etc/init.d. Verify links in

/etc/rc0.d and /etc/rc2.d point to the new file. If hard links are used instead of symbolic links, remove these and replace with symbolic links to /etc/init.d/ss7.

Peform this task on Simplex and SSP servers only. su – cd /etc/init.d cp /prepay/roottasks/ss7 . chmod 744 ss7 ls –la /etc/rc?.d/*ss7* (if not symbolic links then remove

and recreate).

2. Manually copy new prepay startup/shutdown script to /etc/init.d. Verify links in /etc/rc0.d and /etc/rc2.d point to the new file. If hard links are used instead of symbolic links, remove these and replace with symbolic links to /etc/init.d/prepay.

Peform this task on all servers running PrePay. su – cd /etc/init.d cp /prepay/roottasks/prepay . chmod 744 prepay ls –la /etc/rc?.d/*prepay* (if not symbolic links then

remove and recreate).

3. Manually copy new oracle startup/shutdown script to /etc/init.d. Verify links in /etc/rc0.d and /etc/rc2.d point to the new file. If hard links are used instead of symbolic links, remove these and replace with symbolic links to /etc/init.d/oracle. su – cd /etc/init.d cp /prepay/roottasks/oracle . chmod 744 oracle ls –la /etc/rc?.d/*oracle* (if not symbolic links, then remove and recreate)


51

3.22 Apply Any Required Patches for PrePay 10.0.1 Apply any PrePay 10.0.1 patches according to the instructions in their accompanying README.TXT files.

3.23 Install any Tailored Switch Configuration Files Copy any switch configuration files modified in section Prepare the Switch Configuration Files into the $PPHOME/etc directory at this point. This could include:

su – ppadm switchInterface.cfg profileFile.prf denyAnnouncementTable.cfg is41eeDefault.prf winDefault.prf capDefault.prf isupDefault.prf pplError.english is41pDefault.prf

Example: cp -p /<temparea>/work/switchInterface.cfg $PPHOME/etc

3.24 Rerun setupSoftLinks.ksh Symbolic links in /prepay/bin that reference a specific SS7 variant must be recreated. This is accomplished by rerunning the setupSoftLinks.ksh script.

setupSoftLinks.ksh

Errors regarding a symbolic link that cannot be replaced are safe to ignore. Verify symbolic links for SS7 executables point to the desired type of protocol, i.e. ANSI or CCITT (for ITU).


52

cd /prepay/bin ls –l |grep ^l lrwxrwxrwx 1 ppadm prepay 23 Oct 1 10:04 ainIccIntf ->

/prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 23 Oct 1 10:04 camelIntf ->

/prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 21 Oct 1 10:04 cfgLaunch ->

/prepay/bin/scilaunch lrwxrwxrwx 1 ppadm prepay 21 Oct 1 10:04 ctp1Depositor ->

/prepay/bin/depositor lrwxrwxrwx 1 ppadm prepay 23 Oct 1 10:04 ctp1Intf ->

/prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 26 Oct 1 10:04 ctp1PostCallWriter

-> /prepay/bin/postCallWriter lrwxrwxrwx 1 ppadm prepay 21 Oct 1 10:04 ctp1PostRater ->

/prepay/bin/postRater lrwxrwxrwx 1 ppadm prepay 20 Oct 1 10:04 ctp1Rater ->

/prepay/bin/gceRater lrwxrwxrwx 1 ppadm prepay 21 Oct 1 10:04 ctp3Depositor ->

/prepay/bin/depositor lrwxrwxrwx 1 ppadm prepay 23 Oct 1 10:04 ctp3Intf ->

/prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 26 Oct 1 10:04 ctp3PostCallWriter

-> /prepay/bin/postCallWriter lrwxrwxrwx 1 ppadm prepay 21 Oct 1 10:04 ctp3PostRater ->

/prepay/bin/postRater lrwxrwxrwx 1 ppadm prepay 20 Oct 1 10:04 ctp3Rater ->

/prepay/bin/gceRater lrwxrwxrwx 1 ppadm prepay 23 Oct 1 10:04 dataExport ->

/prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 21 Oct 1 10:04 gciDepositor ->

/prepay/bin/depositor lrwxrwxrwx 1 ppadm prepay 23 Oct 1 10:04 gciIntf ->

/prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 26 Oct 1 10:04 gciPostCallWriter -

> /prepay/bin/postCallWriter lrwxrwxrwx 1 ppadm prepay 21 Oct 1 10:04 gciPostRater ->

/prepay/bin/postRater lrwxrwxrwx 1 ppadm prepay 21 Oct 1 10:04 gcpDepositor ->

/prepay/bin/depositor lrwxrwxrwx 1 ppadm prepay 23 Oct 1 10:04 gcpIntf ->

/prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 26 Oct 1 10:04 gcpPostCallWriter -

> /prepay/bin/postCallWriter lrwxrwxrwx 1 ppadm prepay 21 Oct 1 10:04 gcpPostRater ->

/prepay/bin/postRater lrwxrwxrwx 1 ppadm prepay 20 Oct 1 10:04 gcpRater ->

/prepay/bin/gceRater lrwxrwxrwx 1 ppadm prepay 23 Oct 1 10:04 inNwi ->

/prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 23 Oct 1 10:04 inSrv ->

/prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 23 Oct 1 10:04 inapcs1Intf ->

/prepay/bin/apf_process lrwxrwxrwx 1 ppadm prepay 23 Oct 1 10:04 iniIntf ->

/prepay/bin/apf_process


53

lrwxrwxrwx 1 ppadm prepay 23 Oct 1 10:04 ipIntf -> /prepay/bin/apf_process

lrwxrwxrwx 1 ppadm prepay 22 Oct 1 10:04 ivrHandl -> /prepay/bin/ivrHandler

lrwxrwxrwx 1 ppadm prepay 30 Oct 1 10:04 mon_control.pl -> /prepay/monitor/mon_control.pl

lrwxrwxrwx 1 ppadm prepay 21 Oct 1 10:04 neqLaunch -> /prepay/bin/scilaunch

lrwxrwxrwx 1 ppadm prepay 24 Oct 1 10:04 ppXmlServiceDaemon -> /prepay/bin/ppXmlService

lrwxrwxrwx 1 ppadm prepay 23 Oct 1 10:04 ppayProcessCtrl -> /prepay/bin/apf_process

lrwxrwxrwx 1 ppadm prepay 21 Oct 1 10:04 pqiLaunch -> /prepay/bin/scilaunch

lrwxrwxrwx 1 ppadm prepay 24 Oct 1 10:05 ss7Intf -> /prepay/bin/ss7Intf-ANSI

lrwxrwxrwx 1 ppadm prepay 30 Oct 1 10:05 ss7TcapParser -> /prepay/bin/ss7TcapParser-ANSI

lrwxrwxrwx 1 ppadm prepay 24 Oct 1 10:05 wmmMain -> /prepay/bin/wmmMain-ANSI

PREPAY /prepay/bin $

3.25 Verify Non-Standard PPADM or Oracle passwords Several XML files have the PPADM Oracle password stored in them. After a PrePay upgrade, new default files could have overlaid these. Review the contents of these and modify if necessary so that the Oracle password for PPADM is consistent and matches the database.

This is only necessary on Simplex, SCP and SDP servers. grep –i ppadm /prepay/aeenv

The following XML files (/prepay/etc/xml) have the ppadm username and login hardcoded and will require modification if the default login/password are different for the system being upgraded:

access_rater.xml awardsDbConfig.xml email_notify_lowBal_cfg.xml prepay_data_export_main.xml prepay_global_entities.xml purgeCreditCardTables.xml purgeDataTables.xml


54

purgeMNPTables.xml

Use the following to re-validate passwords are consistent and match your needs. cd /prepay/etc/xml grep –i ‘password=’ * | more

3.26 Update SMS Configuration (if used) During testing with Ericsson and Logica SMS Messaging Centers, it was determined that each of these systems required different record configurations.

The files SMPPRec.cfg and SMPPField.cfg have been replaced with messaging center-specific files. The files for the Logica messaging center are named SMPPField_LSMSC.cfg and SMPPRec_LSMSC.cfg. The files for the Ericsson messaging center are named SMPPField_ESMSC.cfg and SMPPRec_ESMSC.cfg. In addition, the following change has been made to the file MCnnn.SMPP.cfg.sample, and the references shown must be modified when configuring the SMS subsystem to refer to the appropriate configuration files.

If the SMS optional feature is enabled and being used for the SMPP protocol, save a copy of the existing MCnnn.SMPP.cfg file and update the end of the file to look similar to the sample section shown below, using either the Ericsson or Logica references.

NOTE: These files were not moved to xml format. cd $PPHOME/etc chmod u+w $PPHOME/etc cp -p MCnnn.SMPP.cfg MCnnn.SMPP.cfg.savebefore10_0_1 chmod u+w MCnnn.SMPP.cfg vi MCnnn.SMPP.cfg <make changes as described, refer to the sample file for

examples.> :wq chmod u-w MCnnn.SMPP.cfg $PPHOME/etc Example of the section at end of the

$PPHOME/etc/MCnnn.SMPP.cfg.sample file: #Uncomment the appropriate SMPPField and SMPPRec cfg files: #ESMSC if using an Ericsson SMSC :: LSMSC if using a Logica

SMSC CFGCommandPath $PPHOME/etc/SMPPCmd.cfg #CFGRecordPath $PPHOME/etc/SMPPRec_ESMSC.cfg


55

#CFGRecordPath $PPHOME/etc/SMPPRec_LSMSC.cfg CFGRecordDetailsPath $PPHOME/etc/SMPPRecDetails.cfg #CFGFieldPath $PPHOME/etc/SMPPField_ESMSC.cfg #CFGFieldPath $PPHOME/etc/SMPPField_LSMSC.cfg OtherFeaturesList

3.27 Install the PrePay Client Application Install a small number of workstations (1 to 3) with the 10.0.1 client. All clients must be upgraded before accessing the 10.0.1 server. Full rollout of the client should not be performed until the PPAS is upgraded and functional. Start the client subsystem.

start_ppay API start_ppay CLIENT

3.28 Configure Emergency Number Table (Lucent Only) If a Lucent switch is involved, copy the emergencyNumberTable.cfg file configured earlier into $PPHOME/etc.

cp /<temparea>/work/etc/emergencyNumberTable.cfg

$PPHOME/etc

This change is only required for Lucent switches. The use of a new configuration file has been introduced. This configuration file '$PPHOME/etc/emergencyNumberTable.cfg' is a text file.

IMPORTANT: This file should be created and protected regardless of whether information is populated in it. Read the following section carefully before creating this file.

The file can be created and edited to contain one or more dialed digit strings that correspond to emergency numbers. Only one emergency number may be entered on a line. Lines are terminated with carriage returns, as in any normal UNIX text file. Any information appearing on a line after the sharp symbol '#' is ignored as a comment. Blank lines are also ignored. The star '*' and sharp '#' symbols may be included in an emergency number as part of the dialed digits. No wildcarding support is provided.


56

The pre-rater looks for the emergency file at startup time, or when requested to re-load information using the 'daemonControl' tool. The file location is determined by a new entry 'preRater.emergencyNumberTbl', in the $PPHOME/etc/prepay.default file.

If the prepay.default entry does not exist, or the referenced file does not exist, an informational message is written to the preRater.log file by the pre-rater process and is no change to pre-rater functionality.

If the file is configured and does exist, the pre-rater will compare the dialed digits of mobile originating calls with the list of emergency numbers that have been configured. If there is a match, the call is allowed as a free call for the maximum allowed call duration. Call charge details are recorded as they are in any free call.

This dialed digit comparison for emergency numbers is performed very early in the pre-rating process, in order to turn around potential emergency calls as quickly as possible. No pre-call or mid-call announcements are played during the call.

Note: The maximum allowed call duration is configured in the file $PPHOME/etc/xml/prepay_voice_rating_entities.xml file as the parameter 'preRater.maxCallingTime'. Its default value is 28800 seconds or 8 hours. If any call duration exceeds this value, regardless of how it is charged, the call is torn down.

Note: This feature should not be used as a replacement for the 'Special Number' feature for dialed digits. The intent of the feature is as stated, where certain dialed numbers should be accepted for immediate routing, such as emergency numbers. If the same number is listed both in the emergency number list, and the special number table, emergency number handling will take priority.

IMPORTANT: This file should be created and protected regardless of whether information is populated in it.

3.28.1 Potential Impacts There are two main areas of concern related to this feature: Security and Availability.

• Security: There is a potential risk of internal fraud where unauthorized numbers could be added to the emergency number configuration file.

Security recommendation: Create the emergency number configuration file regardless of whether or not the feature is being used. The file may be secured for read-only permission and owned by the super-user to minimize potential unauthorized changes. Regular review of file contents is also recommended.


57

• Availability: When certain rating subsystem components, specifically the switch interface, Timing Mediation Server, and pre-rater processes are down, emergency calls will be denied.

Availability comments: This feature is a temporary work-around fix to expedite the ability to provide this functionality.

Lightbridge cannot be held liable for the loss of emergency services during a PrePay outage on any system where this feature is used.

3.29 Application Startup Before starting up the PrePay application, logout and login so that correct environment variables are set. Start the application and verify the process status.

su - ppadm start_ppay

3.30 status_ppay Application Testing Perform basic testing to verify that the upgrade has been successful and that basic functions can be performed.

*** End of DOWNTIME ***


58

Notes for 922 users on major changes introduced with PrePay 10.0

4.1 New startup, shutdown, status, list, and restart scripts The Process Startup/Shutdown tool is intended to provide more centralized control over the configuration and control of application startup and shutdown. Normally applications consist of many processes and components that are controlled using numerous scripts, commands and configuration files. The ability to tailor applications for various environments is not encouraged by such an arrangement. The intention of this tool is to provide better control over applications, as well as, enhance the ability to customize applications at the process control level.

The tool is implemented using the apf_process executable. This executable is similar to ctm_allegro in that its behavior is determined at start time by dynamically loading classes specified in an XML configuration file.

Refer to the “Lightbridge Startup Shutdown Tool Operations Manual.doc” document for full details on this tool.


59

The start_ppay.xml and start_ppay_batch.xml files define the processes that will start and how there are started, stopped and monitored. You must not modify these files, but If you are interested, start with /prepay/etc/xml/start_ppay.xml. Just like in prepay_global_entities, this file includes all the other subsystem files it needs.

Start_ppay.xml defines the processes that make up the real-time PrePay system.

Start_ppay_batch.xml defines the processes that are run in batch, usually out of the crontab.

4.2 Obsolete configuration files (prepay.cfg, prepay.default, etc.) The 9.2.2 prepay.default and prepay.cfg files are now obsolete. All new 10.0+ configuration files are in /prepay/etc/xml.

Out of the box, start_ppay will start a basic voice rating system.

In order to enable additional subsystems, you will have to modify /prepay/etc/xml/prepay_process_control_entities.xml.

The only files you should ever modify are /prepay/etc/xml/prepay_*_entities.xml. All relevant values from the old files have found a home in one of these files.

Another example is that all values from the SYSTEM section in prepay.cfg can now be found in /prepay/etc/xml/prepay_system_entities.xml.

Do NOT modify /prepay/etc/xml/prepay_*_processes.xml. Treat these as code produced by engineering.

4.3 New configuration files introduced in $PPHOME/etc This section describes new configuration files that appear in the $PPHOME/etc configuration directory with the upgrade to PrePay release 10.0.

The two configuration files below are specific for a client installation involving the SPATCH provisioning interface. Please refer to that specific documentation for information on these three configuration files. No action is required for a normal/standard PrePay installation or upgrade.


60

gsmHlr.cfg tdmaHlr.cfg

The two configuration files below are specific for a INAP/CS1R switch interface. Refer to the specific section on configuring a CS1R interface if that applies to the environment being upgraded.

inapCs1RDefault.prf.sample inapCs1RInterface.cfg.sample

4.4 Existing ini, prf, cfg, and dat configuration/data files Existing configuration files with suffixes of ini, prf, cfg and dat are still valid and require no changes after upgrading to PrePay 10.0.1

Note that as discussed previously the files prepay.cfg and prepay.default are now obsolete with the upgrade to release 10.0.1.

4.5 Modifications to prepay_profile If specific client customizations were made to the 9.2.2 prepay_profile configuration file in $PPHOME/etc, you should add those customizations to the new 10.0.1 version of prepay_profile.

Do NOT carry forward any references to the old prepay configuration files (prepay.cfg, prepay.default).

Do NOT carry forward the following variable as it is now in the XML configuration file prepay_ivr_entities.xml.

MSISDN_COUNTRY_CODE=`getcfg "IVR" "MSISDN Country Code"` export MSISDN_COUNTRY_CODE


61

4.6 Configuration of XML file prepay_process_control_entities.xml This XML configuration file defines and controls which subsystems are to be managed by the startup and shutdown tool. This XML file also specifies the process counts for the key rating configuration processes.

Some of these entity variables have corresponding features in the PrePay license that must also be enabled to be totally functional in the PrePay system.

Review entities where there is a TRUE/FALSE choice in relation to features to be enabled for the specific client environment requirements. If the process group or feature is specified as FALSE, the processes will not be started or stopped by the start and stop utility. If specified as TRUE, then the processes will be started and/or the feature will be enabled/available.

The following are the entities and their default values. nonFtWatchDog.enabled must be TRUE for NON FT configurations nonFtWatchDog.enabled must be FALSE for FT configurations <!ENTITY nonFtWatchDog.enabled "TRUE"> ft.enabled must be TRUE for FT configurations. ft.enabled must be FALSE for NON FT configurations <!ENTITY ft.enabled "FALSE"> <!ENTITY earlyAlert.enabled "FALSE"> Controls the enabling of the Early Alert Monitor

mon_control.pl process. <!ENTITY voice_rating.enabled "TRUE"> Controls the enabling of the VOICE PrePay subsystem

processes (e.g. TMDS, preRater, postRater, postCallWriter, depositor, etc.)

<!ENTITY d7.enabled "TRUE"> Controls the enabling of the D7 PrePay invocation of

apm_start. <!ENTITY data_rating.enabled "FALSE"> Controls the enabling of the DATA PrePay subsystem

processes (e.g. GCI, CTP, GCP, etc.)


62

<!ENTITY gci.enabled "FALSE"> Controls the enabling of the GCI data processes (e.g.

gciIntf, gceRater, gciPostRater, gciPostCallWriter, gciDepositor)

<!ENTITY gcp.enabled "FALSE"> Controls the enabling of the GCP data processes (e.g. gcpIntf,

gcpRater, gcpPostRater, gcpPostCallWriter, gcpDepositor) <!ENTITY ctp1.enabled "FALSE"> Controls the enabling of the CCI Version 1 data processes (e.g.

ctp1Intf, ctp1Rater, ctp1PostRater, ctp1PostCallWriter, ctp1Depositor)

<!ENTITY ctp3.enabled "FALSE"> Controls the enabling of the CCI Version 3 data processes (e.g.

ctp3Intf, ctp3Rater, ctp3PostRater, ctp3PostCallWriter, ctp3Depositor)

<!ENTITY camelIntf.enabled "FALSE"> Controls the enabling of the camelIntf switch process. <!ENTITY ainIccIntf.enabled "FALSE"> Controls the enabling of the ainicc process group in

prepay_voice_rating_processes.xml (process ainIccIntf) <!ENTITY inapcs1Intf.enabled "FALSE"> Controls the enabling of the inapcs1 process group in

prepay_voice_rating_processes.xml (process inapcs1Intf) <!ENTITY ivr.enabled "TRUE"> Controls the enabling of the ivrHandl process group in

prepay_ivr_processes.xml (process ivrHandl and ivrRouter) <!ENTITY ivrRouter.enabled "FALSE"> Controls the enabling of the ivrRouter process in

prepay_ivr_processes.xml (ivr.enabled must be true) also. <!ENTITY ipIntf.enabled "FALSE"> Controls the enabling of the ipintf process group in

prepay_ip_processes.xml (process ipIntf). <!ENTITY iniIntf.enabled "FALSE">


63

Controls the enabling of the “in” process group in prepay_in_processes.xml (processes in inNwi, inIntf, inSrv)

<!ENTITY inSrv.enabled "TRUE"> Controls the enabling of the inSrv process in

prepay_in_processes.xml (part of “in” process group controlled by iniIntf.enabled)

<!ENTITY inNwi.enabled "FALSE"> Controls the enabling of the inNwi process in

prepay_in_processes.xml (part of “in” process group controlled by iniIntf.enabled)

<!ENTITY provision.enabled "FALSE"> Controls the enabling of the provision process group in

prepay_provision_processes.xml (processes cfgLaunch, pqiLaunch, neqLaunch, etc.)

<!ENTITY spatch.enabled "FALSE"> Controls the enabling of the spatch process group in

prepay_data_processes.xml (process SpatchConv, etc.) <!ENTITY alcatelMMS.enabled "FALSE"> Controls the enabling of the Alcatel MMS process group in

alcatel_mms.xml (batch process alcatelMMS) <!ENTITY alarms.enabled "TRUE"> Controls the enabling of the alarm process group in

prepay_alarm_processes.xml (processes almDaemon, almUserAlarmServer, almFileWriter)

<!ENTITY monitors.enabled "TRUE"> Controls the enabling of the monitor process group in

prepay_monitor_processes.xml (processes crsm, ersm, guism, ivrsm, ipmsm, snmpMonitor)

The ss7Intf.enabled and ss7TcapParser.enabled parameters must

both be TRUE <!ENTITY ss7Intf.enabled "TRUE"> <!ENTITY ss7TcapParser.enabled "TRUE"> Controls the enabling of the ss7tcap process group in

prepay_voice_rating_processes.xml (part of switch process group which is part of voice process group, handles processes ss7Intf and ss7TcapParser)


64

<!ENTITY wmm.enabled "FALSE"> Controls the enabling of the isup process group in

prepay_voice_rating_processes.xml (process wmmMain) <!ENTITY awdDaemon.enabled "FALSE"> Controls the enabling of the awdDaemon process in the

voice process group in prepay_voice_rating_processes.xml <!ENTITY paymentAwards.enabled "FALSE"> Controls the enabling of the PaymentAwardsMonitor process

in the api process group in prepay_api_processes.xml <!ENTITY autoPayment.enabled "FALSE"> Controls the enabling of the AutoPaymentMonitor process in the

api process group in prepay_api_processes.xml <!ENTITY emailNotify.enabled "FALSE"> Controls the enabling of the EmailNotifyMonitor process in the

api process group in prepay_api_processes.xml <!ENTITY sms.enabled "FALSE"> Controls the enabling of the sms process group in

prepay_sms_processes.xml (process smsHandler) <!ENTITY mnp.enabled "FALSE"> Controls whether the partitioned table maintenance occurs

in start_ppay_batch.xml when the batch tasks are executed (applies to mobile number portability feature)

<!ENTITY ccPayment.enabled "FALSE"> Controls whether the partitioned table maintenance occurs

in the start_ppay_batch.xml when the credit card management feature is enabled

<!ENTITY dataExport.enabled "FALSE"> Controls whether the data export batch processes are

enabled in start_ppay_batch.xml when the batch tasks are executed


65

4.7 Configuration of XML file prepay_global_entities.xml The startup/shutdown tool uses Core Timezones. The TIMEZONE variable found in /prepay/etc/prepay_global_entities.xml is set by default to LOCAL_TIMEZONE.

The host entries in the global entity file basically define the "roles" of a particular host. As the tool parses through the xml in *processes*.xml, it determines if the current process is supposed to run on the current host. So

for example, tmds runs only on an SCP, so when the tool encounters the TMDS entry, it determines if the local host is in the list of SCP_HOSTS. If it is, it will start the timingMedServer, if it is not, then the entry is ignored.

Now there is a special entry LOCALHOST="localhost".

For a simplex system (non-da, single host), this value should not require changing.

However, for a DA system, the same configuration files will be used on ALL servers. In this case LOCALHOST remains "localhost" and the various host entities (SDP_HOSTS, SCP_HOSTS, SPT_HOSTS) must be modified to contain a list of hostnames.

If the Credit Card Processing feature is being enabled, the payment gateway URL information is specified in this configuration file.




66

<!ENTITY PAYMENT_GATEWAY "SPECIFY_GATEWAY_URL_HERE">

Modify the default ppadm login/password if different from the default. <!ENTITY PPDBUSER "ppadm"> <!ENTITY PPDBPASSWD "ppadm">

All entities files are included in the main entities file: /prepay/etc/xml/prepay_global_entities.xml. Start in this file and search for the words, "INCLUDE_SEARCH". All other entities files will be listed in this file this way.

4.8 Converting from old rating configuration to new XML rating configuration After upgrading to 10.0.1, execute /prepay/bin/showRatingConfig to display the currently configured rating configuration:

hobbes /prepay/etc/xml $ /prepay/bin/showRatingConfig SS7_CAMEL_NUM=2 Entity variable: camelIntf.totalCamelNumber SS7_AIN_ICC_NUM=1 Entity variable: ainIccIntf.totalAinIccNumber SS7_INAPCS1_NUM=1 Entity variable: inapcs1Intf.totalInapCs1Number WMM_MAIN_NUM=1 (always 1) No entity variable available, hardcoded value of 1

required. SS7_TCAP_PARSER_NUM=2 Entity variable: ss7TcapParser.totalTcapNumber SS7_TMDS_NUM=3 Entity variable: numberOfTmdsIntf SS7_PRE_RATER_NUM=2 Entity variable: preRaterNumber SS7_POST_CALL_WRITERS_PER_TMDS=2 Entity variable: postCallWriterNumber SS7_POST_CALL_WRITER_NUM=6 Calculated value: number of TMDS * number of

postCallWriters per TMDS SS7_POST_RATERS_PER_POST_CALL_WRITER=2 Entity variable: postStreamNumber SS7_POST_RATER_NUM=12


67

Calculated value: number of postCallWriters * postRaters per postCallWriter

SS7_DEPOSITOR_NUM=3 Entity variable: depStreamNumber

Use the 9.2.2 rating configuration snapshot you saved before the upgrade to review differences and make process count modifications where appropriate. These process count changes will be made in prepay_process_control_entities.xml.

4.9 Modified Default Entity Variables

4.9.1 Username/Password for ppadm (prepay_global_entities.xml) The 9.2.2 SYSTEM variable

Userid ppadm/ppadm # userid for logging onto Oracle

is now specified as entity variables in prepay_global_entities.xml  <!ENTITY PPDBUSER "ppadm"> <!ENTITY PPDBPASSWD "ppadm">

Modify the entity password for the ppadm oracle user as required for the installation.

If the report or shareplex username/passwords need to be changed modify the appropriate entity variables in this XML file also.

4.9.2 System Phone Length (prepay_system_entities.xml) The 9.2.2 SYSTEM variable “System Phone Length” was modified in 10.0 to have a default of 10.

From 9.2.2 prepay.cfg.master System Phone Length 8 # length of free

pool/access numbers


68

New entity variable in prepay_system_entities.xml  <!ENTITY SYSTEM.System_Phone_Length "10">

4.9.3 Launcher The launcher process has been removed in PrePay 10.0+. The functionality is replaced by watchDog (ppayProcessCtrl) process which is part of the ADMIN subsystem.

Configuration of the watchDog process is done in prepay_admin_processes.xml.

By default the D7 processes are not managed by watchDog. If you wanted to specify additional processes NOT to be monitored by watchDog add the process name (as defined by the XML process hierarchy) as an argument to the –ignore parameter,

4.9.4 Specifying Number of Client Funnel Processes (prepay_system_entities.xml) In the 9.2.2 prepay.cfg.master configuration file additional funnel processes were added by specifying additional lines of the following format (and incrementing the Funnel number and Port number) :

# for any subsequent user funnel, increase number as format

listed below Production User Funnel 2 Start Flag Y Production User Funnel 2 Port 3042

To specify additional funnel processes in 10.0.1, modify the prepay_system_entities.xml configuration file and add similarly lines as follows:

Specify the desired total number of funnel processes in prepay_process_control_entities.xml

<!ENTITY client.Number_of_Production_User_Funnel "2">

Then if more than two, add additional declarations in prepay_system_entities.xml

For example, the third funnel process would be defined by adding these lines:


69



<!ENTITY SYSTEM.Production_User_Funnel_3_Start_Flag "true">

<!ENTITY SYSTEM.Production_User_Funnel_3_Port "3044">

4.9.5 Specifying PPAS ID (prepay_system_entities.xml) The 9.2.2 SYSTEM variable PPAS ID is now specified in the prepay_system_entities.xml file. Modify to retain the 9.2.2 value after the 10.0.1 upgrade.

4.9.6 Specifying Minimum Card Number Width (prepay_system_entities.xml) The 9.2.2 SYSTEM variable Minumum Card Number Width is now specified in the prepay_system_entities.xml file. Modify to retain the 9.2.2 value after the 10.0.1 upgrade.

4.9.7 Specifying Phone Card Access Code Width (prepay_system_entities.xml) The 9.2.2 SYSTEM variable Phone Card Access Code Width is now specified in the prepay_system_entities.xml file. Modify to retain the 9.2.2 value after the 10.0.1 upgrade.

4.9.8 Specifying Host Entities (prepay_global_entities.xml, prepay_host_entities.xml) In the 9.2.2 prepay.cfg.master configuration file the HOSTS section declared the TCP server hosts.

# Section containing all TCP server hosts - the clients

will use these when # connecting to the servers. The <host name> values may be

changed # according to your specific site configuration

requirements.


70

# # Format = <server name> <host name> [HOSTS] Provision localhost # host for

the Provision server IVR localhost # host for

the IVR server process IVR Router localhost # host for

IVR Router server process ALARM User Server localhost # host for

alarm user server END

In PrePay 10.0.1 these entities are defined in the XML configuration file prepay_global_entities.xml but referenced in prepay_host_entities.xml.

prepay_global_entities.xml: <!ENTITY PROV_HOSTS "&SDP_HOSTS;"> <!ENTITY IVR_HOSTS "&SDP_HOSTS;"> <!ENTITY IVR_ROUTER_HOSTS "&SDP_HOSTS;"> <!ENTITY ALARM_HOSTS "&SDP_HOSTS;">

prepay_host_entities.xml:  <!ENTITY HOSTS.Provision "&PROV_HOSTS;">  <!ENTITY HOSTS.IVR "&IVR_HOSTS;">  <!ENTITY HOSTS.IVR_Router

"&IVR_ROUTER_HOSTS;">  <!ENTITY HOSTS.ALARM_User_Server "&ALARM_HOSTS;">

Modify as appropriate for the specific installation environment.


71

4.9.9 Specifying Service Entities (prepay_services_entities.xml) The 9.2.2 veriables defined in the prepay.cfg.master SERVICES section are now defined in the prepay_services_entities.xml configuration file.

4.9.10 Obsoleted Priority Variables In 9.2.2 there were several of these variables throughout the prepay.cfg.master that have been obsoleted in 10.0+ releases. Priority Class TS # use time-share

scheduling Priority Init -5 # initial priority Priority Limit 0 # highest possible

priority

4.9.11 CC Network Variables The 9.2.2 CC Network variables declared in the CC section of prepay.cfg.master are now defined in the prepay_voice_rating_entities.xml configuration file.

4.9.12 PreRater Entities (prepay_voice_rating_entities.xml) The 9.2.2 vairables defined iin the PRE-RATER section of prepay.cfg.master are now defined as entities in the prepay_voice_rating_entities.xml configuration file.

This is an important XML configuration file to review and compare against the configured 9.2.2 variable values for the installation.

4.9.13 Configure Dialing Plan Entity Variables The 9.2.2 dialing plan variables defined in the DIALING-PLAN section of the prepay.cfg.master configuration file

[DIALING-PLAN] Customer Name CorsairUSA # Name of the

customer


72

Dialing Plan Id 1 Local Home Location Area Y # Y: use home

location area # N: use serving

location area END

Are now defined in the prepay_voice_rating_entities.xml configuration file. %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% Dialing Plan Configs %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%% -->  <!ENTITY DIALING-PLAN.Customer_Name

"CorsairUSA"> <!ENTITY DIALING-PLAN.Dialing_Plan_Id "1">  <!ENTITY DIALING-PLAN.Local_Home_Location_Area "Y">  <!ENTITY AWARDS-DAEMON.Process "awdDaemon"> <!ENTITY AWARDS-DAEMON.Error_Log_File "awdDaemon.log">  <!ENTITY AWARDS-DAEMON.Recharge_Collection_Period "5"> <!ENTITY AWARDS-DAEMON.Trace_Level "1">  <!ENTITY AWARDS-DAEMON.License_Check_Interval "5"> %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%%%%%%%%%%% Subscriber Awards Configs %%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

%%%%%%%%%%% --> <!ENTITY SUBSCRIBER-AWARD.Apply_Taxes_to_Award_Discount "N">


100

4.17.12 INAP/CS1R Interface INAP/CS1 is the Intelligent Network (IN) standard used in the ITU IN networks to implement a variety of IN services. Besides standard IN services, implementation of call control using

INAP/CS1 has become an attractive alternative to CAMEL/GSM based call control for vendors who do not want to upgrade their networks to full blown CAMEL functionality.

Lightbridge’s objective of providing an IN-SCP based call control on INAP/CS1 based networks is to meet the needs of such vendors.

In order to use this feature, the PrePay license feature must be enabled, set to True.

License File: /prepay/data/license.data

The current License Configuration: CS1R False

Once the license feature has been enabled, the client can configure a switch of type CS1R.

4.17.13 GUI/Crystal Reports The client will need to install the new 10.0.1 GUI on all PCs currently running the Lightbridge PrePay GUI.

There are several new Crystal Reports in the PrePay 10.0.x release. These reports are installed in the crw folder when the PrePay GUI is installed.

The full list of reports installed are: Pprp0010.rpt – Call Detail Report Pprp0020.rpt – New Mobile Activations Detail Report Pprp0030.rpt – Mobile Deactivations Report Pprp0040.rpt – Customer Transactions Report Pprp0050.rpt – Payments Report Pprp0070.rpt – Phone Card Detail Report (by

Status/Retailer) Pprp0071.rpt – Phone Card Detail Report (by Retailer/by

Status) Pprp0080.rpt – Phone Card Expiration Summary Report Pprp0100.rpt – Weekly Funds Expiration Report


101

Pprp0110.rpt – PrePay Free Pool Assignment Report Pprp0120.rpt – PrePay Free Pool Unassignment Report Pprp0130.rpt – Call Analysis Report - Obsolete Pprp0140.rpt – Roamer Reconciliation Summary Report -

Obsolete Pprp0150.rpt - Ported Number Report (new in 10.0) Pprp0160.rpt - MDN Utilization Report (new in 10.0) Pprp0170.rpt - MIN Utilization Report (new in 10.0) Pprp0180.rpt - Failed Credit Card Transaction Report (new

in 10.0) Pprp0190.rpt - Credit Card Transaction Report (new in 10.0) Pprp0900.rpt - Active Subscriber Revenue Report (new in

10.0)

4.17.14 API XML Username/Passwords In order for the API Self Care XML services to work correctly, a username/password row must be inserted into the API_USER table.

Obtain the client’s username and password and execute an insert statement similar to the following example:

SQL> insert into api_user values

('client_name','client_name',sysdate,sysdate,'SAM');

4.18 Log files in 10.0.x One of the things you will notice in /logs with the 10.0 release is that there are no longer *.out files for each PrePay process.

You will still see a *.log file for each PrePay process.

The alarmText* and errorLog files still exist as in previous PrePay releases.

The log file prepay-web-service.log contains the log messages from Java objects running inside Tomcat and the Prepay servlets. Any Java-based services in Prepay will log here.

Instead of seeing cci* log files you will see ctp1* or ctp3* log files depending on whether CTP1 or CTP3 has been configured.


102

4.19 Installation and configuration of 10.0.1 EAM Refer to the Early Alert Monitor Installation/Configuration Manual for PrePay for complete instructions and details on configuring the monitor utility to work with PrePay release 10.0.1

4.20 Start up PrePay, Oracle, and SS7 As root, bring up the subsystems. Oracle may already be up from a previous step in the 9i upgrade. If so, do not restart it.

For Simplex servers, use the following commands: su – cd /etc/init.d ./ss7 start ps –ef | grep ora | grep –v grep ./oracle start (only if the Oracle instance is currently

down) ./prepay start

In a Distributed Architecture configuration, start the SDP first, then SCP servers and then SPT servers.

SDP su – cd /etc/init.d ps –ef | grep ora | grep –v grep ./oracle start (only if the Oracle instance is

currently down) ./prepay start

SCP su – cd /etc/init.d ./prepay start

SPT su – cd /etc/init.d ./ss7 start ./prepay start


103

Verify no errors appear in the logs before continuing on to apply PrePay patches.


4.21 Back up the New PrePay and Oracle Perform the same backup as before but using different backup media so that the pre-upgrade backups are not overwritten.


104

Configuration for Data Billing using the General Charging Interface

Several TCP/IP message-based interfaces have been included in PrePay 10.0+ for support of data billing with the General Charging Engine (GCE). These include interfaces for different protocols.

GCI – Pre-approval data billing.

CCI – Data billing using the CTP protocol from a Nortel GGSN.

GCP – Post-approval data billing

INI – Intelligent Network data billing

If any of the data billing protocols are being implemented as part of the PrePay 10.0.1 upgrade, the following steps should be performed as part of system setup.

References to network element setup and administration for usage-based billing can be found in the PrePay Online Help.

1. Reserve TCP/IP ports for connections from external subsystems to protocol-specific charging interface processes. Depending upon the protocol being used, review the default port assignments in the sample files for any conflicts that may exist with the /etc/services file. Change port numbers if a conflict does exist. Append the entries to /etc/services.

For GCI, refer to $PPHOME/etc/etc_service_gci.sample.


105

For CCI, refer to $PPHOME/etc/etc_service_cci.sample.

For GCP, refer to $PPHOME/etc/etc_service_gcp.sample.

For INI, refer to $PPHOME/etc/etc_service_ini.sample. su – edit /etc/services $re /prepay/etc/etc_service_XXX.sample wq

2. Create a separate file system called ‘/udr’ for the bytestream files generated by the GCE processes.

Sizing guidelines: bytestream data will require approximately 1.4 GB per million billing events.

3. Modify the following entries in the file $PPHOME/etc/prepay.default:

• Change the file system for byte-stream files from ‘/cdr’ to ‘/udr’. Make this change for all data billing postCallWriter processes. Do NOT change the voice billing process ‘*.postCallStream’ from using the ‘/cdr’ file system. gciPostCallWriter.PostCallBSPath gciPostCallWriter.UsageDetailBSPath cciPostCallWriter.PostCallBSPath cciPostCallWriter.UsageDetailBSPath gcpPostCallWriter.PostCallBSPath gcpPostCallWriter.UsageDetailBSPath iniPostCallWriter.PostCallBSPath iniPostCallWriter.UsageDetailBSPath

• Change the ‘*.totalNwiNumber’ to the desired number of general charging interface processes for each specific protocol. For example, if 3 GCI processes are to be running and listening on the first three GCI ports, set ‘gci.totalNwiNumber’ to 3. Possible entries include: gci.totalNwiNumber cci.totalNwiNumber gcp.totalNwiNumber ini.totalNwiNumber


106

4. Modify the following entries in the file $PPHOME/etc/purgeFileConfig to reference the new ‘/udr’ file system. By default, the location is ‘/cdr’, but should be changed if data billing is implemented.

Entries to update, changing ‘cdr’ to ‘udr’: BYTE_DATA 10 /cdr/*/byte_stream.*/data @YYYYMMDD.*.dat

@YYYYMMDD.*.attr RATED_DATA 10 /cdr/*/rated.*/data @YYYYMMDD.*.dat

@YYYYMMDD.*.attr

5. Review the location of the tables created for data billing (RATE_COMPONENT_USAGE, USAGE_CHARGE, USAGE_DETAIL). During the upgrade, the default tablespace was set as ‘DDATA02’ and ‘IINDEX02’. Consider re-creating these tables in a new tablespace if data billing is implemented. Review the contents of the file $PPHOME/etc/xml/purgeTables.xml. The tablespace references in this file should be updated to match the tablespace being used for these tables.

6. Add a new cron entry for the ppadm user to regularly create new and drop old partitions of these tables. Review the file $PPHOME/etc/xml/timezones.xml and select an appropriate timezone name, for example ‘PacUSA’ to use as a timezone reference in the batch command. Run the command at the UNIX prompt as a preparation step to create initial table partitions before generating billing messages into the GCI/GCE subsystem.

7. This following example cron entry runs this job at 12:30am each night and is set for a system on US Pacific Time. (Insert it as one long single line. This cron entry can also be copied and modified from the file $PPHOME/bin/ppadm.crontab.)

Example (of a cron entry): 30 0 * * * ksh -c '(. $HOME/.profile > /dev/null 2>&1;

$PPHOME/bin/apf_process -name purgeTable -root $PPHOME/etc/xml -file purgeTables.xml -entity TIMEZONE=PacUSA >> $PPLOGS/createDataBillingUsagePartitions.log 2>&1)'

Note: For balance query messages, a User Defined Service with the following service identifier must be configured in the database:

External Node ID ='BALANCEQUERYNODE'


107

Node Service ID ='GCIBALANCEQUERY'

For new plan offerings, if this User Defined service is added at time of plan definition, and is made a required service, then all subscribers activated using that plan will have the service initially.

For existing plan offerings, where this User Defined service is added after plan creation, a determination must be made for each subscriber of whether or not to add the service.

These steps are the same for any new User Defined service; subscribers on existing plans do not automatically acquire the service when the plan is modified.


108

Post-Upgrade Steps

Caution: Continue with this section only if you are NOT rolling back.

6.1 Tailor File and Table Purging Scripts 1. Review the files that configure the purging schedule for files and tables. Modify

these files to reflect any changes that may be required by the customer for data retention. Lightbridge’s recommended retention periods are specified in the released configuration files: $PPHOME/etc/purgeFileConfig $PPHOME/etc/purgeTableConfig $PPHOME/etc/purgeProvConfig

2. Login as ppadm user to make any changes: su – ppadm

6.2 Review other sample files Review and update any other ‘.sample’ files provided in $PPHOME/etc and copy them into place if appropriate.

Example: cp lineRangeTable.dat.sample lineRangeTable.dat


109

Sample files: jmbSrvcMapFile.sample -Used for specific HLR lineRangeTable.dat.sample -Used for payments on

multiple servers (IVR Router) MCnnn.CAPII.cfg.sample -Use for SMS option MCnnn.SMPP.cfg.sample -Use for SMS option emergencyNumberTable.cfg.sample –Use for specific MSC

type

6.3 Restore CRON Entries Review the new PrePay 10.0.1 ppadm.crontab and compare to the previous copy saved during preparation. Add custom entries and modify existing jobs to meet the needs of the client.

A new crontab entry has been added for purging old partitions from the data billing tables. This entry requires a timezone be entered. Read the comments in the ppadm.crontab file and set appropriately.

cd $PPHOME/bin diff /<temparea>/work/ppadm.crontab.pre10_0_1 ppadm.crontab vi ppadm.crontab {make customizations} crontab ppadm.crontab

6.4 Purge Obsolete Configuration Files The following files, if they exist, may be purged from the $PPHOME/etc directory when the upgrade is completed:

cd $PPHOME/etc rm -f WMM.ini rm -f WMM.ini.sample rm -f is41ActionReason.cfg rm -f is41ActionReason.cfg.sample rm -f is41ExtPtCodeMap.cfg rm -f is41ExtPtCodeMap.cfg.sample rm -f isupActionMap.cfg rm -f isupActionMap.cfg.sample rm -f isupActionReason.cfg


110

rm -f isupActionReason.cfg.sample rm -f isupPtCodeMap.cfg rm -f isupPtCodeMap.cfg.sample

6.5 Roll Out the Client Workstation If the verification step is successful and no rollback is required, upgrade the remaining client workstations to the 10.0.1 version.

6.6 Delete Work Area Files When the upgrade is complete and there is no plan to perform a rollback, the upgrade working directory may be removed.

Perform this step on the server where the PrePay service group is ONLINE. su - cd /<temparea> rm -rf work

*** This completes the PrePay 10.0.1 Upgrade. ***


111

Upgrading Veritas Volume Manager and File System to 4.x

(As of verification, there is no procedure yet to upgrade to Veritas 4.x. We only have straight Veritas 4.x installation procedure. So, the procedure below is not valid for this upgrade.)

A.1 Preface All PrePay systems should have Veritas Foundation Suite installed. This consists of Volume Manager (VxVM) and Veritas File System (VxFS). Some clients may also have the Veritas Database Edition for Oracle installed. This product is not covered by these instructions and is the responsibility of the client to coordinate its upgrade with Foundation Suite.

Veritas Cluster Server (VCS) is not covered in this document.

After Foundation Suite has been upgraded to version 4.2, Maintenance Patch ? (MP?) must be installed. This consists of several Solaris patches that are installed individually.

A pre-requisite to MP? is the installation of Sun’s SAN Foundation Kit. This can be installed before upgrading Foundation Suite to 4.x.

[End of DrW changes for Veritas stuff. I don’t know the details enough to continue.]

PrePay systems running on older Sun StorEdge A5x00 disk arrays will need to have firmware reviewed and upgraded prior to installing the SAN Foundation Kit.

Packages and patches to apply include:


112

• Veritas Volume Manager 3.5

• Veritas File System 3.5

• Individual patches for VxVM with MP2 and VxFS with MP2.

A.2 Required Materials Clients may choose to acquire their own Sun and/or Veritas software. Lightbridge provides CDs with these packages. The following materials are needed for installing the above-mentioned software in the system.

• Veritas Volume Manager 3.5 CD

• Veritas File System 3.5 CD

• Veritas VxVM with MP2 and VxFS with MP2

A.3 Upgrade Veritas VxVM and VxFS to 3.5 The instructions below show how to upgrade Veritas using the CD drive. These steps can be replaced by using the staging area created during the preparation phase.

Reboot the system in single-user mode. You must be using the server’s console to continue working on the upgrade after switching to single-user mode.

su – init S

A.4 Save the Veritas Volume information for safekeeping

1. Execute the following commands to protect the Veritas volume information. su – /usr/lib/vxvm/diag.d/vxprivutil dumpconfig

/dev/rdsk/c0t0d0s3 \ /rootdgdb.out


113

If the command errors, try a different disk from the rootdg disk group:

2. Repeat step one above but for each disk group. Specify a different disk that is a member of the desired disk group.

3. Save /rootdgdb.out to a safe place.

4. Use the tar command to save the Veritas license and volume definitions. cd /etc/vx tar cvf vxsave.tar reconfig.d volboot elm

5. Check the tar file contents by using the command: tar tvf vxsave.tar

A.5 Load the Volume Manager (VxVM) 3.5 CD Insert the VxVM CD. Load and mount the CD-ROM by starting the volmgt daemon.

/etc/init.d/volmgt start

6.6.1 Unencapsulate the boot disk and save the VxVM info 1. Run the upgrade_start -check script to find any problems that exist which

could prevent a successful upgrade. This script reports errors if found. Otherwise, it reports success and you can proceed with running the upgrade_start script. /cdrom/cdrom0/volume_manager/scripts/upgrade_start -check

2. Run the upgrade_start script to prepare the previous release of VxVM for its removal using the following command: /cdrom/cdrom0/volume_manager/scripts/upgrade_start

3. When the scripts successfully completes, execute a df –k command. Notice the disk partition names for root, usr (if it is a separate file system), and var. If the upgrade_start script worked correctly, after the reboot, these will change to regular disk partition names.


114

df -k

Example output: Filesystem kbytes used avail capacity Mounted on /dev/vx/dsk/rootvol 1765324 1538533 173832 90% / /dev/vx/dsk/usr 1373432 991949 326546 76% /usr /proc 0 0 0 0% /proc fd 0 0 0 0% /dev/fd mnttab 0 0 0 0%

/etc/mnttab /dev/vx/dsk/var 2055705 354730 1639304 18% /var swap 2435464 0 2435464 0% /var/run #

4. Reboot the system in single-user mode. reboot -- -s

5. Execute a df –k command to verify that Volume Manager does not control the boot disk. # df -k

6. Example output: Filesystem kbytes used avail capacity Mounted on /dev/dsk/c0t0d0s0 1765324 1538529 173836 90% / /dev/dsk/c0t0d0s6 1373432 991949 326546 76% /usr /proc 0 0 0 0% /proc fd 0 0 0 0% /dev/fd mnttab 0 0 0 0%

/etc/mnttab /dev/dsk/c0t0d0s7 2055705 354730 1639304 18% /var swap 409568 0 409568 0% /var/run #

7. Reboot the system again in single-user mode. su – reboot -- -s

Note: You will need to mount /opt manually before you can run pkgrm to remove the VxVM packages if /opt is on its own partition.


115

A.6 Remove the Veritas File System (VxFS) packages Remove the VxFS packages, starting with the optional package. Do not remove the license packages VRTSvlic or VRTSlic if there are other VERITAS products installed.

Note: If the VRTSqio package is installed, remove it too. pkgrm VRTSfsdoc VRTSvxfs

A.7 Remove the VxVM packages 1. Remove the old VxVM packages by entering:

pkgrm VRTSvmsa VRTSvmdoc VRTSvmdev VRTSvmman VRTSvxvm

VRTSlic

2. Reboot the system again to single-user mode. reboot -- -s

A.8 Load the Volume Manager (VxVM) 3.5 CD

1. Insert the VxVM CD. Load and mount the CD-ROM by starting the volmgt daemon. /etc/init.d/volmgt start

The Veritas Licensing package is the same for VxFS, VCS, and VxVM. If it has already been loaded by one of the other packages, then this step can be skipped. Add the VxVM 3.5 licensing package with the following command: pkgadd -d /cdrom/cdrom0/volume_manager/pkgs VRTSvlic


116

Example output: Processing package instance <VRTSvlic> from

</cdrom/storage_solutions_solaris_3.5cd1/volume_manager/pkgs>

VERITAS License Utilities (sparc) 3.00.007d VERITAS Software Corp VERITAS License Utilities 3.00.007d Using </> as the package base directory. ## Processing package information. ## Processing system information. 6 package pathnames are already properly installed. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts that will be executed with super-

user permission during the process of installing this package.

Do you want to continue with the installation of <VRTSvlic>

[y,n,?]y Installing VERITAS License Utilities as <VRTSvlic> ## Installing part 1 of 1. /etc/vx/licenses/db/dbacoralkl.txe /etc/vx/licenses/db/dbeddb2lkl.txe . . . . /sbin/vxlicrep /sbin/vxlictest [ verifying class <none> ] ## Executing postinstall script. Installation of <VRTSvlic> was successful.

2. Add the VxVM 3.5 package with the following command: pkgadd -d /cdrom/cdrom0/volume_manager/pkgs VRTSvxvm


117

Example output: Processing package instance <VRTSvxvm> from

</cdrom/storage_solutions_solaris_3.5cd1/volume_manager/pkgs>

VERITAS Volume Manager, Binaries (sparc) 3.5,REV=06.21.2002.23.14 Copyright 1996-2002 VERITAS Software Corp. All rights reserved. VERITAS, VERITAS SOFTWARE, the VERITAS logo and all other VERITAS

product names and slogans are trademarks or registered trademarks of VERITAS Software Corporation in the USA and/or other countries. Other product names and/or slogans mentioned herein may be trademarks or registered trademarks of their respective companies.

This package, VxVM 3.5, is supported on Solaris 2.6, 7, 8, and 9. You appear to be running Solaris 8. Press ENTER to install VxVM

3.5 for Solaris 8, or enter another Solaris version number if you are certain that you want to install the drivers for a different release of Solaris.

Install for which version of Solaris? [9, 8, 7, 2.6] (default: 8): Installing VxVM for Solaris 8 Using </> as the package base directory. ## Processing package information. ## Processing system information. 21 package pathnames are already properly installed. ## Verifying package dependencies. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs. This package contains scripts that will be executed with super-

user permission during the process of installing this package. Do you want to continue with the installation of <VRTSvxvm>

[y,n,?]y Installing VERITAS Volume Manager, Binaries as <VRTSvxvm> ## Executing preinstall script.


118

## Installing part 1 of 1. /etc/init.d/vras-vradmind.sh /etc/init.d/vxnm-vxnetd... /etc/rcS.d/S86vxvm-reconfig <linked pathname> ## Executing postinstall script. Copy /kernel/drv/vxio.SunOS_5.8 to /kernel/drv/vxio... Copy /kernel/drv/vxspec.SunOS_5.8 to /kernel/drv/vxspec... Copy /kernel/drv/sparcv9/vxio.SunOS_5.8 to

/kernel/drv/sparcv9/vxio... Copy /kernel/drv/sparcv9/vxspec.SunOS_5.8 to

/kernel/drv/sparcv9/vxspec... Copy /sbin/vxconfigd.SunOS_5.8 to /sbin/vxconfigd... Copy /kernel/drv/vxdmp.SunOS_5.8 to /kernel/drv/vxdmp... Copy /kernel/drv/sparcv9/vxdmp.SunOS_5.8 to

/kernel/drv/sparcv9/vxdmp... Adding vxdmp driver for SunOS version 5.8... ## Executing postinstall script. Copy /kernel/drv/vxio.SunOS_5.8 to /kernel/drv/vxio... Copy /kernel/drv/vxspec.SunOS_5.8 to /kernel/drv/vxspec... Copy /kernel/drv/sparcv9/vxio.SunOS_5.8 to

/kernel/drv/sparcv9/vxio... Copy /kernel/drv/sparcv9/vxspec.SunOS_5.8 to

/kernel/drv/sparcv9/vxspec... Copy /sbin/vxconfigd.SunOS_5.8 to /sbin/vxconfigd... Copy /kernel/drv/vxdmp.SunOS_5.8 to /kernel/drv/vxdmp... Copy /kernel/drv/sparcv9/vxdmp.SunOS_5.8 to

/kernel/drv/sparcv9/vxdmp... Adding vxdmp driver for SunOS version 5.8... Adding vxio driver for SunOS version 5.8... Adding vxspec driver for SunOS version 5.8... Adding vxspec lines to /etc/devlink.tab... Adding vxdmp lines to /etc/devlink.tab... Running /usr/sbin/devlinks -t /etc/devlink.tab ... Adding vxio vxspec vxdmp lines to /etc/system... Copy liba5k.so.2 to /etc/vx/slib/liba5k_stub.so.2 . . . Copy libc_psr.so.1 to /etc/vx...


119

Adding vid=SEAGATE to the list of JBODs... Adding vid=SUN pid=SESS01 (Vicom) to the list of JBODs... Allocating port for Volume Replicator... Port 4145 has been allocated for Volume Replicator use To change, see vrport(1M) command Installation of <VRTSvxvm> was successful. If warnings are displayed that include the string '/etc/vx',

ignore them and continue.

3. Add the VxFS packages: pkgadd -d /cdrom/cdrom0/file_system/pkgs VRTSvxfs VRTSfsdoc

Example output: Do you want to continue with installation [y,n,?] n 2 packages were not processed! devclust-1# pkgadd -d /cdrom/cdrom0/file_system/pkgs VRTSvxfs

VRTSfsdoc Processing package instance <VRTSvxfs> from

</cdrom/storage_solutions_solaris_3.5cd1/file_system/pkgs>

VERITAS File System (sparc) 3.5,REV=GA06 Copyright (c) 1991 - 2002 VERITAS SOFTWARE CORP. ALL RIGHTS

RESERVED. THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE, AND/OR ITS SUPPLIERS.

## Executing checkinstall script. Using </> as the package base directory. ## Processing package information. ## Processing system information. 32 package pathnames are already properly installed. ## Verifying package dependencies. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs.


120

The following files are being installed with setuid and/or setgid permissions: /opt/VRTSvxfs/sbin/qioadmin <setuid root> /opt/VRTSvxfs/sbin/qiomkfile <setuid root> /opt/VRTSvxfs/sbin/vxdump <setuid root setgid tty> /opt/VRTSvxfs/sbin/vxquota <setuid root> /opt/VRTSvxfs/sbin/vxrestore <setuid root setgid bin> Do you want to install these as setuid/setgid files [y,n,?,q] y This package contains scripts that will be executed with super-

user permission during the process of installing this package.

Do you want to continue with the installation of <VRTSvxfs>

[y,n,?]y Installing VERITAS File System as <VRTSvxfs> ## Installing part 1 of 1. /dev/fdd <symbolic link> . . . /usr/kernel/drv/sparcv9/qlog [ verifying class <s28b64> ] ## Executing postinstall script. VRTSvxfs: You must reboot the system after pkgadd. Installation of <VRTSvxfs> was successful. Processing package instance <VRTSfsdoc> from

</cdrom/storage_solutions_solaris_3.5cd1/file_system/pkgs>

VERITAS File System Documentation (sparc) 3.5,REV=GA06e Copyright (c) 1991-2002 VERITAS SOFTWARE CORP. ALL RIGHTS

RESERVED. THIS SOFTWARE IS THE PROPERTY OF AND IS LICENSED BY VERITAS SOFTWARE, AND/OR ITS SUPPLIERS.

Using </opt> as the package base directory. ## Processing package information. ## Processing system information. ## Verifying disk space requirements. ## Checking for conflicts with packages already installed. ## Checking for setuid/setgid programs.


121

Installing VERITAS File System Documentation as <VRTSfsdoc> ## Installing part 1 of 1. /opt/VRTSfsdoc/vxfs_ag.pdf /opt/VRTSfsdoc/vxfs_ig.pdf [ verifying class <all> ] Installation of <VRTSfsdoc> was successful. Note: If the pkgadd command returns an error stating patch

108901-03 has not been applied and then exits, the Veritas compressed tar file must be applied.

Copy the VxFS package to a work area: mkdir /tmp/vxfs cd /tmp/vxfs cp –r /cdrom/cdrom0/file_system/pkgs/VRTSvxfs . cd /tmp Download the file vxfs35-sol8-0204-fix.tar.Z from the Lightbridge

CD or ftp://ftp.veritas.com/pub/support/vxfs35-sol8-0204-fix.tar.Z.

Uncompress and un-tar the file using the command: zcat vxfs35-sol8-0204-fix.tar.Z | tar xf - cd vxfs35-sol8-0204-fix ./fix /tmp/vxfs/VRTSvxfs Proceed with the Veritas File System installation: pkgadd –d /tmp/vxfs/VRTSvxfs pkgadd -d /cdrom/cdrom0/file_system/pkgs VRTSfsdoc

4. Complete the upgrade typing the following command: /cdrom/cdrom0/volume_manager/scripts/upgrade_finish

5. Perform reconfiguration reboot: reboot -- -r

6. Execute a df –k command. Notice the disk partition names for root, usr (if it is a separate file system), and var. If the upgrade_finish script worked correctly, then after the reboot, these will change back to the Volume Manager names. df –k

Filesystem kbytes used avail capacity Mounted on


122

/dev/vx/dsk/rootvol 1765324 963113 749252 57% / /dev/vx/dsk/usr 1373432 1008033 310462 77% /usr /proc 0 0 0 0% /proc fd 0 0 0 0% /dev/fd mnttab 0 0 0 0% /etc/mnttab /dev/vx/dsk/var 2055705 724916 1269118 37% /var swap 2478688 0 2478688 0% /var/run

7. During boot, the /etc/init.d/vxvm-startup1 script starts all rootdg volumes listed in /etc/vfstab (which are considered special volumes). This occurs very early in the bootup stage, when only rootdg disk group is imported. If the volume entry in /etc/vfstab does NOT belong to rootdg disk group, then this volume will fail to start and the user is notified of this with the following warning messages: vxvm: Volume <volname> for mountpoint <mnt_point> is not in

rootdg disk group; <Cannot start the volume early>

The message shown above is repeated for every non-rootdg volume in /etc/vfstab. The volumes fail to start because they are not in the rootdg disk group. Later in the boot process, after the non-rootdg disk groups are imported, the non-rootdg volumes are safely started and mounted.

These warning messages occur in VxVM 3.5 only. The warning messages can be safely ignored. After the system completes booting, all volumes are actually started and mounted. (This issue is reported in VERITAS Incident 102047 and will be fixed in VxVM 3.5 Patch 01.)

8. Using the pkgadd command, install the additional packages: VRTSvmdoc,VRTSvmman, VRTSvmpro, VRTSfspro, VRTSob, and VRTSobgui. pkgadd -d /cdrom/cdrom0/volume_manager/pkgs VRTSvmdoc

VRTSvmman VRTSob VRTSobgui VRTSvmpro VRTSfspro

A.9 Individual patches for VxVM with MP2 and VxFS with MP2. Apply Veritas 3.5 MP2 Patch su – cd /<temparea>/cd_sw/solaris_patches/Patches zcat 112392-06.tar.Z | tar xvf -


123

unzip 113206-10.zip unzip 113203-03.zip unzip 113595-04.zip unzip 113596-03.zip unzip 113210-03.zip patchadd 112392-06 patchadd 113206-10 patchadd 113203-03 patchadd 113595-04 patchadd 113596-03 patchadd 113210-03


124

Changes to PrePay XML Configuration Files

The following attributes have changed from PrePay 10.0 to 10.0.1.

File (.xml) Variable Old Value (10.0)

New Value (10.0.1)

in/in_server checkForPoundIndicator

New False if entire dialed digits should be checked for Special Number.

True if only check dialed digits starting with #.

prepay_ivr_entities Verify_User_Name_and_Password

New Y / N = for balance query and charge payment

prepay_ivr_entities Verify_User_Name_and_Password_For_Card_Payment_Updates

New Y = Default = True

prepay_ivr_entities Apply_One_Time_Charge

New Y = Default = True

prepay_data_processes

(various) post stream values for DATA changed to always be 1:1


125


New Value (10.0.1)

prepay_data_rating_entities

prepay_process_control_entities

prepay_in_processes

prepay_ip_processes

prepay_voice_rating_processes

between rater and postCallWriter

gci_rating_invoke_message

MDN Now a required parm.

prepay_data_rating_entities

Rate_Only_Updates_Accum_Usage

New Y = RATE-ONLY updates

N = RATE-ONY does not update

No entry = Assumed Y


inSrv.enabled Cleanup Removed redundant entry

prepay_voice_rating_entities

camelIntf.ivrShortCode

New “1234”


camelIntf.ivrAccessNumber

New “3031234567”

prepay_data_export_main

CreationDate

PaymentRecievedDate

Callstarttimestamp

Modified data format explicitly stated as “DD-MON-YYYY HH24:MM:SS”


126


New Value (10.0.1)

EventstartTimestamp


cap_main

Added support of multiple camelIntf instances and trace levels 0-10.

prepay_provision_entities

(comments) added comments for DEC3.8 option in provisioning ESN


ss7Intf.qualityOfService

New 5


inSrvMsgCtr.enabled

inIntfMsgCtr.enables

gceMC.totalNwiNumber

gceMCRater.totalGceRaterNumber

gceMCDepositor.depStreamNumber

gceMCPostCallWriter.postStreamNumber

gceMCPostRater.depStreamNumber

gceMCPostRater.postStreamNumber

Cleanup unused entries and set gceMC items to “1”


127


New Value (10.0.1)


group SWITCH group moved before TMDS group

access_number_migrator


provisioning flags New Added provisioning flags to enable/disable record insertion


IPM.Device_NortelGSM.KeepAliveTimeout

New (as needed)


128

Changes to PrePay Database Tables

The following tables have changed from PrePay 10.0 to 10.0.1.

(How about changes from 9.2.2 ?)

Table Column Old Value (10.0)

New Value (10.0.1)

customer_inus_amount VIEW

Piu_gl_code New column


129


130

Switch Interface Configuration Files

D.1 switchInterface.cfg.sample ## WARNING ## # This file is a sample file, showing how to configure different

point-codes for # switch interface. # Refer to document, " Pre-pay 10.0 Switch Configuration

Consolidation" for more # detailed information related to the configuration. # Configuration for one point-code (or wild-card entry) should be

defined on # one line. Continuation char backslash "\" should be used to

continue one line. ## Max length of a line is 4096 characters. ## There should be no duplicate entries for any point-code. ## The names of profile files can contain the absolute path - For

example, ## /prepay/etc/myWinDefault.prf


131

## One sample "profile" is defined for reference. see profileFile.prf.sample

# # Examples: # ======== # Default entry - any switch not mentioned shall read from the

default.prf profile *-*-* profile default.prf # Network 1 overrides some values in isupDefault.prf with

isupNetwork1.prf. #1-*-* profile isupDefault.prf profile isupNetwork1.prf # This switch uses the isupDefault profile, overridden with

isupNetwork2.prf, # and specifies a specific switchId in the top level file. #2-2-2 profile isupDefault.prf profile isupNetwork2.prf switchId

25888001 # In this case, all values are specified in the top-level - not

recommended. #2-2-3 switchId 25888002 "isupTrunkBlock 22 0" "32 42 0"

"isupTrunkBlock 1 1" "32 43 0" "isupTrunkBlock 3 2" "24 44 2" switchProtocolType ISUP isupEricssonNativeTriggerSupport YES

#isupDefault profile overridden by isupSingleSwitch profile. #10-20-135 profile isupDefault.prf profile isupSingleSwitch.prf # winDefault.prf defines most of the configuration for this

switch, but it # overrides a couple of them (i.e. switchId and winCCDirTimeOut)

here. #10-20-136 profile winDefault.prf switchId 233345 winCCDirTimeOut

5


132

D.2 capSwitchInterface.cfg.sample #################################################################

############### # # CAMEL CONFIGURATIONS # #################################################################

############### # # The configurations for the PPAS CAMEL Switch Interface

processes are contained # in profile files. There can be as many profile files as

desired. Each profile # should be contained in a separate file (e.g. capDefault.prf). # # Profile configurations can be done on a per MSC level. The

association of a # profile configuration to an MSC can be done on the following

basis. # # 1. Point Code # Point Code contained in the Calling Party address in the

SCCP portion of the # incoming message when the routing mechanism is "ROUTE ON

SSN". # # 2. E.164 address # GT Address Signal contained in the Calling Party address in

the SCCP portion # of the incoming message when the routing mechanism is "ROUTE

ON GT". # # 3. Wild Card # When no specific point code or E.164 GT Address need be

specified and default # configuration may be loaded. The wild card characters that

are supported are * # and .(dot). * matches zero or more characters while .

matches just one character. # # In all these configurations - whether point code or GT address,

the association


133

# is always on an MSC level. # # Examples: # # Point Code Based Configurations # -------------------------------------- # 0-57-1 profile capDefaultMsc1.prf # 0-57-2 profile capDefaultMsc2.prf # -------------------------------------- # # # E.164 (GT Address) based configurations # --------------------------------------- # 16003005001 profile capDefaultMsc3.prf # 16003005002 profile capDefaultMsc4.prf # --------------------------------------- # # # Wild Card configuration # -------------------------------------- # 0-57-* profile capDefault1.prf # *-*-* profile capDefault2.prf # * profile capDefault3.prf # 1600300* profile capDefault4.prf # 1600.005* profile capDefault5.prf # --------------------------------------

D.3 denyAnnouncementTable.cfg.sample # # denyAnnouncementTable.cfg # # Purpose: # Translate denial announcement codes received by TMDS from

preRater to # values in callTreatmentMessage understood by the switch

interfaces. # Further evaluation and protocol specific behavior is driven

by the # individual protocol configuration files: *.prf


134

# # Format : # Denial_reason Announcement_id Announcement_Type # # # Where: # # Denial_reason: (input): The reason for denial assigned by

the preRater. # Announcement_id: (output) The announcement identifier

mapped to a .prf # file specific to the switch interface

handling this # call. # Announcement_type: (output) The announcement type to be

used by the # switch interface handling this call. # # The combination of announcement_id and announcement_type

indicates to # the switch interface which exact announcement to play. # # For example: # # INPUT: DENIAL REASON INSUFFICIENT BALANCE = 1 # OUTPUT: ANNOUNCEMENT ID INSUFFICIENT BALANCE = 3 # OUTPUT: ANNOUNCEMENT TYPE IVR BASED = 65 # switch config file: winDefault.prf.sample # # Will match the following entry in winDefault.prf.sample: # # "winIvrAnnouncementId 3" "IVR_BASED 3334445555" # # See Also: # winDefault.prf.sample # is41eeDefault.prf.sample # isupDefault.prf.sample # is41pDefault.prf.sample # ... # # Possible values for each for these fields are given below: # # Denial_reason: # =============== # DENIAL REASON NONE = 0


135

# DENIAL REASON INSUFFICIENT BALANCE = 1 # subscriber is below minimum

# # balance threshold

# DENIAL REASON INACTIVE = 2 # subscriber is not in active

# # status # DENIAL REASON BELOW BILLABLE = 3 # subscriber

balance is below # # minimum

billing increment # DENIAL REASON BELOW SETUP = 4 # subscriber

balance below # # minimum

required for call # # setup

duration # # # Announcement ID: # =============== # ANNOUNCEMENT ID NONE = 0 # ANNOUNCEMENT ID INSUFFICIENT BALANCE = 3 # ANNOUNCEMENT ID SUBSEQ LOW BALANCE = 10 # ANNOUNCEMENT ID SUBSEQ EXPIRED = 11 # # Announcement Type: # ================== # ANNOUNCEMENT TYPE NONE = 0 # ANNOUNCEMENT TYPE SWITCH BASED = 16 # NOTE: These are

hard coded # ANNOUNCEMENT TYPE IVR BASED = 65 # values.

Do not try # # any other

values # # ======== # 0 0 0 1 3 16 2 11 16 3 3 16 4 0 0


136


137

D.4 profileFile.prf.sample ## WARNING## # There should be only one name-value pair per line ## continuation char backslash "\" should be used to continue one

line ## see document : "Pre-pay 10.0 Switch Configuration

Consolidation" for details# "errorRoutingAction SYSTEM_FAILURE" ROUTE_CALL "errorRoutingAction RESOURCE_SHORTAGE" ROUTE_CALLisupEricssonNativeTriggerSupport YESswitchProtocolType

ISUP"isupErrorRoutingAction RESOURCE\_SHORTAGE" ROUTE_CALL"

"isupTrunkBlock 1 0" "32 1 0" "isupTrunkBlock 23 1" "24 67 9" "isupTrunkBlock 1 1" "24 2 0" "isupTrunkBlock 29 0" "32 35 1" "isupTrunkBlock 229 1" "31 512 1"


138

D.5 is41eeDefault.prf.sample # The Switch (MSC) protocol types supported by the MSC. # Format: switchProtocolType " <protocolType> " # <protocolType> could be any one of the following: # - "IS41EE" # - "IS41EE ISUP" # switchProtocolType "IS41EE" #%%PROMPTUSER%% modify at

installation # IS41EE AnnouncementID # Format: # "is41eeAnnouncementId <announcementID>" "<setupCode>" # # <announcementID> could be any one of the following. # # 1 - Call Duration Info. # 2 - Low Balance Warning # 3 - Insufficient Balance # 4 - Call End Warning (i.e. to indicate call will be

disconnected soon). # 5 - Disconnect Warning (i.e. Call is being be disconnected. # 6 - 1 minute Warning (i.e. Call will be disconnected in 1

minute). # 7 - 2 minute Warning (i.e. Call will be disconnected in 2

minutes). # 8 - 3 minute Warning (i.e. Call will be disconnected in 3

minutes). # 9 - 5 minute Warning (i.e. Call will be disconnected in 5

minutes). # 10 - Subsequent Low Balance # 11 - Subsequent Expired. # 12 - First Expiration Warning (The first time expiration

warning is hit). # # NOTE: # - 1, 2, 3, 10, 11 and 12 are MANDATORY - they must be

present. # # - PREPAY WOULD DECIDE TO ROUTE THE CALL OR DENY THE

CALL.


139

# # <setupCode> :- This parameter is used by the SCP to direct

the call setup treatment to be applied by the MSC. # #This contains the value of the announcement related fields of

the SetupCode parameter sent in the response message to the IS41ee Pre-Call Query.

# # <setup Digits> Could be any one of the following: # # 00 "00" Do Not play announcement; route the call. # 10 "16" Call duration announcement; Play MSC or IVR

announcement; # route the call. # 11 "17" Low balance; Play MSC or IVR announcement and

route the call. # 20 "32" Call duration announcement; Play MSC or IVR

announcement; # terminate the call on MSC announcement completion

or IVR # release. # 21 "33" Low balance; Play MSC or IVR announcement and

terminate the call on MSC announcement completion or IVR release. # 30 "48" Call duration announcement; Play IVR

announcement; # terminate the call on IVR release. # 31 "49" Low balance announcement; Play IVR announcement; # terminate the call on IVR release. # 40 "64" Call duration announcement; Play IVR

announcement; # route the call on IVR release. # 41 "65" Low balance announcement; Play IVR announcement;

route the call on IVR release. # "is41eeAnnouncementId 1" "16" "is41eeAnnouncementId 2" "65" "is41eeAnnouncementId 3" "32" "is41eeAnnouncementId 4" "32" "is41eeAnnouncementId 10" "49" "is41eeAnnouncementId 11" "32" "is41eeAnnouncementId 12" "00" #


140

# Configuration to determine the Routing Action on prepay rating errors.

# Format: # "errorRoutingAction <errorCause>" "<RoutingAction>

[announcement ID]" # # <errorCause> - Could be one of the following: # # 1 = RESOURCE_SHORTAGE : A resource for rating the call is

temporarily unavailable. # # 2 = SYSTEM_FAILURE : A temporary failure has occurred

while the call was being rated. # # 3 = UNKNOWN_SUBSCRIBER : Subscriber is NOT a valid Prepay

subscriber. # # <RoutingAction> - The configured routing action. Could be

one of the following: # # ROUTE_CALL : Route/Terminate the call. # # DENY_CALL : Deny call routing/termination. # # PLAY_ANNC_AND_ROUTE_CALL : Play an announcement and then

Route/Terminate the call. # # PLAY_ANNC_AND_DENY_CALL : Play an announcement and then deny

call Routing/Termination.


141

D.6 CapDefault.prf.sample #

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

# # This file contains a description of the "Switch Interface" # configurable parameters for CAP2. # #

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

# # The Switch (MSC) protocol types supported by the MSC. # Format: switchProtocolType "<protocolType>" # # <protocolType> could be any one of the following: # - "CAP2" # switchProtocolType "CAP2" #%%PROMPTUSER%% modify at

installation # # CAP Announcement ID definitions. CAP announcements are IVR-

based only. # # Formats: # # 1. IVR-Based Announcement # ====================== # # "cap2AnnouncementId <prepayAnncID>" "IVR_BASED

<IVRDigits> <maxTime>" # # 2. No Announcement - No announcement is to be played for

specified Announcement ID, <prepayAnncID> # =============== # # "winAnnouncementId <prepayAnncID>" "NO_ANNOUNCEMENT" # # # <prepayAnncID> Could be one of the following:


142

# # 1 - Call Duration Information # 2 - Low Balance Warning # 3 - Insufficient Balance # 4 - Call End Warning (i.e. to indicate call will be

disconnected soon). # 5 - Disconnect Warning (i.e. Call is being be disconnected. # 6 - 1 minute Warning (i.e. Call will be disconnected in 1

minute) # 7 - 2 minute Warning (i.e. Call will be disconnected in 2

minutes) # 8 - 3 minute Warning (i.e. Call will be disconnected in 3

minutes) # 9 - 5 minute Warning (i.e. Call will be disconnected in 5

minutes) # 10 - Subsequent Low Balance Warning # 11 - Subsequent Expiration Warning # 12 - First Expiration Warning (The first time expiration

warning is hit). # # <IVRDigits> - Identifies the IVR Routing digits. # # <maxTime> - Identifies the maximum time for this announcement # Examples of IVR-Based announcements are: # # "cap2AnnouncementId 1" "IVR_BASED 4445556666 20" # "cap2AnnouncementId 2" "IVR_BASED 5556667777 30" # "cap2AnnouncementId 0" "IVR_BASED 0001112222 10" "cap2AnnouncementId 1" "IVR_BASED 1112223333 11" "cap2AnnouncementId 2" "IVR_BASED 2223334444 60" "cap2AnnouncementId 3" "IVR_BASED 3334445555 13" "cap2AnnouncementId 4" "IVR_BASED 3334445555 14" "cap2AnnouncementId 5" "IVR_BASED 3334445555 15" "cap2AnnouncementId 6" "IVR_BASED 3334445555 16" "cap2AnnouncementId 10" "NO_ANNOUNCEMENT" "cap2AnnouncementId 11" "NO_ANNOUNCEMENT" "cap2AnnouncementId 12" "IVR_BASED 5554445555 19" #This value is checked against the 'RemainingTime' parameter

received in #the MidCallAnnouncement message "cap2MaxCallPeriodDuration" "30"


143

#The cause sent in the 'ReleaseCall' message on Forced Disconnect "cap2ReleaseCause" "47" # # Configuration to determine the Routing Action on prepay rating

errors. # # Format: # "errorRoutingAction <errorCause>" "<RoutingAction>

<prepayAnncID>" # # <errorCause> - Could be one of the following: # # 1 = RESOURCE_SHORTAGE : A resource for rating the call is # temporarily unavailable. # # 2 = SYSTEM_FAILURE : A temporary failure has occurred # while the call was being rated. # # 3 = UNKNOWN_SUBSCRIBER : Subscriber is NOT a valid Prepay # subscriber. # # <RoutingAction> - The configured routing action. Could be

one # of the following: # # ROUTE_CALL : Route/Terminate the call. # # DENY_CALL : Deny call routing/termination. # # PLAY_ANNC_AND_ROUTE_CALL : Play an announcement and then # Route/Terminate the call. # # PLAY_ANNC_AND_DENY_CALL : Play an announcement and then # deny call Routing/Termination. # # NOTE : Default <RoutingAction> is set to "DENY_CALL". # --------------------------------------------- # # If <RoutingAction> is PLAY_ANNC_AND_ROUTE_CALL or

PLAY_ANNC_AND_DENY_CALL, then # <prepayAnncID> specifies the announcement to be played. The

announcement # could be either Switch-based or IVR-based. (See <prepayAnncID>

above ).


144

# # # NOTE:: If <RoutingAction> is either PLAY_ANNC_AND_ROUTE_CALL or

PLAY_ANNC_AND_DENY_CALL and <prepayAnncID> is "NO_ANNOUNCEMENT" then default routing action would be either ROUTE_CALL or DENY_CALL.

# #"errorRoutingAction 1" "PLAY_ANNC_AND_ROUTE_CALL 2" "errorRoutingAction 1" "ROUTE_CALL" "errorRoutingAction 2" "DENY_CALL" "errorRoutingAction 3" "ROUTE_CALL" # Other error routing action examples are given below: #"errorRoutingAction 1" "ROUTE_CALL" #"errorRoutingAction 1" "DENY_CALL" #"errorRoutingAction 1" "PLAY_ANNC_AND_DENY_CALL 2" #"errorRoutingAction 2" "ROUTE_CALL" #"errorRoutingAction 2" "PLAY_ANNC_AND_ROUTE_CALL 1" #"errorRoutingAction 2" "PLAY_ANNC_AND_DENY_CALL 2" #"errorRoutingAction 3" "ROUTE_CALL" #"errorRoutingAction 3" "DENY_CALL" #"errorRoutingAction 3" "PLAY_ANNC_AND_ROUTE_CALL 2" #"errorRoutingAction 3" "PLAY_ANNC_AND_ROUTE_CALL 5"


145

D.7 isupDefault.prf.sample ## WARNING## # There should be only one name-value pair per line# # continuation char backslash "\" should be used to continue one

line# # see document : "Pre-pay 10.0 Switch Configuration

Consolidation" for details# # ISUP AnnouncementID # # Format: # "isupAnnouncementId <announcementID>" "<IVRDigits>" # # <announcementID> could be any one of the following. # # 1 - Call Duration Information # 2 - Low Balance Warning # 3 - Insufficient Balance # 4 - Call End Warning (i.e. to indicate call will be

disconnected soon). # 5 - Disconnect Warning (i.e. Call is being be

disconnected. # 6 - 1 minute Warning (i.e. Call will be disconnected in

1 minute) # 7 - 2 minute Warning (i.e. Call will be disconnected in

2 minutes) # 8 - 3 minute Warning (i.e. Call will be disconnected in


5 minutes) # 10 - Subsequent Low Balance Warning # 11 - Subsequent Expiration Warning # 12 - First Expiration Warning (The first time expiration

warning is hit). # # NOTE: 1, 2, 3, 4, 5, 10, 11 and 12 are MANDATORY - they

must be present. # ==== "isupAnnouncementId 0" "#0399902" "isupAnnouncementId 1" "#0399901"


146

"isupAnnouncementId 2" "#0399901" "isupAnnouncementId 3" "#0399902" "isupAnnouncementId 4" "#0399902" "isupAnnouncementId 5" "#0399902" "isupAnnouncementId 6" "" "isupAnnouncementId 7" "" "isupAnnouncementId 8" "" "isupAnnouncementId 9" "" "isupAnnouncementId 10" "#0399902" "isupAnnouncementId 11" "#0399902" "isupAnnouncementId 12" "#0399902" "isupErrorRoutingAction SYSTEM_FAILURE" "DENY_CALL 55" "isupErrorRoutingAction RESOURCE_SHORTAGE" "ROUTE_CALL" # The Switch (MSC) protocol types supported by the MSC. # Format: switchProtocolType " <protocolType> " # # <protocolType> could be any one of the following: # - "ISUP" # - "ISUP-ROAM" # where ISUP-ROAM is used only for Terminating calls and for

SMSCs switchProtocolType "ISUP" #%%PROMPTUSER%% modify at installation # ID of the switch for this point code. this is 8 digit no.

switchId 24588001 # configuration to indicate whether switch supports both prepay

and # non-prepay subscribers in originating calls. # Format: # isupNonPrepayOrigination "<YES/NO> <REL Cause>" # isupNonPrepayOrigination "YES 20" # configuration to indicate whether switch supports both prepay

and # non-prepay subscribers in Termination calls. # Format: # isupNonPrepayTermination "<YES/NO> <REL Cause>" isupNonPrepayTermination "YES 21" #configuration parameter to indicate whether switch is Ericsson

Native # Trigger capable. # Format: # isupEricssonNativeTriggerSupport <YES/NO>


147

#NOTE: if Switch ProtocolType is ISUP-ROAM, it will have this configuration only

isupEricssonNativeTriggerSupport YES #Configuration parameter specifies whether WMM should release

incoming call # handled by GMSC if isupEricssonNativeTriggerSupported is YES # Format: # isupGatewayReleaseForEricssonNativeTrigger "<YES/NO> <REL

Cause>" isupGatewayReleaseForEricssonNativeTrigger "YES 23" # configuration parameter that indicates what action to be taken

if PPL # server return Error. # Format: # "pplErrorMap <errorIndicator>" "<Error Action> <REL

Cause>" "pplErrorMap PPL_SERVER_DOWN" PPL_ERROR_ACTION_CONTINUE "pplErrorMap PPL_ERROR_RESPONSE" PPL_ERROR_ACTION_CONTINUE # configuration Parameters that define set of trunk groups

from/to which WMM # receives/sends ISUP Messages. These Trunk Groups refers to the

trunk group # configuration of Newnet # Format:

# "isupTrunkBlock <MO Trunk Grp> <MO Base CCT>" "<No of CCTs> <MT Trunk Grp>

# <MT Base CCT>" "isupTrunkBlock 1 0" "32 3 0" "isupTrunkBlock 5 0" "32 7 0" "isupTrunkBlock 9 0" "32 11 0" "isupTrunkBlock 13 0" "32 15 0" "isupTrunkBlock 17 0" "32 19 0" "isupTrunkBlock 21 0" "32 23 0" "isupTrunkBlock 25 0" "32 27 0" "isupTrunkBlock 29 0" "32 31 0" "isupTrunkBlock 33 0" "32 35 0" "isupTrunkBlock 37 0" "32 39 0" "isupTrunkBlock 41 0" "32 43 0" "isupTrunkBlock 45 0" "32 47 0" "isupTrunkBlock 49 0" "32 51 0" "isupTrunkBlock 53 0" "32 55 0" "isupTrunkBlock 57 0" "32 59 0" "isupTrunkBlock 61 0" "32 63 0"


148

# The following 4 parameters must be configured properly for ISUP incoming

# calls to be handled properly. These settings may be switch vendor type

# and/or carrier dependent. # # This is an example of the settings for an Ericsson MSC

configured for # loopbacks # isupTerminationIndicator "HOME 4 PRESENT" # isupTldnTerminationParameterId "4 4" # isupSubscriberTerminationParameterId 235 235 # isupDefaultTldn DEFAULT # # This is an example of the settings for a generic switch with

TLDN present # only for roaming calls # isupTerminationIndicator "ROAM 40 PRESENT" # isupTldnTerminationParameterId "NONE 4" # isupSubscriberTerminationParameterId 4 40 # In the following line, DEFAULT should be substituted with a

value in the TLDN # table, to be used as the TLDN for home incoming calls: # isupDefaultTldn DEFAULT # This is an example of the settings for a generic switch with no

TLDN # passed to PPAS, where all incoming calls are rated as home

calls # isupTerminationIndicator "HOME 4 PRESENT"

# isupTldnTerminationParameterId "NONE NONE" # isupSubscriberTerminationParameterId 4 4 # In the following line, DEFAULT should be substituted with a value in the

# TLDN table, to be used as the TLDN for home and roam incoming calls: # isupDefaultTldn DEFAULT # The field in the IAM message used to differentiate home or roam incoming # calls. # Format: # isupTerminationIndicator "<indication> <iamParamId> <indicatorType> [<indicatorValue>]" # <indication> := HOME | ROAM


149

# <iamParamId> := IAM message parameter number. Valid numbers are

# 4 := CALLED_PARTY_NUM # 10 := CALLING_PARTY_NUM # 40 := ORIG_CALLED_NUM # 235 := CHARGE_NUMBER # <indicatorType> := PRESENT | MISSING # <indicatorValue>:= Optional. String with no white spaces. # Used only when <indicatorType> = PRESENT. isupTerminationIndicator "HOME 4 PRESENT" # The field in the IAM message containing the TLDN number for home # and roam incoming calls. # Format: # isupTldnTerminationParameterId "<homeParamId> <roamParamId>" # <homeParamId> := NONE | <iamParamId> (see isupTerminationIndicator) # <roamParamId> := NONE | <iamParamId> (see isupTerminationIndicator) isupTldnTerminationParameterId "NONE NONE" # The field in the IAM message containing the subscriber number for # home and roam incoming calls.

# Format: # isupSubscriberTerminationParameterId "<homeParamId> <roamParamId>" # <homeParamId> := NONE | <iamParamId> (see isupTerminationIndicator) # <roamParamId> := NONE | <iamParamId> (see isupTerminationIndicator) isupSubscriberTerminationParameterId "4 4" # Default TLDN used in case isupTldnTerminationParameterId is "NONE". # Format: # isupDefaultTldn <tldn> # WARNING!! <tldn> must exist in the TLDN table. isupDefaultTldn DEFAULT


150

D.8 winDefault.prf.sample #

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

# # This file contains a description of the "Switch Interface" # configurable parameters for WIN-II. # #

%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%%

# # The Switch (MSC) protocol types supported by the MSC. # Format: switchProtocolType "<protocolType>" # # <protocolType> could be any one of the following: # - "WIN2" # - "WIN2 ISUP" #switchProtocolType "WIN2" #%%PROMPTUSER%% modify at

installation # # WIN Announcement ID definitions for Switch-based as well as for

IVR-based. # # Formats: # # 1. IVR-Based Announcement # ====================== # # "winAnnouncementId <prepayAnncID>" "IVR_BASED

<IVRDigits>" # # Or, # # 2. Switch-Based Announcement # ========================= # # "winAnnouncementId <prepayAnncID>" "SWITCH_BASED

<winAnncCodeID_LABEL-1> <winAnncCodeID_LABEL-2>" #


151

# # Or, # # 3. No Announcement - No announcement is to be played for

specified Announceme nt ID, <prepayAnncID> # =============== # # "winAnnouncementId <prepayAnncID>" "NO_ANNOUNCEMENT" # # # <prepayAnncID> Could be one of the following: # # 1 - Call Duration Information # 2 - Low Balance Warning # 3 - Insufficient Balance # 4 - Call End Warning (i.e. to indicate call will be

disconnected soon). # 5 - Disconnect Warning (i.e. Call is being be

disconnected. # 6 - 1 minute Warning (i.e. Call will be disconnected in

1 minute) # 7 - 2 minute Warning (i.e. Call will be disconnected in



5 minutes) # 10 - Subsequent Low Balance Warning # 11 - Subsequent Expiration Warning # 12 - First Expiration Warning (The first time expiration

warning is hit. # # NOTE: 1, 2, 3, 4, 5, 10, 11 and 12 are MANDATORY - they

must be present. # ==== # # <IVRDigits> - Identifies the IVR Routing digits. # # Examples of IVR-Based announcements are: # # "winAnnouncementId 1" "IVR_BASED 4445556666" # "winAnnouncementId 2" "IVR_BASED 5556667777" #


152

# <winAnncCodeID_LABEL> - Is a label/identifier to a list of one or more of

# WIN/ANSI41 AnnouncementCode parameter values (These identify the switch-based

# tone/announcement). e.g. "ANNC_CODE_SET1 ANNC_CODE_SET2" # # The format of the config. parameter that contains the

<winAnncCodeID_LABEL> is as follows: # # "winAnnouncementMsgId <winAnncCodeID_LABEL>"

"<ListOfAnncCodes>" # # <ListOfAnncCodes> - One or more WIN/ANSI41 AnnouncementCode

parameter values . # These identify a switch-based tone/announcement. # The format of the <ListOfAnncCodes> field is: # # Format: # <Tone Value> <ClassOfAnnc> <StandardAnnc Value> <CustomAnnc

Value> # # <Tone Value>, and <StandardAnnc Values> are those specified

in IS-826. # NOTE: <StandardAnnc Value> and <CustomAnnc Value> may or

may not be # present. # # <Tone Values> examples are: # 192 PipTone # 20 Pre-Paid Charging, Insufficient Funds Tone # 21 Pre-Paid Charging, Warning Tone 1 # 22 Pre-Paid Charging, Warning Tone 2 # 24 Pre-Paid Charging, Disconnect Tone # # <ClassOfAnnc> contains one of the following: # - CONCURRENT Play announcements concurrently with any

call routing. # - SEQUENTIAL Play all announcements before all call

termination or # routing. # # <StandardAnnc Values> examples are: # 152 Pre-Paid Charging, Insufficient Account Balance # 153 Pre-Paid Charging, 5-minute warning


153

# 154 Pre-Paid Charging, 3-minute warning # 155 Pre-Paid Charging, 2-minute warning # 156 Pre-Paid Charging, 1-minute warning # 157 Pre-Paid Charging, Disconnect # # <CustomAnnc Values> identifies Custom announcement codes. # These are determined by bilateral agreement with the MSC

vendor. # # Examples of <ListOfAnncCodes> are: # # "20 CONCURRENT" # "21 SEQUENTIAL 152" # # Some examples of Switch-Based announcements are: # # "winAnnouncementId <prepayAnncID>" "SWITCH_BASED

<winAnncCodeID_LABEL-1> <win AnncCodeID_LABEL-2>" # # "winAnnouncementId 4" "SWITCH_BASED ANNC_CODE_SET1

ANNC_CODE_SET2" # # "winAnnouncementMsgId ANNC_CODE_SET1" "192 CONCURRENT 154" # "winAnnouncementMsgId ANNC_CODE_SET2" "21 SEQUENTIAL 152" # "winAnnouncementMsgId ANNC_CODE_SET3" "21 SEQUENTIAL 152

244", where # 244 is <CustomAnnc.> # # "winAnnouncementId 0" "IVR_BASED 0001112222" "winAnnouncementId 1" "IVR_BASED 1112223333" "winAnnouncementId 2" "IVR_BASED 2223334444" "winAnnouncementId 3" "IVR_BASED 3334445555" "winAnnouncementId 4" "SWITCH_BASED ANNC_CODE_SET1 ANNC_CODE_SET2

ANNC_CODE_SET3 " "winAnnouncementId 5" "SWITCH_BASED 3" "winAnnouncementId 6" "SWITCH_BASED 5" "winAnnouncementId 10" "NO_ANNOUNCEMENT" "winAnnouncementId 11" "NO_ANNOUNCEMENT" "winAnnouncementId 12" "IVR_BASED 5554445555" "winAnnouncementMsgId ANNC_CODE_SET1" "192 CONCURRENT 154" "winAnnouncementMsgId ANNC_CODE_SET2" "21 SEQUENTIAL 152"


154

"winAnnouncementMsgId ANNC_CODE_SET3" "21 SEQUENTIAL 152 244" "winAnnouncementMsgId ANNC_CODE_SET4" "3 CONCURRENT 30 33" "winAnnouncementMsgId ANNC_CODE_SET5" "195 SEQUENTIAL 152" "winAnnouncementMsgId ANNC_CODE_SET6" "20 SEQUENTIAL 153" "winAnnouncementMsgId 3" "21 SEQUENTIAL 152" "winAnnouncementMsgId 5" "21 SEQUENTIAL 152" # # WIN/ANSI-41 DMH_ServiceID parameter value # # Format: winDmhServiceId "<MarketID MarketSegmentID

DMH_ServiceID value>" # winDmhServiceId "30 33 30" # # CCDIR Timer value in seconds. If not specified, a default value

will be used. # This is the time for which the PPAS will wait for a response

from the MSC to # the CallControlDirective Invoke (CCDIR) message. # # In cases where the CCDIR is used to play a mid-call

announcement, the MSC # will send the CallControlDirective Result message after the

announcement has # been completed - so the value should be large enough to take

care of the # time the MSC takes to play the announcement(s) specified in the

CCDIR # message. # winCCDirTimeOut "30" # UnRelCallData Timer value in seconds. If not specified, a

default value will # be used. # This is the time for which the PPAS will wait for a response

from the MSC to # the UnRelCallData Invoke message or CallRecoveryReport Response

message. # winUnRelCallDataTimeOut "30" # This is the value of maximum number of times, the ss&TcapParser

will try to


155

# send UnRelCallData Invoke message, if it does not receives a response, before

# the UnRelCallData Timer expires. winMaximumNumberOfRetryAttemptsForUnRelCallData "3" # 'winWinCapabilityRequired' indicates whether PPAS should log an

error # message upon receipt of an Analyzed Information message without

the # mandatory WinCapability parameter. winWinCapabilityRequired "FALSE" # 'winAcgEnabled' indicates whether the PPAS should send # one ACG Directive to the MSC, when the PPAS determines # that it is in congestion. # Format: winAcgEnabled "<value>" # <value> contains TRUE or FALSE. # Default is FALSE (i.e. do not send ACG Directive,

after congestion). # # See prepay.default for the configuration parameters that

determine when PPAS is in congestion. winAcgEnabled "FALSE" # 'winGapDuration' indicates the length of the time an ACG

control should remain in force, before it is removed. # Format: winGapDuration "<value>" # <value> should be one of the following: # 0 IS41_GAP_DURATION_UNKNOWN # 1 IS41_GAP_DURATION_1_SECOND # 2 IS41_GAP_DURATION_2_SECONDS # 3 IS41_GAP_DURATION_4_SECONDS # 4 IS41_GAP_DURATION_8_SECONDS # 5 IS41_GAP_DURATION_16_SECONDS # 6 IS41_GAP_DURATION_32_SECONDS # 7 IS41_GAP_DURATION_64_SECONDS # 8 IS41_GAP_DURATION_128_SECONDS # 9 IS41_GAP_DURATION_256_SECONDS # 10 IS41_GAP_DURATION_512_SECONDS # 11 IS41_GAP_DURATION_1024_SECONDS # 12 IS41_GAP_DURATION_2048_SECONDS # 13 IS41_GAP_DURATION_INFINITE winGapDuration "6"


156

# 'winGapInterval' indicates the minimum amount of time that the MSC under

# ACG control must wait before sending another query to PPAS. # Format: winGapInterval "<value>" # <value> should be one of the following: # 0 IS41_GAP_INTERVAL_0_SECONDS # 1 IS41_GAP_INTERVAL_3_SECONDS # 2 IS41_GAP_INTERVAL_4_SECONDS # 3 IS41_GAP_INTERVAL_6_SECONDS # 4 IS41_GAP_INTERVAL_8_SECONDS # 5 IS41_GAP_INTERVAL_11_SECONDS # 6 IS41_GAP_INTERVAL_16_SECONDS # 7 IS41_GAP_INTERVAL_22_SECONDS # 8 IS41_GAP_INTERVAL_30_SECONDS # 9 IS41_GAP_INTERVAL_42_SECONDS # 10 IS41_GAP_INTERVAL_58_SECONDS # 11 IS41_GAP_INTERVAL_81_SECONDS # 12 IS41_GAP_INTERVAL_112_SECONDS # 13 IS41_GAP_INTERVAL_156_SECONDS # 14 IS41_GAP_INTERVAL_217_SECONDS # 15 IS41_GAP_INTERVAL_300_SECONDS # 16 IS41_GAP_INTERVAL_REMOVE_GAP_CONTROL # 17

IS41_GAP_INTERVAL_ONE_HUNDREDTH_OF_A_SECOND # 18 IS41_GAP_INTERVAL_ONE_FOURTH_OF_A_SECOND # 19 IS41_GAP_INTERVAL_HALF_A_SECOND # 20 IS41_GAP_INTERVAL_1_SECONDS # 21 IS41_GAP_INTERVAL_2_SECONDS winGapInterval "2" # 'winPcSsnType' indicates the type of functional entity (e.g.

HLR, VLR, MSC) # Format: winPcSsnType "<value>" # <value> should be one of the following: # 0 IS41_PC_SSN_TYPE_UNKNOWN # 1 IS41_PC_SSN_TYPE_SERVING_MSC # 2 IS41_PC_SSN_TYPE_HOME_MSC # 3 IS41_PC_SSN_TYPE_GATEWAY_MSC # 4 IS41_PC_SSN_TYPE_HLR # 5 IS41_PC_SSN_TYPE_VLR # 6 IS41_PC_SSN_TYPE_EIR # 7 IS41_PC_SSN_TYPE_AC # 8 IS41_PC_SSN_TYPE_BORDER_MSC


157

# 9 IS41_PC_SSN_TYPE_ORIGINATING_MSC winPcSsnType "9" # # WIN Response Timer value in seconds. # This is the time for which the PPAS will wait for a

ConnectionFailureReport # Invoke message (CONNFAILRPT) from the MSC after the . The MSC

will send the # CONNFAILRPT message when its IVR call gets disconnected (i.e.

mainly, after # the IVR announcement has been completed). # So the value should be large enough to take care of the time

the # MSC takes to play the IVR announcement(s). # winResponseTimeOut "30" # # 'winMinMdnEquivalenceFlag' - Indicator to determine whether MIN

parameter # value is to be copied into the MobileDirectoryNumber (MDN) if

MDN does # not arrive in the message from the MSC. # Format: winMinMdnEquivalenceFlag "<flag>" # <flag> contains YES or NO. Default is YES. # winMinMdnEquivalenceFlag "NO" # 'winSendCcdirOnceToDisconnect' indicates whether the PPAS

should send # one CCDIR to the MSC to disconnect a call, or should the PPAS

send # one CCDIR (CallControlDirective Invoke) for each call leg. # Format: winSendCcdirOnceToDisconnect "<value>" # <value> contains TRUE or FALSE. # Default is FALSE (i.e. send CCDIR, one for each call

leg). # # Note: # This parameter has been added to take care of MSCs that

disconnect # the all legs in a call (i.e. the entire call) when PPAS

requests it # to disconnect a specific one call leg.


158

# winSendCcdirOnceToDisconnect "FALSE" # # Configuration to determine the Routing Action on prepay rating

errors. # # Format: # "errorRoutingAction <errorCause>" "<RoutingAction>

<prepayAnncID>" # # <errorCause> - Could be one of the following: # # 1 = RESOURCE_SHORTAGE : A resource for rating the call

is # temporarily unavailable. # # 2 = SYSTEM_FAILURE : A temporary failure has

occurred while the # call was being rated. # # 3 = UNKNOWN_SUBSCRIBER : Subscriber is NOT a valid

Prepay subscriber. # # <RoutingAction> - The configured routing action. Could be

one # of the following: # # ROUTE_CALL : Route/Terminate the call. # # DENY_CALL : Deny call routing/termination. # # PLAY_ANNC_AND_ROUTE_CALL: Play an announcement and then # Route/Terminate the call. # # PLAY_ANNC_AND_DENY_CALL : Play an announcement and then

deny call. # Routing/Termination. # # # NOTE : Default <RoutingAction> is set to "DENY_CALL". # --------------------------------------------- # #


159

# If <RoutingAction> is PLAY_ANNC_AND_ROUTE_CALL or PLAY_ANNC_AND_DENY_CALL, then <prepayAnncID> specifies the announcement to be played. The announcement could be either Switch-based or IVR-based. (See <prepayAnncID> above ).

# # # NOTE: If <RoutingAction> is either PLAY_ANNC_AND_ROUTE_CALL or

PLAY_ANNC_AND_DENY_CALL and <prepayAnncID> is "NO_ANNOUNCEMENT" then default routing action would be either ROUTE_CALL or DENY_CALL.

# "errorRoutingAction 1" "PLAY_ANNC_AND_ROUTE_CALL 2" "errorRoutingAction 2" "DENY_CALL" "errorRoutingAction 3" "PLAY_ANNC_AND_DENY_CALL 10" # Other error routing action examples are given below: #"errorRoutingAction 1" "ROUTE_CALL" #"errorRoutingAction 1" "DENY_CALL" #"errorRoutingAction 1" "PLAY_ANNC_AND_DENY_CALL 2" #"errorRoutingAction 2" "ROUTE_CALL" #"errorRoutingAction 2" "PLAY_ANNC_AND_ROUTE_CALL 1" #"errorRoutingAction 2" "PLAY_ANNC_AND_DENY_CALL 2" #"errorRoutingAction 3" "ROUTE_CALL" #"errorRoutingAction 3" "DENY_CALL" #"errorRoutingAction 3" "PLAY_ANNC_AND_ROUTE_CALL 2" #"errorRoutingAction 3" "PLAY_ANNC_AND_ROUTE_CALL 5"


160

D.9 pplError.English.Sample -1001 "Read on the socket failed" -1002 "Write on the socket failed" -1003 "Connect on the socket failed" -1004 "Accept on the socket failed" -1005 "Invalid Request" -1006 "Invalid Response" -1007 "Signal caught error" -1008 "Association down error" -1009 "Socket creation failed" -1100 "Database connect failed" -1101 "Database disconnect failed" -1102 "Database select error" -1103 "Database commit error" -1104 "Database rollback error" -1105 "Database fetch complete error" -1106 "Database fetch Update Count error" -1107 "Database load complete error" -1108 "Database load update error" -1109 "Database fetch TLDN count error" -1110 "Database load TLDN error" -1200 "ERROR_THREAD_COMPLETESYNC_CREATION" -1201 "ERROR_THREAD_UPDATESYNC_CREATION" -1202 "Thread Startup creation error" -1203 "TLDN thread creation error" -1204 "Subscriber Handler Thread creation error" -1205 "Error initializing thread request writer" -1300 "Get element in a Q failed" -1301 "Put element in the Q failed" -1302 "Q is empty -1400 "Invalid state of the object -1401 "Memory Allocation Error" -1402 "Invalid date interval" -1403 "Invalid interval" -1404 "Invalid date" -1420 "Connection State error" -1421 "Listener state error" -1422 "Error initializing listener" -1423 "Error running listener" -1424 "Connection initialization Error"


161

-1500 "Table creation error" -1501 "Error Populating table" -1502 "Table load time error" -1503 "Error finding element in a table" -1504 "Error inserting element in a table" -1505 "Error removing element from a table" -1506 "Error destroying element from a table" -1507 "Destroy and clear table error" -1508 "Table not Set" -1600 "Association state error" -1601 "Association initialization error" -1602 "Association run error" -1603 "Association not set" -1700 "Error adding element at the tail" -1800 "Error processing TLDN request" -1801 "Subscriber request processing error" -1900 "Failed to initialize statistics thread" -1901 "Failed to create statistics thread" -1902 "Error statistics file name is empty" -1903 "Could not open statistics file" -1904 "Failed to terminate statistics thread"


162

Performing a Solaris Rollback

Note: This rollback is not a mandatory step. It should be performed only if a significant problem has been introduced as a result of installing this Solaris upgrade.

Downgrade Solaris from the June 2005 release of Version 8 to the prior version by restoring the Solaris backup.

Caution: Lightbridge strongly recommends that this procedure be performed on a fresh disk.

If a blank disk is available, remove and label the existing boot disk and replace it with the blank disk.

1. Create new file systems on the boot disk. newfs /dev/rdsk/c0t0d0s0 newfs /dev/rdsk/c0t0d0s5

2. Boot the system from the CD-ROM in single user mode. boot cdrom –s

3. Mount the new boot disk on a temporary mount point. mount /dev/dsk/c0t0d0s0 /mnt

4. Change to the /mnt directory. cd /mnt


163

5. Write-protect the tapes.

6. Use the ufsrestore command to restore the root file system. This command uses tape drive 0 (/rmt/mnt/0). ufsrestore rvf /dev/rmt/0

7. The level 0 tape is restored.

8. Verify the file system is restored. ls

9. Remove the restoresymtable file. This file is created and used by ufsrestore to check-point the restore. rm /restoresymtable

10. Change to the root (/) directory. cd /

11. Unmount the newly created file system. umount /mnt

12. Check the new file system for consistency. fsck /dev/rdsk/c0t0d0s0

13. Create the boot blocks on the root partition by using the installboot (1M) command. installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk \

/dev/rdsk/c0t0d0s0

14. Repeat steps 4 through 14 for the /var file system.

15. Reboot the system with the new drive.

The following example shows all of the commands used to perform a Solaris rollback.


164

Example: (of restoring the root (/) file system) mount /dev/dsk/c0t0d0s0 /mnt cd /mnt ufsrestore rvf /dev/rmt/0 ls rm restoresymtable cd / umount /mnt fsck /dev/rdsk/c0t0d0s0 installboot /usr/platform/`uname -i`/lib/fs/ufs/bootblk \

/dev/rdsk/c0t3d0s0 ufsdump 0uf /dev/rmt/0 /dev/rdsk/c0t0d0s0 init 6


165


166

Upgrading from Oracle 9.2.0.4 to version 9.2.0.6 on Solaris 8

WARNING: Before upgrading Oracle to version 9.2.0.6, make sure that a complete backup of the database has been made.

WARNING: PrePay and Oracle application downtime are required for this work. Estimated down time is 90 minutes to perform the upgrade.

Note: Except where explicitly stated otherwise, all steps are to be performed as the 'oracle' Unix user.

Note: All instructions and examples assume the use of the Korn shell (ksh). Use of another shell may cause some commands to fail or to work incorrectly.


167

F.1 Preparation Steps for Oracle 9.2.0.6 For Distributed Architecture configurations, upgrade the Oracle software on the SCP and SDP servers. The database conversion should only be run on the SDP.

F.1.1 Check Solaris is Running in 64-bit Mode Run the command ‘eeprom’ and review the values returned for the ‘boot-file’ parameter. The output should say ‘data not available’ which means it will boot up in 64-bit mode by default.

eeprom | grep boot-file boot-file: data not available.

F.1.2 Check Available Space in $ORACLE_HOME File System Approximately 2GB of free space will be needed in the /oracle/ora920 file system.

df –k /oracle (if ora920 will be a subdirectory within this

file system) df –k /oracle/ora920 (if it will be it’s own file system)

F.1.3 Record the Database Character Set Run the following commands to record database options in case they’re needed later:

su – oracle mkdir /home/oracle/pre9206 cd /home/oracle/pre9206 sqlplus ‘/ as sysdba’ set pages 5000 spool database_options.lst select name,substr(value$,1,40) value from props$; spool off quit


168

F.1.4 Record the Database Block Size Run the following commands to record database block size for later:

sqlplus ‘/ as sysdba’ spool database_blocksize.lst show parameter db_block_size spool off quit

F.1.5 Check for use of N-type Columns Check to see if any user tables use N-type columns. If so, refer to Oracle’s Migration documentation for potential upgrade issues.

To determine if N-type columns are being used, execute the SQL query below. If no rows are returned then continue with this migration.

select distinct owner, table_name from dba_tab_columns where data_type in (‘NCHAR’,’NVARCHAR2’,’NCLOB’) and owner not in (‘SYS’,’SYSTEM’);

F.1.6 Check for Corruption in the Dictionary Run the following query to obtain data dictionary information:

sqlplus ‘/ as sysdba’ set verify off space 0 feedback off pages 0 termout off spool analyze.sql select 'Analyze '||object_type||' '||object_name||'

validate structure;' from dba_objects where owner='SYS' and object_type in ('INDEX','TABLE','CLUSTER'); spool off quit

This creates a script called analyze.sql, which in turn will have to be executed. This script (analyze.sql) should not return any errors.

sqlplus ‘/ as sysdba’ spool analyze.lst


169

@analyze.sql quit

F.1.7 List All Objects that are not VALID After the upgrade is complete, all objects will be invalid. For future comparison, execute this query to list all objects that are not valid. This list will be used to compare against the list of invalid objects when the install is complete.

sqlplus ‘/ as sysdba’ spool invalid_pre.lst select substr(owner,1,12) owner, substr(object_name,1,30) object, substr(object_type,1,30) type, status from dba_objects where status <>'VALID'; spool off quit

F.1.8 Create a Script to Compile All Invalid Objects To create a script to compile all invalid objects, before upgrading, run the script called utlrp.sql in the $ORACLE_HOME/rdbms/admin directory. This script recompiles all invalid PL/SQL in the database including views.

cd $ORACLE_HOME/rdbms/admin sqlplus ‘/ as sysdba‘ @utlrp.sql quit

Run the script and then rerun the query from above to get invalid objects.

F.1.9 List the Grants If the upgrade fails and the dictionary was already rebuild, grants are lost. If you want to go back it is advisable to have a list of grants. Create and run the following script:

cd /home/oracle/pre9206 vi list_grants.ksh #!/bin/ksh #


170

# list_grants.ksh #--: #--: generates DDL of database #--: exp userid=$1/$2 file=struct compress=no full=y rows=n imp userid=$1/$2 file=struct full=y show=y 2> contents.lst rm struct.dmp awk ' BEGIN { prev=";" } / \"CREATE / { N=1; } / \"ALTER / { N=1; } / \"ANALYZE / { N=1; } / \"GRANT / { N=1; } / \"REVOKE / { N=1; } / \"COMMENT / { N=1; } / \"AUDIT / { N=1; } N==1 { printf "\n/\n\n"; N++ } /\"$/ { prev="" if (N==0) next; s=index( $0, "\"" ); if ( s!=0 ) { printf "%s",substr( $0,s+1,length(

substr($0,s+1))-1 ) prev=substr($0,length($0)-1,1 ); } if (length($0)<78) printf( "\n" ); }' < contents.lst > struct1 rm contents.lst sed /^$/d < struct1 > struct2 grep ‘^GRANT’ struct2 | fold –s –w75 > ppay.sql rm struct1 struct2 :wq! chmod 755 list_grants.ksh ./list_grants.ksh system {system_password}

F.1.10 Ensure No Files Need Media Recovery To ensure that no files require media recovery, execute the following query:

sqlplus ‘/ as sysdba‘ select * from v$recover_file; quit


171

This should return no rows. If rows are returned you must check with the DBA responsible for the system you are upgrading.

F.1.11 Ensure No Files are in Backup Mode To determine if there are any file in backup mode run the following query:

sqlplus ‘/ as sysdba‘ select * from v$backup where status!='NOT ACTIVE'; quit

This should return no rows. If rows are returned you must check with the DBA responsible for the system you are upgrading.

F.1.12 Prepare the System Rollback Segment Ensure plenty of free space in the SYSTEM tablespace. A minimum of 50 Mb free space.

select max(bytes) from dba_free_space where

tablespace_name='SYSTEM';

Modify the system rollback segment’s storage parameters alter rollback segment system storage (maxextents 121 next

1M);

F.1.13 Ensure Freespace in Rollback Tablespace Ensure that at least one rollback segment of 70MB if the number of objects in the database exceeds 5000.

select count(*) from dba_objects;

F.1.14 Ensure SYS and SYSTEM have ‘SYSTEM’ as Default Tablespace To list the username and default tablespaces use the following query:


172

select username, default_tablespace from dba_users where username

in ('SYS','SYSTEM');

To modify use: alter user sys default tablespace SYSTEM; alter user system default tablespace SYSTEM;

F.1.15 Record the Locations of All Control Files To list all the control file locations, execute the following query:

select * from v$controlfile;

This information is very important, and it should be used when configuring the initppay.ora file. Also, the control file locations are important so we don’t delete or overwrite those files.

F.1.16 Ensure NLS_LANG Variable is Set Correctly Display the current setting for NLS_LANG.

echo $NLS_LANG

Compare the values to those returned in the query against the props$ table above. If different, then modify /home/oracle/cfg/oracle_profile and resource the ~oracle/.profile. Verify the change by repeating the command above.

F.1.17 Disable All Oracle Related Batch and Cron Jobs Scheduled jobs should be blocked from running while performing the Oracle 9i upgrade. If any scheduler other than cron is being used, disable it for the Oracle UNIX account until the upgrade has been completed.

su – oracle mkdir pre920 cd pre920 crontab –l > crontab.pre920 crontab –r


173

F.2 Upgrade Oracle to 9.2.0.6

F.3 PreParation Tasks 1. Check for post-release updates. Go to metalink.oracle.com and click on the

Advanced tab. Then enter 189908.1 in the document id field and hit Submit. As of May 11, 2005 the following bugs were introduced in 9.2.0.6. After reviewing the details of each, only a subset was determined to be necessary.

2. Review the latest list of bugs introduced in 9.2.0.6 against the list below. If any new bugs are relevant to the client’s own application, download the patch and apply it after these necessary patches. • 4071941 Necessary; 32 bit JDBC library not installed as part of 9206 patch • 4080972 Necessary; Bug can produce incorrect results • 4074633 N/A; AIX only • 4074603 N/A; Data Guard only • 4066495 N/A; RAC only • 3691672 Necessary if using JavaVM • 4254094 N/A; Unless client uses DB Links • 4197078 N/A; Fixed in 9.2.0.6. • 4172170 N/A; Low risk of occurrence. Still under investigation. No patch • 4165093 N/A; Unless client uses DB Links • 4157713 Necessary; Bug can produce ORA-600 under heavy load. • 4154591 Necessary; No patch. Set event 38047 until 9.2.0.7 is available. • 4142932 Necessary; For LMT and ASSM • 4131501 N/A; For star transformations • 4116896 N/A; Low risk of occurrence and impact • 4112324 N/A; Problem still under investigation • 4101485 N/A; Low risk of occurrence and impact • 4098853 N/A; Low risk of occurrence and impact • 4082618 N/A; Low risk of occurrence and impact; no patch • 4058160 N/A; Gateway interfaces only • 4047527 N/A; ODM only • 4039237 Necessary; Bug can produce incorrect results • 4016802 N/A; Not using composite partitioned tables • 4015165 Necessary; Bug can produce ORA-6502 from PL/SQL • 3998408 N/A; RAC only • 3963167 N/A; Low risk of occurrence. Conflicts with 4080972. • 3949307 Necessary; Bug can produce SGA corruption • 3945578 N/A; Linux only • 3926058 N/A; Low risk of occurrence and impact • 3901170 N/A; initppay.ora should not set 10235 or 10501 events


174

• 3844015 N/A; initppay.ora should not set 38044 or 38056 events • 3777178 N/A; RAC only • 3256015 N/A; Low risk of occurrence and impact • 3228560 N/A; Low risk; Can wait for 9.2.0.7 availability

3. Check if SUNWuiu8 is installed. If not, install it first. a. pkginfo SUNWuiu8

4. Verify $ORACLE_HOME has at least 300MB of free space. 5. Verify /tmp has at least 80MB of free space. 6. Verify swap space has at least 150MB of free space. 7. mkdir $ORACLE_BASE/patches 8. Copy the oraInventory9204.tar.gz file for 9.2.0.4 to the patches directory 9. Copy the following 9206 patches to $ORACLE_BASE/patches:

a. p2617419_10102_GENERIC.zip (this is the OPatch patch) b. p3691672_9206_SOLARIS64.zip c. p3948480_9206_SOLARIS64.zip (this is the 9206 patchset) d. p3949307_9206_SOLARIS64.zip e. p4015165_9206_SOLARIS64.zip f. p4039237_9206_SOLARIS64.zip g. p4071941_9206_SOLARIS64.zip h. p4080972_9206_SOLARIS64.zip i. p4142932_9206_SOLARIS64.zip j. p4157713_9206_SOLARIS64.zip

10. Perform an on-line backup of the Oracle database. 11. Backup the Oracle 9.2.0.4 software. Include /oracle and /var/opt/oracle.

F.3.1 Maintenance window tasks Before starting any upgrade activity, enable the logging of your session to a script file with an embedded date/timestamp after logging on as the oracle user.

Recommended filename: ~/oracleupgrade_9206_yyyymmddhhmm.log

Command: script ~/oracleupgrade_9206_<yyyymmddhhmm>.log

*** Beginning of DOWNTIME *** 1. Stop Prepay and any other applications that access the database. 2. Install the oraInventory.tar file into $ORACLE_HOME


175

a. su – oracle b. cd $ORACLE_HOME c. gunzip –dc $ORACLE_BASE/patches/oraInventory9204.tar.gz | tar xvf –

3. Delete statistics on SYSTEM objects if they exist. a. sqlplus /nolog b. connect / as sysdba c. execute dbms_stats.delete_schema_stats(‘SYS’); d. execute dbms_stats.gather_schema_stats(‘SYS’); e. quit

4. Set SESSION_CACHED_CURSORS since behavior has changed in 9.2.0.6: a. cd $ORACLE_HOME/dbs b. vi initppay.ora

If OPEN_CURSORS > 1000 then

If SESSION_CACHED_CURSORS < 1000 then

Set SESSION_CACHED_CURSORS = OPEN_CURSORS

Save changes. 5. Check the SYSTEM tablespace has at least 10MB freespace.

a. select sum(bytes),max(bytes) from dba_free_space where tablespace_name=’SYSTEM’;

6. Set the SHARED_POOL_SIZE and JAVA_POOL_SIZE. a. startup b. show parameter pfile;

i. If the VALUE column is blank then an SPFILE is not being used. c. show parameter shared_pool_size d. show parameter java_pool_size

If either parameter is below 150MB then

If using an SPFILE then

set shared_pool_size to at least 150MB

set java_pool_size to at least 150MB

else

vi $ORACLE_HOME/dbs/initppay.ora

add/update both parameters (for very small servers, both parameters can be set to 100MB)


176

restart the database

endif 7. Shutdown the database and the listener:

a. sqlplus /nolog b. connect / as sysdba c. shutdown immediate d. quit e. lsnrctl stop f. ps –ef | grep –i ora (look for additional listener processes) g. lsnrctl stop {listener_name} (if more than one listener is running)

Installation Tasks 1. su – oracle 2. DISPLAY={X-Window PC}:0.0 3. export DISPLAY 4. Start X-Windows on a PC 5. cd $ORACLE_BASE/patches 6. unzip p3948480_9206_SOLARIS64.zip 7. cd Disk1 8. ./runInstaller

a. If OUI fails to start and reports errors referring to ‘checkdir’ then see Oracle Metalinks Document ID 294190.1 for a work-around. The details of this are included below.

b. Warning messages on the Solaris server regarding ‘Cannot convert string’ can be ignored.

c. On the Welcome screen, click NEXT. d. On the Specify File Locations screen, click BROWSE next to the Path

field in the Source section. e. Select the products.xml file from the stage directory where you unpacked

the patch set files, then click Next. For example: /work/ora9206/Disk1/stage/products.xml

f. In the Name field in the Destination section, select the name of the Oracle home that you want to update from the drop down list, then click Next.

g. On the Summary screen, click Install. h. During the ‘Linking XML Class Generator’ task, a window may appear

with the message: i. Error in invoking target ‘install_isqlplus install’ of makefile. j. This can be ignored. Click on Continue. k. When prompted, run the $ORACLE_HOME/root.sh script as the root

user. l. On the End of Installation screen, click Exit, then click Yes to exit from

the Installer.


177

Post-installation Tasks

Upgrade the Database 1. su – oracle 2. lsnrctl start 3. sqlplus /nolog 4. connect / as sysdba 5. startup migrate 6. spool patch.log 7. @?/rdbms/admin/catpatch.sql 8. spool off 9. review the patch.log 10. if necessary, rerun the catpatch 11. shutdown 12. startup 13. @?/rdbms/admin/utlrp.sql 14. If using RMAN, then upgrade the catalog:

a. rman catalog user/pass; b. upgrade catalog;

Install Patches for 9.2.0.6 1. Shutdown the database and all listeners:

a. sqlplus /nolog b. connect / as sysdba c. shutdown d. lsnrctl stop (stop all listeners if more than one is configured)

2. Check for any Oracle processes. Stop if any are found. a. ps –ef | grep –i ora

3. Verify the Oracle Universal Installer (OUI) is at version 2.2.0.18. It is very important for future patches that the OUI version is at this release.

a. cat /var/opt/oracle/oraInst.loc b. cat <directory identified above>/oui.loc c. look for the value of “InstVer”. It should be 2.2.0.18.0. If not, install the

latest opatch from Metalinks. 4. Install latest version of OPatch:

a. cd $ORACLE_HOME b. unzip $ORACLE_BASE/patches/p2617419_10102_GENERIC.zip

(if prompted with: replace OPatch/docs/FAQ? [y]es, [n]o, [A]ll, [N]one, [r]ename: reply with All )

5. Fix a bug in OPatch where it cannot determine Solaris8 64-bit correctly.


178

a. cd b. vi .profile

i. Add to the end of the file and save the changes: ii. OPATCH_PLATFORM_ID=23 iii. export OPATCH_PLATFORM_ID

c. . ~/.profile d. echo $OPATCH_PLATFORM_ID (verify it is set to 23)

6. For each bug/patch file listed below: • 3691672 • 3949307 (directory created is 4060756) • 4015165 (directory created is 4070695) • 4039237 • 4071941 • 4080972 • 4142932 • 4157713

Perform the following steps. Note the patch directory may not match the bug id in the .zip file. Cd into the directory created when unzipping the patch file.

a. cd $ORACLE_BASE/patches b. unzip p${file}_9206_SOLARIS64.zip c. cd {directory created by running unzip} d. $ORACLE_HOME/OPatch/opatch apply e. Enter ‘Y” after verifying no Oracle processes are running and

$ORACLE_HOME is set correctly. 7. Bug 4154591:

Modify $ORACLE_HOME/dbs/initppay.ora a. cd $ORACLE_HOME/dbs b. vi initppay.ora c. Add the following line to the bottom of the file and save it: d. set event 38047 # Workaround for bug 4154591 until 9207 is applied

8. Reset SHARED_POOL_SIZE AND JAVA_POOL_SIZE. a. cd $ORACLE_HOME/dbs b. vi initppay.ora c. Change SHARED_POOL_SIZE back to its original value. d. Change JAVA_POOL_SIZE back to its original value or delete if it was

newly added for the 9.2.0.6 patchset. 9. Start the database and all listeners.

a. startppay b. startsqlnet

10. Start PrePay


179

*** End of Oracle upgrade ***

Workaround for runInstaller not running. See Oracle Metalinks Document ID 294190.1

Symptom

When trying to start OUI 10.1.0.3, to install the 9.2.0.6 64-bit patchset on Solaris, it failed to start and reported errors like this:

checkdir error: cannot create /tmp/OraInstall2004-12-16_12-20-06PM/oui/bin

checkdir error: cannot create /tmp/OraInstall2004-12-16_12-20-06PM/oui/guide

Cause

Support have raised <Bug:4080902> for this issue with OUI 10.1.0.3

Note that this issue could not be reproduced by Support, and only seems to affect some customers.

Fix

Window 1:

% cd /Disk1

Window 2:

% cd /tmp

% rm -rf OraInstall*


180

Create a shell script called "fix.sh" with the following three lines:

cd /tmp/OraInstall*

mkdir -p oui/bin oui/guide

chmod 777 oui/bin oui/guide

Instructions:

1) In window 1, run the following command:

./runInstaller

2) In window 2, run the following commands:

sh fix.sh

Note that step 2 needs to completed quickly, before OUI fails. If you perform step 2 quickly enough, OUI should start successfully.

If OUI is reporting the problem about another directory, modify the mkdir and chmod commands in fix.sh as appropriate.

References

<BUG:4080902> - Oui 10.1.0.3.0 Reports Checkdir Errors And Fails To Start


181

initppay.ora

1. The following initppay.ora file is for Oracle 9.2.0.x only.

#

*************************************************************************

# * Copyright (c) 2003 Lightbridge, Inc. All Rights Reserved. # * # * Except as expressly authorized by Lightbridge, reproduction # * of any portion or element of this computer program, including

without # * limitation any portion of any image, text or screen is

strictly # * prohibited and is a violation of Federal law. #

*************************************************************************

#@(#)$Filename: #@(#)$Revision: #@(#)$Date: #

*************************************************************************

# # 2003-04-04 Kevin Jewell # Initial configuration file. # # 2003-04-07 Kamlesh Bans # Minor modifications #


182

# 2004-03-08 Kevin Jewell # Updated for Oracle 9i. # _trace_files_public = true audit_trail = false background_dump_dest = /temp/oradata/ppay/bdump #buffer_pool_keep = (buffers:n; latches:n) #buffer_pool_recycle = (buffers:n; latches:n) compatible = 9.2.0 control_files =

(/u01/oradata/ppay/ctrl1ppay.ctl,

/u02/oradata/ppay/ctrl2ppay.ctl,

/redo/oradata/ppay/ctrl3ppay.ctl,

/rollback/oradata/ppay/ctrl4ppay.ctl) core_dump_dest = /temp/oradata/ppay/cdump db_block_size = 8192 db_cache_advice = ready # Allocates

memory for later analysis. #db_cache_size = 256M # model S/A #db_cache_size = 512M # model B #db_cache_size = 768M # model C #db_cache_size = 1536M # model D db_domain = world #db_file_multiblock_read_count = 32 # model S/A/B/C #db_file_multiblock_read_count = 64 # model D #db_files = 256 # model S/A/B #db_files = 512 # model C/D db_name = ppay #db_writer_processes = 2 # model S/A/B #db_writer_processes = 4 # model C/C


183

dbwr_io_slaves = 0 # always use db_writers instead

disk_asynch_io = false #dml_locks = 512 # model S/A/B #dml_locks = 1024 # model C/D #enqueue_resources = 1024 # model S/A/B #enqueue_resources = 2048 # model C/D global_names = true hash_area_size = 20971520 # 20MB for all

models hash_join_enabled = true instance_name = ppay log_archive_dest = /temp/oradata/ppay/archive/ log_archive_format = arch_%s.arc log_archive_start = true # set to true for

archivelog mode #log_archive_start = false # set to false on

QA systems #log_buffer = 1048576 # model S/A/B

1MB #log_buffer = 2097152 # model C

2MB #log_buffer = 4194304 # model D

4MB log_checkpoint_interval = 0 # use time-based

checkpoints log_checkpoint_timeout = 900 # checkpoint

every 15 minutes for all models log_checkpoints_to_alert = true max_dump_file_size = 10240 # limit trace

file size to 5 Meg each #nls_date_format = DD-Mon-RR # application

handles dates correctly. may comment out. nls_language = "american" # set to local

language nls_sort = binary nls_territory = "america" # set to local

territory


184

open_cursors = 1024 # model S/A/B/C/D See Oracle BUG 1244182. Fixed in 8.1.6.3.

optimizer_index_caching = 90 # defaults are too low

optimizer_index_cost_adj = 50 # defaults are too low

optimizer_mode = choose os_authent_prefix = ops$ pga_aggregate_target = 0 # Set >0MB if

workarea_size_policy=auto. #processes = 200 # model S/A #processes = 300 # model B #processes = 400 # model C #processes = 500 # model D #remote_login_passwordfile = exclusive # uncomment

during RMAN installation #remote_os_authent = false rollback_segments =

(r01,r02,r03,r04,r05,r06,r07,r08,r09,r10,r11,r12,r13,r14,r15,r16,r17,r18,r19,r20)

service_names = ppay.world #sessions = 250 # model S/A #sessions = 350 # model B #sessions = 450 # model C #sessions = 550 # model D #session_cached_cursors = 100 # model S/A #session_cached_cursors = 200 # model B #session_cached_cursors = 300 # model C #session_cached_cursors = 400 # model D shared_pool_size = 94371840 # 90MB for all

models #shared_pool_reserved_size = # Do Not Set sort_area_retained_size = 2097152 # 2MB for all

models sort_area_size = 20971520 # 20MB for all

models


185

tape_asynch_io = true timed_statistics = true # always true #transactions = 250 # model S/A #transactions = 350 # model B #transactions = 450 # model C #transactions = 600 # model D transactions_per_rollback_segment = 10 # 10 for all

models user_dump_dest = /temp/oradata/ppay/udump utl_file_dir = * workarea_size_policy = manual

G.1 Obsolete parameters for Oracle 9i _average_dirties_half_life _lm_statistics allow_partial_sn_results always_anti_join always_semi_join arch_io_slaves b_tree_bitmap_plans backup_disk_io_slaves cache_size_threshold cleanup_rollback_entries close_cached_open_cursors compatible_no_recovery complex_view_merging cpu_count db_block_checkpoint_batch db_block_lru_extended_statisti db_block_lru_latches db_block_lru_statistics db_block_max_dirty_target db_file_simultaneous_writes delayed_logging_block_cleanout


186

discrete_transactions_enabled distributed_lock_timeout distributed_recovery_connectio fast_full_scan_enabled freeze_DB_for_fast_instance_re gc_defer_time gc_latches gc_lck_procs gc_releasable_locks gc_rollback_locks hash_multiblock_io_count instance_nodeset job_queue_interval job_queue_keep_connections large_pool_min_alloc lgwr_io_slaves lm_locks lm_procs lm_procs lm_ress lock_sga_areas log_block_checksum log_files log_simultaneous_copies log_small_entry_max_size ogms_home ops_admin_group ops_interconnects optimizer_percent_parallel optimizer_search_limit parallel_default_max_instances parallel_min_message_pool parallel_server_idle_time parallel_transaction_resource_ push_join_predicate row_cache_cursors sequence_cache_entries sequence_cache_hash_buckets shared_pool_reserved_min_alloc snapshot_refresh_interval snapshot_refresh_keep_connecti snapshot_refresh_processes sort_direct_writes sort_multiblock_read_count sort_read_fac


187

sort_spacemap_size sort_write_buffer_size sort_write_buffers spin_count temporary_table_locks text_enable use_ism


188

Rolling Back the PrePay Application

H.1 Rolling Back PrePay 10.0.1 If any serious problems occur after upgrading to PrePay 10.0.1 it may be necessary to roll back the application and database changes.

Coordinate the downtime for the rollback with the customer.

*** Beginning of DOWNTIME ***

1. Stop the PrePay application. su – ppadm stop_ppay

2. Rollback any patches according to the instructions in their README.TXT files.

3. Perform the following steps to roll back the application and database by executing Option 5 in the Prepay Upgrade menu. Type the following commands to start the upgrade script, replacing the string ‘<fromversion>’ with either ‘922’ or ‘100’, depending on whether you are upgrading from the PrePay 9.2.2 or 10.0 release. cd /<temparea>/work ./ppupgrade.ksh <fromversion>

4. Execute Option 4 in the Prepay Upgrade menu.


189

5. Review the rollback.YYYYMMDD error log file for any errors (where YYYYMMDD is the system date): /<temparea>/work/<version>/logs/rollback.YYYYMMDD

6. Type the following command to review the log file for any errors or warnings that may have occurred: more /<temparea>/work/<version>/logs/rollback.YYYYMMDD

7. To roll back database changes, restore the database from the backup taken prior to the upgrade.

H.2 Rolling Back Oracle from 9.2.0.6 to 9.2.0.4 Complete the following steps to downgrade your release 9.2.0.6 database to 9.2.0.4. Before starting any rollback activity, enable the logging of your session to a script file with an embedded date/timestamp after logging on as the oracle user.

1. Shutdown PrePay and Oracle.

2. Restore all Oracle software and data files using the backups created prior to the upgrade.

3. Startup Oracle and Prepay

H.3 Rolling Back from Distributed7 1.4.0.2 to 1.3.1.5

1. Login as ‘root’ su -

2. Run ebs_setrelease to activate back version 1.3.1.5 $EBSHOME/access/install/ebs_setrelease 1.4.0.2


190

Answer "Y" (yes) when asked to convert databases. 3. Run the ebs_setrelease command again to confirm which

software release is currently in use

Documents

PrePay in 10-0-1 Upgrade and Conversion Guide