Skip to main content

Pixi integration

Codept provides integration with Pixi platform since fair amount of merchants use it in their business flow.

Pixi itself exposes data flow to applications through Pixi Messaging.

About Pixi Messaging#

Messaging enables software applications to connect and scale. It is asynchronous, decoupling applications by separating data sending and receiving.

Pixi Messaging is based on AMQP protocol, using RabbitMQ as broker which supports Pixi's messaging infrastructure.

Process behind Pixi Messaging (from official Pixi documentation)#

  1. Producers of events (notifications, messages), which can be the pixi database, pixi Web application or pixi apps, will post messages to one or more MQexchanges named pixiEX... (example pixiEXInvoiceCreated) on localMQ.
  2. Messages from any MQexchange on localMQ will then as soon as possible be shovelled to MQexchange on cloudMQ.
  3. In cloudMQ you then have to create a queue (also multiple queues are possible) and bind it to the proper MQexchange or more MQexchanges depending on the message type (topic or fanout).
  4. You then need to configure your application(s) to listen to the queues, in order to process the information further.

For additional information, see Pixi messaging documentation.

Codept integration with Pixi#

Codept integration with Pixi is done by listening specific RabbitMQ queue, depending on a type of business process, and reacting accordingly. Once the business logic is executed on a Codept side, it will update the Pixi order data through Pixi's SOAP endpoints. If any of the incoming messages fails for any reason, be it JSON parsing/serialization or data validation, it will be persisted as failed message. Otherwise, it will proceed with business logic.

Edit this page