Roles define what users and groups of users are permitted to do, such as access components for read-only, read and write, and administration (start, stop, or execute methods).
When you install and deploy Enterprise Portal into EAServer, the J2EE roles defined in EP are automatically mapped to EAServer roles. If you add new EP roles, you should map the roles to EAServer roles. In the Servers folder in Jaguar Manager, the following folders each contain role-associated properties that you need to map to J2EE roles:
Applications
Web Applications
Packages
For each of these items, click on the icon to expand the folder contents, then for each item in the folder:
Select the item, right-click, and select Properties.
Display the Role Mapping tab, and configure the mappings as follows:
To add a logical J2EE role name, click Add, and enter the role name.
To specify the mapped EAServer role, click in the right column, opposite the J2EE role to be mapped, then use the pull-down menu to choose the mapped role.
Optionally, add a description of the role in the field labeled Description.
Click OK to save the changes.
If necessary, define new EAServer roles to be used by callers of the component and map them to J2EE roles in the package properties.
For more information about role mapping and how to create roles in EAServer, see the EAServer Security Administration and Programming Guide.
