CloudBlue is committed to providing high-quality, cost-effective solutions to our customers. As new technologies emerge, the demand for older product versions and components decreases. Accordingly, as we continue to address our customers' needs by introducing new products and services, we also periodically end support for older software versions.
We are going to remove C++ Domain SDK and plugins from the platform in the next major release. The latest information regarding the EOL timeline will be provided in this article, which will be updated periodically, and in the platform release notes.
Meanwhile, we encourage you to migrate from the existing C++ domain-registering plugins to the domain-registering plugins developed with the use of PHP Domain SDK. After migration, you will be able to apply plug-in updates faster and without platform downtime thanks to the fact that the PHP plugin does not require platform recompilation for upgrade installation. You can find more information on this in the “Migration steps overview” section below. End of support conditions are described in our Product Lifecycle Policy.
Migration steps overview
Important: Migration from the C++ plug-in to the PHP plug-in should be performed within the same registrar.
The PHP plug-in should support the InceptDomainFromCppSdk method which is mandatory for migration, as the method should transform domain data from the format used by the C++ plugin to the format used by the PHP plug-in.
- The following table shows domain registrars currently supported in CloudBlue Commerce and the availability of plugins (C++ and PHP), and indicates support of the migration to the PHP plugin:
| Registrar | C++ plugin available | PHP plugin available | Supports migration from the C++ to the PHP plugin |
|---|---|---|---|
| eNom | yes | yes | yes |
| GoDaddy | yes | yes | yes |
| InterNetX | yes | yes | yes |
| Nominet | yes | yes | yes |
| OpenSRS | yes | yes | yes |
| RuCenter | yes | yes | yes |
| WebNIC | yes | yes | yes |
| CentralNIC | yes (name is EPPRegistrar) | yes (developed by SCIT) | yes |
| EPAG | yes (name is EPNIC) | no (not planned) | - |
| Melbourne IT | yes (developed by SCIT) | no (not planned) | - |
| LogicBoxes | no | yes | - |
| Openprovider | no | yes | - |
| RRProxy | no | yes | - |
If CloudBlue Commerce provides the PHP plugin for the registrar you are partnering with, the high-level migration plan will be the following:
Deployment of the PHP plugin in lab and production environments (including deployment of the PHP SDK Runtime service node). The PHP SDK Runtime service node should be added only once. It will be used for all PHP SDK-based plug-ins.
Test migration performed in a lab environment.
Migration performed in a production environment.
- Ask your TAM for more details.
- If CloudBlue Commerce does not provide a PHP plug-in for the registrar you are partnering with, you must develop a PHP SDK-based plug-in first. Ask your sales representative if you want the CloudBlue team to develop the plug-in for you.