org.forgerock / org.forgerock.opendj

08 Nov, 2007

3 commits

07 Nov, 2007

5 commits

06 Nov, 2007

1 commit

  • 6eee8e2f   Fix for 2423 : remove some replication configuration parameters ... Browse Dir » 
    The attributes :
 ds-cfg-max-receive-queue,
 ds-cfg-max-receive-delay,
 ds-cfg-max-send-queue,
 ds-cfg-max-send-delay
 
were left from some prototyping I did a while ago and not usefull
for now.

I've therefore removed them from the configuration of the
Replication Domain.

  

git-svn-id: https://svn.forgerock.org/opendj/trunk@3415 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     

05 Nov, 2007

6 commits

02 Nov, 2007

5 commits

01 Nov, 2007

1 commit

31 Oct, 2007

1 commit

  • 69733d3a   This set of fixes mainly address the issues where the JE backend does not handle… ... Browse Dir » 
    … attributes with options and subtypes correctly when they are being indexed. 
With this fix:
- All values of an indexed attribute type will be indexed correctly on modifies, adds, and deletes. 
- Updates to subordinate types will now update the superior type if its indexed. 
- Adding and deleting superior attribute types that are not allowed by any object classes (ie. name) will be correctly handled
- Deleting all values from an attribute with no options will no longer delete the values from the same attribute but with options.
 


git-svn-id: https://svn.forgerock.org/opendj/trunk@3395 41b1ffd8-f28e-4786-ab96-9950f0a78031
    boli
     

30 Oct, 2007

1 commit

  • ee0ceaa1   s set of files provides the workflow configuration manual mode. ... Browse Dir » 
    Until now, the workflows were automatically configured-a wokflow
was created for each base DN in the backends. When new suffixes
were added or when a backend was added, the associated workflows
were also created (and simillarly workflows were deleted as suffixes
or backends were removed).

With the manual mode, each and every workflow in the server must
be defined explicitely in the configuration. By default, the server is
running in automatic configuration mode. To have a server running
with manual configuration mode one must set the attribute in
cn=config:

    dn: cn=config
    ...
    ds-cfg-workflow-configuration-mode: auto|manual


No attribute means "auto" mode.

The workflow configuration consist of 3 parts:
- the configuration of workfow elements
- the configuration of workfows
- the configuration of network groups


The Workflow Elements - A workflow element is a basic task in a
workflow. The workflow elements are organized in trees and the
simplest tree is made of one element. For example, the workflow
element that wraps a local backend is configured as follow:

    dn: ds-cfg-workflow-element-id=userRoot,cn=workflow elements,cn=config
    objectClass: top
    objectClass: ds-cfg-workflow-element
    objectClass: ds-cfg-local-backend-workflow-element
    ds-cfg-workflow-element-id: userRoot
    ds-cfg-enabled: true
    ds-cfg-java-class: org.opends.server.workflowelement.localbackend.LocalBackendWorkflowElement
    ds-cfg-backend: ds-cfg-backend-id=userRoot,cn=Backends,cn=config

From an admin standpoint, the local backend workflow element
is an aggregation of a single backend (attribute ds-cfg-backend).
So we cannot disable/delete a backend as long as it is used by a
local backend workflow element.


The Workflows - A workflow is a chain of processing and it's
targeting all the entries under a given baseDN. The processing
is actually identified by the root node of the task tree described
above. The configuration of a workflow looks like:

    dn: ds-cfg-workflow-id=userRoot,cn=workflows,cn=config
    objectClass: top
    objectClass: ds-cfg-workflow
    ds-cfg-workflow-id: userRoot
    ds-cfg-enabled: true
    ds-cfg-workflow-element: ds-cfg-workflow-element-id=userRoot,cn=workflow elements,cn=config
    ds-cfg-base-dn:  dc=example,dc=com

From an admin standpoint, the local workflow is an aggregation
of a single elements (attribute ds-cfg-workflow-element).
So we cannot disable/delete a workflow element as long as it is used
by a local workflow.


The Network Groups - A network group defines categories for
client connection. The network group contains a set of workflows
and each client operation is routed to one (or more) workflow(s).
By default, the server create a default network group which contains
all the workflows defined in the server. The default network group
looks like:

    dn: ds-cfg-id=defaultNetworkGroup2,cn=network groups,cn=config
    objectClass: top
    objectClass: ds-cfg-network-group
    ds-cfg-id: defaultNetworkGroup2
    ds-cfg-enabled: true
    ds-cfg-workflow: ds-cfg-workflow-id=adminRoot,cn=Workflows,cn=config
    ds-cfg-workflow: ds-cfg-workflow-id=ads-truststore,cn=Workflows,cn=config
    ds-cfg-workflow: ds-cfg-workflow-id=backup,cn=Workflows,cn=config
    ds-cfg-workflow: ds-cfg-workflow-id=config,cn=Workflows,cn=config
    ds-cfg-workflow: ds-cfg-workflow-id=monitor,cn=Workflows,cn=config
    ds-cfg-workflow: ds-cfg-workflow-id=schema,cn=Workflows,cn=config
    ds-cfg-workflow: ds-cfg-workflow-id=tasks,cn=Workflows,cn=config
    ds-cfg-workflow: ds-cfg-workflow-id=userRoot,cn=Workflows,cn=config

From an admin standpoint, the network group is an aggregation
of several workflows (attribute ds-cfg-workflow). So we cannot
disable/delete a workflow as long as it is used by a network group.


A unit test named WorkflowConfigurationTest tests the configuration
of network groups, workflows and workflow elements.



git-svn-id: https://svn.forgerock.org/opendj/trunk@3388 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jdemendi
     

29 Oct, 2007

1 commit

26 Oct, 2007

1 commit

25 Oct, 2007

3 commits

24 Oct, 2007

7 commits

23 Oct, 2007

5 commits

  • 338c53a5   Fix for issue 2505 (Provide monitoring information about the number of entries on a given base DN) ... Browse Dir » 
    The following changes are aimed to include a new attribute in the backend monitor entry to provide the number or entries per base DN. This information is used by the status, status-panel, dsreplication and graphical setup to be able to display the number of entries under a given base DN even when there are several base DNs defined in the same database.

The way the new attribute appears in the monitoring entry is:

ldapsearch -w s -p 1389 -b cn=monitor ds-backend-id=userRoot ds-base-dn-entry-countdn: cn=userRoot Backend,cn=monitor
ds-base-dn-entry-count: 0 dc=ta
ds-base-dn-entry-count: 1 dc=ti
ds-base-dn-entry-count: 1 dc=to

I prefer this approach because in my opinion having the number of entries is more important that the suffix.  Anyway I think the discussion around the structure of the value is not crucial as long as the value is easy to parse (which is the case).

The new attribute is defined in the schema and the new OID assigned to it is 1.3.6.1.4.1.26027.1.1.434.

In order to have a minimum impact on performances, the method backend.numSubordinates is only called when there are several base DNs defined in the database.





git-svn-id: https://svn.forgerock.org/opendj/trunk@3361 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 3cbb6f7a   Fix for issue 2494. ... Browse Dir » 
    Add a scriptFriendly option so that the output of the status panel is easier to parse.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3360 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • 274a1dd8   Add properties file support ... Browse Dir » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3359 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff
     
  • cdfc3eb3   Fix for issue 2318. ... Browse Dir » 
    In some cases calling UIManager seems to make the JVM to exit (for instance if it cannot ge the display in some special scenarios).  The fix consists of not calling the UIManager code if we are in CLI mode.


git-svn-id: https://svn.forgerock.org/opendj/trunk@3358 41b1ffd8-f28e-4786-ab96-9950f0a78031
    jvergara
     
  • d100c443   Suppress '.' at the end of ERR_INSTALLDS_TOO_MANY_KEYSTORE_PASSWORD_TRIES message ... Browse Dir » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@3356 41b1ffd8-f28e-4786-ab96-9950f0a78031
    lutoff