Workflow to handle deployment failures
Stages
The following workflow outlines the high-level steps necessary to handle a deployment error that may cause the NFM-P database to be out of synchronization. See the XML API SDK Sample Code Navigator for sample XML scripts.
1 |
Clear the deployment. The XML configuration request uses the GenericObject method clearDeployer on the specified deployerName which identifies the deployment to be cleared. |
2 |
Resynchronize the object that caused the deployment error. The XML configuration request to resynchronize the object using the generic.GenericObject.triggerResync method. Note: When you use the generic.GenericObject.triggerResync method for a specific <instanceName>, you can specify whether a resynchronization on the object is performed by setting the <resyncSelf> flag to true, or whether the resync is performed on its children by setting the <resyncChildren> flag to true. The NFM-P does not notify XML API clients when objects are resynchronized. |
3 |
Perform one of the following steps, depending on your XML API client implementation.
|
Note: Contact your Nokia OIPS technical support representative for information about how to manage deployment failures.