IBM App Connect Enterprise, Version 11.0.0.2 Operating Systems: Windows, Linux


Configuring a connection to IBM Cloud Product Insights through an HTTP proxy server

IBM® App Connect Enterprise provides a facility to connect to the IBM Cloud Product Insights service through an HTTP proxy server.

Before you begin

About this task

Optionally, you can configure your integration servers to connect to Product Insights through an HTTP proxy server, by setting the httpProxy parameter on the mqsichangebluemixreporting command. If the HTTP proxy requires authentication through a user name and password, you can use the mqsisetdbparms command to provide these credentials through the httpproxy:: resource name.

If you would prefer to connect to Product Insights through the Product Insights gateway, see Configuring a connection to IBM Cloud Product Insights through a gateway. For information about connecting directly to the Product Insights service without routing through a proxy or gateway, see Reporting startup and usage information to IBM Cloud Product Insights.

For more information about Product Insights, see IBM Cloud Product Insights overview.

Procedure

Follow these steps to enable your IBM App Connect Enterprise integration server to connect to the Product Insights service through an HTTP proxy server:

  1. Configure your integration server to use the HTTP proxy server, by specifying the -y httpProxy parameter on the mqsichangebluemixreporting command. For example, the following command sets the startup and usage reporting service for an integration server to active, and specifies that the startup and usage information will be sent via the proxy server that is specified by the -y parameter (https://mygateway.co.uk):
    mqsichangebluemixreporting -w c:\workdir\ACEServ1 -c active -j https://hybridconnect-api.ng.bluemix.net
    -k 9ec5g5c2-5cm1-3287-2bxd-3c71fc22d467 -y https://mygateway.co.uk
    You can remove the setting for a previously specified proxy by setting the -y parameter to "". For example:
    mqsichangebluemixreporting -w c:\workdir\ACEServ1 -c active -j https://hybridconnect-api.ng.bluemix.net
    -k 9ec5g5c2-5cm1-3287-2bxd-3c71fc22d467 -y ""
  2. If the HTTP proxy server requires authentication through a user name and password, use the mqsisetdbparms command to specify the credentials on the httpproxy:: resource name.

    You can set the resource name to apply to either an HTTP proxy with a specified host name, in the form httpproxy::proxy_hostname, or as a default for any HTTP proxy that does not have a matching httpproxy::proxy_hostname setting, by specifying httpproxy::HTTPPROXY.

    For example, use the following command to associate a user name and password with a connection to a specified HTTP proxy server (in this example, https://mygateway.co.uk):
    mqsisetdbparms -w c:\workdir\ACEServ1 -n httpproxy::https://mygateway.co.uk -u myUserID -p myPassword
    Alternatively, use the following command to specify the credentials to be used as a default, for connecting to any HTTP proxy server that does not have a matching httpproxy::proxy_hostname setting:
    mqsisetdbparms -w c:\workdir\ACEServ1 -n httpproxy::HTTPPROXY -u myProxyUsername -p myProxyPassword

    For more information, see mqsisetdbparms command.


bz91200_.htm | Last updated 2018-11-02 14:46:39