IBM APIの作成方法オンプレミスとIBM DataPower GatewayをEC2で動作させるには？

DataPower debianパッケージとAPI Connect 5.0.1をオンプレミスの仮想サーバーとして使用して、AWS EC2インスタンスでDataPowerゲートウェイサーバー（7.2節）を実行しています。IBM APIの作成方法オンプレミスと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>

それは「デバッグ」エラーにどのように仕事をしたりしない理由を私は知りません。どんな助けも高く評価されます。

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'

出典

2016-09-06 Christian

ログにデータを記録し、ログをチェックしたり、デバッグプローブをアクティブにして個々のステップの処理を確認したりしてください。 –

@StefanHegny質問するログの抜粋を追加しました。デバッグプローブを有効にするには？ – Christian

'DNSコールバックはホスト 'analytics-lb'を解決できません：エラーを返すので、バックサイドURL' https：// analytics-lb/... 'に接続できません。おそらく、DNSサーバーまたは静的ホストを設定して、その名前をIPにマップできるようにします –

あなたは、デフォルトのドメインネットワークインターフェイスに静的ホストまたはDNSサーバーを追加する必要があります。続き

は

のDataPowerゲートウェイからのログです。 DataPowerはDNS名でホストを見つけることができません。もう1つの方法は、代わりにIPアドレスを使用することです。

出典

2016-11-11 20:10:06 Anders

IBM APIの作成方法オンプレミスとIBM DataPower GatewayをEC2で動作させるには？

答えて

関連する問題