This section covers backwards compatibility between Oracle Communication Services Gateway 4.1 and 4.1.1. The following areas are discussed:
Upgrades from Services Gatekeeper 4.0/4.1 to 4.1.1 are supported. The upgrade process can be managed using the rolling upgrade mechanism unless your installation uses SIP, Native SMPP, or the RESTful facade, in which case a restart is necessary. Scripts and tools to facilitate upgrade and migration of data are provided.
Between 4.0 and 4.1 some account management operations were changed to accommodate the new SLA Types. Older methods continue to work, but are deprecated. Some plugin routing operations have changed to accommodate the new tier routing mechanism. Full documentation is available in Managing Accounts and SLAs and Integration Guidelines for Partner Relationship Management, separate documents in this set.
If you are upgrading from 4.1 to 4.11, there are no changes.
Database schemas were changed between 4.0 and 4.1. If you are upgrading from 4.0 to 4.1.1 you will need to run the supplied data migration scripts. There are no schema changes between 4.1 and 4.1.1.
Between 4.0 and 4.1, the Service Level Agreement mechanism was expanded. Old SLAs will continue to work, but will not be synchronized across geographically remote sites regardless of the setting of the <enforceAcrossSites> tag, which has been deprecated.
|Note:||These changes only affect those upgrading from 4.0 to 4.1.1. There are no SLA changes between 4.1 and 4.1.1.|
As a result of these changes, there are several account management operations that have been changed, and earlier operations have been deprecated, both at the console (MBean) level and at the PRM Operator Service level. The deprecated operations in the console include:
For more information on these changes, see “Managing SLAs” in Managing Accounts and SLAs, a separate document in this set.
The deprecated operations in the Operator Service interface of the PRM include: