iServer Data Exchange Capabilities
Generate Objects from Data Imported from Excel and XML
Information held in other other tools (such as Aris, Casewise,
Systems Architect and Planning IT), can be used to automatically
create new objects in iServer. Using Excel Spreadsheets or
XML data source formats, existing information can be regenerated
for use Visio models or can simply appear as a 'entity or object'
in an EA catalog or list. By aligning imported data to Visio
Shape Masters (notations) new shapes are created which are ready
for immediate use. Data Exchange is provided with a simple
wizard to walk users through the import process, no complex coding
or data configuration necessary. Extensive options in the
wizard can control the information being imported so a definitive
list of content such as an application inventory can be
maintained.
Synchronization with External Data Sources (Master Data
Management)
If a single tool is used as the master storage point for all
application artifacts, but the rest of the architecture is managed
in iServer, it is necessary and useful to reflect the application
artifacts within iServer - they need to be related to other aspects
of the architecture - but a simple one-off import is insufficient.
Firstly, because the other tool is the chosen storage point for
applications, and secondly because the imported copy would quickly
become out of date. Therefore iServer Data Exchange provides a
synchronization mechanism, where artifacts can be imported as
read-only, and periodically updated to reflect changes made in the
other tool. This is extremely useful whe
Bulk re-use of imported Objects
Rapidly and easily create new diagrams and deliverables by
re-using groups of imported objects using the shape explorer tool
and relate them to other aspects of the Enterprise
Architecture.
Import Relationship and Meta Data Held in Excel / XML
New or existing Enterprise Architecture information held or
created in iServer can be enriched by importing meta-data and
relationships from an Excel spreadsheet or XML data source.
Examples of imported data include interfaces between applications,
process to system information, cost and throughput metrics for
processes, asset data or platform / system inventory data
Bulk Data Refresh, Synchronization and Scheduling
Schedule automatic bulk updates of imported objects and their
meta-data from the master data store in order to ensure
consistency and data alignment of your Enterprise Architecture
content. Various options are available to control the
frequency, timing and requests or notification of the update or
refresh made.
Manage imported Objects
List, sort and manage imported objects, restrict editing (if
synchronizing with a master data store), delete and purge
options. Also you can specify import settings that will
determine how updates and conflicts are handled.
Bulk re-use of imported Objects
Rapidly and easily create new diagrams and deliverables by
re-using groups of imported objects using the shape explorer tool
and relate them to other aspects of the Enterprise
Architecture.