2016-09-06 7 views
0

Я запускаю сервер шлюза DataPower (v. 7.2) на экземпляре AWS EC2, используя пакеты debian DataPower и API Connect 5.0.1 на месте в качестве виртуального сервера.Как заставить IBM API Connect на месте и IBM DataPower Gateway работать на EC2?

Однако я не могу заставить его работать должным образом. Я могу успешно опубликовать API, но при попытке вызвать его я получаю:

<?xml version="1.0" encoding="UTF-8"?> 
    <env:Envelope xmlns:env="http://schemas.xmlsoap.org/soap/envelope/"> 
     <env:Body> 
     <env:Fault> 
      <faultcode>env:Client</faultcode> 
       <faultstring>Internal Error (from client)</faultstring>    
     </env:Fault> 
     </env:Body> 
    </env:Envelope> 

Я не знаю, почему он не работает или как «отладка» ошибка. Любая помощь будет высоко оценен.

Ниже лаг от шлюза DataPower:

time(descending) category level domain tid direction client msgid message Show last 50 100 all 
Wednesday, September 7, 2016 
1:23:11 PM mpgw error APIMgmt_96F1E39EF5 12405713 error  0x01130006 mpgw (webapi-internal): Failed to establish a backside connection 
1:23:11 PM mpgw error APIMgmt_96F1E39EF5 12405713   0x80e00126 mpgw (webapi-internal): Valid backside connection could not be established: Failed to establish a backside connection, url: https://analytics-lb/x2020/v1/events/logevent 
1:23:11 PM mpgw error APIMgmt_96F1E39EF5 12405713   0x80e00623 mpgw (webapi-internal): Cannot find the requested resource for the URL 'https://analytics-lb/x2020/v1/events/logevent' 
1:23:11 PM mpgw error APIMgmt_96F1E39EF5 12405729 error  0x01130006 mpgw (webapi-internal): Failed to establish a backside connection 
1:23:11 PM mpgw error APIMgmt_96F1E39EF5 12405729   0x80e00126 mpgw (webapi-internal): Valid backside connection could not be established: Failed to establish a backside connection, url: https://analytics-lb/x2020/v1/events/logevent 
1:23:11 PM network error APIMgmt_96F1E39EF5 12405713   0x80e00048 loadbalancer-group (analytics-lb): DNS Callback cannot resolve host 'analytics-lb': returning error 
1:23:11 PM mpgw error APIMgmt_96F1E39EF5 12405697 error  0x01130006 mpgw (webapi-internal): Failed to establish a backside connection 
1:23:11 PM mpgw error APIMgmt_96F1E39EF5 12405697   0x80e00126 mpgw (webapi-internal): Valid backside connection could not be established: Failed to establish a backside connection, url: https://analytics-lb/x2020/v1/events/logevent 
1:23:11 PM mpgw error APIMgmt_96F1E39EF5 12405697   0x80e00623 mpgw (webapi-internal): Cannot find the requested resource for the URL 'https://analytics-lb/x2020/v1/events/logevent' 
1:23:11 PM mpgw error APIMgmt_96F1E39EF5 12405729   0x80e00623 mpgw (webapi-internal): Cannot find the requested resource for the URL 'https://analytics-lb/x2020/v1/events/logevent' 
1:23:11 PM mpgw error APIMgmt_96F1E39EF5 12405745 error  0x01130006 mpgw (webapi-internal): Failed to establish a backside connection 
1:23:11 PM mpgw error APIMgmt_96F1E39EF5 12405745   0x80e00126 mpgw (webapi-internal): Valid backside connection could not be established: Failed to establish a backside connection, url: https://analytics-lb/x2020/v1/events/logevent 
1:23:11 PM network error APIMgmt_96F1E39EF5 12405697   0x80e00048 loadbalancer-group (analytics-lb): DNS Callback cannot resolve host 'analytics-lb': returning error 
1:23:11 PM mpgw error APIMgmt_96F1E39EF5 12405745   0x80e00623 mpgw (webapi-internal): Cannot find the requested resource for the URL 'https://analytics-lb/x2020/v1/events/logevent' 
1:23:11 PM network error APIMgmt_96F1E39EF5 12405729   0x80e00048 loadbalancer-group (analytics-lb): DNS Callback cannot resolve host 'analytics-lb': returning error 
1:23:11 PM network error APIMgmt_96F1E39EF5 12405745   0x80e00048 loadbalancer-group (analytics-lb): DNS Callback cannot resolve host 'analytics-lb': returning error 
1:23:11 PM network error APIMgmt_96F1E39EF5 100447   0x80e0004e loadbalancer-group (mgmt-lb): Standard health check failed - server down 'https://192.168.247.146:2443/v1/catalogs/status' 
1:23:11 PM multistep error APIMgmt_96F1E39EF5 100447 health  0x80c00075 loadbalancer-group (mgmt-lb): External URL: 'https://192.168.247.146:2443/v1/catalogs/status' timed out. 
1:23:11 PM network error APIMgmt_96F1E39EF5 100447   0x80e00625 loadbalancer-group (mgmt-lb): Connect to URL 'https://192.168.247.146:2443/v1/catalogs/status' timed out 
1:23:11 PM network error APIMgmt_96F1E39EF5 100447   0x80e00049 xmlmgr (webapi): Host connection failed to establish: 192.168.247.146 : tcp port 2443 
1:23:11 PM network error APIMgmt_96F1E39EF5 100447   0x00b30009 xmlmgr (webapi): Host connection could not be established 
1:23:10 PM mpgw error APIMgmt_96F1E39EF5 12405617 error  0x01130006 mpgw (webapi-internal): Failed to establish a backside connection 
1:23:10 PM mpgw error APIMgmt_96F1E39EF5 12405617   0x80e00126 mpgw (webapi-internal): Valid backside connection could not be established: Failed to establish a backside connection, url: https://analytics-lb/x2020/v1/events/logevent 
1:23:10 PM mpgw error APIMgmt_96F1E39EF5 12405601 error  0x01130006 mpgw (webapi-internal): Failed to establish a backside connection 
1:23:10 PM mpgw error APIMgmt_96F1E39EF5 12405585 error  0x01130006 mpgw (webapi-internal): Failed to establish a backside connection 
1:23:10 PM mpgw error APIMgmt_96F1E39EF5 12405601   0x80e00126 mpgw (webapi-internal): Valid backside connection could not be established: Failed to establish a backside connection, url: https://analytics-lb/x2020/v1/events/logevent 
1:23:10 PM mpgw error APIMgmt_96F1E39EF5 12405585   0x80e00126 mpgw (webapi-internal): Valid backside connection could not be established: Failed to establish a backside connection, url: https://analytics-lb/x2020/v1/events/logevent 
1:23:10 PM mpgw error APIMgmt_96F1E39EF5 12405601   0x80e00623 mpgw (webapi-internal): Cannot find the requested resource for the URL 'https://analytics-lb/x2020/v1/events/logevent' 
1:23:10 PM mpgw error APIMgmt_96F1E39EF5 12405617   0x80e00623 mpgw (webapi-internal): Cannot find the requested resource for the URL 'https://analytics-lb/x2020/v1/events/logevent' 
1:23:10 PM mpgw error APIMgmt_96F1E39EF5 12405585   0x80e00623 mpgw (webapi-internal): Cannot find the requested resource for the URL 'https://analytics-lb/x2020/v1/events/logevent' 
1:23:10 PM network error APIMgmt_96F1E39EF5 12405601   0x80e00048 loadbalancer-group (analytics-lb): DNS Callback cannot resolve host 'analytics-lb': returning error 
1:23:10 PM network error APIMgmt_96F1E39EF5 12405617   0x80e00048 loadbalancer-group (analytics-lb): DNS Callback cannot resolve host 'analytics-lb': returning error 
1:23:10 PM network error APIMgmt_96F1E39EF5 12405585   0x80e00048 loadbalancer-group (analytics-lb): DNS Callback cannot resolve host 'analytics-lb': returning error 
1:23:09 PM mpgw error APIMgmt_96F1E39EF5 12405521 error  0x01130006 mpgw (webapi-internal): Failed to establish a backside connection 
1:23:09 PM mpgw error APIMgmt_96F1E39EF5 12405505 error  0x01130006 mpgw (webapi-internal): Failed to establish a backside connection 
1:23:09 PM mpgw error APIMgmt_96F1E39EF5 12405521   0x80e00126 mpgw (webapi-internal): Valid backside connection could not be established: Failed to establish a backside connection, url: https://analytics-lb/x2020/v1/events/logevent 
1:23:09 PM mpgw error APIMgmt_96F1E39EF5 12405505   0x80e00126 mpgw (webapi-internal): Valid backside connection could not be established: Failed to establish a backside connection, url: https://analytics-lb/x2020/v1/events/logevent 
1:23:09 PM mpgw error APIMgmt_96F1E39EF5 12405505   0x80e00623 mpgw (webapi-internal): Cannot find the requested resource for the URL 'https://analytics-lb/x2020/v1/events/logevent' 
1:23:09 PM mpgw error APIMgmt_96F1E39EF5 12405521   0x80e00623 mpgw (webapi-internal): Cannot find the requested resource for the URL 'https://analytics-lb/x2020/v1/events/logevent' 
1:23:09 PM network error APIMgmt_96F1E39EF5 12405505   0x80e00048 loadbalancer-group (analytics-lb): DNS Callback cannot resolve host 'analytics-lb': returning error 
1:23:09 PM network error APIMgmt_96F1E39EF5 12405521   0x80e00048 loadbalancer-group (analytics-lb): DNS Callback cannot resolve host 'analytics-lb': returning error 
1:23:08 PM network error APIMgmt_96F1E39EF5 12618848 scheduled  0x80e00040 xmlmgr (webapi): url-open: Remote error on url 'http://127.227.158.245:2934/catalogs/v1/catalogs/gateway.xml' 
1:23:08 PM network error APIMgmt_96F1E39EF5 12618848   0x80e00625 Connect to URL 'http://127.227.158.245:2934/catalogs/v1/catalogs/gateway.xml' timed out 
1:23:07 PM network error APIMgmt_A0AABCC130 68463   0x80e0004e loadbalancer-group (mgmt-lb): Standard health check failed - server down 'https://192.168.247.146:2443/v1/catalogs/status' 
1:23:07 PM system error APIMgmt_A0AABCC130 12405249   0x80e0027d Unable to open URL 'store:///identity.xsl' 
+0

Зайдите в источник данных и проверьте журналы и/или активируйте пробный отладочный модуль, чтобы просмотреть обработку отдельных шагов. –

+0

@StefanHegny Добавлен запрос на отладку журнала. Как активировать зонд отладки? – Christian

+0

В журнале может быть достаточно информации: 'DNS Callback не может разрешить хост 'analytics-lb': return error', поэтому он не может подключиться к обратному URL-адресу' https: // analytics-lb/... 'So возможно, вы начинаете с установки DNS-серверов или статического хоста, чтобы имя можно было сопоставить с IP-адресом –

ответ

0

Вы должны добавить статические хосты или сервер DNS для домена по умолчанию сетевого интерфейса. DataPower не может найти хост через имя dns. Другой вариант - вместо этого использовать IP-адрес.