Layer7 API Management

 View Only
  • 1.  Unable to create new Application

    Posted Oct 04, 2019 02:29 PM
    We have Portal 3.5 with CR13 installed on 6 different instances of portal, however in one of the instance, I am unable to create any new application.  Here's the process I followed along with the screen shot of the error message:

    1. Click on Dashboard
    2. Click on Organization
    3. Click on 0 link in the Apps column
    Apps
    4. Click on Add Application button
    5. Fill the Application details as shown and click Next Step:

    6. Choose the Available API from the dropdown and accept the terms, then seeing this error message:


    I am unable to reproduce this issue on the other 5 environments.

    Not sure what's wrong?  catalina.out does not have much clue on this error.

    Appreciate your help to resolve this issue.

    If we already have an application, then I am able to assign a new API to the same perfectly fine, this issue happens only when creating a new Application.








    ------------------------------
    Muthugomu Rathnamswamy
    ------------------------------


  • 2.  RE: Unable to create new Application

    Broadcom Employee
    Posted Oct 07, 2019 07:57 PM
    Hi there, 

    have you opened a ticket with the support site, it seems like you have one portal that is behaving oddly and this would be a good place to start.
    In the meanwhile I dont see and error message in your screenshot.

    ------------------------------
    Head of Layer 7 Adoption team
    Broadcom
    ------------------------------



  • 3.  RE: Unable to create new Application

    Broadcom Employee
    Posted Oct 09, 2019 10:38 AM

    Aron, 

    I have this case in support. The problem is,  there is no errors, it looks like UI issue, wizard doesn't recognizes that we selected API. Save button doesn't do anything when clicked and logs are not writing any error since there is nothing to write 




  • 4.  RE: Unable to create new Application
    Best Answer

    Broadcom Employee
    Posted Oct 11, 2019 10:14 AM
    Just wanted to close this question : Fix for this was CR14