using the safran system administration...

Using Safran System Administration 1

Using the Safran System

Administration Tool (Last update: August 21st, 2018)


Copyright © 1999 - 2018, 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 be changed

without notice, and does not represent a commitment as to merchantability or fitness for a

particular purpose by Safran Software Solutions AS.

The software described in this manual is provided by Safran Software Solutions 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 of Safran Software Solutions AS. Safran Project, Safran Details,

Safran Enterprise Developer, Safran Planner, Safran for the Microsoft Project Platform, Safran for

Microsoft Project, Safran Web Access and Working Smarter are trademarks of Safran Software

Solutions AS. All other brands and product names are trademarks or registered trademarks are

property of their respective holders.

Document version history

Version 1 – May 2017 – Safran Project 7.2


Table of Contents Overview ............................................................................................................................................. 5

Using the Administrator's Guide ......................................................................................................... 5

Chapter 1 - Using the Safran System Administration ............................................................................. 6

Starting Safran System Administration ............................................................................................... 6

Safran System Administration Window .............................................................................................. 8

Chapter 2 - Users and security ................................................................................................................ 9

User Names and Passwords ................................................................................................................ 9

Safran Project Users ............................................................................................................................ 9

Safran Project User Groups ............................................................................................................... 10

User Access Object Type ................................................................................................................... 10

Window Access Restrictions ............................................................................................................. 11

Chapter 3 - Defining and maintaining users ......................................................................................... 12

Adding a new Safran Project user ..................................................................................................... 13

Deleting a Safran Project user........................................................................................................... 14

Create a New Safran Project User Group ......................................................................................... 15

Adding a User to a New Group ..................................................................................................... 15

Remove a User Group Membership ............................................................................................. 15

Object Ownership ............................................................................................................................. 17

Transferring ownership ..................................................................................................................... 17

Restricting Access to a Window ........................................................................................................ 19

Managing the license ........................................................................................................................ 20

Chapter 4 - Managing the Safran Project Database ............................................................................. 22

Initiating a New Safran Project Database ......................................................................................... 22

Upgrade an existing Safran Project Database to latest version ........................................................ 23

Recompile Triggers and Procedures ................................................................................................. 23

Database Objects .............................................................................................................................. 24

Look at Database Tables with Definitions ......................................................................................... 25

Look at Database Views and their Definitions .................................................................................. 25

Look at Database Triggers ................................................................................................................. 25

Look at Database Procedures ........................................................................................................... 25

Database Utilities .............................................................................................................................. 26

Execute SQL Queries ......................................................................................................................... 26

Run a SQL Command-File .................................................................................................................. 27

See all current Safran Project users (Microsoft SQL-Server only) .................................................... 27


Update Database Statistics (Microsoft SQL-Server only) .................................................................. 28

Chapter 5 - Setting Project defaults ...................................................................................................... 30

Chapter 6 - The license viewer .............................................................................................................. 31

Managing the license ........................................................................................................................ 31


Overview

Safran Project is a comprehensive project planning, project management and control software. It is

engineered to let project organizations plan, organize track and monitor their work. Built on

Microsoft SQL Server and Oracle databases it provides organizations with enterprise project

management scalability.

Your Safran Project installation includes the Safran Project application, the Safran System

Administrator tool, the Safran Report Spooler and a PDF writer.

The Safran Project System Administrator, Sysadm or SA for short, is an application tool to help you

set up your databases for Safran Project, define users, user groups, set permissions, maintain system

and versions, upgrade your project management software and more.

Using the Administrator's Guide

This guide provides the Technical System Administrator with the knowledge and skills necessary to

plan, deploy and maintain a Safran Project installation. This includes installing, configuring and

upgrading the Safran Project database structure (tables), creating users, set permissions, creating

objects and maintaining profiles.

As a technical system administrator you may want to read the Safran Project System Guide, which

outlines the Safran database and table definitions, and includes the Safran Project data model. You

may also want to refer to the Safran Project user guide “Exploring Safran Project” for details on

system objects, SQL commands, and import/export features.

You should also read the Customer Release Notes and the Installation Guide to get an update on

installation and system requirement information.


Chapter 1 - Using the Safran System Administration

The Safran System Administration application (Sysadm) is used to initiate and maintain your Safran

Project application and database. To be able to use Sysadm, a database and at least one user with

database administrator privileges is needed. Creating databases (and schemes in Oracle) is normally

among the tasks that the IS department like to consider their domain. Therefor we recommend that

you contact your IS department and work closely with them. When you are ready to install Safran

Project you should follow the steps described in the Installation guide.

If you are running a Safran Project Personal edition with a Sybase SQL Anywhere database, the

database file is part of the installation. It is already configured with a DBA user, and the Sysadm

application can be utilized after installing the software.

Starting Safran System Administration

Depending on your installation there are three ways to start the Safran System Administration tool.

1. Using an Icon. For convenient access, a windows capability allows a short-cut icon to be

added to your desktop.

2. Using the windows Start Menu. Another windows capability that is available for initiating

programs is the Start Menu.

3. Choose the program file (.EXE) from the appropriate install directory window in your

windows explorer


To login, Select DBMS system, enter your Log in ID and Password, and server and/or database name.

The system administration login and password should be provided by your IT/IS department. If you

do not know this information you should check with your IS department.

If you use Safran Project Personal you click the ODBC button. You are then allowed to browse for the

SQL Anywhere database file.


Safran System Administration Window

From the File menu you can change the database you are logged into. It is also here you find the

Save option to save changes you have done to the system.

The Tools menu lets you add and modify users and user groups, work with database tables, views,

procedures and more, create database profiles, you can restrict access on certain Safran Project

windows for regular users, define Enterprise fields to be used for this database, set network defaults

and view license key information and maintain your license.

For details on these function please see the relevant chapters in this guide.


Chapter 2 - Users and security

Safran Project provides two mechanisms for protecting against unauthorized access:

• User name and password - to prevent “outsiders” accessing your project data

• Access permissions - to control the actions authorized users are allowed to perform on the

objects in your Safran Project implementation.

User Names and Passwords

When you start your Safran Project session and select the database you wish to use in your Safran

session, Safran Project asks for your user name and password. It checks the information in the user

tables of that database to see if they are a valid combination and, if so, starts your Safran Project

session.

Safran Project Users

Control with who can access Safran Project is mainly kept by creating users, who can be granted or

denied access to Projects, Project Groups Calendars, Userfield sets, Resource sets, Symbol sets, Rule

sets, Rate sets and Profile sets. The users are kept in the table "users" with columns "login_name"

and "full_name".

Each Safran Project user must also be a database user. In order to create a Safran Project user the

user should be created in the database first. All Safran Project users should be members of at least

one database group. When a Safran Project database is initiated, a default group is initiated, and this

group is granted "all" privilege to all the tables, as well as "execute" privilege to stored procedures.

Initially, all Safran project users should be assigned to this group.

If the technical system administrator wants to differentiate the database privilege between different

groups of users a new group may be added, and some of the users moved from the default group to

this new group. The system administrator must then keep track of which users belong to which

database group, and grant and revoke privilege accordingly.


Safran Project User Groups

To simplify access control, Safran project users can be organized in user groups.

NOTE: These are NOT identical to DBMS groups; it is important to keep these two

concepts apart.

When you select the access permission for the objects in your Safran Project database, you can give

all the members of a group the same permission.

A user can be member of several groups.

Information about groups are kept in two tables: One table "user_groups" keeps the definition of

the groups, with columns "group_id", a numeric identification for the group, and "name", to keep a

descriptive name for the group; another table "group_members" with column "group_id" and

"login_name", keeps track of which user is member of which groups.

When a Safran Project database is initiated, the default group "public" is created, with group_id=1.

All new users are given membership in this group.

User Access Object Type

There are two tables for access control: "user_access", with the columns "login" (user), "object_id",

"object_type" and "access_level" (From 1(Read) to 4 (Exclusive); and "group_access" with

"group_id", "object_id", "object_type" and "access_level".

Access for the different objects is controlled from inside Safran Project.


Code Safran Project Object Access Levels

N Project 1=read,2=test,3=update,4=exclusive

S Sub-Project 1=read,2=test,3=update,4=exclusive

R Resource set 1=read,2=update

P Profile set 1=read,2=update

C Calendar 1=read,2=update

U Userfield set 1=read,2=update

W Window 1=read,2=update

A Rule set 1=read,2=update

B Symbol set 1=read,2=update

G Network Group 1=read,2=test,3=update,4=exclusive

L Global Sets 1=read,2=update

O Rate Sets 1=read,2=update

Window Access Restrictions

Whereas access must be set explicitly on standard object for a user to be able to access them,

windows are by default accessible for all users. To restrict user access to a window, this window

must be added to the list of windows with limited access. If a window has restrictions, only users

granted access to the window can open it.


Chapter 3 - Defining and maintaining users

One of the primary functions of Safran System Administration is the creation and maintenance of

Safran Project users. Every user that will be accessing Safran Project must be defined as a valid

Safran Project user.

The User Maintenance option allows you to:

• Create users

• Create user Groups

• Delete Users

• Delete User Groups

• Change/modify Users full name

• Set windows restrictions

• Transfer ownership

Select Tools>Users/Groups from the main menu or click the Users Icon on the main toolbar.

The User Maintenance window is a two -paned windows with a hierarchic out-line style window on

the left and a list of users, groups, and user details on the right.


If you in the left pane, select “users” the right pane displays a list of all defined users with login Id

and full name.

If you in the left pane clicks on the “Users” icon and select an individual user, the right pane displays

the login Id and the full name together with any group membership of that individual user.

Selecting user groups in the left pane window displays a list of defined user groups in the right pane.

Selecting a user group in the left pane, displays group memberships in the right pane.

Adding a new Safran Project user

NOTE: In Oracle, the system administrator must create a database user. In

Microsoft SQL-Server and SQL Anywhere a database login must be created before

a database user is created. A database login can only be created by a database

system administrator. Be sure that these are in place before creating

corresponding Safran Project Users, as it is not possible to create a Safran Project

User without a corresponding database user.

In the user/group maintenance window, select "Users" in the outliner pane, and then "Add user" on

top of the user-list. ("New" from the Edit menu or press Control + "N", has the same effect). The

"Initiate new Safran Project user"-window will appear:

Now you can select a name from the user name drop down, which contains users in the database

that currently are not registered as Safran Project users. Choosing a user may also initiate the "full

name" field, enabling you to choose next.


Deleting a Safran Project user

In the user/group maintenance window, select the user. Choose "Delete" on the "Edit" menu (you

may also click on the "Delete" icon on the window toolbar, press Control + "D" or drag and drop the

user to the bin). You should now be prompted to confirm deletion of the user.

NOTE: Before deleting or removing a user from your Safran Project database,

please read the “object Ownership” section carefully. Deleting users also

removes his or hers filters, layouts and report specifications


Create a New Safran Project User Group

In the user/group maintenance window, select "User Groups" in the outliner pane, and then "Add

user" on top of the user-list. ("New" from the Edit menu or press Control + "N", has the same effect).

The "Initiate new Group" - window will open:

You should now enter the new group's name. Having done that you click "OK", and the new group is

created and ready to accept members.

Adding a User to a New Group

In the user/group maintenance window, select the user. The user name and full name will appear in

the right pane; above the list of groups the user currently is a member of. Drag the icon to the left of

the name, and drop it on the group to which you want the user added.

Remove a User Group Membership

In the user/group maintenance window, select the user, and the list of groups the user is a member

of, will be shown. Click on the group, and drag it to the dust bin in the bottom right corner. This will

remove the group from the list.

OR:


Select the group, and the list of users will be shown. Drag the user over to the dust bin instead. The

user will disappear from the list.

NOTE: You cannot remove a user from the "Public" group!


Object Ownership

By default, the user creating any of the Safran objects (projects, symbol sets, resource sets, rule sets,

userfield sets, calendar sets, profile sets and user saved report specifications and filters) is defined as

the Owner of the objects.

For all objects other than filters and report specifications the owner assigns user access to these

objects. All users may use filters or report specifications created by any user, but they are not

allowed to modify or alter any of these.

When you remove a user from the system, the object owner is no longer valid. The system

administrator may change Ownership from one user to another on all objects.

Removing a user also remove his or hers filters, layouts and report specifications as these are

“private”. However, if a user’s report specifications or filters should be available to other users, you

should transfer ownership to a new user.

Transferring ownership

Transfer object ownerships before removing a user from the system, select Tools>Users/Groups. In

the User Maintenance window highlight the owner/user and select the Owned Objects option (the

Key icon, or Edit>Ownership). You will now see the full list of all objects defined by and owned by the

selected user.

To transfer ownership, select the object type and transfer all objects of this type by using the

Transfer all to option or transfer named object individually to any users by selecting the transfer to

option and the user name of the new owner.


Restricting Access to a Window

You may want to restrict access from some of the areas or features of Safran Project, allowing only

some of the users to e.g. update project information, update calendars, run the initial Baseline, have

Access to the SQL window etc. To do that, you restrict access to the relevant window.

From the main menu choose "Tools", then "Window Restrictions". The window for window access

control opens up. In the left pane of this window there is a tree view with "Restricted Windows" on

top, exploding to show the names of all windows with access restrictions implemented.

Initially the right pane gives you the same list of restricted windows. Selecting a window-name in the

left pane gives you the usual access-control module, enabling you to grant/revoke access to the

window, to users and groups in the usual manner.

Press the New icon, or select New from the short-cut menu to add a new window to the restricted

windows pane. This open a window with the list of Safran Windows to select from. By default, when

adding a window restriction, it will restrict all users or groups, if you want to provide some

users/groups access anyway you do that by selecting the restriction in the left part of the window,

and then add users or groups in the right part.


Managing the license The License Viewer is included 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


To free up or transfer a license from a user, you would:

1. Expand the Safran Project item under Modules.

2. Expand Users and set focus on the username of the user you are going to remove from the

license

3. Click Lock, you will now notice that the number of available licenses is increased by 1. This

license can now available to be used by another user.

Note: The license of Safran Project is disconnected from the users. There can be several users in the

Safran Project database, but not all of these need a license. The license only controls who can start

Safran Project. Let’s say you have removed a license from a user that is not going to use Safran

Project anymore, even after removing the license he will still be a user in the Safran Project

database. If you also want to remove him as a user in the database that can certainly be done, but

before doing that it is recommended to transfer the ownership of the object this person owns

before removing the user from the database.


Chapter 4 - Managing the Safran Project Database

This chapter contains information on how to initiate a new database for Safran Project, how to

upgrade your Safran Project database to latest version and use the database utilities and system

objects features of Safran System Administration. For details on tables and table definitions please

see the Safran Project System Guide - System tables and definitions.

Initiating a New Safran Project Database

From the main menu choose Tools>Database Objects. Then highlight "Utilities", and double-click

"Upgrade Database". You should now see the "Database Upgrade" - Window, with an edit to input

the directory where the initialization files reside (if the SQL-files have not been moved your will find

these in the ANY, ORA or MSS folder of the Safran Project install directory). You can enter the path

directly in the edit box, or use "Browse" to select the correct directory.

When the correct path is entered, the "Status message" should display "Ready to initiate Safran

Project Database". Push the "Upgrade"-button to start database initialization. The SQL-command

files will be run - if any errors should occur, you will get a message asking you to Continue or abort,

telling you what the problem is. Normally no such problems should occur. After creating the

necessary database objects, the database is ready for Safran Project use.

NOTE: When setting up a database make sure the collation is set to

Latin_1_General_CI_AS or Danish_Norwegian_CI_AS. Database creation,

initialization and updating must be done by a dbo account to ensure the default

schema is used.


Upgrade an existing Safran Project Database to latest version

NOTE: For Oracle users: You need to know the names of the table spaces 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".






When the correct path is entered, the "Status message" should display "Ready to update database

from version <current version number>". Push the "Upgrade"-button to start database upgrading.

The SQL-command files will be run - if any errors should occur, you will get a message asking you to

Continue or abort, telling you what the problem is.

Normally no such problems should occur. After performing any changes to the database, all Safran

procedures and triggers are recompiled.

If the database already is upgraded to the latest version, the status message will display "Database

already upgraded to <New version>". You will have check-boxes asking if you want to recompile

procedures and/or triggers. By checking one or both of these, and pressing the "Upgrade"-button, re

compilation will be performed.

Recompile Triggers and Procedures When installing new builds of Safran Project it is recommended to always recompile triggers and

procedures as these might have changed since the previous build used.







You will now get a window telling you “Database is already upgraded to version <verison number>.

You will also see two checkboxes, Recompile Triggers and Recompile Procedures, check these and

click Upgrade. This recompile the triggers and procedures.

Database Objects

Using Safran System Administration you can browse through different types of database objects;

Tables with their definitions, Database views and their definitions, view database triggers and the

procedures stored in the database and check their source, and invoke a set of database utilities.

From the main menu choose "Tools", then "Database Objects". This will open the Database Object

Window:

All the lists and definitions are display only.


Look at Database Tables with Definitions

From the database objects window, select "Tables" in the left pane. This places a list of all defined

tables in the right pane. If you expand the "Tables"-entry in the left pane, all the tables will be listed

under this entry. Selecting one of those gives you the list of column and column types in the right

pane.

NOTE: A detailed table and column definition together with a database model can

be found in the Safran Project System guide.

Look at Database Views and their Definitions

From the database objects window, select "Views" in the left pane. This places a list of all defined

Views in the right pane. If you expand the "Views"-entry in the left pane, all of the views will be

listed under this entry. Selecting one of those gives you the view definition in the right pane.

Look at Database Triggers

From the database objects window, select "Triggers" in the left pane. This places a list of all defined

triggers in the right pane. If you expand the "Triggers"-entry in the left pane, these will be listed

under this entry. Selecting one of those gives you the trigger definition (source) in the right pane.

Look at Database Procedures

From the database objects window, select "Procedures" in the left pane. This places a list of all

stored procedures in the right pane. If you expand the "Procedures"-entry in the left pane, all the

procedures will be listed under this entry. Selecting one of those gives you the procedure definition

(the source code) in the right pane.


Database Utilities

The database utilities of the database objects option allow you to:

• Execute SQL queries

• Run SQL command files and scripts

• Upgrade your Safran Project database

• See all current Safran Project users (MS SQL-Server only)

• Update Database Statistics (MS SQL-Server only)

Execute SQL Queries

From the "Utilities" section of the "Database Objects" window, double-click the "SQL Queries" - icon.

You will then be presented with a window for entering SQL commands.

You can open a multiline edit window by double clicking in the single line database queries window.

You can use this window to write more complex SQL statements. From this window you may also

save your SQL statements to file for later re-usage. This window also allows you to open and run SQL

queries previously saved to file.

NOTE: Be aware that commands entered in this window will be executed and

committed immediately, and there are no "Oops…" options. If you delete


something here, it stays deleted. So, be careful what you ask for, because you just

might get that!

Run a SQL Command-File

From the "Utilities" section of the "Database Objects" window, double-click the "SQL Queries" - icon.

This action will open the "Run SQL Command File" window.

In this window you are supposed to enter a SQL-Command file name. You may either enter the file

name directly into the edit, or use the "Browse" button to open the standard "Find File…" window.

You must also inform the system whether each command should be committed after execution

(default), or all commits shall be done after execution of the document. (Sybase SQL-server requires

commit after each command for all commands that may include table creation.) You must also

specify the command delimiter used in the command file, default is ";".

To execute the command file, press the "Run"-button. The system then executes the commands

within the file, informing you of any (non-fatal) errors occurring during execution, and giving you the

options to continue or abort if errors occur. When the operations are successfully completed, the

window gives you a message telling you the number of lines in the file.

See all current Safran Project users (Microsoft SQL-Server only)


From the "Utilities" section of the "Database Objects" window, double-click the "Logged in users" -

icon. This action opens up a window looking like this

If you suspect that any Safran Project user hangs, and that this may be caused by another process,

you may select the "Show Blocked Processes Only"-option. This sets a filter on the users-list,

showing only users that currently are waiting for a database lock to be released. To identify the

blocker, note the number under "Blocked by", and re-push the button (now renamed to "Show All

Processes"). If the blocker is a Safran Project user, you can find him as a Process ID (If there are many

users, pushing the "Process ID" header will sort the list on Process ID). If the blocking process ID is

not on the list, it does not belong to a Safran Project user.

Update Database Statistics (Microsoft SQL-Server only)

From the "Utilities" section of the "Database Objects" window, double-click the "Update Statistics" -

icon. This brings up this window:

Microsoft SQL-server keeps track of the index configuration and the table layout, as well as the

"spread" of the index keys, in system tables. These are used to optimize database queries. When a

lot of changes and/or insertions/deletes have been done on a database table, the information stored


in these tables becomes incorrect. As a result of this, wrong indexes may be selected for data

retrieval, and performance drops. The tables initially selected, are the ones who most commonly

affect report performance etc. You may switch selection on and off for each individual table. When

you have checked off the ones whose statistics you want to update, you press "OK", and the update

statistics process starts. This process may take some time.


Chapter 5 - Setting Project defaults

Many firms and organizations use standard corporate definitions for calendars, user fields, resource

definitions, resource profiles and symbols.

To support and strengthen the corporate set-up, Safran Project support a network default definition.

Choose the Tools>Network defaults option to open the defaults set-up window. Here you can select

the network “configuration” to be used as default for all new networks to this database. It saves the

users time when defining new networks and it ensures that corporate standards are used. However,

when you create a new network in Safran Project, you can select other sets and overwrite these

standards.


Chapter 6 - The license viewer

Safran Project is a licensed software. A Software key is used to control the license and key

installation is required to get Safran Project to run. As a system manager you can use the License

viewer option to manage your license. In order to manage the license you need to be logged inn

using the safransa user account.

Managing the license The Safran license is managed in a license file, to be able to get a license the user needs to be

configured as a user in the database. When logging into Safran Project for the first time the database

user will be assigned a license (if available) and the user is added to the license file. If you need to

remove a license from a user, you use the license viewer to lock the user’s license. By doing that you

free up that license for others to use. The license will then be assigned to the next person without a

license that logs into Safran. If you want to prevent the user that you removed the license from to

once again get a license you should, after freeing up the license goto the database and lock his user

account to the Safran database.

Lock: Locks/deactivates a user in the license file, freeing up a license. Put focus on the user from

whom you want to deactivate a license, then click Lock to release the license.

Activation Key: Option to apply additional keys to license

Transfer License: Removes a user license on the Activation server and enables you to transfer the

license to another computer/user

The options button lets you set on usage logging and set where the log file is to be located.

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


The license viewer is also described in the Safran Project Installation guide.

using the safran system administration...

Documents