App Connect

App Connect

Join this online user 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.


#Applicationintegration
#App Connect
#AppConnect
 View Only

  • 1.  How to change HTTPListener port for Integration server while Node is used

    Posted Wed April 10, 2019 12:53 PM
    I run the mqsichnageproperties command to change the HTTPListener port for the SOAP call for an integration server, the sample script is: 

    mqsichangeproperties  ACELOCAL -o HTTPConnector -e IntServer1 -n explicitlySetPortNumber -v 18000

    And I am getting the error message as shown below: 

    BIP8384E: This command, with the flag or combination of flags 'e', is not yet enabled for use with an integration node.

    Although commands can be used with integration nodes, some flags or combinations of flags will not be enabled until a later fix pack.

    Users of the product in its current form can use this command with other flags or combination of flags, and can perform some actions in the Enterprise Toolkit.


    The command used to work in IIB9/10,  if the flag combination is not yet enabled in ACE, what is the workaround to make it work?  Thanks.

    ------------------------------
    Andy Mao
    ------------------------------


  • 2.  RE: How to change HTTPListener port for Integration server while Node is used

    Posted Wed April 10, 2019 01:11 PM
    Hi Andy,

    The command options have changed in v11. This link should help ... 
    https://www.ibm.com/support/knowledgecenter/en/SSTTDS_11.0.0/com.ibm.etools.mft.doc/bc43700_.htm
    You can also make direct changes to node.conf.yaml file.

    Cheers,
    Ben

    ------------------------------
    Ben Thompson
    IBM UK
    ------------------------------

    Original Message


  • 3.  RE: How to change HTTPListener port for Integration server while Node is used

    Posted Mon April 15, 2019 02:48 AM
    Hi Ben,

    After changing the Server node to Integration wide node , there is some problem while calling the internal messages flows exposed as web services from another flow. Is this known issue or some problem with configuration I might be doing.

    ------------------------------
    Satendra Negi
    ------------------------------

    Original Message


Related Content