Assets / Assets / IT Asset Manager
Assets / Enterprise Assets / IT Asset Manager
Assets / Telecom Assets / Telecom Management

Migrating Archibus Client/Server Telecom Assets: Data

Migrating Archibus Windows Client/Server telecom data is a two-step process:

• Migrate the data (covered in this topic)
• Migrate the floor plans. Note that you must migrate the data before migrating the floor plans.

The AbCommonResources-BasicRules_TelecomDataMigration rule migrates the data. It converts:

• Card and Network Device records to Equipment records.
• Card Standard and Network Device Standard records to Equipment Standard records.
• Card Port and Network Device Port records to Equipment Port records.
• Punch Block and Punch Block Standard records to Patch Panel and Patch Panel Standard records
• Records in the Connections table to corresponding fields in the Jacks, Equipment, Equipment Ports, and Patch Panel Ports tables.

For information on how fields are exactly mapped to new tables, see Migrating Client/Server Telecom Assets: Field Reference.

Procedure

1. Run the migration rule with these methods:
   • Select the System / Add In Manager / Run Basic Rule Wizard task and choose the AbCommonResources-BasicRules_TelecomDataMigration rule.
     -- OR --
     
   • From the browser, type: http://localhost:8080/archibus/ab-single-job.axvw?ruleId=AbCommonResources-BasicRules_TelecomDataMigration
2. The system runs the rule and alerts you when it has completed.
3. Review \users\public\archibus\WEB-INF\config\archibus.log file for any migration problems. To find the changes made by the routine, search the log file for BasicRules_TelecomDataMigration. All the changes will be in this section of the archibus.log file.

If Primary Key Values Exist in the Equipment or Patch Panels Table

When migrating data from the Network Devices and Cards tables to the Equipment table and from the Punch Blocks table to the Patch Panels table, the conversion routine considers the possibility that the IDs to be migrated already exist in the target tables. For example, you have Card 100 and Equipment item 100.

If a primary key already exists, the routine adds a suffix to the existing ID, following this convention:

Table	Suffix to Add
Network Devices	NETDEV
Cards	CARD
Punch Blocks	PB

Typically, you will run this routine only once and convert all your data at one time. However, the program does accommodate multiple executions of the routine. For example, suppose you run the migration the first time, and the program migrates network device 1111 to equipment 1111. On a possible second execution, the routine will think of equipment 1111 (the network device) as a duplicate and will proceed to add 1111-NETDEV.

To minimize the risk of this behavior, the program checks both the eq_id and eq_std fields. If these are the same, the program does not insert a new record with a suffix.

Example

The program sees a network device with netdev_id 1000 and standard CISCO-SW48.

Suppose in the Equipment table, you also have eq_id 1000 and standard HP-SERVER.

In this case, on the first run the program would create a new eq_id of 1000-NETDEV and transfer the ports to this item. If you run the routine a second time, the routine makes no change since one equipment ID with the suffix has already been created.

In summary, the program checks the ID and the Standard. If both are duplicate, there is no need to migrate the asset. If they are different, then the program will create a new record with the suffix as shown above.

See Also

Migrating Telecom Data Developed in Client/Server to Web Central (Overview)