Asta Development. Product Installation Guide

(1)

Asta Development plc Kingston House Goodsons Mews Wellington Street Thame

Oxfordshire OX9 3BX

United Kingdom

Tel: +44 (0)1844 261700 Fax: +44 (0)1844 261314 www.astadev.com [email protected]

Asta

Development

(2)

Trademarks

Asta Powerproject is a registered trademark of Asta Development plc.

iOS is a trademark or registered trademark of Cisco in the United States and other countries.

Android is a trademark of Google Inc.

Microsoft, ActiveX, Active Directory, SQL Server, Terminal Server, Windows and Windows PowerShell are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

Oracle is a registered trademark of Oracle Corporation and/or its affiliates.

Citrix is a registered trademark or trademark of Citrix Systems Inc in the United States and/or other countries.

(3)

1 Overview of this document

This document describes how to install the Asta Powerproject Enterprise system and the following companion products:

• Asta Licence Manager. • Asta Archive Manager.

• Time Sheet for Asta Powerproject. • Web Access for Asta Powerproject. • Site Progress for Asta Powerproject.

• Business Intelligence for Asta Powerproject.

As well as describing the installation process for each product, this document describes any additional steps that you must take in order for the installation to be successful. For example, if you need to create a database to use with the product, this document describes the necessary steps.

This document also describes how to upgrade existing installations of Asta’s software to the latest version and how to move an installation of Asta Powerproject Enterprise from one server machine to another.

1.1 Notes on operating systems and database types

The instructions in this document assume that you are installing Asta Powerproject Enterprise and its companion products onto a server machine that is running the

Microsoft® Windows® 2012 Server operating system and that you are using Microsoft SQL Server® 2012 Express to create and manage your databases. It is possible to use other operating systems and other types of database. Where instructions differ between operating systems, this document outlines the different steps that you must take. If you choose to use a different type of database, you will need to identify and carry out the equivalent steps in the database management application that you are using.

The instructions in this document that involve working with Microsoft SQL Server describe

one possible way of working, not the only way of working. For example, the instructions in sections 2.1, Creating a Microsoft SQL Server database and 2.2, Creating a Microsoft SQL Server database user, describe one possible way of creating a database and a user to administer the database. It is important to note that while these instructions will achieve the desired result, the protocols in place in your own organisation may mean that you will need to follow slightly different procedures. For example, you may want to use an existing user to administer the database, or your Microsoft SQL Server password policies may necessitate a different approach to the one described here.

Before carrying out the steps in this document to install an item of Asta software, refer to the Asta Powerproject Enterprise Overview and System Requirements Guide for details of the hardware and software that must be in place prior to installation. If any of the required software listed in that document is not already installed on the computer on which you want to install an item of Asta software, install it before proceeding with the instructions in this guide.

(8)

(9)

2 Installing the Asta Powerproject Enterprise system

This section of the document describes how to install the Asta Powerproject Enterprise system, including the additional steps that you need to take in order to create a database for use with Asta Powerproject Enterprise.

The installation of the Asta Powerproject Enterprise system comprises the following steps: • Creating a Microsoft SQL Server database.

• Creating a Microsoft SQL Server database user.

• Specifying the Microsoft SQL Server authentication mode. • Installing Asta Powerproject Enterprise.

• Installing the Asta Name Server and the Enterprise server to run as services. • Configuring the Asta Name Server and Enterprise server services.

• Configuring Asta Powerproject Enterprise registry settings. • Installing an Oracle® driver.

• Creating a data source in Asta Serveradmin.

• Configuring Asta Powerproject Enterprise using Asta Serveradmin. • Configuring firewalls to work with Asta Powerproject Enterprise.

2.1 Creating a Microsoft SQL Server database

Before you install the Asta Powerproject Enterprise system, you must create a database in which to store the Asta Powerproject data.

To create a Microsoft SQL Server database:

1. On the server machine on which Microsoft SQL Server is installed, launch the Microsoft SQL Server Management Studio and connect to your server.

2. Within the SQL Server Management Studio, right-click the Databases folder in the Object Explorer and select New Database:

The New Database dialog appears.

3. On the General page of the dialog, in the Database name field, enter a suitable name for the database, as illustrated below:

4. There is no need to change any of the default settings for this database; click OK

(10)

All of your Asta Powerproject Enterprise data will be stored in this database. For this reason, you must ensure that the database is backed up regularly, preferably as part of an automatically-scheduled backup process. Some database backup mechanisms take the database offline temporarily while the backup is in process. If this is the case with your backup mechanism, you must stop the Enterprise server service before the database is taken offline, then restart it once the backup is complete.

By default, Microsoft SQL Server 2012 Express places the database files that must be backed up in the following location:

C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\DATA\ By default, it places backup files in the following location:

C:\Program Files\Microsoft SQL Server\MSSQL11.SQLEXPRESS\MSSQL\BACKUP\

Depending on the type and version of database that you are using, and the way in which the database software has been installed onto your server machine, these locations may be different for you.

2.2 Creating a Microsoft SQL Server database user

Once you have created the Microsoft SQL Server database, you must create a new user to access it.

To create a Microsoft SQL Server user:

1. Within the Microsoft SQL Server Management Studio Object Explorer, expand the Security folder, right-click the Logins folder and select New Login:

The Login – New dialog appears.

2. On the General page of the dialog, in the Login name field, enter a suitable name for the user, for example “Asta”.

3. Click the SQL Server authentication radio button. A number of fields below this radio button become available.

4. Enter a password for the user in the Password field, then re-enter it in the

Confirm password field.

5. Clear the Enforce password policy check box:

(11)

7. In the Select a page section of the dialog, click Server Roles.

8. On the Server Roles page of the dialog, select the bulkadmin check box:

9. In the Select a page section of the dialog, click User Mapping.

10. On the User Mapping page of the dialog, in the Users mapped to this login group, select the check box to the left of the database that you have created:

11. The name of your database should now be appended to the title of the Database role membership role for group. In this group, select the db_owner check box:

12. Click OK.

It is necessary to assign the “bulkadmin” server role to the database user in order to create data sources in Asta Serveradmin that use the “optimise transaction data” facility (see section 2.9, Creating a data source in Asta Serveradmin for details).

If you are using an Oracle database rather than Microsoft SQL Server, you must ensure that you create a database user with sufficient privileges to use the SQL*LOADER database utility. This can be achieved by giving the user the role of “CONNECT (Default)” and “DBA (Admin and default)”.

2.3 Specifying the Microsoft SQL Server authentication mode

In order for Asta Powerproject Enterprise to work with Microsoft SQL Server, you must set the server authentication mode to “SQL Server and Windows Authentication mode”. To set the server authentication mode:

1. At the top of the Microsoft SQL Server Management Studio Object Explorer, right-click the SQL server and select Properties:

(12)

The Server Properties dialog appears.

2. In the Select a page section of the dialog, click Security.

3. On the Security page of the dialog, click the SQL Server and Windows Authentication mode radio button:

4. Click OK.

2.4 Installing Asta Powerproject Enterprise

Now that you have created your database and a user in Microsoft SQL Server, you can install Asta Powerproject Enterprise. You can install Asta Powerproject Enterprise onto the server machine on which your database is located, or onto another server machine. The instructions in this document assume that you are installing it onto the server machine on which your database is located.

The Asta Powerproject Enterprise installation routine installs the following applications: • Asta Enterprise server – an application that controls access to data sources (eg the

database that you created earlier) and enables more than one user to access data sources simultaneously.

• Asta Name Server – an application that holds details of all of the Enterprise servers that are currently running. The name server publishes details of these Enterprise servers to the Asta Powerproject client applications, without the clients having to connect to the servers individually.

• Asta Serveradmin – a server administration utility.

• Controller – an application that you use to operate the Enterprise server using a command prompt.

(13)

All of these applications are available on the Windows Start screen once you have installed Asta Powerproject Enterprise.

To install Asta Powerproject Enterprise:

1. Log into the server machine as a user with Administrator privileges.

2. Insert the Asta Powerproject Enterprise installation CD into the server’s CD drive. 3. Browse the CD in Windows Explorer and locate the setup.exe file.

If you have downloaded the installation files for Asta Powerproject Enterprise, setup.exe will be located in the folder into which you unzipped the installation files, not on a CD.

4. Right-click the setup.exe file and select Run as administrator from the menu that appears.

5. Follow the steps in the installation wizard to install Asta Powerproject Enterprise, clicking Next to move between the various screens of the wizard.

If Microsoft .NET Framework 4 is not present on the server machine, the

installation wizard will install it automatically. The installation of .NET Framework 4 will take some time and may require you to reboot the server machine; if so, the Asta Powerproject installation wizard will carry on automatically after the reboot. 6. Enter your user name, the name of your organisation and your Asta Powerproject

Enterprise serial number in the fields on the following screen:

Asta Powerproject Enterprise is installed into the following folder by default: C:\Program Files\Asta\Asta Powerproject – enterprise\ (32-bit systems). C:\Program Files(x86)\Asta\Asta Powerproject – enterprise\ (64-bit systems). 7. If you want to install Asta Powerproject Enterprise to a location other than the

default, click the Custom radio button on the following screen, which will give you access to an additional page of the wizard in which you can specify an installation folder:

(14)

8. On the above screen, leave the Install server as a service check box cleared. Although you can use this check box to install the server as a service

automatically, it is preferable to install the server as a service manually after the initial installation – following the steps in the next section of this document – as this gives you the ability to configure the name of the service, as well as a number of other variables.

9. Click Install on the final screen of the wizard to install Asta Powerproject Enterprise.

10. When the installation routine is complete, click Finish to exit the wizard. 11. Reboot the server machine on which you have installed Asta Powerproject

Enterprise.

2.5 Installing the Asta Name Server and the Enterprise server to run as

services

Now that you have installed Asta Powerproject Enterprise, you can install the Enterprise server (AstaEnterprise.exe) and the Asta Name Server (AstaNameServer.exe) to run as services, so that they are loaded automatically when Windows starts and run in the background. You should install the Asta Name Server as a service first, followed by the Enterprise server.

2.5.1 Installing the Asta Name Server to run as a service

To install the Asta Name Server to run as a service:

1. On the server machine on which you have installed Asta Powerproject Enterprise, launch a command prompt, ensuring that you run it as Administrator. A command prompt window appears:

2. In the command prompt window, change the directory location to the folder in which Asta Powerproject Enterprise has been installed, which is, by default:

(15)

C:\Program Files\Asta\Asta Powerproject – enterprise\ (32-bit systems). C:\Program Files(x86)\Asta\Asta Powerproject – enterprise\ (64-bit systems). 3. Type AstaNameServer.exe –install and press ENTER. You see a

confirmation that the service has been installed successfully:

If you are planning to use Asta Archive Manager to archive historic data from your projects, instead of entering AstaNameServer.exe –install, enter

AstaNameServer.exe –web –install. This turns on web services that Asta Archive Manager requires to operate.

2.5.2 Installing the Enterprise server to run as a service

You can install the Enterprise server to run as a service in a number of ways, each of which is described below. Choose the way that best fits the manner in which you want to use Asta Powerproject Enterprise and follow the instructions in that section.

If you are not carrying on directly from the previous section, start by launching a command prompt on the server machine on which you have installed Asta Powerproject Enterprise, ensuring that you run it as Administrator, then change the directory location to the folder in which Asta Powerproject Enterprise has been installed (as described in the previous section).

As with the installation of the Asta Name Server, if you are planning to use Asta Archive Manager to archive historic data from your projects, add –web to whichever command you use to install the Enterprise server, to turn on web services that Asta Archive Manager requires to operate.

2.5.2.1 Installing the Enterprise server to run as a standard service

If you install the Enterprise server to run as a standard service, it runs as a service with a name of “<user name>_<machine name>”, where <user name> is the name of the person who has logged onto the server machine and <machine name> is the name of the server machine itself. For example, if user JSMITH has logged onto a server machine called MAINSRV, the Enterprise server is run as a service on this machine with a name of JSMITH_MAINSRV.

To install the Enterprise server to run as a standard service, enter the following at the command prompt:

AstaEnterprise.exe –install

2.5.2.2 Installing the Enterprise server to run as a service with a specific name

To install the Enterprise server to run as a service with a specific name, enter the following at the command prompt:

AstaEnterprise.exe –install <server name>

Where <server name> is the name with which you want the service to run. The name must be a single word, with no spaces or punctuation. For example, to install the Enterprise server as a service so that it runs with the name “AstaServer”, enter:

(16)

2.5.2.3 Installing the Enterprise server to run as a service with a specific identification number and name

If you want to enable users to log in automatically using Active Directory®, you must install the Enterprise server with a specific identification number and name.

To install the Enterprise server to run as a service with a specific identification number and name, enter the following at the command prompt:

AstaEnterprise.exe -server_id <server identification number> –install <server name>

Where <server identification number> is the number with which you want to identify the server and <server name> is the name with which you want the service to run. For example, to install the Enterprise server as a service so that it runs with the server identification number 1 and the name “AstaProjectServer”, enter:

AstaEnterprise.exe -server_id 1 –install AstaProjectServer

2.5.2.4 Installing multiple Enterprise servers to run as services

If you want to run more than one Enterprise server on a server machine, you must install each one with a specific identification number and name, as described in the previous section.

For example, you could enter the following commands at the command prompt to install two Enterprise servers to run as services:

AstaEnterprise.exe -server_id 1 –install AstaServer1 AstaEnterprise.exe -server_id 2 –install AstaServer2

2.5.2.5 Installing the Enterprise server to run as a service with specific dependencies

Depending on which other services are installed on the server machine, you may experience problems in the following circumstances:

• If a service that is required for the Enterprise server or one of its components to operate does not run.

• If a service that prevents the Enterprise server or one of its components from operating does run.

In particular, if you install the server to run as a service onto a server machine on which Oracle is installed, it is made dependent on all Oracle services (all services beginning with “Ora”) by default. As well as potentially causing problems, this can degrade performance. You may want to install the Enterprise server to run as a service, while specifying the services on which it is dependent.

To install the Enterprise server to run as a service and specify the services on which it is dependent, enter the following at the command prompt:

AstaEnterprise.exe –depend <dependencies> –install

Where <dependencies> is a comma-separated list of the services on which the service is dependent. For example, you could enter the following command at the command prompt to install the Enterprise server as a service that is dependent on the

OracleServiceTEAMPLAN and MSSQLSERVER services:

AstaEnterprise.exe –depend OracleServiceTEAMPLAN,MSSQLSERVER –install

To incorporate a server identification number and server name into such a command, enter the following at the command prompt:

AstaEnterprise.exe –depend <dependencies> -server_id <server identification number> –install <server name>

(17)

For example, to install the Enterprise server as a service that is dependent on the

MSSQLSERVER service and so that it runs with the server identification number 1 and the name “AstaProjectServer”, enter:

AstaEnterprise.exe –depend MSSQLSERVER -server_id 1 –install AstaProjectServer

2.6 Configuring the Asta Name Server and Enterprise server services

Once you have installed the Asta Name Server and Enterprise server to run as services, they appear in the list of services in Windows Control Panel. Initially, both services are set to be started manually. You must configure the services to start automatically.

To configure the Asta Name Server and Enterprise server services:

1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Control Panel.

2. Within Control Panel, select System and Security, then Administrative Tools. The

Administrative Tools window appears.

3. Double-click the Services administrative tool. The Services window appears:

4. Locate the “Asta Name Server” and “Asta Powerproject – Enterprise Server” services in the list (highlighted in the above illustration). If you have installed more than one Enterprise server to run as a service, a separate service will appear in the list for each Enterprise server.

5. Double-click one of the Asta services. The service’s Properties dialog appears. 6. On the General tab of the dialog, select Automatic in the Startup type field:

(18)

8. Double-click the next Asta service in the list of services and repeat steps 6 and 7 to configure this service in the same way as the first.

9. If there are further Asta services in the list, configure these in the same way.

2.7 Configuring Asta Powerproject Enterprise registry settings

There are a number of registry settings that affect the way in which Asta Powerproject Enterprise operates. Follow the instructions in this section to configure the registry settings in a way that suits your preferences.

2.7.1 Specifying whether baselines are pre-mounted completely

Once you have created one or more projects in the Asta Powerproject Enterprise system, it is recommended that you specify that the projects and their baselines should be pre-mounted each time the Enterprise server starts (see section 4.8, Specifying that projects and their baselines should be pre-mounted, for more details). This is in order to speed up the mounting of projects and baselines, to reduce the usage of memory when projects are mounted and to prevent projects from being dismounted automatically when all users have finished working with them.

However, some users prefer to maintain a slightly longer mounting process, as this can mean that the runtime performance of the Enterprise server is improved. You can use a registry key to specify whether baselines are pre-mounted completely when the Enterprise server starts, or whether only key (index) fields are mounted into memory, thereby

reducing the amount of time taken to pre-mount baselines.

To specify whether baselines should be pre-mounted completely when the Enterprise server starts:

1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Registry Editor.

2. In the left pane of Registry Editor, expand the registry to the following branch: HKEY_LOCAL_MACHINE\SOFTWARE\ASTA\PowerProject Teamplan\1.0\ DataSourceMount\ (32-bit systems).

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Asta\PowerProject Teamplan\1.0\DataSourceMount\ (64-bit systems).

3. In the right pane of Registry Editor, locate the KeyFieldsOnly registry key. This key determines whether or not baselines that are set to be pre-mounted are mounted completely, or whether only key (index) fields are mounted into memory, thereby reducing the amount of time taken to mount baselines. The default,

recommended value for this key is 2, which means that only key fields are mounted.

4. If you want to specify that baselines should be pre-mounted completely, edit the properties of this key and set its value to 0:

(19)

Although changing the behaviour in this way results in longer mounting times and greater memory usage, it also results in faster baseline updates, as baseline data does not have to be read into memory as and when it is required.

2.7.2 Specifying whether projects are recalculated at mount time

If you experience a server problem or crash that prevents associated objects from being updated in line with each other, associated values can become mismatched. For example, a link may become detached from one of the tasks it is supposed to link.

You can use a registry key to specify whether or not the Enterprise server recalculates projects and baselines at mount time, to check that all associated values match up with each other. Recalculating projects and baselines as they are mounted solves any such problems, but it also results in longer mounting times.

To specify whether projects and baselines are recalculated at mount time:

2. In the left pane of Registry Editor, expand the registry to the following branch: HKEY_LOCAL_MACHINE\SOFTWARE\ASTA\PowerProject Teamplan\1.0\ DataSourceMount\ (32-bit systems).

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Asta\PowerProject Teamplan\1.0\DataSourceMount\ (64-bit systems).

3. In the right pane of Registry Editor, locate the RecalcOnMount registry key. This key determines whether or not projects and baselines are recalculated at mount time. The default value for this key is 1, which means that projects and baselines are recalculated at mount time.

4. To specify that projects and baselines should not be recalculated at mount time, edit the properties of this key and set its value to 1.

Although changing the behaviour in this way results in shorter mounting times, it may lead to problems that result from mismatched associated values.

2.7.3 Specifying database timeout settings

You can use the following registry keys to specify how long the Enterprise server should wait for responses from your database:

(20)

• Use the ConnectionTimeout key to specify how long the Enterprise server should wait for a response from the database when connecting to it initially. If the value (in seconds) is exceeded, the Enterprise server assumes that the database is not available.

• Use the CommandTimeout key to specify how long the Enterprise server should wait for confirmation that a command that has been submitted to the database has been completed successfully. If the value (in seconds) is exceeded, the Enterprise server assumes that the command has failed.

To specify database timeout settings:

2. In the left pane of Registry Editor, expand the registry to the following branch: HKEY_LOCAL_MACHINE\SOFTWARE\ASTA\PowerProject Teamplan\1.0\ EntSrv\ (32-bit systems).

HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432node\Asta\PowerProject Teamplan\1.0\EntSrv\ (64-bit systems).

3. In the right pane of Registry Editor, locate the ConnectionTimeout and CommandTimeout registry keys.

4. To specify different timeout settings, edit the properties of the keys and set their values to the required number of seconds. You may find that longer timeout values work better if you are working with extremely large volumes of data.

2.8 Installing an Oracle driver

If you are using an Oracle database rather than Microsoft SQL Server, you must install a contemporary version of the Oracle Data Access Components for Oracle Client (ODAC) driver onto the server machine on which you have installed the Enterprise server. This driver must be installed in addition to the standard Oracle client software that is required in order to connect an Enterprise server to an Oracle data source.

The earliest version of the driver that you must install is ‘ODAC 11.2 Release 3 and Oracle Developer Tools for Visual Studio (11.2.0.1.2)’; you can install a later version of this driver. The driver is freely available, with installation instructions, on Oracle’s website.

2.9 Creating a data source in Asta Serveradmin

You created a database when following the steps in section 2.1, Creating a Microsoft SQL Server database. You now need to create a corresponding “data source” in Asta

Serveradmin, the application that you use to administer the Enterprises server. To create a data source in Asta Serveradmin:

1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Asta Serveradmin.

1. Select the New command from the Datasource menu. The New Datasource

wizard appears.

2. On the first screen of the wizard, click the Datasource direct connection radio button:

(21)

3. Click Next.

4. On the second screen of the wizard, enter a suitable name and description for the data source in the Name and Description fields; it is a good idea to give the data source a description that describes the projects that it will contain.

5. If you have installed more than one Enterprise server on the server machine or if you want to enable users to log in automatically via Active Directory, enter a positive integer that links the data source to a particular server in the Server identification number field:

If you only use a single server and you are not using Active Directory to enable automatic login, you can leave this number set to 1. You can make a data source inaccessible to all servers (ie take it offline), by setting this number to zero. 6. Click Next.

7. On the third screen of the wizard, click Build to access the Connection String Generation wizard, which you can use to create the ActiveX Data Objects® (ADO) connection string that specifies the database provider and the data source to which the Enterprise server should connect.

8. On the first screen of the wizard, click the Microsoft SQL Server database radio button:

(22)

10. On the second screen of the wizard, enter the name of the server machine on which you created the Microsoft SQL Server database in the Please enter the name of the machine that is running SQL Server field, noting the following points: If you are using Microsoft SQL Server 2012 Express, enter <server machine name>\SQLExpress, where <server machine name> is the name of the server machine. For example, if the server machine is called “Server1”, enter

Server1\SQLExpress.

If you are using Microsoft SQL Server 2012 Express and you have installed Asta Powerproject Enterprise onto the server machine on which your database is located, enter .\SQLExpress.

If you are using a version of Microsoft SQL Server 2012 other than “Express”, simply enter the name of the server machine. For example, if the server machine is called “Server1”, enter Server1.

11. Enter the name that you applied to the Microsoft SQL Server database when you created it in section 2.1, Creating a Microsoft SQL Server database, in the Please enter the catalog (database) to use field:

12. Click Next.

13. On the third screen of the wizard, enter the user name and password of the Microsoft SQL Server user that you created in section 2.2, Creating a Microsoft SQL Server database user and leave the Use SSPI integrated security check box

cleared; if you use Windows authentication (in which Microsoft SQL Server interrogates Windows and grants access only to user accounts that are specified by the database administrator), do not enter a user name and password, but select the Use SSPI integrated security check box:

14. Click Finish to close the Connection String Generation wizard and return to the

New Datasource wizard, where a connection string containing the information you have provided appears in the Connection string field:

(23)

15. Leaving the Optimise transaction data check box selected, select or clear the

Server/database on same machine check box as appropriate – depending on whether you have installed Asta Powerproject Enterprise on the server machine on which Microsoft SQL Server is installed.

16. If you have installed Asta Powerproject Enterprise onto a different server

machine, create a folder on the server machine on which Microsoft SQL Server is installed and give the user account that is being used to run the Asta Powerproject Enterprise server “Full Control” access rights to the folder. Temporary files will be stored in this folder. You must then specify the location of the folder in the

Server/database shared folder field, in the format \\<server name\<path and folder name>. For example, if the server machine is called “Server1” and the folder is on the root of the server and called “AstaTemp”, enter

\\Server1\AstaTemp.

17. Click Test to test that the connection to the database works correctly. A message appears informing you whether or not the connection string is valid.

If the connection string is not valid, double-check the details of the database and user that you created, then create the connection string again.

18. Click Finish to close the New Datasource wizard. The new data source is created and appears in Asta Serveradmin:

2.10 Configuring Asta Powerproject Enterprise using Asta Serveradmin

Once you have created a data source, you must follow the instructions in this section to use Asta Serveradmin to configure Asta Powerproject Enterprise.

If the Enterprise server service is currently running, stop it before carrying out the steps described in this section, then restart it once you have finished configuring Asta

Powerproject Enterprise using Asta Serveradmin.

2.10.1 Specifying the server location method in Asta Serveradmin

You must specify the way in which you want the Asta Powerproject clients to locate the Enterprise server(s) that you have installed.

To specify the server location method:

1. Within Asta Serveradmin, select the Set Locator command from the Server menu. The Server Location Method dialog appears.

(24)

2. Select the Asta Name Server check box, then enter either the IP address or the server name of the server machine on which you have installed the Asta Name Server.

3. Enter the number of seconds after which you want the Enterprise server to time out when it tries to connect to the Asta Name Server in the Asta Name Server timeout field.

4. The Asta Name Server pings for Enterprise servers every 20 seconds to determine which are available. Enter the number of minutes after which an unavailable Enterprise server should be removed from the Asta Name Server’s list of servers in the Contact server timeout field. As servers may be unavailable temporarily – as a result of network problems, for example – entering a suitable timeout such as 5 minutes means that a server that is only unavailable temporarily is not removed unnecessarily from the Asta Name Server’s list.

5. Click OK.

2.10.2 Specifying the server temporary folder

You must specify a folder on the server machine on which you have installed Asta Powerproject Enterprise into which the Enterprise server can store temporary files as it works. The server stores work-in-progress for the Asta Powerproject clients in order to be able to restore a client’s work if the client crashes.

As you can have more than one Enterprise server running on a server machine, the temporary files for each Enterprise server are stored in subfolders, each one unique to an Enterprise server, within the temporary folder you that you specify here.

To specify the server temporary folder:

1. Within Asta Serveradmin, select the Set Temporary Folder command from the

Server menu. The Browse For Folder dialog appears.

2. Select a folder on the server machine on which you have installed Asta

Powerproject Enterprise in which to store temporary files; click Make New Folder

to create a new folder at this point in time if a suitable folder does not already exist.

(25)

3. Click OK.

2.10.3 Specifying the audit logs folder and enabling audit logging

You must specify a folder on the server machine on which you have installed Asta Powerproject Enterprise into which the Enterprise server can store audit logs as it works. The audit logs record which users perform which actions, the date and time on which the actions are performed, the applications that perform each action and the dates and times at which users log into and log out of projects. You can display audit logs from within Asta Serveradmin.

If you have more than one data source, you can enable or disable audit logging for each one individually. Asta Serveradmin creates a subfolder for each data source for which audit logging is enabled. Every project in a data source has its own audit log file, <project

name>.LOG, and its own usage log file, <project ID>_USAGE.LOG (where <project name> and <project ID> are the name and ID of the project respectively).

Project audit logs continue to grow indefinitely, so if you edit a project regularly, you should delete the audit log files occasionally so that they do not take up too much disk space.

To specify the audit logs folder:

1. Within Asta Serveradmin, select the Set Folder For Audit Logs command from the

Server menu. The Browse For Folder dialog appears.

2. Select a folder on the server machine on which you have installed Asta

Powerproject Enterprise in which to store audit logs; click Make New Folder to create a new folder at this point in time if a suitable folder does not already exist.

(26)

To enable audit logging for a data source:

1. Within Asta Serveradmin, select the data source for which you want to enable audit logging.

2. Select the Properties command from the Datasource menu. The Datasource Properties dialog appears.

3. Click the Auditing tab.

4. Select the Generate auditing log for datasource check box:

5. Click OK.

6. Repeat the above steps to enable audit logging for each data source.

2.10.4 Enabling users to log in automatically using Active Directory

By default, users may have to enter their usernames and passwords once or twice to log in to a project in Asta Powerproject:

• Once to log in to the server (if there are server-level users defined).

• Once to log in to the project (if there are project-level users defined, and if the project-level username does not match the server-level username).

Asta Powerproject Enterprise supports the Active Directory service, which catalogues information about all the objects on a network, including people, computers, and printers, and distributes that information throughout the network. Security is integrated with Active Directory through login authentication and access control.

If you use Active Directory to manage the users on your network, you can configure Asta Powerproject Enterprise to allow users to log into servers and projects automatically, using the security and access control provided by Active Directory. This means that users do not have to enter user names and passwords when they log into their projects.

To enable users to log in automatically using Active Directory:

1. Structure your users within Active Directory so that they belong to security groups which can be associated with specific Enterprise servers. For example, if you want one set of users (A) to have access to the data sources associated with server 1 and another set of users (B) to have access to the data sources associated with server 2, structure your Active Directory security groups so that the users

belonging to set A are in one security group and the users belonging to set B are in another.

2. Associate each data source in Asta Serveradmin with a server identification number, so that when you link an Active Directory security group with a server identification number, the users within that security group will have access to the projects within the data sources that are associated with a particular server. Note that when using Active Directory to enable users to log in automatically, you must always start each Enterprise server with a unique name and identification number that corresponds to the server identification numbers you apply to your data sources.

(27)

You use this dialog to specify the Active Directory security groups whose users you want to be able to log in automatically to each Enterprise server.

4. Click Add. The Add Active Directory Group dialog appears.

5. Select the domain on which the security group is located in the Domain field. The Active Directory security groups within the domain appear in the Group field, listed within their hierarchy.

6. Select the security group whose users you want to be able to log in automatically in the Group field.

7. Enter the identification number of the server to which you want the users of the selected security group to be able to log into automatically in the Server ID field. 8. Click OK to confirm your selection and return to the List of Auto Login

Information dialog.

9. If you have more than one Enterprise server, follow steps 4 to 8 for each server. 10. Click OK to close the dialog.

11. Create projects within Asta Powerproject within the appropriate data sources. Within each of the projects, create project-level users that correspond precisely to the users that are defined within Active Directory. The user names of the users you create within your projects must be identical to the names of the

corresponding user in Active Directory.

12. Within your Asta Powerproject projects, apply a unique password to each project-level user. The passwords, which do not have to correspond with anything within Active Directory, prevent users within the same security group from accessing projects using the user name of another user within the same security group. 13. Within your Asta Powerproject projects, select the Active Directory Filtering

check box on the General tab of the Options dialog.

14. Within Asta Serveradmin, specify that the Asta Powerproject projects should be mounted each time the Enterprise server(s) starts (see section 4.8, Specifying that projects and their baselines should be pre-mounted, for details of how to do this). 15. Users within the selected security group can now log in automatically to the

projects within the data sources that are associated with the specified Enterprise server. Note that you can select up to four separate security groups per server identification number, enabling their users to log in automatically.

Although Asta Serveradmin contains additional configuration options, you have now completed the basic tasks that are required to configure Asta Powerproject Enterprise.

(28)

Refer to the Asta Serveradmin Help for details of further configuration steps that you can carry out, for details of how to create user-defined fields in which to store your own information and for details of how to operate the Enterprise server using the Controller application, which is installed alongside the Enterprise server.

2.11 Configuring firewalls to work with Asta Powerproject Enterprise

If you have installed Asta Powerproject Enterprise onto a server machine that is running Microsoft Windows 2008 Server R2 or later, you may find that your Asta Powerproject clients are unable to access your data sources and projects. This is a result of the Windows Firewall’s default settings blocking communications to and from the Asta Name Server and the Enterprise server. You may notice similar problems if you use a firewall other than the Windows Firewall.

If this is the case, follow the instructions in this section to configure your firewall to enable your Asta Powerproject clients, the Asta Name Server and the Enterprise server to

communicate with each other. You do this by adding a number of inbound and outbound rules on the firewall on the server machine on which Asta Powerproject Enterprise has been installed.

These instructions show how to configure the Windows Firewall, as this is the firewall that is used by default. If you use a different firewall, you should still follow the instructions in this section, adapting them as required to suit the firewall that you use.

2.11.1 Setting firewall rules for the Asta Name Server and Enterprise server

To set up new inbound and outbound rules to enable communication with the Asta Name Server:

1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Windows Firewall.

2. In the left pane of the Windows Firewall, click Inbound Rules. The existing inbound rules are displayed in the middle pane.

3. Right-click Inbound Rules in the left pane and select New Rule. The New Inbound Rule wizard appears.

4. On the first screen of the wizard, click the Program radio button, then click Next:

5. On the second screen of the wizard, click the This program path radio button, then click Browse and locate the Asta Name Server application

(AstaNameServer.exe) in the dialog that appears; it is located in the folder in which Asta Powerproject Enterprise has been installed. Select this and click Open

(29)

6. On the third screen of the wizard, click the Allow the connection radio button, then click Next:

7. On the fourth screen of the wizard, select the Domain check box, clear the Private

and Public check boxes, then click Next:

8. On the fifth screen of the wizard, enter a name and description that will enable you to identify the new rule, then click Finish:

9. Right-click Outbound Rules in the left pane and select New Rule. The New Outbound Rule wizard appears.

10. Follow steps 4 to 8 above to create a new outbound rule in the same way that you created the inbound rule.

You now need to set up similar inbound and outbound rules to enable communication with the Enterprise server. To do this, follow the steps above, but rather than specifying the Asta Name Server application on the second screen of the wizard, specify the Enterprise server (AstaEnterprise.exe, again located in the folder in which Asta Powerproject Enterprise has been installed).

(30)

2.11.2 Setting firewall rules for specific ports

If you have followed the instructions in the previous section to set up firewall rules for the Asta Name Server and the Enterprise server, but your Asta Powerproject clients are still unable to access your data sources and projects, follow the instructions in this section to set up firewall rules for specific ports. You must set up an inbound rule and an outbound rule for each of the following ports:

• 42362. This port is used for communication between the Enterprise server and the Asta Name Server.

• 4199, 4200, 4201, … These ports are used for communication between the

Enterprise server and the Asta Powerproject clients. If you have a single Enterprise server service running on a server machine, you need only create rules for port 4199; if you have two Enterprise server services running, you need to create rules for ports 4199 and 4200; if you have three Enterprise server services running, you need to create rules for ports 4199, 4200 and 4201; and so on.

• 4299 – 4398. These ports are used for communication relating to notifications. The number of ports used depends on the number of client instances accessing the Enterprise server at any one time from a single computer (either from a client computer or from a Time Sheet or Web Access server). Port 4299 is used by all clients for notifications, but in some instances, multiple instances of a client can access the Enterprise server at the same time, resulting in more ports being used. As a result of this, you may need to create rules for the entire range of ports from 4299 to 4398.

Follow the instructions below to set up new inbound and outbound rules for each of the above ports (or ranges of ports):

1. On the server machine on which you have installed Asta Powerproject Enterprise, launch Windows Firewall.

2. In the left pane of the Windows Firewall, click Inbound Rules. The existing inbound rules are displayed in the middle pane.

3. Right-click Inbound Rules in the left pane and select New Rule. The New Inbound Rule wizard appears.

4. On the first screen of the wizard, click the Port radio button, then click Next. 5. On the second screen of the wizard, click the TCP radio button.

6. Click the Specific local ports radio button and enter the port, or range of ports, to which the rule applies in the field to the right, then click Next:

7. On the third screen of the wizard, click the Allow the connection radio button, then click Next.

8. On the fourth screen of the wizard, select the Domain check box, clear the Private

(31)

9. On the fifth screen of the wizard, enter a name and description that will enable you to identify the new rule, then click Finish.

10. Right-click Outbound Rules in the left pane and select New Rule. The New Outbound Rule wizard appears.

11. Follow steps 4 to 9 above to create a new outbound rule in the same way that you created the inbound rule, noting that the radio button mentioned in step 6 above is called Specific remote ports rather than Specific local ports in the New

(32)

(33)

3 Installing an Asta licence server and Asta Licence Manager

This section of the document describes how to install an Asta licence server, on which are located the licences for your Asta software applications, and the Asta Licence Manager application that enables you to manage the licences. It also describes how to obtain your licences from Asta Development.

The installation of Asta Licence Manager comprises the following steps: • Choosing a server machine on which to install an Asta licence server. • Installing the Asta Licence Manager application.

• Obtaining your licences from Asta Development.

• Configuring Asta licensing in a Windows domain environment. • Configuring Asta licensing in a Windows workgroup environment. • Configuring firewalls to work with the Asta licence server.

3.1 Choosing a computer on which to install an Asta licence server

When you install the Asta Licence Manager application, a licence server is installed automatically onto the same computer. However, you may want to install a licence server onto a different computer to the Asta Licence Manager, as this enables you to manage the licences contained within the licence server remotely, for example from the system administrator’s computer. You do this by running the separate Asta licence server installer which is available on the Asta Licence Manager CD.

In normal practice, you will probably only want to install and use a single licence server, containing all of your licences. Ensure that you install the licence server onto a computer to which all of your Asta Powerproject clients can connect.

Install the Asta Licence Manager onto any suitable computer that can connect to the computer on which you have installed the licence server, for example the system administrator’s computer.

Although one licence server is normally sufficient, you can install and use more than one, each on a different computer. You may want to install more than one licence server in the following circumstances:

• If you have an extremely large number of licences and want to spread the load over a number of different computers.

• If you want to set up different licence servers to serve different “communities” within your network.

• If you want to set up different licence servers to serve different “product types”. For example, you could have one licence server containing your normal licences, and another containing your read-only licences.

• If you want to set up a second licence server as a “backup”, containing a number of spare licences for use in the event of the failure of your main licence server (this would of course cost more in terms of the additional spare licences).

The computer on which you install Asta Licence Manager will ideally be a physical machine, although it is possible to install it onto a virtual machine. If you choose to install Asta Licence Manager onto a virtual machine, the following restrictions apply:

• If you copy, clone or upgrade a virtual machine image on which Asta Licence Manager is installed, the licences are unavailable in the copied, cloned or upgraded virtual machine and you are unable to add any licences to the copy, clone or upgrade.

(34)

• You cannot move or loan a licence from a licence server that has been installed onto a virtual machine. A warning message appears if you attempt to do so. • If you attempt to move a licence from a licence server that has been installed onto

a physical computer to an Asta software client or to a licence server that has been installed onto a virtual machine, you are warned that the move cannot be

reversed and asked if you wish to continue.

• If you attempt to loan a licence from a licence server that has been installed onto a physical computer to an Asta software client or to a licence server that has been installed onto a virtual machine, you are warned that the loan cannot be cancelled and asked if you wish to continue.

3.2 Installing the Asta Licence Manager application

To install Asta Licence Manager:

1. Log into the computer on which you are going to install Asta Licence Manager as a user with Administrator privileges.

2. Insert the Asta Licence Manager installation CD into the computer’s CD drive. 3. Browse the CD in Windows Explorer and locate the setup.exe file.

If you have downloaded the installation files for Asta Licence Manager, setup.exe will be located in the folder into which you unzipped the installation files, not on a CD.

4. Right-click the setup.exe file and select Run as administrator from the menu that appears.

5. Follow the steps in the installation wizard to install Asta Licence Manager, clicking

Next to move between the various screens of the wizard.

6. Enter your user name, the name of your organisation and your Asta Licence Manager serial number in the fields on the following screen:

7. Click Install on the final screen of the wizard to install Asta Licence Manager. 8. When the installation routine is complete, click Finish to exit the wizard.

If you want to install an Asta licence server onto a separate computer, you can now do so by running the separate Asta licence server installer, which is available on the Asta Licence Manager CD, on the other computer.

3.3 Obtaining your licences from Asta Development

Once you have installed Asta Licence Manager, you can use the application to obtain the licences that you need for your Asta software from Asta Development.

(35)

To obtain your licences from Asta Development:

1. Launch Asta Licence Manager on the computer on which you have installed it. 2. Click the Request tab:

3. Enter the name of the computer on which the licence server for which you want to request licences is installed in the Server name field. Alternatively, click Browse

to search the network for a licence server.

4. Select the product for which you want to request a licence in the Product field. 5. Select the Read only client check box if you want to request a licence for a

read-only version of Asta Powerproject, or select the Educational client check box if you want to request a licence for an educational version. Leave both check boxes clear to request a standard licence.

6. Click Generate.

Asta Licence Manager generates a licence request key, which is displayed in the

Licence request key field. You must transfer the licence request key to Asta’s Technical Support department.

7. Click Copy to copy the licence request key to the Windows Clipboard.

8. Paste the licence request key into an email, entitled NEW LICENCE REQUEST, and send it to [email protected].

9. Once you have transferred the licence request key to Asta, the Technical Support department will send you a licence code. Copy the licence code that you have received to the Windows Clipboard.

10. Within Asta Licence Manager, click the Add tab:

11. Click Paste to paste the licence code into the Licence key field.

(36)

3.4 Configuring Asta licensing in a Windows domain environment

The instructions in this section assume that you are working in a Windows domain environment. If you are working in a Windows workgroup environment, ignore the

instructions in this section and refer to section 3.5, Configuring Asta licensing in a Windows workgroup environment. The absence of a “Domain users” group (referred to below) indicates that you are working in a Windows workgroup environment. If you are not sure whether you are working in a domain environment or in a workgroup environment, consult with your IT staff.

After you have obtained your licences from Asta Development, you need to configure the computer on which your Asta licence server is located to enable users to access the licences.

Note that domain administrators have access to the licences by default, so you should use a non-administrator user to test access to the licences.

Before you configure the Asta licence server machine, you should choose an Active Directory group with which to control access to licences. Which group you use will depend on whether you want to allow or deny access to the licences by default. Two common choices are as follows:

• The “Distributed COM users” group. Users would not be a member of this group by default and would be denied access to the licences unless they were added to this group.

• The “Domain users” group. Users would be a member of this group by default and the licences would be freely accessible to anybody who is logged into the domain. To configure the Asta licence server machine:

1. On the computer on which you have installed the Asta licence server, launch Control Panel.

2. Within Control Panel, select System and Security, then Administrative Tools. The

Administrative Tools window appears.

3. Double-click the Component Services administrative tool. The Component Services window appears:

4. Double-click the Computers folder in the middle pane of the Component Services

window. The My Computer icon appears.

5. Right-click My Computer and select Properties. The My Computer Properties

dialog appears.

6. On the Default Properties tab of the dialog, ensure that the Enable Distributed COM on this computer check box is selected:

(37)

7. On the COM Security tab of the dialog, click Edit Limits in the Launch and Activation Permissions group:

The Launch and Activation Permission dialog appears:

8. Click Add. The Select Users, Computers, Service Accounts, or Groups dialog appears:

9. In the Enter the object names to select field, enter the name(s) of the individual users or the name of the Active Directory group that contains the users who are to use the licences.

10. Click Check Names to ensure that you have entered the user or group name correctly.

11. Click OK to return to the Launch and Activation Permission dialog.

12. With the new group selected in the Group or user names field, select all four

Allow check boxes in the Permissions for… field, then click OK. 13. Click OK to close the My Computer Properties dialog.

Asta Development. Product Installation Guide

Asta

Development

Trademarks

Table of Contents

1

Overview of this document

1.1

Notes on operating systems and database types

2

Installing the Asta Powerproject Enterprise system

2.1

Creating a Microsoft SQL Server database

2.2

Creating a Microsoft SQL Server database user

2.3

Specifying the Microsoft SQL Server authentication mode

2.4

Installing Asta Powerproject Enterprise

2.5

Installing the Asta Name Server and the Enterprise server to run as

services

2.6

Configuring the Asta Name Server and Enterprise server services

2.7

Configuring Asta Powerproject Enterprise registry settings

2.8

Installing an Oracle driver

2.9

Creating a data source in Asta Serveradmin

2.10

Configuring Asta Powerproject Enterprise using Asta Serveradmin

2.11

Configuring firewalls to work with Asta Powerproject Enterprise

3

Installing an Asta licence server and Asta Licence Manager

3.1

Choosing a computer on which to install an Asta licence server

3.2

Installing the Asta Licence Manager application

3.3

Obtaining your licences from Asta Development

3.4

Configuring Asta licensing in a Windows domain environment