| Enterprise
Search & Categoriztion
Browse the inContext™ FAQ
Q: Arikus Information
Q: inContext™ Information
Q: inContext™ Site Deployment/Infrastructure
Q: inContext™ Performance and Scalability
Q: ASP / Hosted Deployment
Q: Software Deployment/Installation
Q: Information Collection Features
Q: Search Functions
Q: Indexing Features
Q: Development and Operations
Q: Reporting
Q: Miscellaneous
Q: Documentation
Q: Sales Channel
Q: Pricing (Manufacturer's Suggested
Retail Price)
Q: Support and Maintenance
Q: Customers
|
|
| Q:
Arikus Information |
| Full
Company Name |
Arikus Inc. |
| Year
Established |
1997 |
| Website |
www.arikus.com |
| Public/Private |
Private |
| Corporate
Headquarters Location |
Toronto, ON, Canada |
| Primary
Sales Telephone Number |
1-877-868-8804 |
| Primary
Sales Email Address |
sales@arikus.com |
| Support
Website |
www.arikus.com/support.html |
| Number
of current customers for this product line |
100+ |
| Smallest
Installation |
6-Seat |
| Largest
Installation |
5000-Seat |
|
| |
|
|
| Q:
inContext™ Information |
| Product Name |
inContext™ |
| Date
product first released to market |
1-Jun-00 |
| Current
software revision |
2.6 |
| Release
date of latest version |
12-Jul-05 |
| Target
Customer Size |
Small/Medium/Enterprise |
| Can
it be purchased as a point solution? |
Yes |
| Components
included in this product |
Search server, crawlers, categorization,
summarization, notification |
| How
many commercial releases has your product had to date? |
7 |
| How
many major / minor releases, service packs, etc. does
Arikus release per year? |
1 Major version, 3-4 point releases.
Ongoing hot fixes. |
| What
is the version number of the next planned release? |
3.00 |
| What
is the expected release date for the next version? |
Q4 2005 |
| Industry
standards followed/used |
XML, J2EE, COM, .NET, PHP |
| What
development frameworks are supported? |
Java, COM, .Net, PHP |
| Smallest
installation |
5 users |
| Largest
installation |
1000+ users |
| Average
installation |
100+ users |
| Number
of current customers for this product line |
100+ |
|
|
|
|
| Q:
inContext™ Site Deployment/Infrastructure |
| Dedicated
server/workstation required |
No |
| Supported
Browsers for Client |
|
| Microsoft
IE 6.0 |
Yes |
| Microsoft
IE 5.5 |
Yes |
| Microsoft
IE 5.0 |
Yes |
| Microsoft
IE 4.0 |
Yes |
| Netscape |
Yes |
| Firefox |
Yes |
| Mozilla |
Yes |
| Safari |
Yes |
| Opera |
Yes |
| Supported
server operating systems |
|
| Microsoft
Windows XP Professional |
Yes |
| Microsoft
Windows 2000 |
Yes |
| Microsoft
Windows Server 2000 |
Yes |
| Microsoft
Windows Advanced Server 2000 |
Yes |
| Microsoft
Windows Server 2003 |
Yes |
| Microsoft
Windows Server 2003 Standard Edition |
Yes |
| Microsoft
Windows Server 2003 |
Yes |
| Microsoft
Windows 2003 Enterprise Edition |
Yes |
| Microsoft
Small Business Server 2003 |
Yes |
| Microsoft
NT 4.0 |
Yes |
| Novell
Netware |
Yes -- Upon Request |
| IBM
AIX |
Yes -- Upon Request |
| HP-UX |
Yes -- Upon Request |
| Suse
Linux |
Yes -- Upon Request |
| Red
Hat Linux 7-9 |
Yes |
| Red
Hat Enterprise Linux 3 |
Yes |
| Solaris
(2.7 = 7, 2.8 = 8) |
Yes -- Upon Request |
| Does
inContext™ require a database to be installed? |
No |
| Supported
databases |
|
| Microsoft
Access |
Yes |
| Microsoft
SQL Server 2000 |
Yes |
| Microsoft
SQL Server 7.0 |
Yes |
| Oracle
8 |
Yes |
| Oracle
9 |
Yes |
| Sybase |
Yes |
| DB2 |
Yes |
| MySQL |
Yes |
| PostGres |
Yes |
| Informix |
Yes |
| Ingres |
Yes |
| Supported
web servers: |
|
| Apache |
Yes, All |
| Microsoft
IIS |
Yes, All |
| Netscape |
Yes, All |
| Sun
Java System Web Server |
Yes, All |
| In
terms # of users - what do you consider a typical deployment. |
500+ |
| Recommended
hardware configuration for an average deployment. |
1 development, 1 staging,
1 production |
| What
are the hardware requirements for the servers identified
in the above response. |
Minimum system: single
CPU (>2.5 Ghz), 2Gb RAM and a fast hard drive. Additional
CPU would provide more headroom for any peaks of activity |
|
|
|
| Q:
inContext™ Performance and Scalability |
| How
is backup implemented? |
Copying the database
files to a secure location |
| How
is restore implemented? |
Restore files and refresh from admin
console |
| Multi-site
deployment |
Yes |
| Does
the product support load balancing? |
Yes |
| Does
the product support clustering for failover protection? |
Yes |
| Do
you support high-availability configurations? |
Yes |
| Recommended
failover configuration |
Network Filesystem to hold files.
Systems can then access shared files |
| Supported
configurations |
|
| Active
/ Passive |
Yes |
| Active
/ Active |
Partial (only one can be adding
documents) |
| Active
/ Standby |
Yes |
| Cold
Standby |
Yes |
|
| |
|
|
| Q:
ASP / Hosted Deployment |
Do
you provide managed services through yourself or through
partners?
|
No |
|
| |
|
|
| Q:
Software Deployment/Installation |
Login
script/command line
|
Yes |
|
| |
|
|
| Q:
Information Collection Features |
| Document
Types Supported |
Over 290 file formats supported |
| WORD |
Yes |
| Excel |
Yes |
| PowerPoint |
Yes |
| PDF |
Yes |
| HTML |
Yes |
| Text |
Yes |
| XML |
Yes |
| Outlook |
Yes |
|
| |
|
|
| Q:
Search Functions |
| Relevance
Ranking |
Yes |
| Boolean |
Yes |
| Natural
Language |
Yes |
| Fuzzy Search |
Yes |
| Search by
Document Section (Headline, Lead Paragraph, etc.) |
Yes |
| Word Stemming |
Yes |
| Synonyms |
Yes |
| Stop Words
- Default and User Defined |
Yes |
| Limit Search
by Document Type |
Yes |
| Phrases |
Yes |
| Word Proximity |
Yes |
| Query by
Example - "More Like This" |
Yes |
| Search within
Search Results |
Yes |
| User Defined
Relevance Rank |
No |
| Spell Check
and Replacement for Query Words |
Yes |
| Search by
Metadata |
Yes |
| Include
/ Exclude Specific Collections |
Yes |
| System Default
Boolean Operator |
User selectable |
| Configurable
Default Boolean Operator |
User selectable |
| Supports
Web Search + (AND) - (NOT) notation |
Yes |
|
| |
|
|
| Q:
Indexing Features |
| Incremental
Indexing |
Yes |
| Time delay
to index new documents |
Configurable |
| Spider to
find new documents |
Yes |
| How are
changes to documents handled |
Old documents are revmoed from the
index and the changed document is added |
| Relative
size of index to document collection |
Depending on features selected from
.25-.75 of collection |
| Automated
publishing of updated indexes |
Yes |
| Federated
Search across multiple index collections |
Yes |
| Content
Expiration - Ability to selectively expire douments from
the Index |
Yes |
| Automatically
expire content based on publish date, expiration date,
etc. |
An administrator can setup a time
from the insertion time that the document should be
removed from the index. |
| Ability
to exclude documents from index so that sensitive document
collections are not available to general users |
Yes |
| Index External
Sources (websites) and integrate with internal sources |
Yes |
| Notification
of indexing success / failures |
Yes |
| Notification
of content upload success / failures |
Yes |
| Classification
Features |
|
| Automatic
Classification / Categorization of Documents |
Yes |
| Taxonimies
provided |
These are provided by our partners |
|
| |
|
|
| Q:
Development and Operations |
| API
Availability |
Yes |
| Languages
supported |
.Net, C++, COM, Java |
| Document
Limit per server |
No fixed limit. Depends on Hardware |
| Queries
per Second |
Peak Rates > 20 per second |
| Average
response Time per Query |
Depends on size of index. For a
moderate size index .1 seconds |
|
| |
|
|
| Q:
Reporting |
| Standard
reporting capability |
Yes |
| Standard
Reports Available |
Top Search Terms, Search
Volume, Queries with 0 Results, Queries with Spelling
replacements, etc.
|
| Real Time
Access to Search Logs |
Yes |
| API Access
to Seach Logs |
No |
| Alerting
Ability on Seach Volume or Specific Searches |
No |
| Ability
to customize reports |
Yes |
| Ability
to export data for reporting |
Yes |
|
| |
|
|
| Q:
Miscellaneous |
| What mechanism(s)
do you have in place for notifying customers of critical
updates / patches? |
E-mail |
| What 3rd
party products (including open source) are embedded in
the product? |
Apache Tomcat |
| What is
the support model for these? |
We fully warranty any included open
source software |
| How long
does a typical deployment take (requirements to deployment)? |
Measured in days. |
| Does InContext have
a documented SDK for customer driven development / integration? |
Yes |
|
| |
|
|
| Q:
Documentation |
| Installation
manuals |
Yes |
| User guides |
Yes |
| Development
manuals |
Yes |
|
| |
|
|
| Q:
Sales Channel |
| Sold
directly |
Yes |
| Sold via
resellers |
Yes |
| Sold via
integrators |
Yes |
|
| |
|
|
| Q:
Pricing (Manufacturer's Suggested Retail Price) |
| Are
trial periods available? |
Yes |
| How long? |
15 days |
| License
Methodology/Structure |
Number of documents per server |
| Price based
on number of documents |
|
| Are Government and Educational Discounts available. |
yes |
| Is there
a fee for update services? |
Not with support contract. |
|
| |
|
|
| Q:
Support and Maintenance |
| Basic
Service |
Business hours, tech
support, upgrades incl. |
| Cost of
basic service |
20% of purchase price |
| Upgrades,
fixes, etc. downloadable via support website |
Yes |
|
| |
|
|
| Q:
Customers |
| Arikus
technology deployments include those acquired through
working together with our partners, with whom we’ve
delivered integrated solutions into legal, enterprise,
publishing, and helpdesk sectors. Arikus inContext™
is deployed at over 100 Fortune 5000 companies.
Some customer deployments have been running for
over 5 years without interruption. Deployments include
scenarios where document counts have surpassed over 30
million documents with approximately 10 meta-tags for
each file. The original index size was almost 50
Gb. |
|
