Previous provisioning APIs required knowledge of the underlying database, and were vulnerable to changes in the database schema.
CUPI provides a layer over the database to make the interface more stable.
CUPI is standards based. CUPI was developed by using the latest advances in web-based interfaces. It is a REST interface that
standardizes operations such as add, delete, and modify. The XML comes with standard XML schema definitions that are annotated
with information about what is in them.
Other product groups in VTG are developing REST-based interfaces, and as the interfaces converge this positions CUPI well
to fit in with them. REST interfaces also work well with Web 2.0 applications.
As a web-based interface, CUPI is independent of operating system and programming language and does not require any client
libraries to use.
Note: It is recommended to perform provisioning only on the Publisher server in Active-Active mode and on Subscriber (Acting
Primary) in case of cluster failover. The password change and password setting modification for User PIN/Web application should
be provisioned on Publisher server in Active-Active mode.