IBM Support

Best Practice: Use a custom Gateway peering object when configuring the API Connect Gateway service

Troubleshooting


Problem

Rebooting your DataPower can bring the default Gateway peering object "default-gateway-peering" to disabled state. If the API Connect Gateway service references this object, it can result in it going down.

Symptom

The API Connect Gateway service goes in to a down state

Cause

The default gateway peering object "default-gateway-peering" has some specific default config by system that will bring it to disabled state after rebooting.

Resolving The Problem

It's best practice for customers to create their own gateway-peering objects for their purpose to avoid this problem as there is no startup config, which disables their custom objects. 

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"ARM Category":[{"code":"a8m0z0000001it3AAA","label":"API Connect-\u003EManagement and Monitoring (MM)-\u003EGateway Service"}],"ARM Case Number":"TS009838618","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0.0;10.0.1;2018.4.1.0;and future releases"}]

Document Information

Modified date:
19 July 2022

UID

ibm16605343