logo
down
shadow

WSO2 QUESTIONS

ADD a existing API without server downtime
ADD a existing API without server downtime
I hope this helps . Yes, it is possible. You can replace the existing API configuration in the deployment folder or the CAPP (If you used capps to deploy the api) and you do not need a server restart to apply changes.
TAG : wso2
Date : November 24 2020, 03:01 PM , By : shubham
WSO2-AM: API calls in store fail after restart
WSO2-AM: API calls in store fail after restart
like below fixes the issue I guess you haven't used any persistent storage for API Manager. When you create an API, the API artifact is created in the file system and stored in wso2am-2.1.0/repository/deployment/server/synapse-configs/de‌​fault/api l
TAG : wso2
Date : November 14 2020, 03:01 PM , By : Anoop Singh
Is there another way to cluster WSO2 IS servers aside from connecting to embedded-ldap on another node?
Is there another way to cluster WSO2 IS servers aside from connecting to embedded-ldap on another node?
may help you . Sharing the user stores is mandatory for the functionality of the cluster as both nodes of the cluster should be exposed to the same user base but the user store doesn't have to be the embedded LDAP. The embedded LDAP is usually used f
TAG : wso2
Date : November 05 2020, 03:01 PM , By : S. Singh
How can we determine the request environment (sandbox / production) in a WSO2 custom handler?
How can we determine the request environment (sandbox / production) in a WSO2 custom handler?
this will help The environment is always decided based on the access token. If the API is open it's by default sent to the production environment. See [1].[1] https://github.com/wso2/carbon-apimgt/blob/6.x/components/apimgt/org.wso2.carbon.apimgt.gat
TAG : wso2
Date : November 04 2020, 03:01 PM , By : Unknown
shadow
Privacy Policy - Terms - Contact Us © voile276.org