Layer7 API Management

  • 1.  Portalman sync service not getting called

    Posted Jun 10, 2017 08:25 AM

    Hi,

     

    I have one cluster api1.company.com and a portal is synced to this.I got other cluster network to configure api2.company.com but it should also connect to same portal.

    I have installed and configured everything, but still portalman sync service is not getting called.

     

    Can you please help me where could be the issue.

     

    Thanks,

    Ravish



  • 2.  Re: Portalman sync service not getting called

    Posted Jun 10, 2017 11:35 PM

    Do you mean both gateway clusters connecting to one portal ?



  • 3.  Re: Portalman sync service not getting called

    Posted Jun 10, 2017 11:42 PM

    Yes.



  • 4.  Re: Portalman sync service not getting called

    Posted Jun 10, 2017 11:44 PM

    what version of the portal are you running?



  • 5.  Re: Portalman sync service not getting called

    Posted Jun 10, 2017 11:52 PM

    Gateway version: 9.0

    Portal Version: 3.5



  • 6.  Re: Portalman sync service not getting called

    Posted Jun 10, 2017 11:54 PM

    i don't think its possible to have two gateway clusters integrated with one portal



  • 7.  Re: Portalman sync service not getting called

    Posted Jun 11, 2017 12:02 AM

    This is our QA cluster which is connected to portal.

    We have two other dev cluster, these two are also connected to the same portal.

    Note: When we push any API to QA cluster, then only the API is getting displayed to portal.

    But sync service gets called to dev cluster also due to which I am able to call API portal snippet.

    Like these dev cluster, i want my new QA cluster also to be configured and sync service to be called.



  • 8.  Re: Portalman sync service not getting called
    Best Answer

    Broadcom Employee
    Posted Aug 04, 2017 03:46 PM

    This is possible, but only supported by CA Professional Services as a customization. You may need to reach out to CA Services for further assistance with your use case.