Docstoc

Busy

Document Sample
Busy Powered By Docstoc
					                                                                                        Busy



                    Using BUSY with Remote Server
Remote Server
A Remote server is a computer placed anywhere in the world and any authorised person can
access or use resources of it through Internet connection from any location.

For example, a company has its head office in Delhi and branches all over the country. If the
data entered through all branches needs to be stored/retrieved on the computer placed at
head office directly then the computer at the head office will become the Remote Server for all
other computers lying at different branches. Here the Application Software is installed at the
individual computers in all the braches and the data is being saved centrally at the head office.



                                          Delhi
                                      Remote Server
                         (Data of all the branches get stored here)

         Sending data         Retrieving data    Sending data         Retrieving data

                     Mumbai                                  Kolkata
                   Client machine                        Client machine
                   (Busy installed)                      (Busy installed)




In the above example, benefit of saving data at Remote Server is that all the braches and the
head office are always synchronised and have access to the latest updated data.

BUSY Client Server model can be used easily to save/retrieve your data on any Remote
Server.


Using BUSY Client Server model with Remote Server
The computer from where the Application Software is installed and used is called the Client
Computer and the computer where the data is being saved is called the Server Computer.

    Prerequisite for client and server computer are:

    Server

        1.   Windows Server OS (Recommended Windows 2003 Sever with SP2)
        2.   MSSQL 2000
        3.   Anti Virus Software
        4.   Internet connection with Static IP (Minimum 512 KBPS)

    Client

        1.   Windows 98/2000/XP/2003
        2.   BUSY (Client Server model)
        3.   MDAC 2.8
        4.   Internet Connection (Minimum 256 KBPS)




BIPL                              Accessing BUSY on Remote Server                              1
                                                                                     Busy

   As mentioned above, these are the basic requirements on both the server and the client
   machine by fulfilling which you can run BUSY on a Client computer while saving data on a
   Remote Server. After fulfilling these requirements, follow the steps mentioned below to
   configure and run BUSY with remote server.

   Steps Involved

       1. Set up Server computer (Install Windows Server 2003, MS SQL 2000 and Anti
          Virus Software
       2. Set up Client Computer (Install BUSY and MDAC 2.8)
       3. Configure BUSY to run in Client Server mode
       4. Specify Server details in BUSY (Using Set Server Info option)


Step 1: Set up Server computer

The very first step you have to perform is to make a computer as Server. For this purpose,
you have to install a Windows Server OS in it (We recommend Windows 2003 Server with SP2
as its inbuilt firewall is very strong). After this you have to install MSSQL 2000 and a good
anti virus software on the computer.

Note: For installing SQL Server 2000, you can refer to the ‘Client-Server Model in
BUSY’ document.

You should also make sure that the computer you are setting up as Server should have
Internet connection with static IP Address and a minimum speed of 512 KBPS.



Step 2: Set up Client Computer

The next step is to install BUSY and MDAC 2.8 (MS SQL connectivity drivers) on all the client
machines. BUSY is to be installed in normal mode as we install in non Client Server mode. To
install MDAC 2.8, simply go to the MDAC 2.8 folder and run the Setup.

Note: MDAC 2.8 is available in BUSY CD ‘\Drivers’ folder.

You should also make sure that client machines have Internet connection (Static IP not
required) with minimum speed of 256 KBPS.

Note: Internet connection on both the server and the client machine should be
Broadband/DSL. There should not be any wireless Internet connection either on
client or on server machine.




Step 3: Configure BUSY to run in Client Server mode

Next you have to configure BUSY installed on client machines to be able to run in client server
mode. If you have SC (Standard Client Server) or PC (Professional Client Server) dongle then
BUSY will automatically start in Client Server mode. Otherwise if you do not have a SC or PC
dongle then to start the BUSY application in Client Server mode, perform the following steps:

      Create a separate icon of BUSY.
      Right click the BusyWin icon you have created and select the Properties option.
      Click the Shortcut tab and then specify SC or PC as Command Line Argument in the
       Target field. Given below is a screenshot of Shortcut to Busywin.exe Properties window
       with Command Line Argument specified in it.



BIPL                             Accessing BUSY on Remote Server                             2
                                                                                     Busy



                                                            Command Line
                                                            Argument




In the Target field, some text displaying the path from where this shortcut will be run already
appears. You simply have to write the Command Line Argument ahead of that text. For
example, "C:\BusyWin\BusyWin.exe" is already appearing in the Target field and you want
to run BUSY in Standard Client Server mode. For this you simply have to write "/sc” as
Command Line Argument. The text will then look like “C:\BusyWin\BusyWin.exe /sc”. For
Professional Client Server mode please specify “C:\BusyWin\BusyWin.exe /pc”.



Step4: Specify Server details in BUSY

Once BUSY starts in Client Server mode, you need to specify the Server details (IP Address,
User ID and Password of the SQL Server installed on Remote Server) to access database of
BUSY on a remote server.

To specify Server details on the client machines, perform the following steps:

      Run BUSY in Client-Server mode.
      Click Company menu and then click the Set Server Information option. Given below is
       the screenshot of Company menu.




      On clicking the Set Server Information option, a Server Information window appears.
       Given here is a screenshot of Server Information window.



BIPL                             Accessing BUSY on Remote Server                             3
                                                                                       Busy


                                                                         IP Address of the
                                                                         Remote Server




In the Server Information window, following data fields appear:
       Database – Specify the name of the database in this data field. By default MSSQL
        appears in the data field. This need not be changed.
       Server Name – Specify the IP Address of the remote server in this data field.
       User ID – Specify a valid MSSQL server User ID in this data field. Default MSSQL
        Server user name is sa. If you have created a new user then make sure that the new
        user should have the same rights as user sa.
       Password – Specify password for the user name specified. If you are using the sa user
        then specify the password that you have specified for the user name sa at the time of
        registering for a new Server on the remote server.

After entering the necessary details, click the Save button to save these details.

Now all the steps involved are complete and you can start using BUSY as you would use in non
Client Server mode.


Troubleshooting
While connecting to Remote Server, sometimes some connectivity problems occur. In case, if
you are not able to connect to the Remote Server then you can check for the following details:

    1. Make sure that MDAC 2.8 is loaded on the client machine.
    2. Check whether the internet connectivity has been established to the Remote Server or
       not by using the Ping command explained below. To use the PING command, perform
       the following steps:
                 Go to Start menu  click Run option and type PING with the IP address of
                   the Remote Server followed by „-t‟. Given below is a screenshot of Run
                   option.


                                                                       Ping command with
                                                                       the IP address of the
                                                                       remote server




                   Click the OK button or press Enter key.
                        o On clicking the Ok button, if the connection to the Remote Server
                            has been established then the following screen would appear.




BIPL                              Accessing BUSY on Remote Server                              4
                                                                                   Busy




                      o   If the connection to the Remote Server cannot be established then
                          the following screen will appear:




                In such a case, try the following:
                     Check that the Internet connections are working properly at both Client
                      & Server computers.
                     Temporarily remove anti virus software from Client / Server
                      computers, as sometime the anti virus software or firewalls blocks the
                      connection to the remote server.

   3. Make sure that the firewall installed at your server has allowed incoming SQL
      requests.
   4. Make sure that the User Name specified in Set Server Information should be either sa
      or should have equivalent rights.



                                            ---------xxx--------




BIPL                           Accessing BUSY on Remote Server                             5

				
DOCUMENT INFO
Shared By:
Categories:
Stats:
views:35
posted:6/25/2011
language:English
pages:5