Where are my application files and data stored?

Introduction

The following article will offer insight on the different locations used by our software to store application-level files/data. Files are stored on the Intranet server whereas data is stored in your SQL database.

 

Identifying the Application and Relevant IDs

In certain circumstances you may wish, or be asked by support, to identify where a certain application stores its data. To do so, you will need to identify the original name of the application as well as the appropriate IDs.

Browser URL: 

Your original application name can be identified in the browser URL of the site.  Open the application in question (within the site) and check the following area of your browser:

appnames1.png


Several useful parameters are present in the link:

Original Application Name: The original name of the application is the entry found to the right of the ‘frpath=’ entry. In this case it is documents.

Content IDs: Each application, category and item on the site has its own unique IDs. In this link the relevant IDs are MenuID=6, CategoryID=7, ID=51

Other URL Parameters are also passed in this fashion but are not discussed in this document.
 
Identifying your Application (original vs clone):

To identify the location of your content within the database, you will need to know both the Original Application Name and the MenuID.

MenuID’s for applications fall into two groups.

MenuID = 1- 99: These are the original applications. For example, the MenuID of the original documents application is 6.

MenuID > 5000: Cloned Applications. All copies of the original applications have MenuID’s greater than 5000. When looking for the application tables of a cloned application you will note that they have the MenuID appended to the table name.

 

Locate Your Application's Tables

Open your Intranet Connections database. Applications tables are labeled according to the original application name. In this example, we will look at the associated tables for two links:

http://intranet/index.cfm?frpath=documents/detail_view.cfm?MenuID=6andID=51andCategoryID=7

Tables:

  • Documents
  • DocumentsApproval
  • DocumentCategories
  • DocumentSubCategories
  • DocumentVersions
  • DocumentFields
  • DocumentOrder

http://intranet/index.cfm?frpath=documents/detail_view.cfm?MenuID=5123andID=254andCategoryID=2

Tables:

  • Documents5123
  • DocumentsApproval5123
  • DocumentCategories5123
  • DocumentSubCategories5123
  • DocumentVersions5123
  • DocumentFields5123
  • DocumentOrder5123

Note that when dealing with a cloned application, each table has the cloned MenuID appended to its name.

 

Locate an Individual Record

Item records are stored in the application’s main table. The table shares its name with the original application name. In the example of the link below:

http://intranet/index.cfm?frpath=documents/detail_view.cfm?MenuID=5123andID=254andCategoryID=2

This particular record would be stored in the Documents5123 table. We could open the table to view the application’s entire recordset, or we could query this table for records where ID = 254 and CategoryID = 2 to return the unique record.

 

Locate Your Application’s Files
Files are also stored by menuID. To locate your files you will again need your Original Application Name and your MenuID. Files are stored on the web server. You can identify the location of your site files on the server by going to Admin à Site Settings and checking the Server Drive & Path Location value.

appnames3.png

Once you have identified the location of the root intranet folder, we can confirm the location of individual application containers. Using the same two links as an example:

http://intranet/index.cfm?frpath=documents/detail_view.cfm?MenuID=6&ID=51&CategoryID=7

Uploaded files Location:       ..\intranet\documents\files

http://intranet/index.cfm?frpath=documents/detail_view.cfm?MenuID=5123&ID=254&CategoryID=2

Uploaded files Location:       ..\intranet\documents\files5123

Have more questions? Submit a request

0 Comments

Article is closed for comments.