EDS365 - How to change parameters in the Engagement Workbook prior to a continued OSC - WKB209264
OBJECTIVE or GOAL
Change parameters in the Engagement Workbook prior to a continued OSC.
If there are any changes in the Empower environment that cause the ODI to fail to connect to the Oracle database, the Engagement Workbook must be updated with the new entries. When updated, it must be reloaded via ODI into the EDS365 Oracle database prior to the next OSC.
ENVIRONMENT
- EDS365 - all versions
PROCEDURE
-
Sheet 1 - Edit the engagement workbook to ensure that all the connection details are correct for the Empower server. The required entries are:
- Empower Node
- SID
- Host
- Service
-
Sheet 2 - Any change to the EMPOWER NODE (column B in sheet 1) must be replicated exactly in the EMPOWER_NODE_ID column of sheet 2.
-
Sheet 3 - When the Engagement workbook has any updates made in an EDS365 environment that already contains data, if the customer is resuming the OSC and NOT running an FMI, there are some flags that must be altered.
- NEW_ENGAGEMENT_ID = N (Otherwise, you will get duplicate projects in the project hierarchy.)
- TRUNCATE_ALL_DATA must be removed (Simply inputting an N will not stop the truncating.)
- After the edited Engagement_workbook is placed back in the BIC_FILE_DROPOFF folder on the EDS365 server, it must be reloaded in ODI. In order to do this, open the ODI Studio:
- On the Operator tab, under "Load Plans and Scenarios", select the EDSIP_RUN_LOAD_ENGAGEMENT_WORKBOOK scenario, right-click, and execute (selecting the BIMAgent01 as the logical agent):
- When this procedure completes, a check can be made in SQL Developer to ensure that the node connection details are correct, by viewing the B_NODE_CONTROL_TA:
ADDITIONAL INFORMATION