Handling of Product Models

The procedure of handling product models has been updated.

Catalog service reads the product models, divides them into a single model, and then sends each product model to either JMS queue or REST endpoint. For a particular file, if there are many models and those all are processed as a bulk in a single instance, then there is a huge load on that instance of catalog service. To distribute the load, the catalog service now reads the models and republishes them across different instances.

The Catalog service endpoints have been updated as follows:

Action Model APIs

  • Get Bulk Action Model

    Endpoint: http://<host_address>:<port_address>/v1/actionModel/bulk

    Method: GET

  • Submit Bulk Action Model

    Endpoint: http://<host_address>:<port_address>/v1/actionModel/bulk

    Method: POST

  • Delete Bulk Action Model

    Endpoint: http://<host_address>:<port_address>/v1/actionModel/bulk

    Method: DELETE

Plan Fragment Model APIs

  • Get Bulk Plan Fragment Model

    Endpoint: http://<host_address>:<port_address>/v1/planfragmentmodel/bulk

    Method: GET

  • Submit Bulk Plan Fragment Model

    Endpoint: http://<host_address>:<port_address>/v1/planfragmentmodel/bulk

    Method: POST

  • Delete Bulk Plan Fragment Model

    Endpoint: http://<host_address>:<port_address>/v1/planfragmentmodel/bulk

    Method: DELETE

Product Model APIs

  • Get Bulk Product Model

    Endpoint: http://<host_address>:<port_address>/v1/productmodel/bulk

    Method: GET

  • Submit Bulk Product Model

    Endpoint: http://<host_address>:<port_address>/v1/productmodel/bulk

    Method: POST

  • Delete Bulk Product Model

    Endpoint: http://<host_address>:<port_address>/v1/productmodel/bulk

    Method: DELETE