After the roles are in place, the next step to implement declarative security
is to associate these roles with specific components or component interfaces.
When a role is assigned to a component, MTS will honor members of the role whenever
they request to use an object from the component. If a user who is not a member
of any of the roles makes a request for object instantiation, the request will
For any component or component interface, any number of roles can be assigned
at the discretion of the administrator of the MTS Server.
The following steps enable you to assign a role to a component:
STEP BY STEP
16.7 Assigning a Role to a Component
Expand the package that contains the component to which you want to assign
In the Components folder, expand the component.
You will see two folders off of the components. Expand the one titled Role
Membership. By default, no roles are assigned to a component when it is first
added to a package.
With the Role Membership folder selected, click on the Action menu, choose
New, and then choose Role. This brings up the Select Roles window shown in Figure
FIGURE 16.9 Role membership enables you to assign a role to a component
From the Roles frame, select the roles you want to assign to the component.
You may simultaneously select as many roles as you want by clicking on each one.
Now the Role Membership folder will contain an object for each role that was
assigned to it.
NOTE - Components With More Than One Interface:
Some MTS components might export more than one interface. When you assign a role
to a component, it enables users in that role to use only the default interface
of the component. If the component has additional interfaces, you must remember
to assign roles to each interface as desired. This is done in the exact same way
as assigning roles to components, except the Role Membership folder will be a
child of a specific interface. Additional interfaces are listed in the Interfaces
folder off of the component.