Not a cluster - only one instance of DataPower on Docker. Yeah ports 3000 and 9443 configured. I verified 3000 by setting up a mock service on it and I am able to test it via SoapUI. After the test I have removed the mock service to avoid conflict with the ''API Connect Gateway service''. I have brought up xml interface, which was disabled, its port is still not open on the docker level, I don't think the xml mgmt should be the cause of 'API Connect Gateway Service' being down-pending.
Original Message:
Sent: Wed January 31, 2024 11:10 PM
From: Ajitabh Sharma
Subject: Setting up APIConnect
Hi Asim,
Is your environment a clustered environment from DP perspective? Does it use AO module of DataPower? If no then these peering objects are least likely culprits. The very first thing we need to ensure is that your api gateway service objects are up on DataPower. Second is to ensure that ports that you specify are reachable from ouside the DP docker. This you can only do when you start the docker instance. Please double check if ports being used (I am assuming 3000 and 9443 here) are exposed and mapped for external consumption.
Also as mentioned in KB link (that you shared above), XML management interface must be up, running and accessible from outside of docker instance. If these are setup well, API Gw service should be up and running and should be reachable and configurable from CMC.
Note: Depending upon license used by DataPower docker image, I have observed that it sometimes has limitation regarding number of ports it can aquire from host, especially if the ports are higher in range (this could be a limitation of docker or OS, I can't tell you for sure). I am not sure if this is documented somewhere but it is certainly a replicable thing. I am not sure if this could be a reason for your failure. Try switching to VM version of DataPower and see if it works.
------------------------------
Ajitabh Sharma
Original Message:
Sent: Wed January 31, 2024 01:48 PM
From: Asim Khan
Subject: Setting up APIConnect
Hi Ajitabh,
I am setting up version 10.0.5 - Configuring DataPower API Gateway. For this version it relies on the gateway peering configurations. Ports I used for different gateway peering objects (rate limit, probe, subscriber etc) ranges from local port 16380 to 16384. Monitor port 26380 to 26384.
I have tried installing the 'API Connect Gateway service' on 3000 or 3100 etc.
Please note, the datapower instance is running on docker.
------------------------------
Asim Khan
Original Message:
Sent: Wed January 31, 2024 12:11 AM
From: Ajitabh Sharma
Subject: Setting up APIConnect
Hi Khan,
Because there is no much detail available, I would like you to check if port number 3001, 3002, 3003, 3004 and 3005 are taken by some other processes? Better change your API Gw to listen on 3100 and see what happens?
------------------------------
Ajitabh Sharma
Original Message:
Sent: Tue January 30, 2024 02:54 PM
From: A Khan
Subject: Setting up APIConnect
Hi Ajitabh
The service is in a non default application domain. However as you pointed this out, service is going into 'down-pending' state. The child objects are in up state. I did try toggling the state back and forth, restart of the domain as well, but no success.
Asim Khan
Original Message:
Sent: Tue January 30, 2024 01:06 AM
From: Ajitabh Sharma
Subject: Setting up APIConnect
Hi Khan,
Are you sure your API connect service is up and running in DataPower? It should be setup in non default domain. If tcp connection test from DataPower to this service is failing, perhaps the service is not up, restarting several times or it is going down frequently for various reasons.
------------------------------
Ajitabh Sharma
Original Message:
Sent: Fri January 26, 2024 02:14 PM
From: A Khan
Subject: Setting up APIConnect
Hi
I have setup Datapower which is running on docker.
While doing corresponding setup of APIC I experience following issue:
Failed to create gateway service MyDomain.
An error occurred communicating with the gateways subsystem at 'https://DataPowerIP:3000' (error: 'connect ETIMEDOUT DataPowerIP:3000'). View error ID 500 API error
Is there a way I can check on apiconnect whether this port is reachanle? Any other input what might go wrong here? Tks
------------------------------
A Khan
------------------------------