Está en la página 1de 22

FDM EE Tutorial: How to change the ODI SUPERVISOR

Monday, April 4, 2016

As part of installing and configuring FDM EE, securing EPM is typically forgotten. As you might know, FDM
EE is built on top of ODI 11g. Sadly ODI is configured with the factory default credentials, which imposes a
security risk. The more because ODI is not only accessible through the ODI Studio (which is per default
not installed), but also through the web based ODI Console.

What will you learn?

During this tutorial you will learn how to enhance ODI security by changing the "SUPERVISOR" password
without breaking FDM EE.

The Steps
Below the main steps in order of execution:
1. Change the password for the ODI agent through Enterprise Manager;
2. Change the password for ODI through ODI Studio;
3. Validate the ODI agent connection from ODI;
4. Configure the new password in FDM EE.

Step 1 - ODI Agent (EM)
1. Start Weblogic Admin Server
2. Login to Enterprise Manager (http://localhost:7001/em) and use the "epm_admin"
account to login
3. In the left pane, select "EPMSystem" in Farm_EPMSystem -> Weblogic Domain
4. In the middle pane, select Credentials in Weblogic Domain -> Security

5. Select "SUPERVISOR" and click "Edit"

6. Change the password and click OK

7. Logout from Enterprise Manager

8. Shutdown Weblogic Admin Server

Step 2 - ODI Studio (Security Navigator)

1. Start ODI Studio
(\oracle\product\11.1.1\Oracle_ODI_1\oracledi\client\odi64.exe) and login
2. Open "Security Navigator" from the View menu
3. In the left pane, expand the "Users" section if not already so
4. Right click on "SUPERVISOR" and select "Open"
5. In the right pane, make sure tab "Definition" has been selected
6. Click "Change password" and change the password (to be identical to the previously
created password)
7. Make sure to save the changes
8. Important: Logout ODI Studio
9. Optional: Restart FDM EE Windows Services "Oracle Hyperion FDM Enterprise Edition -
Java Web Application (epmsystemX)"

Step 3 - Validate ODI Agent connection (Topology Navigator)

1. Login ODI Studio with the newly created password
2. Open "Topology Navigator" from the View menu

3. In the left pane, right mouse click on OracleDIAgent in Agents and select "Open"
4. In the right pane, just under tab "OracleDIAgent" click "Test"
5. If not successful, you probably forgot to logout from Oracle Studio and re-login?

6. Close ODI Studio

Step 4 - Configure the new password in FDM EE

1. Login to Workspace and open FDM EE

Oracle EPM & BI Blog

FDMEE Tutorial: How to Change the ODI SUPERVISOR
Posted by Terry Ledet | Oracle FDMEE , | Data Integration

Share This Post

During the installation and configuration of Financial Data Quality Management Enterprise
Edition (FDMEE), the Oracle Data Integrator (ODI) master repository and agent are
installed with a default username of SUPERVISOR and SUNOPSIS. Securing the Oracle
Hyperion EPM environment by changing the SUPERVISOR password is not a single step but
requires changes in three separate interfaces: FDMEE, ODI Studio Console, and WebLogic /
Oracle Enterprise Manager.

This post will proceed with version of Oracle EPM installed on Windows Server
2012 R2. The steps for of EPM are the same except for Operating System
1. Log into Workspace.
2. Navigate –> Administer –> Data Management.

3. Select the Setup tab and then System Settings.

4. Select ODI from the Profile drop down.

5. Key the new ODI password for User Name SUPERVISOR and then select Save.

6. After a successful Save, the message “Your changes have been saved” will display.

7. To verify the ODI SUPERVISOR password has changed, select “Check ODI
Connection," which will display an Error. Select OK to close the error.
8. Select ODI Studio from Apps By Name.

9. Key the User “SUPERVISOR” and the Password “SUNOPSIS,” and then select OK.

10. Select View –> ODI Security Navigator.

11. Select Users –> Supervisor then right click and choose Open.

12. Select Change password.

13. Key the New Password and then select OK.

14. Select File –> Save.

15. Select View –> ODI Topology Navigator.

16. Select Agents –> OracleDIAgent and then double click OracleDIAgent.
17. Select Test, which will generate an error. This verifies the password has changed.
Select OK to close the Error dialog box.

18. Select Start Admin Server for WebLogic Server Domain from Apps By Name.

19. Once the Admin Server has started, select Admin Server Console from Apps By

20. Key the WebLogic Username and Password created during installation and then
select Login.

21. Select Oracle Enterprise Manager from Helpful Tools.

22. Key the WebLogic User Name and Password created during installation and then
select Login.

23. If the Accessibility Preference dialog box appears, update if needed (the default is
displayed below) and then select Continue.

24. Select and expand WebLogic Domain.

25. Select EPMSystem –> WebLogic Domain –> Security –> Credentials.
26. Expand and select oracle.odi.credmap –> SUPERVISOR.

27. With SUPERVISOR selected, click Edit.

28. Key the updated password and then select OK.

29. Return to FDMEE –> System Settings –> ODI and select Check ODI Connection,
which will display a successful test of the ODI agent.

30. Return to ODI Console and select ODI –> Disconnect “SUPERVISOR.”

31. Select ODI Connect.

32. Key the User “SUPERVISOR” and Password “Updated One,” and then select OK.
33. Select View –> ODI Topology Navigator.

34. Select Agents –> OracleDIAgent and then double click OracleDIAgent.

35. Select Test, which will generate an Agent Test Successful dialog box. Select OK to
close the dialog box.
2. In the left pane, select tab "Setup" and click "System Settings"
3. In the right pane, select ODI as profile type

4. Change the "ODI Password" and click Save (upper most right)
5. Click "Check ODI Connection" in order to validate the connection to the agent

6. Congratulations,you have changed the password successfully

Final Notes
As you noticed changing the "SUPERVISOR" password can be a bit cumbersome. However from a security
perspective worth the effort. I would avoid using complex passwords that include special- and high ASCII
characters. It could very well break FDMEE and/or ODI.