Spectrum Modelinggateway pros and cons


Article ID: 197423


Updated On:


CA Spectrum CA eHealth


What are the pros and cons of the Modeling Gateway?


Release : 10.4.2

Component : Spectrum Core / SpectroSERVER


There are limitations to what can be exported via the modeling gateway which are known and cannot be overcome, so it is not always a good idea to use it for upgrading or migrating.  Instead it is should be used for export of more specific models.

The pros & cons of Modeling Gateway are:

It removes any and all prior SS modeling database (SSdb) corruption.
Most modeling is retained (Global Collections, Services, Policies (but not Service Policies), device modeling/connectivity)
You can utilize “Huge Landscape Handle” functionality.

Loss of all previous catalog changes. These include Watches, changes made via Model Type Editor (MTE), attributes mapped from importing mibs in MibTools, and changes made in Attribute Editor when selecting “Save as Default”
Loss of events and alarm history.
Loss of NCM capture and SPM Test Results data.
Administrative time to compare/reconfigure customizations and integrations.


Additional Information

Modeling Gateway Toolkit