Migrating Telecom Data Developed in Client/Server to Web Central

Client/Server Telecom users will find that the Web Central Telecom Console provides the connectivity and tracing features previously available only in the Client/Server environment. The Web Central Telecom features use fewer tables and a different connection methodology than Client/Server. Therefore, users who want to use the telecom data developed in Client/Server with the Web Central Telecom Console will need to migrate their data to the Web Central format.

ARCHIBUS has developed workflow rules and LISP routines for converting database tables and CAD drawings that adhere to the standard ARCHIBUS schema. If you have customized the schema, you must work with an ARCHIBUS Business Partner to adjust the provided routines to meet your needs.

Note the following about the conversion routines:

Running these routines is a one-time process; once your data is converted you will not need to run these routines again.
In the V.23.1 and later projects, the database records and floor plans for building HQ have not been converted to the new format. Therefore, you might want to experiment with these floor plans and records to understand how the routines work.
The routines are designed for working on a standard, non-customized schema.

Warning: Before running these routines, verify that you have not customized the telecom hierarchy, the telecom inventory tables, or the operation of the connection feature. If you have made customizations, consult an ARCHIBUS Business Partner for help with the migration.

Warning: Before running these routines on your production database and floor plan drawings, run them on test databases and drawings and review the converted drawings and database records. In general, as with all data migrations, check your data for consistency and integrity before migrating.

Procedure

The process involves converting drawing and data assets. The basic steps are:

Prerequisite: Make a back-up of your database and floor plan drawings.

From Web Central, migrate the database records by running the AbCommonResources-BasicRules_TelecomDataMigration Basic rule. See

From the SmartClient Extension for AutoCAD, run the provided AutoLisp program for converting Client/Server-format asset symbols to Web Central-format asset symbols.
- See Migrating Telecom Data: Floor Plans.

Publish the updated floor plans as enterprise graphics.

Which Telecom Assets are Migrated?

Assets that require no migration

The following telecom elements remain the same in Web Central and require no migration.

Faceplates
Jacks
Patch Panels
Equipment
Patch Panel Ports
Equipment Ports

Assets that are not migrated

The Web Central system does not use the following tables. There is currently no migration path for these tables.

Cables
Cable Pairs
Wireways
Standalone Ports

Assets that are migrated

The routines migrate the following Client/Server elements. A field-by-field mapping is provided in Migrating Telecom Data: Field Reference.

This Client/Server table migrates to ...	this table in Web Central
Network Devices	Equipment
Network Device Standards	Equipment Standards
Network Device Ports	Equipment Ports
Punch Blocks	Patch Panels
Punch Block Standards	Patch Panel Standards
Punch Block Positions	Patch Panel Ports
Cards	Equipment
Card Standards	Equipment Standards
Card Ports	Equipment Ports
Connections table (afm_tccn)	corresponding fields in the Jacks, Equipment, Equipment Ports, and Patch Panel Ports tables