API Management

Get Involved. Join the Conversation.

Comments

  • Jairo Rojas Mendez

    We do the same for our on premise SOA and OSB process which are exposed as API for external consumption.

     

  • Sharath Chandra Gavini

    Hi Geetha,
    You can simply use conversation.variable('<variableName>'); from the custom component to access your variables.
    Please refer to this documentation for more information on SDK.
    Thanks,
    Sharath Chandra Gavini.

  • Geetha Devi

    Could anyone help me on this?

  • Ram Naresh Rayaprolu

    Why do we need to add header/line IDs? It is a bug from Oracle side. Moreover when updates are performed we might not get the IDs from the 3rd party system payload.

  • Milind Dalvi

    Try using ID's , header ID and Line ID in your payload.

  • Rakesh Soni

    I have resolved this issue.

  • Daniel Diaz

    Thanks for the replay.  the question would be..

    Can we document the service over there?  I already saw options to document through a uploaded file or manually eather by html, Markdown or APIARY option?

    The services will be expose as a SOAP and REST but currently consume by SOAP..

    So it is useful

    it is useful to register them as a REST in the API? can i do the governance by that way?

  • Viv

    You can expose services exposed through APICS however they need to be rest endpoints.  The idea should be to provide security , governance and control as well as using Apiary to document , test and help developers for discovery .

    We do the same for our on premise SOA and OSB process which are exposed as API for external consumption.

     

  • David Vanden Bussche

    Hi

    To fix this I had to add a root element in my api blueprint definition : 

    ## Tweet API Root [/]
    
    

    In APICS it was taking /tweet as the root element and was working with /tweet/tweet. In order to just pass /tweet we need to introduce the root element.

    Hope this can help you...

  • Patrick Bogers

    Hi Martin, 

    Is this a bug?

    From what I have understood from Oracle Support, this came back with build as designed. 

     

    Can you tell us more about it please?

    I can only tell you what the current functionality is when using swagger: 

     

    basePath  is concatenated behind the API Request Path. 

    So API Request path is: /api/v1/beers

    basePath in spec is : /api/v1/beers  will result in deployment on endpoint: /api/v1/beers/api/v1/beers instead of /api/v1/beers

     

     

     

     

    thanks

    Patrick

     

  • Patrick Bogers

    Hi Martin,

    Yes, that would be possible. Downside is that functionality such as method mapping based on Spec is not available

     

    Patrick

  • Martín Delis

    An additional comment. I realized that I can attach separately the documentation in the publication tab (to be used in the development portal). It works fine in this way so it is not now an impediment but will be good to know how it progress the discussion with the product management team.

     

    Thanks again

  • Martín Delis

    Hi Patrick,

       I'm having the same issue when I link the Apiary specification into the API. If I create a new API Without the Apiary specification, it works perfectly but as soon I link the Apiary specification into the API and redeploy it into the gateway, in run time I'm receiving a response code 405 Method Not Allowed

    { "msg": "Service method /resource is not allowed to accessed" }

     

    The Apiary specification was made in swagger 2.0. I've tried removing the basePath, host and schemes (all combinations). Also I tried changing the API Implementation (in the Request tab) but without success. The only success was simply removing the Apiary Specification (but the problem will come in the developer portal i we want to link the documentation to explain how to use the APIs...)

    • Is this a bug?
    • Can you tell us more about it please?

    I'm in the middle of an implementation for a customer and this is a blocker for us

    Thanks Mario Martín.-

  • Patrick Bogers

    Hi David,

    Now try this....set your api request endpoint to /tweet and the basePath to /tweet. Associate the spec to the api implementation and deploy.

    You will get a 405 on the /tweet  endpoint because it is actuallly accessible on /tweet/tweet 

     

    As for my expectations I consider this to be incorrect behaviour and it caused quite a few issues for our API Provider teams and I have raised an SR for it. 

    It turned into an Enhancement Request as this was built as specified by Development. This issue will be top of the priority list to discuss with Product Management.

    For now we instructed all our teams to remove basePath from specs and be carefull with deploying with specs associated

    thanks

    patrick

  • David Vanden Bussche

    Hi Patrick

    Thanks for your reply !

    Indeed , I have an Apiary spec linked to my API, when I unlink it and redeploy my API, it works !

    But , in your opinion, is this wanted behaviour ? 

    This is not the way I expect the combination Apiary + APIPCS should work, or am I missing something ?

    Can someone from Oracle reply also, to give some guidance on this one ?

    I uploaded a word doc with some screenshots..

     

    thanks!

    David

    apipcs.docx (337KB)