using juddi for an infrastructure

[Wolfgang Schuller <wo...@googlemail.com>]

Hi Folks;

I am very new to juddi, in fact just started reading about the concepts. As
a part of requirement spec. that I am going to start has a few points which
I would like to know (may be naive questions) if juddi really support.

i. Federations
    * Does juddi registry support federations? Here I mean the federated
uddi registries in a soa infrastructure, that includes policies definition
for a federation, where the web services could easily join on/out. This
implies allowing multiple registries to form a group to serve a type of
services to certain community.

ii. Information Model
    * Can we use our information model to define web services additional
metadata?

iii. Security
     * How about the protecting the service metadata "partially" and
"completely" for a priviliged access.

iv. Datastore replication
     * Which (type of) datastore is being used within juddi? Is it possible
to distribute and replicate to achieve fault tolerance and scalability?

Thanks in advance!
WS

Re: using juddi for an infrastructure

[Kurt T Stam <ku...@gmail.com>]

Hi Wolfgang, some comment inline. Hope this helps. Cheers  --Kurt

On Thu, Dec 2, 2010 at 11:34 AM, Wolfgang Schuller <
wolfgang.schuller@googlemail.com> wrote:

> Hi Folks;
>
> I am very new to juddi, in fact just started reading about the concepts. As
> a part of requirement spec. that I am going to start has a few points which
> I would like to know (may be naive questions) if juddi really support.
>
> i. Federations
>     * Does juddi registry support federations? Here I mean the federated
> uddi registries in a soa infrastructure, that includes policies definition
> for a federation, where the web services could easily join on/out. This
> implies allowing multiple registries to form a group to serve a type of
> services to certain community.
>

Yes you should be able to do this using the subscription API.

>
> ii. Information Model
>     * Can we use our information model to define web services additional
> metadata?
>

Yes you can create your own tmodels to handle that.

>
> iii. Security
>      * How about the protecting the service metadata "partially" and
> "completely" for a priviliged access.
>

UDDI does not restrict accest access. It is readonly to everyone just as a
phonebook/yellow pages. However you could run different jUDDI nodes specific
for a group of users.

>
> iv. Datastore replication
>      * Which (type of) datastore is being used within juddi? Is it possible
> to distribute and replicate to achieve fault tolerance and scalability?
>

We are using JPA, so in theory you can use a wide range of datastores. We
test with Derby, but in prod I would recommend postgres or mysql.


>
> Thanks in advance!
> WS
>