WSO2 EI, grouping sequences into folders - wso2

I'm currently integrating some services via WSO2 EI and because of having a lot of methods, I have created a lot of sequences:
There are more than forty sequences in my project and there will be more.
Is it possible to somehow group these sequences in folders, they are not dynamic and won't be saved in registry?

You can have different ESB projects and composite applications based on your usecase to group the artifacts (e.g. Sequences). Please refer the best practices guide in here.

Related

What is the best Practices to exporting wso2

What is the best to exporting API & EndPoint & DataService on WSo2 ?
usually I export the API & EndPoint in same car.file then exporting dataservice in other carbon file
If your APIs and the Dataservices depend on each other it may be best to package them together. If not, packaging them together would introduce unnecessary downtime to the other service when updating one service. (Redeploying an API would redeploy the Data services). Also, Carbon Applications are deployed in alphabetical order. So if you have anything that depends on the deployment order you can prefix the carbon application with a number or a letter. For example 1_APIServices.car, 2_AppDataServies.car. So they will always be deployed in a certain order on server restart.
This is based on the use cases and requirements. If you want to reuse the data service or the API, then you can have them in separate car files and deploy. Otherwise you can have those in a single car file.

WSO2 apim exporting/importing multiple apis from APIM publisher from develop environment to QA / production environment

How to do a WSO2 apim exporting/importing of multiple apis from APIM publisher from develop environment to QA / production environment . Say I have a 15 Apis defined in APIM publisher with params , need these to be exported to another environment where another wso2 APIM is hosted in that environment with a different db in there.
API Import-Export tool can only be used to migrate APIs in between different environments of the same APIM version. This is not supported for Migrating APIs across different APIM versions. Therefore, It is really suit for your requirement.
But, we can export multiple APIs at once using the WSO2 API Manager import/export tool. Using the command in the following documentation[1] you can export all APIs of a particular tenant.
But importing multiple APIs is not supported at all.
Further, exporting or importing number of APIs as per our choice(like two, three APIs) is also not possible right now.
[1] https://apim.docs.wso2.com/en/latest/learn/api-controller/migrating-apis-to-different-environments/#export-all-the-apis-of-a-tenant-at-once
You can use the CLI tool for this. From that wso2 apim allows you to import/export both APIs and Applications among multiple environments on the same version.

Extracting Sitecore Analytic Data

I'm new to Sitecore concepts, and I'm searching almost five days for an answer. I couldn't find what I'm looking for.
I'm trying to access Sitecore analytic data from a web service. I found a web service of Sitecore with using this document. I want to extract data that are about this. I believe this is a public demo site.
I want to access Web Api, then extract data and use it at my own project. Any idea?
When working with Sitecore 9, the API you want to use to connect to analytics data is known as xConnect. A secure connection is required using trusted certificates, so you cannot connect to an existing instance that somebody else setup like the Habitat demo you linked to.
xConnect is an abstraction API that allows you to collect and search all data in the xDB. The architecture fully supports both vertical and horizontal scaling of xConnect services separate from your Sitecore installations.
Resources
You can read more about xConnect here in the official developer documentation: https://doc.sitecore.net/developers/xp/xconnect/
There is an xConnect tutorial available here: https://doc.sitecore.net/developers/xp/getting-started/#tutorials-xconnect
I also have a small tutorial you can use on GitHub to start learning the concepts: https://github.com/jst-cyr/XConnectTutorial

Criteria for choosing simple Apache Synapse Vs WSO2

While evaluating various ESB's, I came across Apache Synapse & WSO2. In WSO2 it's mentioned that WSO2 completely uses Synapse and built on top of it.
However I am not still clear what additional features does WSO2 offer over Synapse? (Apart from commercial support).
One difference I could see is the web UI to manage proxy definitions, sequences creation etc. Are there any other features which WSO2 provides over Synapse? Also please share if there are any guidelines to choose between Synpase & WSO2
I just wanted to be sure why I am going to WSO2 over Synapse.
Thanks,
Harish
WSO2 ESB offer many great features on top of synapse. I am listing few here.
Graphical management console to create/manage/monitor proxies/APIs and services.
Support for many transports [1].
Statistics, logging and auditing support
Support for many content types
And industry accepted proven performance.
List can go on and on. Hence I am referring you to WSO2 documentation on features[2]. Hope you can get some idea from there.
[1] https://docs.wso2.com/display/ESB481/ESB+Transports
[2] https://docs.wso2.com/display/ESB481/Features

How do you configure WS02 to use different endpoints URIs in different environments?

We are evaluating multiple ESB products currently (Mule, Fuse and WSO2), and one of our key requirements is to easily migrate services between multiple environments. I can see how this can be done in WSO2 with g-reg for the most part, but am struggling to see how we would parametrise the endpoint uris and maintain them separately in each environment? (This seems fairly trivial in Mule and Fuse).
The preferred way is:
Create/save ALL endpoints as registry resource (either using management console or Developer Studio)
Since the endpoints are saved in the registry, now the ESB configuration is totally independent of the environment. (We can create a Carbon Application out of this, which is basically can be deployed in any environment)
So, if you need to move the configuration from dev->qa, you can use the same .car file created