DX NetOps

 View Only
  • 1.  REST API Global Collection creation issues

    Posted Sep 02, 2015 08:43 AM

    We're trying to create global collection models using REST API but only the first request is seen in the explorer tab. The subsequent requests seem to be updating the previously created model instead of creating a new one.


    The first request is this:


    The second request is almost the same as the first one, but we only change the name of it:


    It looks as if One click was not updating the models view  in the Explorer tab, but also after restarting Tomcat, I'm still seeing only one model. Another thing I noted is that the created model's uniquekey attribute is empty.











    Any idea? I've seen this in Spectrum 9.2 as well as in Spectrum 10.

  • 2.  Re: REST API Global Collection creation issues

    Broadcom Employee
    Posted Dec 29, 2015 10:01 AM

    I tested this out and you do have to create the global collection with a two step process. The first URL you are going to use to get the unique Global Collection ID. You can do this with the following URL:




    Your going to get a response that looks like the following:


    <?xml version="1.0" encoding="UTF-8"?>

    <action-response error="Success" xmlns="http://www.ca.com/spectrum/restful/schema/response">

    <attribute id="0">56786f82-44da-1007-0351-00505686075a</attribute>



    What you want to do is take the attribute value which contains the unique global collection id and we are going to use that to populate the 0x12e56 attribute vaule in the following URL:




    When creating the second global collection you will need to send the action to the server again and use the new global collection unique id to create the second global collection

  • 3.  Re: REST API Global Collection creation issues

    Posted Jan 04, 2016 10:06 AM

    Yes, that's the way to do that. You need to get the unique key first and then you create the new GC.


  • 4.  Re: REST API Global Collection creation issues

    Posted Mar 19, 2018 06:53 AM

    Sorry to resurrect this old thread, but this is very useful, thanks. I created a global collections for almost a year now and didn't really use the ID, but instead used a unique string usually associated to the global collection. Does anyone know if you have to use the unique ID? What actually happens under the hood? Is it just a unique string? I assume you can put any unique Id as long as it is unique and you don't use it anywhere else? I'm keen to use the unique ID method explained here but just trying to find out how it is connected to anything else. We had some issues with unique keys and CA PM so want to make sure I'm using the 'CA way'.

  • 5.  Re: REST API Global Collection creation issues

    Posted Sep 17, 2018 10:54 AM

    Years ago, before this thread, I spent a few days playing with Global Collection creation and had issues because I couldn't figure out how to create this unique id. I forgot what exactly, but I believe when you try to link multiple landscapse GCs back to the master model there are issues.