client-server model in busy

8/2/2019 Client-Server Model in BUSY

1/5

Busy

Implementation of Client-Server Model in BUSY

Before starting the implementation of Client Server in BUSY, let us first understand working of aBusiness Application (e.g. BUSY) with databases. Any Business Application consists of threemain components:

a) Applicationb) Database Engine (DBE)c) Data Files

Business Application interacts with the DBE for the saving/retrieval/processing of data and theDBE in turn interacts with the Data Files for saving/retrieval of data.

There are primarily two types of database technologies

a) File Serverb) Client Server

In File Server mode, the Application and the DBE resides on the same computer whereas theData Files may reside on the same computer or some other computer. Examples of File ServerDatabase are MS Access, Dbase, Paradox, FoxPro or any other Flat File Database.

In Client Server mode, the DBE and the Data Files resides on the same computer and theApplication may reside on the same computer or some other computer. Examples of ClientServer Databases are MSSQL, Oracle, Informix, Ingress, MYSQL etc.

For avoiding confusion we would be discussing the most common Multi-User case where theApplication and the Data Files resides on different computers. We would be referring thecomputer where the Application is residing as Clientand the computer where the Data Files areresiding as Server.

File-Server ModeGiven below is a pictorial view of a File Server Based Application. Here the Application and theDBE are residing on the Clientand the Data Files are residing on the Server.

BIPL 1

Application

Request Sent Result Sent

Data Processing

DatabaseEngine

Data Files

Client Server


2/5

Busy

Client-Server Mode

Given below is a pictorial view of a Client Server Based Application. Here the Application isresiding on the Clientand DBE and the Data Files are residing on the Server.

Advantages of Client ServerSince the DBE and the Data Files resides on a single computer only, all the data processingtakes place on the Servercomputer only. So first of all it improves the speed of data processingresulting in better application speed. Second in case of network failure between ClientandServer(Which is very common), the data processing does not get affected hence improving the

data integrity and reliability.

After discussing the difference between the Client-Server and the File-Server models, let usdiscuss the Database technologies available in BUSY and implementation of Client-Server inBUSY.

Database Technologies available in BUSYBefore Ver. 3.0(4a), BUSY was based on File Server Technology only (MS Access as BackendDatabase). Now starting from BusyWin 3.0(4a) version we have the option to choose thebackend Database. User can use BUSY either in File Server mode (MS Access Database) orClient Server mode (MSSQL Database).

Different models of BUSYTill now we had 4 models of BUSY software

a) SS (Standard Single-User)b) PS (Professional Single-User)c) SM (Standard Multi-User)d) PM (Professional Multi-User)

All the above four model works in File Server mode (MS Access based). Now we haveintroduced two more models to provide Client Server database capabilities

a) SC (Standard Client-Server)b) PC (Professional Client-Server)

SC would provide the features of Standard Edition in Client Server mode and PC would beproviding features of Professional Edition with Client Server mode.

Client Server would always be Multi-User but unlike SM & PM, where a single dongle is sufficientfor all the computers in a LAN, all the Clientcomputers in Client-Server mode would requireindependent dongle of either SC or PC model.

Maintaining our old tradition, we still have the single BUSY application, which would switch torelevant database mode depending upon the dongle installed on the computer. If no donglewere installed on the computer then the default mode would be File Server mode (MS Access).

BIPL 2

ApplicationRequest Sent

Result Sent

Data Processing

DatabaseEngine

Data Files

Client Server


3/5

Busy

Requirement for Client-Server model

1. Operating System requirement

For Server: Any Server operating system such as Windows Server 2000, Server2003, XP Server and so on which can run MSSQL Server 2000.

For Clients: Windows 98 or any higher version.

2. Software requirement

For Server: MSSQL Server 2000 Database Server

For Clients: BUSY Application, ODBC Connectivity Drivers and SQL Server 2000Client Tools (Although Client Tools are not required for the running of BUSY, thesemay be required for troubleshooting)

After going through the requirements for running Client-Server model, let us now have a look atthe steps to configure Client-Server model.

Steps to Configure Client Server model

On Server1. Install SQL Server 2000 Server Database (Set theAuthentication Mode to Mixed

Mode (SQL Server & Windows) and NOT on Windows Only)2. Register for a new Server through Enterprise Manager. While registering new

Server, you can specify a name to this server. This server name would be requiredwhile specifying Server Information on Clientcomputers.

3. Change the password for the default User SA. This password would again berequired while specifying Server Information on Clientcomputers.

On Client machine

1. If you have SC (Standard Client Server) or PC (Professional Client Server)dongle then BUSY will automatically start in Client Server model.

2. If you do not have a SC or PC dongle then to start the BUSY application in ClientServer model, perform the following steps:

2.1 Create a separate icon of BUSY.

2.2 Right click the BusyWin icon you have created and select the Propertiesoption.

2.3 Click the Shortcut tab and then specify SC or PC as Command LineArgument in the Target field. Given below is a screenshot of Shortcut toBusywin.exe Properties window with Command Line Argument specified init.

BIPL 3


4/5

Busy

After configuring Client-Server model, the next step is to install the ODBC Connectivity Driversin the client computer.

Installing ODBC Connectivity DriversIn Windows 2000 / XP, ODBC Connectivity Drivers are part of the OS itself so there is no needto install them separately. For Windows 98, you need to install ODBC Connectivity Drivers.These drivers are available from Microsoft in the form of MDAC (Microsoft Data AccessComponents) Ver. 2.8. For the convenience of users we have provided these drivers in theBUSY CD (\Drivers folder) itself. MDAC is a single executable file by the name ofmdac_typ.exe.Kindly go to \Drivers\MDAC2.8 folder in BUSY CD and execute mdac_typ.exe file and the ODBC

Connectivity Drivers would be installed in the client computer.

In case of Windows 2000 / XP although it is not required to install these drivers, you may installthem in case of any problem in connectivity of client with the server.

After installing the ODBC Drivers, next step is to specify the Server related information in theBUSY application.

Setting Server InformationWhen you run BUSY on Client-Server mode then instead of CompanySet Data Directory,

CompanySet Server Information option appears in the Companymenu.

Click the Set Server Information option to specify details related to the Server. On clicking the Set Server Information option, a Server Information window appears.

Given here is a screenshot ofServer Information window.

BIPL 4

Command Line

Argument


5/5

Busy

In the Server Information window, there are various data fields. The data fields are:

Database Specify the database name in this data field (Fixed as MSSQL for the timebeing).

Sever Name Specify the Server name in this data field as specified at the time ofregistering a new Server.

User ID Specify a valid MSSQL server User ID in this data field. Default MSSQLServer user name is Sa.

Password Specify password that you have specified for the user name Sa at the timeof registering for a new Server.

This is the only configuration required to run BUSY in Client Server mode. Once thisconfiguration is done, BUSY will work as it is as it works in File server mode (MS Access).

Data Exchange between Client-Server and File-Server modeIf you are working in File-Server mode and want to work in Client-Server mode then BUSYprovides you with the BUSYAcces2SQL utility. This utility will convert the existing data from MSAccess to MSSQL. The process of converting data may take some time depending upon the sizeof the data.

Note: The BUSYAcces2SQL utility is provided in the Add-On & Utilities folder in BUSY CD.

The same process can be reversed also. If you are working in Client-Server mode and want towork in File-Server mode then you can use the same BUSYAccess2SQL utility to convert datafrom MSSQL to MS Access.

BIPL 5

client-server model in busy

Documents