I would like to change the API owner/publisher of an API I have published, so I can keep publishing new versions of this API with another user.
I am using wso2 v2.6
I've been looking for an option in the Publisher & Store UI but did not see the option
This is not possible as the owner (provider) is one of the fundamental attributes of an API. Even if you change the owner, you would not be able to create new versions as this would be considered as a new API, not a version of the previous API and this would result in duplicate context. The same validation prevents you from creating two separate APIs with the same context.
If you want to change the owner of the API by deleting the previous one, you can do so using the cli tool[1]. Here you can export the API, delete the previous API and reimport the same API with a different owner (provider).
Please note that cli tool is only available with the WSO2 WUM updates from July 8, 2019 and you need WSO2 subscription.
[1] - https://docs.wso2.com/display/AM260/Initializing+projects+using+the+CLI+Tool
Related
Can I publish an agent version on an environment using the Dialogflow V2 API?
I can't find any documentation on how to do that.
The doc about versions and environments only mentions doing this using the console (https://cloud.google.com/dialogflow/docs/agents-versions).
And the API doc of the agent environments resource only contains a list method (https://cloud.google.com/dialogflow/docs/reference/rest/v2/projects.agent.environments).
Does it mean that every change done using the API is automatically reflected in production?
Or does it mean that every change done by API is staged, and can only go to production by manually accessing the console and publishing the new version?
Both options seems terrible by the way.
Currently, it's not possible to manage agent versions through the Dialogflow API, it seems that this feature is already being contemplated to be integrated to Dialogflow; however, there is no an ETA for its implementation. You can follow up this request here.
I've published an API named as "DocumentAPI", after publishing I can find two API's with the name "DocumentAPI" in publisher. Can find only one API with name "DocumentAPI" in store. Tried deleting, recreating and republishing the API and also restarted my server.
Two gateways(internal(MZ) and external(DMZ)) are there in the current environment which means some the APIs are specific to internal and some are specific to external and some are published to both the gateways(cuurent problematic API is published to both the gateways)
There is no synchronize method setup between these two nodes.
We are on APIM-2.6.0
There is no duplicate entries in AM_API, REG_PATH tables with repect to problematic API. Only in publisher UI we are seeing two APIs with same name,version & conetxt and when I modify any one API the change immediately relfecting into other API as well. In store only one API it is showing and when I test this API through Postman subsequent calls are getting failed.
Note: Publishing in fully distributed environment.
Are you using APIM wum updated pack or vanilla pack? If it is wum, what is the wum level(AM_HOME/updates/wum)?
Did you try to recreate a new API instead of that "DocumentAPI" name (with a different name) and did you see the same issue for this when publishing to both GW nodes?
In APIM 2.6.0 we have seen a similar issue if we have created an API with uppercase (eg: AbcAPi) and published it. Then remove it and try to recreate the api with the same name but lowercase (eg: abcApi) and publish it. Then we can see two API in the publisher portal but not in Store UI. And AM Table has one record. But in the registry has two paths (as you have seen).
eg:
/_system/governance/apimgt/applicationdata/provider/admin/AbcAPi
/_system/governance/apimgt/applicationdata/provider/admin/abcApi
One path for that old api name and another path for the new API. Since currently, we have fixed this, and that fix is available in the latest wum updated pack of the APIM 2.6.0. Therefore did you notice such differences in both reg paths (select * from REG_PATH where REG_PATH_VALUE).
If yes, it has fixed in the latest wum of APIM 2.6.0. The reason here is when removing API, it remains some metadata of old API and when recreating registry keep both paths.
When creating an API in wso2 APIM, it doesn't allow to create two APIs with the same name, context and version (name, context and version should unique).
As per the provided mentioned details, we hope that both APIs in the publisher node has the same name, context and version.
In your distributed set up how many GWs are available(one or many)?
If has multiple GW nodes, are you using any deployment artefact syncronize method like NFS?
What is the APIM version
Are you noticing two records for the above API in the AM database(AM_API table)?
By reading the new API it says that we are no longer allowed to create Facebook Events for our users. Am I reading that correctly? If that is the case, is there a way that individual applications could be manually approved by Facebook?
We are a full service ticket company (we do not resell tickets) for our customers. Our software has always automatically created events for our customers. I understand trying to get rid of the spam events that get created, but for legit events also?
Example Event:
https://www.facebook.com/events/714621851990427/
That is correct, you can no longer create Facebook events with the API. There is no way to get it approved for any App.
As you can read in the docs, there is not even a permission you could get approved: https://developers.facebook.com/docs/graph-api/reference/v2.3/event#publish
You cannot create events via the Graph API.
This is part of the upgrade to v2.0 of the API, the removal of v1.0 was introduced on April 30, 2014. You can read more about the different API versions in the changelog: https://developers.facebook.com/docs/apps/changelog
I am working on WSO2 API Manager, version 1.6 and 1.8. I have created a new subscriber via Store APIs, and i don't see that there is supported to update or remove existing subscriber. Does WSO2 API Manager still not support that ?
Thanks,
An
You can block the existing subscription form the publisher # subscriptions menu.
WSO2 API manager has 4 components
API Gateway
API Publisher
API Store
API Key Manager Server
I would like to run each of these components on separate boxes. While doing so on box where I have API Publisher component I want to remove other 3 components from the api manager so on with other components. By this I would like to achieve that only 1 component exists at run time of each instance of wso2 api manger.
I would like to know how can we remove each of these components from wso2 api manager?
You can remove the relevant features from the product via Carbon Feature Management (Or you can add necessary features as well).
You can find more information regarding how to uninstall a particular feature here.
You can also find more information regarding feature management for WSO2 Carbon products here.
HTH,
Lasantha
To add to Lasantha's answer, this article describes how these 4 components can be deployed separately in a cluster with an ELB.
Installing High Level components is supported from API Manager 1.5.0 onwards. If you want to start API Manager as one of the components, that can be achieved by starting as a server profile. You can find more information here.