eRoom Recycle Bin not accessible

If your eroom Recycle Bin is not functioning properly, Go the Site Administration page via MMC console. Login to the eroom and empty the recycle bin. Come back and check from outside if it helps accessing the recycle bin.

These issues appear sometimes due to unknown reasons like corrupt files, high volume of data in the recycle bin.

Can i retrieve folder structure from eroom back end?

Indexing Services in eRoom

The indexing services that are installed in an eroom Advanced installation are  as below. There will be another service called Indexing service which is a wondows service and is not related to eroo indexing. From the below three services, Hummingbird connector service can be run and other two can be kept disabled.

-1- Hummingbird Connector Service

-2- Hummingbird Connector Manager

-3- Hummingbird STR service

Merging Two eRooms

Is there any tool that will merge the contents of the two erooms?

Any comments are welcome on this topic.

eRoom Capacity Planning

eRoom Capacity planning determination depends on the usage and the load on the server. In this direction,the number of users play a vital role in planning the capacity.The few factors that determine the capacity in terms of servers are as below.This is just a guideline to start with. The factors that determine planning your capacity is hardware performance, user base growth and performance.

-1- No. of Registered (with login credentials) users (Say, R Nos)

-2- No. of concurrent users ( Accessing the server at a time say C%)

-3- Average no. of Daily users (Say D%)

Required concurrent users (C)= R * C %* D%

Now, No. of eRoom servers (N)= C \ Users supported per server

No. of Database Servers = N/3

No. of  Index Servers = N/3

No. of File Servers = No. of eRooms * estimated average size of the eroom ( This estimation is a rough estimation and just to start with initially. Further more file servers can be added as per the growth)

The above data is taken from EMC guide for scalability and capacity planning.

Any concerns and questions,please write me at bharadwaj.choudhury@gmail.com

What is Squid Proxy and it’s significance in eroom set up?

Squid is a proxy server and web cache daemon. It has a wide variety of uses, from speeding up a web server by caching repeated requests, to caching web, DNS and other computer network lookups for a group of people sharing network resources, to aiding security by filtering traffic.

However, it also can introduce significant privacy concerns as it can log a lot of data including URLs requested, the exact date and time, the name and version of the requester’s web browser and operating system, and the referer.

So, it is upto the architect to decide whether they should go ahead with this implementation or not.

Please feel free to comment or email me at bharadwaj.choudhury@gmail.com for any feedback for improvement or for any information accuracy related issues.

Regards

BBC

eRoom Installation Components

Different Components for a Fresh eroom installation (Windows) consists of the following.

-1- eRoom Server Software/Index Server/Database Server

-2- Security Agents like Siteminder

-3- Physical or Virtual VMWare servers

-4- Anti Virus Software Component

-5- Back up Component

-6- Network Support Component

-7-  Storage Component

These are a few basic components that can be cosidered while setting up a new eroom environment. Any question or feedback on the topic, please write to bharadwaj.choudhury@gmail.com

Regards….BBC

Monitoring the Indexing Process

After rebuilding of index for a facility,the following things can be monitored.
-1- eRNotifier and ftrmsrv process
-2- only, one eroom facility will be indexed at a time.
-3- Log file will contain lines as 1:Search Server:indexing…\Facility\Folder_1243..
-4- In case, eTrace is set, the eTrace log will contain ERNotifier messages depending upon the settings in etrace.
-5-Time stamp for the ~Full text directory,will be current for the files with the specific facility ID which is being rebuilt.
-6-Indexing process will catalog the contents thus creating [FacilityID].cat files.
-7- The .dup files for the facility should disappear and and should be replaced by a .dct file after the validation is over.Till the validation is ON, the time stamp on the index and the log file will not be updated to the current one.
-8- Once, validation is over, the log file will contain information like ending indexing at….
-9- The event viewer will give a message that index has been build for this facility.
-10- Any failures, will be recorded in FailedOperations.csv file
-11- New facility will be started to be rebuilt.

Fixing Indexing issues in eRoom

Que: Explain briefly the steps to fix indexing issues in eRoom.

Ans:Basically there are two steps in fixing indexing issues in eroom. One, Identify the Facility which is showing problem.Two, Rebuild the index for the identified Facility.Let’s discuss each of the steps in detail.

One, Identifying problematic facility:

Review the ~FullText Directory for the file types like .rup,.sup or .dup. If these files are older than 24 hours, then there are chances that index engine was unable to process those facilities.The Facility name can be determined from the UniqueId associated with the file.The UniqueId can be collected from the eRoom_eRoomSite database. You will find different types of files associated with this ID.However, we are of concern for ‘i’ files and ‘f’ files ( ‘i’ files are incremental index files and ‘f’ files are the permanent index files, associated with that facility.

Two, rebuilding the index:

Once, you identify the specific problematic facility, you need to rebuild the index for that facility.Follow the procedure as below.

-1- Stop the eRoom Scheduler service -2- Clean up (take back up) all permanent index files( ‘F’ files) from \eRoom Data\~Full Text directory -3- Clean up (take back up) all incremental index files( ‘I’ files) from \eRoom Data\~Full Text directory -4- Go to eRoom Site Settings -> Scheduler and make sure that option for “Index New Files” is checked. -5- Start the “eRoom Scheduler service” -6- Rebuild the index by going to Facility Settings Page and then the indexing section. -7- Monitor the Re-indexing.

Once, reindexing is over, it will write an event to the event viewer saying that “The Fulltext index for the facility has been rebuilt. Elapsed Time:xxxxx minutes.Number of Files processed:xxxx“

eRoom Architecture

Let’s discuss the eroom Architecture in a simple and precise way.

3 tier Architecture of eRoom