Development Budget Install Guide

Version: 2.5 Doc. Version: 1.1 Rev. Date: 29/10/08 ARGUS Development Budget Installation Guide
ARGUS Software: ARGUS Development Budget Installation Guide
The contents of this document are considered proprietary by ARGUS Software, the information
enclosed and any portion thereof may not be utilised for any purpose other than the consideration of
ARGUS Software. Information in this document is subject to change without notice and represents no
commitment on the part of ARGUS Software.
Copyright © 2008 ARGUS Software, Inc. All rights reserved.
Trademarks
ARGUS Software™ is a trademark of ARGUS Software. All other trademarks and registered
trademarks are property of their respective companies and should be treated as such.
ARGUS Developer was formerly known as CircleDeveloper.
ARGUS Development Budget was formerly known as CircleBudget.
Disclaimer
This manual has been prepared for use by ARGUS Software personnel, licensees and customers.
ARGUS Software reserves the right to make changes without notice at any time to this document, and
shall not be held legally responsible for any typographical, arithmetic and listing errors.
Build date: 29 October 2008 2:44 pm

CONTENTSi
Chapter 2
Typical examples of memory, processor, disk and WAN usage . . . . . . . . . . . . . . . . . . . . . 4
Compatibility with Citrix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Installing the software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Local Standalone installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Local Workstation installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Network Server installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Network Client installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Chapter 3
Changing the number of users on your licence . . . . . . . . . . . . . . . . . . . . . . . . 47
Chapter 5
Middleware configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
File format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
Connection strings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
CONTENTS ii
Connecting to an SQL Server database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
Connecting to an Oracle database . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
Important notes about Oracle client PCs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
Upgrading your database. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
Chapter 6
CHAPTER 1
Introduction
Welcome to ARGUS Development Budget - congratulations for buying the world’s premier
software for budgeting and analysis in the property and real estate business.
ARGUS Development Budget is budgeting and analysis software for working on portfolios of
projects.
ARGUS Development Budget contains many options and features enabling a wide variety of
customs and traditions to be employed as used in the global real estate market.
The heart of the system is a database providing capacity for large amounts of data without specific
limit. A choice of SQL Server and Oracle databases offers flexibility for the user. The addition of
several import and export options further extend data storage and retrieval.
About this manual
This booklet is provided as an installation guide to enable you to get Development Budget up and
running.
The installation, use and application of the software is subject to the Terms and Conditions set out
in the licence agreement, and opening the package constitutes acceptance of these terms. The
licence agreement can be found in the program installation folder after you have performed an
installation (PDF file). It is important to note that demonstration versions of the programs may not
be used for actual business or financial gain, and the user is deemed to agree that the intended use
of the software is for evaluation purposes only.
For further information about licensing, installation and use of the software, please contact ARGUS
Software. See “Contact details” on page 61.
Further documentation about this product
In addition to this booklet, you will find full documentation in Acrobat PDF format, which is
installed alongside Development Budget in the program folder.
This includes the following documents:
• DevelopmentBudgetInstallGuide.pdf - This installation guide in PDF format.
• DevelopmentBudgetUserManual.pdf - This is the main user guide, containing in-depth details

ARGUS Development Budget version 2.5 Installation Guide
CHAPTER 2
Setting Up
The purpose of this chapter is to walk you through the steps of the installation and activation
processes.
Before installation
To install and run ARGUS Development Budget, you will need to satisfy the following installation
prerequisites:
• A version of Microsoft Windows that will support .NET;
• Microsoft .NET Framework 2.0 - this will be installed for you if you do not already have it;
• For multiuser installations, a database system such as Oracle 8i (or later version) or SQL Server
2000/2005 is required.
For standalone installations, you can use the SQL Server 2005 Express database provided by
default in the standalone installation (see “Local Standalone installation” on page 10).
Note: If you are using Oracle, please note that the Oracle client program is NOT required on
client or workstation PCs.
Only the Oracle Data Provider for .NET 2.0 is required from the Oracle Data Access
Components v10.2.0.2.21 (this item can be downloaded from Oracle’s website).
You must install this component on all client or workstation PCs before installing
Development Budget (note also that the .NET Framework 2.0 MUST be installed before
installing the Oracle Data Provider for .NET 2.0). When installing the Oracle Data Provider,
select only the Oracle Data Provider for .NET 2.0 10.2.0.2.20 option.
You must note that while versions of Oracle 8i and above are supported for server
installation, only the Oracle Data Provider in the Oracle Data Access Components
v10.2.0.2.21 (and higher versions) are supported for client and workstation PCs.
Development Budget system requirements
The following are the minimum system and product requirements for ARGUS Development
Budget:
• Microsoft Windows XP (service pack 2), Windows 2000 (Service Pack 4) or Windows Vista;
• A minimum of 512 MB RAM (1 GB is recommended);
• Approximately 300 MB free hard disk space for the application plus extra for your data (1 GB
recommended for initial use);
• At least 1024 x 768 high colour (16-bit) display screen resolution.
Warning: Please note that ARGUS Software is unable to support programs running on
Windows 95 or 98.
Typical examples of memory, processor, disk and
WAN usage The following information gives some typical observed examples of memory, processor and disk
requirements on Windows XP in different usage scenarios:
Memory usage
Typical memory usage for Development Budget is 300 MB, for a typical customer with 400
worksheet cost codes, and a 12 month budgeting period.
Application data disk usage
The following information outlines the typical disk usage for your application data.
Note: This is in addition to the 300 MB disk space (mentioned in the system requirements
section above) required for installation of the application.
Development Budget creates a folder in the application data folder (typically in Documents and
Settings\All Users\Application Data, but this depends on your particular setup).
The size of this folder’s contents depends on the type of installation you have:
• Standalone installation: The size of the folder depends on how much data is entered into
Development Budget – the Development Budget database is stored here.
• Workstation installation: Typically less than 10 MB.
• Client installation: 0 MB.
• Server installation: Typically less than 30 MB.
System administrators should note that there are some log files in the application data folder
(typically in Documents and Settings\All Users\Application Data, but this
depends on your particular setup) that may need to be deleted occasionally if they grow too large.
Processor usage
Processor usage is generally modest, with occasional peaks when a worksheet is opened. Due to the
variable nature of processor usage during program operation, no specific measurement can be
provided.
Application hosting over a WAN environment (such as Citrix or Terminal Services)
Development Budget will run when hosted over an application hosting WAN environment, but
please bear in mind the following:
Disclaimer: Although the application will run successfully over an application hosting WAN
environment, formal testing of the application in such an environment has not been
undertaken. ARGUS Software can take no legal responsibility for any problems that arise
from this use of the application. If issues arise that pertain to your WAN environment, please
refer to that third-party product’s documentation or manufacturer for guidance.
Compatibility with Citrix Because of the complexity of Citrix software and the variety and permutations of network types,
ARGUS is unable to provide support for Citrix or networks. Support concerning the use of working
programs for valuations and appraisals is unaffected by the configuration type.
Development Budget is not certified to work under Citrix. However, many of our clients have
installed and run ARGUS software using Citrix in two main configurations described in greater
detail below:
Creating and maintaining a Citrix network takes a reasonable level of expertise and should only be
undertaken if you have previous experience. Although ARGUS will provide guidance where

What is Citrix?
Citrix software provides users with a means to manage their data and applications across
departments, offices and worldwide sites. Although this can be achieved using more traditional
network configurations, these networks may be restricted by the speed of the network links,
especially where the client computer is communicating with a server in another office or country.
The principle behind Citrix is that the computer processing is done remotely. The application
program is housed on the Citrix server or an optional, linked server with a fast (normally local)
connection with the Citrix server. Since all the “thinking” is done centrally, the client computer
need only send user inputs to the Citrix server and view the results as they appear. The client
computer is not involved in database updates or recalculations, and the speed and dependability of
the link between the client computers and the central servers becomes less critical.
Example: A person is using a client computer and changes some data in an input field. When they
click into another input field, the client computer informs the Citrix server of the change. The
Citrix or application servers then perform various calculations and the resulting picture of the
screen is fed back to the client computer. This picture will show the end result of a calculation.
• Citrix software is normally installed on a server running Microsoft Windows 2000 or 2003
Server.
• The processing is run centrally and the application program may not be able to “see” or use
hardware attached to the client computer such as local hard disks or printers.
• Citrix allows individual applications to be run locally, on the client computer, or remotely as
described above.
Installing to a Linked Server
Install Development Budget to a server linked to the Citrix server. Create a mapped drive on the
Citrix server to the installation folder on the linked server. Then, run the client install on each Citrix
server.
Installing on to the Main Server Running Citrix XP
Install Development Budget onto the Citrix Server and create a mapped drive on all client
computers to the installation folder. Run the client install on each client computer.
Installing the software You must have the .NET framework installed on your computer before you can install
Development Budget. For information about installing .NET, visit the following Web site:
http://www.microsoft.com/downloads/details.aspx?familyid=0856eacb-4362-
4b0d-8edd-aab15c5e04f5&displaylang=en
If you don’t have .NET 2.0, the installation program will install it for you.
To install Development Budget:
Note: Before you install Development Budget, you must ensure that you have the appropriate
Windows access privileges to install new programs. See your system administrator for details
or read the user accounts section of Microsoft’s documentation for your operating system if
you are not sure.
Ensure all applications are closed.
Place the Development Budget CD-ROM in your CD-ROM drive, and pause briefly while the
installation program loads automatically.
Or, if installing a downloaded version of the software, double-click the downloaded Development
Budget file.
Follow the instructions that appear on the screen to help you quickly and easily install the
Development Budget software on your system.
The installation program will open the Development Budget Setup Wizard.
If you currently have versions of Development Budget already installed, you may see a message
like the following:
This gives you the choice of installing a completely new installation, or updating an existing
installation. Select the appropriate option.
If you wish to install a fresh installation (Local Workstation, Network Server or Network
Client), select the Install a new instance of this application option button and follow the
remaining instructions in this section. After this, follow the procedures as described in “Local
Workstation installation” on page 17, “Network Server installation” on page 23 or “Network
Client installation” on page 24.
If you wish to update an existing installation, and more than one is listed, you must select the
correct one. Select the Maintain or update the instance of this application selected below option
button and select the installation you wish to update from the list. From this point onwards, follow

Please wait until you see the following message:
Click on the Next > button to proceed. Please wait until you see the following message:
Select your country of residence
Select the appropriate country of residence from the options presented here. If you are outside the
US, select the “Rest of the world” option.

Click on the Next > button to proceed. Please wait until you see the following message:
Please read the software licence agreement carefully before you proceed. The example shown
above is for a US installation - you may see something different if you are installing a version for a
different country.
If you accept the terms of the licence, click on the I Agree button to proceed. You will be prompted
to choose the type of installation that you require:
Select the appropriate option from the list and click on the Next > button to proceed.
From this point onwards, depending upon which option you selected (either a Standalone,
Workstation, Client or Server installation), you should follow the procedures as mentioned below.
To install a Local Standalone Installation, follow the procedure as described in “Local
Standalone installation” on page 10. This is a full installation of Development Budget, complete
with a local SQL Server 2005 Express database.

To install a Local Workstation installation, follow the procedure as described in “Local
Workstation installation” on page 17. This is a full installation of Development Budget that you
can use as a workstation that will point at a server installation.
To install a Network Client installation, follow the procedure as described in “Network Client
installation” on page 24. A client installation will allow you to install a workstation version of
Development Budget that will point at an installation on a network server.
To install a Network server installation, follow the procedure as described in “Network Server
installation” on page 23.
Local Standalone installation This procedure continues on from the procedure described at the beginning of the “Installing the
software” section. When the installation arrives at a point where you have a choice of “Local
Standalone Installation”, “Local Workstation”, “Network Client” or “Network Server”, select the
“Local Standalone Installation” option:
Click Next > to proceed.
The installation wizard prompts you to enter details of an installation folder for Development
Budget:
Browse to a location where you wish to install Development Budget.
Click on the Next > button to proceed.
The installation program will ask you to specify a location where you would like to store your data
files:

The wizard will display a licence agreement for the SQL Server 2005 Express database:
You must read and agree to the licence agreement before clicking on the Yes button to proceed.
You will be prompted to confirm the settings:

Click on the Next > button to proceed. The installation progress will be displayed:
If you don’t already have .NET 2.0 installed on your PC, the installation program will prompt you
for a response in order to install it:

Click on the Next > button to proceed. The licence agreement will be displayed:
Check the I accept the terms of the License Agreement box and click on the Install > button to
proceed. The .NET framework will be installed.
After the .NET framework has been successfully installed, you should see the following message:
Click on the Finish button to proceed.
The installation program will proceed to install Microsoft Report Viewer and Crystal Reports if
they are not currently installed.

The following screen will be displayed:
This is the installation screen for a local SQL Server 2005 Express setup. The installation progress
will be displayed:
When the installation has finished, you should see the following message:
Click on the Finish button to close down the installation wizard.
You should now proceed to activate Development Budget. See “Activating your Licence” on
page 37 for further details.
The activation program should automatically launch if you left the I would like to launch the
licence program for ARGUS Development Budget check box selected when you clicked on
Finish.
Local Workstation installation This procedure continues on from the procedure described at the beginning of the “Installing the
“Local Workstation” option:
The installation wizard prompts you to enter details of an installation folder for Development
Budget:
Browse to a location where you wish to install Development Budget.

The installation program will ask you to specify a location where you would like to store your data
files:
By default, data files are normally stored in the Data folder in the program installation folder, but
you may wish to specify a separate location because you have more than one copy of Development
Budget installed on one machine, or because you wish to keep your files in a location where they
can be backed up easily. Click on the Browse button to specify a folder.
Note: All users who wish to use the application MUST have read/write permissions for this
folder - if you are the system administrator, you should ensure the appropriate permissions
have been granted to users. The main reason for separating the data from the program files is
simply to enable administrators to grant read/write permissions to the data files, while
leaving the program files protected.
The installation wizard prompts you to select the type of database that you wish to use with
Development Budget:
Select the appropriate option - see “Specifying a database when installing” on page 53 for
information about these options.
Note: If you are installing a Development Budget workstation and using it to connect to an
Oracle server, see the notes regarding the client PCs (“Important notes about Oracle client
PCs” on page 56).
If you selected either of the SQL Server or Oracle options, the installation program will branch off
to allow you to set up database connection information (see “Connecting to an SQL Server
database” on page 53 and “Connecting to an Oracle database” on page 55).

To confirm the installation, click on the Next > button to proceed. The installation will commence,
and the progress will be displayed:


You should now proceed to activate Development Budget. See “Activating your Licence” on
page 37 for further details.
The activation program should automatically launch if you left the I would like to launch the
licence program for ARGUS Development Budget check box selected when you clicked on
Finish.
Network Server installation The installation procedure for a network server is essentially the same as for a full local installation.
Before you proceed with a server installation, you will need to ensure that you have full access
rights to the server.
Warning: Please note that the data folder defaults to the program folder.
Please note also that it must be installed using the same path(s) as it will be run from. For
example, you cannot install the application to c:\program
files\ARGUSDevelopmentBudget and then run the application from
\\10.0.0.3\Applications\ARGUSDevelopmentBudget . If you do not follow this
rule, there will be the following consequences:
• Firstly, if the product is activated immediately after installation, the licence path will not
match the run-time path for clients and the licence will be rejected;
• Secondly, the Data Folder Path entry in the ARGUSDevelopmentBudget.ini file
will potentially refer to an invalid path.
This procedure continues on from the procedure described at the beginning of the “Installing the
“Network Server” option:
From this point on, follow the instructions as described in “Local Workstation installation” on
page 17.
Note: Please bear in mind the information described above when specifying folders.
Important note: You should not attempt to run the server installation directly from the server
machine - the server installation is only intended to be accessed via the use of network clients.
Also, if you try to run the Development Budget server installation remotely (from another

Network Client installation Before you proceed with a client installation, you will need to ensure that you have full access
rights to the installation on the server.
Note: If you are using Oracle, see the notes regarding the client PCs (“Important notes about
Oracle client PCs” on page 56) BEFORE proceeding with this installation.
This procedure continues on from the procedure described at the beginning of the “Installing the
software” section.
When the installation arrives at a point where you have a choice of “Local Standalone
Installation”, “Local Workstation”, “Network Client” or “Network Server”, select the “Network
Client” option:

You will be asked to specify where the full installation is located on the network.
Click on Browse... to browse for the installation folder.
Select the folder and click OK .
Click on Next > to proceed with the installation.

You will be asked to confirm the installation.
Click on Next > to proceed with the installation.
The installation program will proceed with the installation:

This message will not be displayed if you already have this component installed.

If this window appears, you must type in the appropriate response (“Yes” to confirm, or “No” to
decline) and press your Enter key to proceed.

Update installation This is continued from the procedure as described on page 8.
Note: If you are upgrading from an older version, you may also need to upgrade your
database. See “Upgrading your database” on page 57 for details.
If you choose to update an existing installation of Development Budget, you will see a similar
sequence of screens to the following:
Select the installation you wish to update
Select the Maintain or update the instance of this application selected below option button and

Click Next > to proceed. The wizard prepares the setup program:
You should see the following screen:

Click Next > to proceed. You will be prompted to specify your country of residence:
Select the appropriate option and click Next > to proceed. The licence information will be
displayed:
You must read and agree to the licence agreement before clicking on the I Agree button to proceed.
A summary of the upgrade will be displayed:


When this process has finished, you will see the following message:
Maintenance Complete message
Click on Finish to close down the installation program.
You should be able to start up Development Budget without the need to go through the activation
process (your PC already has the licence activation details and settings from the previously-
installed version).
Note: You may also need to upgrade your database. See “Upgrading your database” on page
57 for details.
Uninstalling the Software If you need to uninstall the Development Budget software, you should first ensure that you really
need to uninstall your Development Budget installation before you proceed.
Note: The uninstall process will not remove any existing Development Budget data files.
Select Control Panel | Add/Remove Programs from the Windows Start menu.
Select the appropriate Development Budget installation from the list:

Click on the Remove button and then click on Yes.
The wizard will prepare to perform the procedure:

The following screen will be displayed:
Click on Next > to proceed. You will be prompted to confirm the procedure:
Click on Yes to proceed. The wizard will proceed to uninstall the chosen installation of
Development Budget:

Click on the Finish button to close down the wizard.
Starting Development Budget for the first time You can start Development Budget by double-clicking the ARGUS Development Budget icon
on the desktop, or by browsing to the installation folder and double-clicking on
ARGUSDevelopmentBudget.exe.
When you try to run the program for the first time, you will be prompted to enter an activation code
and serial number. Please see “Activating your Licence” on page 37 for details of how to proceed
with activating your licence.
CHAPTER 3
Activating your Licence
Before you can use your copy of Development Budget, you should have completed a successful
installation, and you should now proceed to activate your licence.
Activation is a necessary stage that you must complete in order for your installation of
Development Budget to be used. The process takes just a few minutes, and can be done via
telephone or an Internet connection.
Activation procedure
When you try to run the program for the first time (by double-clicking on the Development Budget
icon on the Windows desktop), you will be prompted to enter an activation code and serial number.
If you do not have your activation code or serial number, please contact your ARGUS sales
representative or the ARGUS Support line.
Note: If you are setting up Development Budget for use in a client-server configuration over a
network, the licence should be activated from one of the client machines.
Once you have completed the installation of Development Budget and started the program, the
following screen will appear:
Development Budget activation dialog
Type your company name into the Company Name field exactly as it appears in the
correspondence from ARGUS Software.
Enter the Serial Number and Activation Code into the appropriate fields. Take care to enter these
exactly as supplied by ARGUS Software.

Choose the type of activation you wish to use, by selecting either of the Activate through Internet
or Activate by Phone option buttons.
Now, proceed with the activation as described in “Activation by Internet” on page 38 or
“Activation by phone” on page 40.
Activation by Internet To choose this activation method, select the Activate through Internet option button.
If you are not sure whether your PC is currently connected to the Internet, click on the Detect
internet connection status link.
If you are currently connected, a message similar to the following will be displayed:
Displaying your connection status
If you are unable to connect to the Internet, you can choose to activate your licence by phone. See
“Activation by phone” on page 40 for further details.
Click on the OK button to close down the message. You will be returned back to the activation
dialog.

If you are activating your licence through the Internet, the next page will confirm the details of
your licence.
Confirmation of licence
Click on the Next >> button to activate your licence. You will receive a message to confirm that it
has been successfully activated:
Successful activation message
Click on the Finish button to complete the process. You can now proceed to use Development
Budget.
Activation by phone Alternatively, if you are activating your licence by telephone, type in your company name, serial
number and activation code and select the Activate by Phone option button:
Choosing Activate by Phone
Click on the Next >> button to proceed.
The following page will provide information that you will need to give to ARGUS Support to
activate your licence:
Contact ARGUS Support and read out this information

This displays a small dialog which lists the installation number in words - all you need to do is read
this out to ARGUS Support.
Installation number displayed as words
Click on OK to close down this dialog, and click on the Next >> button to proceed.
You will be prompted to type in an Installation Key:
Type in the Installation Key here
ARGUS Support will supply you with an Installation Key, which you must enter in the appropriate
text box. This is a very long alphanumeric string, so take care when typing it in.
Click on the Next >> button to activate your licence. You will receive a message to confirm that it
has been successfully activated:
Successful activation message
Click on the Finish button to complete the process. You can now proceed to use Development
Budget.
CHAPTER 4
Licensing
The licences set out which program modules are active and how many users can access the program
at any one time.
• Licences are effectively the keys used to activate the programs.
• They cannot be copied or “hacked”.
• Licences cannot be restored from backup.
• Licences are delicate and users must follow defined procedures to move licences.
• Corrupted licences cannot be recovered without the assistance of the ARGUS Support service.
Transferring licences
Transferring with Web licensing Licences can be moved/transferred between installations by “checking-in” the licence and then “re-
activating” to a different installation. Please note that an Internet connection is required.
Note: The laptop or other PC must contain a full installation of the Development Budget
program as applicable, before transferring the licence. Ensure that Development Budget is
not currently running before you begin.
There are two main stages required to move a licence from one PC to another:
• Checking-in - see “Checking-in a licence” on page 44;
• Re-activating - “Re-activating the licence on a different computer” on page 46.
Open Windows Explorer and browse to the installation folder. If you don’t know where your
installation folder is, try right-clicking on the program shortcut on your computer desktop.
Select the Properties menu option. This opens the Properties dialog:
Properties dialog
Click on the Shortcut tab. Make a note of the Target. This sets out where the program is installed.
Some versions of Windows provide a Find Target... button which automatically opens Windows
Explorer to the correct folder.
Checking-in a licence
Note: Before you begin, you must ensure that you have an active Internet connection.
Also, you must make a backup of the folder containing your data if you wish to transfer it to
the new computer.
Licence maintenance program
This displays the licence checking-in dialog:
Check-in dialog
Note: Make a note of all the information you see in this dialog - you will need it for re-
activating your licence on the computer to which you are moving the Development Budget
licence. Do not lose this information.
Select the Check in through Internet option, and click on the Next >> button (if you are unable to
connect to the Internet, you can choose to check in your licence by phone - call ARGUS Support
for guidance).
If the check-in was successful, you should see the following message:
Successful check-in

When you are returned back to the Licence Maintenance program, it will now show the program as
unlicensed:
If you have checked-in a licence in order to set up a separate installation (such as on a laptop or a
PC at a separate location), you will need to re-activate the licence on that other computer. See the
next section, “Re-activating the licence on a different computer”.
Re-activating the licence on a different computer
To re-activate the licence after you have checked it in, you will need to perform a new installation
of Development Budget on the computer that you wish to transfer the licence to.
When you have performed the installation according to the instructions detailed in “Local
Workstation installation” on page 17, you will need to activate the software. To activate the
software, follow the procedure as detailed in “Activation procedure” on page 37.
Note: To successfully conclude the activation process, you will need the Company Name,
Serial Number and Activation Code that you noted down when you checked-in your licence.
When you go through the activation procedure, you will be prompted to enter this
information.
After you have re-activated the licence, if you wish to, you can transfer the database file from your

Changing the number of users on your licence To increase the number of users on your Development Budget licence, you will need to do the
following:
First, you will need to purchase the extra licences from ARGUS Software. You will need to
have an Internet connection for the following process.
Contact ARGUS Support for the appropriate licence changes to be made. Once you have been
advised by ARGUS that the extra users have been added to your licence, you can proceed.
Before you start, ensure that you have a functioning Internet connection. Also, ensure that all users
are logged out. To check that all users are currently logged out, browse to your Development
Budget program folder (typically, this is C:\Program Files\ARGUS
Software\ARGUSDevelopmentBudget) and locate the Licence.exe file.
Close down any instances of Development Budget that may be running.
Double-click on this file to open the licence maintenance program:
Licence Maintenance program showing licence currently in use
You will need to contact all users and get them to log out of the application. Once all users have
logged out, you can proceed.
Click on the Refresh... button to update your licence and add the new users.
You will be prompted to proceed:

Start of licence refresh
Click on Next >> to proceed.
You will be asked to confirm if this is the licence that you wish to maintain:
Click on Next >> to proceed.

Licence Maintenance window showing updated “Max Users” field
Close down the licence maintenance program.
You can now use Development Budget with the new user options you have just enabled.
Note: If you encounter any problems or errors when performing changes to your licence, you

CHAPTER 5
Database Configuration
This chapter will require you to have some system administrator and database administrator
knowledge. The purpose of this chapter is to guide you through the setup process if you wish to use
a database engine other than the SQL Server 2005 Express database (this is provided by default for
use in the standalone installations).
The SQL Server 2005 Express database provided with Development Budget is fine for standalone
budget models and for training purposes, but for multi-user purposes, you may wish to use a more
powerful SQL-based server.
For multi-user systems, a database system such as Oracle 8i (or later version) or SQL Server 2000/
2005 is recommended.
Note: SQL Server and Oracle databases must be set up and administered by your IT
department. This demands a level of expertise and should not be attempted without previous
experience. Note also that ARGUS Software does not provide technical support for the
administration of these third-party products.
If you are using Oracle, please see the important notes regarding client PCs (“Important
notes about Oracle client PCs” on page 56).
Choosing the database to connect to
When you start up Development Budget after installation and product activation, you will see a
sign-on screen similar to the following:
Here, you can use the Connect To drop-down to choose the database that you wish to connect to.
If you have more than one database engine configured, the drop-down will list the options available

Middleware configuration Note: You can skip this section if you have gone through the configuration process as
described in “Specifying a database when installing” on page 53.
The Middleware initialisation file The middleware initialisation file contains all the middleware configurations available to the
application. Each middleware configuration allows Development Budget to connect to a single
back-end database and is selected when a user attempts to login.
The middleware initialisation file is stored in the same folder as the main application executable
and has the filename:
ARGUS Development Budget.middleware.ini
If you are the system administrator, you can edit this file to add details of databases that you wish
Development Budget to use.
File format The middleware initialisation file takes the format of a conventional Windows initialisation file. It
must contain one section named “Database” for each configuration defined in the file. For example:
Each section of the ini file must have three values:
Provider
The “Provider” value defines what type of connection to use to connect to the database. The
possible values are:
• OracleODP
• SQLServer
“OracleODP” indicates that an Oracle connection (via Oracle Data Provider) is to be used.
“SQLServer” indicates that a native SQL Server connection is to be used.
Name
The “Name” value defines a unique and meaningful name by which to refer to this configuration.
Connection String
The “Connection String” value defines the connection string used to connect to the database
using the provider specified by the “Provider” value. Details of the connection strings for each
provider type are described in the following section.

Connection strings Note: The connection strings listed here are examples only. As system administrator, you
must use your own knowledge and judgement to create the correct connection strings.
Connection strings for Oracle release 8i and later
Note that this connection string is for use with release 8i and later versions. For earlier versions,
please refer to your database documentation.
Specifying username and password:
Using integrated security:
Security=SSPI;
Id=usr;Password=pwd;
ID=usr;Password=pwd;
Warning: In SQL Server, the connection strings are case sensitive. In addition, you should
also treat the initial catalog name, user name and password as case sensitive.
Specifying a database when installing This is continued from “Full Installation” on page 12.
Note that if you use this procedure when installing Development Budget, you will not need to
manually edit the connection strings as described in the “The Middleware initialisation file” on
page 52.
Connecting to an SQL Server database If you selected the SQL Server option when running the installation program, the following dialog
box will be displayed:
Here, you can enter the appropriate connection information, allowing you to connect to a database.
Type in an IP address or a host name into the Server Instance Name field. If you have more than
one server running, you can add a backslash ( \ ) and the name of the instance at the end of the host
name.
In the Database Name field, type in the name of the database.
In the Title field, you can type in a name for this connection, or you could just leave the default text
in place.
Click on Next > to continue. A message like the following will be displayed:
Click on Yes if you wish to use the login settings already set up within Windows. If you don’t wish
to use these settings, click on No.

Here, you can type in a username and password that will be used for logging in to the database.
Click on Next > to continue.
You will be returned to the installation program (see page 12).
Connecting to an Oracle database Note: See the notes regarding the client PCs (“Important notes about Oracle client PCs” on
page 56).
If you selected the Oracle option when running the installation program, the following dialog box
will be displayed:
Here, you will need to type in a server host name (TNS entry). Contact your Oracle Database

In the Server Host Name field, type in the server host name.
In the Title field, you can type in a name for this connection, or you could just leave the default text
in place.
You will be prompted to enter a username and password:
Type in a username and password that will be used for logging in to the database (this could be
provided to you by your database administrator).
Click on Next > to continue.
You will be returned to the installation program (see page 12).
Important notes about Oracle client PCs Note: If you are using Oracle, please note that the full Oracle client program is NOT required
on client PCs or workstations.
Only the Oracle Data Provider for .NET 2.0 is required from the Oracle Data Access
Components v10.2.0.2.21 (this item can be downloaded from Oracle’s website).
You must install this component on all client or workstation PCs before installing
Development Budget (note also that the .NET Framework 2.0 MUST be installed before
installing the Oracle Data Provider for .NET 2.0).

When installing the Oracle Data Provider, select only the Oracle Data Provider for .NET 2.0
10.2.0.2.20 option (see below):
You must note that while versions of Oracle 8i and above are supported for server
installation, only the Oracle Data Provider in the Oracle Data Access Components
v10.2.0.2.21 (and higher versions) are supported for client PCs and workstations.
Upgrading your database
If you are upgrading your software, you may also need to upgrade your database.
Note: If you have more than one database that requires upgrading, you should repeat this
process for each one. The upgrade process should only need to be performed once for each
database.
On server installations - first, upgrade both server and client installations using the
procedure as described in “Update installation” on page 29. Then, run the upgrade utility
from one of the client installations. You will only need to do this once. For client PCs, you do
not need to perform the upgrade for each client.
On workstation installations - if more than one workstation shares a database, the upgrade
process does not need to be performed for each workstation (just one is required).
To start the upgrade process, click on the Windows Start button and use the Programs | ARGUS
Software | ARGUS Development Budget | Database Upgrade Utility menu choice.
Note that this option is not displayed if you are running a network server version of Development
Budget.

This utility will detect the database(s) that will need upgrading. Select the appropriate database and
click on the Update Database button to proceed.
A message warning you to back up your database before you proceed will be displayed:
If it is necessary to do so, back up your database and click on OK to proceed with the upgrade.
When the database has been successfully upgraded, a message is displayed:
You will also note that a message is displayed stating that a database update is not required:
Click on the Close button to exit from the upgrade utility. You can now proceed to use your
upgraded installation of Development Budget.

SQL scripts provided (administrators only) If you are running Development Budget on SQL Server or Oracle, you will need to set up a schema
and database that can be used to hold your data.
Some SQL scripts have been provided for you in order to help you set up a schema and a basic start
database on SQL Server or Oracle.
Note: These scripts are only of relevance to you if you are the database administrator.
Please refer to the documentation provided with your copy of SQL Server or Oracle to find
out how to run the scripts.
These scripts are held in the SQL Scripts folder in your program installation folder. Typically, the
path might be:
C:\Program Files\ARGUS Software\ARGUS Development Budget\SQL Scripts.
The scripts provided are:
minimal data.
• Microsoft SQL Server_SchemaDefinition.sql - this script sets up an SQL Server
schema for Development Budget.
• Oracle_SchemaDefinition.sql - this script sets up an Oracle schema for Development
Budget.

CHAPTER 6
Contact details
UK contact details:
ARGUS Software (UK)
Fax: +44 (0)020 8959 6079
Support Tel : +44 (0)20 8238 8345
Support email: [email protected]
Info email: [email protected]
US contact details:
Support Tel: +1 888 472 1005
Support Tel: +1 888 472 1005
Support Tel: +1 888 472 1005
Support Tel: +1 888 472 1005
Canada contact details:
ARGUS Software
Sydney NSW
ABO Software
Cape Town
SOUTH AFRICA

Development Budget Install Guide

Documents

Transcript of Development Budget Install Guide