Thursday, 28 February 2013

Inforouter - prevented from opening a MS Office 2010 document

[Inforouter]  When accessing a MS Office document with Office 2010, it is possible you will see the following message and will be prevented from opening the document.

“Access to this web server is disabled by default because it is controlled by basic authentication and does not use Secure Sockets Layer SSL).”

This is an issue with Office and the following MS knowledge base article addresses it.


Inforouter - Storage Requirements

[Inforouter] An example of an Inforouter Storage Scenario;

A Customer wishes to store 100,000 documents with each page being a full page of text. On average each document is 200kb, and 25% of these documents will have a second version.

100,000 x 200kb = 20 Gb - Primary Warehouse Storage
25% x 100,000, x 200kb = 5Gb - additional storage for document versions

Total Warehouse Size = 25Gb

As these documents are catalogued with MS Index Server to provide full text search, an allowance of 150% of the original warehouse size needs to be made for the MS Index Server Catalog;

25Gb x 1.5 = 37.5Gb

Finally there is the Inforouter database, which in this example can be approximated to 300mb

Therefore the total requirement is

25 + 37.5 + 0.3 = 62.8Gb


Inforouter - MS Index Server

[Inforouter] The main search facility within Inforouter is based upon the Custom Property Sets, which contain the meta-data, and are held in the database behind Inforouter. Inforouter also has a secondary search facility, which queries an MS index server catalog of the documents in the Inforouter Warehouse. Whilst Inforouter queries this catalog to provide the full text search functionality, the generation of the catalog is independent of inforouter, and it's creation and contents are the responsibility of MS Index Server. MS Index server can interact with any MS Office document, or any document where an associated ifilter has been loaded. (See other posts on a suitable ifilter for PDF files).

Please Note: It is possible that an MS Index Catalog of an Inforouter warehouse can be 1.5 times the size of the original warehouse. This is in addition to the original warehouse size. (pca)

Friday, 15 February 2013

Set IE to prompt for username and password

[Workflow] When using Internet Explorer in its default settings your Windows credentials will  automatically be used to log you on to the DG Workflow system. This behavior saves a user having to log into a system using credentials which they have already entered when they logged into Windows.

In most cases this is the desired behavior.  But what if you want to log into the DG Workflow system using different credentials from those used to log into Windows?

IE can be configured to prompt a user to enter the username and password which should be used to log into a given system for a given security zone.  Specifically in this case you can set IE to always prompt you for a username and password when accessing the Local intranet zone (the zone within which the DG Workflow system exists).

The following instructions show how to configure IE9 to prompt for a username and password when accessing the DG Workflow system.

  • Open IE
  • Open the Internet Options dialog
  • Click on the Security tab (1)
  • Select the Local intranet zone (2)
  • Click on Custom level... (3)
  • Scroll to the User Authentication section
  • By default Automatic logon only in Intranet zone is selected (4), change this to Prompt for user name and password
  • Click OK, you will be prompted to confirm you want to save the changes
  • Click Yes, the Security Settings dialog will close
  • Click OK to save the changes and close the Internet Options dialog
Internet Options \ Security Settings dialogs

NOTE: - If the address used to access the DG Workflow system contains a period character (.) then IE may evaluate the system to be within the Internet zone and not the Local intranet zone.  In this case the instructions above should be modified appropriately.

Tuesday, 5 February 2013

Inforouter Indexing Custom Properties

[Inforouter] When a Custom Property Set (CPS) is created within Inforouter none of the fields are indexed. This is because Inforouter does not have a method of formulating  the relative importance or frequency of use of any given field with the CPS. However manual indexes can be applied within the Database, you can ask you DBA to do this for you. (PCA)