[prev in list] [next in list] [prev in thread] [next in thread] 

List:       forgerock-openidm
Subject:    [OpenIDM] repo for managed users
From:       andi.egloff () forgerock ! com (Andreas Egloff)
Date:       2011-09-09 3:02:23
Message-ID: CALto_twtU3G7+ZeBmdpyx3++E2k4t86Rdsn3OTw=2Sx6NGujew () mail ! gmail ! com
[Download RAW message or body]

I'll try to clarify this a little more below

On Wed, Sep 7, 2011 at 11:32 AM, Rene Zeipelt <zeipelt at uni-wuppertal.de>wrote:

>  That it is - I forget to remove the repo.orientdb.json from conf folder.
> So I have two repo.<x>.json files and
> it takes orientdb instead of jdbc while I do a jdbc configuration in
> system.properties. Now I know that system
> is for system and repo.jdbc.json for managed objects - but config-objects
> comes from system.properties???
>

system.properties stands for Java system properties; these also can be
provided instead on the (java) command line via -D. This is a generic java
platform facility as opposed to aimed at business level functionality. Maybe
we should move it into a different directory to not mix it with the
application configuration files.

This should not be confused with the external system representation in
OpenIDM, which we refer to as "system object" and is addressable via the
system/ URI.

In terms of persistence, the repository is the pluggable mechanism to use
different NoSQL and RDBMS facilities.

There is a minor distinction made between a "bootstrap" repository
connection to obtain the initial configuration, and the repository service
addressable via repo/ to persist everything else. The reason is that this
allows the system to bootstrap configuration from a database, before the
full business level services are initialized. Ideally this distinction
should be largely irrelevant to the system use and setup, where we clearly
identified some ways to eliminate some configuration duplication in our
earlier discussions when you use system properties. If you only use the
repo.<x>.json file to bootstrap this is already used by the bootstrapping
and repository service. Right now settings passed via Java system properties
are only used in bootstrapping the rest of the configuration.

Andi


>
> Am 07.09.2011 17:06, schrieb Andreas Egloff:
>
> Rene, as Laszlo points out the repository configuration file in conf/
> (repo.<x>.json) should match the type you want to use for your object store.
>
> If you are always going to use the file based configuration the simplest
> thing is to only use the .json files, and not set the system properties at
> all. It will then default the details for the bootstrapping to this json
> file. The system properties are primarily there for bootstrapping against a
> database when no file view is desired.
>
> There are a couple of items that your issue brings up though that I think
> are worth fixing/enhancing to make this clearer:
>
> - Maybe we should disallow having a different repository type for
> configuration vs. the operational data of the system. Or at least we could
> warn about them being different.
> - When system properties are used, the connection related properties in the
> repo.<x>.json files should be optional and default to the system property
> settings
>
> would be helpful :-) thanks again.
>
>
> Thoughts?
> Andi
>
>  2011/9/7 Rene Zeipelt <zeipelt at uni-wuppertal.de>
>
>> I configured a jdbc repository in system.properties:
>>
>> openidm.repo.type=jdbc
>> openidm.repo.dbType=MYSQL
>> # openidm.repo.jndiName=
>> openidm.repo.dbDriver=com.mysql.jdbc.Driver
>> openidm.repo.dbUrl=jdbc:mysql://localhost:3306/openidm
>> openidm.repo.user=openidm
>> openidm.repo.password=notthisone
>> openidm.repo.dbSchema=openidm
>>
>>
>> If started the sample-scheduler for reconciliation
>> systemxmlAccounts_managedUser the managed users are
>> create in orientdb and not in my jdbc. If I don?t start
>> orientdb the jdbc backend is used as it should. Is the
>> type definition to jdbc satisfy which repository is used
>> for managed users?
>> thanks and by
>>
>>
>>
>> _______________________________________________
>> OpenIDM mailing list
>> OpenIDM at forgerock.org
>> https://lists.forgerock.org/mailman/listinfo/openidm
>>
>>
>
>
> _______________________________________________
> OpenIDM mailing listOpenIDM at forgerock.orghttps://lists.forgerock.org/mailman/listinfo/openidm
>
>
>
> --
> _________________________________________________________
>
> BERGISCHE UNIVERSIT?T WUPPERTAL
> Zentrum fuer Informations- und Medienverarbeitung - ZIM
>
> Gaussstr. 20
> D-42097 Wuppertal (Germany)
>
> room  : P.06.09
> phone : +49 202 439 2236
> fax   : +49 202 439 2910
> e-mail: zeipelt at uni-wuppertal.de
> _________________________________________________________
>
>
> _______________________________________________
> OpenIDM mailing list
> OpenIDM at forgerock.org
> https://lists.forgerock.org/mailman/listinfo/openidm
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.forgerock.org/pipermail/openidm/attachments/20110908/d6928839/attachment.html 

[prev in list] [next in list] [prev in thread] [next in thread]