In some cases Service Virtualization Designer communicates with external services using the HTTP protocol. The first case is the communication with Service Virtualization Server, where the service is the server management API. The second case is the import of the a real service WSDL. In some situations, the Designer’s HTTP communication must be forwarded through an external HTTP Proxy. In that situation, the HTTP Proxy settings must be placed in the Designer’s configuration file.

Note: The setting of HTTP Proxy for agents is not done in the Designer configuration file. For details, see Forward HTTP agent communication through an HTTP proxy.

In order to use an external HTTP Proxy for the Designer HTTP communication with a server and the import of a WSDL from real services, the Designer configuration file must be modified. This file is located at %[INSTALLLOCATION]%\Designer\bin\VirtualServiceDesigner.exe.config.

In the configuration file the element <defaultProxy> holds the HTTP Proxy configuration. This element is located in the document in elements <configuration><system.net>. By default, HTTP Proxy is disabled by <defaultProxy enabled="false"/>.

The Designer can be configured to use the system HTTP Proxy or to use a specific HTTP Proxy. Detailed documentation can be found at http://msdn.microsoft.com/library/kd3cf2ex.aspx. The Designer must be restarted in order to apply the changes in the configuration file.

If using the system HTTP Proxy, ensure that the HTTP Proxy is configured in the system. The settings are available in Windows Internet Explorer® menu Internet Properties > Connections > LAN settings > Proxy server. The Designer must be configured to use the same proxy in the configuration file in the element <defaultProxy> like this:

<configuration>

   <system.net>

      <defaultProxy enabled="true">

        <proxy usesystemdefault="true"/>

      </defaultProxy>

   </system.net>

</configuration>

If using a specific HTTP Proxy other than the system one, follow this example of Designer configuration:

<configuration>

   <system.net>

      <defaultProxy enabled="true">

        <proxy proxyaddress="http://foo.com:8080"/>

      </defaultProxy>

   </system.net>

</configuration>

If the Designer is configured to use HTTP Proxy with authentication, some additional modifications may be required in the Designer configuration file. This will allow the supplying of credentials for the HTTP Proxy. These modifications are required in the case of HTTP communication with the server management API. In the case of WSDL imports, these modifications are only optional as the Designer will prompt the user for credentials if needed.

In order to set credentials for authenticated HTTP Proxy in the Designer, this section must be enabled in the configuration file VirtualServiceDesigner.exe.config:

<configuration>

   <system.net>

      <defaultProxy enabled="true" useDefaultCredentials="false">

        <module type = "HP.SOAQ.ServiceVirtualization.ServerManagementClient.Remote.AuthenticatedProxy, HP.SV.ServerManagementClient" />

      </defaultProxy>

   </system.net>

</configuration>

The credentials for the authenticated HTTP Proxy are set in application keys section. Example of credential settings follows:

<configuration>

   <appSettings>

      <add key="proxyUserName" value="user1" />

      <add key="proxyPassword" value="pass1" />

      <add key="proxyAddress" value="http://foo.com:8080" />

   </appSettings>

</configuration>

Where keys are defined as:

Once the credentials and the proxy settings are configured as described above then the Designer will use them both for HTTP communication with the server management API and WSDL imports from real services.