Partition Overview

Partition Overview has the following sub-sections:

1 Log History
2 Job/Task Tracking
3 Event Admin
- 3.1 Event Configurator
4 Accelerators
- 4.1 Automatic Deployment of Plasma Accelerators
5 Upload Queue

Log History

Shows the log history for the given partition.

Job/Task Tracking

Shows all details on jobs/tasks executed at the Pricefx partition (e.g. calculation of Price Lists or LPGs).

In this section you can also define a notification on a specific job/task; for details see Account Notifications.

To see this section, you need to have the Partition Events/Jobs - read permission.

Event Admin

Shows all events generated by Pricefx (e.g. CALCULATION_COMPLETED_CFS).

To see this section, you need to have the Partition Events/Jobs - read permission.

It is also possible to re-run an event from here – if Retries Left = 0 and you have the Partition Events/Jobs - edit permission.

Event Configurator

You can also configure the events here (without having to access the partition). If you have the Partition Admin - Events permission, you will see the Event Configurator button at top.

Options:

Event Bitmask – Allows you to specify what events the partition should send.
Event to Kafka/MQ – Allows to select either QA or PROD version of the Message Queue (MQ) service where the events are sent. The versions need to match (RabbitMQ QA consumes PlatformManager QA and cannot see events from PlatformManager PROD).
If left empty, the setting is taken from the instance which will most likely be PROD instance.
Event URL – HTTP endpoint to which events from the partition are published. If left empty, no events are published.
Disable sending events through HTTP (Push) – See the explanation in Pricefx Unity documentation.
Email – Email address to which events from the partition are published.

For more details on these configuration options, see Server Events in Pricefx Unity documentation.

Accelerators

In this section you can see which Accelerators were deployed to a specific partition. For each record there are the following details: name of the Accelerator, its version, when it was deployed and by whom, and its status (finished, in progress, failed).

Assets with no deployments are not included.

For Accelerators in Failed and In Progress states it is possible to rollback the deployment and delete objects which were already deployed. Make sure these objects are not used by other configurations on the partition, otherwise they would stop working.

Automatic Deployment of Plasma Accelerators

Since the version 1.50 there is an automation job PlasmaPackageAutoDeploymentJob which deploys Plasma Accelerators to partitions based on a condition.

Prerequisites:

Instances have the Hurricane 9.0 version and newer.
Partitions are marked as 'Production' type in Salesfx.
Their associated Accounts have the Plasma flag set to opted-in in Salesfx.

How it works:

The job checks if it can communicate with a partition. If the technical user is not created, it will create it.
The job deploys the latest version of the two Plasma Accelerators (net.pricefx.accelerators:plasma-quote-processor, net.pricefx.accelerators:plasma-transaction-processor) at the partition.
The job removes the technical user if this account was not present there previously.

Upload Queue

In this section you can see a queue of all running/waiting data loads to the partition. This queue includes Data Uploads from PlatformManager UI, Accelerator data uploads, and other deployments from Accelerators (logics,…). With this overview you can prevent issues caused by large data being loaded into the partition simultaneously.

You can:

Force Stop Uploading all Data Uploads which are in progress. After that the Data Upload status changes to Canceled.
Remove from Queue all Data Uploads which are waiting.