|
Contents:
About This Release
Introduction
What's New In Visual Intercept Enterprise 3.7
What's Available In Visual Intercept Enterprise
Getting Started
Upgrading from an Earlier Version of Visual Intercept
Release Notes
Installation Notes
Technical Support
Visual Intercept 3.7.0 is a service release which includes new features as well as minor fixes and change requests.
This readme describes new features and issues resolved by Visual Intercept 3.7 as well as specific issues addressed by the Visual Intercept 3.7.0 service release as described in the Release Notes section of this document.
Thank you for choosing Visual Intercept Enterprise 3.7. This guide is designed to help you quickly install and configure Visual Intercept Enterprise as well as keep you up to date on the latest updates and incident fixes.
The Getting Started section provides information on installing Visual Intercept for evaluation, for multiple users in a networked environment, or as an upgrade from an earlier version of Visual Intercept.
The Release Notes section provides information about known and resolved incidents in this version. The release notes are detailed, but not comprehensive. If you believe you are experiencing a problem not mentioned in the Known Incidents section or would like to receive more information about a known incident, please feel free to contact Elsinore Technologies Technical Support Services.
The Installation Notes section provides information on system requirements, ODBC information and basic installationinstructions. For more detailed information please refer to the Visual Intercept User's or Administrator's guide.
This guide does not cover the administration and use of Visual Intercept. For information on using Visual Intercept, please consult Visual Intercept's Help system or the appropriate Visual Intercept manual. If you have questions or encounter problems that are beyond the scope of these documents, please contact Elsinore Technologies technical support services.
Back to Top
The following is an outline of the features and enhancements you can look forward to in Visual Intercept 3.7. The features are grouped by the product to which they apply.
Visual Intercept 3.7 is a service release that includes the following new features and enhancements that were introduced in Visual Intercept 3.7. For information on defects and other changes addressed in this release, please consult the Release Notes section of this document.
Incident Management System
| Feature |
Enables you to |
| Directory Services Integration |
Visual Intercept System Administrators can provide users with automatic logon based on Windows authentication, and user account, contact, and group security information can be automatically updated from directory services. |
| Administrator Search Tool |
Visual Intercept Web Administrators can easily search for users or groups by keyword or attribute. |
Back to Top
The following is an outline of the features and enhancements you can look forward to in Visual Intercept 3.x. The features are grouped by the product to which they apply.
Incident Management System
| Feature |
Enables you to |
| Additional custom fields types |
Utilize more custom fields as well as new UserID and Boolean custom fields |
| New standard fields |
Track product build numbers associated with incidents, dates associated with product versions, and comments associated with related documents |
| Parameter precedence values |
Override the ASCII sort order to define custom sort orders for parameters such as Priority |
| Notifications for new users |
Allows the administrator to have new users automatically notified when they are added to Visual Intercept |
| E-mail templates by status |
Have different e-mail notification content based on incident status |
| Template based cloning |
Replicate and relate incidents together for tracking multiple instances of the same incident |
| Mass update capability for work start, work stop, version, and release fields |
Update these fields for multiple incidents at a single time |
| Status Promotion Reversal |
Provide users the option to reverse the last status promotion for an Incident if they are the user that made the status change |
Visual Intercept Enterprise Web and Web Relay
| Feature |
Enables you to |
| Integrated screen capture and attachment |
Generate a screen capture from any window and a have it automatically attached and uploaded with the current issue |
| Ability to add custom fields to list views as a user preference |
Allow your users to add custom fields to document list views |
| Ability specify users as Web Relay only users |
Prevent Web Relay users from logging on to Web Enterprise and have them re-directed to the correct web site |
| Previous and next navigation on item forms |
Navigate to the previous and next items in a list without having to navigate away from the document form |
| Incident ID display in browser title bar |
Easily view the current incident ID when scrolling or when multiple browser windows are open |
| Visual SourceSafe Integration |
Associate source file versions with incidents and check-in and check-out source files from Visual Source Safe over the internet |
| Mass-update capability |
Modify multiple documents in one action |
| Spell checking |
Check the spelling of your text entries into Visual Intercept |
| Automatic logon |
Logon to Visual Intercept without a logon prompt |
| Recurse option for the Explorer view |
Have the Explorer view display incidents related to all sub-projects of a selected project |
| Clone users and groups |
Easily create similar users and groups without having to re-enter settings and permissions |
| Support for $PROMPT queries |
Create queries that prompt you for the search value |
| Reverse sorting on columns |
Sort a list ascending or descending by clicking on the column header |
| New Document Icons |
Easily create new incidents and other documents from the toolbar |
| Electronic signature support |
Require users to enter their password to verify their identity when updating or inserting records |
| Toolbar button for navigating from a document |
Easily navigate from an incident or other document back to a list or Explorer view |
| Notification and prompt to reset session timeout before expiration |
Allows users to reset the timeout before their session terminates |
| Auto update option |
Allows users to have their work saved to the database without clicking the Update button |
| Support for [Incident Search] and [Incident Bookmarks] for reporting |
Allows searches and bookmarks to be used wherever the query list is displayed |
| Relay incident submission options |
Allows Visual Intercept Web Relay to be configured so users can optionally set priority, category, and severity when an incident is created |
| Multi-site support per web directory |
Run multiple sites with different options from one physical web directory |
| Date display options |
Control the format of date display as a user preference |
| Ability to limit Request ID based on project privileges |
Control who can be set as the RequestID based on those users who have privileges to those incidents |
| Auto logon is configurable as a per-site option |
Control which sites allow for autologon |
| Drag and drop status promotion editor |
Easily build, edit, and review incident workflows in a drag and drop environment |
| Document bookmarks |
Create links to specific Incidents and other Visual Intercept documents you work with frequently without building a search or query. |
| "Go to Page" navigation |
Jump to any page in a set of document lists by simply entering the page number |
| Document e-mail templates |
Use templates to provide different formats for Incidents and other documents you e-mail from Visual Intercept Web |
Visual Intercept Enterprise Desktop and Studio
| Feature |
Enables you to |
| Integration to Rational ClearCase |
Associate ClearCase versioned objects with incidents and check them in and out from within Visual Intercept |
| Incident submission from Outlook e-mail and Outlook tasks |
Select and e-mail or task in Outlook 2000 or XP and click a button to create a new Visual Intercept Incident from it |
| Integration to the Accurev Version Control System |
Relate found and fixed versions of sources files to Incidents and check-in and check-out from directly within Visual Intercept |
Visual Intercept Enterprise Project
| Feature |
Enables you to |
| Import/Export of work start and finish dates |
Visual Intercept incidents now persist work start and finish dates from or to a Microsoft Project plan. |
|
Percent Complete Update
|
Update the precent complete for tasks based on corresponding Incident status values
|
|
Hyperlink Generation
|
When linking tasks and summary tasks to projects generate the link as a URL within the plan.
|
|
Task Leveling into Alternate Date Fields
|
Place leveled task finish dates into alternate date fields without altering actual dates. |
Back to Top
Installing for Evaluation
If you are installing Visual Intercept for purposes of evaluation, it is likely that you will want to run the Visual Intercept Wizard after installation. The Visual Intercept Wizard can load the Visual Intercept database with various kinds of sample data as well as assist in creating a Visual Intercept Project hierarchy for production use. The Visual Intercept Wizard is located in the Visual Intercept Enterprise program group.
In addition, if you are evaluating, you may not have access to a high performance database management system such as SQL Server. For this reason, Visual Intercept Enterprise can be installed with a pre-configured Microsoft Access database file. Because it requires no configuration or additional software, the Microsoft Access database is ideal for evaluation. However, because of performance limitations we do not recommend that you use an Access database in production environments where more than 10 users will be using Visual Intercept. Please see the next section of this guide for information on using Visual Intercept with other Database Management Systems.
If you selected Microsoft Access as your DBMS during a Server installation, the database file was installed to your local drive and an ODBC connection was created to connect Visual Intercept to the database file. Every Visual Intercept database is pre-configured with four users: isuser, isadmin, isnotify, and guest. The passwords for each of these users is null. Thus, when prompted to logon to Visual Intercept simply click OK in the Visual Intercept Security dialog.
The Project hierarchy forms the backbone of the Visual Intercept Incident Management System. All Incidents are registered against a particular version of a Project. You can create your Project hierarchy and sample data working from the Visual Intercept Manager. However, the most efficient way to populate the database is through the Visual Intercept Wizard, located in the Visual Intercept program group. The Wizard presents you with three options: Source Code Control System, Product Architecture, and Example Project. The Example Project data includes 100 Incidents, 45 Projects, 30 Contacts, 7 Accounts, and 5 Hardware; these numbers represent the amount of data a user might expect to fetch when using the product.
If you choose the Example Project option, you will be prompted at one point to log on to the Visual Intercept database as the Visual Intercept administrator (isadmin). The logon dialog will contain the userID "isadmin". Simply click OK. As previously mentioned, the password for isadmin is null. Once you click OK the application will insert the sample data into the database. Inserting the example data requires that you log on as administrator because the process will drop all existing data in the database.
The Product Architecture option will step you through the process of creating a project hierarchy based on several common types of software architecture. When prompted to login simply click OK. The user password is null by default.
If you want to model your Visual Intercept project hierarchy on a project hierarchy in a SourceSafe database, select the Source Code Control Option in the Wizard. In order to use the Source Code Control option you will need a Visual SourceSafe userID and password. You will also need to know the location of your Visual SourceSafe directory that contains a scrsafe.ini file.
Installing Visual Intercept Desktop for Multiple Users in a Networked Environment
When you install the Visual Intercept Desktop using the Server option a NetSetup directory is created in the Visual Intercept installation directory. The NetSetup directory contains a Setup.exe that clients may use to install Visual Intercept client software to their computers. Besides eliminating the need for installation media, using the NetSetup provides two other advantages. First, the NetSetup does not install the Visual Intercept Administrator, Wizard, or Notification Server. Second you can pre-configure many Visual Intercept installation options by editing the isdefs.ini file located in the NetSetup sub-directory of the Visual Intercept installation directory.
Using Visual Intercept Enterprise With a DBMS Other Than Microsoft Access
When you begin using Visual Intercept in a production environment, or even during an evaluation, you will want to consider using a high performance DBMS for Visual Intercept's back-end database. Visual Intercept currently supports the following DBMS:
- Microsoft SQL Server 6.5, 7, and 2000
- Oracle 7.3 and greater
- Sybase Adaptive Server
When you select either SQL Server, Oracle , or Sybase during installation, Visual Intercept will place a script file in the Database sub-directory of the Visual Intercept installation directory. These files are named respectively: intercpt.sql, intercpt.ora, and intercpt.syb. Each file contains comments on how to run and edit the script file to suit your environment. However, if you have questions about using the script files, please consult the Visual Intercept Database section of the Visual Intercept on-line Help system or contact Elsinore Technologies technical support services.
Once you have run the script file you will have a Visual Intercept database ready to accept data. At this point you may run the Visual Intercept Wizard to populate the database or enter data from Visual Intercept Web or the Visual Intercept Manager and Administrator. The script file creates several Visual Intercept users with blank passwords. You can logon to the new database as "isuser", "guest", "isnotify", or "isadmin". To logon to the new database you will need an DSN (Data Source Name) that connects Visual Intercept to the database. A data source name is created during installation. However, you may also create one manually in the ODBC Data Source Administrator located in the Control Panel.
Back to Top
For detailed information on upgrading from previous versions of Visual Intercept to this release, please consult the migrate.html installed to the Documentation directory of the Visual Intercept Enterprise primary installation directory.
Back to Top
Release Notes:
Incidents closed in this release:
| Incident |
Description
|
| 5329 |
Custom extended user ID Fields now provide the option to select [None]. |
| 5333 |
Extended parameter fields would not populate the correct values for each document type. |
| 5347 |
Custom date fields could prevent entry of dates in Work Start and Work Finish date fields. |
| 5398 |
Web Administrator would prompt for Group name in incorrect circumstances. |
| 5420 |
Verbose and Account bullet reports would not print when using Oracle. |
| 5670 |
The "k" in the "Add SharePoint Link" button was malformed. |
| 5677 |
Visual Intercept Web now produces a more informative error message when a use tries to delete their contact information. |
| 5766 |
Spin button behavior was corrected on the form for new items. |
| 5836 |
Error message produced when using spin button after attaching a hardware item to an incident. |
| 5837 |
Spin button would not function properly after attaching one incident to another. |
| 5844 |
Corrected a date mismatch that could cause notifications to fail to be generated. |
| 5847 |
Hardware Bullet report now displays total number of items in the title. |
| 5856 |
Custom parameter fields enabled via the desk top now properly display in the notification builder. |
| 5857 |
Changes to Custom Parameters would not trigger notifications. |
| 5860 |
Query with "Incident.WorkFinishDate IS NULL" in WHERE clause would fail with SQL syntax error in desktop Manager. |
| 5862 |
Calendar control would jump when adding a resource to incident on last row of calendar. |
| 5863 |
Version field would not default to the version with the most current date. |
| 5864 |
Status Promotion Reversal feature was not functional. |
| 5866 |
Installing on a machine without the .NET framework would cause errors preventing updates to administrative options. |
| 5867 |
Changing the name of an existing notification rule and clicking Save would create a 2nd rule, rather than updating the 1st rule. |
| 5869 |
Changes introduced in v3.6 ismail.dll were not compatible with Exchange v5.5. |
| 5872 |
Incident query results were not being recursed properly in Explorer view. |
| 5873 |
Inconsistencies in the display of custom date fields between the Web and desktop version were corrected. |
| 5874 |
Some projects would not display a complete contact list. |
| 5875 |
Right-click in the Browser and Explorer in the Visual Intercept Manager would change color coding of projects. |
| 5887 |
Mass update on release version would causes the Visual Intercept Manager to crash. |
| 5890 |
Notification builder in Visual Intercept Web Administrator was changed to use single quotes. |
| 5891 |
Linking a task to an incident with required Custom field produces an error message using Date field. |
| 5893 |
Date Format broken when adding project versions in dd/mm/yyyy format. |
| 5900 |
With the Document Content Indicator set to True in teh DefaultProfile.xml, the tabs do not italicize. |
| 5905 |
Tab display options would not persist in the Visual Intercept Manager. |
| 5906 |
Web email template would post the incorrect link if site is secure. |
| 5908 |
Incident to incident relationships could be improperly removed in the Visual Intercept Manager. |
| 5913 |
Cloning a project in the Visual Intercept Manager would create two new projects in the Browser. |
| 5921 |
Security restrictions for Hardware & Contacts documents could fail to be enforced. |
| 5925 |
-16 Error when trying to modify the Parameter name in Visual Intercept Web or Web Relay when adding text to name. |
| 5926 |
With ALL Custom fields enabled the calendar for Date one would display behind the custom Parameter 1 & 2 fields. |
| 5927 |
Related projects would not display on Account document. |
| 5933 |
Default set to select Cancel instead of Attach when attaching Sharepoint links to Projects. |
| 5939 |
-12 error when sorting custom/Customex columns in bookmark view. |
| 5950 |
Project import would not correctly create versions. |
| 5952 |
At time of insertion versions could not be created for root projects. |
| 5955 |
Unable to clone a document's Boolean field information. |
| 5956 |
Shared Folder tab for Projects would produce a -12 error when using Oracle. |
| 5959 |
Inconsistent timestamp behavior in Web Relay with protect existing text enabled. |
| 5960 |
Entering UserID and Password for Sharepoint credentials did not enable Apply button in the Web Administrator. |
| 5966 |
Unable to update after attaching projects to the account document. |
| 5968 |
Attaching Incidents to Projects in the Desktop will not allow the user to update until you close out of the manager. |
| 5969 |
Checkbox not remainined selected for Immediate on the Shared tab of a project in the Desktop Manager. |
| 5979 |
New Document form now prompts for Required information if you attempt to insert without required information. |
| 5999 |
Checking the Delete option for Projects in a group should also check and gray out Refresh of Contacts before Insert/Update. |
| 6008 |
Apply button not working correctly for Customize options on Tab Display in the Desktop Manager. |
| 6016 |
Custom Required fields are entering data without prompt if you do not enter data yourself on insert. |
| 6039 |
Update project needs to be selected for inserting incidents in the web product. |
| 6040 |
Need update selected by default for projects selected on group that you want the ability to insert projects only projects for. |
| 6046 |
Creating Group with Same name as one that already exists did not prompt user about duplicate name. |
| 6050 |
Moving incidents and deleting the original project resulted in loss of historical data. |
| 6051 |
Unable to detach an incident from a contact document in Visual Intercept Web. |
| 6053 |
Modification of group name in the Web administrator would produce an error. |
| 6055 |
Sorting on custom fields for Accounts would produce a -12 error message in Visual Intercept Web. |
| 6059 |
Adding Screenshot to contact in Web Relay would not display check box for remove selected. |
| 6060 |
Could not launch attached documents from a user's contact page. |
| 6061 |
Importing logo in Web Administrator was case sensitive when checking format of image. |
| 6085 |
Description field for contacts would not display in list views. |
| 6086 |
Related Projects tab would not italicize if you had projects attached. |
| 6101 |
Including apostrophes in the page title set in the administrator would cause logon page errors. |
| 6107 |
Release field would reset to null when moving an incident from one project to another. |
| 6108 |
In the query builder users listed as possible values were not ordered correctly. |
| 6116 |
Visual Intercept Web would not prompt the user to save changes before leaving the page to print. |
Incidents closed in previous 3.6 releases:
| Incident |
Description
|
| 5855 |
When editing certain custom fields the "Document Changed" icon does not appear |
| 5822 |
The Contact documents tab in Web Relay has Client column and should be comment column |
| 5850 |
Setting work start or finish does not set the modified flag on the incident |
| 5849 |
Report Limit: not letting reports display when you change it from 0 to another number such as 5 |
| 5848 |
Searching for Hardware documents by Search string not working in Web Relay |
| 5846 |
Cannot enter info into Hardware Search String to search |
| 5845 |
Cannot change the Account Code after inserting into the database Recieve -12 error when update again |
| 5843 |
Can not null values for SharePoint in web relay admin |
| 5842 |
isnotesv.tpl displays full project name in incident notification even if $PROJECT is used as the variable |
| 5839 |
ShowCrystalReports.asp strNoValue should not be set to 0 |
| 5838 |
Two Stock queries are not working Old Active Incidents and Incidents by Start Date |
| 5833 |
Creating Global queries does not work for all parameters in the Web Administrator |
| 5829 |
CustomEx data is lost on Project move |
| 5828 |
Comments to document attachments are lost if Enter key is used |
| 5827 |
Visual Intercept Web Help is missing image in Setting topic |
| 5826 |
"Restrict UserID to Web Relay" can cause confusion and prevent user from logging in |
| 5821 |
The VI Project Import Wizard's "Create Tasks from Projects" returns nothing |
| 5819 |
Changes to "Enable email notification" do not persist in the Notification Options tab |
| 5816 |
"Incidents By Contact" returns -12 error if more than one user has a similar last name |
| 5815 |
"Verify Query" tool returns "Verification FAILED" on all stock queries |
| 5814 |
Cannot insert a new version if date format is set to "yyyy-mm-dd" |
| 5811 |
ORDER BY sql statements fail in the Explorer view with a -12 error |
| 5809 |
Stock "Incidents By Contact" query returns errors and does not fetch desired dataset |
| 5807 |
$CONTACTID is being transposed in the Web to $CHANGEID |
| 5806 |
VersionBuild and ReleaseBuild are not included in the isnotesv.tpl variablee reference list |
| 5802 |
SCCS File Properties feature can fail with errors |
| 5801 |
Attempting to create a notification rule with a forward slash in the RuleName returns a -2 permissions error |
| 5798 |
Upgrade overwriting modified isnotsv.tpl's and changing Notification SMTP IP to default 192.168.1.1 |
| 5796 |
Enabling "Protect Existing Text" prohibits the use of templates as the new incident doc loads with the template txt protected |
| 5795 |
Incidents won't load in the incidents frame of the Explorer view on clicking "Return To View" in an incident document |
| 5794 |
Incident Clone feature does not set $LEADID value |
| 5791 |
isnotesv.tpl is not pulling data for $CUSTOM fields |
| 5790 |
After upgrading to v3.6.1, viWebDev prompts users asking if they want to display non-secure items |
| 5789 |
Once SharePoint integration is enabled in the WebDev Admin (and WebRelay Admin), it cannot be disabled |
| 5782 |
$PROMPT queries do not work reliably with reports |
| 5781 |
Errors when selecting Tools | Reset Web in Web Admin |
| 5780 |
Errors reported when generating "Old Active Incidents" report |
| 5779 |
Error received when attempting to print a result set based on StartDate of Incidents |
| 5773 |
Web Reports are limited to under 250 records |
| 5769 |
Status Promotion Model cannot be enabled or disabled via the web admin |
| 5768 |
Start-up queries are not executing in some circumstances |
| 5765 |
Custom parameter field values not being passed when creating new parameters in administrator |
| 5764 |
Cloning with Extended Custom Number fields blank will insert a 0 into the field for all document types |
| 5762 |
$PROMPT Queries fail on validation but work when you execute them |
| 5743 |
The project name for an incident is not auto adjusting to display the full name as it does on the project document |
| 5738 |
Hardware documents with long names could not be related to incidents |
| 5713 |
Some security settings would prevent users from adding versions to projects for which they had privileges |
| 5686 |
Opening a vii file produces an Unexpected File Format error |
| 5682 |
Cannot sort the Named Users from the Statistics window in the Web Administrator |
| 5681 |
Cannot open the Promotion Editor when looking at the About information |
| 5676 |
Work Start and Work End dates are not available for the column list views on Incidents |
| 5667 |
Changing the Date display to yyyy-mm-dd or yyyy/mm/dd would add time in addition to the date |
| 5659 |
Input box for the precedence value should not allow decimals |
| 5655 |
Changes to an incident's related outer-join data updates local ChangeDate, until document Refresh |
| 5654 |
Changes to Custom parameter data doesn't persist ChangeDate in History table |
| 5643 |
Need to implement viPreserveSQL formula handling to leave report SQL alone at runtime |
| 5640 |
Clone.xml does not explicitly exclude history, so when an incident is cloned, the history is as well |
| 5615 |
VI Web does not clone custom data |
| 5611 |
If you have a + in a query name, you can not edit the query or execute it from the query list view |
| 5608 |
Log on screen, focus should be on Password field, not User ID |
| 5607 |
WebDev installer needs to lay down Crystal Desktop run-time components |
| 5598 |
Version Date does not determine sort order |
| 5597 |
Clone feature allows users without insert rights to insert documents |
| 5595 |
Commas in Graphs can cause graphing to fail |
| 5594 |
Renaming of [Root] level project can result in errors and data corruption |
| 5593 |
When 2 instances of VIWeb are open on the same client for the same database data corruption can occur |
| 5583 |
Provide query validation |
| 5581 |
Provide the ability to change the display order of entries in large text fields |
| 5580 |
You are not logged into Visual Intercept message received when attempting to launch documents |
| 5578 |
Error message needs to be changed to better inform users when they have exceeded character limit for titles |
| 5574 |
Error when trying to use import functionality with Project 2003 |
| 5573 |
The default unpack option in the installer should be changed |
| 5571 |
Notification builder in VI Web lacks the notification events for Work Start and Work Finish |
| 5563 |
The viwebconfig.xml is not persisting the forced fixed in version option and this option is not in Admin pages |
| 5482 |
The related resource user ID is being reset to current user on modification |
| 5409 |
When Search is enabled you cannot click the Bookmark icon from a list view to view Bookmarks |
| 5393 |
SCCS integration will not set the fixed version to the current version when checking in a modified file |
| 5360 |
Unbookmark not working from the Actions Menu |
| 5018 |
Attach document dialog in the desktop should support UNC paths |
When using NT 4.0 the MMC snap-in does not display. A number of steps must be made to configure the MMC snap-in.
The "Protect Existing Text" option does not apply to Custom full text fields.
Installation
Visual Intercept Desktop installs VBA (Visual Basic for Applications) 6.0. The VBA 6.0 distribution set is not officially supported for Windows 95. As a result, the Visual Intercept Enterprise installer will generate several exceptions during the installation process and after reboot. When an exception message is generated click the “Close” button, the message will disappear and the installer will continue the installation process. Although the installer generates these exceptions, Visual Intercept Enterprise will be installed successfully.
Data Source Names (DSN):
If your DSN points to a location where the database no longer exists (e.g., you move the database but do not change the DSN), you may get two (2) logon dialog boxes before you can logon to Visual Intercept.
Oracle
Oracle allows only one long field per table. A long is a variable length character string over 255 characters. Furthermore, keyword searches cannot be run against Oracle longs. The Incident table is designed to have three searchable 32k text fields: Description, Resolution, and Workaround. Because of this inherent limitation in Oracle, some compromise has to be made when running Visual Intercept against it. Thus, we designed the intercpt.ora script to build the Description field as a long, and the Resolution and Workaround fields as varchar2. Varchar2 fields are searchable. However, their size is limited to 2k. If you like, you may edit the intercept.ora script to build all three fields as varchar2 or designate the Workaround or Resolution field as the long.
Back to Top
Server Operating Systems and Requirements
Visual Intercept Desktop, Visual Intercept Studio, Visual Intercept Project, and Visual Intercept SDK are compatible with Windows 95, Windows 98, Windows Millennium, NT 4.0, Windows 2000, and XP operating systems. Visual Intercept Web is compatible with NT 4.0, Windows 2000, Windows 2000 Server, and Windows XP Professional running their respective versions of Internet Information Server.
The minimum hardware requirements for a Visual Intercept server installation are: a Pentium class processor of 200 Mhz or greater, 128 MB of RAM, and approximately 100MB of disk space.
Client Operating Systems and Requirements
Visual Intercept Desktop, Visual Intercept Studio, Visual Intercept Project, and Visual Intercept SDK are compatible with Windows 95, Windows 98, Windows Millennium, NT 4.0, Windows 2000, and XP operating systems. Use of Visual Intercept Web requires Internet Explorer 5.5 or greater.
The minimum hardware requirements for a Visual Intercept client installation are: a Pentium class processor of 200 Mhz or greater, 64 MB of RAM, and approximately 80MB of disk space.
Installing the Visual Intercept Incident Management System
Before installing the Visual Intercept Incident Management System, decide which database best suits your needs. At this time Access, SQL Server, Oracle and Sybase are supported. If you select a file based database, such as Access, be sure you have enough room to hold the database as it grows with use. If you select a server based database such as SQL Server, be sure that not only do you have enough room, but you have rights to build an entirely new database.
Note: You must install the Server installation set on at least one computer to deploy all of the Visual Intercept programs. Currently the product ships with an application-ready Access database. The installer can not automatically build other databases against a server. Instead, the product installer copies an installer script to the database directory and you must manually run the script through an SQL editor to build the Visual Intercept database table schema.
Back to Top
When you have a question about Elsinore Technologies’ Visual Intercept Enterprise, look first in the online Help files or the Visual Intercept Enterprise User’s Guide or Administrator’s Guide. If the documentation does not address your question, no-cost support from Elsinore Technologies' support engineers is available via a toll call between 9:00 A.M. and 5:00 P.M. Eastern Standard Time, Monday through Friday, excluding holidays. Support is available to all registered owners of Visual Intercept products for thirty days from the original date of purchase. Additional support contracts are also available. When you call, you should be at your computer and be prepared to provide the following information:
- The version number and product ID of the Visual Intercept product you are using.
- The type of hardware that you are using, including any network hardware, if applicable.
- The operating system that you are using.
- The exact wording of any messages that appeared on your screen.
- A description of what happened and what you were doing at the time of the incident.
- A description of how you tried to solve the problem.
To Contact Elsinore Support Engineers:
Telephone: 866-866-0034
Fax: 919-532-0023
E-mail:
Web Site: http://elsitech.com
Back to Top
|
