Has anyone already tried to connect wso2 production with elastic apm server ?
I have done this
export JAVA_OPTS="$JAVA_OPTS -javaagent:/tmp/apm-agent.jar"
export JAVA_OPTS="$JAVA_OPTS -Delastic.apm.service_name=wso2am"
export JAVA_OPTS="$JAVA_OPTS -Delastic.apm.server_urls=http://192.168.1.156:8200"
But i dont have the http request of the API in the APM in kibana
Related
I have installed WSO2 Identity Server using helm like below command
helm install sso wso2/is-pattern-1 --version 5.11.0-4 --namespace my-ns
So the service exposed with ingress and i got a domain like https://identity.wso2.com/carbon i could able to see/login/create service provider in my management console also i'm able to do SSO. But when i'm trying to redirect https://identity.wso2.com:443/oauth2/authorize..... it throws 503 error in browser.
I have followed this Document https://is.docs.wso2.com/en/5.10.0/learn/deploying-the-sample-app/#deploying-the-pickup-dispatch-webapp
On my side, I have built two microservices and a gateway with JHipster.
When I build and deploy the docker files on my laptop and I access to the Registry (localhost:8761), I have well access to the Swagger API of my microservices.
However, when I deploy the same docker files on Elastic Kubernetes Service (AWS) by following this process:
- jhipster kubernetes ...
https://medium.com/#barryvredevoort/deploying-jhipster-microservices-on-aws-eks-elastic-container-service-for-kubernetes-d8ec77f5a9
I do not have the API menu to access the Swagger file with the JHipster registry.
Thank you in advance for your assistance and understand why
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.
Hi I have running wso2 docker image running inside aws instance. I am accessing wso2 apim services(store/publisher/carbon console) through aws ELB. And I have mapped ELB with DNS name inside Route 53.
Problem is I am able to access store and publisher(https://wso2.vitkutin.com./store/ and https://wso2.vitkutin.com./publisher/) successfully but when I'm trying carbon console https://wso2.vitkutin.com./carbon/ gives me below error.I am able to successfully curl -v -k https://localhost:9443/carbon/admin/login.jsp inside docker container. Can someone help me to solve this error ?
<am:fault xmlns:am="http://wso2.org/apimanager">
<am:code>404</am:code>
<am:type>Status report</am:type>
<am:message>Not Found</am:message>
<am:description>The requested resource is not available.</am:description>
</am:fault>
Route 53 DNS name is configured inside carbon.xml and apimanager.xml as shown below :
carbon.xml
<HostName>wso2.xxx.com.</HostName>
<MgtHostName>wso2.xxx.com.</MgtHostName>
apimanager.xml
<GatewayEndpoint>http://wso2.xxx.com.:80,https://wso2.xxx.com.:443</GatewayEndpoint>
<APIStore>
<URL>https://wso2.xxx.com.:443/store</URL>
</APIStore>
<APIPublisher>
<URL>https://wso2.xxx.com.:443/publisher</URL>
</APIPublisher>
As per the access log, it seems the request is sent to 8280 or 8243, instead of 9443. Please check your loadbalancer rules.
I can't configure WSO2 API Manager at EC2 instance of AWS . I install jdk & Set JAVA_HOME at the particular EC2 instance .Then I using sh command to stated the service , service is stated. But I can't display any response at browser when I hit
https://IP:9443
I already successful configure WSO2 API Manager at my local machine.
version of WSO2 API Manager is 1.9.1