I'm using WSO2-APIM 2.1.0 version.
I've set of API in WSO2-APIM as Inventory whose version is defined as 1.0.0. Then I've created new version 2.0.0 of the same following process given in link.
But now newer version don't have any applications subscribed to it.
Is there is a way to define whatever applications are subscribed to version 1.0.0 should also get subscribed to version 2.0.0.
I do have around 10K applications, doing everything manually is pain. Let me know if there is workaround for the problem.
Related
There are certain API rate limits applied on Facebook v2.7 onwards. Is there anyway I can revert back to v2.6?
You can't use a deprecated API. There is no way you can use API v2.6 now.
The only possible way would be to get an old app that was created using API v2.6.
No you can't use an older version. You have to use the latest version.
You can find this on the facebook for developers website
An app can make calls to the version of the API that was the latest
available when the app was created, as well as any newer,
un-deprecated versions launched after the app is created.
As an example, if your app was created after v2.0 was released, it
will be able to make calls to v2.0 until the expiration date of that
version, and any subsequent versions (v2.1 etc) until their expiration
dates.
I have PizzaV1.0.0 API, which strategy does it use to generate a new V2.0.0 version and keep both in ESB.
If version the CAR, the duplicity of APIs and Sequences.
I have not found a way to version the APIs in eclipse, I need to version the API and some sequences that have changed.
In API Manager I created a new version, now I have two versions published.
What versioning strategy do you use in ESB to stay in sync with API Manager?
Maybe this post can help you
http://nandikajayawardana.blogspot.com.br/2014/02/proxy-service-version-management-with.html
I do what they describe and it is working great.
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.
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.
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/