| Exit Print View | |
Sun OpenDS Standard Edition 2.2 Deployment Planning Guide |
|
1. Overview of Sun OpenDS Standard Edition
2. Overview of the Directory Server
3. Overview of the Proxy Server
4. Building Blocks of the Proxy Server
Load Balancing Using the Proxy
Data Distribution Using the Proxy
5. Example Deployments Using the Directory Server
6. Example Deployments Using the Proxy Server
7. Simple Proxy Deployments Using the Command Line Interface
A workflow is defined by a naming context (base DN) and a workflow element that define how the Sun OpenDS Standard Edition proxy should handle an incoming request. A workflow must be registered with at least one network group, but can be attached to several network groups.
A network group can point to several workflows when the naming context of the workflows are different. However, several network groups can point to the same workflow when the network group QOS policies are different, but the naming context of the workflow is the same.
For example, if a Sun OpenDS Standard Edition proxy has the following network groups (as illustrated in Figure 4-2), where:
Network Group 1 with a bind DN of **,l=fr,dc=example,dc=com
This network group is associated to Workflow 1, with naming context l=fr,dc=sun,dc=com
Network Group 2 with a bind DN of **,l=uk,dc=example,dc=com
This network group is associated to Workflow 2, with naming context l=uk,dc=example,dc=com
Network Group 3 with a bind DN of **,dc=example,dc=com
This network group is associated to Workflow 1 and Workflow 2, with naming context dc=example,dc=com
A search with bind DN **,l=uk,dc=sun,dc=com would be handled by Network Group 2 and sent to Workflow 2.
A search with bind DN **,dc=sun,dc=com would be handled by Network Group 3 and sent to Workflow 1 and Workflow 2.
|
