I am new to WSO2 product. I have setup WSO2 ESB cluster. Servers comes up nicely but configuration done on server1 doesn't gets reflected to server2, say, I created datasource on server1, but it doesn't shows up on second server in cluster.
Related
How do I upload the API I created in WSO2 Integration Studio installed on my own computer to the WSO2 API Manager on the remote server.
From the Add new server menu, I clicked the WSO2 Remote Server option under WSO2 and entered the host and server URL information, but it did not publish. When I examined WSO2's own documents, I could not find detailed resources about connecting to a remote server and publishing.
Can you help with this?
Can you add your integration studio version and WSO2 Api Manager version?
You can try this documentation https://apim.docs.wso2.com/en/latest/integrate/develop/working-with-service-catalog/
You can register the service in the service catelog as below.
Start the WSO2 Micro Integrator pointing to API Manager.
You should have the carbon app of that particular service in the Micro Integrator.
When Micro Integrator starts it registers the available services in the API Manager.
From logging into the APIM publisher you can create an API.
Instructions are available here - https://apim.docs.wso2.com/en/latest/integrate/develop/working-with-service-catalog/
How to connect a server that run wso2 API manager to show statics on a server that run wso2 analytics that actually exist on differnt servers with different IP.
I am using version 3.2.0
You can follow the documentation and configure analytics for APIM 3.2.0.
In the configurations, instead of using localhost, use the IP address of the analytics server.
https://apim.docs.wso2.com/en/3.2.0/learn/analytics/configuring-apim-analytics/#configuring-apim-analytics
Does the Micro Gateway and API manager always have to be installed on the same servers?
Does the Micro Gateway setup require WSO2 Identity Server and WSO2 Enterprise Integrator for Hybrid API?
We have an architecture that would be working with 3 servers (1) Cloud for API Manager and Developer Portal providing Authentication and Analytics and store for (2) Production Environment (3) Sandbox Environment
Does the API manager needs to be installed in all the servers to set API Gateway and API Micro Gateway?
So here are the task that I have tried to set the WSO2 API manager and the Micro Gateway services in my local system , so here is a sample configuration
OS: Ubuntu server 18 LTS
WSO2 API Manager - Local Server IP: 192.168.1.50
WSO2 MicroGateway service (Sandbox) - Local Server IP: 192.168.1.51
WSO2 MicroGateway service (Production) - Local Server IP: 192.168.1.52
API Manager:
Installed all prerequisites
Install directly in the server
Changed the hostname to IP address in deployment.toml since I tried changing in carbon.xml and api-manager.xml but it get override
All the services were successfully active
Carbon Admin - http://192.168.1.50:9443/carbon, Admin Module - http://192.168.1.50:9443/admin, Developer Portal - http://192.168.1.50:9444/devportal, Publisher - http://192.168.1.50:9443/publisher
MicroGateway:
Create a mock hello world API using PHP to access the backend and datastore services.
Created a sample OpenAPI 3.0 yaml file to forward the request to the backend php services.
Installed all prerequisites
I had document to install the Microgateway services in docker, but I decided to try the MGW services installation directly within the server without docker
Created a API using micro-gw init and placed the yaml file within api-definitions
created the build successfully
Ran the build using gateway which was accessible using Postman.
Tried to change the hostname of microgateway service to listen IP instead of localhost but gets overrides to localhost:9090 however the service can be accessible using IP so no further changes made.
Configuration of API Manager and MGW
Uploaded the same YAML to API manager using publisher to configure the API manager and microgateway services.
Used API managers key certificates to set the microgateway (which failed)
create the end points to point to Production and Sandbox micro gateways using the IP address and the port number http://192.168.1.51:9090 and http://192.168.1.52:9090
Accessed the developer portal, created a token key.
However, the token failed to help access the microgateway service. Even I tried using the URL provided by the API manager http://192.168.1.50/sample/context/1/test but still inaccessible.
WSO2 EMM Version: 2.0.1
Database: MySQL
I am setting VPN on iOS device using https://docs.wso2.com/display/EMM201/Setting+Up+a+VPN+on+iOS+Devices+via+the+REST+API API.
But every time I call an API, WSO2EMM is creating a new VPN. I just want to update an existing VPN connection or remove the VPN connection if an update is not possible.
How can I achieve that?
I want to set up WSO2 Identity Server cluster and an other for WSO2 API Manager. Identity server will be used to enable SSO for our applications and also to register existing Identity Providers (ex: ADFS). API Manager will be used to manage our Rest API's and to provide them to our applications. I also want to configure the Identity Server to be the Key Manager.
As the documentation says for WSO2 Cluster deployment, Management nodes are specialized in management of the setup, while worker nodes are specialized in serving requests to deployment artifacts. Besides that, API Manager product provides 5 diferent profiles (key-manager, publisher, store, gateway-manager and gateway-worker).
For now, I have 3 servers (server1, server2 and server3) in which I will install and configure the WSO2 Cluster nodes for Identiy Server and API Manager. I also created a load balancer that will be used to forward requests for each cluster nodes (IS and AM).
After some reading, I concluded that I would need to install WSO2 IS and WSO2 AM as manager nodes on the server1 and the two other servers would be used as worker nodes.
I think I already managed to install and configure Identity Server cluster, the url mgt.identity.mydomain.pt points to the server1 node and identity.mydomain.pt points to server2 and server3 nodes for load balancing requests.
Now I'm stuck with API manager cluster configuration, I want to use server2 and server3 as the gateway to load balance requests (apis.mydomain.pt) for our Rest API's and use server1 to manage our API's using store and publiser components (mgt.apis.mydomain.pt). I'm struggling to understand which profile I have to use for each nodes. I tried to install a manager node on server1 with the default profile and install worker nodes on the server2 and server3 with the gateway-worker profile but I'm getting errors related to the Deployment Synchronizer (error logs). I guess I am doing something wrong because those errors only shows up when using the gateway-worker profile.
Anyone can explain me the difference between worker and manager nodes and how they are related with wso2 profiles?
UPDATE:
I found out what I was missing and was causing the error. I was starting the server2 and server3 just with -Dprofile=gateway-worker, I added -DworkerNode=true and I have no errors in log anymore.
Anyway, I am still a little bit confused about using the gateway-manager and gateway-worker profiles.
https://docs.wso2.com/display/CLUSTER44x/Configuring+SVN-Based+Deployment+Synchronizer contains Deployment synchronizer related configurations. Can you check whether you configured the manager and worker nodes correctly