Specifying a non-default TCP port for the Web Access application

Note that you cannot include a TCP port number in the URL that you specify with the -secondary parameter of the fs_dhsm -connection command. If you attempt to include a TCP port number, the fs_dhsm -connection command fails with a message similar to the following, and the archiving and recall of files on the Celerra will fail:

Error: The host name in the secondary url evserver.demo.local:85 is either missing or formatted incorrectly.

If you have configured the Web Access application to use a TCP port other than default port (port 80), you can use the following workaround to use a non-default port with the Celerra.

To specify a non-default TCP port for the Web Access application

  1. Create an IIS Web site that uses the default TCP port, port 80.

  2. In the new Web site, create a virtual directory that is named EnterpriseVault. Set a redirection URL for this virtual directory to the original EnterpriseVault virtual directory on the non-default port.

  3. Configure the Web Access application to use default TCP port 80 on the General tab of the Enterprise Vault Site properties.

  4. Use the -httpPort parameter with the fs_dhsm - connection command to specify the non-default port, as follows:

    fs_dhsm -connection fs_name -create -type http
-secondary ev_url -user user -password user_password -cgi n 
-httpPort port_number

    For example:

    fs_dhsm -connection fsa_fs -create -type http 
-secondary http://EVServer.demo.local/EnterpriseVault 
-user vaultadmin@demo.local -password p4ssw0rd -cgi n
-httpPort 85