TUI Migration Plan 2010
TUI - Transformation of Postcode logins to Named logins
Preparing user data
A list of users will need to be provided in a spreadsheet containing the following information:
- Service Number
- First Name
- Last Name
- Windows Username
The username should not contain any special characters, except ‘.’.
Return to top
Importing and Exporting
A full database export will be taken prior to any changes being made on the system as this can be restored in case of unexpected outcome.
A live to test data import will need to be carried out so the users/data is current.
The user list (spreadsheet) will be imported into a table with the following name and column names:
[account]_personnel.frs_tui_data
- tui_user
- tui_rank
- tui_win_account_name
- tui_servno
Return to top
Update Routines
The following routine will select the users from the imported table (frs_tui_data) and insert it into fpassport (create TUI records), insert
into f_passport_person (TUI record in Personnel Record Card) and insert into forauser (Create Oracle accounts).
Personnel > Supervisor > More personnel data updates > Insert into fpassport
This routine will need to run on SOPHTLOGIC Live TUI Server to create the users TUI records. The common password would have already
been discussed and agreed.
It will also be need to run on the FRS database to create TUI records, create Personnel TUI records and create Oracle users.
Return to top
Migration to New Named Logins
Once the implementation of the named logins has been completed, the system will need to be changed over to support the named logins.
There are various tasks that need to be carried out in order for the users to use the system with the named logins.
A new set of privilege profiles should be added. FRS (with our assistance) should ensure the profiles are concise. It is advisable to
identify groups/profiles to perform a phased roll-out. IT Staff/smaller groups to start with.
All saved queries will need to be moved over to the new usernames.
Return to top
Acceptance by FRS
After the roll-out of the named logins the final stage will be to provide FRS with a report to maintain the migration. We will do this by creating a
database table and publishing it as a querybuster that will lookup from the old postcode to the new username. (This will be part of the TUI creation routine.)
Once acceptance has been decided by the FRS, we will need to drop the old users, making sure no objects are attached as we do not want to drop users and all owned objects.
The users will need to be deleted from the following tables:
Return to top
Data Restore Procedure
The system can be fully restored back to the original postcode logins should the need arise.
Contact the SOPHTLOGIC Support Desk for assistance.
Return to top
Testing
During the testing phase a test of the global TUI can be achieved by following the steps:
A user can validate their TUI licence and check to see the correct username is displayed on the TUI Console i.e. The userid should display
the windows account name ‘John.Smith’ opposed to postcode ‘STN441’
Once the user has validated their TUI account successfully a checkout can be performed to ensure they are receiving the correct work (jobs, incidents etc...)
If the checkout is unsuccessful the system is likely to be reporting the following error:
“ORA-01017: invalid username/password; logon denied”
In the event of this happening please contact SOPHTLOGIC Support Desk.
Return to top