configurator 4.0 concepts guide issue 1.0

7/29/2019 Configurator 4.0 Concepts Guide Issue 1.0

1/38

Amdocs Cramer&RQILJXUDWRU

Concepts Guide

ED003009 Issue 1.0


2/38

Cramer Systems Limited, all its affiliates and subsidiaries were acquired by Amdocs in August 2006. This

document contains naming conventions and branding information that is in the process of transition as

part of the acquisition. Accordingly, slight inconsistencies may exist within this document and/or between

this document and other portions of the Cramer Amdocs OSS Division materials or other Amdocs

documents.

Copyright AmdoDT. All Rights Reserved. The included software and/or documentation cannot be

reproduced, downloaded, disseminated, published, transferred, or combined with any other materials, in whole or in

part, in any form or by any means, without the prior written consent of Amdocs. The included software may contain

and utilize third-party software products. These materials are confidential, and shall be returned to Amdocs upon

request. Amdocs reserves the right to revise the included software and/or documentation and to make changes in the

content from time to time without notice. The trademarks and service marks of Amdocs, including the Amdocs mark

and logo, Ensemble, Enabler, Clarify, Return on Relationship, Intelecable, Collabrent, Intentional Customer

Experience, QPASS and Cramer are the exclusive property of Amdocs, and may not be used without permission. All

other marks are the property of their respective owners.


3/38

Proprietary and Confidential Information of Amdocs iii

Contents

Contents

About thisguide Intended audience. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vSoftware information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vDocumentation feedback. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vDocument structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vi

Chapter 1 Executive summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Chapter 2 Configurator overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Configurator as part of the"NEPDT$&4$SBNFS044. . . . . . . . . . . . . . . . . . . . . . 4Developer tools . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Chapter 3 Key features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

Creation and maintenance of metadata . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10Version names for datasets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Active version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Metadata transfer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Visualization of metadata. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Color coding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Globalization for multiple language support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13Metadata library and version management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Chapter 4 Configurator technology support. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Chapter 5 User interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17Wizards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19WebReports. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Views . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 6 Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Related reading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Glossary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25


4/38

Contents

iv Proprietary and Confidential Information of Amdocs

Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29


5/38

Proprietary and Confidential Information of Amdocs v

Aboutthis

guide

About this guide

The purpose of this document is to introduce you to the concepts of the Amdocs

Cramer Configurator and to describe its purpose and function. It introduces you tothe general features of the Configurator and the main concepts of its operation withinAmdocs Cramer.

Two versions of the Configurator are available, the standard version and the advancedoption pack. This guide describes the features available in both versions and indicateswhich functions apply to which version.

Intended audience

This guide is intended for readers who are unfamiliar with the Configurator, in order tohelp them understand its capabilities and the benefits that can be achieved by using it.

Software information

This document reflects both the Configurator and the Configurator (Advancedoption pack). Differences between the two products are clearly indicated.

Documentation feedback

We value any feedback regarding our documentation. You can send your comments bye-mail to [email protected].


6/38

About this guide

vi Proprietary and Confidential Information of Amdocs

Document structure

This document is divided into the following chapters:

Chapter No Title Description

1 Executive summary A summary of the capabilities of the Configurator in

business terms.

2 Configurator

overview

An overview of the main features of the Configurator

and its integration with$SBNFS044.

3 Key features How the Configurator works as a data configuration

utility.

4 Resource Managertechnology support

Describes the technology supported by the Configurator.

5 User interface Broad explanation of the Configurator user interface.

6 Conclusion A summary of the Configurator concepts described in

this guide.


7/38

Proprietary and Confidential Information of Amdocs 1

Chapter

1

Chapter 1 Executive summary

At the hearUPG$SBNFS044 is the Resource Manager inventory management

platform, which enables telecommunications operators to increase their productivityand functional efficiency. The Amdocs Cramer Resource Manager inventory iscarefully designed to enable customers to tailor it to their business needs. One of themost important areas of configuration lies in the inventory's network model.

Flexibility is provided to enable customers to model network equipment, connectivityand services in a manner most intuitive to their users, and most aligned with theiroperational needs. This flexibility is delivered out of the box through a layer of

configuration data (known as 'metadata'). The metadata also drives user-orientedconfiguration, such as the authorization of functionality to users, the menus andsubmenus presented in the Amdocs Cramer user interface and the localization of userinterface text into other languages.

The Configurator product enables customers or their partners to create and maintainconfiguration data through a powerful and intuitive user interface. It is an optionalcomponent of$SBNFS044.

Rapid design and deployment of new services and networks in Amdocs Cramer meanscustomers can respond to market demands and start provisioning and automatingdelivery at the earliest opportunity.

Configurator capabilities snapshot

The Configurator has a number of capabilities, which include the following:

State-of-the-art user interface that has the same look and feel as the ResourceManager, enabling you to visualize the metadata

Enables configuration without coding

Reduces effort and risk, by minimizing the complexity of creating and loadingmetadata

Automatically carries out metadata integrity checking

Based on the industry-standard Oracle RDBMS

Allows metadata libraries (datasets) to be built away from live data


8/38

Chapter 1 Executive summary

2 Proprietary and Confidential Information of Amdocs

Version controls to enable you to accurately identify current datasets and seehistorical development

If you have the Configurator (Advanced option pack), multiple datasets can bemaintained in one database

The standard version of the Configurator supports the maintenance of only one dataset at a time.


9/38


Chapter

2

Chapter 2 Configurator overview

Every Amdocs Cramer customer has specific requirements for the network equipment

and technology supported in their deployment of Amdocs Cramer software, includingthe way in which it should be modeled and visualized. Customers also have tailoredrequirements for their users and user groups in order to ensure that the appropriatefunctionality is provided to authorized users. In order that the Resource Manager cansupport these requirements and be fully flexible, it uses a metadata configuration layer.The configuration of the metadata that forms this layer is carried out using theConfigurator.

The Configurator provides a sophisticated user interface to enable rapid and intuitivemanipulation of this metadata layer. For example, typical tasks that you use theConfigurator for include:

To define new device types (from new manufacturers or required for new

technologies)

To define new parts for device types, such as new shelf types, slot types or cardtypes

To define new device templates, to automate the filling of devices

To define new templates for cabling and cross connection

To define new connection types, such as link types and circuit types

To define new logical configurations, such as location types, service types andsubscriber types

To define new customer-specific attributes for inventory data

To define which attributes are available on the attributes page of ResourceManager wizards

To authorize Amdocs Cramer users to execute Amdocs Cramer functionality

To configure the Cramer Object Model

To localize $SBNFS044 to one or more different languages

The Configurator is an independent database of metadata that you use to create andmaintain metadata for rules and relationships used in the Resource Manager datamodels, for example, defining templates for new devices of evolving technology. The


10/38



Configurator has its own user interface with a similar look and feel as other products in$SBNFS044.

In this guide you will discover that the Configurator:

Allows you to configure metadata without coding or an extensive understanding ofthe Resource Manager data models, through the use of the wizards.

Allows you to visualize your metadata in views.

Provides you with a sophisticated dataset management function away from livedata.

Allows you to upgrade your metadata for new releases of the Resource Managerand version control your current metadata.

Allows you to check the integrity of your metadata.

Ensure that your metadata is protected using the same levels of security providedin the Resource Manager.

Configurator as part ofWKH&UDPHU266

The Resource Manager inventory model forms the core of$SBNFS044, as acomplete network inventory application. Additionally, Amdocs Cramer has developeda number of tools to support every stage of network resource management. These

include:

Inventory management tools, which support the Resource Manager inmaintaining a complete, accurate and maintained model of network resources.

Provisioning automation tools, which provide the capability for encapsulating,and then automatically executing, the design and implementation processes.

Adapters and integration tools, to rapidly integrate Amdocs Cramer products,including the Resource Manager, with external OSS applications.

Developer tools, to enhance the processes of building and maintaining inventorydata.

The Configurator provides a user interface to guide developers through the process ofconfiguring Resource Manager metadata. Using the Configurator, you can create,modify and delete metadata using libraries of metadata sets.

The Configurator supports metadata configuration, that is, the definition of networkinventory behavior and vendor-specific device models, without coding. Itssophisticated dataset management and integrity checking capabilities reduce effort andrisk, by minimizing the complexity of creating and loading metadata. New networktechnologies and network equipment upgrades can be rapidly and easily modeled andpassed into the inventory, as can additional attributes to existing network objects. A


11/38

Amdocs Cramer Configurator Concepts Guide


complete history of all metadata changes is maintained, and comparison of differentversions supported.

The standard version of the Configurator supports the creation of a single dataset. Theadvanced option supports the partitioning of metadata into multiple datasets and sub-datasets. This enables libraries of related or independent metadata to be maintained,ready to be combined in flexible ways for new deployments.

Amdocs Cramer has developed a number of tools to support every stage of networkresource management, from the initial loading of data to implementing a service. TheConfigurator is part of Amdocs Cramers Inventory solution. Figure 2-1 shows howthe $SBNFS044 fits together in the context of the OSS environment. Thisdiagram does not show the interaction between the Configurator and the ResourceManager; it is shown in Figure 2-2 on page 6.

Figure 2-1 7KH&UDPHU266


12/38



Resource Manager

The Resource Manager provides a centralized approach to network inventory andservice configuration management within a framework that allows capacity constraintsof all kinds to be modeled. It uses an industry-standard Oracle RDBMS to maintainthe metadata driven model of physical and logical inventory.

The Configurator interacts with your standard Resource Manager database directly, orindirectly through XML generated data.

The interaction between the Configurator and Resource Manager database isrepresented in Figure 2-2.

Figure 2-2 Interaction between product databases

This architecture enables you to create and maintain independent libraries of metadataaway from live data. The Configurator automatically enforces rules within its wizardsto ensure that inconsistencies in the metadata you are maintaining are avoided.

After you have created or carried out maintenance on your metadata, the Configuratorprovides you with tools to export the datasets either directly into the Resource Managerdatabase, or into an XML file. During this procedure the integrity of the metadata ischecked.

ResourceManagerdatabase

Metadatatables

Core tables(hold the

ResourceManagerdata)

Configuratordatabase

Export/Importwizard

Other(for example,

Cramer constants)Configurator XML

Satellite tables

Metadatatables


13/38



Developer tools

The Amdocs Cramer development environment comprises a number of products andlicences that support the building and management of a network inventory at thedeveloper level.

Developer activities concern the configuration, initial population and maintenance ofthe inventory platform itself, and not the day-to-day user and maintenance activities.

Developer tools are needed for:

Configuration

Modeling of the components of an inventory, the equipment and services, atthe developer level is supported by the Configurator.

Data migration

The process of population of the database is supported by the Migrator.

Data load from third-party sources can be carried out using the Sync Engine.If the source system is to remain in use, ongoing synchronization is supportedby the Sync Engine. For further information, refer to the Sync Enginedocumentation set.

Integration

Integration with external systems is supported by the Amdocs Cramer API,the Cramer Object Model and the Amdocs Cramer client framework.

Business rule customization

For features such as naming conventions.

Web content tailoring

For modification or extension of homepages, WebReports, or graphical webcontent.

Further information about the developer tools are described in the Amdocs Cramer Resource Manager ConceptsGuide.


14/38




15/38


Chapter

3

Chapter 3 Key features

The Configurator enables you to create and modify your metadata by visualizing it as

objects in the user interface. The Configurator is a database of metadata that youexport for use in the Resource Manager. A number of key features form the frameworkfor the successful operation of the Configurator; understanding these key features helpsyou to maximize its capabilities.

These features can be summarized in the following list. Each feature is expanded indetail in subsequent sections:

Feature Description

Creation and

maintenance of metadata

The Configurator has been built to enable you to manage your

metadata in a simplified and logical way.

Metadata transfer in andout of Resource Manager

deployments

The Configurator allows you to carry out your metadatamanagement away from your live data, in its own database.

Visualization of metadata The Configurator provides you with a sophisticated user interface

for creating, modifying and managing Resource Manager

metadata.

Globalization for multiple

language support

The localization of text strings into a different language can be

done without programmers, managed using the Configurator.

Metadata library and

version management

A key feature of the Configurator is to provide security for your

metadata.


16/38



Creation and maintenance of metadata

The Configurator has been built to enable you to manage your metadata in a simplifiedand logical way. This typically includes tasks such as creating new metadata when newtechnology becomes available, or changing metadata when new operating proceduresare introduced. The Configurator can cater for many different scenarios that you maywant to implement for your business environment, such as the management of trainingsystems.

Key to understanding metadata management is the understanding of datasets, theirhierarchy and version control.

Datasets

A dataset is a collection of metadata that has been grouped together in theConfigurator database. Each item of metadata in the database belongs to a specificdataset.

When you use the standard version of the Configurator you can only work on onedataset at a time, this is know as the active dataset. The information shown in the userinterface browsers, the views and the wizards all relate to the active dataset andcompatible releases. The active dataset is at the top of a hierarchy, as one dataset cancontain any number of other datasets. This may be used, for example, to differentiatebetween:

Old and new device types

Different technologies and manufacturers

Test, training and live inventory deployments

The following additional options are available in the Configurator (Advanced option pack):

If you group related pieces of metadata together as datasets, you can use these as sub-datasets. Forexample, You can select sub-datasets to include in a containing dataset and so flexibly group the metadata inas many ways as you need. Including a dataset includes all its sub-datasets, this means that all the metadatathat belongs to the sub-dataset can be seen and used in the containing dataset. You cannot change themetadata in the sub-dataset by making changes to the containing dataset.

You can organize datasets in a hierarchy so that there are as many levels of sub-datasets as you require.However, they can be included only if the datasets are compatible. That is, if they belong to the same, orcompatible, Amdocs Cramer release and the metadata in the including dataset and sub-dataset is consistent.


17/38



Version names for datasets

The Configurator keeps a complete history of all the changes made to the metadata.

You can consider each change to the metadata to be a different version of the metadataand you can give a version name to each of the changes at any time.

Since any change you make to the Configurator database is associated with one datasetor another, you actually add version names to datasets. You can use the version nameto export the metadata or to access it at a later date.

Active version

If a dataset has versions, you can select one of its versions to be the active version (of thedataset). So that you can easily identify the dataset your are working with, the name ofboth the dataset and the version appears clearly in the user interface.

Now, all the information shown in the browsers, views and homepages relates to theactive version of the dataset and compatible Amdocs Cramer releases. That is, themetadata is shown as it was when the version was created.

Upgrades

You can upgrade from one Amdocs Cramer release using the Configurators Upgradewizard.

Metadata transfer

The Configurator allows you to carry out your metadata management away from yourlive data, in its own database. In order for you to use your metadata, you need toexport it from the Configurator database into the Resource Manager database. You can

import from a Resource Manager database into the Configurator database.

You can export and import metadata between Configurator databases, the ResourceManager databases and also XML files. For example, a partner carrying out metadatamanagement for a customer can export the dataset to an XML file to enable thecustomer to download it from a remote server.

You can either use the Export/Import wizard provided, or you can run a command lineutility.


18/38



Using an Export/Import wizard in the Configurator, you can:

Export the metadata of a whole dataset or export only the difference between twoversions of the same dataset

Export a dataset

Export complete or partial datasets

You can choose whether to include individual items of metadata when the dataset isexported, using an export selection option. Items that you choose not to include are

shown in gray in the browser to help you to identify which items are included forexport. You can override these settings when you run the Export/Import wizard.

Visualization of metadata

The Configurator provides you with a sophisticated user interface for creating,modifying and managing Resource Manager metadata. Configurator provides youwith wizards, WebReports, views, homepages and tree browsers for navigating andmanaging metadata.

The wizards are for creating and modifying metadata for use in the Resource Manager.They allow you to see, for example, descriptive text about object behaviors, rather thantrying to identify an objects constant value. Apart from the fact that you only seeinformation in the wizards that is in the active dataset, the way in which theConfigurator wizards work does not differ from the way the Resource Manager wizardswork.

WebReports enable you to carry out tasks that may otherwise be time consuming andprone to errors, such as comparing differences between versions of datasets. After yourun a WebReport, the results are presented in a logical order in a formatted HTMLpage in the user interface.

The Configurator views are used to take textual information from the database andpresent it in the user interface using a range of different icons, bitmap images and colorcoding. The icons you see in the views are context-sensitive, which means that you canopen further views or related information about an object, or you can select anddeselect the item from inclusion in an export. The items that you see in the views aredisplayed only for the active dataset.

If you are using the Configurator (Advanced option pack), you can choose to export a dataset with or without itssub-datasets.


19/38



Color coding

An important part of the visual features of the Configurator is the use of color to helpyou understand the organization of the metadata you are viewing.

When you create a dataset you can choose a color to represent its icon in the userinterface. All the icons of the objects belonging to a dataset have the same color as thedataset icon itself. This is especially useful for distinguishing between items belongingto a dataset and items belonging to its sub-datasets.

As described previously, names of items can appear as either black or gray in theResource browser. Gray items indicate that they are not to be included in the export.

Globalization for multiple language support

Amdocs Cramer's Resource Manager, Resource Manager Options, Service Catalog,Task Engine, Delivery Engine, Route Finder, Sync Engine, Activation Engine, adaptersand Packs are fully globalized, and are capable of being localized into virtually anylanguage. The localization of text strings into a different language can be done withoutprogrammers, managed using the Configurator.

Configurator displays all translation values for any item of user interface text, with fullunicode support. Configurator provides an export capability for all translationinformation into tab delimited file format, in addition to the standard ConfiguratorXML format. This allows translatable information to be passed to third-partytranslation tools that can import tab delimited files. The Configurator cansubsequently import the translated tab delimited files.

The localization metadata and localizations for all user interface text can then be passedto a Resource Manager deployment. Multiple language support is provided, enabling aResource Manager instance to support users with different preferred languages.

The Configurator user interface enables configuration of values into virtually anylanguage.

The user interface of Configurator itself is English and is not localizable. Any module metadata managedoutside the Configurator product (for example, a Task Engine Metadata Maintenance Utility) is translated outsideConfigurator.


20/38



Metadata library and version management

A key feature of the Configurator is to provide security for your metadata. The levels ofsecurity are the same levels as those provided by the Resource Manager and otherproducts in $SBNFS044. It implements the same features of owners and roles,which means that you can limit Configurator users with respect to:

The type of access they have, whether it is read-only or read and write.

The wizards, homepages, WebReports and browser information they can access.

Making changes to datasets they own.

In the Advanced option pack, datasets are assigned their own access permissions using the Dataset wizard,

which is available in only the Advanced option pack.


21/38


Chapter

4

Chapter 4 Configurator technologysupport

The Configurator is built alongside Amdocs Cramers standard product suite tosupport all technologies currently supported in the Resource Manager. As theConfigurator is used to create the metadata that the Resource Manager uses to supportdifferent technologies, the full list of technologies are described in more detail in theconcepts documentation for the Resource Manager.

For more information on supported technologies, see the Amdocs Cramer Resource Manager Concepts Guide.


22/38

Chapter 4 Configurator technology support



23/38


Chapter

5

Chapter 5 User interface

The Configurators user interface has four resizable frames comprising the Resource

and Relation browsers, a Wizards frame and a WebReports and Views frame thatdisplay information about the metadata, the Configurator wizards and theConfigurator views, homepages and WebReports. The user interface has a title bar,menu bar and tool bar, which includes a Find facility, and a status bar, as well ascontext-sensitive shortcut menus.

The Configurator enables you to visualize the metadata using specific wizards,WebReports and views in the user interface.

Figure 5-1 The Configurator user interface

Each frame has a dedicated use and the overall configuration allows separate butrelated functions to coexist without overlapping.

WebReports andViews frame

Relationsbrowser

Wizards

frame

Resourcebrowser


24/38



Frame Description

Resourcebrowser

Provides an information exploration tool. Provides access through tabs thatshow different configurable entities, such as circuit types or location types.

Exploring these tabs shows instances of them that exist in the active dataset.

Relations

browserThe Relations browser provides related information on a selected objects.

Anywhere in the interface that you find an object you can send the object to

the Relations browser, which will instantly be populated with its related

objects. Similarly to the Resource browser, related objects are grouped under

headings.

The Relations browser is context sensitive and the displayed information is

specific to the selected object.

For example, you select Relation from the shortcut menu of the Copper linktype (in the Connection Types tab of the Resource browser), in the Band-

widths tab of the Relations browser you can see a short list of bandwidths.

WebReports

and Views

frame

The WebReports and Views frame displays graphical representations of the

metadata that is configured in the active dataset.

Every object within the Configurator has an associated homepage that can be

displayed in this frame. Homepages present the information of the object, in

forms. They assist you in maintaining a wide range of object-specific

attribute data as attributes can be updated on the form and submitted.

WebReports are the reporting interface, providing summary information for

different activities. For example, you can use the Comparison WebReport to

compare the active dataset with an earlier version of the active dataset.

Wizards frame The Wizards frame displays the wizards that are used to create metadata.


25/38



Wizards

Wizards make standard operations faster, easier and consistent. The wizards provide alogical sequence for carrying out tasks and offer appropriate choices for each task.There are many wizards that you use to configure and manage your metadata; these aresplit into three main categories to help you understand their function. The wizardsinclude:

Network wizards that create and maintain metadata used by Resource Managerwizards. For example, Bandwidth wizard or Device Type wizard.

Client wizards that create and maintain metadata for the Resource Manager userinterface. For example, the Icon wizard or the Action wizard

Configurator wizards that organize the metadata held in the Configurator. Forexample, the Dataset wizard or the Export/Import wizard.

WebReports

WebReports are powerful data visualization tools that provide interactive reportingand investigation of the metadata held in the Configurator. WebReports incorporate acombination of text, hyperlinks and graphics:

The Comparison WebReport can compare different versions of the same dataset ordifferent datasets of compatible releases.

The History WebReport shows all the changes made to any of the metadata in adataset.

The Integrity Check WebReport reports inconsistencies in the metadata within adataset.

For a more comprehensive list of the wizards available in the Configurator, see the Amdocs Cramer Configurator(Advanced option pack) User Reference Guide.


26/38



Views

The views available in the Configurator allow you to visualize the metadatacomponents of an object, instead of a representation of numbers and IDs for relatedobjects. For example, a bandwidth view as shown in Figure 5-2, can be used to seeconfigured bandwidth information.

Figure 5-2 Example of a Bandwidth view

Views available in the Configurator are:

Bandwidth

Card template

Card type

Circuit type

Dataset

Device template

Elevation

Internal cross connection

Link type

Link template

Shelf type

Topology type


27/38


Chapter

6

Chapter 6 Conclusion

The Configurator provides a powerful user interface for the management of inventory

configuration data known as metadata.

By taking out the requirement for an in-depth knowledge of the Resource Managerschema, your metadata can be managed by specialized users, instead of developers.

The wizards in the Configurator ensure that you create only metadata that conforms tothe rules and relationships used in the Resource Manager data model. This metadatacan be viewed graphically and with color-coded icons, using views in the user interface.

The Configurator provides ongoing flexibility for introduction of new technology andsimplifies the task of upgrading metadata between Amdocs Cramer releases.

The Configurator provides you with a complete solution for simplifying the

maintenance and management of your inventory model as your business evolves.


28/38

Chapter 6 Conclusion



29/38


Relatedreading

Related reading

Configurator documentation

Overview documentation

$SBNFS044 Concepts Guide


Amdocs Cramer Configurator Release Notes

Administration documentation

$SBNFS044 System Administration Guide

Amdocs Cramer Configurator Prerequisites Guide

Amdocs Cramer Configurator Installation and Upgrade Guide

User documentation

Amdocs Cramer Configurator User Interface Guide

Amdocs Cramer Configurator User Task Guide

Amdocs Cramer Configurator User Reference Guide

Documentation is distributed through licences. For example, you must have the CustomizationKit licence beforeyou receive the Configuration documentation and API documentation.


30/38

Related reading



31/38


Glossary

Glossary

Active dataset The dataset that is currently active. The active dataset is the one whose name appears

to the right hand side of the status bar. It has a red right-arrow to its left in theResource browser, Dataset tab. Its contents populate the wizard lists. In views, theitems in the active dataset appear with no color, items belonging to its sub-datasetsappear in the same color as the sub-dataset itself.Note. The existence of multiple datasets and sub-datasets is applicable to only theConfigurator (Advanced option pack).See Dataset.

Active version The version of the active dataset that is currently active. The name of the active versionof a dataset appears to the right hand side of the name of the active dataset, in the statusbar. The red right-arrow still appears to the left of the active dataset in the Resource

browser, Dataset tab. Few wizards are available for use when an active version has beenselected. The information you see in the view, WebReports and homepages reflect themetadata as it had been at the point in time when the version was created, read-only.See Active dataset.

Alias An alias is another value for an instance of metadata. You can use an alias to overridecertain values of the metadata in a sub-dataset. This feature is applicable to only theConfigurator (Advanced option pack).

API Application Program InterfaceAn API is the specific method prescribed by a computer operating system or by anapplication program (in this case, the Configurator) by which a programmer writing aprogram can make requests of the operating system or application program.

Browser icon Browser icons are the small icons that appear to the left of the names of items in theResource and relations browser frames.See also View icon.


32/38

Glossary


Change A change is any change made to a dataset. After one or more changes are made to adataset it can be given a version name. The Configurator keeps a complete history of

all the changes made to every dataset.

See Version.

Client A client is an instance of the Configurator that is running.

Color coding Colors help to understand the organization of the metadata that is on view in theConfigurator user interface.Each dataset and the items that belong to it are represented in the Configurator userinterface by the same color.The names of items in a dataset that have been deselected for export are shown in gray

in the Resource browser.

Compatiblerelease

Metadata in the Configurator comes from a specific Resource Manager release. TheConfigurator can hold metadata from different Resource Manager releases.Metadata in the Configurator is said to be compatible if the metadata comes fromResource Manager releases that are compatible. Resource Manager releases arecompatible if there has been no significant change to the Resource Manager data modelbetween releases. An example of compatible releases are Resource Manager 4.0 andResource Manager 4.0d.

Containing

dataset

A containing dataset is a discrete set of metadata that includes one or more other

datasets, known as sub-datasets. This feature is applicable to only the Configurator(Advanced option pack).See Sub-dataset.

Dataset A dataset is a discrete set of metadata. The Configurator (Advanced option pack)database can contain several sets of metadata simultaneously.The dataset is a concept relevant only in the Configurator and any intervening XMLfiles. When metadata is imported to a Resource Manager database, informationrelating to datasets, versions and aliases are discarded.

Dataset hierarchy A dataset hierarchy exists if a dataset has one or more sub-datasets. In turn these sub-

datasets may themselves contain sub-datasets. To see a dataset hierarchy either expandthe tree levels of a dataset in the Resource browser or open the Dataset View of adataset. This feature is applicable to only the Configurator (Advanced option pack).

Dataset type To help organize the Configurator metadata it is possible to define different types ofdataset, using the Dataset Type wizard. When different types of dataset exist, actualdatasets can be created. This feature is applicable to only the Configurator (Advancedoption pack).

Export Moving metadata from a Configurator database, a Resource Manager database or anXML file.


33/38



History The Configurator keeps a complete history of all the changes made to every dataset.See Change.

Homepage Homepages are displayed in the Views frame of the Configurator user interface. Eachhomepage provides details of the item and allows maintenance of the item.

Import Moving metadata to a Configurator database, a Resource Manager database or an XMLfile.

Initial version This version of a dataset is generated by the Configurator when a new dataset is created.It is usually empty. It is used in the WebReports and in the Export/Import wizard asthe beginning of the list of available versions of a dataset.

Latest version This is the most recent version of a dataset. It has the most up-to-date changes in the

dataset. It is used in the WebReports and in the Export/Import wizard (as the lastchoice) in the list of available versions of a dataset and in the Comparison WebReportas the most up-to-date version of the datasets against which to run the comparison.

Metadata Metadata is used in most of the $SBNFS044. It is data of a predefined value andbehavior that cannot be changed by users of the product suite. It is widely used inwizards, homepages and WebReports.

MMU Metadata Maintenance Utility.Tool used to manipulate the metadata of the Task Engine, the Delivery Engine, theRoute Finder and the Sync Engine.

Release See Compatible release.

ResourceManager

The Resource Manager is Amdocs Cramers inventory management tool. It waspreviously known as the Cramer Active Inventory Platform (AIP).

Resource

Managerdatabase

The standard database on which the Resource Manager runs.

Sub-dataset A sub-dataset is a discrete set of metadata that is included in another dataset, known asthe including dataset. This feature is applicable to only the Configurator (Advancedoption pack).See Including dataset.

Upgrade To upgrade a dataset means updating the metadata from one Resource Manager releaseto another.

Version After one or more changes are made to a dataset it can be given a version name. Thissnapshot of the dataset is known as a version of the dataset.See Change, Initial version, Latest version.


34/38

Glossary


View icon View icons are the icons that appear in views, in the Views frame.See also Browser icon.

WebReport These are typically sophisticated queries of the data model (in this case, theConfigurator data model) visualized using a combination of text, hypertext andgraphics. WebReports combine visual and textual information for you to explore.

XML eXtensible Markup LanguageXML is a way to create common information formats and to share both the format andthe data on the World Wide Web, intranets, and in the case of the Configurator,between the Configurator and Resource Manager databases.


35/38


Index

A

Access permissions ........................................... 14Active dataset ........................................... 10, 12

Active version ................................................... 11Attribute tables ................................................... 3Automating delivery .......................................... 1

B

Behaviors .......................................................... 12Bitmap .............................................................. 12Browser

Relations .................................................... 18Resource .................................................... 18

C

Colour coding .................................................. 13

Compatible ....................................................... 11Compatible releases ......................................... 10

D

Data model ......................................................... 3Database .............................................................. 3Dataset ..................................................... 10, 11Dataset management .......................................... 4Developer tools .................................................. 7

Application Program Interface (API) ........ 7Configurator ............................................... 7Migrator ...................................................... 7

Differences ........................................................ 12

E

Export ........................................................ 6, 11

F

FramesViews frame ............................................... 18WebReports .............................................. 18Wizards ..................................................... 18

H

History .............................................................. 11

HTML ............................................................... 12

I

Icons .................................................................. 12Import ............................................................... 11Include .............................................................. 12Integrity ....................................................... 1, 4Inventory

Management ............................................... 5

L

Live data ..................................................... 9, 11

M

Metadata ............................................................. 4Multiple datasets ................................................ 2

OObjects ................................................................ 9Oracle .................................................................. 1OSS ...................................................................... 5

P

Provisioning ....................................................... 1

R

Relations browser ............................................. 18Remote server ................................................... 11Resource browser ............................................. 18Rules .................................................................... 6

S

Security ............................................................... 4Sequence ........................................................... 19

T

Tasks ................................................................... 3Templates ........................................................... 3

U

Upgrade ..................................................... 4, 11User interface .................................... 9, 12, 17

Relations browser ..................................... 18

Index


36/38

Index


Resource browser ...................................... 18

V

Version .............................................................. 11Version control .......................................... 2, 10Views ................................................................. 20

Frame ......................................................... 18Visualize ....................................................... 1, 4

W

WebReports ...................................................... 19Frame ......................................................... 18

Wizards ...................................................... 3, 19Frame ......................................................... 18

X

XML ........................................................... 6, 11


37/38


38/38

Cramer, Amdocs OSS DivisionCramer House

The SquareLower Bristol Road

BathUnited Kingdom

BA2 3BHTel: +44 (0) 1225 471300

Fax: +44 (0) 1225 471301

configurator 4.0 concepts guide issue 1.0

Documents