Netcool® Performance Manager for Wireless

Document Version 0.3

Technology Pack - Extension

TIVOLI® NETCOOL® PERFORMANCE MANAGER FOR WIRELESS TECH PACK EXTENSION

Note: Before using this information and the product it supports, read the information in Notices on page 48.

This edition applies to Core Version 9.1.2, 9.2 and above of IBM® Tivoli® Netcool® Performance Manager for Wireless and to all subsequent releases and modifications until otherwise indicated in new editions.

© Copyright IBM Corp. 2008, 2011. All rights reserved.

US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

Table of Contents1. About this documentation ...................................................................... 6

1.1 Audience ............................................................................................. 6 1.2 Required Skills and Knowledge .......................................................... 6 1.3 GLOSSARY OF TERMS .................................................................... 6

2. Overview .................................................................................................. 7 2.1 Scope of Document ........................................................................... 7

3. General Design Guidelines .................................................................... 9 General Design Guidelines for Creating Extension Tech Pack: ............... 9

4. CASE A: Retrieve the necessary information from base techpack .. 10 Information from the installation package of the base techpack ........ 10 4.1.1. Metalayer - Main.xml ....................................................................... 10 4.1.2. Loadmaps – Datasource*.xml ....................................................... 11 4.1.3. Loadmaps – Loaderconfiguration*.xml ......................................... 12 4.2. Information from the PRS of the base techpack ............................. 12 4.2.1. Information of the reporting object ............................................... 12 4.2.2. Information of the target object ..................................................... 13 5. CASE A: Develop the extension pack using TPDK ............................ 15 5.1. Create New project ............................................................................ 15 5.2. Create Entry for Vendors ................................................................... 15 5.3. Create Entries for Subsystem ........................................................... 16 5.4. Create Entry for Counter Source ...................................................... 17 5.5. Create Entries for LIF Type ............................................................... 18 5.6. Create Entry for Ruleset .................................................................... 19 5.7. Create Entry for Techpack ................................................................. 20 5.8. Create Entry for Modules .................................................................. 20 5.9. Create the Reporting Object and Target Object .............................. 21 5.10. Run the Component Desginer ....................................................... 23

UG - 3

5.11. Create New Extension Package in TPDK ....................................... 24 6. CASE A: Packaging .............................................................................. 26 7. CASE A: Installation ............................................................................. 27 7.1. Installation of Base Techpack ........................................................... 27 7.2. Installation of New Extension Techpack .......................................... 27 8. CASE B: Retrieve the necessary information from base tech pack . 29 8.1. Information from the installation package of the base tech pack . 29 8.1.1. Metalayer - Main.xml ....................................................................... 29 8.1.2. Loadmaps – Datasource*.xml ....................................................... 30 8.1.3. Loadmaps – Loaderconfiguration*.xml ......................................... 31 8.2. Information from the PRS of the base techpack ............................. 31 8.2.1. Information of the target object ..................................................... 31 9. CASE B: Develop the extension pack using TPDK ............................ 33 9.1. Create New project ............................................................................ 33 9.2. Create Entry for Vendors ................................................................... 33 9.3. Create Entries for Subsystem ........................................................... 34 9.4. Create Entry for Counter Source ...................................................... 35 9.5. Create Entries for LIF Type ............................................................... 36 9.6. Create Entry for Ruleset .................................................................... 37 9.7. Create Entry for Techpack ................................................................. 38 9.8. Create Entry for Modules .................................................................. 38 9.9. Run the Counter Parser tool ............................................................. 39 9.10. Run the Component Desginer ....................................................... 40 9.11. Create New Extension Package in TPDK ....................................... 41 10. CASE B: Packaging ............................................................................ 42 11. CASE B: Installation ........................................................................... 43 11.1. Installation of Base Techpack ......................................................... 43 11.2. Installation of New Extension Techpack ........................................ 43 Appendix A - Customizing Stored Busy Hour definitions ................... 45 2 Appendix B - Notices and Trademarks ................................................ 48

UG - 5

1.About this documentation1.1 Audience

The target audience of this document is IBM support personnel, consultancy staff, business partners and customers who have responsibility for the installation of Technology Packs and/or reports.

1.2 Required Skills and KnowledgeThis guide assumes you are familiar with the following:

• IBM Tivoli Netcool Performance Manager (TNPM) product

• IBM TNPM TP Development Tool Kit (TPDK) product

• Windows (XP) operating system command shell

• Unix operating system command shell

This guide also assumes that you are familiar with your company’s network and with procedures for configuring, monitoring, and solving problems on your network.

1.3 GLOSSARY OF TERMS

TERM Term DefinitionTech Pack Technology PackTNPMW Tivoli® Netcool® Performance Manager for Wireless

VN Vendor NeutralVS Vendor Specific

GOM Global Object Model

2.Overview

2.1 Scope of Document

This document is the technical note that provides step by step procedure on creating extension tech pack. It gives a high level guideline on how to add KPIs into the existing objects through extension tech pack approach. The newly added KPIs will be stored in the new raw table. Addition to that, this new raw table will acts as an extension table to the existing raw table from the base tech pack.

This document is intended to cover the below scenarios:

1. Adding new KPIs into the existing Vendor Specific network object (Case A) - Scenario from Case A shall be used as an example to cover ‘Adding new KPIs into the existing Vendor Specific network object’ scope- Please refer Section 4 until Section 7 for the details

2. Adding new KPIs into the existing GOM network object (Case B) - Scenario from Case B shall be used as an example to cover ‘Adding new KPIs to the existing GOM network object’ scope- Please refer Section 8 until Section 11 for the details

CASE A:-

Objective:To add 2 new KPIs (in new KPI group) to the existing Vendor Specific network object.

Sample base tech pack: ZTE CDMA BSS V802004-3.0.0

2 KPIs will be added to a new KPI Group under the existing Vendor Specific network object. The purpose of the new KPI group is to act as extension of the target KPI Group.

Existing Vendor Specific network object: ZTE_DO_Board Target KPI group: PUB_BTS_CPU_USAGEThe 2 KPIs to be added are:-

1. NEW_12. NEW_2

New Extension KPI Group: TEST_NEW_Group_UXT

Before generating the extension tech pack, please have the following items ready:-1. Base tech pack package. E.g. vallent-vt-CDMA_Zte_BSS_V802004-3.0.0.tar.gz2. PRS of the base tech pack

UG - 7

Note: It is assumed that the gateway of the base tech pack has the LIF block and counters for the new KPIs.

CASE B:-

Objective:To add new KPIs (in new KPI group) to the existing GOM network object.

Sample base tech pack: GSMUMTS Huawei HLR V900R003C05 v1.0.0.0

In this base pack, we have the following 2 KPI groups:

KPI Group LIF BlockProcessor.Huawei.GSM.HDU_CPU_usage B150999067Processor.Huawei.GSM.SAU_CPU_usage B150998984

For the extension tech pack, it is intended to add 1 new KPI group called "C_CPU_usage" to the HLR object. This new KPI group "C_CPU_usage" contains the aggregated KPIs (at HLR level) from the above 2 KPI groups (total of 12 KPIs).

Existing GOM network object: HLR New Extension KPI Group: C_CPU_usage

Before generating the extension tech pack, please have the following items ready:-1. Base tech pack package. E.g. vallent-vt-

GSMUMTS_Huawei_HLR_V900R003C05-1.0.0.tar.gz2. PRS of the base tech pack

Note: Some configuration need to be done at the gateway in order to have the aggregated data at HLR level. For these scenario, the aggregated LIF block name as "B150999067_8984_Aggr" need to be defined. Later on, this block need to be mapped to the new KPI group "C_CPU_usage".

3.General Design Guidelines

3.1.General Design Guidelines for Creating Extension Tech Pack:

1. Where possible, avoid creating multiple KPI Groups for the same network objects, (i.e. Map all custom KPIs into a single custom KPI group for a network object).

Note: The above guide is to limit the number of custom tables created in the database. Too many custom tables created may have negative impact on performance.

2. Prefix the custom KPI Group Name with the string "C_" or suffix the custom KPI Group Name with the string " _UXT " .

3. Prefix the custom KPI Group Abbreviation with the string "C_" or suffix the custom KPI Group Abbreviation with the string "_UXT ".

4. Business Partners/Customers are advisable to contact IBM with regards the custom design. IBM be able to provide design review and approval.

Disclaimer:

1. The custom extension pack is not supported by IBM.

2. The custom extension pack is dependent on the original pack as prerequisite, as such the custom extension pack will need to be re-built when an upgrade of the original pack is formally released from IBM.

3. The custom extension pack is not Cognos enabled.

UG - 9

4.CASE A: Retrieve the necessary information from base techpack

4.1.Information from the installation package of the base techpack

1. Extract the base techpack (vallent-vt-CDMA_Zte_BSS_V802004-3.0.0.tar.gz) to get vallent-vt-CDMA_Zte_BSS_V802004.sw.

2. Extract the vallent-vt-CDMA_Zte_BSS_V802004.sw to get the content as follow:-

4.1.1.Metalayer - Main.xml

1. To get the reporting object name:-a. Go to the metalayer folder b. Open the main.xmlc. Find ‘<FileType Entity_Name’ in the xml file. E.g.

<FileType Entity_Name="ZTE_DO_BSSB"….

d. Reporting object: ‘ZTE_DO_BSSB’

2. To get the information of the base techpack module.

a. Find the ‘<ModuleInfo>’

i. Module Name: Value of the 'Module name'=>ZTE CDMA BSS

ii. Technology: Value of the 'technolody'=> CDMA

iii. Vendor: Value of the 'vendor'=> ZTE

iv. Subsystem: Value of the 'subsystem'=> BSS

v. Tech Pack Version: value of the techpack_version=> 3.0.0.0

vi. Module Version: value of the 'release' => 3.0.0

vii. Prerequisite Modules: value of the 'RequiredModule release'=> Neutral Core GoM

4.1.2. Loadmaps – Datasource*.xml

1. Go to the loadmaps folder and open the datasource*.xml file to find the values for following items:-a. Starttime

i. Find ‘<ColumnName>starttime</ColumnName>’

ii. Get the value in the <Expression> tag.iii. Starttime: utime(START_DATE & START_TIME,"%d %b %Y %R")

b. Endtime

i. Find <ColumnName>endtime</ColumnName>’

UG - 11

ii. Get the value in the <Expression> tagiii. Endtime: utime(END_DATE & END_TIME,"%d %b %Y %R")

c. Period mapping

i. Find <ColumnName>measurement_seconds</ColumnName>’ii. Get the value in the <Expression> tag

iii. Period mapping : PERIOD

4.1.3.Loadmaps – Loaderconfiguration*.xml1. Go to the loadmaps folder and open the loaderconfiguration*.xml file to find the values for

following items:-

a. DataSource name : Value of the ‘Datasource Name’ => ZTE CDMA BSSb. D/S version: Value of the ‘Version’ => V802004c. Ruleset Name : Value of the ‘Datasource Name’ + Value of the ‘Version’ => ZTE

CDMA BSS V802004d. Ruleset description: Value of the ‘Description’ => ZTE CDMA BSS V802004 loader

mappings

4.2. Information from the PRS of the base techpack

4.2.1.Information of the reporting object

1. Open the PRS of the base techpack.

2. Find the primary identifier of the reporting object ‘ZTE_DO_BSSB’

Primary Identifier of reporting object: BSC_Id

3. The primary identifier mapping of the reporting object is retrieved from the ‘Mapping’ column

Primary Identifier mapping of reporting object: DO_Global_Session_Setup.SERVER_ID&"-"&BSSB_ID

4.2.2.Information of the target object

1. Find the primary identifier of the target network object ‘ZTE_DO_BOARD’

Primary Identifier of target object : Board_Id

2. In some of the cases, there will be more than 1 LIF block found in the primary identifier mapping(see the snapshot above: LIF block found include PUB_MP_CPU_Usage, PUB_PP_CPU_Usage and PUB_BTS_CPU_Usage).

3. Find the mapping which belongs to the LIF block that populate to the extension table, in this case, block ‘PUB_BTS_CPU_Usage’.

a. To find the mapping, open the PRS, look for the statistics of ‘PUB_BTS_CPU_USAGE’

b. Notes that LIF block ‘PUB_BTS_CPU_Usage’ is found in the “Derivation” column. Thus, ‘PUB_BTS_CPU_Usage’ is the LIF block that populate to the ‘PUB_BTS_CPU_USAGE’ KPI group.

c. Primary Identifier mapping of the target object : PUB_BTS_CPU_Usage.SERVER_ID&"-"&BSSB_ID&"-"&SYSTEM_ID&"-"&SUBSYSTEM_ID&"-"&UNIT_ID&"-"&SUNIT_ID&"-"&BOARDNAME&"-"&BOARDTYPE

UG - 13

5.CASE A: Develop the extension pack using TPDK

5.1. Create New project1. Open the TPDK2. Create New Project by going to File>New Project

5.2.Create Entry for Vendors1. In the project that created, go to File>Vendor2. If the vendor entry is available, proceed to next section, create the vendor entry for the project

otherwise.

UG - 15

5.3. Create Entries for Subsystem1. In the ‘vendor’ windows, select the correct vendor name. Click on the ‘Subsystem’ button.

2. In the Subsystem window, choose the correct subsystem name. If not available, create a new subsystem and create the entry in the ‘Versions’ and ‘Interfaces’.

3. Save the Subsystem entry.

5.4. Create Entry for Counter Source1. Go to the Definitons>Vendors.2. Select the correct vendor name, click on the ‘Counter Source’ button to open the ‘Counter

Source’ window

UG - 17

3. Select the appropriate Subsystem and Version value from the drop down list.4. Insert the Source Name: <techpack>_UXT_source5. Save the entry.

5.5. Create Entries for LIF Type

1. Create the new LIF Type for the subsystem entry that created 2. Click on the the LIF Type button to open the LIF Type window.3. Insert the value into each of the column of the LIF Type window

a. LIF Type Name : <techpack>_UXT_liftypeb. Select the appropriate value from the drop down list of the column of

i. Technologyii. Subsystem

iii. Minimum Versioniv. Interfacev. Maximum Version

vi. Reporting Object : This is the reporting object name that retrieved from base techpack package.

vii. Start Time Mapping: This is the Starttime value that retrieved from base techpack package

viii. End Time Mapping: This is the Endtime value that retrieved from base techpack package

ix. Period Mapping: This is the Period mapping value that retrieved from base techpack package

4. Save the LIF Type.

5.6. Create Entry for Ruleset1. Go to Definitions> Rulesets2. Creating a new entry for Ruleset

a. Ruleset ID : A unique dummy valueb. Datasource Name: Datasource name retrieved from the base techpack

=> ZTE CDMA BSSc. D/S version: <D/S version retrieved from the base techpack>Ext. Ext is concatenated

to the D/S version of the base techapck. => V802004Ext

d. D/S Type : Custome. Ruleset Name: Ruleset name retrieved from the base techpack

=> ZTE CDMA BSS V802004

UG - 19

f. Description: Add the word ‘Extension’ into the Description retrieved from base techpack => ZTE CDMA BSS V802004 Extension loader mappings

5.7. Create Entry for Techpack1. Go to Definitions>Techpack2. Create a new entry into the Tech pack name if the required tech pack name is not available in

the Techology Packs window

5.8. Create Entry for Modules

1. In the Go Techology Packs window, select the required tech pack name.2. Click on the Modules button to open the Modules windows.3. Create the new module based on the value retrieved from the base techpack.

a. Module Name: Value of the 'Module name' concatenated with ‘Ext’=>ZTE CDMA BSS Ext

b. Technology: Value of the 'technology' from base techpack=> CDMA

c. Vendor: Value of the 'vendor' from base techpack=> ZTE

d. Subsystem: Value of the 'subsystem' from base techpack=> BSS

e. Vendor version: Select the extension pack vendor version from drop down listf. Tech Pack Version: value of the techpack_version from base techpack

=> 3.0.0.0g. Module Version: value of the 'release' from base techpack

=> 3.0.0h. Compatible Version: Optional(leave empty)i. Prerequisite Modules: Based on the value of the 'RequiredModule release' from base

techpack, select from the drop down list.=> Neutral Core GoM (1.0)

5.9. Create the Reporting Object and Target Object1. Go to Definitions > Network Object2. Create a new object using the name of Reporting Object, ZTE_DO_BSSB, retrieved from the

base techpack package. 3. Create a new object using the name of the Target Object, ZTE_DO_Board.

UG - 21

4. Create the primary key in the Attributes of the ZTE_DO_BSSB by entering the value retrieved from the Base techpack and the PRS.

5. Create the primary key in the Attributes of the ZTE_DO_Board by entering the value retrieved from the Base techpack and the PRS.

6. For target object ZTE_DO_Board, create the KPI group and the KPI entries.

7. Note the extension KPI group name should be in the format of <original kpi group name>_EXT.

5.10. Run the Component Desginer 1. Run the component designer to create the raw table and its entries.

UG - 23

5.11.Create New Extension Package in TPDK1. In the TPDK, go to Definitions>Packages2. Create a new extension package as below

3. For the package created, perform the following to include or exclude the required packaging item by ‘check’ or ‘uncheck’ the items selected

a. Ruleset: check the ruleset created for the new extension pack

b. Report: Ignore(no report)c. Raw Tables: Check only the new raw table created for this extension packd. NC Tables: Uncheck all the NC tablese. LIF Types: Check only the new LIF Types created for this extension packf. KPIs: Check only the 2 new KPIs created for this extension packg. Coutner Sources: Check only the new counter source created for this extension packh. Busy Hours: Ignore(no busy hour)i. Attributes: Uncheck all the attributesj. Alarms: Ignore(no alarm)

UG - 25

6.CASE A: PackagingOnce the new extension tech pack package is created in the TPDK, engineer may proceed to generate the extension tech pack package, <Extension Tech_Pack_Name>.tar.gz.

7.CASE A: Installation7.1. Installation of Base Techpack

Install the base techpack by following the instruction in the release notes of the base techpack.

7.2. Installation of New Extension Techpack

1. Copy the Extension Tech Pack to $WMCROOT/admin/techpacks/packages.

cp <file_directory>/<Extension pack>.tar.gz $WMCROOT/admin/techpacks/packages

2. Execute the following command:

$WMCROOT/admin/common/install/scripts/deploy_techpacks -wmcr /appl/virtuo

-techpacks <Extension pack>.tar.gz

3. Check if Extension Tech Pack has the same datasource attributes (i.e. Name and Version), Tech Pack attribute (i.e. Name) and loader configuration attribute (i.e. Name) as the Base Tech Pack.

In the case where there are 2 loadmaps available in the Base Tech Pack, use the Performance loadmap for the steps below.

a. Get the above mentioned attributes from datasource_<TP_Ruleset_Name_Definition >.xml and loaderconfiguration_<TP_Ruleset_Name_Definition>.xml for Extension Tech Pack.

cd /appl/virtuo/admin/techpacks/<Extension Tech_Pack_Name>/<Module_Version>/loadmaps/<Tech_Pack_Name>/

grep 'DataSource Name' datasource_<TP_Ruleset_Name_Definition>.xml

grep 'Techpack Name' datasource_<TP_Ruleset_Name_Definition>.xml

b. Get the above mentioned attributes from datasource_<TP_Ruleset_Name_Definition>.xml and loaderconfiguration_<TP_Ruleset_Name_Definition>.xml for Base Tech Pack.

cd /appl/virtuo/admin/techpacks/<Base Tech_Pack_Name >/<Module_Version>/loadmaps/<Tech_Pack_Name>/

grep 'DataSource Name' datasource_<TP_Ruleset_Name_Definition>.xml

grep 'Techpack Name' datasource_<TP_Ruleset_Name_Definition>.xml

4. If the loader configuration and datasource are different, please change the Base techpack loadmap to match the Extension techpack loadmap. This is to ensure both loadmaps are control by single loader process.

Execute the following SQL Commands:

UG - 27

LC_DATASOURCE

update lc_datasource set datasource_name = '<Extension pack datasource name>' where datasource_id ='<ID for the Base Tech Pack>';COMMIT;

update lc_datasource set datasource_version = '<Extension datasource version>'where datasource_id ='<ID for the Base Tech Pack>';COMMIT;

update lc_datasource set techpack_name = '<Extension techpack name>' where datasource_id ='<ID for the Base Tech Pack>';COMMIT;

5. Check to ensures that the above changes are made using the following SQL commands:

select * from lc_datasource where datasource_id ='<ID for the Base Tech Pack>';

6. Install the Tech Pack using the following command.

techpack_admin -a

8.CASE B: Retrieve the necessary information from base tech pack8.1.Information from the installation package of the base tech pack

1. Extract the base tech pack (vallent-vt-GSMUMTS_Huawei_HLR_V900R003C05-1.0.0.tar.gz) to get vallent-vt-GSMUMTS_Huawei_HLR_V900R003C05.sw.

2. Extract the vallent-vt-GSMUMTS_Huawei_HLR_V900R003C05.sw to get the content as follow:-

8.1.1.Metalayer - Main.xml

1. To get the information of the base tech pack module.

a. Find the ‘<ModuleInfo>’

i. Module Name: Value of the 'Module name'=> Huawei GSM HLR

ii. Technology: Value of the 'technolody'=> GSM

iii. Vendor: Value of the 'vendor'=> Huawei

iv. Subsystem: Value of the 'subsystem'

UG - 29

=> HLRv. Tech Pack Version: value of the techpack_version

=> 1.0.0.0vi. Module Version: value of the 'release'

=> 1.0.0vii. Prerequisite Modules: value of the 'RequiredModule release'

=> Neutral Core GoM=> Neutral GSM BSS/NSS GOM

8.1.2. Loadmaps – Datasource*.xml

1. Go to the loadmaps folder and open the datasource*.xml file to find the values for following items:-

a. Starttime

i. Find ‘<ColumnName>starttime</ColumnName>’

ii. Get the value in the <Expression> tag.iii. Starttime: utime(StartDate & StartTime,"%Y-%m-%d %R")

b. Endtime

i. Find <ColumnName>endtime</ColumnName>’

ii. Get the value in the <Expression> tagiii. Endtime: utime(StartDate & StartTime,"%Y-%m-%d %R") + Period

c. Period mapping

i. Find <ColumnName>measurement_seconds</ColumnName>’

ii. Get the value in the <Expression> tagiii. Period mapping : Period

8.1.3.Loadmaps – Loaderconfiguration*.xml

1. Go to the loadmaps folder and open the loaderconfiguration*.xml file to find the values for following items:-

a. DataSource name : Value of the ‘Datasource Name’ => Huawei GSM HLRb. D/S version: Value of the ‘Version’ => V900R003C05c. Ruleset Name : Value of the ‘Datasource Name’ + Value of the ‘Version’ =>

Huawei GSM HLR V900R003C05d. Ruleset description: Value of the ‘Description’ => Huawei GSM HLR

V900R003C05 loader mappings

8.2. Information from the PRS of the base techpack

8.2.1.Information of the target object

1. Open the PRS of the base tech pack. 2. Find the primary identifier of the target network object ‘HLR’

UG - 31

Primary Identifier of target object : HLR_Id

3. Primary Identifier mapping of the target object : HLR_Id

9.CASE B: Develop the extension pack using TPDK

9.1. Create New project1. Open the TPDK2. Create New Project by going to File>New Project

9.2.Create Entry for Vendors1. In the project that created, go to File>Vendor2. If the vendor entry is available, proceed to next section, create the vendor entry for the

project otherwise.

UG - 33

9.3. Create Entries for Subsystem1. In the ‘vendor’ windows, select the correct vendor name. Click on the ‘Subsystem’

button.

2. In the Subsystem window, choose the correct subsystem name. If not available, create a new subsystem and create the entry in the ‘Versions’ and ‘Interfaces’.

3. Save the Subsystem entry.

9.4. Create Entry for Counter Source1. Go to the Definitons>Vendors.2. Select the correct vendor name, click on the ‘Counter Source’ button to open the

‘Counter Source’ window

UG - 35

3. Select the appropriate Subsystem and Version value from the drop down list.4. Insert the Source Name: <techpack>_UXT_source5. Save the entry.

9.5. Create Entries for LIF Type

1. Create the new LIF Type for the subsystem entry that created 2. Click on the the LIF Type button to open the LIF Type window.3. Insert the value into each of the column of the LIF Type window

a. LIF Type Name : <techpack>_UXT_liftypeb. Select the appropriate value from the drop down list of the column of

i. Technologyii. Subsystem

iii. Minimum Versioniv. Interfacev. Maximum Version

vi. Reporting Object : This is the reporting object name that retrieved from base tech pack package.

vii. Start Time Mapping: This is the Starttime value that retrieved from base tech pack package

viii. End Time Mapping: This is the Endtime value that retrieved from base tech pack package

ix. Period Mapping: This is the Period mapping value that retrieved from base tech pack package

4. Save the LIF Type.

9.6. Create Entry for Ruleset1. Go to Definitions> Rulesets2. Creating a new entry for Ruleset

a. Ruleset ID : A unique dummy valueb. Datasource Name: Datasource name retrieved from the base techpack

=> Huawei GSM HLRc. D/S version: <D/S version retrieved from the base techpack>Ext. Ext is concatenated

to the D/S version of the base techapck. => V900R003C05Ext

UG - 37

d. D/S Type : Custome. Ruleset Name: Ruleset name retrieved from the base techpack

=> Huawei GSM HLR V900R003C05f. Description: Add the word ‘Extension’ into the Description retrieved from base

techpack => Huawei GSM HLR V900R003C05 Extension loader mappings

9.7. Create Entry for Techpack1. Go to Definitions>Techpack2. Create a new entry into the Tech pack name if the required tech pack name is not available in

the Techology Packs window

9.8. Create Entry for Modules

1. In the Techology Packs window, select the required tech pack name.2. Click on the Modules button to open the Modules windows.3. Create the new module based on the value retrieved from the base techpack.

a. Module Name: Value of the 'Module name' concatenated with ‘Ext’=>Huawei GSM HLR Ext

b. Technology: Value of the 'technology' from base techpack=> GSM

c. Vendor: Value of the 'vendor' from base techpack=> Huawei

d. Subsystem: Value of the 'subsystem' from base techpack=> HLR

e. Vendor version: Select the extension pack vendor version from drop down listf. Tech Pack Version: value of the techpack_version from base techpack

=> 1.0.0.0g. Module Version: value of the 'release' from base techpack

=> 1.0.0h. Compatible Version: Optional(leave empty)i. Prerequisite Modules: Based on the value of the 'RequiredModule release' from base

techpack, select from the drop down list.=> Neutral Core GoM (1.0)

=> Neutral GSM BSS/NSS GOM (1.0)

9.9. Run the Counter Parser tool1. Develop a counter parser CSV file to load into the TPDK. Attached here is an example file

used for the development of this document procedure.

2. Launch the Counter Parser from the Tools Menu.3. Select the Import to Counter Source option.4. Select the appropriate Technology.5. Navigate to choose your CSV file

UG - 39

9.10. Run the Component Desginer 1. Run the component designer to create the raw table and its entries.

9.11.Create New Extension Package in TPDK1. In the TPDK, go to Definitions>Packages2. Create a new extension package as below

3. For the package created, perform the following to include or exclude the required packaging item by ‘check’ or ‘uncheck’ the items selected

a. Ruleset: check the ruleset created for the new extension pack

b. Report: Ignore(no report)c. Raw Tables: Check only the new raw table created for this extension packd. NC Tables: Uncheck all the NC tablese. LIF Types: Check only the new LIF Types created for this extension packf. KPIs: Check only the 12 new KPIs created for this extension packg. Coutner Sources: Check only the new counter source created for this extension packh. Busy Hours: Ignore(no busy hour)i. Attributes: Uncheck all the attributesj. Alarms: Ignore(no alarm)

UG - 41

10.CASE B: PackagingOnce the new extension tech pack package is created in the TPDK, engineer may proceed to generate the extension tech pack package, <Extension Tech_Pack_Name>.tar.gz.

11.CASE B: Installation11.1. Installation of Base Techpack

Install the base techpack by following the instruction in the release notes of the base techpack.

11.2. Installation of New Extension Techpack

1. Copy the Extension Tech Pack to $WMCROOT/admin/techpacks/packages.

cp <file_directory>/<Extension pack>.tar.gz $WMCROOT/admin/techpacks/packages

2. Execute the following command:

$WMCROOT/admin/common/install/scripts/deploy_techpacks -wmcr /appl/virtuo

-techpacks <Extension pack>.tar.gz

3. Check if Extension Tech Pack has the same datasource attributes (i.e. Name and Version), Tech Pack attribute (i.e. Name) and loader configuration attribute (i.e. Name) as the Base Tech Pack.

In the case where there are 2 loadmaps available in the Base Tech Pack, use the Performance loadmap for the steps below.

a. Get the above mentioned attributes from datasource_<TP_Ruleset_Name_Definition >.xml and loaderconfiguration_<TP_Ruleset_Name_Definition>.xml for Extension Tech Pack.

cd /appl/virtuo/admin/techpacks/<Extension Tech_Pack_Name>/<Module_Version>/loadmaps/<Tech_Pack_Name>/

grep 'DataSource Name' datasource_<TP_Ruleset_Name_Definition>.xml

grep 'Techpack Name' datasource_<TP_Ruleset_Name_Definition>.xml

b. Get the above mentioned attributes from datasource_<TP_Ruleset_Name_Definition>.xml and loaderconfiguration_<TP_Ruleset_Name_Definition>.xml for Base Tech Pack.

cd /appl/virtuo/admin/techpacks/<Base Tech_Pack_Name >/<Module_Version>/loadmaps/<Tech_Pack_Name>/

grep 'DataSource Name' datasource_<TP_Ruleset_Name_Definition>.xml

grep 'Techpack Name' datasource_<TP_Ruleset_Name_Definition>.xml

4. If the loader configuration and datasource are different, please change the Base techpack loadmap to match the Extension techpack loadmap. This is to ensure both loadmaps are control by single loader process.

Execute the following SQL Commands:

UG - 43

LC_DATASOURCE

update lc_datasource set datasource_name = '<Extension pack datasource name>' where datasource_id ='<ID for the Base Tech Pack>';COMMIT;

update lc_datasource set datasource_version = '<Extension datasource version>'where datasource_id ='<ID for the Base Tech Pack>';COMMIT;

update lc_datasource set techpack_name = '<Extension techpack name>' where datasource_id ='<ID for the Base Tech Pack>';COMMIT;

5. Check to ensures that the above changes are made using the following SQL commands:

select * from lc_datasource where datasource_id ='<ID for the Base Tech Pack>';

6. Install the Tech Pack using the following command.

techpack_admin -a

Appendix A - Customizing Stored Busy Hour definitions

(Reference from TNPM_1.3.1_Administration_Guide_Wireless_Component.pdf- page 160-162)

UG - 45

UG - 47

2 Appendix B - Notices and Trademarks

This appendix contains the following:

• Notices

• Trademarks

Notices

This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in all countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user’s responsibility to evaluate and verify the operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not grant you any license to these patents. You can send license inquiries, in writing, to:

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk NY 10504-1785U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property LicensingLegal and Intellectual Property LawIBM Japan Ltd.1623-14, Shimotsuruma, Yamato-shiKanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION “AS IS” WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk.

IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose of enabling: (i) the exchange of information between independently created programs and other programs (including this one) and (ii) the mutual use of the information which has been exchanged, should contact:

IBM Corporation2Z4A/10111400 Burnet RoadAustin, TX 78758U.S.A.

Such information may be available, subject to appropriate terms and conditions, including in some cases, payment of a fee.

The licensed program described in this document and all licensed material available for it are provided by IBM under terms of the IBM Customer Agreement, IBM International Program License Agreement or any equivalent agreement between us.

Any performance data contained herein was determined in a controlled environment. Therefore, the results obtained in other operating environments may vary significantly. Some measurements may have been made on development-level systems and there is no guarantee that these measurements will be the same on generally available systems. Furthermore, some measurements may have been estimated through extrapolation. Actual results may vary. Users of this document should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of those products.

All statements regarding IBM’s future direction or intent are subject to change or withdrawal without notice, and represent goals and objectives only.

This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental.

If you are viewing this information softcopy, the photographs and color illustrations may not appear.

UG - 49

TrademarksIBM, the IBM logo and ibm.com are trademarks of International Business Machines Corp., registered in many jurisdictions worldwide. Other product and service names might be trademarks of IBM or other companies. A current list of IBM trademarks is available on the Web at "Copyright and trademark information" at www.ibm.com/legal/copytrade.shtml.

Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.

Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

UNIX is a registered trademark of The Open Group in the United States and other countries.

Other company, product or service names may be trademarks or service marks of others.

IBM®

Printed in the U.S.A.