Search Engine Sneak Preview: X1 Technologies' X1 Enterprise Edition 2.0
This search engine lets admins and users in Windows environments find missing information quickly, no matter where it was misplaced.
![](https://eu-images.contentstack.com/v3/assets/blt69509c9116440be8/bltc0182b2356ae8eed/64b83949410a1b4c0bd7459b/IW_generic_image.png?width=1280&auto=webp&quality=95&format=jpg&disable=upscale)
Lose something? Where did you see it last--on your desktop, in a network share or in your e-mail inbox? X1 Technologies' Enterprise Edition 2.0 can index and search data on the desktop, in message stores or remote file shares, to find missing information quickly.
X1 Enterprise Edition 2.0 has two components: X1 Enterprise Server, for indexing and administering searches, and X1 Enterprise Client, for end-user searches. Within Enterprise Server, Server Manager provides a range of management functions. Deployment Manager, meanwhile, is used for configuring and exporting Enterprise Client.
Windows of Opportunity
I tested Enterprise Server in our Syracuse University Real-World Labs® on a Windows 2003 Server outfitted with dual 1.4-GHz PIII processors, 1,024 MB of RAM and 17 GB of disk space. I could have used Windows 2000 or XP, if it had IIS 5 or 6 available and sufficient disk space to hold an index of the content to be searched. X1 recommends enough space to hold 20 percent of the total data searched.
I made more than 1 GB of local and network information searchable to end users within minutes. Using Active Directory Domain credentials, I locked down the browser search interface so only authorized users could see certain search results. Then I extended X1's search functions to desktops by configuring and exporting X1's Enterprise Client 2.0 (Build 1852dj-bi), a Win32 application. The procedure took less than an hour.
By default, Enterprise Server runs as a Windows service using a local system account. The server acts as a central scanning or indexing engine for Windows shares and interacts with IIS to authenticate and let end users search data stores from a Web browser or the client. The browser allows views of preconfigured network searches only; client users have a wider range of desktop and network search options.
I could have used a local system account to run the service and index local data stores, but I wanted to search all the Windows shares in my Active Directory Domain. I created a Domain user ("X1 user") that would run Enterprise Server as a Windows service, gave "X1 user" access to remote directories targeted for search and enabled Windows shares on those directories.
Good |