As the Odata Service in Micro Integrator 7.x has to use keywords "odata_service" and "Datasource", it is right only one Odata Service can be built in one WSO2 Micro Integrator instance?
Is the only work around (to have muliple Odata Service) is to have mulitple MI instance?
Thanks.
"odata_service" and "Datasource" are not keywords. I am assuming you are referring to this documentation https://ei.docs.wso2.com/en/next/micro-integrator/use-cases/examples/data_integration/odata-service/
The above values are shown as example. You can create multiple DataServices with ODataEnabled with different service name and dataservice id in a single Micro Integrator instance.
Related
I try to start service micro integrator wso2 7.1.0
Enterprise Integration 7.1.0 Micro integrator
but, i cant open dashboard https://localhost:9743/dashboard/login
This site can’t be reached
what i missed ?
It is because, when you start Micro Integrator, the monitoring dashboard does not start automatically. It is separate from the Micro Integrator runtime. You need to start the dashboard in a different terminal and connect it to the runtime. https://ei.docs.wso2.com/en/latest/micro-integrator/administer-and-observe/working-with-monitoring-dashboard/#setting-up-the-dashboard
Can somebody please explain, how WSO deploy its products?
First i got familiar with WSO EI 6.6. I could create a proxy service or use the DSS to make API alternative to entity framework in .net core services.
Then I found out that the superior product to WSO2 EI is WSO2 APIM - api manager.
WSO2 APIM has WSO2 IS included, so it is basically the single point for authentication and service proxying and so on.. However I have not seen there any option to make the DSS ??
WSO EI 7.0 is completly different to WSO EI 6.6 as far as i understand. WSO EI 7 is the name for 3 other products balerina integrator, microservice and streaming integrator. None of these services has the /carbon framework and all of them are just some apis for some custom editor. If this is true, why do they call it WSO EI 7?? Does that mean that the configuration of proxy services or access to database through res api is obsole and should not be used for new project?
So basically there is no way to have DSS in latests products?? Do I must use WSO EI 6.6 in order to use the DSS?
I have scratched my head at the naming and grouping of these products previously as well. From what I could figure, every now and then the groups change. As you have noticed rightfully, EI was the latest one to change. It indeed split into 3 entities. It is however still usable with code from EI 6.6. The Micro Integrator can be downloaded separately and used with all the code and CAR files made with 6.6. I have run a couple of them and found no problems thus far. It is basically the latest version but without the Carbon framework and frontend. One MI instance also runs just 1 CAR file but does so really fast.
As for your DSS needs I have no experience with that side of WSO2. I googled however and found that DSS can be downloaded right here as a standalone product. I hope that solves your last question.
The APIM is not superior to EI either, but functions in a different way. Since the older products were all based on Carbon as you mentioned before means there was a certain bit of overlap. IS for example can also be downloaded separately.
If I was to guess I would say they WSO2 will be trying to make all their services into Microservice versions in the upcoming years. This is just speculation btw.
If you want to dive more into the reasoning behind WSO EI 7.0 and why it was decided to work like that I would suggest this talk by the WSO2 director.
We are doing technical feasibility for migrating to WSO2 Micro Integrator 7.X version.
From the documentation it seems the admin services can now be explored in a REST API way or in a visualized dashboard manner (https://ei.docs.wso2.com/en/latest/micro-integrator/administer-and-observe/working-with-management-api/) .
What about other admin services like AuthenticationAdmin service and others , see link in paranthesis (https://docs.wso2.com/display/EI650/Working+with+Admin+Services). Is it possible to access these back end services in WSO2 Micro Integrator 7, keeping in view that only a micro integrator is used within the plaform.
I am wondering as the footprint of a micro integrator is small , these admin backend services which earlier available may not be accessible within the Micro Integrator at all. Do let me know if that is a correct understanding.
Hi Rajarshi Bhattacharjee
Basically the admin services which were in EI 6x series is no-more in Micro Integrator. These are new REST APIs which are there to retrieve the artifacts. You might see the available rest APIs in https://github.com/wso2/micro-integrator/blob/master/doc/mi-rest-api.md . Please report an issue in https://github.com/wso2/micro-integrator/issues if there is a necessity for other services.
Thanks !
Nirothipan
I have already read many documentations of WSO2, there are some products of WSO2 such as: Enterprise Integration (EI), API Management (APIM), Identity Access Management (IS), Analytics Stream Processing (SP). I can understand the functions of IS and SP.
1. But I dont know what are differences between EI and APIM?
2. When can we use EI? When can we use APIM?
3. Can we merge WSO2 EI and APIM and IS and SP Products to execute all of them on one server?
Sorry for many questions, but I am really confuse in these matters, please give me advice.
WSO2 EI can be used to integrate different systems, orchestrate and then expose as new services/APIs.
WSO2 APIM can be used to manage those services/APIs. You can manage security, rate limiting, CORS, etc. and can see analytics of API usage etc. too. For APIM analytics, there is a customized version of SP which you can download separately.
You can't run all 4 as a single server. Those are 4 runtimes, so you have to start them separately.
I have installed WSO2 AS, after I have installed GReg and ESB by Feature Install. It was OK.
But now I would like to know how to I have to configure GReg and ESB using same WSO2 Application Server.
For example, I would like to configure ESB and GReg following pattern #2 or pattern #3 of this blog post but considering that ESB and GReg were installed in same WSO2 AS instance.
Is that a correct escenary ? or I Have to install allways in separated AS ?
Regards!
Oscar
These patterns are used when you need to share registry spaces across multiple server instances. A common config registry space is used to share configuration details across multiple instances of the same product. A common governance registry space is used to share metadata across the multiple products in a platform.
In the setup you have described,since ESB and AS products are installed in the same server, there is no need for sharing the registry space.
Sharing the registry space would be required only if these products are run as separate server instances.
Is there any particular reason/requirement you have for the setup described?
Regards,
Gillian