Installguide Safran Project 7download.safran.no/.../ver72/Installguide_for_Safran_Project_7.2.pdfInstallguide for Safran Project 7.2 5 Installation General Safran Project 7.2 installation

Installguide for Safran Project 7.2 1

Installguide

FOR

Safran Project version 7.2 (Last update: December 14st, 2017)


Copyright © 1999 - 2017 Safran Software Solutions AS. All Rights reserved.

Accuracy

Although every effort has been made to ensure the accuracy and completeness of this document, no

warranty, expressed or implied, is made by Safran Software Solutions AS as to the accuracy of this

publication and the features or the applicability of techniques suggested.

Copyright Notice

The information provided in this manual is for informational purposes only. It may change without notice

and does not represent a commitment as to merchantability or fitness for a particular purpose by Safran

Software Solutions AS.

Safran Software Solutions provide the software described in this manual AS under a Safran License

Agreement. The software may be used only in accordance with the terms of the license agreement.

No part of this manual may be reproduced or transmitted in any form or by any means, electronic or

mechanical, including photocopying and recording, for any purpose without the express written

permission of Safran Software Solutions AS.

Safran is a registered trademark; Safran Project, Safran Planner, Safran Risk, Safran for Microsoft Project,

Safran for the Microsoft Project Platform, Safran Web Access, Safran Integrator for SAP, Safran

Enterprise Developer, Safran Details and Safran Details Developer are trademarks of Safran Software

Solutions as. All other brands or names are trademarks or registered trademarks owned by their

respective holders.

Introduction

The purpose of this document is to familiarise you with the process of installing Safran Project and the

structure of Safran Project folders and file structure.

This book is written to assist support personnel, application developers, and system integrators.


Table of Contents Installation ..................................................................................................................................................... 5

General ....................................................................................................................................................... 5

Requirements ............................................................................................................................................. 5

Installation types and licensing .................................................................................................................. 6

Install recommendation that influence performance ............................................................................... 6

Important information for users upgrading from Safran Project v5 ......................................................... 7

Important information for users upgrading from Safran Project Trial to full version ............................... 8

Before you install ....................................................................................................................................... 9

Chapter 1 - Installing Safran Project ............................................................................................................10

MSI Installation ........................................................................................................................................11

Chapter 2 - Activate your copy of Safran Project .........................................................................................17

Licensing Networked edition ...................................................................................................................18

Activating the license ...............................................................................................................................19

Registry Settings .......................................................................................................................................19

Grace period “Roaming” ..........................................................................................................................19

Chapter 3 – Managing the license ...............................................................................................................20

Chapter 4 - Safran Project files and folders installed ...................................................................................22

Files and folders in installation directory. ................................................................................................22

Files and folders in user specific directory ...............................................................................................22

Chapter 5 - Safran Project Database ............................................................................................................24

Database definitions ................................................................................................................................24

Database procedures ...............................................................................................................................24

Chapter 6 - Creating a new Safran Project database ...................................................................................25

Microsoft SQL Server ...............................................................................................................................25

Oracle Database Server ............................................................................................................................25

Database initiation ...................................................................................................................................26

Chapter 7 - Updating a Safran Project database to the latest version ........................................................28

Chapter 8 - Recompile triggers and procedures ..........................................................................................30

Troubleshooting Licensing Issues ................................................................................................................32

Check License issue ..................................................................................................................................32

Read Write Access....................................................................................................................................33

License mismatch .....................................................................................................................................34

License is locked .......................................................................................................................................35


Sub-Module says Activation Required .....................................................................................................36

Contact Safran Software Solutions AS. ........................................................................................................37


Installation

General

Safran Project 7.2 installation is a basic msi installation created with Installshield.

This guide performs a normal set up with the executable file, but informs you were to pick up the clean

msi-package.

Requirements

Operating System:

Windows 10 recommended, Windows 7, Windows 8.1.

Microsoft .Net Framework 4.5

Database drivers.

Microsoft Native Client 2008 is required when connecting to a MSSQL database.

Oracle – OraClient is required when connecting to an Oracle database.

Supported Environments.

Please see the Customer Release Note for your current build of Safran Project for information on

supported environments.

Running Safran Project from a network share.

If running software from a network share csapi.dll, Licprotector310.dll and Licprotector500.dll are

required to be registered on the client, this is normally done by the installation. Contact Safran Software

Solutions support for information about running Safran Project from a network share.

Administrative privileges:

The installation must be done with administrator rights on the client computer.


Installation types and licensing

Safran Project comes in a Personal and an Enterprise edition.

Personal is for a single user while Enterprise is for several users.

There is a difference in setting up the licensing for the two editions.

After installation of Personal edition, enter serial number when Safran Project launched.

For licensing information for network installs (Typically done for Enterprise edition), see chapter

“Licensing Networked Edition”.

Install recommendation that influence performance

There are several factors that will influence the system performance.

On the client side, we recommend this client configuration (for the list of supported environments see

the Customer Release Note):

• Windows 10 Processor:

• 2 GHz or higher

• Memory: minimum 4 GB RAM, recommended 8GB

• 250 MB available disk space on local hard disk for local installations.

Please ensure that at least 20% free disk space for optimum Windows performance.

On the database server, the performance will be influenced by processing speed, and how much RAM is

available for the database service. The rule of thumb here is you need more RAM and higher processing

speeds if you have many users working on the same database at the same time, the same is true if there

are many or large projects that carry a large amount of information. Available free space on the

database is also important. We recommend that if you configure the database to expand if it is close to

filled, make it expand by at least 300MB at a time.

The users’ temp folder is extensively used by Safran Project. The temp folder should be kept locally for

best performance. (E.g. If you install Safran Project in a terminal server environment the temporary

folder should be placed as near the end user as possible.)


Important information for users upgrading from Safran Project v5

When upgrading, the database used with Safran Project v5 to Safran Project 7.2 we would like to

emphasize that there will be changes to database tables and fields. In particular, for users that used to,

during status update, save activity history. The Activity History table will as part of the upgrade be

truncated. However, before truncating the database we move the information we need to run forecast

and revisions, from the activity history table to the period_status_a table. The reason for truncating

Activity History is that it saved to much information therefor it would impact performance as it filled up

the database with information the system didn’t need to perform its operations. We know that a few of

our customers have custom made code that used information from Activity History, our

recommendation is that you contact us before upgrading so that we can provide some

recommendations and help find a solution for you.


Important information for users upgrading from Safran Project Trial to full

version

For people upgrading from 30 or 60day trial versions of Safran Project it is recommended that you prior

to running the upgrade do a complete uninstall of the trial product. After the uninstall make sure that

the registry entry for the Safran Project Trial product is removed from the registry, you can check this

here in this registry entry HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Safran Software

Solutions\Safran Project. You should also check that the license file is deleted. You can check in Windows

explorer by typing in %AppData%\Safran\Lic\Project. If you after uninstalling the trial version you still

find a file named SPEP7.lic delete that file.

After these steps, you are now ready to run the install of the full version of Safran Project.


Before you install

▪ Backup/archive all data before updating the software. (The default location of the local database (if you have a previous installation of Safran Project Personal) is %appdata%/safran. It may however, reside elsewhere.

▪ Read these Customer Release Notes carefully.

▪ Read the Installation guide carefully.

▪ To use Safran Project 7.2 the Safran Project database must be upgraded to version 7.1. The Personal Edition is packaged with an updated database ready to use.

▪ If you are upgrading from Safran Project v5, Safran Project v7.0 or Safran Project v7.1, you should uninstall the previous version before you install Safran Project 7.2.


Chapter 1 - Installing Safran Project

Safran Project uses Installshield from Flexera Software for automatic software distribution and

installation.

Follow these instructions if you are installing a copy of the Safran Project software.

To install:

1. Open Windows Explorer and browse for the Safran installation files

2. Run the installation file

3. When the dialog box appears, select Next


MSI Installation If you want to deploy Safran Project with an msi package, you need to browse to

“C:\Users\YOURACCOUNT\AppData\Local\Temp\”

In one of the folders with a cryptic numeric name you will find Safran Project.msi.

Copy and paste this file to a location for further packaging.

You need to read, and accept, the license agreement before continuing.


1. Choose where to install Safran Project, and click Next.

Go to step 6 for instructions on changing installation destination.

Default for 64 bit version of Windows is:

“C:\Program Files (x86)\Safran Software Solutions\Safran Project 7\”

Default for 32 bit version of Windows is:

“C:\Program Files\Safran Software Solutions\Safran Project 7\”


2. Change the destination folder for Safran Project.

Specify a new Destination Folder and press Ok to return to the Choose Destination Location Window

and press Next to continue.


3. Select one of the two and select Next

You can choose between a complete or custom installation.

A complete installation will install the program files and all the database interfaces.

Choose Custom if you do not want to install Safran System Administrator.


4. Ready to install. Click Install to complete installation.


5. Click Finish when installation has completed.

Notice to people upgrading Safran Project Personal: When you start Safran Project

7.2 the first time you will get a message telling you “Database not upgraded for this

version of Safran Project”. Click ok on this, then you can choose if you want to

upgrade your current Safran.db file to the new version or you can browse to your

“%appdata%/safran” folder and use the new Safran72.db file.


Chapter 2 - Activate your copy of Safran Project

The first time you start the application you will be asked to enter a valid serial number and customer

contact information. The system will then contact the Safran Activation Server and activate your copy of

the software. You will not be able to use the software without this activation.

You have now successfully activated your Safran Project software.


If you also have a license for any combination of the following:

• Scheduled Risk module

• Integrated plan

• Safran Integrator for IFS

• ILAP

• Pert Chart (Network Drawing)

• Contract Items

• Enhanced API

• Analytics,

you need to add that using the License Viewer of Safran Project System Administration tool.

Licensing Networked edition

After Safran Project is installed you will find a “SPEN7.lic” file in “%appdata%\Safran\Lic\Project” folder.

For licensing to work for all users on the network, you need to move the SPEN7.lic file to a network share

where all users of Safran Project have access to it. Users will need “write” permission to the SPEN7.lic

file.

In addition, every Safran Project client will need to have the path to the location of SPEN7.lic in the

registry. (See Registry Settings for example.)

The license file is activated by the first user. This way all the users use the same activated license file

eliminating the need for multiple activations.

Let’s say a company has purchased 100 licenses of Safran Project Enterprise. The correct way of setting

up such an environment is as follows:

Copy the license file (SPEN7.lic) to a file share where all Safran users have R/W access

Distribute (install) the software to the clients

Configure the registry for all the users (see “Registry Settings”)

Run software to activate License on file server


Activating the license

The License requires one activation. After the initial activation, each user will automatically register in

the license file ticking of licenses as they register.

Registry Settings

We highly recommend that you use the UNC path when setting the License path. We have used

\\10.10.2.1 as an example below, you need to adjust that according to your systems. The path must be

the same for all users.

32 bit

[HKEY_LOCAL_MACHINE\SOFTWARE \Safran Software Solutions\Safran Project]

"License"="\\10.10.2.1\Safran\SPE\SPEN7.lic"

64 bit

[HKEY_LOCAL_MACHINE\SOFTWARE \Wow6432Node\Safran Software Solutions\Safran Project]

"License"="\\10.10.2.1\Safran\SPE\SPEN7.lic"

Grace period “Roaming”

If for any reason a user loses the connection to the license file, the software will continue working for 30

days counting from the last successful connection to the license file. After this period the user needs to

reconnect to the original license file to continue using the software.

This is maintained by the license file “SafranLocal7.lic” located in “%appdata%\Safran\Lic\Project”

folder. Users must have read/write access to this file.


Chapter 3 – Managing the license The license Viewer is included in the System Administration Module (Safran Project System Manager) to

enable you to manage your license. You need to be logged in as safransa in order to make

changes/adjustments to the license.

Lock: Locks/deactivates a user in the license file.

Activation Key: Option to apply additional keys to license

Transfer License: deactivates your license from the Activation server and enables you to transfer the

license to another domain/computer/user.

http://www.helpserver.biz/onlinehelp/lp/easygo/3.1/help2000/network_deactivate_a_network_licence.htm


LVL – License Viewer Limited

License Viewer Limited (LVL.exe) is in the installation directory and can be used by support personnel for

quick access to your license. You do not need Safran System Administrator installed to view your license.

LVL.exe is limited to view active users, serial key and license file location.

For working with your license, you need to do this in Safran System Administrator


Chapter 4 - Safran Project files and folders installed

Files and folders are in different locations.

All executable files are in the installation directory. (Default under Program Files.)

All user specific files are in “%appdata%\Safran”. (None-changeable, unless changing %appdata%-path.)

Files and folders in installation directory.

During installation, these folders are copied to the specified folder on your hard drive.

Folder “Environment” keeps files that is used when a person start Safran Project for the first time.

Folder “gs” is for GhostScript, used for Safran PSWriter when printing reports to pdf.

Folders “any”, “mss” and “ora” are folders used for database connections.

(Folder “any” is for Safran Project Personal edition only.)

See “Database Definitions” chapter below for more info.

Folder “Safran PDF Printer” keeps the pdf writer that is part of the Safran Project install

Folder “templates” carries US government excel templates

Files and folders in user specific directory

When Safran Project is installed, these personal files and folders are in “%appdata%\Safran”. These are

generated and put in place on first use of Safran Project. Origins are kept in the “Environments” folder in

the Safran Project install directory.


The “Lic\Project” folder contains SPEN7.lic and SafranLocal7.lic.

See “Licensing Networked edition” and “Grace period “Roaming”” for more information.


Chapter 5 - Safran Project Database

Database definitions

Catalogues with the user-selected database programs are created directly under the Safran Project

catalogue. Valid catalogues are:

• MSS : SQL command files for creating and upgrading Microsoft SQL Server databases.

• ANY : SQL command files for creating and upgrading Sybase Adaptive Server Anywhere

databases. (Safran Personal Edition)

• ORA : SQL command files for creating and upgrading Oracle databases.

These catalogues contain database table definition upgrades as wells as trigger definitions. Please find

enclosed:

• initdb.sql : Definitions for creating a new Safran Project database. May be run from

safransa.exe. Ref chapter 3 Creating a Safran Project database for further information.

• spdbxxx.sql : Version updates file, where xxx is an internal database log sequence

number. These files should not be run by the users. Only for system use.

• Sptrig.sql : Command file with all triggers for a complete Safran Project database.

May be run from safransa.exe to refresh triggers in a new or old database.

Database procedures

A database procedure is a SQL program which performs an operation or supplies a database result set

for the application. Safran Project utilizes this facility and has approx. 70-80 procedures in service.

During installation, a catalogue named PROC is created below each of the database catalogues ANY, MSS

and ORA. The PROC-catalogue holds the SQL-command-files necessary to successfully create the Safran

Project procedures. These files may be run single or complete by safransa.exe. Ref. chapter 7 for more

information.

Safran Project users may also add personal written procedure files to this catalogue if they wish to

compile these procedures along with Safran delivered procedures. Ref. chapter 7 for more information.


Chapter 6 - Creating a new Safran Project database

You need to create a new database before you can start using Safran Project Networked edition.

Microsoft SQL Server

Using Microsoft SQL Server, a user with “db-owner” role needs to be used for creating and updating the

Safran database. Best practice is to create an account named “safransa”, this ensures that the default

schema is used. The “safransa” user account is a user with special rights hardcoded into the system,

enabling you to log into the Safran database without being a defined user. On SQL-Servers the database

is initialised with a group named POWERPLAN, to which all objects later will be granted.

When setting up a Microsoft SQL Server database make sure the collation is set to

Latin_1_General_CI_AS or Danish_Norwegian_CI_AS. Database creation, initialisation and updating must

be done by a user with db owner role.

Oracle Database Server

If your DBMS is Oracle, you need to consider the tablespaces, rollback segments and whether the indices

should reside in a separate tablespace (recommended by Oracle). You need to know the name of the

tablespaces before you start installation. If these are anything but "safran_data" for the data and

"safran_index" for the indices, you need to edit the SQL-command file named "initdb.sql", in the "ORA"

sub-directory. You must replace "tablespace safran_data" and "tablespace safran_index" with the

correct names, or, if indices shall be kept with the data, remove all "tablespace safran_index".

Before installing you need a user called SAFRANSA, with at least CREATE TABLE, CREATE SYNONYM and

CREATE PROCEDURE privilege. Preferably the SAFRANSA user should be granted DBA privilege. A default

role called "SAFRAN" will be created during database initialisation, and all privilege ("all" on

tables/synonyms, "execute" on procedures) will be granted to this role. All tables must be created with

SAFRANSA as owner, and corresponding synonyms will be created through which the application will

access the tables ("Create public synonym activities for SAFRANSA.activities" will enable the application

to access the activities table without referring to its owner).

Make sure that all files described in the previous chapter are installed.


Database initiation

After this preparation, you may now initiate the database for Safran Project. Start the System

Administrator (safransa.exe) which is installed with Safran Project:

Log on to the database as system administrator (SAFRANSA in Oracle). (You will get a message informing

you that the database is not properly configured for version 3.x, which you already know. Click OK to

proceed.)

Select “Tools\ Database Objects” from the menu.

• Choose Utilities, and double-click the "Upgrade Database"-Icon


• Write directly the file Safran Catalogue\dbms-catalogue\initdb.sql or select by the Browse button.

• Press the Upgrade button to start execution. Database Tables, Procedures and Triggers will now be

created and initialised. What remains is to create Safran Project users (and groups). This is also done

from the Safran Project System Administration module, see the System Administration Guide for

details.


Chapter 7 - Updating a Safran Project database to the

latest version

For an easy and fast upgrade, use the System Administrator program, safransa.exe, installed with Safran

Project. Follow this instruction:

• Log on to the database with the “safransa” or “db-owner” user.

• Select Tools\ Database Objects from the menu


For Oracle users:

You need to know the names of the tablespaces to be used for table data and indices. If these are

anything but "safran_data" for the data and "safran_index" for the indices, you need to edit the

SQL-command files named "spdbxxx.sql", in the "ORA" sub-directory. You must replace "tablespace

safran_data" and "tablespace safran_index" with the correct names, or, if indices shall be kept with

the data, remove all "tablespace safran_index".

NB!: If you are upgrading from a Safran Project v5 database where the temp_psr script has not been

applied, you would get two messages when upgrading the database. These will tell you that

informing that there is an issue creating public synonym temp_psr and also temporary table

temp_psr. These are not errors, just continue the upgrade process and the database will be

successfully upgraded.


• Write directly or use Browse to choose the catalogue-path where all SQL files are to be found.

• Press the Upgrade button to start execution.

• If the message after execution says successfully upgraded, Safran Project is upgraded to the latest

version.


Chapter 8 - Recompile triggers and procedures

To recompile triggers and procedures you need to use Safran Project System Administration.

Follow this instruction:

• Log on to the database with the “safransa” or “db-owner” user.

• Select Tools\ Database Objects from the menu


• Write directly or use Browse to choose the catalogue-path where all SQL files are to be found (these

are in the install directory, by default that is in C:\Program Files (x86)\Safran Software

Solutions\Safran Project remember to enter either the MSS, ORA or Any folder based on the DBMS

you use.


• If your database is upgraded to the correct version you should get a window looking like this where

Recompile Triggers and Procedures are checked (If your database isn’t upgraded you will not see the

Recompile Triggers and Procedures options and you need to run the database upgrade first, before

recompiling triggers and procedures)


Troubleshooting Licensing Issues If you need to debug license issue to get more information, you can do that by adding a String value and

set the value to 1. The string value should be added here

HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Safran Software Solutions

If you have finished debugging, you can reset the string value to 0.

Starting from Safran Project v7.1 Build 117021 we have added a tool named InstallCSAPI.exe that can be

used when you need to install/reinstall a CSAPI.dll file. You start the tool, then specify the directory

where you have the new CSAPI file, choose that file and then choose to install.

Check License issue If you get the following error message related to the Safran Project here are some suggestions on how to

resolve it:

1. First you need to check that .NET Framework 4.5.2 or higher is installed.

2. You should check that the files listed here are all available in C:\Program Files (x86)\Common

Files\Safran Software Solutions:

• CPR.dll

• CSAPI.dll

• CSAPI.reg

• Interop.Licprotector.dll


• LicProtector310.dll

• LicProtector500.dll

• SafranEnvironmentValidator.dll

• Safran.Licensing.dll

• SpreadsheetGear.dll

3. Check if CSAPI.dll is registered. By default, the CSAPI.dll is stored here: C:\Program Files

(x86)\Common Files\Safran Software Solutions. To register the file, you can use the tool named

InstallCSAPI.exe. It is in the Environment\Lic\Project folder of the Safran Project install directory

(e.g C:\Program Files (x86)\Safran Software Solutions\Safran Project 7\Environment\Lic\Project )

4. Check that LicProtector310.dll and LicProtector500.dll are registered. To register these, you need

to use the Windows RegSvr32 tool.

Read Write Access If a user get this error message it means that he/she doesn’t have read/write access to the license file or

the license file folder. Make sure that all users have read and write access to the license file on the

location where it is stored.


License mismatch If you get the error message below it means that you have a mismatch between the installed Safran

Project version and the license file version, you have registered in your registry. It might be that you

have installed a version of Safran Project Personal while the License file is SPEN7.lic (Enterprise license

file) or it could be that you have installed Safran Project Enterprise and the License file used is a SPEP7.lic

(Personal license file)

To fix this issue, you should ask yourself if it is the license file that is correct or if it is the installed

software. If it is the License file that is the correct one, we recommend that you install the correct Safran

Project version, that should solve the issue. (Remember to uninstall the wrongfully installed Safran

Project version).

If the error occurs when you have installed the correct Safran Project version, you can update the

registry to point to the correct License file. In this case, you need to know where that is installed, see

Chapter 2 - Activate your copy of Safran Project for details.

A final option is to enter the registry settings for the license and delete the Users value there. You find

that setting here: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Safran Software

Solutions\Safran Project


License is locked If you get a message telling you that the license is locked. Click Activate again. If the license doesn’t

reactivate contact [email protected] to gain more activations.

The main reason for getting a locked license is that there are users activating against the same license

from different domains. If that is the case inform us at [email protected] and we will solve the issue

for you.

The other reason that will get your license locked is that you work in a network license setup, but you

got more than one license file that the users activate against. If this is the case, you should decide which

license file your organisation should use and make sure that all users have their registry setup to point to

that license file. While working out the solution for this contact [email protected] to get some

additional activations that will help you until you manage to sort out the license file issue.

mailto:[email protected]




Sub-Module says Activation Required If you look into the License Viewer and see that one of the Sub-Modules, such as Schedule Risk Analysis,

Integrated Plan etc, shows as Activation(Required), that is not an indication that you have a problem. If

you are unsure if you the license for the sub-modules is activated check the license viewer and see if it

displays as Available, that would indicate that it is working.


Contact Safran Software Solutions AS. Submit a request online: https://support.safran.com/

Email address: [email protected]

Telephone: +47 40 00 47 07

https://support.safran.com/


Documents

Installguide Safran Project 7download.safran.no/.../ver72/Installguide_for_Safran_Project_7.2.pdfInstallguide for Safran Project 7.2 5 Installation General Safran Project 7.2 installation