api-manager

How can I modify the port 5672 in AM?

由 对着背影说爱祢 提交于 2019-12-11 07:04:18
问题 I start the AM server by running the commond wso2carbon.sh and the carbon.log prompts the 5672 was used. So I have to modify the port. Thus, which configuration file I should modify? Thanks a lot. 回答1: Here is a quick grep which will help you. (note: here the port is changed from 5672 to 5678.) bhathiya@bhathiya-x1:/data/products/am/wso2am-2.0.0/bin$ grep -r 5678 ../repository/conf/ -A 5 -B 5 ../repository/conf/api-manager.xml- <!--InitDelay>300000</InitDelay> ../repository/conf/api-manager

WSO2 APIM 2.0 Clustering deployment issue when try API console from API store

由 泄露秘密 提交于 2019-12-11 06:16:35
问题 I deployed 2 keymanager nodes, 2 pub-store nodes, 1 gateway manager node and 2 gateway worker nodes in one server, and deployed nginx for load balance. When i try to access API via API Console, it reported below error: TID: [-1234] [] [2016-08-29 21:10:57,237] WARN {org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler} - API authentication failure due to Unclassified Authentication Failure {org.wso2.carbon.apimgt.gateway.handlers.security.APIAuthenticationHandler} TID: [

WSO2 API Manager: Categorising and grouping APIs

由 ぐ巨炮叔叔 提交于 2019-12-11 05:30:02
问题 Migrating from WSO2 AM 1.10 to 2.0. Won't mention all the obstacles I've had to overcame. But this one is pretty obvious and I am really stunned that this went overlooked/ignored by the developers before releasing the new version. Let's ignore all the bugs with CSRF, BUT this one sucks arse, too: Grouping and categorizing. WSO2 documents have not been updated since the last release, which is kinda sad. BUG 1: Grouping does not work unless all the subdirs (in Carbon) under "tags" dir are

WSO2 API Manager - context management

由 你说的曾经没有我的故事 提交于 2019-12-11 02:37:32
问题 Can we reuse the context of an api that has been deleted? I am looking at the scenario, where someone accidentally deleted the api and want to recreate it. Or reuse the context for different purpose. Currently, when I try do the same, I get an error - Error occurred while adding the API. A duplicate API already exists for "your api" Is this a bug? 回答1: You should be able to use. But i think there is a reported bug regarding this.(not sure though) We will fix in the future release. But please,

WSO2 APIM clustering - how to improve the response time?

由 时光毁灭记忆、已成空白 提交于 2019-12-08 03:33:18
问题 I clustered APIM with 1 manger gateway node and 2 or more work node to test APIM response time. it did not give me good data. without APIM,my api response time is 20 ms.though APIM 400ms-1s. how to confige this question? 回答1: There are several handlers in APIM, through which all API calls are going. Eg. Authentication, Throttling, CORS etc. You can enable analytics in APIM and see a latency breakdown graph among stages. See Figure 9 of this article. Then you can identify if there are any

wso2 am 1.10.0 API Store: “Error occurred while executing the action generateApplicationKey” with “ Invalid credentials provided.”

由 核能气质少年 提交于 2019-11-28 02:25:38
Product: WSO2 AM 1.10.0 DB: MSSQL Security: SAML2 integrated with PingIdentity OS: Linux When I tried to create or generate keys from "/store/site/pages/subscriptions.jag" page, UI gave me: Error occurred while executing the action generateApplicationKey Here is what's in the log: Summary of the errors: Error while obtaining the application access token for the application:safsa org.wso2.carbon.apimgt.api.APIManagementException: Error occurred while Creating Keys. at org.wso2.carbon.apimgt.impl.utils.APIUtil.handleException(APIUtil.java:1195) ... Caused by: org.wso2.carbon.apimgt.api
订阅 api-manager