We recently pushed through the upgrades of our WSO2 instances to IS 5.1, API 1.10.0 and GREG 5.1. We are a clustered setup, with IS 5.1 serving as Key Manager, API 1.10.0 serving as the API Gateway, and GREG 5.1 serving as the API Store/Publisher, all using the a shared MGT DB.
Once the upgrades completed we started noticing errors such referencing "IAT.CONSUMER_KEY".
ERROR {org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO} - Failed to get keys for application: 35 {org.wso2.carbon.apimgt.impl.dao.ApiMgtDAO}
com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Unknown column 'IAT.CONSUMER_KEY' in 'where clause'
Looking into the jar we noticed that the API Store/Publisher jar was still referencing the old column name, CONSUMER_KEY, for IDN_OAUTH2_ACCESS_TOKEN. In a shared setup the IS 5.1 upgrade dropped that column and created the column CONSUMER_KEY_ID.
I installed a vanilla 5.1 Greg and installed the 2.0.1 Store plugin again and the jar impacted definitely appears to be trying to use CONSUMER_KEY:
org.wso2.carbon.apimgt.impl_2.0.1.jar
Anyone hit this issue? Did we outpace the API Store/Publisher plugin for GREG? Or, I have just setup the system incorrectly.
Thanks for the help,
Kevin
You need to install API key manager features or use pre-packaged WSO2 Identity Server 5.1.0 as [1] when configuring IS 5.1.0 as key manager with APIM 1.10.0.
https://docs.wso2.com/display/CLUSTER44x/Configuring+the+Identity+Server+5.1.0+as+a+Key+Manager+with+API+Manager+1.10.0
Related
I am trying to install following feature in wso2 API manager 2.0.
http://xacmlinfo.org/2015/05/13/federated-authenticators-in-wso2-api-manager-wso2apim/
but I am getting error in API manager's console while installations.
It seems the above package is not compatible for 2.0 version.
Please suggest me the exact version of 'Application Authenticator' feature which is compatible with wso2 AM version 2.0.
Thanks in advance
It seems the p2 repos are still not updated with the latest Authenticator versions based on Identity Application Management Server Feature 5.2.0 or above. This will be updated soon with the next release.
However you can use WSO2 IS for this use case. You can configure SSO for APIM with IS using this link . Then you can federate IS for OpenAM with this link . With that you can connect APIM with openAM.
Hope this helps.
Is Latest Version of WSO2 API Manager(2.0.0) compatible with latest version of WSO DAS(3.1.0)?
In the download page of WSO2 API Manager 2.0.0, only WSO DAS 2.0.0 download is mentioned for Analytics.
Yes, they are compatible.
2nd question is not much clear. Could you please tell where it says about DAS 2.0.0? Actually, there is no version 2.0.0 in DAS. It was called BAM before.
If you're talking about wso2am-analytics-2.0.0.zip pack, it's a customized version of DAS 3.0.x. It has required CAR files installed and is configured to work with APIM, with less manual configurations.
I followed the tutorial here:
https://docs.wso2.com/display/AM191/Publishing+API+Runtime+Statistics+Using+WSO2+DAS#PublishingAPIRuntimeStatisticsUsingWSO2DAS-ConfiguringWSO2APIManager
On configuring WSO2 API Manager, I cannot seem to configure Analytics when I am inside the Admin Portal. Is there some configuration first that needs to be done?
You are looking at APIM 1.9.1 documentation. But it looks like you are using latest APIM which is 2.0.0. In 2.0.0 you can configure analytics in api-manager.xml only. See APIM 2.0.0 documentation.
One important thing about APIM 2.0.0 is, you don't need to configure DAS from scratch. Now DAS is pre-configured with required CApps and shipped as wso2am-analytics-2.0.0.zip. You can download it from APIM Product page itself.
We're running the WSO2 API Manager 1.4 and would like to upgrade to the latest version 1.6. Can we go directly to 1.6 or do we have to upgrade to 1.5 first? Mainly I'm just concerned regarding the DB migration, as these scripts only seem to be relevant for single version increments. https://svn.wso2.org/repos/wso2/carbon/platform/branches/turing/products/apimgt/1.6.0/modules/distribution/resources/
Thanks.
As you said, for the databases migrations, you can execute migration-1.4.0_to_1.5.0 and migration-1.5.0_to_1.6.0 SQLs sequentially.
It's important to note that API Manager 1.4.0 is based Carbon 4.1.x and API Manager 1.6.0 is based on Carbon 4.2.0. See Release Matrix for WSO2 Products.
This means that the underlying clustering, registry and user-mgt have some major changes. The API Manager related configurations also has changed.
Therefore my advice is to do as follows.
Backup your existing database and API Manager 1.4.0 deployment.
Migrate databases in an incremental manner.
Re-do all configurations in API Manager 1.6.0 instances. i.e. direct migration from 1.4.0 to 1.6.0. You may compare your API Manager 1.4.0 repository/conf files with a fresh wso2am-1.4.0 pack.
I hope this helps!
You can folow below posts in order. Post [1] provides the migration instructions for wso2 api manager 1.4.0 to 1.5.0. Post [2] provides instructions for migrating from 1.5.0 to 1.6.0.
[1]http://blog.lakmali.com/2013/11/migrating-wso2-api-manager-140-to-150.html
[2]http://blog.lakmali.com/2013/12/migrating-wso2-api-manager-150-to-160.html
I guess there is a version issue between the tribes used by the ELB 2.0.3 (tribes version 028) and the tribes used by ESB 4.7.0 or 4.8.0M1 (tribes version 032) which lead to deserialization issue of org.apache.catalina.tribes.membership.MemberImpl during the JOIN process:
ERROR {org.apache.axis2.clustering.tribes.Axis2GroupChannel} - Unable to deserialize message:ClusterData[src=org.apache.catalina.tribes.membership.MemberImpl[
If I use ELB 2.0.3 with ESB 4.6.0 (tribes 028), it works like a charm.
Is there a newest (and compliant) version of ELB available ?
Thanks
Dom
ELB 2.0.3 should work well with Carbon 4.0.x and Carbon 4.1.x based products.
Check WSO2 Release Matrix for more information about the Carbon version of each product.
Carbon 4.2.0 introduces Hazelcast based clustering and the compatible ELB product version is 2.1.0, which will be released in next few days.
ESB 4.8.0 is also based on Carbon 4.2.0 and therefore you will need ELB 2.1.0 to setup a cluster.
The release candidate builds are announced in dev mailing list and you should be able to download ELB 2.1.0 RC.