Renaming
...
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 involve, among other things, renaming of Databasedatabase(s) and change changes to database schemas.
If the partition is located in our AWS Pricefx hosting infrastructure, this can only be achieved by migrating the whole solution to a new AWS Instance instance prepared with the new name(s). This is to safeguard against Database 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
...
needs to be changed both on Pricefx side and
...
customer side.
...
If you
...
access Pricefx through one of
...
the APIs, change of authorization is needed on both sides.
...
If your configuration uses bound call, this needs to be changed
...
.
You need to provide a maintenance window for this
...
change.
Renaming of Partitions partitions is complex, it is time consuming (depends depending on the volume of data in the database) and most likely involves work of an Integration Engineer and a Configuration Engineer.
Therefore, change changes of Partition partition names are subject to invoicing based on Time time and Materialmaterial.
Our Pricefx TechOps team can provide a time estimate ahead of the order.
Renaming
...
Entire Cluster or Instance
Generally, we use the term Cluster about cluster for customers on Bare Metal bare metal infrastructure and we use the term Instance instance for customers on AWS the hosting infrastructure.
The steps taken to change name of a Cluster or a Instance is the cluster/instance names are the same as with changing Partition Namesfor partition names. But in addition to the above, the customer needs to be aware of the following constraints:•
The
...
access URL changes
...
, so modifications of everything using this
...
URL (single sign-on
...
including SAML certificate, some integration configurations) are needed.
...
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)
...
.
You need to provide a maintenance window for this
...
change.
Renaming of Clusters clusters and Instances instances is complex, it is time consuming (depends depending on the volume of data in the database) and most likely involves work of an Integration Engineer and a Configuration Engineer.
Therefore, change changes of Cluster cluster or Instance instance names are subject to invoicing based on Time time and Materialmaterial.
Our Pricefx TechOps team can provide a time estimate ahead of the order.