org.forgerock / org.forgerock.opendj

20 Jun, 2007

2 commits

  • 6d7cf7d7   small improvement in the replication monitoring ... Browse Code » 
    The replication monitoring was showing information for
- the replication domains
- the remote LDAP servers connected to the replication server
- the remote replication server connected to the replication server

but does not show any information for a local replication server.
A replication server that is started but does not have any server connected yet
therefore does not publish any monitoring information.

This changes add a new monitoring entry that fixes this lack and also change the names
of the monitoring entries of the server connected to the replication server to include the
"remote" keyword.

As an example, the monitoring information of a server that is also its replication server now looks like this :

dn: cn=Replication Server 8989 1,cn=monitor
objectClass: extensibleObject
objectClass: top
objectClass: ds-monitor-entry
replication server id: 1
replication server port: 8989
base-dn: dc=example,dc=com
cn: Replication Server 8989 1

dn: cn=Replication plugin dc=example\,dc=com,cn=monitor
objectClass: extensibleObject
objectClass: top
objectClass: ds-monitor-entry
lost-connections: 0
connected-to: localhost/127.0.0.1:8989
resolved-naming-conflicts: 0
replayed-updates: 0
base-dn: dc=example,dc=com
unresolved-naming-conflicts: 0
max-send-window: 100
max-rcv-window: 100
resolved-modify-conflicts: 0
current-send-window: 100
cn: Replication plugin dc=example,dc=com
pending-updates: 0
sent-updates: 0
received-updates: 0
current-rcv-window: 100
replayed-updates-ok: 0

dn: cn=Remote LDAP Server dc=example\,dc=com furon 1,cn=monitor
objectClass: extensibleObject
objectClass: top
objectClass: ds-monitor-entry
approximate-delay: 0
max-waiting-changes: 10000
update-sent: 0
waiting-changes: 0
update-received: 0
base-dn: dc=example,dc=com
update-waiting-acks: 0
max-send-window: 100
ack-received: 0
max-rcv-window: 100
current-send-window: 100
cn: Remote LDAP Server dc=example,dc=com furon 1
server-id: 1
LDAP-Server: furon
current-rcv-window: 100
ack-sent: 0 

git-svn-id: https://svn.forgerock.org/opendj/trunk@2131 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gbellato
     
  • c0547923   Set MAX_LINE_WIDTH to the value of the COLUMNS environment variable if it is available. ... Browse Code » 
    git-svn-id: https://svn.forgerock.org/opendj/trunk@2130 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     

19 Jun, 2007

2 commits

18 Jun, 2007

10 commits

17 Jun, 2007

1 commit

15 Jun, 2007

9 commits

14 Jun, 2007

14 commits

13 Jun, 2007

2 commits

  • a9fc769d   Add support for tagging managed object definitions so that similar types of mana… ... Browse Code » 
    …ged object can be grouped together. Tagging will enable us to automatically generate more user-friendly documentation and administration tools as a result of them being easier to navigate and search. For example, an administration CLI will be able to split the available set of sub-commands into categories, thus making it easier for administrators to find the sub-command that they need.

This change is implemented as follows:

* provide an extensible way in which tags can be defined: the XML root configuration definition element now supports an "adm:tag-definition" element, which can be used as follows:

  <adm:tag-definition name="logging">
    <adm:synopsis>Logging</adm:synopsis>
  </adm:tag-definition>

* provide a means for tagging managed object definitions with zero or more tags using an "adm:tag" element, which can be used as follows:

  <adm:tag name="logging"/>

* add support to the admin framework APIs for querying a managed object definition's tags

* define an initial set of tags and tag managed object definitions appropriately (this is just an initial guess and is likely to change):

  * logging
  * replication (incl. mmr)
  * database (incl. caching)
  * security (authn and authz)
  * identity (user account management, pwp, etc)
  * core (connection handlers, virtual attributes, etc)


git-svn-id: https://svn.forgerock.org/opendj/trunk@2093 41b1ffd8-f28e-4786-ab96-9950f0a78031
    matthew_swift
     
  • b540d5cd   Issue 1784 data and temporary files must go into a unique folder ... Browse Code » 
    
git-svn-id: https://svn.forgerock.org/opendj/trunk@2092 41b1ffd8-f28e-4786-ab96-9950f0a78031
    gary_williams