Is it possible to install API Manager 1.6.0 Feature on wso2esb 4.8.1 .I tried to install using Feature Management,but it is showing dependency problem..
While trying to install using feature management,i am getting the below error
Your original install request has been modified. org.wso2.carbon.registry.core.server.feature.group-4.2.1 is already present because other installed software requires it. It will be added to the installed software list. org.wso2.carbon.security.mgt.feature.group-4.2.2 is already installed, so an update will be performed instead. org.wso2.carbon.module.mgt.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list. org.wso2.carbon.rest.api.server.feature.group-4.2.1 is already present because other installed software requires it. It will be added to the installed software list. org.wso2.carbon.endpoint.server.feature.group-4.2.1 will be ignored because a newer version is already installed. org.wso2.carbon.registry.community.features.server.feature.group-4.2.1 will be ignored because it is already installed. org.wso2.carbon.event.server.feature.group-4.2.1 will be ignored because it is already installed. org.wso2.carbon.application.mgt.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list. org.wso2.carbon.mediators.server.feature.group-4.2.1 will be ignored because a newer version is already installed. org.wso2.carbon.sequences.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list. org.wso2.carbon.datasource.server.feature.group-4.2.1 will be ignored because it is already installed. org.wso2.carbon.application.mgt.synapse.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list. org.wso2.carbon.mediation.templates.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list. org.wso2.carbon.relay.server.feature.group-4.2.0 will be ignored because it is already installed. org.wso2.carbon.localentry.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list. org.wso2.carbon.logging.mgt.feature.group-4.2.1 is already installed, so an update will be performed instead. org.wso2.carbon.security.mgt.server.feature.group-4.2.2 is already installed, so an update will be performed instead. org.wso2.carbon.registry.resource.properties.feature.group-4.2.0 is already installed, so an update will be performed instead. org.wso2.carbon.service.mgt.server.feature.group-4.2.1 is already present because other installed software requires it. It will be added to the installed software list. org.wso2.carbon.event.common.feature.group-4.2.0 will be ignored because it is already installed. org.wso2.carbon.task.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list. org.wso2.carbon.throttle.feature.group-4.2.0 will be ignored because it is already installed. org.wso2.carbon.rule.mediation.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list. org.wso2.carbon.core.common.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list. org.wso2.carbon.core.runtime.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list. org.wso2.carbon.identity.authenticator.saml2.sso.server.feature.group-4.2.0 is already installed, so an update will be performed instead. org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.group-4.2.1 will be ignored because it is already installed. org.wso2.carbon.core.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list. Cannot complete the install because of a conflicting dependency. Software being installed: WSO2 Carbon - Webapp Management Feature 4.2.1 (org.wso2.carbon.webapp.mgt.feature.group 4.2.1) Software being installed: WSO2 Carbon - Webapp Management Core Feature 4.2.0 (org.wso2.carbon.webapp.mgt.server.feature.group 4.2.0) Only one of the following can be installed at once: WSO2 Carbon - Webapp Management Core Feature 4.2.2 (org.wso2.carbon.webapp.mgt.server.feature.jar 4.2.2) WSO2 Carbon - Webapp Management Core Feature 4.2.1 (org.wso2.carbon.webapp.mgt.server.feature.jar 4.2.1) WSO2 Carbon - Webapp Management Core Feature 4.2.0 (org.wso2.carbon.webapp.mgt.server.feature.jar 4.2.0) Cannot satisfy dependency: From: WSO2 Carbon - Webapp Management Feature 4.2.1 (org.wso2.carbon.webapp.mgt.feature.group 4.2.1) To: org.wso2.carbon.webapp.mgt.server.feature.group [4.2.1] Cannot satisfy dependency: From: WSO2 Carbon - Webapp Management Core Feature 4.2.0 (org.wso2.carbon.webapp.mgt.server.feature.group 4.2.0) To: org.wso2.carbon.webapp.mgt.server.feature.jar [4.2.0] Cannot satisfy dependency: From: WSO2 Carbon - Webapp Management Core Feature 4.2.1 (org.wso2.carbon.webapp.mgt.server.feature.group 4.2.1) To: org.wso2.carbon.webapp.mgt.server.feature.jar [4.2.1]
Can anyone help me on this please....
Thanks in advance,,,,
Related
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
I would like to install API Manager 1.7.1 feature on ESB 4.8.1 and receiving this as a message summary. Any help for steps to proceed from here.
Your original install request has been modified. org.wso2.carbon.security.mgt.feature.group-4.2.2 is already installed, so an update will be performed instead.
org.wso2.carbon.module.mgt.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list.
org.wso2.carbon.rest.api.server.feature.group-4.2.1 is already present because other installed software requires it. It will be added to the installed software list.
org.wso2.carbon.stratos.common.feature.group-2.2.1 is already installed, so an update will be performed instead.
org.wso2.carbon.endpoint.server.feature.group-4.2.1 will be ignored because a newer version is already installed.
org.wso2.carbon.registry.community.features.server.feature.group-4.2.1 will be ignored because it is already installed.
org.wso2.carbon.event.server.feature.group-4.2.1 will be ignored because it is already installed.
org.wso2.carbon.application.mgt.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list.
org.wso2.carbon.mediators.server.feature.group-4.2.1 will be ignored because a newer version is already installed.
org.wso2.carbon.sequences.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list.
org.wso2.carbon.databridge.datapublisher.feature.group-4.2.1 is already installed, so an update will be performed instead.
org.wso2.carbon.datasource.server.feature.group-4.2.1 will be ignored because it is already installed.
org.wso2.carbon.mediation.templates.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list.
org.wso2.carbon.application.mgt.synapse.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list.
org.wso2.carbon.relay.server.feature.group-4.2.0 will be ignored because it is already installed.
org.apache.synapse.transport.nhttp.feature.group-2.1.2.wso2v4 is already installed, so an update will be performed instead.
org.wso2.carbon.localentry.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list.
org.wso2.carbon.logging.mgt.feature.group-4.2.1 is already installed, so an update will be performed instead.
org.wso2.carbon.security.mgt.server.feature.group-4.2.2 is already installed, so an update will be performed instead.
org.apache.synapse.wso2.feature.group-2.1.2.wso2v4 is already installed, so an update will be performed instead.
org.wso2.carbon.registry.resource.properties.feature.group-4.2.0 is already installed, so an update will be performed instead.
org.wso2.carbon.registry.core.feature.group-4.2.1 is already installed, so an update will be performed instead.
org.wso2.carbon.service.mgt.server.feature.group-4.2.1 is already present because other installed software requires it. It will be added to the installed software list.
org.wso2.carbon.event.common.feature.group-4.2.0 will be ignored because it is already installed.
org.wso2.carbon.task.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list.
org.wso2.carbon.throttle.feature.group-4.2.0 will be ignored because it is already installed.
org.wso2.carbon.proxyadmin.server.feature.group-4.2.1 is already present because other installed software requires it. It will be added to the installed software list.
org.wso2.carbon.rule.mediation.server.feature.group-4.2.0 is already installed, so an update will be performed instead.
org.wso2.carbon.mediation.security.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list.
org.wso2.carbon.core.common.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list.
org.wso2.carbon.user.mgt.feature.group-4.2.1 is already installed, so an update will be performed instead.
org.wso2.carbon.core.runtime.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list.
org.wso2.carbon.identity.authenticator.saml2.sso.server.feature.group-4.2.0 is already installed, so an update will be performed instead.
org.wso2.carbon.identity.authenticator.saml2.sso.ui.feature.group-4.2.1 will be ignored because it is already installed.
org.wso2.carbon.core.server.feature.group-4.2.0 is already present because other installed software requires it. It will be added to the installed software list.
Cannot complete the install because of a conflicting dependency.
Software being installed: Key Store Management Feature 4.2.4 (org.wso2.carbon.security.mgt.feature.group 4.2.4)
Software currently installed: WSO2 Carbon - Service Management Feature 4.2.1 (org.wso2.carbon.service.mgt.feature.group 4.2.1)
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]
I am having similar issues when trying to install any of the features on top of any other wso2 product.
A work-around would be to uncheck the "bundles"(underneath the feauture - eg API Manager - uncheck Key Store bundle) that are causing the dependancy issues.
Hope this helps. I am having a lot of these conflicts when adding: AppServ to Carbon , MessageBroker to ApplicationServ.
We have decided to rather not try and bundle these whole products together , as there are too many issues and bugs etc etc, but rather to run them in standalone mode and utilize SSO.
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
Is there any documentation available that describes the WSO2 svn structure?
It seems that the folder https://svn.wso2.org/repos/wso2/branches/ is deprecated.
Question 1: Should I only be working in the svn folder https://svn.wso2.org/repos/wso2/carbon/?
In the https://svn.wso2.org/repos/wso2/carbon/ folder, I'm managing to piece bits together, for example the difference between Carbon orbit, kernel and platform (see previous stackoverflow question).
In the https://svn.wso2.org/repos/wso2/carbon/platform/branches/ folder, there are 3 sub-folders:
4.0.0
4.0.2AF
4.1.0
Question 2: 4.0.0 and 4.1.0 seem to be for the Carbon Platform, but what is 4.0.2AF - Is this Application Factory?
Question 3: If I want to work on a specific version of Carbon say 4.0.3, it seems that I need to checkout the 4.0.0 branch. What else do I need to do so that mvn clean install will build 4.0.3 for me?
Question: Should I only be working in the svn folder https://svn.wso2.org/repos/wso2/carbon/?
WSO2 is currently doing active development in following svn directory.
https://svn.wso2.org/repos/wso2/carbon/
Question: 4.0.0 and 4.1.0 seem to be for the Carbon Platform, but what is 4.0.2AF - Is this Application Factory?
The branches in https://svn.wso2.org/repos/wso2/carbon/platform/branches/ are for the Carbon platform. The branch 4.0.2AF is for WSO2 App Factory (http://wso2.com/cloud/app-factory/)
Question: If I want to work on a specific version of Carbon say 4.0.3, it seems that I need to checkout the 4.0.0 branch. What else do I need to do so that mvn clean install will build 4.0.3 for me?
You can build Carbon 4.0.3 from following:
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0/patch-releases/4.0.3/
You will be able to build products using the branch. That's why branch SVN URL is given in the links.
Each branch has a patch release for minor platform releases. For example: https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0/patch-releases/
As mentioned in your answer, you can build from a tagged version also.
You can more details about product version and carbon version from the release matrix: http://wso2.com/products/carbon/release-matrix/
You can also subscribe to WSO2 mailing lists and get more information, if you have not subscribed already.
The answer to question 3 is build a checkout a tagged version (of course!!). Thanks to the answer here for pointing me in the right direction.
I was blindly following the wiki documentation which tells you to checkout a branch.
The release matrix for the wso2 platform is here: http://wso2.com/products/carbon/release-matrix/
If I want to build Identity Server 4.0.0 it seems that I need carbon 4.0.3.
Question 1. Will Identity Server only build on carbon 4.0.3, or will it build on 4.0.3+?
I have checked out the source from:
https://svn.wso2.org/repos/wso2/carbon/orbit/branches/4.0.0
https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.0.0
https://svn.wso2.org/repos/wso2/carbon/platform/branches/4.0.0
However, when I look in the orbit patch-releases folder, I only see:
4.0.1
4.0.2
4.0.5
4.0.6
Question 2. Which version of orbit patch release will I need to build for IS 4.0.0?
Question 01
To build IS 4.0.0 you need to build patch-release 4.0.3
But there can be some components from 4.0.0 up-to 4.0.3 but not 4.0.3+ So its better to build all main branch plus patch-release versions below your required version. As Ratha mentioned if you build online these jars will be downloaded if available.
Question 02
You need to build orbit patch-release 4.0.2 since it was used on IS 4.0.0
The reason for not having patch-release 4.0.3 version is there is no difference from 4.0.2 version. So same version is used during production.
Hope this will help you.
if you don't find particular version, that means product is released with older version of jars..
In your case, you might need to build 4.0.2..
Anyway if you do online build, if jars are available in the repo, they will be downloaded..You don't need to build older versions..
If not, you have to..