Professional Documents
Culture Documents
RELEASE 8.1
Release: 8.1
Publication Date:
Catalog Number:
Information Security: Level 2 – Sensitive
Created: 31/01/2010 10:22:00 AM
Account/FOP:
Author:
Editor:
Last Edited: 12/03/2010 10:07:01 AM
File Name: Amdocs OSS8.1 - Sync Engine Product Description.docx
Template: Product.dotm
4 Licensing Information..................................................................................................... 11
Sync Engine is integrated with Amdocs Resource Manager and with Adapter products. In
addition, Sync Engine is a key part in many productized Amdocs Data Integrity
Management solutions that include Discovery Engine and technology and vendor packs.
The following diagram shows Sync Engine as part of the Amdocs OSS portfolio.
Resource Manager
Ensuring Accuracy of Resource Manager inventory records is the primary function of
Sync Engine. This can be achieved through generation of discrepancy reports allowing
users to resolve data or implementation issues. Alternatively Sync Engine can also
implement customer specific business rule to automatically update Resource Manager
using the standard API and DesignRecords.
Data Integrity Management Solutions
DiscoveryEngine provides an option to use a dedicated platform to assist in integration
with network data sources such as management systems (NMS), element managers
(EMS), sub-network managers (SNM) and other equipment vendor interfaces.
Through the integration of Sync Engine, Discovery Engine and packs, Amdocs offers a
number of pre-integrated Data Integrity Management solutions for major technologies
and network equipment types.
Adapters
Sync Engine can use adapters to manage the access to external systems and also the
translation of data to a format Sync Engine understands. Sync Engine can interact with
adapters either by scheduling batch sync processes and requesting scoped data from the
adapter, or by allowing the adapter to send data on an event basis. In either case, the
adapter is required to supply data in UDM format.
A synchronization run can be started, paused, restarted and abandoned at specific points
during the execution through both the user interface and the API.
Configurable synchronization rules
Sync Engine uses profiles that set the scope of the synchronization. Each profile may
contain one or more rules, where each rule will specify a domain, the object class of
interest (devices, for example) and either a filter or a list of object instances.
Each rule may have include and exclude conditions attached. For example a rule might
specify a circuit type filter in the “Management System A” domain and an include
condition might specify that only “in service” circuits are to be synchronized.
Finally a rule will specify which details and attributes of the object should be returned.
For example, for a device, you may want to request just attribute information, or even the
full structural information including contained nodes, shelves, slots, cards and ports.
Manual, semi-automatic and fully automated synchronization
Differences can be automatically updated in the Resource Manager database, manually
applied after user intervention, or converted to a DesignRecord to drive a network update
(in the event that the network configuration is incorrect).
Scheduled synchronization
Synchronization runs can be initiated manually through the Sync Engine user interface,
through the API, or automatically launched at specific times using the Sync Engine
scheduler. Synchronization runs can then be scheduled to execute outside office hours or
during periods of low activity.
Event-based synchronization
The capability to support event-driven synchronization enables the update of the
Resource Manager inventory to be driven by external system requests. A Sync Engine
synchronization process can be initiated by an external system. Object creation,
modification and deletion events are supported.
Flexible object model synchronization
Sync Engine is able to automatically update the Resource Manager inventory even where
the information available from the network describes physical equipment types or
physical equipment configuration that is not currently modeled in Cramer.
Under certain circumstances an external system may define both the configuration and
the structure of an inventory object. Typically this is the case for distribution frames (for
example DDFs and ODF), where frames are managed by inside-plant engineering
systems. Unlike devices such as routers and switches, a distribution frame‟s structure
may change and expand as engineers require additional connectivity.
Supports network domains
Resource Manager contains inventory data spanning many different technologies and
sub-networks. The Domain object is used to capture the set of network elements that are
meaningful to a network management system or other external source of configuration
information.
Domains can be defined as either management or sub-network. Management domains
typically specify the complete set of elements under the control of the external system.
Views
Sync Engine does not provide any additional Views.
WebReports
Synchronization WebReport
The Synchronization WebReport is provided to enable the user to view the results of a
one or more synchronization processes. The synchronization process results can be
filtered and organized. Where synchronization results have not been automatically
processed, users can launch the appropriate wizards to process them.
Wizards
Domain Wizard
This wizard enables objects in the Resource Manager to be placed in one of two domain
types, management domains and sub-network domains.
Sync Profile Wizard
This wizard defines the rules and filters to be included in a synchronization process.
Sync Rule Wizard
This wizard defines which objects are to be synchronized and more specifically, which
attributes are to be compared.
Homepages
Each Sync Engine instance object: Domains, Sync Processes and Sync Diffs: has
HomePages.
Adapter
This is a piece of software that has to be written for each external system with which the
Resource Manager is to synchronize. An adapter contains all the objects in the NMS that
can be synchronized.
DesignRecords
A DesignRecord describes a change that has been made to the network model in
Resource Manager. For example, a change record is created when a user specifies a new
device. DesignRecords also provide roll-back and auditing capabilities.
Differences
A difference is a single difference found in the data that is held by both the Resource
Manager and an external system. There are many types of difference and each has an
associated type.
Domain
Two types of domain are used in the Sync Engine: management domains define a set of
objects in an external system for which the Resource Manager holds inventory; sub
network domains define a subset of these sets of objects.
External system
A system that is external to the Amdocs OSS Suite and that holds application specific
inventory information.
NMS
Network Management System
Sync diff
See Differences.
Sync diff filter
A sync diff filter is the final refinement to a synchronization that you can add. Sync diff
filters exclude particular differences or objects from the Synchronization WebReport.
Sync profile
There are two types of sync profile, single and group.
A single sync profile is a means to group sync rules and generic sync diff filters together
to refine the amount and type of information that is required from a synchronization. A
single sync profile cannot contain any other single or group sync profile.
A sync group profile is a means to group single sync profiles together to combine the
different requirements of single sync profiles for the synchronization. A sync group
profile cannot contain any other sync group profile.
Sync rule
A sync rule is a means of identifying a particular object that should be included or
excluded from synchronization. You group sync rules together in a sync profile to make
complex conditions for including or excluding objects from synchronization.
Topologies
Network elopements and their connectivity can be grouped in to Topologies to represent
a logical network region or entity. For example, optical networks may be rolled out in
rings to provide redundant routes. These rings can be described by a Topology.
Topologies may then be used to provide context to automation processes (primarily Task
Engine and Route Finder) and also to offer users additional subjects for views and
reporting.
UDM Unified Data Model
UDM is the means by which Sync Engine can exchange information with external
systems, usually Network Management Systems (NMS). It is a standardized XML
description of network inventory information.
XML Extensible markup language
XML is a flexible way to create common information formats and share both the format
and the data between computers in a consistent way.