Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Current »

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 involve, among other things, renaming of database(s) and changes to database schemas.

If the partition is located in Pricefx 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 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 partitions is complex, it is time consuming (depending on the volume of data in the database) and most likely involves work of an Integration Engineer and a Configuration Engineer.

Therefore, changes of partition names are subject to invoicing based on time and material.

Pricefx TechOps team can provide a time estimate ahead of the order.

Renaming Entire Cluster or Instance

Generally, we use the term cluster for customers on bare metal infrastructure and the term instance for customers on AWS infrastructure.

The steps to change the cluster/instance names are the same as for 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 clusters and instances is complex, it is time consuming (depending on the volume of data in the database) and most likely involves work of an Integration Engineer and a Configuration Engineer.

Therefore, changes of cluster or instance names are subject to invoicing based on time and material.

Pricefx TechOps team can provide a time estimate ahead of the order.

  • No labels

Found an issue in documentation? Write to us.