IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.



#Automation


#Applicationintegration
#webMethods
#Integration
 View Only
Expand all | Collapse all

webMethods API Gateway Q&A - Upgrading API Gateway cluster fails at migrate.sh step

  • 1.  webMethods API Gateway Q&A - Upgrading API Gateway cluster fails at migrate.sh step

    Posted 10/10/23 04:40 AM

    Product/components used and version/fix level:

    Upgrading an API Gateway cluster from 10.5 to 10.11.
    The source cluster consists of three nodes: qa-01, qa-02, qa-03, and the target cluster consists of qa-04, qa-05, qa-06.

    Detailed explanation of the problem:

    Following the upgrading API Gateway cluster section from the following guide: https://documentation.softwareag.com/webmethods/api_gateway/yai10-11/10-11_Api_Gateway_Upgrade_Guide.pdf

    Running this command on qa-05. /var/tmp/config.properties, the file was copied from …/local/apps/webM/APIGateway/IntegrationServer/instances/API/packages/WmAPIGateway/config/resources/elasticsearch dir.

    Error messages / full error message screenshot / log file:

    ./migrate.sh datastore -dstoreSrc /var/tmp/config.properties command failed with the following errors:

    Error while reindexing APIs. Error type - illegal_argument_exception, reason [phx-wmgateqa-03:9240] not whitelisted in reindex.remote.whitelist

    Data store migration failed

    Reason - Error while reindexing APIs. Error type - illegal_argument_exception, reason [phx-wmgateqa-03:9240] not whitelisted in reindex.remote.whitelist


    #API-Management
    #webMethods
    #API-Gateway
    #Tuesday-troubleshooting


  • 2.  RE: webMethods API Gateway Q&A - Upgrading API Gateway cluster fails at migrate.sh step

    Posted 10/10/23 04:40 AM

    There are two steps that will help resolve this issue.

    The following must be defined in the elasticsearch.yml on ALL the target cluster elasticsearch nodes.

    reindex.remote.whitelist: <source>:<port>

    The “default” Integration Server instance names were not used in the source or target nodes. The migrate command was modified to use the IS instance names.
    Example:

    ./migrate.sh datastore -dstoreSrc /var/tmp/config.properties -reindex -indicesType core  -instanceName <source instance name> -newInstanceName <target instance name> 
    

    #webMethods
    #Tuesday-troubleshooting
    #API-Management
    #API-Gateway