Professional Documents
Culture Documents
Copyright 2008 AIRCOM International All rights reserved ADVANTAGE, ASSET, CONNECT, DATASAFE, DIRECT ENTERPRISE, NEPTUNE, ARRAYWIZARD, OPTIMA, OSSEXPERT, and WEBWIZARD are recognised trademarks of AIRCOM International. Other product names are trademarks of their respective companies. Microsoft Excel , .NET, Microsoft Office, Outlook , Visual Basic Windows, Windows XP, Windows Vista and Word are trademarks of the Microsoft Corporation. This documentation is protected by copyright and contains proprietary and confidential information. No part of the contents of this documentation may be disclosed, used or reproduced in any form, or by any means, without the prior written consent of AIRCOM International. Although AIRCOM International has collated this documentation to reflect the features and capabilities supported in the software products, the company makes no warranty or representation, either expressed or implied, about this documentation, its quality or fitness for particular customer purpose. Users are solely responsible for the proper use of ENTERPRISE software and the application of the results obtained. An electronic version of this document exists. This User Reference Guide finalised on 12 September 2008. Refer to the Online Help for more information. This User Reference Guide prepared by: AIRCOM International Ltd Cassini Court Randalls Research Park Randalls Way Leatherhead Surrey KT22 7TW Telephone: Support Hotline: Fax: Web: +44 (0) 1932 442000 +44 (0) 1932 442345 +44 (0) 1932 442005 www.aircominternational.com
Contents
Explanation of Symbols 7 9
12
13
14
14 15
About a Project Adding a New Project Checking the Database About Updating Project Properties
Updating General and Database Server Machine Properties Updating Mediation Machines, LUNS, and Summary Definitions Properties
16 16 22 23
24 25
Uploading Project Information Defining Global Parameters Opening the Project Working Folder Exporting a Project About Interface Workbooks
Using the Interface Definition button About File Format Information About CFG Table Information About Raw Table Information About Counter Group Information About Parsed Counter Information About Loaded Counter Information About CFG Fields Information About Hierarchy Chain Information About Hierarchy Field Information About Default Element Level Alias Information About Summary Definition Information About BusyHour Definition Information About BusyHour Table Information About BusyHour Summary Information
27 27 28 28 29
30 32 33 34 34 35 36 38 39 39 40 40 41 42 43
44
44 45 46 46 47 48 49 50
Page 5
Power Tools
Generating a 6.1 Interface Template from Existing Sources Merging Two Interface Templates Reporting on Differences Between Two Interface Templates Removing a File Version/Format from an Existing Interface Template Migrating 1.4.x Interface Templates to the 6.1 Format Displaying an Existing Interface Template
51
51 56 57 58 58 59
Adding an Interface Workbook to a Project Validating an Interface Workbook Template Uploading an Interface to the Database Activating an Interface
Generating a Decommissioning Report
60 61 62 64
66
Reusing PRIDs Viewing INI Files Exporting an Interface File Refreshing the Interface Name Troubleshooting
68 70 71 71 72
Index
75
Page 6
Explanation of Symbols
Throughout this guide, where appropriate, some symbols are used to highlight particular pieces of text. Three different symbols are in use, and are explained as follows:
Symbol Brief Description Note Tip Warning or Important Full Description Signifies text that should be noted or carefully considered. Signifies text that may help you do something in an easier or quicker way. Signifies text that is intended as a warning or something important.
Page 7
Page 8
CHAPTER 1
You can carry out the first three tasks offline but you must carry out the last two tasks online.
Page 9
The tool can perform the following functions: Automate the creation of new vendor interface schemas Create INI files for Combiner (if used), Validator and Loader Create INI files for Directory Maintenance, Process Monitor, Directory Maintenance Loader and Log loader Populate network configuration for Loader tables Populate OPTIMA Summary tables with network configuration for Summaries, Busy Hour definitions and Busy Hour Summaries Create the vendor tables (Raw/Summary/BH Definition/BH Summary tables) and associated tablespaces Create scripts to install the INI files Create scripts to install the directories on the mediation and database servers Configure the table maintenance, tablespace maintenance Allow an interface to be configured in an Excel workbook, and then reused at different customer sites from a central repository
Page 10
However, the tool does have the following limitations: Does not configure the FTP or Parser components Limited to single user (only one installer can work on a project/database at one time) Does not configure OPTIMA Client Reports/Modules/KPIs/Alarms Does not create tables in the AIRCOM or GLOBAL schemas Project working directory and database connection details must be modified for each user
In This Section
About the Created Interface Installing the OPTIMA Installation Tool About a Project Adding a New Project Checking the Database About Updating Project Properties Uploading Project Information Defining Global Parameters Opening the Project Working Folder Exporting a Project About Interface Workbooks Creating an Interface Workbook Power Tools Adding an Interface Workbook to a Project Validating an Interface Workbook Template Uploading an Interface to the Database Activating an Interface Reusing PRIDs Viewing INI Files Exporting an Interface File Refreshing the Interface Name Troubleshooting 12 14 16 16 22 23 27 27 28 28 29 44 51 60 61 62 64 68 70 71 71 72
Page 11
Page 12
Page 13
Ensure that the AIRCOM, GLOBAL and LOGS schemas exist. Ensure that the Common Scripts (SCR-GEN-001-GEN-826) is installed. Ensure that the OSS_Logging Package (SCR-GEN-001-GEN-828) is installed. Ensure that the OSS_Maintenance Package (SCR-GEN-001-GEN-827) is installed. Ensure that the OPTIMA_Summary Package is installed.
Page 14
Page 15
About a Project
A project contains information about the local OIT root directory, database server connection, mediation server directories, logical units (LUNS) for database tablespaces. Everytime you open the OPTIMA Installation Tool, you will need to specify a project. There can only be one project for the entire OIT schema. The project information can be updated using the Project Properties dialog box. It is not possible for two people to work on the same project concurrently because the OIT root directory is user specific (set by default to My Documents\OIT). If a new user wishes to use the same project, they must redefine the OIT root directory for their local Windows PC.
Page 16
2 3 4 5 6
In the Project Name box, type a name for the project. In the OIT Root Directory path, browse to the required folder on your local PC. In the Description box, type a description for the project. Click Next. Specify the Database Connection Details: In the Connect Using drop-down list, select the method you want to use for connection In the Database drop-down list, select the project database In the User/Schema box, type the user or schema In the Password box, type your password
Page 17
7 8
Click Test Connection to test the database connection. If the connection is successful, click Next. You cannot proceed until the test is successful. (At this stage, a check is made to record whether the database is ASM or nonASM.) The project information is added to the database when you log in to the database and upload the project.
Specify the Database Server Machine details: In the Machine ID box, the machine ID is always 0 In the Platform drop-down list, specify the type of platform corresponding to the database operating system In the External (Loader Directory), type the name of the directory for the external mapping path to the mediation machine
Page 18
10 Click Next. 11 Specify the Mediation Server Machines details: In the Machine ID drop-down list, specify the ID of the machine In the Platform drop-down list, specify the platform corresponding to the mediation machine operating system In the OPTIMA (root) Directory box, type the name of the OPTIMA root directory (absolute path) In the INI File Directory, type the name of the directory for the INI files In the External (Loader) Directory, type the name of the directory for the external data files In the Local PRID Directory, type the name of the PRID directory The last three directory names can be either relative paths to the OPTIMA root path, or absolute paths.
Page 19
12 Click Add to add all the details for a particular machine ID to the grid. 13 Click Next. 14 Specify the LUNS details. The four defaults of System, Data, Index and Temporary automatically appear in the grid. If required, you can modify the LUN Path box and LUN Capacity by specifying new values and clicking Modify. If you need to add more LUN Types, click Add and then modify the LUN Type, LUN Path and LUN Capacity as appropriate. If the database is ASM, the LUN Path is inactive.
15 In the Datafile edit box, specify a Maximum Size which represents the maximum individual size of an Oracle Datafile. If more than one user is configuring OPTIMA using the OPTIMA Installation Tool, they must ensure that this size is the same for each user.
Page 20
16 Click Next. 17 Specify the summary definitions details: In the Definition ID box, type the ID of the definition In the Definition Name box, type the name of the definition In the Definition Group Time box, type the group time of the definition In the Definition Based On box, type the time parameter on which the definition is based on In the Definition Where Clause box, type the where clause of the definition
18 Click Add to add all the summary definition details to the grid. 19 Click Finish. You can also modify or delete information. To do this: Select the row in the grid that you want to modify or delete. Click Modify or Delete.
Page 21
Page 22
It provides information about the following: Release Number OIT GUI Patch Build Info Source Contorl Revision In case of generic errors, a short description of the error is explained. If there is an incompatible module, then that module is also highlighted in red along with the error message. If you encounter an error, please contact AIRCOM International for support.
Page 23
Page 24
4 5
Make modifications to the properties which you want to update. Click OK to save your modifications. -orClick Apply to apply your modifications. -orClick Cancel to exit.
Page 25
4 5 6
Select the row from the grid that you want to modify and make modifications to the required properties. Click Modify. Click OK to save your modifications. -orClick Apply to apply your modifications. -orClick Cancel to exit.
Page 26
Specify the following details: Database TNS Name Loader User Loader User Password
The current three settings included are the connection details for the Loader client to connect to the Loader Package in the database. This applies to Loader Clients on all mediation devices.
Page 27
Exporting a Project
To export a project: 1 2 Select the project, right-click and click Export Project. In the Export Project dialog box that opens, click Browse to select the location where you want to export the selected project.
3 4
In the Save As window, specify a name for the project and click Save. Click OK. The project is exported in a zip file.
Page 28
The following keys are defined in the Excel sheet: PK = Primary Key FK = Foreign Key WFK = Weak Foreign Key, either it is partially matched or is not enforced
Page 29
Summary and Busy Hours When you click this button, only the following worksheets are displayed in the spreadsheet: Summary Definition BusyHour Definition BusyHour Tables BusyHour Summary Hierarchy and Config When you click this button, only the following worksheets are displayed in the spreadsheet: CFG Tables CFG Fields Hierarchy Chains Hierarchy Fields Default Element Level Alias Interface Dictionary When you click this button, only the following worksheets are displayed in the spreadsheet: FileFormats Raw Tables Counter Groups Parsed Counters Loaded Counters KPIs and STD Reporting When you click this button, only the following worksheets are displayed in the spreadsheet. This feature is not yet implemented.
Page 30
Description When you click this button, all the worksheets reappear in the spreadsheet.
Notes: Oracle object names are not case sensitive and any object names generated from the Interface Menu screen properties in the template can be considered in UPPERCASE. For example, Vendor=Ericsson, Domain=Utran will generate a Vendor Schema in Oracle = Ericsson_UTRAN. Directory paths and file names in Unix are case sensitive, while directory paths and file names in Windows are not. For example, P001110001.ini and P001001001.ini refer to different files in UNIX but refer to the same file in Windows.
Page 31
Number of days that the OMC/NEM stores the files. No It is a numeric value. Regular expression that describes the raw filename. This is used for FTP and Combiner configuration. The format of the date in the filename. Used by Combiner to combine files based on similar filename. However, this filename may have a distinguishing feature that needs to be removed. This is a regular expression that if matched, it is removed from the filename before combining. Default = 1. This sets the number of headers that will be loaded for this file type. No
*.CSV
No No
YYYYMMDD A
No
Page 32
No
Yes/No
Element Level
Yes
CELL
History
No
Yes/No
Default HierarchyID
WFK. Default ID of the hierarchy.This field No contains a hierarchy of all the hierarchy elements specific to a particular configuration table. For example, In a CELLCFG table, we might have a hierarchy of BSC and Cell. The chain is this case would be B_C where B is BSC and C is Cell. The value defined in the default hierarchy ID should correspond to the 'Hierarchy Unique ID' column in the Hierarchy Chains tab of the Interface Workbook Excel sheet.
B_C
Page 33
FK[CFG Table]. The parent Configuration Table for this Yes raw table. All tables should have a CFG table that will update information automatically for things like maximum timestamp that the Object has data for. The 'Add CFG Tables' button in the CFG Tables worksheet uses the information in this column to autopopulate the list of CFG tables. Indicates whether this table needs to be created. If this table has multiple counter groups loading to it, and you want to configure combiner before loading, then the field value should be 'Yes'. Expected granularity is specified in minutes. Yes No
CELLCFG
Enabled Combiner
Yes/No Yes/No
Yes
60
Counter Group
CELLTRAFFIC
CGroup Alias
CELLTRAF
Enabled FileFormatID(s)
Yes/No CSV-G3
Page 34
You must ensure that: The first data row of the worksheet has the value VARCHAR2 for the Type field, and a size is specified in the Dateformat/Size field. The Dateformat/Size field is set to 0 when the Type field has value NUMBER for the first time in the worksheet.
Field
Counter Group
Mandatory
Yes
Example
CELLTRAFFIC
PK. The output from a parser will contain a headerline. This field must match the name in the header for the column in the parser output. This is used to configure the validator INI and Loader_File_Mappings table.
Yes
Optima Alias
When loading a file to the EXTERNAL table in No oracle, the field name must be less than 30 characters. This alias us used to standardise naming conventions to use the same loader for certain fields. If 'null', then the header is assumed for the column name in the EXTERNAL table. [VARCHAR2/DATE/NUMBER]. This indicates the type of the field as it is to be loaded into the external table. Yes
SDCCH_Call Drop
Type
VARCHAR2
Dateformat/Size
If type = VARCHAR2, then this sets the length of the Not Mandatory if 50 field in bytes. If type = DATE, then this describes the Type = Number ORACLE dateformat used to change the field from text into a DATE number. If Type=Date, then format of the date would be YYYYMMDDHH24MISS. Determines the order of the columns for Validator. Loader expects the columns to be in this order after validation. It is a numeric field. Indicates whether this column exists in the counter group for this install. Yes 30
Order
Enabled FileFormatID(s)
Yes Yes
Yes/No CSV-G3
Page 35
Field
Combiner Type
Description
[<null> / KEY / REMOVE / UNIQUE]. When combining this counter group, the field can have any of the following values: Key: It must match with other counter groups. Remove: While it exists in the parser output, it must be removed when combined. Unique: The field exists in multiple counter groups and must be kept for each counter group separately.
Mandatory
No
Example
UNIQUE
Page 36
Field Type
Description This classifies the column in terms of type of information stored in the column. It can have the following values: CT: Normal Counter PI: Primary Identifier. All fields that form part of the primary key should be set to either GPI or PI. Only one field can be classified as GPI. GPI: Grouping Primary Identifier. This field is used to determine the group element to group the summaries. For example, a table with a primary key of DateTime, BSC, and Cell would have GPI set to BSC and PI set to Cell. DT: Primary Date field DC: Delta Counter. This is used when the counter value is calculated by subtracting sequential counter values. Therefore, the original counter contains cumulative values. AC: Array Counter. This is used when a counter contains multiple subcounters within a single counter value. For example, it will be 3_5_6 if view is created giving access to individual sub counters. OI: Other Identifer. It indicates that it is a string or number that is not a measurement counter that helps identify information about the object but is not used as a part of the primary key. OD: Other Date. It indicates any meaningful date that is loaded into the table that does not identify the measurement part as the primay key.
Mandatory Yes
Example PI
Formula
WFK[Parsed Counter.File Header/Alias]. Any formula or value manipulation required to get from the parsed counter to the loaded value. This is used to populate the mapping values in the Loader_Table_Mappings configuration table. When Type = [OI, PI, GPI]. It determines the size of a VARCHAR2 column. Determines the order of the column in the tables. Indicates whether the column is to be loaded to the raw tables for this install.
No
OBJECTID
Size
Mandatory when 30 Type = [OI, PI, GPI] Yes Yes 3 YES CSV-G3
Order Enabled
FileFormatID( PK,FK[File Format]. It is a comma separated list of file format Yes s) IDs that indicate the supported versions for this counter group. New versions may drop or add new counter groups entirely. It is a combination of File Format and Vendor Version. For example, if the file format is XML, CSV and the vendor version is G3, P5 , then ID can be CSV-G3 or XML-P5. Aggregate TIME Determines the aggregation of the counter over time. Multiple Yes aggregations may be defined and these create multiple columns in Summary Objects using the aggregation as a column name extension. Possible values are MAX, MIN, SUM, AVG. If no aggregation is to be performed, use NULL. Determines the aggregation of the counter over elements. If the field value is 'null', then use AGG TIME. No
MAX
CELL MAX
Determines the aggregation of the counter up to the hour. This No is useful if the granularity is less than 60 minutes. If the field value is 'null', then use AGG TIME. Description of the column. This is used when the original counter name has to be shortened. No
CELL IDENTIFIER
Page 37
Yes Yes No Not mandatory if Type = Number Yes It is mandatory if CFG table is a foreign key in Counter Group. It is mandatory if the value of the Populate field in the CFG Table is 'Yes'.
from File Config WFK[Parsed Counter.File Header/Alias]. The Data Loader formula utilising Parsed Counters from the Counter Formula Group associated to the CFG table, used to load information into this field. from Loaded Raw-Data Data Table Procedure Formula WFK[Loaded Counter.Column]. The formula utilising loaded counters from the Counter Group associated to Raw Tables(s) associated to the CFG table, used to load information into this field.
BSC
Page 38
Hierarchy Unique ID
PK. Unique identifier for the hierarchy. This field Yes contains a hierarchy of all the hierarchy elements specific to a particular configuration table. For example, In a CELLCFG table, we might have a hierarchy of BSC and Cell. The chain is this case would be B_C where B is BSC and C is Cell. The value defined in the default hierarchy ID should correspond to the 'Hierarchy Unique ID' column in the Hierarchy Chains tab of the Interface Workbook Excel sheet. Description of the hierarchy. No
N_B_C
The WHERE clause in the SELECT statement has No the filtering is to be applied for the hierarchy.
Element Level Name of the element. This should be consistent across the interface. Formula from CFG Table The LOOKUP formula for element level.
Yes No No
Element Alias Shortened version of the element level. Override Hierarchy Level
This describes the sequence of the hierarchical structure. Yes It indicates the order of element level in hierarchical structure. It is a numerical value.
Page 39
Element Alias
Default shortened version of the element level. The Yes shortened versions are mainly used in the Summary and Busy Hour tables. When summaries and BH Summaries aggregate data to a specific element level, the element alias for that level is included in the summary table name. For example, standard element alias for Network = NW, Cell = CL, Neighbour Cell = NCL, BSC = BSC, Region = R, City = CTY.
NCL
Aggregation
DY
PK,FK [Hierarchy Field, Element Level]. If this Yes field is used, the Summary Report aggregates the Raw data up to the level specified in this field. WFK [Hierarchy Chain]. If this field is defined, No then this overrrides the Hierarchy to perform the aggregation to the Element Aggregation. This field contains a hierarchy of all the hierarchy elements specific to a particular configuration table. For example, in a CELLCFG table, we might have a hierarchy of BSC and Cell. The chain in this case would be B_C where B is BSC and C is Cell. The value defined in the default hierarchy ID should correspond to the 'Hierarchy Unique ID' column in the Hierarchy Chains tab of the Interface Workbook Excel sheet.
NBRCELL
N_NB_NC_B_C
Page 40
BH Name
PK. Short name for the BusyHour Definition Yes that is used in the Name for the BusyHour_<BH Name> and all BH Summary tables using this Busy Hour Definition. For example, for a BH based on Erlang, the BH Name would be ERL.
ERL
BH Formula FileFormatId(s)
Yes
THCALLS CSV-G3
PK,FK[File Format]. It is a comma separated Yes list of file format ids that indicate the supported versions for this counter group. New versions may drop or add new counter groups entirely. It is a combination of File Format and Vendor Version. For example, if the file format is XML, CSV and the vendor version is G3, P5 , then ID can be CSV-G3 or XML-P5. This is a Boolean value field. If the Base Table No has data that is sub-hourly, then if a rolling busy hour has to be calculated, set to TRUE. A rolling hour means 60 minutes from the DateTime and not a 'calendar' hour which is the 60 minutes between xx:00 and xx+1:00.
Rolling Hour
Yes/No
To Hour Aggregation If the Base Table has data that is sub-hourly, No then this is the aggregation of the formula to 60 minutes whether that is rolling or not. Hierarchy Aggregation If the BH Definition is used at an Element Level No that is NOT the element level of the Base Table, then this is the aggregation of the formula to the defined Element Level A WHERE clause on the Base Table to apply in No the Summary Report. User input to describe the BusyHour Definition. No It is added to the Summary Report as part of the description.
MAX
MAX
Page 41
Yes
DYBH
BusyHour Level
PK. Identifies the element level against the Base Yes Table's Associated CFG table at which level of aggregation the BH calculation is ranked. For example, TCH BH Definition has a base table of CELLSTATS, which has a CFG table of CELLCFG which has three hierarchies - one or more of which has BSC as a level. The BH is calculated to the BSC level according to the hierarchy formula on the CELLCFG table joined with CELLSTATS. [High/Low]. Order of the formula that results for ranking function. Sets the ranking to store: Rank From to Rank To. If these two values are equal, then only one BH period is stored. If Rank From = 1, and Rank To = 3, then three BH periods are stored. Yes No
BSC
High/Low 1
Rank To
You must populate these columns with two integer values. To find only the Busiest Hour, set both values to 1 (this is the Default).
No
Page 42
BH_Table Name PK,FK [BusyHour Table]. The Busy Hour Table used to Yes Ext determine which hour was the busiest for the element. Hierarchy ID WFK [Hierarchy Chain]. The Hierarchy ID used to track from the Busy Hour Table Element Level to the Busy Hour Summary Element Level. No
CELL_ERL_DYBH N_B_C_NC
PK. The Element Level for the Base Table to be Yes aggregated to according to the Busy Hour Element Level Busy Hour(s) . Default=NO If the Busy Hour Table has Rank From <> Rank To, then a Multi-rank average can be calculated in the Summary as a single row (no BUSYHOUR timestamp value). If NOT, then all ranked hours will be put into the summary. No
BSC
YES
Include BH Level Default=NO If the BH Element Level <> Hierarchy Aggregation Element Level, then decide whether or not to include the element name from the BH table in the resulting Busy Hour Summary.
No
YES
Page 43
Maximum length of the FileformatID is 7 characters. To fill in information about the file format and version ID: 1 2 3 4 Go to the File Formats worksheet of the Interface spreadsheet. In the File Format column, fill in the file format. In the Version column, fill in the version. In the FileFormatID column, combine the file format and version and specify it. For example, if the file format is IOG and version is R10, then the FileFormatID could be IOG_R10. 5 In the Enabled column, select the 'YES' value from the drop-down list. This will turn the file format ON for the entire installation.
Page 44
7 8 9
10 In the Enabled column, specify YES. 11 In the FileFormatID(s) column, specify the fileformatID that you have identifaied in the previous section.
Page 45
Combining Objects
It is possible to combine counter groups having the same Primary Keys before loading. This also helps to remove the fields that might cause conflict when joined. If there are fields of the same name in different counter groups, then we can keep them as UNIQUE after the join. To combine objects: 1 2 3 4 Open the Parsed Counters worksheet. Select two identical parser file headers and in the Combiner Type column, mark them as KEY to create a join between the two counter groups. Open the Counter Groups worksheet. In the Tablename column, set the tablename for all Counter Groups to be combined into the same table in accordance with standards. Click the Filter by Table button 5 6 7 Open the Raw Tables worksheet. Click the Add Raw Tables button to add the raw tables. In the Combiner column, set value as 'YES' for the corresponding table. to filter the list of Parsed Counters.
Validating
Validation performs the following two functions: It guarantees the order of the columns in the file It splits one file into two output files The Splitting functionality is useful when the number of columns in the input file exceeds the number of columns in the database. The OPTIMA Installation Tool does not currently support the splitting functionality. To validate: 1 2 Open the Parsed Counters worksheet. In the Counter Group column, specify the counter group. This should match up to a Counter Group Name in the Counter Group worksheet. 3 In the Parser File Header column, specify the header of the parser file. This should match the name in the header for the column in the parser output. This is used to configure the validator INI. 4 In the Order column, set the Parsed Counters order. This determines the order of the columns for the Validator. The loader expects the columns to be in this order after validation.
OPTIMA Installation Tool Version 6.1
Page 46
In the Enabled column, specify whether the column exists in the counter group for this installation. If it does, select YES.
Loading
WIth the loading process, you can load: Combined or single objects into a table Multiple objects into a table For the loading process, you need to: Identify the column Enter the type - specify OI: Other Identifier, OD: Other Date Provide a formula Specify the Order: the order that you want to see in the raw table Assign the CounterGroupName or the CounterGroupAlias if it has been set previously The PI, GPI, and DT are combined to make the primary key and they must be consistent for all objects that have the same raw tables in the CG. They also need to have the same order. Ensure that the Enabled column is set to YES.
Page 47
To load counters: 1 2 Open the Loaded Counters worksheet. Click the Add All Counters button . This populates the worksheet with all the counters from the Parsed Counters worksheet where the column Enabled has been set to 'YES'. If an alias has been defined for the counter group, then the alias will be automatically used. 3 In the Type column, specify the Type. This indicates the type of the field as it is to be loaded into the external table. For more information on Type, see About Loaded Counter Information on page 36.
Loading an external file into the config table on a periodic basis This is not currently supported by the OPTIMA Installation Tool.
Page 48
Defining Hierarchies
This always relates to the Config Tables. 1 Define the config table it is based on, and a unique identifier. The identifier is usually an under_score concatenation of the network elements in the hierarchy. For example, if the hierarchy of network elements is Network_BSC_CELL, then the unique identifier would be N_B_C. Go to the config table and define the default ID as N_B_C. Hierarchy fields relate to CFG fields. All information in the Hierarchy Fields worksheet is taken from the CFG Fields worksheet by name or formula. Hierarchies are in a 1:N tree structure. When networks are not 1:N, we must define the multiple hierarchies to support them. This picture shows an ideal hierarchy:
2 3
+ 4 5 Element Aliasing We define a short name for the network element. For example, CELL = CL For a specific hierarchy element level, we can override the alias value in the Element Alias Override column in the Hierarchy Fields worksheet. The purpose of creating an alias is for naming the tables. For example, CELLSTATS_CELL = CELLSTATS_CL
Page 49
Creating Summaries
Creating Summaries affects Loaded Counters and Summary Definitions worksheets. In Loaded Counters, the field is Aggregate_Time and Aggregate_Hour and object is not used. For each column in loaded counters, we define how each column is aggregated. Use comma separation if multiple aggregation is required. To create summaries: 1 2 Open the Loaded Counters worksheet. Set values for the following columns: Aggregate Time: This is recommended for the OI and OD type. It is the aggregate formula used by Summary to sum, min, max, and average the counters in the summary. If NULL is used, this excludes the counter from aggregation. Aggregate Object: Is the aggregate formula used for the counter over objects rather than time. When it is left empty, aggregation over time is assumed. Aggregate Hour: In sub performance data, this may be used to aggregate the counter to the hour in a different way than you normally aggregate over time.
Page 50
Power Tools
The Power Tools have been designed to help you create, amend or review interface templates. The Power Tools enable you to: Create an interface template from an existing installation Merge two existing 6.1 interface templates for the same interface Report on differences between two templates for the same interface Migrate 1.4x interface templates to 6.1 interface templates Remove a file format/version from the 6.1 interface template Create a blank 6.1 interface template Display a 6.1 interface template
Page 51
To use this feature: 1 2 3 4 5 From the Tools menu, click Power Tools. In the dialog box that appears, click Next. Select the Generate a 6.1 Interface Template option. Click Next. Select the required source(s). You can select: Both Database and Parser Out - or Database only - or Parser Out only
Whichever permutation you select, you can choose to include or exclude the INI files. 6 Click Next. The following steps vary according to which source selections you have made. Steps when Database has been Selected as a Source 1 Specify the database connection details in the available drop-down and edit boxes.
When you have specified these details, a message prompt appears. Click this to test the connection and the existence/accessibility of the tables.
Page 52
Select the schema to use from the drop-down list, as in this example:
When all database details have been specified and tested (using the message prompt), the grid will show a list of the available tables. 4 Click Next.
Steps when INI Files have been Selected as a Source 1 Specify the folder locations containing the INI file information of the existing installation. It is possible for you to leave the folder with Combiner INI files empty and still continue.
2 3
When you have specified three valid folders, a message prompt appears. You can click this to preview the INI files. Click Next.
Page 53
Steps when Parser Out has been Selected as a Source 1 Specify an 'Out Folder' that contains the sample Parser Out information.
If all the sample files are in one single folder (as opposed to subfolders) then you can select the 'Output in Single Folder' checkbox. For this option, you must provide a valid regular expression to extract the counter name from each sample file. If you want all files for each measurement object to be read (rather than just one file), select Scan All Files. You can preview the counter group names, by clicking the appropriate prompt message. Click Next.
3 4 5
Specifying the File Format 1 2 Specify the File Format and File Format Version. Click Next.
Running the Tasks The Creating Interface Data screen now appears, listing all the tasks to be performed. 1 2 Click Start. Wait until all the tasks change their state from Not Started to Finished. Click Finish. The Interface dialog box opens, showing the interface template that has been created. You now have the opportunity to save the template. For information on this, see Saving an Interface Template on page 55.
Page 54
Page 55
7 8
In the Save Interface dialog box, click Save. Each task is performed, and when the state for each task changes from Not Started to Finished, the template is saved. Click Close to exit.
8 9
Page 56
Click Start. Wait until all the tasks change their state from Not Started to Finished. Click Finish.
OPTIMA Installation Tool Version 6.1
The Interface dialog box opens, showing the interface template (with merged values) that has been created. You now have the opportunity to save the Interface Template. For information on this, see Saving an Interface Template on page 55.
Page 57
Page 58
The Interface dialog box opens, showing the updated interface template that has been created. You now have the opportunity to save the template. For information on this, see Saving an Interface Template on page 55.
8 9
Click Start. Wait until all the tasks change their state from Not Started to Finished. Click Finish.
The Interface dialog box opens, showing the interface template populated with values. You now have the opportunity to save the template. For information on this, see Saving an Interface Template on page 55.
Page 59
The Add Interface:Workbook dialog box appears 3 Click Browse to select the interface workbook that you want to add to the project.
Click Next. The Interface Properties dialog box appears. The Interface Properties dialog box appears only when you add a new interface. If you add another version of an existing interface, this dialog box does not appear.
Page 60
Click Finish.
Page 61
Click Export Validation XML to export the errors to an XML file. -orClick Export Errors to export the errors to a CSV file. You need to fix these errors in the Excel files.
The dialog box that appears lists the tasks to be uploaded. 5 Click Start.
Page 62
It provides the following information: Source of the task State of the task Time Start Time of the upload Running Time of the upload End Time of the upload Click Cancel to stop the upload during the upload process. 6 Click Exit to close the dialog box. You can click View Log to see the log messages once the upload is finished. The interface is uploaded to the database.
Page 63
Activating an Interface
To activate an interface: 1 2 Ensure that there is at least one interface template uploaded to generate a revision. Select the Vendor Interface <Revision_Number>, right-click and select Activate Interface. The Activate Interface screen opens.
The Activate Interface screen displays all the activation objects such as loaders, combiners, and validators for a particular revision. It displays all the existing objects in the Activation Tree in a green colour. The combiner, validator, loader operations which have an entry in the AIRCOM.INSTANCES table are displayed in a yellow colour. It contains the following panes: Activation Tree: Lists the activation objects, type of activation objects, version and format. Database Operations: Lists the various database operations. The check boxes enable you to selectively activate a particular operation. It is not possible to deactivate the Busy Hour Summary database operation without deactivating the corresponding Busy Hour database operation. Additionally, it is not possible to deactivate raw table database operation. Detail: Lists the details of the various activation objects selected in the activation tree pane. For a particular schema, the Details pane shows all the ORACLE objects within that schema.
Select the Database Operations to be activated. You can select the Create Partitions checkbox to run the OSS Maintenance Package to create table partitions.
Page 64
Click Activate. A dialog box is displayed indicating that a backup of the AIRCOM schema is created in the AIRCOM_BACKUP schema. Click OK. The activation process creates the objects that have been defined in the interface revision. For example, if you activate the CFG tables, then the activation process will compare the columns that have been uploaded with the columns that already exist in the database and then will add any columns that do not already exist. The objects that now exist in the database are marked in Green after the activation process. INI files and batch files are always recreated during the activation process and existing files are overwritten.
5 6
Click Working Folder on the Activate screen to open the working folder. After activation is complete, the deployment scripts are copied to the working folder. Copy all the files in the <Mediation_ID> folder in the working directory to the mediation device. You need to manually set the home directory for the OPTIMA backend referenced by the environment variable $OPTDIR (UNIX OS) or %OPTDIR% (WIN OS) before running the deployment scripts.
Click Close to exit. Click Activation Log to see the activation log. It lists the following details: Log Message Severity Date Time Client Machine
In the Log Display window, click Export to export the activation log messages to a file in the CSV format. You can also select the Show Preview Row checkbox to expand the log message details. In case, you click Activate again without closing the original activation screen, a dialog box will appear asking you to keep or override the current backup.
Page 65
To generate a Decommissioning Report: 1 2 Ensure that you have activated an interface. For more information on this, see Activating an Interface on page 64. Right-click on the revision number for which you want to generate the report, and from the menu that appears, click Decommissioning Report. The Decommissioning Report for the selected version opens. It lists the tables, columns, old and new summary configuration, instance, and loader configuration information that is no longer needed for this version.
Page 66
Click Collapse all/Expand all to collapse/expand all the details. You have the option to export the decommission report in HTML or XML format. To do so, click the button and save the report to the appropriate location and in the required format.
Page 67
Reusing PRIDs
For an older version of an OPTIMA installation (pre V6.1), the AIRCOM INSTANCES table does not contain the following columns: Vendor Version File Format Tablename Each row in the AIRCOM INSTANCES table defines an OPTIMA process. Each process is identified by its PRID (AIRCOM Process Identifier). The PRID is formed by concatenating values in the following columns: MACHINEID PROGID INSTID There are multiple instances of combiners, validators and loaders for each vendor version, file format, and object. Hence, during activation, it becomes necessary to identify each instance with a unique Process IDs (PRID). To avoid duplicates, when you are upgrading an OPTIMA installation using version 6.1 of the OIT, this functionality enables you to associate existing PRIDs with their respective vendor version, file format, and object, and to update the AIRCOM INSTANCES table with that information. The OPTIMA Installation Tool will attempt to reuse any AIRCOM INSTANCES records which match the current vendor version, file format and object. This is the basis of the PRID Re-use function. Reusing PRIDs is only necessary for combiners, validators and loaders and only when an upgrade is taking place. New vendor versions, file formats, and objects which cannot be matched to an AIRCOM INSTANCES record will generate a new PRID and a new INSTANCES record. Summary Process is vendor-neutral and therefore there is no need to reuse PRIDs.
Page 68
To reuse PRIDs: 1 Select the <Revision_Number>, right-click and from the menu that appears, click Reuse PRIDs. The Reuse PRIDs window that opens displays the data from the AIRCOM Instance Table. For every instance of a combiner, validator, and loader for which you want to reuse a PRID, select the particular row.
From the Vendor version, File format and Operation object name drop-down lists, select the correct values. You can get the correct values for any instance from the respective INI files.
Click Apply.
Page 69
Click any INI File in the left hand pane to see the respective key and value in the right hand pane. You can also edit the combiner, validation and loader path.
Page 70
Page 71
Troubleshooting
I cannot log in to the database with the tool after I run Setup.exe Ensure you have installed the API and data dictionary in the OSS_DICTIONARY schema. This is available in distribution under Management Tools, program code 431. Follow the installation instructions to install the API, then log on to the tool as oss_dictionary/password. I have applied patch 1.0.x and now I want to go to patch 1.0.y Simply download and run the latest patch installer, as long as you are on a 1.0.x version you can re-install the previous updates without any issues. The tool is not responding, what should I do next? The tool can sometimes take several hours to complete an upload or an activation. However occasionally, the tool finishes processing but freezes. To find out what the tool is doing, run the following query: SELECT * FROM OSS_DICTIONARY.LOG_EVENT ORDER BY EVENT_DATETIME DESC The log messages refer to IDs, how do I know what tables this is referring to? The DD_OBJECT table enables you to see which object the ID refers to. The DD_OBJECT table should never be altered, however, it can be queried to retrieve the object. For example, for the log messageFunction ACT_ON_RAWTABLE processing objectid 309925 with activation value 1, the following query can be run: SELECT OBJECT_NAME FROM DD_OBJECT WHERE OBJECT_ID=309925 I get an error when I validate my template. How should I resolve this? The validation results will show which spreadsheet in the workbook the error applies to and the error that is encountered. The template can be re-validated by selecting Validate Template from the Tools menu. The SQL that is used in the validation can be found by clicking on 'Export Validation XML', any rows brought back by the queries signify an error in the template workbook. I am trying to add a new project to my database, but I get an error There is a limit of one project per database. So 1 project -> 1 database -> 1 customer -> 1 project file. New interfaces can be added to the same project, but two projects cannot exist in the same database. I have defined some summaries, but they have not been included when I upload/activate the interface This is normally caused by a lack of hierarchy information. In the current version of the installation tool, all summaries must have hierarchies defined. Either a hierarchy must be defined per summary in Summary Defn.Hierarchy ID, or more simply CFG Tables.Default HieraerchyID must be populated for the CFG table associated with the raw base table in the Raw Tables spreadsheet. I get an error about VARCHAR2a when compiling an Optima Backend package
Page 72
You need Oracle 9.2.0.3 or above and you need to ensure that the catalogue (Oracles catpatch) has been migrated successfully for varchar2a to be usable. To run the catpatch for the database do the following: sqlplus sys/<password>@<optimadb> as sysdba SQL> Shutdown immediate SQL> Startup migrate SQL> @?/rdbms/admin/catpatch.sql How should I update a pre 6.1 interface template file to the official 6.1 interface template file? You should use the migrate operation in the Power Tool wizard and save the interface. How should I update a beta 6.1 interface template file to the official 6.1 interface template file? You should use the display interface operation in the Power Tool wizard and save the interface.
Page 73
Page 74
Index
A
Alias Information, default element level 40
B
BusyHour definition information 41 summary information 43 table information 42
C
CFG fields information 38 table information 33 Counter Group Information, about 34 Creating interface workbooks 44 projects 16
D
Database connection properties 24 server machine properties 24 Defaull Element Level Alias Information, about 40 Defining blank interface workbook 44 global parameters 27 project 16 Definition Information busyhour 41 summary 40
Information (root) busyhour definition 41 busyhour summary 43 busyhour table 42 cfg fields 38 CFG Table 33 default element level alias 40 hierarchy chain 39 hierarchy field 39 Information counter group 34 file format 32 raw table 34 loaded counter 36 parsed counter 35 summary definition 40 Interface activating 64 uploading to database 62 Interface Workbook about 29 adding to a project 60 busyhour definition information 41 busyhour summary information 43 busyhour table information 43 cfg fields information 38 cfg table information 33 counter group information 35 default level alias information 40 file format information 32 hierarchy chain information 39 hierarchy field information 39 loaded counter information 36 raw table information 34 summary definition information 40 validating 61
L
Loaded Counter Information, about 36 LUNS Defintion, updating 25
M
Menu Button, using 30
F
Fields CFG information 38 hierarchy information 39 File Format Information, about 32
O
OSS Installation Tool, about 9
G
Global Parameters,defining 27
P
Parameters Global 27 Project adding an interface workbook 60 creating 16 updating properties 23, 24, 44 uploading information 27 Properties, updating 23, 24, 25
H
Hierarchy chain information 39 field information 39
Page 75
R
Raw Table |nformation, about 34
S
Summary Definition Information, about 40
T
Table Information busyhour 42 CFG 33
U
Updating database connection properties 24 database server machine properties 24 general properties 24 LUNS properties 25 mediation machines properties 25 project properties 23, 24, 25 summary definitions properties 25
W
Workbooks blank 44
Page 76