In 'FDMEE System Maintenance Tasks' blog series, we have already covered the following topics :
Manual implementation:
FDMEE: System Maintenance Tasks: Maintain FDMEE Data Tables
FDMEE: System Maintenance Tasks: Maintain ODI Session Data
FDMEE: System Maintenance Tasks: Maintain Application Folder
FDMEE: System Maintenance Tasks: Maintain Process Tables
FDMEE: System Maintenance Tasks: Maintain EBS GL Balances Table
Automation:
Automation of 'Maintain FDMEE Data Tables' System Maintenance Task
If you have not already gone through the above articles, I would suggest you read them first to get a comprehensive understanding of all the Hyperion Financial Data Quality Management (FDMEE) System Maintenance Tasks.
Note:
Manual implementation:
FDMEE: System Maintenance Tasks: Maintain FDMEE Data Tables
FDMEE: System Maintenance Tasks: Maintain ODI Session Data
FDMEE: System Maintenance Tasks: Maintain Application Folder
FDMEE: System Maintenance Tasks: Maintain Process Tables
FDMEE: System Maintenance Tasks: Maintain EBS GL Balances Table
Automation:
Automation of 'Maintain FDMEE Data Tables' System Maintenance Task
If you have not already gone through the above articles, I would suggest you read them first to get a comprehensive understanding of all the Hyperion Financial Data Quality Management (FDMEE) System Maintenance Tasks.
Note:
- The demonstrating Hyperion environment has the 'Windows Server 2012 R2 Standard' operating system.
- The demonstrating Hyperion environment has 'Oracle database server 12.2.0.2 (18c)' as backend database.
- This post has been written and associated activities have been demonstrated on Oracle FDMEE version 11.1.2.4.220.
- There is no outage required on the FDMEE application to execute these scripts. But it is advisable not to run any data loads during the activity.
- Don't forget to take complete FDMEE schema backup before attempting to run these scripts.
- Different paths and folder names mentioned in this post may slightly vary for different Hyperion setups but at large it should be the same.
Command syntax of FDMEE batch utility executescript.bat:
----------------------------------------------------------------------------------
executescript <username> <password> "<script name>" "<parameters>" <execution mode>
Where:
executescript <username> <password> "<script name>" "<parameterdisplay1=value1>" "<parameterdisplay2=value2>" <SYNC | ASYNC>
If you are going to use an encrypted password (which is the recommended best practice), following will be the command syntax:
executescript <username> <password | -f:password.txt> "<script name>" "<parameterdisplay1=value1>" "<parameterdisplay2=value2>" <SYNC | ASYNC>
You will find the configuration steps for password encryption in the FDMEE admin guide as shown below:
You need to ensure that your encrypted password.txt file is placed in the location defined in Navigate-Administer-Data Management-Setup tab-System Settings-Encrypted Password Folder.
----------------------------------------------------------------------------------
executescript <username> <password> "<script name>" "<parameters>" <execution mode>
Where:
- <username>: is your FDMEE user running the script
- <password>: can be either the hard-coded password or a file with encoded password (-f:filename)
- <script name>: is the name of the script registered in Script Registration page (not the python script filename). You find the script name here: Navigate-Administer-Data Management-Setup tab-Script Registration
- <parameters>: are the script parameters in the form "Display Name=Parameter Value"
- <execution mode>: is either SYNC (synchronous) or ASYNC (asynchronous). SYNC—Process runs immediately and control returns when process completes. ASYNC—When the ODI job is submitted, control returns. The load process continues to execute in ODI.
executescript <username> <password> "<script name>" "<parameterdisplay1=value1>" "<parameterdisplay2=value2>" <SYNC | ASYNC>
If you are going to use an encrypted password (which is the recommended best practice), following will be the command syntax:
executescript <username> <password | -f:password.txt> "<script name>" "<parameterdisplay1=value1>" "<parameterdisplay2=value2>" <SYNC | ASYNC>
You will find the configuration steps for password encryption in the FDMEE admin guide as shown below:
You need to ensure that your encrypted password.txt file is placed in the location defined in Navigate-Administer-Data Management-Setup tab-System Settings-Encrypted Password Folder.
Automating 'Maintain ODI Session Data' System Maintenance Task:
-------------------------------------------------------------------------------------------------
In this post, we will see how to automate 'Maintain ODI Session Data' System Maintenance Task. I suggest you to first read this post FDMEE: System Maintenance Tasks: Maintain ODI Session Data for theoretical understanding, manual implementation, and post-execution activities of 'Maintain ODI Session Data' System Maintenance Task.
In this post, we will see how to automate 'Maintain ODI Session Data' System Maintenance Task. I suggest you to first read this post FDMEE: System Maintenance Tasks: Maintain ODI Session Data for theoretical understanding, manual implementation, and post-execution activities of 'Maintain ODI Session Data' System Maintenance Task.
When you execute ‘Maintain ODI Session Data’ purge script manually from Data Management console, it seeks one input parameter: Days to keep ODI Sessions
To run ‘Maintain ODI Session Data’ purge script using executescript.bat command-line utility below is the command syntax:
executescript username password "MaintainODISessionData" "Days to keep sessions=EnterDaysInNumber" SYNC
executescript username password "MaintainODISessionData" "Days to keep sessions=EnterDaysInNumber" SYNC
You need to enter the number of days you want to retain data for in ODI tables.
Note: Maintain ODI Session Data scrip takes some time to execute so its advisable not to purge too much in one go.
Note: Maintain ODI Session Data scrip takes some time to execute so its advisable not to purge too much in one go.
Suppose using FDMEE Admin user, you want to run 'Maintain ODI Session Data' purge script for 90 days (3 months) i.e. you want to delete all the ODI Sessions details keeping only last 90 days (3 months) details.
In order to achieve the above goal, create a batch script name 'MaintainODISessionData.bat' under folder E:\Admin\scripts having the following content:
MaintainODISessionData.bat:
--------------------------------------------------
@echo off
--------------------------------------------------
@echo off
REM Set the value for the variables
set "username=Admin"
set "password=YourAdminPassword"
REM Clear the content of existing logfile
rem.> %logfile%
REM Navigate the executescript.bat utility folder
cd "E:\apps\OracleEPM\Middleware\user_projects\epmsystem_fdm\FinancialDataQuality"
REM Run executescript to perform "MaintainODISessionData" for the mentioned days to keep ODI Sessions
set "password=YourAdminPassword"
set "DaysToKeepODISessions=90"
set "logfile=E:\Admin\scripts\MaintainODISessionData.log"
REM Clear the content of existing logfile
rem.> %logfile%
REM Navigate the executescript.bat utility folder
cd "E:\apps\OracleEPM\Middleware\user_projects\epmsystem_fdm\FinancialDataQuality"
REM Run executescript to perform "MaintainODISessionData" for the mentioned days to keep ODI Sessions
> %logfile% (
echo call executescript %username% %password% "MaintainODISessions" "Days to keep sessions=%DaysToKeepODISessions%" SYNC
call executescript %username% %password% "MaintainODISessions" "Days to keep sessions=%DaysToKeepODISessions%" SYNC
)
cd E:\Admin\scripts
Change the paths and variables mentioned in the script as per your requirement and FDMEE application setup.
Now login to your FDMEE server, open an Administrator Command prompt and run MaintainODISessionData.bat.
After completion of the script your MaintainODISessionData.log will be generated in below format:
After completion of the script your MaintainODISessionData.log will be generated in below format:
To verify whether your process ID has successfully completed or not, you can navigate to Process Details page (In Data Management console, click on the Process Details link under the Workflow tab—Monitor—Process Details):
Click on the 'Show' button against the Process ID to open the corresponding log file to see more details.
That's all for this post.
I hope this article has helped you.
Your suggestions/feedback are most welcome.
Keep learning and Have a great day!!!
I hope this article has helped you.
Your suggestions/feedback are most welcome.
Keep learning and Have a great day!!!
0 comments:
Post a Comment