Configure an HTTP proxy for a discovery connector node by using an HTTP Proxy policy.
About this task
Discovery connectors deployed to an on-premises system might require an HTTP proxy to connect to
public endpoints. You can configure the following discovery connector nodes to use an HTTP proxy for
such connections:
Procedure
Configure an HTTP proxy for a discovery connector node by completing the following
steps:
- Create a credential to be used for authenticating the connection, by using the mqsicredentials command. The credential must have a type of
httpproxy. For example:
mqsicredentials --create --ext-vault-dir c:\temp\credential -ext-vault-key myvaultkey --credential-type httpproxy
--credential-name httpseccred --username proxyUser --password proxyPassword
- Create an HTTP Proxy policy and set the HTTP
Proxy URL property to specify the full URL of the HTTP proxy server. Use the
Credential name property to specify the name of the credential that will be
used for the connection, with a type of
httpproxy.
- Configure the discovery connector node to use the HTTP Proxy policy, by editing the
policy that contains the connection details of the node (such as the Microsoft Azure Blob Storage
policy specified on a Microsoft Azure Blob Storage Request node),
and set the Proxy name property to the name of the HTTP Proxy policy that you
created in step 2,
in the format
{policyProjectName}:policyName.
- Optional: You can also specify an HTTP Proxy policy during connector
discovery, by using the Connector Discovery wizard. In this case, you specify the name of the HTTP
Proxy policy in the Proxy name property, and the HTTP proxy is used to create
the connection. For example:
- Deploy the policies with the message flow.