FileHold Portal Integration
Details / Setup Instructions
NOTE: When configured, the Quick Portal Integration
will essentially allow users to logon to the FileHold Web Client via 2
separate URLs.
When the FileHold web client is opened from the default …/WebClient
URL, it displays the regular FileHold login page allowing users to logon
with their username and password. Once authenticated the standard FileHold
header pane will appear along with the standard Tree, Body and Footer
panes. If user access FileHold from the …/WebClientPortal URL, the
custom header pane will appear and the user will be automatically logged
on according to the settings described below and displays a custom header
control.
The following settings will allow you to adjust which guest
user account credentials will be automatically used when logging on from
the WebClientPortal URL. These settings are adjusted in the the Web.config
file located in the webclient folder on the FileHold
application server. If installed using the default settings the webclient
folder is located at C:\Inetpub\wwwroot\FH\FileHold\WebClient
on the fileHold Application server. Locate and edit the following entries
in the appSettings group of the Web.config file:
- PortalLogin - Name of the guest account which will
be used when opening the web client from the WebClientPortal URL.
- PortalPassword - the Password
associated with the guest account
The following settings allow you to specify which pane
will be used in place of the default FileHold Header pane when logging
on from the WebClientPortal URL. These settings are adjusted in the the
Web.config file located in the webclient
folder on the FileHold application server. If installed using the default
settings the webclient folder is located at C:\Inetpub\wwwroot\FH\FileHold\WebClient
on the fileHold Application server. Locate and edit the following entries
in the appSettings group of the Web.config file
- PortalHeaderPath - Path to the
control which will be used instead of the standard FileHold header.
The path is relative to the WebClient directory.
- PortalHeaderClass - Name of the
class to be used as the header. Only needed if PortalHeaderPath is a
.dll file.
The header control can be one of the following:
- A plain .html file - The content of this file will
be inserted verbatim into the page header
- An .ascx file (with a code-behind .ascx.cs file)
- The ASP.NET control will be inserted into the page header
- A compiled .dll file - The control will be loaded
from the given assembly and inserted into the page header.
Note: An .ascx control cannot be used in FileHold '08.
The following section contains instructions for converting an .ascx control
into a .dll file. A sample .html file, zipped .ascx control and compiled
.dll file is included in the Custom subdirectory of the WebClient.
The following steps are required to convert an .ascx control
into a .dll file which can be used as custom header in FileHold '08:
- Open Visual Studio .NET 2005 and create a new Web Site project. Select
the Empty Web Site template.
- Add the .ascx file and the corresponding code-behind .ascx.cs file
to the project.
- Select Build -> Publish Web Site. Uncheck the ‘Allow this
pre compiled site to be up datable’ option and check the ‘Use
fixed naming and single page assemblies’.
- Copy the generated .dll file from the ‘bin’ directory
of the target location into the Custom directory of WebClient. Its name
will look like ‘App_Web_customheaderpanel.ascx.cdcab7d2.dll’.
If necessary, also copy other.dll files that the control depends on.
- Enter the path to the .dll (relative to the WebClient directory)
in the web.config file.
- Enter the name of the class generated by ASP.NET. For an .ascx file
named ‘CustomHeaderPanel.ascx’, the class name will be ‘ASP.customheaderpanel_ascx’
(note that the name of the class must be lowercase).
|
