IT Managers FAQ

  1. What Database Engines Does SuperOffice Support ?
  2. What are the system Requirements of SuperOffice ?
  3. Does SuperOffice offer a web interface ?
  4. Does SuperOffice require a dedicated Machine for the SQL server, and what about security ?
  5. What is the IT departments' involvement in a typical implementation?
  6. What about Support for remote travelers ?
  7. My MS SQL DB transaction log size is running amok, what can I do.

What Database Engines Does SuperOffice Support ?

SuperOffice applications run on IBM DB/2 database (Win, Unix, Linux)

Seamless integration to Lotus Notes and Lotus SmartSuite

Integrates with IBM WepSphere

 SuperOffice applications run on Oracle databases

Integrates with Oracle Financials

 SuperOffice applications run on Microsoft SQL Server database

Seamless integration to Microsoft Office and Exchange

Integrates with Microsoft Business Solutions (Navision)

Back to Top

What Are the System Requirements of SuperOffice ?

The SuperOffice windows client requires Win 98 2nd Ed, Win 2000, or Win XP, with a minimum clock speed of 233 MHz. SuperOffice can run on a Win NT 4, or 2000/3 or with 10 Mbit TCP/IP network with less than 10 ms latency. As for server requirements, ask us, or refer to the technical documentation outlining requirements from the SQL server manufacturer in question:

For Microsoft SQL 2000

For Sybase Adaptive Enterprise Server

For IBM DB 2

Oracle (pending)

 

Back to Top

Does SuperOffice offer a web interface ?

SuperOffice offers both windows and Web client access. A lot of CRM system offers ONLY a web interface, and this IS correct in some cases, but certainly not in ALL cases. The SuperOffice thin client is designed to run inside a web browser. You can also combine the two, having some users access SuperOffice through windows, others through the web, and even have the same user choose between the two.

Click for an general comparison of the pros and cons of running CRM in a windows vs. web based environment

Back to Top

Does SuperOffice require a dedicated Machine for the SQL server, and what about security and back-up ?

In many cases, SuperOffice does not need a dedicated server, even though this will obviously depend on such factors as number of users, size of database, and hardware employed. There is however absolutely no exclusivity requirements inherent in the software as such. We would refer back to the manufacturer of the Database engine(s) that you are considering as to what level of users will have to be reached to require dedicated server(s). As an example, You can support up to around 80 users on a single processor machine, if running MS SQL 2000 Server.

Using Microsoft SQL server as an example, SuperOffice does not require the SA account for either installation or in a production environment. Furthermore, it supports both network, and SQL specific login, and  then be set in accordance with company IT Policy.

Depending upon document management plug in used, all documents created in SuperOffice is contained within one main directory, but with sub directories per user and time frame to ensure easy backup configuration, as well as retirement to secondary backup in accordance with policy.

 Back to Top


What is the IT Departments involvement in a typical implementation ?

Please review Notes on SuperOffice prior installation, for a general review of IT related issues to be addressed prior to install. As a general rule for a 20 user, one site installation with a good network structure, you will not need to set aside more than a half day to assist mainly with access to servers and workstations etc. That being said this is a general observation, and may not apply to you at all; the involvement may substantially change depending upon who will be tasked with administration, and if so, what level of training that may involve, complexity of installation, and ongoing support.

Back to Top

What about support for remote travelers ?

SuperOffice provides support for users on the road, termed SuperOffice Travel. This function comes in two flavors. Standard Travel, and Remote, (aka Asynchronous) travel.

Standard travel is designed for users that spend most of their time in the office, and are on the road for only a short period of time. When leaving for the day, the user will download the database and his documents to the laptop. On the road, he can then make whatever new entries are needed, and when returning to the office, the travel function will carry the changes directly into the main database, log the user on, and he is back on the main database.

SuperOffice Remote travel is designed for users that are out on the road for longer periods of time, users that work from home etc. Remote travel will then, when the user choose to connect to the network, create a log file of net changes to the database, and the routine will then transfer this log file, that will be read into the main database on scheduled intervals using the SuperOffice travel gateway that runs on the server. The user can also choose what documents to be carried over, if files over a given size is not to be transferred, and what documents created by other users or departments are to be carried over. The remote travel function will require that the main database is available via RAS, or VPN.

You can obtain more information about SuperOffice travel here.


My MS SQL DB transaction log size is running amok, what can I do.

The intent of this FAQ is not to go into depth about MS SQL server. A number of books have been published on this matter. One thing that sometimes comes up is the transaction log file that can grow very fast. In most cases, SuperOffice customers does not need the capability to roll back the database on a transaction level. However, simply deleting the log, is not a wise approach. Read this document to get an overview of how to detach a transaction log.
Back to Top

Information in this document is believed to be correct and current. Please do notify us if your experiences suggest otherwise.
Last Revised: 02/17/06.