We are doing a DB Migration for WSo2 Governance Registry from 4.5.0 and migration script is not available for some specific versions at WSO2 Site hence requesting for the same for the specified versions below. Please find below the versions as we are doing a Sequential migration and kindly facilitate the script for both Oracle and MySQL
GREG versions starting from 4.5.3, 4.6.0, 5.0.0, 5.0.1, 5.1.0, 5.2.0, 5.3.0
Database: Oracle and MySQL
Please find the instructions given in these documentations to upgrade the WSO2 Governance Registry.
[1] - Upgrading from G-REG 4.5.3 to 4.6.0
[2] - Upgrading from G-REG 4.6.0 to 5.0.0
[3] - Upgrading from G-REG 5.0.0 to 5.0.1
[4] - Upgrading from G-REG 5.0.1 to 5.1.0
[5] - Upgrading from G-REG 5.1.0 to 5.2.0
[6] - Upgrading from G-REG 5.2.0 to 5.3.0
Note that from G-REG 5.0.0 onwards, it provides a migration client for the ease of upgrading.
Related
I am migrating WSO2 Identity server from version 4.5.0 to 5.5.0 using the steps given below,
Migrated from 4.5.0 to 5.0.0 given in https://docs.wso2.com/display/IS500/Upgrading+from+a+Previous+Release
Then I migrated from 5.0.0 to 5.5.0 by changing the current version to 5.0.0 as per the document https://docs.wso2.com/display/IS550/Upgrading+from+a+Previous+Release
But the primary user stores which were created using ldap and all the Oauth created in 4.5.0 are not migrated. Why ?
Is there any other steps I need to do ?
I am using wso2 identity server version 5.1.0-beta. I want to upgrade to 5.3.0. How can i upgrade the version without loosing my data. Do i need to upgrade 5.1.0 then 5.2.0 then 5.3.0 ?
Expecting WSO2 identity server documentation to upgrade from 5.1.0 to 5.3.0 directly.
Anyone help me to find the document. Thanks in advance
You cannot directly migrate to 5.3.0 from 5.1.0. You need to first migrated to 5.2.0[1] then to 5.3.0[2]
[1] https://docs.wso2.com/display/IS520/Upgrading+from+a+Previous+Release
[2] https://docs.wso2.com/display/IS530/Upgrading+from+a+Previous+Release
For a new project I'd like to setup the new ESB 5.0 adding the dss feature as well. I was about to do it from the wilkes repository (http://product-dist.wso2.com/p2/carbon/releases/wilkes/), but during installation it shows following error:
Cannot complete the install because of a conflicting dependency. Software being installed: Data Service Hosting Feature 4.3.4
(org.wso2.carbon.dataservices.feature.group 4.3.4) Software currently installed: WSO2 Carbon - Transaction Manager Feature 4.5.4
(org.wso2.carbon.transaction.manager.feature.group 4.5.4) Only one of the following can be installed at once: WSO2 Carbon - Transaction Manager Feature 4.4.7 (org.wso2.carbon.transaction.manager.feature.jar 4.4.7) WSO2 Carbon -
Transaction Manager Feature 4.5.4 (org.wso2.carbon.transaction.manager.feature.jar 4.5.4) Cannot satisfy dependency: From: Data Service Hosting Feature 4.3.4 (org.wso2.carbon.dataservices.feature.group 4.3.4) To: org.wso2.carbon.dataservices.server.feature.group [4.3.4] Cannot satisfy dependency: From: Data Service Hosting Feature 4.3.4 (org.wso2.carbon.dataservices.server.feature.group 4.3.4) To: org.wso2.carbon.transaction.manager.feature.group [4.4.0,4.5.0) Cannot satisfy dependency: From: WSO2 Carbon - Transaction Manager Feature 4.4.7 (org.wso2.carbon.transaction.manager.feature.group 4.4.7) To: org.wso2.carbon.transaction.manager.feature.jar [4.4.7] Cannot satisfy dependency: From: WSO2 Carbon - Transaction Manager Feature 4.5.4 (org.wso2.carbon.transaction.manager.feature.group 4.5.4) To: org.wso2.carbon.transaction.manager.feature.jar [4.5.4]
How can this be solved? the same procedure using ESB 4.9.0 works as expected. Is it something that still to be updated in the new ESB 5.0?
In that case what are the alternatives you suggest?
This seems like a bug. I have raised a Jira (https://wso2.org/jira/browse/DS-1249) to track this. This will be fixed in the next release.
Thanks.
I have tried several options to install IS on App Server and using different repositories but it always complains about some packages. What is the easy way to get the correct dependencies and repositories?
This is an example of the errors:
Cannot complete the install because of a conflicting dependency.
Software being installed:
STS Feature 4.2.1 (org.wso2.carbon.sts.feature.group 4.2.1)
Software currently installed: WSO2 Carbon - Carbon Feature 4.4.1 (org.wso2.carbon.core.feature.group 4.4.1)
Only one of the following can be installed at once: WSO2 Carbon -
Carbon Feature 4.4.1 (org.wso2.carbon.core.feature.jar 4.4.1) WSO2 Carbon -
Carbon Feature 4.2.0 (org.wso2.carbon.core.feature.jar 4.2.0)
What version of IS and what version of App Server are you running? I have never tried to implement the scenario you are but I could see you getting that type of error if the version of App Server you are running is on Carbon 4.4 and the version of IS is still on Carbon 4.2. The current 5.0 release of IS runs on Carbon 4.2 but I think the 5.1 release of IS runs on Carbon 4.4 and should be available before long.
Joe
When I try to integrate CEP into BAM following the documentation I get a message that
no features will be installed.
Along with the summary.
Your original install request has been modified. org.wso2.carbon.cassandra.dataaccess.feature.group-4.2.2 will be ignored because a newer version is already installed. org.wso2.carbon.cassandra.common.feature.group-4.2.2 will be ignored because a newer version is already installed. org.wso2.carbon.cassandra.server.feature.group-4.2.3 will be ignored because a newer version is already installed. org.wso2.carbon.registry.resource.properties.feature.group-4.2.0 is already installed, so an update will be performed instead. org.wso2.carbon.databridge.streamdefn.registry.server.feature.group-4.2.1 will be ignored because a newer version is already installed. org.wso2.carbon.webapp.mgt.server.feature.group-4.2.2 will be ignored because a newer version is already installed. org.wso2.carbon.cassandra.mgt.feature.group-4.2.2 will be ignored because a newer version is already installed. Cannot complete the install because of a conflicting dependency. Software being installed: WSO2 Carbon - Service Management Feature 4.2.1 (org.wso2.carbon.service.mgt.feature.group 4.2.1) Software currently installed: Key Store Management Feature 4.2.4 (org.wso2.carbon.security.mgt.feature.group 4.2.4) Only one of the following can be installed at once: WSO2 Carbon - Security Management UI Feature 4.2.2 (org.wso2.carbon.security.mgt.ui.feature.jar 4.2.2) WSO2 Carbon - Security Management UI Feature 4.2.0 (org.wso2.carbon.security.mgt.ui.feature.jar 4.2.0) Cannot satisfy dependency: From: Key Store Management Feature 4.2.4 (org.wso2.carbon.security.mgt.feature.group 4.2.4) To: org.wso2.carbon.security.mgt.ui.feature.group [4.2.2] Cannot satisfy dependency: From: WSO2 Carbon - Security Management UI Feature 4.2.0 (org.wso2.carbon.security.mgt.ui.feature.group 4.2.0) To: org.wso2.carbon.security.mgt.ui.feature.jar [4.2.0] Cannot satisfy dependency: From: WSO2 Carbon - Security Management UI Feature 4.2.2 (org.wso2.carbon.security.mgt.ui.feature.group 4.2.2) To: org.wso2.carbon.security.mgt.ui.feature.jar [4.2.2] Cannot satisfy dependency: From: WSO2 Carbon - Service Management Feature 4.2.1 (org.wso2.carbon.service.mgt.feature.group 4.2.1) To: org.wso2.carbon.service.mgt.ui.feature.group [4.2.0] Cannot satisfy dependency: From: WSO2 Carbon - Service Management UI Feature 4.2.0 (org.wso2.carbon.service.mgt.ui.feature.group 4.2.0) To: org.wso2.carbon.security.mgt.ui.feature.group [4.2.0]
Any ideas how to resolve this and integrate these?
It appears to be an issue with recent releases, old releases integrate fine. Dropping features to be integrated as they cause issues which are highlighted in the summary seems to be one way to work past this but is far from ideal.
From BAM 2.4.0 onwards, the core CEP features have also been included inside BAM by default. There is no need to install CEP features separately. However, the CEP dashboard will not be available since BAM has its own dashboard.
If you use BAM 2.4.0, CEP features released for CEP 3.0.0 will be available. If you need CEP 3.1.0 features in a BAM pack, you can use BAM 2.4.1.
You can verify what is the corresponding version of CEP features for a particular BAM pack by referring to the WSO2 release matrix [1]. The latest BAM pack will always ship with the latest CEP features available.
[1] http://wso2.com/products/carbon/release-matrix