| AJS 4.x
Manual | Note! This Manual is for the "Windows authentication" version, which is designed to work with existing Windows server or Active Directory accounts and Windows authentication. If you want to create accounts by yourself and store their credentials in your own HTTP Commander XML database, you need to download the "Forms authentication" version! This Manual is for the Windows authentication version only! | Web file manager Free Installation assistance Manual Home page

Integration with Outlook Web App and Sharepoint 2010

HTTP Commander can be integrated to existing SharePoint portal or Outlook Web App interface. This means that users of SharePoint/OWA will see link to start HTTP Commander. HTTP Commander shown in the same browser window there SharePoint/OWA loaded, also it don't requires authentication if user authenticated while logon to SharePoint/OWA.

- Integration with Outlook Web App (OWA) in MS Exchange 2010
- Integration with Sharepoint 2010

## Integration with Outlook Web App (OWA) in MS Exchange 2010

For integration HTTP Commander with OWA you should have Microsoft Exchange Server 2010 (and also with SP1, SP2 or SP3) installed with enabled Outlook Web Access feature (see more info about its installation at Microsoft website).
Below you will find required steps to make integration:
Note! All necessary the files are in this archive.

- Install HTTP Commander with Windows Authentication on IIS 7 on your Exchange server.
- Add the HttpCommanderAuthModule module in IIS 7 to enable single sign on at OWA and HTTP Commander. This will allow users to click on the HTTP Commander button within OWA 2010 and not be prompted for authentication again.
  - Copy the module\HttpCommanderAuthModule.dll to the OWA bin folder %EXCHANGEINSTALLPATH%ClientAccess\Owa\Bin, where %EXCHANGEINSTALLPATH% - path to installed Exchange server (default location: C:\Program Files\Microsoft\Exchange Server\V14\).
  - Open IIS Manager and navigate to the OWA site. In Features View double-click Modules. On the Modules page, in the Actions pane, click Add Managed Module. In the Add Managed Module dialog box, in the Name box, type a name for the managed module, e.g. HttpCommanderAuthModule. In the Type box, enter exactly the following: HttpCommander.HttpCommanderAuthModule. Click OK. (Note. If you see warning as on the 2nd screenshot click "Yes")
    Screenshots

    Or you can add in the file %EXCHANGEINSTALLPATH%ClientAccess\Owa\web.config in the section system.webServer/modules a line
    <add name="HttpCommanderAuthModule" type="HttpCommander.HttpCommanderAuthModule" />.
    Screenshot

- Copy all files from images folder (clear.gif, HttpCommanderLarge.png, HttpCommanderSmall.png, loadingLarge.gif, loadingSmall.gif)
  to folder %EXCHANGEINSTALLPATH%ClientAccess\Owa\forms.
- Now it is necessary to change some javascript OWA files.
  Note. These files are stored in the %EXCHANGEINSTALLPATH%ClientAccess\Owa\Current\scripts\ (in subfolders basic and premium), and also can be duplicated in folders with Exchange server versions (for example ClientAccess\Owa\14.0.639.21\scripts or ClientAccess\Owa\14.3.123.3\scripts) if it is exists. It is necessary to change each copy of required files. Further in the instruction the folder(s) with javascript files is named as %OWASCRIPTSPATH%. Thus if any folder with the version exists, javascript files from the folder with the greatest version are actually used therefore enough to change files only in such folder.
  - In files scripts\HCOwaBasicIntegration.js and scripts\HCOwaPremiumIntegration.js find a line
    var httpCommanderRelativeUrl = '/HTCOMNET/'
    and change '/HTCOMNET/' to your relative path of HTTP Commander site if you used a path not default (/HTCOMNET).
    Also in the scripts\HCOwaPremiumIntegration.js file you can set HTML description for HTTP Commander which will be visible at the left above.
    For this purpose find the line:
    var httpCommanderDescription ='';
    and set the value necessary to you. For example:
    var httpCommanderDescription = '<div>HTTP Commander description</div>';
    Screenshot

  - Add in the end of file %OWASCRIPTSPATH%\basic\cmn.js contents of file scripts\HCOwaBasicIntegration.js.
  - In each of files addrbook.js, ctsvw.js and msglst.js (in the folder %OWASCRIPTSPATH%\basic) find a substring:
    window.onload=function(){
    and insert the line:
    /* Begin include HttpCommander unit3 */try{HttpCommander.Owa.Basic.insert()}catch(e){/*alert(e)*/};/* End include HttpCommander unit3 */
    right after an opening curly bracket (this line also can be copied from the file scripts\HCOwaIntegration.js).
    Screenshot

  - In the end of file %OWASCRIPTSPATH%\basic\cldly.js add a line:
    window.onload=function(){/* Begin include HttpCommander unit3 */try{HttpCommander.Owa.Basic.insert()}catch(e){/*alert(e)*/}/* End include HttpCommander unit3 */}
  - In each of files cntedt.js, fldmgt.js, itmmv.js, msgedt.js, msgrd.js, mtgrd.js, opt.js, wrhead.js (in the folder %OWASCRIPTSPATH%\basic) find a substring:
    window.onload=
    In each of these files after this substring some function name is specified. Find definition of this function in the current file and at the beginning of definition right after an opening curly bracket add a line:
    /* Begin include HttpCommander unit3 */try{HttpCommander.Owa.Basic.insert()}catch(e){/*alert(e)*/};/* End include HttpCommander unit3 */
    Screenshots

  - In the beginning of file %OWASCRIPTSPATH%\premium\uglobal.js add file scripts\HCOwaPremiumIntegration.js contents.
    In the same file (uglobal.js) find substring:
    checkScripts()}
    and between 'checkScripts()' and '}' insert a line:
    /* Begin include HttpCommander unit4 */;try{HttpCommander.Owa.Premium.insert()}catch(e){/*alert(e)*/}/* End include HttpCommander unit4 */
    Screenshot

  - In each of files startpage.js and unav.js (if exists) (in folder %OWASCRIPTSPATH%\premium\) find substring:
    positionMailboxQuotaBar()}function clearNwMB(){
    and paste between 'positionMailboxQuotaBar()' and '}function clearNwMB(){' line:
    /* Begin include HttpCommander unit5 */;try{HttpCommander.Owa.Premium.hide(arguments[0])}catch(e){/*alert(e)*/}/* End include HttpCommander unit5 */
    Screenshot

- Restart IIS on Exchange server.

Screenshots

## Integration with Sharepoint 2010

For integration HTTP Commander with Sharepoint you should have Microsoft Sharepoint Server 2010 installed (see more info about its installation ).

- Install HTTP Commander for Windows Authentication on your Sharepoint server. HTTP Commander must be installed under the SharePoint Website.
  Screenshot

- Add in web.config file of HTTP Commander in system.web section a line:
  <trust level="Full" originUrl="" />
  Screenshot

- In IIS7 for SharePoint Website and HTTP Commander site configure to use Basic Authentication. Disable other authentications, then, enable ASP.NET Impersonation and Basic Authentication. Restart SharePoint – 80 website.
  Screenshot

- Log on to your SharePoint Portal http://<your_sharepoint_server_name> as Administrator . Click Lists. Click Links. Under the links summary – Add new link. Create a link to HTTP Commander http://<your_sharepoint_server_name>/hctest Test the link. You should not be prompted for a username and password a second time. Screenshot

- Log on to SharePoint 2010 as Administrator. Add Page Viewer Web Part.
  - Choose Home Page, and click Edit Page.
    Screenshots

  - Click Web Part. Click Insert Tab. Select Media and Content in Categories, then, select Page Viewer in Web parts. Click Add button.
    Screenshot

  - Click open the tool panel.
    Screenshot

  - Enter HTTP Commander URL. Then, expand Appearance. Enter the title in Title textbox. Enter the Height and width, click on Apply. You will see HTTP Commander in the web part. Adjust Height and Width to meets your needs. Click OK.
    Screenshot

  - Click Save & Close to exit editing page.
    Screenshot

Screenshot