I've tried working on the API Manager subscription workflow in a single instance and it's working fine. Now I want the same to be performed on a distributed deployment environment. Can I know on which node shall I update the SubscriptionCallbackService.epr path and on which node I should enable the " Engaging the WS Workflow Executor in the API Manager ".
Note:
We are using EI 6.5.0 and APIM 2.6.0 and 3.1.0 in two different environments.
You need to copy the <API-M_HOME>/business-processes/epr (any of the apim nodes) folder to <EI_HOME>/wso2/business-process/repository/conf/epr, SubscriptionCallbackService following value should be updated, Gateway port is 8243 if you have not done any offset.
<wsa:Address>https://<APIM_GATEWAY_IP>:PORT/services/WorkflowCallbackService</wsa:Address>
"Engaging the WS Workflow Executor in the API Manager" should be done in the devportal node
Related
i downloaded the wso2 Micro integrator and api-manager the two component are up and running.
Now i need to Connect the api-manager to micro integrator through service catalog , i found in api-manager but i need some clarity, how the two components are integrating each other . there're any other way to connect the API-manager and micro integrator.
we don`t have micro-integrator dashboard also.
i have a fresh setup of api-manager and micro integrator,i stared the two components in cmd it`s up and running, i used service catalog in apim, Under Micro Integrator (wso2ei-7.1.0)'s conf/deployment.toml file,
i enable this section as well as dashboard also. I couldn't find any logs in log folder
I have this section:
Integration API Manager and Micro integrator via service catelog is easy.
You just need to add the following configurations in MI deployment toml and publish the integrations.
[[service_catalog]]
apim_host = "https://localhost:9443"
enable = true
username = "admin"
password = "admin"
Once you have created the integration service and deployed it in the Micro Integrator, you only need to start the two servers (API-M server and the Micro Integrator server). The client in the Micro Integrator publishes the integration services to the API-M layer during server startup.
More information can be found in this doc page.
Integrate apim with micro integator
How to integrate apim with micro integator without using integration studio
If you have already created a back-end API, then you don't need Micro-integrator, and you can directly expose that API through the API Manager. The API Manager can add schema validation as well.
If you need to implement additional message mediations, message transformations, and service orchestration on top of your existing back-end services, then you can do that using Micro-integrator and expose that as an API using API Manager.
Please see - https://apim.docs.wso2.com/en/latest/get-started/integration-quick-start-guide/
Micro Integrator is already embedded with the API Manager 4.1 .If you need to add some transformations to your API that you didn't found in the API Manger ,then you have to do it in the Integration Studio and then publish it to the Publisher Portal using service catalog feature.
You can follow this documentation
https://apim.docs.wso2.com/en/latest/tutorials/integration-tutorials/service-catalog-tutorial/
Integrating API Manager and Micro-integrator will be done via the Service Catalog by adding the following configurations in MI deployment .toml.
[[service_catalog]]
apim_host = "https://localhost:9443"
enable = true
username = "admin"
password = "admin"
Once you have created the integration service and deployed it in the Micro-integrator, you only need to start the two servers (APIM server and the Micro-integrator server).
More information - https://apim.docs.wso2.com/en/latest/integrate/develop/working-with-service-catalog/
WSO2 API Manager needs to restart after creating and publishing a new API in the new version (4.1.O). In old versions, there is no need to restart it.
Do you have a distributed API Manager deployment (not an all-in-one setup)? I suspect there could be a misconfiguration between the Control plane and the gateway node. Better to verify the configurations first (refer [1]).
In a distributed setup, gateway nodes listen to a JMS topic in the control plane. when API is deployed, gateway gets an event and after that, it queries the CP and gets the API-related artifacts. I suspect this CP->GW event is not reaching the gateway. As a result, APIs are not deployed in the gateway and cannot invoke it.
Gateway node does not keep the API artifacts stored. When there is a restart, gateway node calls the control plane directly and gets the available API-related artifacts and deploys them. That is why it works when you restart the gateway.
This is the new event-based mechanism we use in the APIM versions 3.2 onwards. That is why it worked in old versions.
[1] https://apim.docs.wso2.com/en/latest/install-and-setup/setup/distributed-deployment/deploying-wso2-api-m-in-a-distributed-setup/
Good day
I have created my ESB project using the enterprise integration studio provided by wso2 and have also downloaded the API manager separately. Meanwhile when I start WSO2 API manager, API Publisher and developer dashboard open.
I just want to create WSO2 API Gateway. How can I achieve this also I want gateway should be access based.
Please assist me how can I proceed for the gateway implementation.
I only want the WSO2 API gateway.
WSO2 APIM is consist of 5 profiles as Gateway, Traffic Manager, Publisher, Store(Devportal in APIM 3.x series) and KM profiles. You can start an APIM with the default profile (if you started as sh wso2server.sh) and you can work with each profile. But if you want to start APIM as Gateway profile, then you need to start the server with "-Dprofile" mode as follows.
sh wso2server.sh -Dprofile=gateway-worker
You can read this document https://docs.wso2.com/display/AM260/Product+Profiles to aware of the profile of wso2 APIM.
And WSO2 has Micro GW product too, you can find more details about that MGW here https://docs.wso2.com/display/AM260/Working+with+the+API+Microgateway. You can download the form here https://wso2.com/api-management/api-microgateway/ and test.
We are designing wso2 apim 2.0 cluster deployment architecture, from 2.0 clustering, we just found distribution deployment description, so
Is the wso2 apim gateway 2.0 cluster same with 1.10?
Any recommendation for system CPU/MEMORY requirement?
wso2 apim 2.0 has traffic manager, how to cluster it?
For store/publisher, how to cluster them?
When integration with APIM Analytics, do we just need to config gateway workers?
1) There are configuration changes, and also new configs, in gateways. But gateway clustering has not been changed.
2) See Installation Prerequisites and Tuning Performance
3) There is no public document yet. It'll be there soon. Until now, you can cluster it in the same way gateways are clustered.
4) Store and publisher should be in the same cluster.
5) Gateway workers, store and publisher
Update:
About Dep-Sync: In gateway worker-manager setup, we only publish API synapse files to manager node, and then use dep-sync to copy those APIs to gateway workers. You can use anything that can sync artifacts between nodes instead of SVN based dep-sync. (eg. rsync)