Concepts Necessary for Using UME Permissions with this Tutorial 

Before beginning with the tutorial, you should be familiar with the concept for using UME roles, actions, and permissions. For an overview of these concepts, see the following topics:

·        Authentication Between the Components Using Logon Tickets

This topic explains how the Web Dynpro authenticates the user, obtains a logon ticket for the user, which it passes to the EJB in the backend over the Web service.

·        Permissions, Actions, and UME Roles

This topic explains how the UME enforces authorizations using permissions, actions, and UME roles.

·        Permission class for your application

This topic describes how to implement an explicit permission class for your application, which you will then use in your application code to check UME permissions.

●      actions.xml file

This topic describes the structure and syntax to use for the actions.xml file, which you use to consolidate the permissions that you check in your application into actions. The administrator consolidates these actions into roles, which he or she can then assign to the users.

●      UME archive file

This topic describes the UME archive file, which contains the actions.xml file, so that the actions can be deployed to the AS Java.

Next Step:

If you are familiar with these concepts, you can begin the tutorial. See Importing the Project Templates for the Web Dynpro Application.