FileHold document and record lifecycle software is based on the Microsoft .NET 3.0 framework Service Oriented Architecture (SOA) model. Microsoft provides an ideal technology platform to implement web services and to deliver modern Service Oriented Architecture. This architecture provides tremendous benefits to our customers, our partners and to FileHold's product development and professional services teams in terms of product scalability, flexibility and performance.

The main subsystems of FileHold communicate with each other via secure and fully authenticated web service calls. All FileHold application clients (including the FileHold Web Client, FileHold Desktop Application and FileHold MS Office Add-in) interact with the FileHold Server using the same web services and calls. These very same Web Services make up the FileHold Web Services API for integration of custom clients with the FileHold library. Sample custom integrations include integration of FileHold functionality into other productivity applications, develop connectors to import documents and metadata into FileHold from other applications or the ability to retrieve data and documents from the FileHold Library through a custom Intranet portal.

The SOA architecture provides the ability to deploy web services on different servers for the ultimate in system scalability and performance management.

Available Web Services & Operations

The FileHold application exposes a total of 13 Web Services with the following names. Clicking on the web service will show the names of all the operations associated with the web service along with the web service description. Clicking on any of the operation names will show in detail the operation SOAP calls and parameters required to interact with the operation.

NOTE: To access the location of these on your local FileHold production server replace the server location in the below URL with your internal server name and path.

Subsystem/Component	Web Service Name	View Web Service Details & Operations At
Document Repository	RepositoryController	https://demo.tryfilehold.com/FH/FileHold/DocumentRepository/RepositoryController.asmx
Full Text Search	FullTextSearch	https://demo.tryfilehold.com/FH/FileHold/FullTextSearch/FullTextSearch.asmx
Library Manager	DocumentFinder	https://demo.tryfilehold.com/FH/FileHold/LibraryManager/DocumentFinder.asmx
Library Manager	DocumentManager	https://demo.tryfilehold.com/FH/FileHold/LibraryManager/DocumentManager.asmx
Library Manager	DocumentSchemaManager	https://demo.tryfilehold.com/FH/FileHold/LibraryManager/DocumentSchemaManager.asmx
Library Manager	GlobalSettingsManager	https://demo.tryfilehold.com/FH/FileHold/LibraryManager/GlobalSettingsManager.asmx
Library Manager	LibraryStructureManager	https://demo.tryfilehold.com/FH/FileHold/LibraryManager/LibraryStructureManager.asmx
Library Manager	UserPreferences	https://demo.tryfilehold.com/FH/FileHold/LibraryManager/UserPreferences.asmx
Library Manager	VirtualFolderManager	https://demo.tryfilehold.com/FH/FileHold/LibraryManager/VirtualFolderManager.asmx
Library Manager	WorkflowManager	https://demo.tryfilehold.com/FH/FileHold/LibraryManager/WorkflowManager.asmx
User Role Manager	UserGroupManager	https://demo.tryfilehold.com/FH/FileHold/UserRoleManager/UserGroupManager.asmx
User Role Manager	SessionManager	https://demo.tryfilehold.com/FH/FileHold/UserRoleManager/SessionManager.asmx
User Role Manager	LicenseManager	https://demo.tryfilehold.com/FH/FileHold/UserRoleManager/LicenseManager.asmx

Web Service Error Logging

FileHold adds a node to the Windows 2003 Event Viewer called FileHold that is useful for troubleshooting error conditions when integrating with the FileHold library using the FileHold Web Services API. The FileHold log file is created upon installation of FileHold onto a Windows 2003 Server. Upon installation all logging is enabled to the FileHold node. The FileHold event log is used for logging most application error messages. In addition, some error messages are logged to standard Windows logs (Application, System, Security).