Renaming of single partition
Renaming of a single partition involves several steps requiring the partition to be off-line for a lengthy period of time. This requires a maintenance window.
The steps needed involves among other things renaming of Database(s) and change to database schemas.
If the partition is located in our AWS infrastructure, this can only be achieved by migrating the whole solution to a new AWS Instance prepared with the new name(s). This is to safeguard against Database corruption.
As a customer, you need to be aware of the following constraints:
• Any Partition name must be unique cluster-wide
• As the Partition name is part of the authorization for Integration, Integration authorization would need to be changed on Pricefx side and Customer side
• If you are accessing Pricefx through one of our API’s – again this would require change of authorization on both sides
• If your configuration uses bound call, this needs to be changed to
• Provide a maintenance window for this Change
Renaming of Partitions is complex, it is time consuming (depends on the volume of data in the database) and most likely involves work of an Integration Engineer and a Configuration Engineer.
Therefore, change of Partition names are subject to invoicing based on Time and Material.
Our TechOps team can provide a time estimate ahead of the order.
Renaming of entire cluster or Instance
Generally, we use the term Cluster about customers on Bare Metal infrastructure and we use the term Instance for customers on AWS infrastructure.
The steps taken to change name of a Cluster or a Instance is the same as with changing Partition Names. But in addition to the above, the customer needs to be aware of the following constraints:
• The Access URL changes – requires modification for everything using this url (single sign-on incl. SAML certificate, some integration configurations)
• Pricefx needs to issue a new TLS/SSL Certificate for accessing Pricefx applications
• If Pricefx integrates to a webservice managed or provided by the customer, the customer needs to forward a new TLS/SSL Certificate for this service to Pricefx
• Configuration of Forwarding url needs to be changed (if used)
• Provide a maintenance window for this Change
Renaming of Clusters and Instances is complex, it is time consuming (depends on the volume of data in the database) and most likely involves work of an Integration Engineer and a Configuration Engineer.
Therefore, change of Cluster or Instance names are subject to invoicing based on Time and Material.
Our TechOps team can provide a time estimate ahead of the order.