01 - Prepare Environment

Sist oppdatert 2019-02-25 10:50

Execution period

The activities in this section are executed in the period 2/1 to 4/1.


Summary of activities

To prepare the production environment is the first major part of the technical Go Live process. The environment will at this stage contain data from the Dress Rehearsal that has to be deleted and the database restored to a ready state. This section lists all required steps to restore the environment and make it ready for the next part which is the initial data migration.


Content overview

Preparation of the environments contains the following main parts:

  1. Stop incoming traffic
  2. Clear the system of any ongoing processing and extract data
  3. Prepare EDM
  4. Prepare EnergyIP
  5. Prepare OSB
  6. Prepare SOA/BPM
  7. Prepare Reporting
  8. Add required users that will not be part of migration
  9. Start incoming traffic
  10. Verify connectivity
  11. DB Links and Access on Security Schema

Commissioning steps

Task IDCommissioning stepStart timeDeadline

Execution Organization

Step description

Done

N/AStart migration mode2/1 04:30 CET2.1Accenture

Start migration mode

Set soft blackout before starting any activities

  •  

0.0 Configure and trigger schedules

0.0.0Cancel OSB job requests2/14/1Accenture

Cancel OSB job requests

How to cancel all Job Requests for OSB schedulers

  •  

0.0.1

Verify and Configure "EMDM Triggers in applications"

2/14/1Accenture

Verify and Configure scheduler according to table "Triggers in Applications" on the following site:

EMDM - Scheduler repository

To Verify the triggers, follow below page

Verify EMDM Triggers in EIP applications

  •  
0.0.5Configure and trigger "ESB jobs"2/14/1Accenture

Configure scheduler according to table on the following site:

ESB - Scheduled Jobs Repository

Schedule the jobs:

  1. Manually configure ESB job schedules in Enterprise Manager
  2. Manually create new scheduled job requests in OSB EM
  •  
1.0 Perform verifications prior to (or in parallel) with CRB execution
Step 1.0.1 can be run in parallel with all other CRB activities down to 1.4.10: Put EIP in migration mode
1.0.1Verify EIP server configurations2/14/1Accenture

Verify EIP server configurations for Operations by executing step 2 (heading: Configuration changes) in:

Turn EnergyIP to Operations mode

Any deviations must be analyzed and resolved before this step can be closed.

  •  

1.1 Stop incoming traffic

1.1.1Turn off OHS to stop all web traffic to Elhub2/14/1Accenture

Turn off OHS to stop all web traffic to Elhub

Turn off OHS to stop all web traffic to Elhub

  •  
1.1.1.bTurn off WebPlugin access for the market parties2/14/1Accenture

Turn OFF WebPlugin access for the market parties

Turn ON/OFF WebPlugin access for the market parties

  •  
1.1.2

Turn off OAG to stop all web service traffic to Elhub

2/14/1Accenture

Turn off OAG to stop all web service traffic to Elhub

Turn off OAG (EMIF) to stop all web service traffic to Elhub


  •  
1.2 Clear the system of any ongoing processing and extract data
1.2.1Turn off scheduled procedures EnergyIP2/1


 4/1
Accenture

Turn off scheduled procedures EnergyIP

Turn off scheduled procedures in EnergyIP

  •  
1.2.2Wipe EIP/MTM and EMDM job schedules2/1


 4/1
Accenture

Wipe EIP/MTM and EMDM job schedules

Wipe EIP/MTM and EMDM job schedules

  •  
1.2.3Turn off scheduled procedures ESB

2/1

 4/1

 Accenture
  •  
1.2.4Turn off scheduled procedures ODI

2/1

 4/1

 Accenture

Turn off scheduled procedures ODI

Turn off/on scheduled procedures ODI

  •  
1.2.5Delete all messages on OSB queues. 2/1 4/1Accenture

Delete all messages on OSB queues.

Delete all messages on OSB/SOA/BPM queues.

  •  
1.2.6Delete all messages on SOA/BPM queues. 2/1 4/1Accenture

Delete all messages on SOA/BPM queues.

Delete all messages on OSB/SOA/BPM queues.

  •  
1.2.7Terminate any running processes in SOA/BPM.2/1


4/1
Accenture

Terminate any running processes in SOA/BPM.

Terminate any running processes in SOA/BPM

  •  
1.2.8Extract data from EnergyIP2/1 4/1Statnett

Extract data from EnergyIP that we want to reinsert after system clean up.

Extract data from EnergyIP

 

  •  

 1.3 Prepare EDM
1.3.1Delete data from EDM database

2/1


4/1
Accenture

Wipe EDM database

Delete all data from EDM Database


  •  
1.3.1.bDelete old migration files

2/1


4/1
Accenture

Remove old migration files

Delete EDM migration files from elhwls servers

  •  
1.3.1.cClean the quarantine folder in DMZ2/14/1Accenture

Manually clean the quarantine folder in DMZ

Clean the quarantine folder in DMZ

  •  
1.3.1.dEnsure partitons on EDM tables2/14/1Accenture

Ensure that partitioned tables have the correct partitions.

Partitioning metering value tables

  • From date - 2018-12-24
  • To date - 2019-01-28
  •  
Steps 1.3.2, 1.3.3, 1.3.4, 1.3.5, 1.3.8, 2.3.6 and 3.5.1.1 can be executed in parallel
1.3.2EDM Database Verification2/14/1Accenture

EDM Database Verification

Database verification

Database verification

  •  
1.3.3Verification of Server Configuration for EDM2/14/1Accenture

Verification of Server Configuration for EDM

Verification of EDM Application

Verification of EDM Application

  •  
1.3.4Verification of ODI Configuration2/14/1Accenture

Verification of ODI Configuration

Verification of ODI before Handover

  •  
1.3.5Verification of SQL Loader2/14/1Accenture

Verification of SQL Loader

Verification of SQL*Loader

  •  
1.3.6Verification of Folders Existence in EIP2/14/1Accenture

Verification of Folders Existence in EIP

Verification of Folders Existence in EIP.

  •  
1.3.8Verify Users able to login in EDM Web Application.2/14/1Statnett

To make sure that the EDM portal works as intended, a normal login should be performed.

Navigate to https://dam.elhub.no and log in using your EDM user. If login is successful, continue. This step should be performed by one of the EDM operators.

  •  
1.3.9Validate Completeness Report Deployment2/14/1Accenture

Validate Completeness Report Deployment

Validate Completeness Report Deployment

  •  

1.4 Prepare EnergyIP
1.4.1Back up EnergyIP DB (not HBASE)2/14/1Accenture

Logical database Backup for EIP as fallback option before deleting.

TA - ExArch - Infra - Exadata

EnergyIp DB Backup

  •  
1.4.2Pause GG synchronization2/14/1Accenture

Pause GG synchronization

Goldengate Start and Stop steps .

  •  
1.4.3Delete data from EnergyIP

2/1

4/1

Accenture

The objective of this step is to delete all data except configuration data.

Delete data from EnergyIP (overview)

  •  
Step 1.5.1, 1.7.1 and 1.8.1 can be run in sequence once the database part of 1.4.3 has been verified
Steps 1.4.4, 1.4.5, 1.4.6, 1.4.7 and 1.4.8 can be executed in parallel
1.4.4Verify roles exist in EnergyIP

2/1

4/1

Accenture

Verify that all required roles are defined in EnergyIP. (Only that roles exist, not that users are added.)

Verify Roles exist in EnergyIP

  •  
1.4.4.b

Load reference data after wipe, including special market parties.

2/1


4/1
Accenture

Load reference data after wipe, including special market parties.

Load reference data after wipe, including special market parties

  •  
1.4.4.cConfirm the schedules of EIP/MTM and EMDM jobs

2/1

4/1

Accenture

Confirm the schedules of EIP/MTM and EMDM jobs

Confirm the schedules of EIP/MTM and EMDM jobs

  •  
1.4.5Verify the data in the configuration tables in EnergyIP is correct.

2/1

4/1

Accenture

Verify the data in the configuration tables in EnergyIP is correct. If not, upload the latest configuration. (EIP Liquibase)

Verify the data in the configuration tables in EnergyIP is correct. If not, upload the latest configuration. (EIP Liquibase)

  •  
1.4.6

Create dummy metering grid area for sub grid areas.

"SGA Default Connection"

2/14/1Accenture

Sub grid areas have connection points that model how much energy they get. In EnergyIP, this are regular exchange points, so they need to point to an adjacent grid area while there is none. Therefore, we need to make a "fake" grid area to which we can point all the exchange points in sub grid area's. See EIM - Sub Grid Area - Mapping to EIP.

Create dummy metering grid area for sub grid areas(SGA Default Connection)

  •  
1.4.7

Configure parameters for reconciliation-functionality.

2/1

4/1

Accenture

The date planned for go live is 18th of February 2019. Elhub will tak over reconciliation-responsibility from and including this date. Reconciliation will run monthly, but parameter settings must take into account downtime up to several weeks. (Recon settings must take into account that FinalGridLoss runs with an offset and recon only runs once a month, hence changes up to date must be more than just three years.)

Set parameters accordingly:

recon.usageDateSince
recon.reconInProgressMaxTimeMinutes
recon.maxReconAllowedSpanDays
recon.maxDaysSinceUsgDtForGAStatusVerTimeChk
recon.enforceNoGaps
recon.changesUptoDays

How to Verify parameters recon.maxDaysSinceUsgDtForGAStatusVerTimeChk and recon.maxReconAllowedSpanDays

  •  
1.4.8Verify technical configuration for EDM2/1

4/1



Accenture

Check if the correct properties are loaded in the table.

Verify technical configuration for EDM

  •  
1.4.9Verify that EIP is empty and ready for migration2/1

4/1



Accenture

Verify that:

  • SGA Default Connection exists
  • Parties exists
    • Elhub
    • IFS
    • NECS
    • NBS

Verify EIP is empty and ready for migration

  •  
1.4.10Put EIP in migration mode2/1

4/1


Accenture

Put EIP in migration mode

How to switch modes in EIP using ConfigurationManagementTool.sh - Prepare Migration Mode

  •  
1.4.11Ensure DB health of EIP2/14/1Accenture

Identify and remedy issues with

  • Invalid indexes
  • Stale stats
  • Fragmentation

Ensure DB health in EIP

  •  

1.5 Prepare OSB
1.5.1Delete data from OSB - custom tables and re-insert tables.

2/1

4/1

 Accenture

Delete data from OSB - custom tables and re-insert tables. This includes EMIF schema, so no separate step is required for this as part of OAG.

Reset Custom DB

  •  
1.5.2Run SOA Liquibase

2/1




4/1
Accenture

Run SOA Liquibase

Run SOA liuibase

  •  

1.6 Prepare SOA/BPM
1.6.1Deploy exceptional timings for processes to SOA/BPM2/14/1Accenture

Deploy exceptional timings for processes to SOA/BPM. Change to go live values.

Deploy exceptional timings for processes to SOA/BPM


  •  

1.7 Prepare Reporting
1.7.1Delete data from reporting tool and re-insert tables.

2/1

4/1

 Accenture

Delete data from reporting tool and re-insert tables.

Deleting data from reporting tool and re-insert tables.

  •  
1.8 Golden Gate Sychronization
1.8.1Synchronize tables after source systems Truncate2/14/1Accenture

Synchronize tables after source systems Truncate (GoldenGate)

GoldenGate Configuration Steps (initial load)

DO NOT execute. will be done after the initial migration (step 2.6.8.gg)

1.8 Add required users that will not be part of migration
1.8.2.preStart EMDM service2/14/1Accenture

Start EMDM service in EIP. This is required for steps 1.8.2 and 1.10.*

Stop and Start EMDM Service in EIP

  •  
1.8.2

Add the first Elhub Super User into the system

2/1

4/1

Accenture

Add the first Elhub Super User into the system

  1. An Elhub employee must be appointed to be the first user of Elhub. The following details must be provided:
    1. Birth number
    2. First name
    3. Last name
    4. E-mail address

  2. Contact to get information of the first user.

  3. Insert the user from step 1. Refer to documentation: How to add the very first Elhub Web Portal User and assign it the Elhub Super User Role


  •  

1.9 Start incoming traffic

1.9.1Make sure all BRSs are turned off2/14/1Accenture

Verify that there are no entries with BRS_NUMER='POLL' and STATUS='Open'. If the BRS is not present in the view, then it is closed.

Verify BRSs are closed for traffic

  •  
1.9.4Turn on OAG to start all web service traffic2/14/1Accenture

Turn on both OAG instances.

Turn on OAG (EMIF) to start all web service traffic to Elhub

  •  
DO NOT turn on web portal DAM. This will be done as part of migration steps.
1.10 Verify connectivity
All steps to verify connectivity can be executed in parallel
1.10.1Verify connectivity to NBS2/14/1Accenture

Test for confirming connectivilty with NBS

Follow the steps in Verify connectivity to NBS

  •  
1.10.2Verify connectivity to NOA2/14/1Accenture

Test for confirming connectivilty with NOA

Follow the steps in Verify connectivity to NOA

  •  
1.10.3Verify connectivity to Nordpool2/14/1Accenture

Test for confirming connectivilty with NordPool

Follow the steps in Verify connectivity to Nordpool

  •  
1.10.4Verify connectivity to IFS2/14/1Accenture

Test for confirming connectivity with IFS

Follow the steps in Verify connectivity to IFS

  •  
1.10.5Verify connectivity to NECS2/14/1Accenture

Test for confirming connectivilty with NECS

Follow the steps in Verify connectivity to NECS

  •  
1.10.6Verify connectivity to ALTINN2/14/1Accenture

Test for confirming connectivilty with Altinn

Follow the steps in Verify connectivity to Altinn

  •  
1.10.7Stop EMDM service2/14/1Accenture
  •  


1.11 DB Links and Access on Security Schema
1.11.1DB Link verification2/14/1Accenture

Required DB Links are created

DB links and grant has been executed on liquid-base deployment so validating by executing document: Verify DB Links and priveleges

  •  
1.12 Other Preparation Tasks
1.12.1

Allocate CPU for migration

2/14/1Accenture

Allocate CPU for migration

CPU allocation for migration

  •