Anypoint Platform Apps/Schedulers - api

Is there a way to get details of all the apps in an Anypoint Platform Business Group. For example, if there are 3 apps available in the RunTime Manager, I am looking at details like below:
I know there are cloudhub APIs which can get the details, but is there a custom API? If yes, can it be integrated with a reporting tool like PowerBI to create a live dashboard?
Please advise.

All or nearly all REST APIs provided by Anypoint Platform return JSON, including the CloudHub REST API. You can check the platform APIs in MuleSoft Dev Portal.
You can use the cloudhub/api/v2/applications/{domain} endpoint to get details of an application: https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/cloudhub-api/minor/1.0/console/method/%231839/
To get the schedulers information the endpoint there is a cloudhub/api/applications/{domain}/schedules endpoint: https://anypoint.mulesoft.com/exchange/portals/anypoint-platform/f1e97bc6-315a-4490-82a7-23abe036327a.anypoint-platform/cloudhub-api/minor/1.0/console/method/%233128/
Both return JSON responses with the information described in above links.
I don't know if that is useful for PowerBI. If not, you can develop your own custom application to query above information and return it in a suitable format. Your application can implement an API of your design if needed.

Related

How to linkup API in API manager with interface deployed in Cloud Hub?

I have an API deployed in API Manager, deployed one interface in cloud hub with API auto discover option.
In API manager, i gave cloudhub link as implementation url. so i thought both are linked up.
But when i apply SLA tier to API it is not getting applied. is there anything need to be done ?
Please first apply Auto discovery properly on the app. Create one API in the API manager. copy API ID into autodiscover configuration in the app. please find below link for details explanation.
Auto discovery article from dzone

Integrate WSO2 API Manager with third party api gateway like kong

I´m interested in using the store and the developer portal. In some cases I want to integrate third-party gateway like kong.
The documentation from WSO2 API Manager 2.x says:
- Components usable separately: developer portal can be used to catalog
APIs deployed in third-party gateways
(https://wso2.com/api-management/features/)
Do you have more information about that feature and how to configure it?
Technical this is feasible but requires some work. I've found that someone did it with Intel Expressway Service Gateway.
You would need to implement a custom handler in WSO2 and connect it with Kong. But as the features might differ, the UI may not perfectly fit.
Besides than offering extension points, WSO2 has no real interest in supporting this as the API Gateway is the core component and all of their business models are based on it.

How can we use API Connect to publish the existing REST API of customer?

Supposed that customer only provides me the URL end point of their existing API. They don't have swagger file for us to import the APIs.
Customer wants to use API Connect to publish their API to users to use.
I did that successfully with API Management. Now API Management is deprecated by API Connect, but that feature is still in API Connect. I failed to make it work with API Connect. How can we use API Connect to publish the existing REST API of customer not using swagger? Please shed the light. I'm greatly appreciated with your help.
Regards,
Quyen Tran
To publish an API into an IBM API Connect catalog, and to have access to that API managed by the API Gateway, you will need a Swagger (OpenAPI) document.
If you don't have a Swagger document, you will need to author one e.g. using the API Designer or API Manager tooling. You will need to know the URL of the existing endpoint but also the schema of any data that needs to be sent to or received from that URL.
If you made it work with IBM API Management then it should be no different with IBM API Connect.

Wso2 API orchestration requirement for API Management

We successfully launch Wso2 API management solution. One of the main functionality of our project is to orchestrate several simple API and make one Meta API. Then we want to publish this Meta API into Wso2 API Management Publisher and make it available to use.
Is any solution to this requirement?
You can do this. If I understand you correct, you only want to publish the meta api as a managed api. Other simple apis won't be published. If so, things are pretty easy.
WSO2 API Manager uses Apache Synapse as the mediation engine (which is used by WSO2 ESB too). This allows to do the chaining. Please go through the following articles.
http://wso2.com/library/articles/2014/03/batch-api-api-chaining-scenario/
https://docs.wso2.com/display/ESB470/Service+Chaining+Example
http://wso2.com/library/articles/2012/09/get-cup-coffee-wso2-way/

Mule:How to connect Mule ESB with Hybris?

I have a requirement to connect Mule ESB with Hybris. I didnt find Hybris connector provided by Mule( Also didnt find sample examples as well). This is the 1st time going to try Mule with Hybris..Please let me know the steps or efficient procedural way to connect Hybris.
Is the hybris URL enough to connect?. Please suggest me with your thoughts to implement. Thanks in advance.
Hybris has many ways to integrate with their platform. If you have a login you can access their docs which details examples of integration with the platform including JMS and the Platform Web Services.
There is no connector supplied by Mule, but you can access their Platform Web Services which are implemented with a HTTP Restful API using the Mule http transport or by building your own connector using the Mule DevKit.
The hybris wiki has pages dedicated to most of the endpoints and the request/response formats. You can view this here if you have a login: https://wiki.hybris.com/display/release5/WebService+API+-+Reference
Also, in your hybris installation there are a bunch of examples in /bin/ext-platform-optional/platformwebservices/src...
and /bin/ext-platform-optional/platformwebservices/testsrc which show the actual web service implementations and their test cases using Jersey client.