 |
|
 |
 |
|
We are constantly improving our products. Look below to review an archived list of our accomplishments.
The current build is indicated by bold text - click a different build number to be taken to its associated release notes.
|
X1® Enterprise Edition Server 3.2 (Build 1882ar) (Thursday, March 25, 2008)
X1® Enterprise Edition Server 3.0.1 (Build 1790hf) (Thursday, October 5, 2007)
X1® Enterprise Edition Server 3.0 (Build 1790gw) (Thursday, September 6, 2007)
X1® Enterprise Edition Server 2.6.2 (Build 1776xi) (Wednesday, July 18, 2007)
X1® Enterprise Edition Server 2.6.1 (Build 1776vf) (Tuesday, May 15, 2007)
X1® Enterprise Edition Server 2.6 (Build 1776so) (Friday, December 8, 2006)
X1® Enterprise Edition Server 2.5.4a (Patch Build 1763ia) (Monday, September 11, 2006)
X1® Enterprise Edition Server 2.5.4 (Build 1763hs) (Tuesday, August 15, 2006)
X1® Enterprise Edition Server 2.5.3 (Build 1763gt) (Tuesday, July 18, 2006)
X1® Enterprise Edition Server 2.5.2 (Build 1434fl) (Thursday, April 20, 2006)
X1® Enterprise Edition Server 2.5.1 (Build 1434ca) (Monday, March 28, 2006)
X1® Enterprise Edition Server 2.5 (Build 868pr) (Thursday, February 14, 2006)
X1® Enterprise Edition Server 2.0.1 (Build 2053ce) (Thursday, August 4, 2005)
X1® Enterprise Edition Server 2.0 (Build 2053br) (Monday, June 20, 2005)
|
 |
X1® Enterprise Edition Server v2.5 (Build 868pr)
(Released Thursday, February 14, 2006)
New Features
Best Practices - General
Best Practices to Avoid Known Issues
Troubleshooting
NEW FEATURES
2.5
- Larger Index Size Possible
- Processes can be distributed across multiple machines
- Cluster Manager
- Added support for Mozilla Firefox in the Browser Client
- Performance Monitoring
- Extensibility through an SDK
- New Content Connectors available
BEST PRACTICES - GENERAL
RAM and Disk Drives
For best performance, a minimum of 2 GB of RAM is recommended. The application will run with 1 GB, but performs much better with 2 GB or more of RAM. The startup.properties file defines the maximum amount of memory available to each X1EE component. For best performance, use multiple hard disks. Use one hard disk for OS and swap, one disk for the X1 install, and one or more for indexes.
During install, consider using the fully qualified domain name.
If the short domain name does not match the long domain name (eg: short: “abcdef” and long: “abcd-inc.com”, use the fully qualified domain name in the install wizard. By using such explicit naming, this ensures there is no confusion by the application.
Ensure the directories to be searched are readable by the account the X1 services are running as.
In order for X1EE to search the content in a particular directory, the files in that directory must have their permissions set to allow read access to the account that the X1 services are running as. Generally, files inherit the permissions of the directory, so changing the permissions of the directory is usually sufficient to grant access to all files in that directory. One exception: if an individual file has its permissions set explicitly, this overrides the inheritance from the directory. Remember to check the “Deny” list as well, by clicking the Advanced button on the permissions tab. These permission changes will be visible to the user after the next index of the data.
Create an X1Users group for granting permissions to saved searches.
By default, saved searches do not have any account or group permissions. These must be set explicitly in the Manage Federation Engine screen. For ease of maintenance, grant permission to an X1Users group, rather than adding users individually. Besides being faster than individually assigning permission to each and every user, it allows changing membership in this group without impacting the X1EE application. To create multiple levels of read access to files, create multiple groups (eg: Finance, Engineering, HR, Everyone).
Allow time for replication between multiple Active Directory controllers.
When creating the account that the X1 services will run as, and the X1Users group, note that this occurs on a particular active directory controller for the domain. When there are multiple controllers for a domain, time must be allowed for replication of that information in the other controllers.The Active Directory default replication time is 180 minutes, but can be shorter or longer; consult your active directory administrator for how your installation is setup. The X1EE application may not be accessible by all users in your domain prior to the completion of the replication cycle.
If the default Index Directory is not used, ensure the permissions on that directory include Full Control permissions for the account that the X1 Services are running as.
The default index directory is underneath Program Files / X1 Enterprise Server. Full Control permissions are required so that X1EE can read and write to this directory, as well as create and delete index files. These permissions are automatically assigned if one is logged in as this account when the directory is created.
Ensure the required Operating System ports are available.
The X1EE application consists of a collection of processes that interact with each other using defined ports. Some of these ports are dynamically assigned at the start of the application; others are fixed. See the X1 Server Administrator Guide, Appendix B, for more details on the required ports.
Verify access to the Browser Client
If one desires to access the web client as a user other than the logged-in user, specify the IP address or the fully qualified domain name (DNS) in the URL. This will cause a window to pop up where the username and password can be entered, so that authentication is explicit. The use of localhost uses the workstation credentials.
Browsing may not be immediately available when X1EE is started the first time.
It may take up to five minutes for the first set of indexed data to be committed to index. During this time, you can still see the authorized saved searches, but you will see zero results.
To change the user authenticated with the Browser Client, close the browser and access Browser Client URL again.
User authentication occurs the first time the browser accesses the web client. A session is created by IIS for that user, and all accesses by the browser thereafter are for that user. To change users, the browser must be closed and reopened, which forces IIS to create a new session and authenticate the user.
To Register the X1 Server Product
The X1 Server comes preconfigured with a trial license that limits you to one server, 15 concurrent web users, 4 indices, and 30 days of use. You will need to apply your license file prior to installing any additional nodes to your cluster and prior to the expiration date of the trial license. To apply your License File, first save the file to the server that will act as the central node. We do not recommend saving it in the same directory as the X1 Server installation in case you need to uninstall for some reason. Please note that after applying the license file, X1 creates it's own copy and you are free to move the original to another location. Start the Cluster Manager. In the Help menu, select "Register Product..." Click Load and navigate to the location where you saved the license file. Highlight the license file and click Open. Look over the information within the License File to verify it is correct. If there are any errors, you should contact X1 Customer Care for a new License File. Click Apply to apply the License File. Click Yes and OK to the confirmation dialog boxes. Click Close to close the license information dialog box. Your license file is now applied.
BEST PRACTICES TO AVOID KNOWN ISSUES
This is a quick summary of actions that can be followed to avoid known issues. To read more about the description of the problem and solutions once the problem is encountered, please refer to the Troubleshooting section below.
- Do not install the server on a disk configured with a FAT32 file system
- Do not install the server on the domain controller
- Do not install the Federation Engine and the Browser Client on separate nodes
- Do not install X1EE as a user not explicitly part of the domain that the server is running on.
- Do not use the characters !&-)#$_ within the Installing User Name
- If DNS load balancing is in use for a server with two IP addresses that map to the same hostname, then during installation explicitly specify the IP address to use for all X1EE access, and not the hostname of the server.
- Installing Google toolbar or ICQ toolbar within Internet Explorer on computers that you want to use the Browser Client to access the X1 Enterprise Server will cause problems when executing the Open File action.
- Anti-virus software installed on the sever may interfere with installation, operation, or performance of the X1 server.
- When creating mountpoints, set share security = false if you are not using Share Level Security
- Never set permission = deny on a saved search for any groups the installing user belongs to.
- Avoid restarting the Index Engine during a running scan.
- Do not attempt to change the state of a scanner multiple times without verifying that the first state change was completed.
- Do not remove a running mountpoint. First stop it and delete data prior to removing it.
- When executing "Start all services" against several nodes, visually verify that all nodes have started.
- Do not place invalid SCM files in the X1 Enterprise Server\x1ee\schemas directory or save mountpoints in this directory
TROUBLESHOOTING - WORKAROUNDS FOR ISSUES USERS MAY ENCOUNTER
Server running X1EE is unable to authenticate users. (XEE-2207)
Ensure the clock on the X1EE server is within 5 minutes of the Active Directory server. Otherwise, the Kerberos tokens issued by that server will not be authenticated. To ensure the server clock never drifts, enable NNTP server synching.
The server will not run if installed on the domain controller (even in a VM) (XEE-2027)
Install the server on a non-domain controller
The presence of an anti-virus application may adversely affect X1EE performance. (XEE-2016)
Some anti-virus applications may utilize ports that X1EE requires, making it impossible to start the X1EE application. We have specifically noted a problem with McAfee VirusScan enterprise 8.0.
User is able to see data on a mountpoint that was removed while it was indexing data. (XEE-1913)
Delete the index that this mountpoint was writing to. Warning - deleting the index will delete data from other associated mountpoints.
High System Controller memory use. By default the System Controller is configured to use up to 512 MB of RAM. In situations where there are a large number of Connector Engines scanning a large number of unusually large files this may be insufficient. This unusual situation can be observed by selecting View: System Controller Performance and observing the "Current Memory %" value. In this situation the memory will be close to or at 100%. (XEE-1902)
Contact X1 Customer Service who can walk you through the steps of increasing the System Controller memory allocation.
Indexed Count and Document Counts are not matching after restarting the Index Engine. (XEE-1884)
If the queue is stacking up due to system performance issues, the correct action is to pause running scanners to allow the queue to clear up and then resume the scanners. Avoid restarting the Index Engine during a full scan to try to solve this problem.
In Federation Engine, some schemas are actually saved searches, and "Edit Aliases" does not work. (XEE-1870)
Ensure that there are no inappropriate files in the X1 Enterprise Server\x1ee\schemas directory.
Browser Client returns "The X1 Server is not responding" when the Browser Client is installed on the central node and the Federation Engine is on a remote node (XEE-1857)
The Federation Engine and Browser Client must be installed on the same node. Reinstall components to achieve this configuration.
Not all nodes start when executing "Start all services" and the "Start all services" command is still active. (XEE-1849)
This may occur when the remote nodes are on slow machines and the cluster manager times out on sending the start command. Re-execute the "Start all services" command until all nodes have started. Consider improving the hardware on the slow nodes.
Errors when installing the Federation Engine on a system with a FAT32 file system (XEE-1826)
Do not install X1EE on a system with a FAT32 file system - file systems must be NTFS to properly support Active Directories.
Authorization denied - unable to access saved search with browser client or desktop client. (XEE-1811)
In the IIS – websites - services tab, ensure IIS 5.0 isolation mode is not checked.
User that X1EE is installed as receives "You do not have access to any Published Searches on this X1 Server" when accessed via the user used to install the server. (XEE-1805)
Ensure that the user used to install the server is explicitly part of the domain that the server is running on. The user cannot only be a associated with a trusted domain.
Installation does not begin, a java.lang.Exception error occurs or cannot grant "Log on as a service" rights (XEE-1767)
Use of characters !&-)#$_ in the Installing User Name are not supported. If needed, create a custom user name with just alphanumeric characters to install the X1 Server.
When a computer in domain A scans files from a computer in domain B, users from domain A can't see the files. Domain A and domain B are trusted domains (XEE-1751)
Please contact X1 Customer Support to help resolve this issue.
Occasionally may be unable to resume a paused scanner. In some unknown circumstances the Cluster Manager may not show the "resume" option for a "paused" scanner. This prevents the administrator from resuming the paused scanner. (XEE-1737)
Try the following steps: 1) Restart the Cluster Manager. 2) Wait for a few minutes to see if the problem resolves itself. 3) Select the "Restart All Servers" command from the Servers menu in the Cluster Manager. 4) If the scanner never truly paused, you may have to wait until the scanner has completed prior to trying to change the state of it. You can verify if the scanner is still processing by checking the System Controller Performance.
When accessing with the client, user receives "this page cannot be displayed/cannot find server or DNS error" (XEE-1681)
When installing on a server with more than one IP address, always specify the IP address when identifying central and remote nodes. Do not use the NETBIOS or DNS name.
Installing User is unable to reconfigure the Federation Engine (XEE-1005)
The installing user must never deny permission (including being denied permissions as a part of a group) to saved searches as it prevents viewing of them from within the Federation Engine. To fix this, you must go to the installation folder ...\X1 Enterprise Server\x1ee\published and in the security tab within the properties dialog uncheck the deny permission that is causing the problem. The general rule is "Allow a set, and then deny a subset."
User accesses the Browser Client and uses it to open a file. Following that, no additional files can be opened with that Browser Client. (XBR-129)
Either do not use the Open File action or do not install the Google toolbar or ICQ toolbar within Internet Explorer.
HTTP 500 error when try to access X1EE
Ensure IIS services are started. Sometimes, the World Wide Web Publishing service will not start because the HTTP SSL service is disabled.
|
|
|
|
|
|
|
|
