Is it possible to change the name of an interface or site once it is created?
Oracle B2C Service Interface, All versions
It is possible to change the site name, interface name, and interface vhostname after a site has been created.
All agents will need to be logged out of the interface when the rename is performed.
Renaming an interface will cause downtime while DNS finishes propagating, this typically takes an hour up to several hours. Please note that we have no insight or control over the DNS propagation. However, you can check https://dnschecker.org. This will help know when the name change has been propagated via DNS.
For more information on how this process works, refer to DNS Propagation – Explained.
The interface name and interface vhostname (end-user page url) affect the launch url. Therefore, interface renames will require all agents to log out and re-install the product from the new launch url.
In some cases, it may be necessary to test the interface rename on the test site first. However, be aware that the interface vhostname (end-user page url) should include "tst" (example: newname-tst1.custhelp.com) because if/when you implement the changes on the production site (newname.custhelp.com), the url will already be used if the "tst" is not included. It is not possible to use the same url on both the test and production site.
Once interface renames are completed on the production site, best practices suggest to refresh/re-create the test site(s) to have the changes implemented on the test sites.
Interface names only allow lowercase letters, numbers and the underscore character (_). Typical meta characters are not permitted in site names. (!@#$%^&*())
Renaming a site does not cause any downtime.
This action does not take DNS propagation.
There is no impact to the administration console, the customer portal, or the customer portal end user pages. Typically the process can require up to 30 minutes to complete. You can request this change to be made outside of business hours.
Once site rename is completed on the production site, best practices suggest to refresh/re-create the test site(s) to have the changes implemented on the test sites. Best practices also suggest to always keep the production site and corresponding test sites named the same. (example: newsitename, newsitename__tst1, newsitename__tst2)
Site names only allow lowercase letters, numbers and underscore character (_). Typical meta characters are not permitted in site names. (!@#$%^&*())
Please note, when there are post-update(upgrade) transactions still in process on the production site, we are unable to rename interfaces or site names until these have been completed. These processes can take up to 10 days to complete.
We also offer the option to first rename the interface on an existing test site, so that you can proactively evaluate the process to confirm there will be no impact.
To only change the interface vhostname (end-user page url), this task can be completed in the Configuration Assistant self-service tool.
To change the interface name and interface vhostname (end-user page url), submit a service request to Ask Technical Support.
Please Note: Oracle B2C Service Technical Support is not equipped to evaluate your site configuration and business practices and predict the impact of how renaming your site and/or interface name and interface vhostname may or may not impact your particular site. They are also not able to provide a dedicated agent(s) to join bridge calls or monitor processes while a change is taking place. Should this level of support be needed, please engage Oracle Consulting and/or consider Oracle Cloud Priority Support.