Configuring proxy settings

Edit online

Traditional:
If you use a proxy server for internet connections, you can configure IBM® Business Automation Workflow so that it uses the appropriate server and protocol for internet connections, such as when connecting to Blueworks Live.

About this task

The following table shows proxy setting properties for IBM Business Automation Workflow.

Important: If your proxy settings are identical for HTTP and HTTPS, do not use the protocol attribute. <proxy-settings> sections without the protocol attribute take precedence over any <proxy-settings> sections with a protocol attribute.

Table 1. Proxy settings
Setting	Required or Optional	Description
`host`	Required	IP address or host name of the proxy server.
`port`	Required	Port number that is used by the proxy server for client connections.
`user-name`	Optional	User name used by the proxy server for client connections.
`password`	Optional	Password used by the proxy server for client connections.
`password-encrypted`	Optional	Encryption status for the password. The value is `true` if the password is encrypted; otherwise, the value is `false`. For more information, see the topic Enabling encrypted passwords in proxy settings.
`excluded-hosts`	Optional	IP addresses or host names of any hosts for which proxy settings should not be applied. `localhost` , `127.0.0.1` , and `0:0:0:0:0:0:0:1` are excluded by default. Use a comma-separated string of IP addresses to exclude additional hosts.
`proxy-auth-alias`	Optional	Name of a Java Authentication and Authorization Service (JAAS) authentication alias containing the user and password information.

The following is an example of a XML code snippet that uses an authentication alias to make configuration changes in the 100Custom.xml file. The protocol attribute of proxy-settings is for specifying whether you are using HTTP or HTTPS. If your proxy settings are identical for HTTP and HTTPS, do not use the protocol attribute. It is recommended to store your credentials using an authentication alias, rather than storing your credentials directly in the configuration file.

<server>
    <connection merge="replace">
        <proxy-settings>
            <host>myproxy.com</host>
            <port></port>
            <proxy-auth-alias>ProxyAuthAlias</proxy-auth-alias>
            <excluded-hosts></excluded-hosts>
        </proxy-settings>
    </connection>
</server>

The following is an example of a XML code snippet that can be used to make configurations in the 100Custom.xml file without the use of an authentication alias. In this example, the proxy-settings protocol attribute is used for specifying the different proxy settings for HTTP and HTTPS.

<server>
    <connection merge="replace">
        <proxy-settings protocol="http">
            <host></host>
            <port></port>
            <user-name></user-name>
            <password></password>
            <password-encrypted></password-encrypted>
            <excluded-hosts></excluded-hosts>
        </proxy-settings>
        <proxy-settings protocol="https">
            <host></host>
            <port></port>
            <user-name></user-name>
            <password></password>
            <password-encrypted></password-encrypted>
            <excluded-hosts></excluded-hosts>
        </proxy-settings>
    </connection>
</server>

For information about the 100Custom.xml file's location, and how to create, modify, and deploy it, see The 100Custom.xml file and configuration.