Public facing API URL for OPDK

sidd-harth
Participant V

Hi guys, I have installed the on-premise version of Edge (apigee-gateway-4.14.04.00) in our private cloud.

Access the management console at http://xx.x.x.xx:9000/

We created a reverse proxy entry for the same & the Apigee login page was accessible through http://myAPI.demo.com/login

I went ahead and created an sample Api proxy for testing.

How do I determine an public facing API URL(none of the below work),

http://myAPI.demo.com/v1/{proxy-base-path}/{resource-path}
http://router-ip:9001/{proxy-base-path}/{resource-path}
http://{org}-{env}.apigee.net/{proxy-base-path}/{resource-path}
HTTP/1.1 503 Service Unavailable
Date:Wed, 23 Nov 2016 14:30:12 GMT
Content-Length:139
Connection:keep-alive
Content-Type:application/json
Server:Apigee Router
{
  "fault": {
    "faultstring": "The Service is temporarily unavailable",
    "detail": {
      "errorcode": "messaging.adaptors.http.flow.ServiceUnavailable"
    }
  }
}

FYI While installing qpid service failed, I know qpid is for analytics(correct me if I'm wrong).

Installing qpid
Patch qmf/console.py to get qpid-printevents working
Finished installing qpid
Start Qpid Daemon
Starting Qpid AMQP daemon: 2016-11-22 23:22:37 critical Unexpected error: Can't create PID directory: /home/apigee/.qpidd
                                                           [FAILED]
Finished setting up qpid

-------------------------------------
Starting qpidd
Checking if qpidd is up.
.......................................
Last chance. Waiting 2 minutes longer.


Could not connect to port 5672.                            [FAILED]
Check for problems with qpidd startup.
chown: cannot access `/opt/apigee4/var/lock/subsys/qpidd': No such file or directory

@Anil Sagar @sgilson

0 2 289
2 REPLIES 2

hari_vr
Participant IV

Hello @Barahalikar Siddharth

Can you find out what virtualhost that your proxy is listening on? You can see it in your ProxyEndpoint, under the <HTTPProxyEndpoint> tag. You can get details about the vhost by making the below ManagementAPI call.

curl -X GET -u <adminusername> "http://myAPI.demo.com:8080/v1/organizations/<org>/environments/<env>/virtualhosts/<vhostname>"

This will give you the details (including the port) of the virtual host that you are using in your proxy. You can then send requests to your proxy using

http(s)://myAPI.demo.com:vhostPort/{proxy.basepath}/{proxy.pathsuffix}

@Barahalikar Siddharth

By default the port of http or default vhost is 9000. Can you login to any router and fire the below request

curl -v http://localhost:9000/{proxy_basepath}/{proxy_pathsufiix}

Also, if you know the name of the VIP for a particular VHOST, then you can directly use postman client. But remember that there are INTRANET VIP as well as INTERNET VIP. So its possible that your system is not able to access the VIP.

Check the connectivity to the VIP by telnet

telnet <VIP name> 443

Usually the secure port is 443