Open APIs

 View Only
Expand all | Collapse all

Service Specification to Catalog Relationship on TMF633 Service Catalog Management API

  • 1.  Service Specification to Catalog Relationship on TMF633 Service Catalog Management API

    Posted Apr 12, 2022 10:50
    Edited by Florian Kammermann Apr 13, 2022 11:01

    We have to federate multiple Catalogs into one Catalog. This means that there are multiple decentralized Catalogs, which will be accessible over one TMF633 API.
    In the API Spec I see that it is possible to retrieve multiple Catalogs TMF633_ServiceCatalog/TMF633-ServiceCatalog-v4.0.0.swagger.json at master · tmforum-apis/TMF633_ServiceCatalog

    As an example I have the following catalogs with the following entries.
    THIS IS JUST PSEUDO JSON, NOT TMFORUM COMPLIANT

    {
      "servicecatalogs": [
        {
          "catalogname":"ServiceCatalogA",
          "servicespecifications":[
            "TestService1","TestService2","TestService3"
          ]
        },
        {
          "catalogname":"ServiceCatalogB",
          "servicespecifications":[
            "TestService4","TestService5","TestService6"
          ]
        },
        {
          "catalogname":"ServiceCatalogC",
          "servicespecifications":[
            "TestService7","TestService8","TestService9"
          ]
        }
      ]
    }
    



    Now I want to expose all ServiceSpecifications over one TMF633 endpoint.
    And I also want to know which ServiceSpecification is sourced from which Catalog.

    Where is the Information, to which Catalog a specific Service Specification belongs, I can not see this information in the API Spec.
    Or what is the idea of retrieving multiple Catalogs over one TMF633 endpoint?



    ------------------------------
    Florian Kammermann
    Swisscom AG
    ------------------------------


  • 2.  RE: Service Specification to Catalog Relationship on TMF633 Service Catalog Management API

    TM Forum Member
    Posted 29 days ago
    Hi Florian
    I'm not sure that the current API design for the P/S/R catalogs supports catalog federation. For example, there is nothing in the model of the Catalog entity that exposes an endpoint for accessing the catalog.
    My understanding of the Catalog entity is that it allows you to have multiple logical catalogs over a single physical implementation, where each catalog exposes different catalog items (ultimately this means Service Specs in TMF633, or Product Specs and Offerings in TMF620). The same service spec could be exposed in multiple logical catalogs.
    Hope it helps

    ------------------------------
    Jonathan Goldberg
    Amdocs Management Limited
    Any opinions and statements made by me on this forum are purely personal, and do not necessarily reflect the position of the TM Forum or my employer.
    ------------------------------