Enterprise Manager 12c Named and Preferred Credentials

In this demo I show how to setup Named and Preferred credentials for target password management in Enterprise Manager 12c.

Do you always find yourself or your teammates typing in the password for targets in Enterprise Manager 12c? Do you have a long list of saved passwords and you do not know what save credentials are for what target? Do you have quarterly password changes that make it a nightmare to manage the passwords for targets in Enterprise Manager 12c.

Using Named and Preferred credentials will be easier to manager all credentials for your different targets in Enterprise Manager.

Setup Named Credentials

1. Log into Enterprise Manager Cloud

2. Click Setup>Security>Named Credentials

3. Click Create

4. Type in the name and description for the credential. Select the target type for the authorization and the credential type. Set the username, password and role for the credential properties. Now test the credentials by clicking "Test and Save" button.

For my example I set database instance and database credentials. This named credential is for sys account with sysdba role privileges.

5.Click the magnifying glass.

6. Select the target or type in the target name to search. Click Select button when ready.



7. Now click the "Test and Save" button.

8. You will see credential operation successful. Select the newly created credential to review the details. Now click the create icon again to add a non-sysdba credential.

9. Type in the name and description for the credential. Select the target type for the authorization and the credential type. Set the username, password and role for the credential properties. Now test the credentials by clicking "Test and Save" button.

For my example I set database instance and database credentials. This named credential is for system account with normal role privileges.

10. Click the magnifying glass.

11. Select the target or type in the target name to search. Click Select button when ready.

12. Now click the "Test and Save" button.

13. You will see credential operation successful. Select the newly created credential to review the details. Now click the create icon again to add host target credential.

14. Type in the name and description for the credential. Select the target type for the authorization and the credential type. Set the username, password and role for the credential properties. Note you can set run privileges like sudo. Now test the credentials by clicking "Test and Save" button.

For my example I set host and host credentials. This named credential is for OS authentication.

15. Click the magnifying glass.

16. Select the target or type in the target name to search. Click Select button when ready.

17. Now click the "Test and Save" button.

18. You will see credential operation successful. Select the newly created credential to review the details.

Setup Preferred Credentials

1. Click Setup>Security>Preferred Credentials

2. Select the target type  and click Manage Preferred Credentials.

3. Select target name with SYSDBA database credentials and click set.

4. Select the named credential with SYSDBA role created early  and click test and save.

5. You will see named credentials association done successfully. You will see the target you selected now has a preferred credential set.

6. Now select the target with normal database credentials and click set.

7. Select the named credential with normal role created early and click test and save.

8. You will see named credentials association done successfully. You will see the target you selected now has a preferred credential set. Now we will set the host credentials, click the preferred credentials link below the successful message.

9. Select the host target type and click manage preferred credentials.

10. Select the host and click set.

11. Select the named credential created early and click test and save.

12. You will see named credentials association done successfully. You will see the target you selected now has a preferred credential set. Now we will set the database host credentials, click the preferred credentials link below the successful message.

13. Select database instance target type and click manage preferred credentials.

14. Select the database target for database host credentials and click set.

15. Select the named credential created early and click test and save.

16. You will see named credentials association done successfully. You will see the target you selected now has a preferred credential set.

Conclusion

Setting named and preferred credential help with password management for your Cloud Control 12c targets.

You can use the named credentials when you need to log into pages that require database log in credentials.

When creating jobs you can use the preferred credentials to easily set the credentials needed to execute jobs.

Follow me on Twitter

Create Node Level Blackouts on Enterprise Manager 12c

If you plan to have server maintenance then do not forget to create your node level blackout to keep unwanted alerts on your Enterprise Manager 12c.

In this demo I show you how to create node level blackout from Enterprise Manager 12c or from command line.

You can create node level blackouts for one node or for many nodes at a time.

In this demo I will be adding memory to my vbox machine and I do not want o get alerts from Enterprise Manager 12c.

Create Node Level Blackout from Target

1. Log into OEM

2. Go to the host target homepage.

3. Click Host>Control>Create Blackout

4. Give the blackout a name or leave the default. Add comments and select a reason if needed. Un-check the box to not allow jobs to run during the blackout. Click Next

5. You can see that all targets on the host will be blacked out. Click Next

6. You can set the blackout to start immediate or at a later date and time. You can set the blackout duration to indefinite, a certain length or to an until date and time. You can also set the blackout to repeat. Click Next

I set the blackout to start immediately and the duration to indefinite.

7. Review the blackout configuration and click Finish.

8. You will see a message that states the blackout has started. Now in the search box type the host that you just created the blackout and click the arrow.

9. We can now see that all targets that are part of the host show a status of blackout.

10. I will now shutdown my server.

11. We can see that the targets are in blackout and no new alerts have come in for availability.

12. I add new memory to my server.

13. The server has been restart and all targets on my host have been restarted.

Remove Blackout

14. Back in OEM select the host which we blacked out.

15.  Click Host>Control>End Blackout

16. Click Yes

17. You will see a message that states the blackout was successfully ended. Type the host into the search box and click the arrow.

18. You will see the targets in a pending state.

19. If you wait a few minutes and click refresh you will then see the target status to online.

Create Blackouts for More Then One Target

1. Log into OEM

2. Click Enterprise>Monitoring>Blackouts

3. Click Create

4. Give the blackout a name or leave the default. Add comments and select a reason if needed. Un-check the box to not allow jobs to run during the blackout. Click Add

5. Set the target type to host and search for your targets. Select the targets that need to be in this blackout operation. Click Select

6. All the targets on the host will be part of the blackout click Next

7. You can set the blackout to start immediate or at a later date and time. You can set the blackout duration to indefinite, a certain length or to an until date and time. You can also set the blackout to repeat. Click Next

I set the blackout to start immediately and the duration to indefinite.

8. Review the blackout and click Finish

9. You will see a message that confirms the blackout has been started.

Remove Blackout

10. Search for a host that is the parent of the blackout. Select one of the targets in the blackout and click Stop.

11. You will see all targets in the blackout that will be stopped. Click Yes

12. You will see a message that states the request to stop the blackout. The status for the blackout will show stop pending. If you wait a few minutes and then click refresh the status will change to stopped.

Command Line

You can also create node level blackout from the server
$cd $AGENT_HOME/bin
$./emctl start blackout `hostname` -nodelevel

Follow me on Twitter

My webpages
http://db12c.blogspot.com/
http://cloudcontrol12c.blogspot.com/