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
Related
WSO2 API Manager Version 4.0.0 is Working Fine With Choreo Analytics but Is there Any Way to Configure API Manager Version 4.0.0 with API-M Analytics Version 3.2.0?
No, this is not possible with API Manager 4.0.0.
The API Manager v4.0.0 has gone through a lot of architectural changes and the Handlers and implementations related to publishing Analytics Data to the APIM Analytics server have been removed. Therefore, with my understanding, it is not possible to achieve the same in the v4.0.0 environment.
With the API Manager 4.0 release, the API Analytics was completely revamped and offered as a cloud-based analytics solution to provide users with an unparalleled analytics experience. Therefore, integrating APIM Analytics 3.2.0 with APIM 4.0.0 is not a possible/advisable solution due to architectural constraints.
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
Is there an installation and configuration guide for Stratos 1.6?
Stratos 1.6 comes as a downloadable pack (which is called the Stratos Local Setup). You can download it from here. It contains a readme and necessary scripts to get you started. Download it and try.
Stratos manager is the entry point for Stratos cloud services. So Manager and ELB services should be started in order to access cloud services.
Can you give more details on the database issues you faced. When errors are thrown and what erros are thrown etc.
meetudara.blogspot.com/2013/02/wso2-stratos-16-how-to-intall-and.html
I've been testing WSO2 BRS and WSO2 Data Services separately and working properly. The next step was to add in the WSO2 ESB the features that provide these capabilities, but they have bugs that keep the deployment of services.
BRS Feature: Can't upload the . jar with the class model for rules. (Rule Service - 3.2.0)
Data Services Feature: Various failures to create new services, not looking tables of datasource and can't upload the services created previously. (Data Service Hosting - 3.2.0)
Has anyone done these features work properly?
What is the ESB version you are using? If it is ESB 4.0.3, please install the latest versions of Rule Service and Data Services features.
Rule Service and Data Services versions: 3.2.2
Thanks
Thilini
The installation instructions are clear how to download a .zip for an individual product (e.g. ESB, Application Server, Mashup Server). But based on the OSGi component architecture, I thought it would be possible to, for example, add Mashup Server functionality to an existing install of the ESB. I've looked at the Feature Manager, and tried adding a repository (http://dist.wso2.org/p2/carbon/releases/3.2.4/), but have not had success.
Any guidance appreciated.
It's possible to install different features via the feature manager, but you have to determine the correct version of the feature compliant with the target server. For example, to install BPEL features to WSO2 ESB 4.0.2, first find the related WSO2 Carbon platform version. This can be determined by the version of $ESB-HOME/repository/components/plugins/org.wso2.carbon.core-x.x.x.jar. So if WSO2 ESB 4.0.2 is the target server, then the version of org.wso2.carbon.core jar would be 3.2.2. So the relevant BPEL feature version is 3.2.2.
You can read more about Installing+Features and How install the BPEL features via Feature Manager.
Please refer to WSO2 release matrix [1] in order to match the correct version
By looking at it, you can easily find the Carbon version of any product version.
For example ESB 4.0.2 has the carbon version 3.2.2
[1] http://wso2.com/products/carbon/release-matrix/