|
Problem(Abstract) |
Does the staff plug-in provider have to use the local
registry that WebSphere® Application Server uses, or can it use a separate
registry?
If the LDAP user registry changes, which the staff plug-in provider uses,
should you change the business process?
If you already used a custom user registry in WebSphere Application
Server, can you use it for business processes? |
|
|
|
Resolving the
problem |
- Does the staff plug-in provider have to use the local registry that
Websphere uses, or can it use a separate registry?
Yes, you can use a separate registry for Staff resolution different
from what WebSphere Application Server is using for authentication. The
three staff plug-in providers that are included are:
- LDAP (using the LDAP user registry)
- User Registry (using the user registry which WebSphere
uses for authentication and authorization)
- System (using the Local OS User Registry)
- If the LDAP user registry changes, which the staff plug-in provider
uses, should you change the business process?
No, you do not need to change the business process if the user
registry that the staff plug-in provider uses changes.
There are a number of possible user registries which can be queried. In
order to support different registries without exposing details of the user
registry in the queries within the Business Process, the queries are
defined in a generic format. This format is limited to a label of Verb and
Parameters. The generic queries are then mapped down to the actual user
registry, using a transformation file. With this type of design, there is
a layer or abstraction between the Business Process and the runtime
environment. The business process definition can remain free from any
runtime specific settings. In the event that the user registry changes,
the business process does not need to change.
- If you already used a custom user registry in WebSphere Application
Server, can you use it for business processes?
A custom user registry, which is used by WebSphere Application Server
Enterprise for authentication and authorization, can also be used for
business processes.
The three Staff Plugin Providers used for resolving Staff activities and
are included with WebSphere Application Server Enterprise are LDAP, User
Registry, and System. The User Registry Staff plug-in actually directs its
calls to the WebSphere Application Server for resolution to whatever the
application server has been set to use for authentication and
authorization.
If a custom registry is being used, then the calls for Staff activities
will use the custom registry.
Note: The User Registry Staff Plug-in Provider only supports a
subset of all of the available Verbs for staff resolution.
|
|
|
|
|
Cross Reference information |
Segment |
Product |
Component |
Platform |
Version |
Edition |
Business Integration |
WebSphere Studio Application Developer Integration Edition |
|
Windows, Linux |
5.0, 5.1, 5.1.1 |
|
Business Integration |
WebSphere Business Integration Server Foundation |
Process Choreographer |
All Platforms |
5.1, 5.1.1 |
|
|
|
|