How to deploy the api manager on a server? - wso2

I want to deploy the api manager on a server of the company, but I never did't and I need some help, I already installed the wso2 esb and it's ok, but the new release (3.0) is giving me a localhost link to acess the store and the publisher, so I can't access this from another computer what I'm doing wrong?
Any help will be much apreciated

Extract a new APIM 3.0 zip and configure hostname in deployment.toml to be a hostname or a public IP of the server. Then you can use that public IP to access the server.
[server]
hostname = "192.168.0.1"

Related

How to connect a server that run wso2 API manager to show statics on a server that run wso2 analytics

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

WSO2 Micro Gateway Installation and architecture

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.

Is there any way to connect GCP to local IP ?

So my partner builds an API on top .NET and uses a local server to put the project. so to connect the API endpoint I need to create a VPN before I can access the API,
I've done connect from my PC to my partner local server, if in windows 7
create a Workplace then filled Internet Address, destination Name, Username and Password.
So how can I do this from GCP till I can access my partner local server from GCP ?
Don't ask me why not just upload your partner api project to gcp.
thanks..
Have you tried to: just do it?
Just
Create a tunnel from a GCP Compute Instance (Virtual Machine with HTTP/HTTPS) to your partners local server on prefered port?
GCP offers VPN Products - https://cloud.google.com/vpn/docs/concepts/overview - maybe they will help you.
Based on your question, there are a few solutions available. I’ll provide two solutions which may help you.
If you would like to set up an internal path from your GCP instance to your partner’s local server, maybe you should look into this following quickstart on VPNs.
However if you’re looking to use an external path to connect your GCP instance to your partner’s local server, try exposing your partner’s server IP externally and configure a load balancer to it.

WSO2 Enterprise Mobility Manager and Amazon EC2 Instance

I'm trying to install a WSO2 EMM server on Amazon EC2 Instance, but have a problem with it. EC2 instance have 2 IP addresses - one of them is internal Amazon address like 172.32.x.x, another is external real IP.
If I try to setup carbon.xml file with real IP (or domain), I have a problem with thrift server, which can't open port 10500 at a real IP. If I use internal IP running of server is fine, but in application I can't reach identity server (because it's a gray IP, of course).
I tried some tricks with using /etc/hosts file, for example, setup 0.0.0.0 as my domain. In this case server is running without errors, and a can see that port 10500 is open using netstat, but web application is not redirect to identity server.
May be there are any solutions of this problem?
I have to update EMM server to version 1.1.0 and all is working now.
Thanks all!
In the carbon.xml, change the HostName and MgtHostName to the real IP and start the server.
For example if the real IP is 172.32.x.x then HostName and MgtHostName in the carbon.xml should change to:
<HostName>172.32.x.x</HostName>
<MgtHostName>172.32.x.x</MgtHostName>

WSO2 API Manager change in hostname not reflecting

I am trying Wso2 API Manager in EC2 Ubuntu instance. When i run the ./wso2server.sh, the host name is set to the Private IP of the EC2 machine. To change that Private IP to my elastic IP i changed
<ServerURL>https://${carbon.local.ip}:${carbon.management.port}${carbon.context}/services/</ServerURL>
to
https:// <-- elastic_IP --
:${carbon.management.port}${carbon.context}/services/
inside PRODUCT_HOME/repository/conf/carbox.xml.
This didn't solve my issue. So i replaced all ${carbon.local.ip} present inside PRODUCT_HOME/repository/conf/ to my elastic IP, but still when i started the server i am getting 'CarbonUIServiceComponent Mgt Console URL with my private IP'
can someone help me solve this issue of changing the Private_IP to elastic_IP ?
Thanks
Thanks for trying out API Manager on EC2.
This seems to be a bug in API Manager 1.0.0. Created an issue (https://wso2.org/jira/browse/APIMANAGER-703) to track the progress. Fix will be available on API Manager 1.0.1 release (scheduled to happen by mid of September 2012).