Configure a Proxy for Resource Providers Outside the Internal Network

If you are using a network proxy server to communicate with a resource provider outside of the internal network (the resource provider's service access point is located outside of the internal network), configure CSA and Operations Orchestration to use this proxy server.

If you are using a network proxy server to communicate with a resource provider outside of the internal network, proxy configuration is required in the following situations:

• CSA - Validating the accessibility of a resource provider's URL. When a resource provider is created or modified, accessibility of the provider URL is validated with an HTTP or HTTPS GET call.
• Operations Orchestration - Contacting a resource provider. When an Operations Orchestration workflow provisioning step is executed, Operations Orchestration attempts to contact the resource provider.

If you do not configure the proxy server, you may see a Provider Validation Failed message when creating or updating a resource provider whose service access point is located outside of the internal network. Or, provisioning of a design fails when Operations Orchestration is unable to communicate with a resource provider that is located outside of the internal network.

To configure the proxy server for CSA and Operations Orchestration, do the following:

1. On the system running CSA, open the following file in a text editor:

   Linux: PERSISTENT_VOLUME_PATH/jboss‑as/bin/standalone.conf

2. After the last uncommented line that sets the JAVA_OPTS property, add the following lines:

   • Linux:

     # HTTP Proxy Settings
JAVA_OPTS= "$JAVA_OPTS -Dhttp.proxyHost=<proxy.company.com>
-Dhttp.proxyPort=<proxy_port>"

# HTTPS Proxy Settings
JAVA_OPTS= "$JAVA_OPTS -Dhttps.proxyHost=<proxy.company.com>
-Dhttps.proxyPort=<proxy_port>"

# HTTP/HTTPS hosts not handled by the proxy
JAVA_OPTS= "$JAVA_OPTS -Dhttp.nonProxyHosts=mycsaserver\|localhost\|127.*\|10.* "

     where <proxy.company.com> is the fully-qualified domain name of the proxy server,
     <proxy_port> is the port used to communicate with the proxy server, and \| is the separator used when defining more than one non-proxy host.

3. Save and exit the file.

4. Restart the CSA pod.

   See Restart or redeploy individual deployments for instructions.

5. If you have integrated with Operations Orchestration version 9.07, do the following:

   1. Log in to Operations Orchestration Studio.
   2. Open the Configuration folder.
   3. Right-click the System Properties folder and select New.
   4. In the dialog, enter CSA_Proxy_Host and click OK.
   5. Set the Property Value to the fully-qualified domain name of the proxy server and click OK.
   6. Right-click the System Properties folder and select New.
   7. In the dialog, enter CSA_Proxy_Port and click OK.
   8. Set the Property Value to the port used to communicate with the proxy server and click OK.

6. If you have integrated with Operations Orchestration version 10.50, do the following:

   1. Log in to Operations Orchestration Central.
   2. Click the Content Management button.
   3. Select Configuration Items > System Properties.
   4. Click the Add icon.

   5. Enter the following information if it is not already configured:

      Field	Description
      Name	CSA_Proxy_Host
      Override Value	The fully-qualified domain name of the proxy server.
      Name	CSA_Proxy_Port
      Override Value	The port used to communicate with the proxy server.

   6. Click Save.