Application Server Installation Guide For AE 11 0
Application Server Installation Guide For AE 11 0
Published by:
ARGUS Software, Inc.
750 Town and Country Blvd
Suite 800
Houston, TX 77024
Telephone (713) 621-4343
Facsimile (713) 621-2787
www.argussoftware.com
Information in this document is subject to change without notice and represents no commitment on the part of
ARGUS Software, Inc.
This document is copyright 2016, ARGUS Software, Inc. All rights reserved. This document is a confidential and
proprietary trade secret of ARGUS Software, made available only under a license agreement and or other
agreements containing obligations of confidentiality.
"ARGUS" and “ARGUS Enterprise” are trademarks of ARGUS Software, Inc. All other trademarks and registered
trademarks are property of their respective companies.
Table of Contents
Introduction........................................................................................................................................................... 1
Purpose ......................................................................................................................................................................1
Introduction
Purpose
This document is intended to facilitate the deployment of ARGUS Enterprise by providing the following:
• An overview of the Windows component service and other components used by ARGUS Enterprise
Application Server
• Step-by-step instructions for installing each of these components, regardless of deployment scale
Note: Pay particular attention to the SQL server requirements if you are performing an
upgrade to an existing database. Modifications to the database structure will cause the
upgrade process to take much longer than normal, especially on large databases.
Desktop Requirements
1. Confirm that your system meets the requirements outlined in the appropriate Small, Medium, or Large
Enterprise Planning guide.
2. You need to have administrator rights to proceed with the installation.
1. Create a Domain Service Account to run the core ARGUS Enterprise services (Application and Processing
Services). It is good practice to set the following:
• Password never expires
• User cannot change password
2. For added security, optionally remove the service account from the domain users group by performing
the following steps:
• Create a domain group (e.g., AE Service Accounts).
• Assign this group to the primary group of the service account.
• Change the service accounts primary group to the new domain group that you created.
• Remove the service account from domain users. This limits the security footprint of the account by
limiting access to other machines in the domain. Thus, if this account becomes compromised, the
exposure is limited.
• Add this new group to the users local group of the service machines.
Note: This account will also be used to run the ARGUS Enterprise SQL Server Reporting Services (SSRS)
component and additional permissions may need to be applied. (See the Reporting section.)
In all cases, the selected service account or service accounts group will need to be added to the “AE Users” role in
the ARGUS Enterprise database order to limit access rights to just those needed by the service.
Note: If you are running windows firewall, ensure that the TCP/IP service ports are opened on the
firewall. You may also need to check any virus scanning software you have installed as some of them have
firewalls as well.
Note: If you are upgrading from an earlier version of ARGUS Enterprise, it should be noted that the
Service Account is no longer required to be part of the Local Admin Group.
2. HTTP/HTTPS protocol:
Either:
• For http run “netsh http add urlacl url=http://+:8103/ user="Domain\Username"”, or for https run
“netsh http add urlacl url=https://+:8103/ user="Domain\Username"” from an administrator
command line. Change the parts in red to match your installation port and service account username
minus the outside quotes.
Or:
• Add the service account to the local administrators. Although this is a simpler solution, consult your
security guidelines before implementing this as this increases the security footprint.
Note: The upgrade of a database to ARGUS Enterprise version 10.5 and subsequent
versions from a pre-10.5 database will require a significantly longer time to accomplish than
previous versions due to some underlying technical changes. Please expect upgrade times
that may last up to several hours for very large databases. Ensure that you have a current
backup before proceeding with an upgrade.
Before executing the database upgrade through the configuration utility or by manually running the upgrade
scripts (See Appendix), ensure that the following steps are taken to prepare and secure the database from
unintended access during the upgrade process.
• Ensure that a database backup has been taken so that the log file is truncated as the log file can grow
very large during the database upgrade. Also, in the unlikely event that a problem is encountered
with the upgrade that cannot be rectified without starting over, the original database can be restored
and the process repeated.
• In order to reduce the size the log file can grow to and potentially fail the upgrade due to disk space
issues, it is recommended you switch the database recovery model from Full Recovery to Bulk
Logged as per the advice in the Configuration Utility Database Upgrade Wizard.
• For an upgrade of a pre-10.5 database, it is recommended you pre-grow the database and log files
prior to the upgrade as the database can grow by as much as 60% due to the need to move data
when making structural changes to the Results Tables necessary in order to enhance performance.
Pre-sizing the files will ensure that there is sufficient disk space and also will be less time consuming
than repeated auto grow extensions of the database. Leave Auto Grow enabled in case the estimated
growth is insufficient.
• CalculatedKPIs
• FinancialLineItems
• FinancialLineItemValues
• KPIItems
• KPIItemValues
• ModeledEntities
• ModeledEntityDetails
• ModeledEntityReportData
• OtherItems
• OtherItemValues
• UKTVAcquisitionCost
• UKTVCapitalExtras
• UKTVGroundLease
• UKTVGroundLeaseRentSlice
• UKTVOperatingExtra
• UKTVProperty
• UKTVPropertyCapitalCosts
• UKTVPropertyRunningYields
• UKTVRevExes
• UKTVTenant
• UKTVTenantRentSlice
IMPORTANT NOTE: It should be noted that this may have an adverse effect on the performance of any Custom
Reporting or data extract that relies on the primary key indexes that were present prior to 10.5 as these indexes
will no longer be present. Those queries are now liable to cause table scans which will perform poorly on large
databases where results records can run into the tens of millions.
It is recommended that custom reports and data extracts be modified to include the Scenario Id as part of the filter
criteria of queries to these tables. If this is not immediately possible, ARGUS Support can provide an optional script
that will create indexes to replicate the old indexes and give similar read performance to that prior to 10.5, with
two significant warnings: This may degrade write performance and will have a big impact on the space taken up by
the database, increasing the size of the data files by as much as 20%.
For these reasons, it is recommended that queries be modified to include ScenarioId rather than apply this script.
If it proves necessary to apply the indexes as an interim fix to the system, ARGUS Support can also provide a script
to remove the indexes once all custom modifications have been made.
Note: If your enterprise will be exporting and importing models to and from ARGUS Valuation DCF, additional
security might need to be granted to the APLW com object in the Distributed Component Object Model (DCOM)
Config section of Component Services. If the service account used as the login for the Application and Process
services is not a local administrator on the server, then that account needs to be granted Launch and Activation
permissions and Access permissions.
Note: When importing a .sf file on a machine that contains the Application Service and/or the Process Service and
the database, the service(s) will need to logon using a local machine account or a domain account
(recommended.) Be aware that the use of NT Authority\Local Service will not work in this scenario.
In Place Updates
In Place Updates for Service Packs – For 11.0.0 and Forward
Starting with 11.0.2, you can use In Place Updates to install service packs for the same major/minor version
without having to check in your license or uninstall the previous version. In Place Updates for Service Packs cannot
be used for install versions prior to 11.0.0 or to upgrade to minor/major release versions. For example, you can use
In Place Updates to install AE 11.0.2 over a previously installed 11.0.1, but you cannot use In Place Updates to
upgrade from 10.6.0 to 11.0.0.
Expired Licenses
If your license is expired, the Installer allows you to use In Place Updates to install a new service pack; however,
ARGUS Enterprise will not allow you access until you renew your license subscription with a new expiration date.
Installation Instructions
Use this procedure to install a new service pack using In Place Updates:
Online
Visit our support page at https://argussoftware.com/customersupport.
By Telephone
Support Hours of Operation
Americas
Europe
Middle East/Africa:
Asia/Pacific
Application Services
Application services represent the principal business logic layer for the ARGUS Enterprise Solution. Requests from
the ARGUS Enterprise client application and Excel Add-in component are handled by the application service.
Typically, a single application service is deployed, but the solution can be scaled by deploying multiple application
services behind a load balancer. The subject of load balancing is outside the scope of this document.
Process Service
The ARGUS Enterprise Process Service operates as the bulk data management and manipulation component of the
application. The process service manages communication between the business logic layer and the database. The
solution can be scaled by deploying multiple process services, each requiring its own server.
The ARGUS Database Server may follow two paths for installation: Standalone or Cluster. The appropriate path for
your installation varies based on your organization’s needs and the scale of your deployment. See the three
documents for Large, Medium, and Small Enterprise Planning for more information on how to select the most
appropriate installation path for your deployment of ARGUS Enterprise.
System Requirements
Before installing the ARGUS Enterprise core business services, the installation of the ARGUS Enterprise Database
Server should be completed and verified. Please refer to the ARGUS Enterprise Server System Requirements to
determine the hardware and software requirements that match the scale of your deployment.
Installed Components
Upon successful completion of the tasks described in this document, the following components will be installed:
• Run: Choose Run to run the installation program if it is located on a local network.
• Save: Choose Save if the installation program is being downloaded from the ARGUS support site.
Remember to note the file location for future reference.
3. Navigate to the location of the installation program and double click the file to launch the installer. Click
Run. The installer launches automatically.
4. Click Next to launch the Setup Wizard.
5. The system displays which components need to be installed and which ones (if any) are already installed.
The installation program automatically detects whether your computer has Microsoft .NET Framework
Version 4.0 installed. If it is not found, the installation program launches the Microsoft .NET installation.
Click Accept to install Microsoft .NET Framework Version 4.0 and follow the instructions on-screen.
6. Read and accept the End-User License Agreement. Click Next to continue.
7. Select which type of ARGUS Enterprise Installation will be performed. When you click the icon, the setup
automatically continues. For a single server installation, select the Server Installation option to
automatically install all three services (application services, process services, and data integration
services).
8. To change the default installation folder, enter the name of the new folder, or click Change to browse for
another folder. Click Next to proceed.
9. Click Install to install the software or click Back to review or change settings.
10. The Setup Wizard displays a status bar to indicate progress installing the program. If prompted by
Windows User Account Control (UAC), click Yes to allow the program to make changes to this computer.
Note: If upgrading from an earlier release of ARGUS Enterprise, the system displays the database
selection screen. Select the database server with your prior version ADW database.
12. This screen does not appear if you are installing to a server that has never had any version of ARGUS
Enterprise. Click OK.
13. The ARGUS Enterprise Configuration Utility runs automatically to configure Services and the ARGUS Data
Warehouse database.
14. For each machine on which you have installed a service, set the connection strings for any installed
service by clicking AE 11.0 Database. For example, if the services are installed on only one machine, click
AE 11.0 Database and runs the Database Wizard once. If the services are installed on three machines, you
will need to repeat this process once for each machine. If this is the first service you are configuring, AE
11.0 Database installs or upgrades your existing prior version database. Refer to the Configuration
Utility>AE 11.0 section.
• Run: Choose Run to run the installation program if it is located on a local network. If you select this
option, continue with Step 2.
• Save: Choose Save if the installation program is being downloaded from the ARGUS support site.
Remember to note the file location for future reference.
3. Navigate to the location of the installation program and double click the file to launch the installer. Click
Run. The installer launches automatically. Click Next to launch the Setup Wizard.
4. The installation program automatically detects whether your computer has Microsoft .NET Framework
Version 4.0 installed. If it is not found, the installation program launches the Microsoft .NET installation.
Click Accept to install Microsoft .NET Framework Version 4.0 and then follow the instructions on-screen.
5. Click Next.
7. Select Custom Installation to install the server components. When you click the item, the setup
automatically continues to the next step.
8. The Custom Setup window allows you to choose specific software components and a location for
installation. Select only the ARGUS Enterprise server you wish to install (e.g.., the application service, the
process service, the data integration service). Click Browse to change the installation path or to install one
or more of the services on a different drive. To remove a component from installation, de-select the
component. Click Next.
Note: Some Administrators also install clients (e.g., Excel4ADW, Enterprise Client) if they want to test
directly on this same server. This is recommended.
9. Click Install to begin the installation of the software, or click Back to review or change your settings.
11. If upgrading from an earlier release of ARGUS Enterprise, the system displays the database selection
screen. Select the database server with your prior version ADW database. Click OK. This screen does not
appear if you are installing to a server that has never had any version of ARGUS Enterprise.
12. Once the installation is complete, the system displays the above screen. Click Finish.
13. The system displays the ARGUS Enterprise 11.0 Configuration screen. For each machine on which you
have installed a service, set the connection strings for any installed service by clicking Database Wizard in
the AE 11.0 Database page selector.
Note: If this is the first service you are configuring, Update or Change Database installs or upgrades
your existing prior version database. Refer to the Configuration Utility>AE 11.0 section.
Configuration Tool
System
The System option enables you to create and save a Diagnostics system report that contains the configuration of
ARGUS Enterprise 11.0 along with basic information about your operating system (no persona information is
included).
This report may help ARGUS Software support to assist you with any issue you encounter.
Diagnostics
Click Diagnostics Report and select an option from the pick list. You may choose from the following options:
• Copy to Clipboard
• Save to File
System Health
Read any error or warning messages in this section. On the right side of the window, you can click on any of the
Click here to fix hypertext links to launch the Data Service for each issue. Click Refresh to refresh the window.
AE 11.0 Database
The AE 11.0 Database option enables you to manually launch the Database Wizard. The SQL Server Instance
options can be updated or changed as often as necessary by clicking Database Wizard.
Read any error or warning messages in the Status section. You can also click on any of the Click here to fix
hypertext links to launch the Database Wizard window.
4. If you know your server and database names, enter them in the appropriate fields. Otherwise, you can
search for them in the pick lists. If installed on a cluster, the name of the SQL Server on which the ADW
database is to be installed is the shared Instance Name. Click Next to continue.
• Server: If you know your server and database names, enter them in the appropriate fields. Otherwise,
you can search for them in the pick lists. If installed on a cluster, the name of the SQL Server on which
the ADW database is to be installed is the shared Instance Name.
o Windows Authentication: If this option is selected, the User ID and Password do not have to be
entered.
o SQL Server Authentication: If this option is selected, the appropriate User ID and Password must
be entered.
Note: You should select the Windows Authentication option in most cases. You should only select the
SQL Server Authentication option if you are a database administrator or a person who will be responsible
for making regular user changes and monitoring user access to the ARGUS Enterprise database.
• Database: The name of the ADW Database to be installed on the SQL Server.
5. Upgrading an existing database, the wizard displays both the current and the upgraded database
versions. Click Next to continue.
6. Select Run the database scripts now, and click Next to continue running the scripts. If you wish to inspect
the scripts before applying them to the database, you can select the option Save the scripts so that I can
run them later.
• Run the database scripts now: If this option is selected, the wizard connects to the MS SQL Server
using the user credentials supplied earlier and creates the database immediately.
• Save the scripts so that I can run them later: Refer to the Appendix: Manual Database Upgrade.
Warning: If you have never performed a SQL backup on your database, you will see the following screen.
You may need to perform a SQL backup before proceeding with the database upgrade.
7. After you have backed up your database, select the box next to the message By checking this box you are
agreeing… Click Next to proceed with the database upgrade.
Note: If you choose Run the database scripts now, we recommend performing a transaction log backup
before clicking Next.
If you select Run the database scripts now, you may see the following screen. If you don’t see the
following screen, continue to Step 8. Choose to alter the recovery model automatically to bulk – logged
(recommended) or to ignore the recovery model. Click Next to continue.
Note: If you select bulk-logged recovery mode the wizard will switch back to full recovery on
completion of the upgrade. It is highly recommended that you choose bulk logged mode to reduce the
log file size increase during the upgrade process.
8. The wizard confirms the creation of the new database. Click Finish to close the installer and return to the
Configuration Utility. The ARGUS Enterprise Configuration utility runs automatically to configure Services
and the ARGUS Data Warehouse database. For details on database configuration, see the Configuration
Utility>AE 11.0 section.
1. Click Database Wizard on the right side of the screen to launch the Database Wizard.
4. Enter the names of the existing SQL server and new database. Click Next.
If you know your server and database names, enter them in the appropriate fields. Otherwise, you can
search for them in the pick lists.
6. Select Run the database scripts now, and click Next to continue running the scripts. If you wish to inspect
the scripts before applying them to the database, you can select the option Save the scripts so that I can
run them later.
• Run the database scripts now (recommended): If this option is selected, the wizard connects to the
MS SQL Server using the user credentials supplied earlier and creates the database immediately.
• Save the scripts so that I can run them later: Refer to the Appendix: Manual Database Upgrade.
Note: If you choose Run the database scripts now, we recommend performing a transaction log backup
before clicking Next.
7. Click Next.
8. If you select Run the database scripts now, you may see the following screen. If you don’t see the
following screen, continue to Step 9.
If you do see the following screen choose Alter the recovery model automatically to bulk – logged or
Ignore the recovery model. Click Next to continue.
9. The wizard confirms the creation of the new database. Click Finish to close the installer and return to the
configuration utility. The ARGUS Enterprise Configuration utility runs automatically to configure Services
and the ARGUS Data Warehouse database. For details on database configuration, see the Configuration
Utility>AE 11.0 section.
Reporting
The Reporting option allows you to deploy your reports according to the parameters set in the Report Mode and
Report Location fields.
Deploy to SSRS
You can choose to deploy your reports to an existing Microsoft SSRS instance.
It is assumed that SSRS 2008 (required) or SSRS 2008 R2 (recommended) installation has been completed and
verified.
To best support Repertoire Reporting, SSRS security should be configured in the following manner:
• Use the ARGUS Enterprise Service Account for accessing SSRS Report content via the Connection
String.
• Define an AD group containing all users that will be accessing the content defined in SSRS as a
BROWSER role.
Prerequisites
• Before beginning the installation, ensure MS SQL Server 2008 R2 has been installed.
• If the database server is shared with other applications, database backups should be performed prior
to installing.
• If SSRS is installed on the same cluster as ADW, the SSRS Reports for Repertoire Reporting installation
must be run on each node of the cluster even though SSRS is not cluster-aware.
• If SSRS is running on a remote-hosted instance of SQL Server (different from the instance where ADW
is installed) the SSRS Reports for Repertoire Reporting should be installed on the server hosting SSRS.
33 © 2016 ARGUS Software, Inc.
ARGUS Enterprise Application Server Installation Guide
Deployment Types
The Report Deployment Wizard offers two Deployment Types. You can choose to deploy your reports to either:
Deploy to SSRS
You can choose to deploy your reports to a network.
2. Enter the URL of your SQL Server Reporting Services web service and base folder in the Report Server URL
and Base Folder fields. Click Next to continue.
9. Click Reporting in the left navigation pane to view your report mode and location.
Deploy to Folder
You can choose to deploy your reports to a folder on your local machine or network.
Prerequisites
Before deploying the reports to a folder, the following prerequisites must be met:
• Reports must be deployed to a network share where users have access and full permissions.
• ARGUS Enterprise users must have direct access to the SQL Server.
• ARGUS Enterprise users must have read and write permissions to the ARGUS Enterprise database.
1. In the Configuration tool, click Reporting in the left navigation pane.
2. Click Deploy Reports. The ARGUS Enterprise Report Deployment Wizard starts.
5. The program prompts you to use the pre-selected folder. Click to select a different folder. Click Next
to continue. The Report Deployment Wizard is now ready to deploy your reports.
7. The Report Deployment Wizard has finished deploying your reports. Click Finish to complete this process.
Process Service
The Process Service option allows you access to the ARGUS Enterprise Process Service, which operates as the bulk
data management and manipulation component between the core business services and the database.
You may need to manually configure your services if the account you are using to run them has never been used
for services before.
1. Select ARGUS Enterprise 11.0 Configuration from the ARGUS Software\ARGUS Enterprise 11.0 folder in
the Start>All Programs menu or run the application file ARGUS.ConfigurationUtility.UI.exe in the database
folder from Windows Explorer.
2. Choose Process Service in the left navigation pane.
3. The service account used by the Process Service defaults to LocalSystem. To change the service account,
first click to stop the service. Then click .
4. If the Process Service is currently stopped, choose the hyperlink Click here to fix.
Note: The service account will need to be associated with the AE User role in the ARGUS Enterprise
database in order to limit access rights to just those needed by the service.
7. Click to start the Process Service. The Service Status changes to Running. You can also click to
stop the Process Service
8. Update Simultaneous Tasks on the server dedicated to the Process Service to the number of server
processor cores multiplied by 1.5.
Note: The Performance Settings for Busy Wait Time and Empty Queue Wait Time should only be adjusted
on the advice of the ARGUS Support Team.
Application Service
The Application Service option allows you access to the ARGUS Application Service, which is the principal business
logic layer for handling requests from the Enterprise Client.
You may need to manually configure your services if the account you are using to run them has never been used
for services before. If you have difficulty getting the services to start, consult the Manual Configuration of
Windows Services section.
Note: The Configuration Utility does not have to be run immediately after installation; however, the
system will need to be configured prior to using ARGUS Enterprise.
1. Select ARGUS Enterprise 11.0 Configuration from the ARGUS Software\ARGUS Enterprise 11.0 folder in
the Start > All Programs menu or run the application file ARGUS.ConfigurationUtility.UI.exe in the
database folder from Windows Explorer to display the ARGUS Enterprise 11.0 Configuration screen.
2. Click the Application Service option in the left navigation pane.
3. The Service Account defaults to Local Service. To change the Service Account, first click to stop the
application service.
4. Select an account type for the Service Account. You may choose from the following options:
• Use Default Account: The Account Name and Password are auto populated.
• Use Specific Account: You must enter an Account Name and Password.
5. Enter the Account Name and Password in the appropriate fields. Click OK to finish.
6. In the Network Configuration section, click next to the TCP Endpoint field.
7. Enter the port number in the Port Number field. You may also increment/decrement the number using
the arrows to the right. Click Set Default Port to set your selected port number as the default.
8. Make sure the Enabled option remains selected, so your changes take effect. Click OK when you are
finished.
Note: The service account will need to be associated with the AE User role in the ARGUS Enterprise
database in order to limit access rights to just those needed by the service.
9. Click to start the Application Service. The Service Status changes to Running.
10. Repeat Step 3-8 for the HTTP Endpoint and HTTPS Endpoint fields.
Data Service
The Data Service option provides specialized data integration facilities. It is an optional part of ARGUS Enterprise
11.0 and should only be installed and configured if data integration is required.
You may need to manually configure your services if the account you are using to run them has never been used
for services before. If you have difficulty getting the services to start, consult the Manual Configuration of
Windows Services section.
1. Select ARGUS Enterprise 11.0 Configuration from the ARGUS Software\ARGUS Enterprise 11.0 folder in
the Start > All Programs menu or run the application file ARGUS.ConfigurationUtility.UI.exe in the
database folder from Windows Explorer.
2. Click Data Service in the left navigation pane.
Note: The service account will need to be associated with the AEUser role in the ARGUS Enterprise
database in order to limit access rights to just those needed by the service.
9. Select I accept the terms of the license agreement after you review the Software License Agreement.
10. Click Print to print a copy of the agreement. Access this agreement any time.
11. Click Next to continue.
• Check out my license by telephone – use this option if you do not have an Internet connection.
Refreshing a License
Refreshing your license allows you to retrieve license information from the IBL server and update the license
information saved in the local store. To refresh your license, you need an Internet connection.
Checking In a License
Checking in your license allows you to reuse the license and product key for a version upgrade or reinstall or to use
them on a different computer. To check in your license, you need an Internet connection.
Internet Check In
1. Navigate to Start>All Programs>ARGUS Software>ARGUS Enterprise 11.0>ARGUS Enterprise 11.0
Configuration. Alternatively, you can run the application file ARGUS.ConfigurationUtility.UI.exe in the
database folder from Windows Explorer.
2. Select Licensing in the left navigation pane.
3. Select the license from the right navigation pane.
Phone Check In
1. Select Licensing in the left navigation pane.
2. Select the license you want to check in from the right navigation pane.
3. Click Check In Selected License.
4. Select Check in my licenses by telephone.
5. Click Next to continue.
6. Select your region from Please tell us where you are located.
7. Click Next to continue.
8. Call the number displayed on the Telephone Check In window.
9. Give the ARGUS representative your license key and site code. (These fields are automatically populated).
Enter the authorization code the representative gives you.
10. Click Next to continue.
Removing a License
Removing a license will prevent the license and product key from being used on the current computer. To remove
a license, you need an Internet connection.
To access the Windows Service console, click Start>Control Panel>System and Security>Administrative
Tools>Services. Then right click the server name (e.g., AE 11.0 Application Service), and select Properties.
General Tab
Click General for display information about your service properties. In the AE 11.0 Application Service Properties
(Local Computer) window, the Startup type field is set to Automatic by default. This is the recommended setting
and ensures the ARGUS Enterprise Services come back online whenever the machine is rebooted.
You can click the hypertext link Help me configure service start up options to open the Microsoft Management
Console window for additional information.
Log On Tab
Click Log On to access the account information. You can change the Log on as option by selecting either Local
System account or This account and entering an account and password for the service account.
You can click the hypertext link Help me configure user account log on options to open the Microsoft
Management Console window for additional information.
Note: A domain account with privileges to both the local application server and the ARGUS Enterprise
Database Server is required to run the ARGUS Enterprise Core Services.
Dependencies Tab
1. Click Dependencies to review any system component dependencies that may be associated with the
ARGUS Enterprise 11.0 Application Service.
2. Navigate back to the General tab, and click Start to start the service if it is not already started.
3. Click OK to close the Service Properties window.
4. Repeat these steps for each installed Server:
• AE 11.0 Process Service
• AE 11.0 Data Service (if installed)
1. Navigate to the location of the installation program, and double click the file to launch the installer.
2. Click Next to launch the Setup Wizard.
4. The Custom Setup window allows you to choose specific software components and a location for
installation. Select only the ARGUS Enterprise server you wish to install (e.g., the application service, the
process service, or the data integration service). Click Browse to change the installation path or to install
one or more of the services on a different drive. To remove a component from installation, deselect the
component. Click Next to continue.
Note: Some administrators also install clients (e.g., Excel 4 ADW, Enterprise Client) if they want to test
directly on this same server.
Repair Installation
You can fix missing or corrupt files from the current installation.
1. Navigate to the location of the installation program and double click the file to launch the installer.
2. Click Next to launch the Setup Wizard.
3. Select Repair to alter the way that features are installed. You can also click Back to return to the previous
window or Cancel to stop this process.
4. Wait while the Setup Wizard repairs ARGUS Enterprise 11.0. You can also click Cancel to stop this process.
Remove Installation
You can remove the current installation.
1. Navigate to the location of the installation program and double click the file to launch the installer.
2. Click Next to launch the Setup Wizard.
3. Select Remove to remove ARGUS Enterprise from your computer. You can also click Back to return to the
previous window or Cancel to stop this process.
4. Click Remove to completely remove ARGUS Enterprise 11.0 from your computer. You can also click Back
to return to the previous window or Cancel to stop this process.
AE 11.0 Database
The AE 11.0 Database option enables you to manually launch the Database Wizard. The SQL Server Instance
options can be updated or changed as often as necessary by clicking Database Wizard.
Before you begin: Read any error or warning messages in the Status section. You can also click on any of the Click
here to fix hypertext links to launch the Database Wizard window.
Important note: The upgrade of a database to ARGUS Enterprise version 10.5 and subsequent versions
from a pre-10.5 database will require a significantly longer time to accomplish than previous versions due
to some underlying technical changes. Expect upgrade times that may last up to several hours for very
large databases. Ensure that you have a current backup before proceeding with an upgrade.
• Server: If you know your server and database names, enter them in the appropriate fields. Otherwise,
you can search for them in the pick lists. If installed on a cluster, the name of the SQL Server on which
the ADW database is to be installed is the shared Instance Name.
Note: Only select the SQL Server Authentication option if you are a database administrator or a person
who will be responsible for making regular user changes and monitoring user access to the ARGUS
Enterprise database. Otherwise, select the Windows Authentication option.
• Database: The name of the ADW Database to be installed on the SQL Server.
Warning: If you have never performed a SQL backup on your database, you will see the following screen.
You may need to perform a SQL backup before proceeding with the database upgrade.
9. After you have backed up your database, select the box next to the message By checking this box you are
agreeing…
10. Click Next to generate the scripts.
Note: We recommend performing a transaction log backup before clicking Next whether you choose Run
the database scripts now or Save the scripts so that I can run them later.
11. When you select Save the scripts so that I can run them later… you can save the scripts to a series of files
and run them later using SQL Server management tools. Click Next.
12. Select a directory.
Click OK.
13. Once the directory is selected, the script files are generated and stored in the selected directory.
Result: The wizard confirms the creation of the database Scripts.
Note: Multiple files are created, one for each version of AE from your current version to the version of AE
you are upgrading to. It is essential that the scripts are run in order of the prefix shown by the script
naming convention. A batch file is provided to ensure that you run the scripts in the correct order or you
can manually run each script in order.
14. Click Finish to close the installer and return to the configuration utility.
Warning: Each Script file will have been generated to apply updates to the database specified during the
script generation process. It is important that the scripts only be applied to the originally selected
Database, must only be run once against that database and only if the database is still at the same
version as when the scripts were generated.
---------------------------------------------------------------------
-- ARGUS Database Update Script
---------------------------------------------------------------------
SET NOEXEC OFF;
---------------------------------------------------------------------
-- Setting the database to single user mode before starting modifications.
-- SCRIPT FILE: C:\Program Files (x86)\ARGUS Software\ARGUS Enterprise 11.0\Configuration
Utility\Scripts\ADW_BeforeUpdate.sql
---------------------------------------------------------------------
USE [YOURDATABASENAME]
-- ETC…
Warning: The Scripts are designed to fail in such a way that an upgrade can continue on from the point of
failure once the reason for the failure has been diagnosed and the problem corrected. The Configuration
Utility is designed to continue from the point of failure. HOWEVER, the upgrade scripts generated for
manual execution will not continue on from the point of failure. Should you encounter an error during the
upgrade process, contact ARGUS support to obtain an explanation of the problem and a plan for
continuing the upgrade. Once the problem is resolved, you will need to re-run the Database Upgrade
Wizard inside the Configuration Utility to generate a new set of scripts that will continue the upgrade
from the current point of failure.
Prerequisites
Before executing the scripts manually using the provided batch file, ensure the following steps are taken to
prepare and secure the database from unintended access during the upgrade process.
• Ensure that no ARGUS Enterprise Application Services, Data Services or Process Services are running.
• Ensure that any SYMPHONY servers are shutdown.
• Disable the SSRS server access to the ARGUS Enterprise database.
• Disable any access to the database from custom interfaces, reporting etc…
• Ensure that a database backup has been taken so that the log file is truncated as the log file can grow
very large during the database upgrade. Also, in the unlikely event that a problem is encountered with the
upgrade that cannot be rectified without starting over, the original database can be restored and the
process repeated.
• In order to reduce the size the log file can grow to and potentially fail the upgrade due to disk space
issues, switch the database recovery model from Full Recovery to Bulk Logged. For example:
USE [master]
GO
ALTER DATABASE [YOURDATABASENAME] SET RECOVERY BULK_LOGGED WITH NO_WAIT
GO
• It is recommended you pre-grow the database and log files prior to the upgrade as the database can
grow by as much as 60% due to the need to move data when making structural changes to the Results
Tables necessary in order to enhance performance. Pre-sizing the files will ensure that there is sufficient
disk space and also will be less time consuming than repeated auto grow extensions of the database.
Leave Auto Grow enabled in case the estimated growth is insufficient.
The output will be written to a log file which provides a record of the changes made and can be used to
diagnose any problems that maybe encountered during the upgrade process.
Warning: The Upgrade process may take several hours to complete. If no error messages are encountered
within the log file and the log file is continuing to grow, the upgrade process is proceeding even though
there will be no outward indication of progress. DO NOT interrupt the batch file execution. See below for
a way to check progress.
2. If necessary, you can check the progress of the upgrade from SQL Server Management Studio by running
the following Query against the DbVersion table.
SELECT TOP 1 [Id]
,[VersionMajor]
,[VersionMinor]
,[VersionRevision]
,[VersionIteration]
,[DateAdded]
,[Comments]
,[ComputedVersion]
FROM [YOURDATABASENAME].[dbo].[DbVersion] ORDER BY Id DESC
NOTE: During the current ARGUS Enterprise 10.5 Version upgrade, most of the time will be spent
performing the 100200042 and 100200043 script upgrades, so don’t be surprised if the above query
shows the version to be 100200041 or 100200042 for a considerable amount of time (possible hours if the
results tables contain many millions of records).
When the upgrade batch file has successfully completed, the command window should display the
message All scripts have now completed successfully and the log file should show the message *****
RUNNING 08-END-DBUpgrade.sql *****
3. Run this query to establish that the final database Version has a computed version of 100500042.
Upgrade failures
In the event of an upgrade failure, the following process should be observed:
Warning: The Scripts are designed to fail in such a way that an upgrade can continue on from the point of
failure once the reason for the failure has been diagnosed and the problem corrected. The Configuration
Utility is designed to continue from the point of failure. HOWEVER, the upgrade scripts generated for
manual execution will not continue on from the point of failure. Should you encounter an error during the
upgrade process, Contact ARGUS support to obtain an explanation of the problem and a plan for
continuing the upgrade. Once the problem is resolved, you will need to re-run the Database Upgrade
Wizard inside the Configuration Utility to generate a new set of scripts that will continue the upgrade
from the current point of failure.
GO
GO
3. Proceed with the rest of the ARGUS Enterprise by installing the 11.0 ARGUS Enterprise Services and
Clients.