Obtaining authorized access

To instantiate the Thread Manager, your client or component must execute with with the system identity or an identity that is in the ThreadManager role. These are the recommended ways to satisfy this constraint:

• Start threads from a service component and create the Thread Manager proxy in the service’s start or run method. These methods execute with the system identity.

• For a component that is pooled or shared, create the Thread Manager proxy in the component’s class constructor, the setSessionContext or setEntityContext method (for EJB components), or the setObjectContext method (for CORBA components). All of these methods execute with the system identity.

• For a component that is not a service and not pooled or shared:

  • Delegate Thread Manager operations to another component that is pooled or shared, or

  • Run the component with an identity that is in the ThreadManager role.

• For a base client, connect to EAServer with a user name that is a member of the ThreadManager role.

  ThreadManager privileges can be dangerous User accounts with ThreadManager role membership can use the Thread Manager to implement denial of service attacks or to stop thread groups. Treat ThreadManager role accounts with the same care as you would Admin role accounts.

Copyright © 2005. Sybase Inc. All rights reserved.

View this book as PDF