Abacus 21 Client Log-In
Username: »Clear
 
Password:
 
 
Forgot your password?

Site Search

Cool Things available from Abacus 21
New Things from Abacus 21

Frequently Asked Questions

Testimonials

Partners


Adobe Reader Download

Subscribe
to Abacus 21's
Product Announcements 

Network, Server, Workstation, and Peripherals Requirements

Workstation (or POS Station)  top

To run Abacus 21 System 441, client devices must meet the following requirements:

  • Standard PC architecture with a minimum processor speed of 1-Ghz or greater suggested -- as required for the Operating System.
  • Windows 2000 or Windows XP (which require Comet 2002-or-better if Legacy products are involved on that particular PC) should be the 'Professional-Edition' or 'Business-Edition' or 'Server-Edition'-versions.  The 'Home-Edition' version is not supported.
    • Windows 95 and Windows 98 are no longer supported.
    • Windows NT4.0 installations need Microsoft Data Access Components (MDAC) 2.5 or greater.  Note that Windows NT Workstation Operating Systems are now considered obsolete by MicroSoft -- and should be avoided.
  • MicroSoft Vista™ has not passed certification (see the seres of announcements over the last couple of years -- the last being the July 17, 2009 Announcement).  Abacus 21 does not plan to certify this lame-duck Operating System.
  • Abacus 21 has completed the bulk of its testing on Windows-7™ -- and it is currently found to be suitable if run in Windows-2003 compatibility mode.  Note that Windows-7™ PC's should have a minimum of 2GB of Memory.
  • Available hard disk space (see below).
  • Microsoft mouse or 100% compatible pointing device (optional for Touch POS Stations).
  • VGA or SVGA video adapter with color monitor capable of 16-bit High-color resolution or better -- with minimally 800 x 600 (1024 x 768 suggested -- depending on PC's specific use).
  • Use of Large Fonts (within a Monitor's Display Properties) may result in Abacus 21 Screen mis-alignments -- and should be avoided.
  • A Network Interface Card (NIC) and TCP/IP Connectivity; 10 Mbps Minimum (100 Mbps or higher suggested).
  • Network 'switches' are preferred to Network 'hubs' to better accommodate network traffic.
  • Appropriate Connectors for POS and regular peripherals.
  • Note:  It is an Abacus 21 System-441 requirement that Network Users must be set up as 'Standard-Users' (as opposed to 'Restricted-Users')

Microsoft Update Workstation Software Considerations -

   The important ones that Upgrade Pilot 1.3+ series checks for are:

  • Microsoft XML Library (MSXML) - This one is the most important and Upgrade Pilot may fail if it is not installed.
    • If this is missing you may get the error:  'System 441 Upgrade Pilot Error: An error in detecting System 441 information has stopped this process.'
    • If Microsoft XML Library 6 (MSXML6) is installed, Upgrade Pilot will work fine and this is what is recommended.
    • Minimally Microsoft XML Library 4 (MSXML4) or higher is required.
    • This is also needed for the About Box Export.
  • Microsoft Internet Explorer 6.0 or higher
  • Microsoft DirectX 9c or higher
  • Microsoft ADO 2.5 or higher (ADO 2.81 recommended)

Other Related Recommendations:

  • Appropriate Anti-Virus protection
  • Appropriate Internet Access
  • Appropriate Backup Provisions

Citrix (or Terminal Service) Workstation  top


To run the ICA Win32 Program Neighborhood Client (not considering any non-Citrix or TS functionality), client devices must meet the following requirements:

  • Standard PC architecture, 80386 processor or greater as required for the Operating System
  • Windows 9x, Windows ME, Windows 2000, Windows XP, or Windows NT 3.51 or later
    • 8MB RAM or greater for Windows 9x
    • 16MB RAM or greater for Windows NT   3.51 or 4.0
    • 32MB or greater for Windows Me and Windows 2000
    • 128MB RAM or greater for Windows XP
    • Note that Windows 9x,Windows ME, and Windows NT are now considered obsolete by MicroSoft -- and should be avoided.
  • To use the ICA Win32 Program Neighborhood Client with a Web browser, Internet Explorer Version 5.0 or later, or Netscape Navigator or Communicator Version 6.0 or later
  • Microsoft mouse or 100% compatible pointing device
  • VGA or SVGA video adapter with color monitor
  • High-density 3.5-inch disk drive (optional) and available hard disk space (see below)
  • For network connections to the MetaFrame server, a Network Interface Card (NIC) and the appropriate network transport software are required.   Supported connection methods and network transports are:
    • TCP/IP+HTTP
    • SSL/TLS+HTTPS
    • TCP/IP
    • NetBIOS
    • IPXSPX
  • Network 'switches' are preferred to Network 'hubs' to better accommodate network traffic.
  • Appropriate Connectors for POS and regular peripherals

Other Related Recommendations:

  • Appropriate Anti-Virus protection
  • Appropriate Internet Access
  • Appropriate Backup Provisions
  • The Interbase Server should not generally be running on a Citrix Server.
  • Note that when using Win2003 as the Terminal Server's O/S, please check with Abacus 21 to insure that the relevant POS printer Manufacturers have released drivers compatible with that O/S -- as they have been known to lag.  Terminal-Services and/or Citrix should not utilize Server-2008 as its Server.

Server  top

To run Abacus 21 System 441, server devices must meet the following requirements:

  • Standard file server architecture with a processor speed and memory as required for the Operating System and performance.  (Note Abacus 21 supports both single-core and dual-core Processors -- as will as multi-Processors.  Dual-Core and Multi-Processor configurations require proper version of Interbase -- IB-2009 --for the Database).  See notes below regarding running Abacus 21 (via Interbase SMP-2009) on 32-bit and 64-bit versions of Server-2008).
  • Windows 2000 Server or Windows Server 2003 or 2008 (MicroSoft Small Business Server... except for Clients with Legacy products) for Client-Server environment.  Note:  Server-2008 can not be used as a Citrix or Terminal-Services Server.  Windows NT is no longer supported.  Linux is currently not supported.  Currently, Windows Server 2003 is the recommended overall solution.  (See notes below regarding Interbase SMP-2009 and 32-bit and 64-bit versions of Server-2008.) 
  • To date, Abacus 21 has only limited experience with VMWare (aside from using it in our own internal experimentation purposes from time-to-time)... and that is with a Client that is just getting started up... and, as such, we do not have any "history" of the Abacus software being deployed in high-intensity production environments such as encountered at a Club or Resort.  So, we can not 'sanction' VMWare at the moment... nor do we know that it will not work properly.

  • Available hard disk space (see below).CD-ROM Access.

  • A Network Interface Card (NIC) and TCP/IP Connectivity; 10 Mbps Minimum (100 Mbps or higher suggested).

  • Network 'switches' are preferred to Network 'hubs' to better accommodate network traffic.

  • Available dedicated USB or Parallel Port.

Server Database  top

Abacus 21's System 441 utilizes primarily Borland's Interbase Database Version 7+ -- purchased and configured for the appropriate number of concurrent Users (and 'connects' to the Database -- with four 'connects' possible for each concurrent Simultaneous User license).
 
The current level of Interbase utilized by Abacus 21 is Interbase SMP-2009 (see below).

Comments on other (older) Levels of Interbase are described here:

  • Interbase 6.0
    • Abacus 21 no longer supports Interbase 6 -- and Clients running under it should upgrade to Interbase 7.5 or the newer Interbase 2009 -- which is recommended (See below.)
    • Moreover, the Interbase 6 Installer program may be incompatible with future version of Windows XP -- which, despite prompting for the Windows XP Install CD, allows the User to overwrite a new dll with an older one..
    • If your installation is going to utilize and of Abacus 21's Message Broadcast Services, then a provision needs to be provided for a sufficient number of Interbase User Licenses... and a sufficient number of Database 'connections'.
  • Interbase 7.5 (or an upgrade to Interbase 7.5) is required in the following environments:
    • In order to utilize Abacus 21 Release 52 or Better.
    • If the Client has a hyper-threaded Processor on its Server -- or if the Processor is dual-core. 
    • If the Client has a multi-Processor capable Server and  wants to take advantage of this to improve performance.  (This is an Interbase 7 optional add-on feature.  It is recommended for those installations utilizing Abacus 21's Message Broadcasting System -- or our IP Phone Interfaces.)
    • If the Client has a Win2003 (or better) Operating System on their Server.
    • If the Client's live application database is (or is expected to be) larger than 2GB.
    • If the Client wishes to have the system incorporate improved Backup-Sweep-Restore features.
    • To access to more/better support utilities and support avenues.
    • Interbase 7 and Interbase-2007 also offers an Annual Software Assurance Plan Option -- for Maintenance/Support that includes providing the Client with new Upgrades & New Releases Levels.
    • Interbase 7 and Interbase-2007 has internal features that the Abacus 21 Application Software can and will take advantage of.  These will and are being incorporated into upcoming Releases... and Clients will need to be on these higher Interbase 7 platforms in order to take implement those Abacus 21 Upgrades.
    • Note that Installations that deploy other Vendor products that utilize Interbase must make separate arrangements with those Vendors for their applications' requisite levels of Interbase.  Please note that there may be conflicts between Version Levels of Interbase (used by different Vendors), and it is the Client's sole responsibility to properly segregate these Applications-Databases appropriately from one another to avoid such conflicts.
  • Interbase 2007 (or an upgrade to Interbase 2009) is required in the following environments:
    • If the Server has a Dual-Core (or Multi-Core) Processor -- and can optionally accommodate up to 8-Core Processors.
    • Journaling and Journal Archiving, improves VLDB management, OLTP performance, and facilitates disaster recovery (Server Edition only).
    • Online Dump, provides backup for seamless incremental backup.
    • Batch Updates allow sending multiple SQL statements, reduces the network traffic resulting in improved performance, especially in LAN and WAN environments.
    • Point-in-time-recovery allows Journal-based Recovery based on timestamps for greater recovery flexibility (Server Edition only).
    • Extended International character support via Unicode(r) UCS-2 and UTF-8
  • Interbase Database Licenses (and Connections):
    • Each System requires the Interbase Server Engine (which comes with 1 Client-User License).
    • Additional Licenses (for concurrent Simultaneous Users) are available in the following Client-User count plateaus:
      • Additional single-User Licenses
      • A 10-User Pack
      • A 20-User Pack
      • A 50-User Pack
      • An Unlimited-User Site License
    • Each Client-User License for Interbase comes with four (4) Connections.
      • A typical Abacus 21 System 441 User would require three (3) connects:
        • Two (2) for the main Application System
        • One (1) for Reporting
      • Additional Connections are necessary for each User anticipated to be utilizing (each of) Abacus 21's dynamic-server style of applications -- such as:
        • Phone System Messaging Interface
        • Message Broadcast Center
        • Who's In-House
        • Fingerprint Registration or Fingerprint Recognition
        • ODBC-Transfer Program (for those Clients still with Legacy-441 Hybrid)
        • Any live Abacus-xml program interacting with the Web or other xml-program
        • 3rd-Party Live 3rd-Party Interfaces done via TCP/IP (such as Micros Live Interfaces)
        • Data Analyzers (while done in 'Standalone' mode)
        • Multiple Reports (done simultaneously from a Workstation)
        • During the Running of Scripts
        • During Imports/Exports from/to 3rd-Party System
        • When running System 441 Utilities
        • When conducting a Backup/Restore
        • Etc. (contact Abacus 21 for further details)
    • The multi-processor extension (which is an option for Interbase 7 & Interbase-2007 and Higher) is sold per additional processor.
      • As noted above, this is recommended for those installations utilizing Abacus 21's Message Broadcasting System -- or our IP Phone Interfaces.
      • Moreover, the addition of a 2nd-Processor can dramatically improve system performance.  Interbase offers expansion up to 8-Core Processors.
    • Interbase also has available an optional (Annual) Software Assurance Support-Upgrade program -- which provides for direct (limited) support and future Interbase upgrades at no additional charge beyond the annual fee.
    • The System Administrator should make provisions for an appropriate number of Client-User Licenses and Connections (and perhaps the multi-processor performance enhancer -- and the Support-Upgrade coverage).
  • Note that Abacus 21's Clients who signed up for the System 441 Migration prior to June 2004 had Interbase Version 6 bundled in (Borland's latest version of Interbase -- for the appropriate number of Users as stated in the Migration plan -- unless stated otherwise in the plan agreement).
    • Any Clients with Interbase 6 bundled in (or actually installed) must upgrade-purchase appropriate level of Interbase-2009 in order to take advantage of its features and provisions as noted above.

Interbase (procured via Embarcadero... formerly CodeGear and Borland) Support and Maintenance programs are an integral part of all Interbase products. Interbase customers use maintenance update and upgrade release features to leverage their current technology investments.  Customers also use the technical support features to utilize detailed technical assistance to manage the resolution of all technical issues.  Both features are necessary to ensure that their systems are running at peak performance. Without a current support agreement, you will not be entitled to all technical assistance, online web-access, and software upgrade privileges.

Click here for more information on Delphi & Interbase.

Click here for more information/pricing on Borland's Interbase.

Click here for a partial list of Interbase's world-wide Customers (and testimonials).

Interbase SMP-2009 -

InterBase SMP-2009 is current level of Interbase Database used by Abacus 21.

     (SMP means Symmetric Multi-Processing)

  • New Security and Encryption features
  • Built-in SMP for greater scalability; supports Dual/Quad-Core and additional CPU's
  • High performance durable database solution
  • Powerful, high availability database for embedded and enterprise applications

InterBase Scalable, High-Performance, Durable Architecture - 

SMP support for high performance on multiple CPU systems including Dual/Quad-core CPUs.  InterBase is one of the fastest databases available  and through its built-in SMP (symmetric multiprocessing) it seamlessly scales to multiple CPUs. SMP support is included with no additional licensing required.

InterBase SMP combines performance benefits of a multi-generational architecture with peace of mind of log-based journaling and disaster recovery. Easy installation, small footprint, automatic crash recovery, self-tuning, Unicode, built-in SMP support, SQL 92 compliance, and near zero maintenance makes InterBase SMP the ideal database for embedded and business-critical small-to-medium enterprise server applications.

Interbase-2009 runs on Windows-2000 and Windows-2003 Servers... and can run on 32-bit Windows-2008 (certified)... and can be configured for use with Abacus 21 installations on 64-bit Windows (although not officially sanctioned by Embarcadero... they note it is compatible due to built-in support for 32-bit programs on 64-bit versions of Windows).

    • Embarcadero has indicated that Interbase-2011 SMP (due out in September 2010) will be certified for native 32-bit and 64-bit.
    • Any Client who has a valid Interbase Support-Maintenance Contract is eligible for the upgraded versions of Interbase at no additional charge.
    • Note:  Clients will receive notification via email directly from Embarcadero on these matters... and so it's important you watch for emails from Embarcadero (both inbox and spam) -- and since these notification emails don't come to us, Clients themselves are solely responsible for getting-reading-acting on these emails.

    Journaling -

    Journaling with Write Ahead Logging (WAL) technology improves VLDB management, and facilitates disaster recovery

  • Journals are short lived files that represent all of the changes required to complete all transactions that occur within their checkpoint timeframe. When you turn journaling on, you specify the checkpoint in terms of the number of changed pages and/or the amount of time that has passed, and also a file size (length).

    Journals work like this:

    • Forced writes are turned off to the database file, all writes are now asynchronous
    • Forced writes are turned on to the journals, all writes are now synchronous
    • As the pages are changed, they are written to the journals
    • A separate thread is processing these page updates and applying them to the database in a more efficient manner than normally available (clustering page updates, etc)
    • At Checkpoint, all changes are flushed to the database to ensure consistency in the database file
    • At LENGTH, the journal files roll over to a new file. The old one is kept and reused for the next rollover (it is renamed and overwritten).
    • If the server dies before the journal contents are written to the database file, on startup, a short term recovery is started and the database is bought up to date.

    Journals increase performance as long as they are kept on a different disc from the main database because:

    • The change to delayed writes for the database
    • The greater level of intelligence available to the database when writing pages back to the disc - it is able to amalgamate consecutive pages perhaps from different transactions and write them sequentially
    • All writes to journals are being done sequentially rather than randomly

    Journaling provides a mechanism to increase performance with multiple discs. Journals provide a far greater performance improvement in situations where the database has been put into forced write mode because of reliability concerns. Typically this is done in small organizations where there is no battery backup or RAID set ups. Forced writes operate at ten times slower than delayed writes, thus making journaling an attractive option while retaining the same level of reliability.

    Database and Column-level Encryption - 

    InterBase-2009 now supports the use of either weak (DES) or strong (AES) encryption to encrypt a Database and/or individual columns in a Database table, providing ultimate security for data and communications between Servers and Clients.

    Over-the-Wire (OTW) Network Encryption -

    Typically, data encrypted at the database (or column-level) is not encrypted during the transmission process.  OTW encryption, however, allows us to do just that: encrypt data as it is communicated over a network from a Client to a Server.  With OTW encryption, Abacus 21 can encrypt network transmissions with the same strength as was used to encrypt the database or columns.  You can use weak or strong encryption, though to use strong (AES) encryption, you must obtain an optional strong encryption license, available at no additional charge.

    Encryption of Backup Files -

    When we encrypt a Database and/or any of its columns, we also can encrypt the Backup files for that Database.   Then we decrypt the Backup files during the Restore process.  This adds an additional layer of protection to your data.

    InterBase SMP 2009 To-Go Edition -

    Abacus 21 also offers the new InterBase To-Go Edition -- a small, portable version of the Desktop Edition. Target applications for the To-Go Edition include small devices and public kiosks.  Used in the To-Go edition form, InterBase does not have to be separately installed on any Server or End-User Workstation.

    Journal Archiving provides disaster recovery in the event a database becomes unavailable due to hardware or software failures that may make the primary database permanently inaccessible

    Journals add to the reliability of your system when Journal Archiving is turned on. Journal archives are designed for long term recovery, and when activated do two things:

    • They take a copy of your database as of the time you created the journal archive (a database dump, the same technology that is used for the incremental backups.
    • When a journal hits its length, it is archived instead of being “deleted” (re-used). The journal is copied to the Journal Archive directory.

    Journaling Summary

    By using the new journaling capability, sites that use InterBase can dramatically increase their reliability - even in single server, single disc situations. Journaling is typically considered a VLDB capability, but it need not be.  Even small Servers with the addition of a cheap second disc can achieve dramatically greater reliability for their data where only catastrophic failures (such as destruction of the server) will result in data loss.

    Point-in-Time Recovery -

    Point-in-time-recovery allows journal based recovery based on timestamp for greater recovery flexibility.

    Point-in-time recovery allows you to recover to a specific point in time if you wish - you just specify the time when recovering the database and it will apply all transactions up to that point.

    On-Line Dump -

    On-line Dump provides Backup for seamless incremental Backup.

    The Incremental Backup (on-line dump) feature is a physical backup mechanism. It backs up the physical pages of the database to “dump” files.  The incremental backup feature ensures that the output dump files represent the on-disk state of the database as of the instant the online dump was started, so transaction and page consistency are maintained in the process.

    You can use the incremental backup as a staging area from which a logical GBAK can be performed, so that your production database is not adversely affected.  To do this, send the on-line dump to a remote machine and do the logical GBAK backup on that remote machine. This will also allow you to run a database validation because validation requires exclusive database access, which cannot be obtained on a production database unless that database is shut down.

    Additionally, this feature allows you to create incremental dumps that write only those database pages to the dump files that have been modified since the last time a full/incremental dump was successfully completed. It also provides a means for you to move or copy a multi-file database to a different location. This was not possible previously because there was no way to modify the encoded file names stored on the primary and secondary header pages of the database files.

    Batch Updates -

    Batch Updates allow sending a group of SQL statements, reduces the network traffic resulting in improved performance, especially in LAN and WAN environments

    Batch updates is a new feature in InterBase 2007 which allows you to put a large amount of DML together in one bundle (up to 2 GB) and send it to the InterBase server. The client then gets back an array of responses. The reason this is faster is that there is no back and forth for each statement between the client and the server, and the server is able to “look-ahead” to make better judgments about what the client wishes it to do.

    Additional New Features -

  • Hyper threading support for Intel® Pentium® 4 and Intel Xeon® processors
  • Thread-safe client library-enhanced stability and improved performance for InterBase® clients
  • Multi-generational architecture enables unparalleled concurrency between readers and writers
  • Native multi-threaded server with background garbage collection and multi-user page buffer management
  • Scalability from embedded, single-user applications to enterprise demands
  • Immediate automatic recovery from system failures
  • Garbage collection improves response and throughput
  • Improved memory management allocation algorithms
  • Stored procedure and trigger cache management
  • Sort buffer cache management
  • Thread-private Latch Cache for enhanced SMP scalability

    Interbase Editions -

    • Server Edition
      InterBase SMP 2009 Server Edition features a scalable, portable, cross-platform database, ideal for mission critical enterprise or embedded applications.

      InterBase SMP 2009 Server Edition delivers high performance for applications with complex business logic and high concurrent user levels through its symmetric multiple processing support and multi-threaded architecture.  Built-in SMP allows enterprises greater scalability with support for Dual/Quad-core and additional CPUs built-in, no additional licensing required.  Fast, easy installation, a small footprint, automatic crash recovery, self-tuning, and near-zero maintenance make InterBase SMP the ideal solution for embedded, turn-key applications such as Abacus 21's.  SQL-92 compliance, advanced data reliability and recovery, Unicode, numerous connectivity options, and support for Windows® make InterBase SMP perfect for high-powered, cost-effective business-critical Server application enterprises.

      Desktop Edition
      InterBase SMP 2009 Desktop Edition for Windows is a powerful, cost-effective deployment solution for standalone applications.

      Through its integration with RAD Studio, Delphi®, C++Builder®, 3rdRail, and JBuilder® development tools, InterBase Desktop Edition enables the rapid development of sophisticated business applications.  With a small operational footprint, capabilities for automatic crash recovery and incremental Backup, InterBase SMP Desktop Edition is an ideal embedded database for broad, cost-effective deployments that lack IT support and administration resources.

      To-Go Edition
      The new InterBase SMP To-Go Edition is a completely embeddable, full-featured, zero-administration database that enables ISVs and OEMs to bring their applications and solutions to market faster. The To-Go Edition allows deployment of applications that utilize the InterBase engine DLLs. No separate database server process is running; the database engine is executing in the application process space. InterBase To-Go provides the benefits of InterBase in an extremely small footprint. Available October,2008

      Developer Edition
      InterBase SMP 2009 Developer Edition provides all developers the best cross-platform database to build and test database applications for embedded and SME segments. Developers are free to choose the standard connectivity they want, and make use of a mature SQL92 compliant database for their applications. Database performance monitoring allows the developer to streamline applications for optimal deployment.

    Reasons to Upgrade to Interbase SMP 2009 -

    Durability to protect data and sustain high availability:

    To further improve availability, InterBase® SMP 2007 offers new enhancements for protection against failures and increased disaster recovery options through log-based journaling for short-term recovery, and journal archiving for long-term recovery in the occurrence of hardware system failures. In addition, InterBase SMP 2009 introduces Online Dump of database files and Point-in-Time Recovery from archives.

    The portable, international, cross-platform database allows for growth and flexibility:

    InterBase SMP 2009 Server Edition is certified to run without modification on Windows®, Linux, Solaris™, and Mac OS® X. This enables deployment to a wide variety of platforms without having to rewrite code. The database is fully portable between platforms, and also from InterBase SMP 2007 Desktop Edition to InterBase SMP 2009 Server Edition, allowing for flexible deployment. In addition, InterBase 2007 supports international deployment for international character sets, including the latest Unicode, UTF-8 and UCS2.Framework components as well as other updates and enhanced documentation.

    When performance matters:

    InterBase SMP 2009 is one of the fastest native databases available, and through support for SMP (symmetric multiprocessing) it scales to multiple CPUs, including multi-core CPUs. Performance enhancements and optimizations have been added in a number of areas, such as batch updates, query optimizations, and OLTP improvement via journaling. InterBase implements a multi-generational architecture providing unique versioning capabilities that result in high data availability for transaction processing users and decision support users—simultaneously. Support for multiple simultaneous instances of InterBase on the same machine provides application isolation and load balancing.

    Embed–Deploy–Relax:

    InterBase SMP 2009 combines simple installation and automatic crash recovery, with a self-tuning engine that makes it well suited for embedding. It is ideal for ISVs, OEMs, and VARs who require a database that is very compact in memory and disk size without compromising sophisticated features to support high-powered, business-critical applications. And, unlike many other enterprise databases that require expensive ecosystems of support and maintenance, InterBase SMP 2009 is virtually maintenance free

    Built for Developers:

    Developers using CodeGear RAD Studio, which includes Delphi® and Delphi for .NET, and C++Builder®, as well as JBuilder®, 3rdRail and other tools can leverage a wide range of standard database connectivity options through ODBC, JDBC, ADO.NET, and IBX. Transaction monitoring facilities provide developers with granular database controls for viewing, starting, stopping, and rolling back transactions, processes, and queries. InterBase, compliant with SQL92 standards, offers developers everything they can expect from an SQL database: triggers, stored procedures, and views, as well as advanced concepts such as domains and event alerters.

    Other Related Server Recommendations:

    • Appropriate RAID, Duplex, Mirroring
    • Appropriate Anti-Virus protection
    • Appropriate Internet Access
    • Appropriate Backup Provisions
    • It is recommended that the Server be a 'name brand' (not a 'clone' or 'white box').  This is the foundation of the system and is where you should put your money -- and investment in better performance here translates to better performance thoughout the entire network.
    • The Interbase Server should not generally be run on a Citrix Server.
    • Network 'switches' are preferred to Network 'hubs' to better accommodate network traffic.

    Abacus 21 System 441 in a Multi-Location Environment: top

    Abacus 21 is a totally-integrated system that provides real-time updates between modules and real-time availability of information to Users.  This is typically accomplished by means of a central database where all information is retained.  In a multi-location environment, it may be beneficial to have additional Servers locally residing at the remote site for a variety of purposes -- for printing services, credit card authorization, or for non-Abacus purposes.  But normally the Abacus 21 System 441 database must reside in a single centralized location.

    The remote Workstations will carry their own versions of the programs so that running programs will not create unnecessary network traffic... but they must be able to access the central database through the network.  If for some reason fast network connectivity is not available, then the Workstations can be configured as Thin-Clients by means of Terminal Services or Citrix in order to achieve good system response.  (Of course Thin-Clients are usable in the local environment -- and many Network Administrators prefer this architecture for ease of workstation configuration and support    .)

    In certain multi-Property (or Facility) scenarios that are separate (but related) Business entities, it might be desirable to set up separate 'independent' Servers-Databases -- perhaps tangentially linked to a Corporate Server... but, on these occasions, specialized software is needed from Abacus 21 to 'synchronized' those elements of operation that must "bridge" across boundaries.

    Setup Recommendations: top

    Interbase & Abacus Server Install should not be run on Citrix or Terminal Services Servers used to host System 441 Client.

    • It is common practice to setup Database Servers as dedicated Servers.
    • It is common practice to setup Citrix or Terminal-Services Servers as dedicated Servers for hosting client programs only.
    • This avoids performance & resource conflicts between Remote Users (Client Programs) and Server programs.
    • Having two dedicated Servers also makes Upgrades easier.

    Installation on Drives:

    • Interbase can be installed on the C: drive of Servers -- but Abacus 21 Software should be installed on another drive letter such as D: or E: which is already typical among our Clients.
    • It is common practice that C: drive partitions are rather small compared to other partitions.  This is because C: is expected to have mostly Operating System programs and minimal installations of other critical programs.
    • For the best performance, the System 441 Server should be installed on a separate physical disk from the Operating System.

    Miscellaneous Performance Notes: top

    Servers should have (or be able to accommodate) at least two (or more) physical Processors. (Dual or non-Dual Core).

    • This provides the ability of utilizing additional Processor Licenses for Interbase.
    • This also provides the ability for Abacus Server programs to have their workload distributed among Processors by the Operating System.
    • Servers should have 2GB or more of memory.
      • This allows the possibility of increasing the database memory size to improve performance.
    • Servers should have On-Line battery backup.
      • In case of power failure, this would allow the Server to shutdown properly... and significantly reduce the possibility of Database corruption.
    • The more physical storage drives the Server has the better that Abacus 21 can configure System 441 to improve performance.  (Storage drives can be hard drives, RAID, or Ram Disk, etc...)
      • Installing the System 441 Server on a dedicated storage device will generally enable better performance -- as it would not have to compete with other programs for the same storage device.
        • This should include disabling the virtual memory swap file on the disk where the System 441 Server is installed.
        • Note:  If there is only one physical disk on the Server, then the swap file should not be disabled.

    There are many possible storage configurations that affect performance:

    • A highly performance-efficient hard drive configuration for an Interbase Server could be the following:
      • Dedicated Disk 1 - Server Operating System & Interbase Installation (includes Security Database Access)
      • Dedicated Disk 2 - Server Operating System Swap File
      • Dedicated Disk 3 - Interbase Sort File (perfect for RAM Disk type)
      • Dedicated Disk 4 - System 441 Server Installation & System 441 Database
      • Dedicated Disk 5 - System 441 Server Temporary Files (perfect for RAM Disk type)
      • Dedicated Disk 6 - System 441 Backups (ibk)
    • The 'typical' configuration for an System 441 & Interbase Server is the following:
      • Dedicated Disk 1 - C: drive
        • Server Operating System & Server Operating System Swap File
        • Interbase Installation & Interbase Sort File
      • Dedicated Disk 2 - D: or E: drive
        • System 441 Server Installation & System 441 Database
        • System 441 Server Temporary Files
        • System 441 Backups (ibk)
    • The 'worst' performing hard drive configuration for a System 441 & Interbase Server seems to be the following:
      • Dedicated Disk 1 -
        • Server Operating System & Server Operating System Swap File
        • Interbase Installation & Interbase Sort File
        • System 441 Server Installation & System 441 Database
        • System 441 Server Temporary Files
        • System 441 Backups (ibk)

    Other things that can negatively impact performance:

    • Antivirus scans of Databases or Database Backups as they are being modified.
    • Other d\Database system databases being installed on the same drive as the System 441 Database -- like MSSQL Server.
    • An active Windows swap file on the same drive as the System 441 Database.
    • Disk file fragmentation.

    Disk Space  top

    The Disk Space requirements for Abacus 21 Programs (System 441, with an 'empty' database) are:

    • Server - 200 MB
    • Client - 200 MB (if not a Citrix-TS Workstation)
    One portion of the 'Disk Space' will be occupied by Client's data (for which we have no good way of 'predicting' Transaction Intensity, Image Libraries, History Retention, and Purge Frequency-Depth the Client will desire, encounter, or experience).

    If the Client anticipates an Abacus Application database size exceeding 2GB, then the Harddrive should be formatted as NTFS rather than FAT32.
    The other portion of the 'Disk Space' will be occupied by whatever else the Client has on the Server or Workstations -- in terms of Operating System related things, Utilities, Office Automation software, Interfaces, 3rd-Party programs (and all their associated data -- and 'traffic').

    The Client needs to make their own determination of their overall Installation disk space requirements.
    A 'typical' installation would have a  40GB Server.  A 'large' Client Database may grow to 8GB (and beyond).  Note that this is typical of the network system configurations appropriate for Abacus 21 Application software.  It does not necessarily accommodate the Client's non-Abacus computing requirements. 

    Report Printers  top

    Although Abacus 21 does not provide nor endorse any particular Laser Printers, we have found the following to work particularly well:

    • Konica Multi-Function Printers for Statements and Heavy-Duty Printing
    • For standard 'workhorse' printers, most LaserJet printers will work properly if they support PCL 5 code.
      • One exception to this is the HP LaserJet 1000 -- which does not appear to properly handle the coding for A/R Statements, A/P Checks, and other 'custom' reports or forms.
      • Some of the Printers that do have better success are LaserJet 1200, LaserJet 4000 series, and LaserJet 4200 series.
      • Older models that (typically) do satisfactory printing are the LaserJet 4, 5, and 6 series.
    • For lighter print loads, the DeskJet 900 series, DeskJet 1200 series, and DeskJet 1700 series have been found to perfom well.

    The most important factors to consider when selecting a Printer for compatibility with Abacus 21 applications are that they support PCL 5, 16.67 Pitch, and 66 Lines-per-Page.  (Note that Ink-Jet printers do not support PCL code -- nor do they naturally support BarCode fonts.)

    • For those Clients still using Abacus 21's Legacy System (as opposed to System 441), Printers that supports PCL 5 generally will work in Abacus 21's Legacy System -- but Printers that support only PCL 6 seem to have some problems (at least with printing Statements and Checks).

    If you are still unsure of the compatibilty of a Printer, you can make arrangements to ship it to Abacus 21 for testing (Hardware testing fees apply).  If you are intending to buy a new Printer, we suggest that you make an arrangement with your Hardware provider to 'return' a newly-purchased Printer that turns out not to work.

    Abacus 21 no longer supports the older-style 'band' printers.  Also, continuous-form Dot-Matrix Report printers are not supported.  (Contact Abacus 21 for further details.)

     
    • It is an unfortunate fact of technical life when dealing with Point-of-Sale, Inventory, and other Peripheral Devices -- such as Touch Screens, Touch PC's, Receipt-Ticket Printers (including associated Cash Drawers and portable ones), Prep Printers, Handheld POS Units, PDA's, BarCode Printers, BarCode Portable Scanner-Recorders, RF-Devices, Magnetic Stripe Readers, Fingerprint Scanners, Signature Capture devices, Photo ID & Gift Card & Wrist Band Printers/Encoders, Customer Displays-Kiosks, Weigh Scales, etc. -- that these Devices sometimes behave dramatically different from brand-to-brand and model-to-model... and sometimes differently between Parallel vs. Serial vs. USB vs. Ethernet... ... and sometimes differently with respect to Workstation or Server Operating Systems (including Terminal Services situations) ... and then sometimes differently because of different 'manufacture date' production runs .
    • Moreover, Abacus 21 Applications that utilize these devices are sophisticated and intertwined.... consequently we must be extremely careful which exact combination of peripherals involved in an Installation and the software-hardware-driver configuration thereof in order to insure that all aspects of the system will perform appropriately.
    • Abacus 21 will not guarantee system performance with these types of Peripherals that are not purchased from Abacus 21.  Any diagnosis, research, repair, system reconfiguration or data correction activities associated with resolving issues associated with this topic will be handled on an 'as able to' basis for a fee of $150 per hour.
    • Existing (or Client-procured) peripherals of this nature must meet Abacus 21 compatibility specifications.  With prior agreement with a Client, these units may need to be tested at Abacus 21's Buffalo Office (currently priced at $150 per hour) in order to confirm initial compliance.  These items may need to be sent to the Buffalo Office at least 30 days prior to the anticipated go-live Date.
    Policy & Procedures on Testing and Approving these Devices:
      • The pertinent Abacus applications that might be able to utilize these  Devices have a wide variety of  of Application Software functionality, Software-Hardware Driver pairings, and Hardware Setting configuration settings... and all permutations of them need to be checked out.
      • The Software-Device Driver sets and our internal Software logic/settings need to be aligned properly for the Device to operate appropriately -- and making the Device behave properly may involve new programming (or Driver development) and testing on our side.

    As our Contracts state, Abacus 21 does not guarantee the performance of any Printers (or other POS devices) -- either initially, or in future Release levels -- that are not purchased thru Abacus 21 (and hence 'certified')... for the above types of reasons.... and because Abacus 21 has leverage with its suppliers/manufactures for those hardware or software components purchased via Abacus 21 to have them assist us and the Client in the diagnosis and rectification of any problems that crop up.

    That said, Abacus 21 does offer a service to test and certify these types of Peripheral Devices (for Applicational suitability) upon Client request:
      • The Client purchases one of the 'previously un-certified' Devices (perhaps via Abacus 21) and has it to Abacus 21.
      • Abacus 21 would spend up to 2-Hours doing some initial tests ($300) on it... and let you know the results at that point.
      • If the tests on the Device are "unsatisfactory" we would ask you if you would like us to 'continue to try to get it to work' or 'bail'.
      • If the tests are "successful", then we offer the Client two choices:
        • Have the Device shipped back to the Client... with the Device being declared 'certified' for Abacus 21's current Release (only).  Client pays Shipping-Insurance costs.
        • Leave the device with Abacus 21 perpetually... in which we will insure it is compliant with current and future Releases (assuming the Client does not change the operating environment).
    Abacus 21 offers attractive pricing on all of its certified Peripheral 3rd-Party products... and you are welcome to contact us for an updated Quotation.
    • Abacus 21 Hardware Peripheral prices include all the appropriate Operating System and Abacus 21 Application Software device Drivers.  Use of 3rd-Party products may require acquisition-configuration of the requisite Abacus 21 Drivers.
    General  top

    Abacus 21 does not provide Networks, Network Software, Cabling, Servers, normal (non-POS) PC's, Workstations, and associated installation, training, support, or disaster protection services.  Abacus 21 only supplies POS (and related) peripherals and other specialized Hardware (such as Photo ID Card Printers and Electronic Document Capture devices).  It is suggested that the Client contact a reputable local provider for Network and related Hardware, Software, Disaster Recovery and other Services.  Abacus 21 would be more than glad to work with you and your local Vendor on ascertaining the appopriate configuration.
    It is the Client's responsibility to physically connect any of these Devices onto the Network... and to make them 'visible' as normal Windows devices.

    Note that for those Devices and Operating Systems and Network Configurations that are originally Abacus 21 'certified', Abacus 21 will continue to guarantee their applicational functionality performance of the Peripheral Devices and PC's as long as the software-hardware-operating-technical environment in which they are placed does not change... and as long as new developments in Operating System or Hardware architecture do not obsolete the devices and as long as the respective Manufacturers of these Devices provide Drivers for new Operating Systems or PC's.

    In certain instances, Abacus 21 may take advantage of newer technologies to enable certain new features that the older Peripherals may not be able to accommodate.  However, Abacus 21 will maintain the performance integrity of prior Feature functionality that was facilitated by any respective Device in accordance with the caveats stated above.

    Note that your implementation of Anti-Virus software should be configured so as not to 'interfere' with other auto-pilot upgrades, critical backup, background processing, interface, and other System 441 application software performance.

    Virus Scanner software (like McAfee Anti-Virus) can conflict by scanning temporary files as System 441 is starting up or being Backed-Up.  Apparently the virus scanner locks the files it was scanning (and not letting them go fast enough) thus preventing them from being updated.  This can be avoided by excluding a directory of Abacus-related files from the scan.

    • 'Interference' can arise from the AV program's mis-interpreting one of Abacus 21's files as being bad and inactivating it -- or the AV program could be taking too long to scan files, thereby slowing down the system.

    • Anti-virus should be told to ignore the *.ib files:

      • Since these database files change frequently they may be subject to more frequent scans.

      • Scanning while the database is in operation may cause interference.

      • Abacus 21 has noticed an improvement in performance when we told AV to ignore the database (*.ib) and database backup (*.ibk) files.

    For further System 441 Requirements for operation, click here.

    The suggested minimum requirements guidelines expressed above are merely intended to be generic -- and may vary based on the Client's own particular general environment, overall computing needs, and specific combination of Abacus 21 applications & devices.

    Existing Legacy System Clients, please click Here for other Network & O/S Considerations.  (Note that Abacus 21 has dis-continued support of the Comet-based system.)

    top

    •  
    All material ©2010 Abacus 21, Inc. All Rights Reserved.