01-08-2017 11:21 PM - edited 03-01-2019 04:35 AM
Can we do end to end deployment of iwan hub and branch side in APIC-EM with APIs calls ?
Thanks in advance for help.
Solved! Go to Solution.
01-09-2017 01:02 AM
The short answer is: yes.
The long answer is: Depends on APIC-EM release you're using. In release 1.3, we 'unintentionally' exposed iWAN App APIs through swagger but disabled them in further releases. Additionally, the APIs are purely for internal use and are not supported and/or well documented. Not all of the iWAN App APIs conform to API governance model put in use for APIC-EM either and it was never the intention of iWAN App team to expose and support'em. For end-to-end development, one may have to use not only iWAN App APIs, but them in conjunction with others from other required services (E.g. inventory-manager-service). Such usage is the onus of API-based workflow developer and iWAN App team recommends usage of UI-based workflow for all operations.
Having said that, if you have a strong specific use-case for bypassing UI usage and develop a strictly API-based workflow, we can get you in touch with some wiser folks on and off this forum. aradford, qinzhou, do you want to take this up further?
01-09-2017 01:02 AM
The short answer is: yes.
The long answer is: Depends on APIC-EM release you're using. In release 1.3, we 'unintentionally' exposed iWAN App APIs through swagger but disabled them in further releases. Additionally, the APIs are purely for internal use and are not supported and/or well documented. Not all of the iWAN App APIs conform to API governance model put in use for APIC-EM either and it was never the intention of iWAN App team to expose and support'em. For end-to-end development, one may have to use not only iWAN App APIs, but them in conjunction with others from other required services (E.g. inventory-manager-service). Such usage is the onus of API-based workflow developer and iWAN App team recommends usage of UI-based workflow for all operations.
Having said that, if you have a strong specific use-case for bypassing UI usage and develop a strictly API-based workflow, we can get you in touch with some wiser folks on and off this forum. aradford, qinzhou, do you want to take this up further?
01-09-2017 05:34 PM
it probably makes sense to try to automate branch deployment rather than HUB, given the nature of the API (not officially supported) and that you only deploy a HUB once.
Automating policy, which is a more likely day-n operation is supported, and I have published examples of this.
Adam
01-17-2017 12:07 AM
I am from CMS team. We are working on APIC-EM integration with Serivce Fullfilment Portal(SFP). SFP is Cisco Internal tool which will be consuming API exposed by APIC-EM for different app(iWAN, Easy QoS, PnP etc).
I are using APIC-EM version 1.3.1.9. I came to know that API for APIC-EM Apps will not be exposed in next releases.
I would like to know the road-map for APIC-EM, so that we can plan SFP development accordingly ?
Any help or redirect will be appreciated ?
Br//
Raj
01-17-2017 12:06 AM
I am from CMS team. We are working on APIC-EM integration with Serivce Fullfilment Portal(SFP). SFP is Cisco Internal tool which will be consuming API exposed by APIC-EM for different app(iWAN, Easy QoS, PnP etc).
I are using APIC-EM version 1.3.1.9. I came to know that API for APIC-EM Apps will not be exposed in next releases.
I would like to know the road-map for APIC-EM, so that we can plan SFP development accordingly.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide