How to install DataServicesServer on WSO2 ESB 4.9.0? - wso2-data-services-server

Does anyone know how to install DataServicesServer on wso2esb 4.9.0 ? It's not in the repository of carbon 4.4.0 (on which I'm fairly sure esb 4.9.0 is based).
Repository url that I was looking at: http://product-dist.wso2.com/p2/carbon/releases/4.4.0

WSO2 ESB is based on carbon 4.4.0. Therefore, the corresponding P2 repository is http://product-dist.wso2.com/p2/carbon/releases/wilkes/

Related

Installing feature in wso2 apim

How do i install Logging management feature in wso2 apim version-3.1.1 using pom file.
I tried from official doc in below link:
https://docs.wso2.com/m/mobile.action#page/85376969
But I'm facing dependency conflict.

WSO2 APIM 2.6.0 version is compatible with WSO2 IS 5.6.0

I am working with WSO2 APIM 2.6.0 version and trying to integrate with WSO2 Identity Server v 5.6.0
Identity Server 5.6.0 is already present in the project so we donot want to make any changes in that.
However, due to technical road block in APIM 2.5.0, I am trying to migrate APIM from 2.5.0 to 2.6.0.
APIM is migrated as it is provided in the documentation link but when I am trying to integrate with IS 5.6.0, its not happening as it should be. The token which are generated from IS 5.6.0 are not authorize in APIM 2.6.0 and its throwing error as below
ERROR - AMDefaultKeyManagerImpl Invalid OAuth Token : Invalid Access
Token. Access token is not ACTIVE.
[2019-09-09 08:49:07,825] ERROR - WebAppAuthenticatorImpl Authentication
failed. Please check your username/password
There are no changes in the process as to how we used to generate the token earlier and perform operations when APIM 2.5.0 and Identity Server 5.6.0 was integrated.
Can some one please let me know if the compatibility exists between APIM 2.6.0 and Identity 5.6.0
Thanks
Compatibility between APIM 2.6.0 and IS 5.6.0 can't be guaranteed as it's not officially tested by WSO2. The compatible IS version for APIM 2.6.0 is IS 5.7.0.

Different structure in a conan repository in Artifactory

I've noticed a different repository structure for a conan repository in Artifactory.
1. Artifactory Enterprise 6.3.2
Repository Layout: conan-default
Repository strucutre: repository_name/conan_username/conan_package_name/version/channel
2. Artifactory Enterprise 5.4.6
Repository Layout: conan-default
Repository strucutre: repository_name/conan_package_name/version/conan_username/channel
Do you know why? Is it because the Artifactory version? I haven't found anything in Artifactory release notes related to the conan repository structure.
The default layout for conan packages was migrated in Artifactory 6, to match other package managers default layouts that put the user (organization) name first, as the most important classification of packages.
The migration should be automatic, and affect only the visual appearance in Artifactory web UI. If there is some other changes, or the conan client breaks (and this is the reason you are asking), then, it is a failing migration in Artifactory upgrade. It should be reported to JFrog and ask support to help recover it.

How to host a p2 repository on artifactory oss

I know that artifactory oss version does not support hosting p2 repositories natively.
Is it hovewer possible to do it somehow without such support? I think you cannot get a pro version for free for open source projects?
If you want to have p2 or npm repositories natively you need the Artifactory Pro version.
There are not option to have a free Artifactory pro version without support for opensource projects.
If you don't want to buy Artifactory PRO, there are free alternatives.

Issues in deploying .car file in wso2 esb

I am creating the >car file using Developer studio and deploying using Wso2 Carbon server4.0.
When i am deploying always getting the older versions. Some times the server not properly deploying the car. And also how to build the project to get the latest changes.
Please suggest me a better procedure creating and deploying the car file.
I am using Wso2 esb 4.7.0 version,
Developer studio 3.2 version.
Refer to the following documentation.
http://docs.wso2.org/display/DVS310/Deploying+and+Debugging

Resources