RE: [uddi-dev] UDDI Linkup

[Anne Thomas Manes <anne@manes.net>]

Dharmesh,

As far as can tell, none of the private registry implementations supports
the V2 replication API. (In your case, WASP UDDI and WebSphere Business
Registry do not support it.) WASP 4.5 supports the V3 subscription and
notification API, so if you upgrade your existing registry to 4.5, you
should be able to use the subscription API to implement a one-way
master/slave replication schema from WASP to WebSphere. You won't be able to
replicate in the other direction, though.

Anne

> -----Original Message-----
> From: Daniel Feygin [mailto:feygin@unitspace.com]
> Sent: Friday, March 14, 2003 5:15 AM
> To: 'Chohan, DB (Dharmesh)'; uddi-dev@lists.oasis-open.org
> Subject: RE: [uddi-dev] UDDI Linkup
>
>
> Dharmesh,
>
> UDDI replication is part of V2, but last time I checked I don't think
> Systinet's registry implemented it.  If you are using the latest
> version of
> WASP UDDI you should be able to take advantage of its subscription and
> notification functionality, which follows the design of V3
> Subscription API.
> Once you make the initial copy of registry data, you can subscribe to all
> future updates and inserts that you will receive with your UDDI4J-based
> process.  If you want to receive a complete copy, then you should be
> prepared that Subscription API is not designed for that job and you will
> have to engage in a fair amount of trickery to do it.  By monitoring the
> changes in WASP UDDI you will have the ability to migrate the changes into
> the mirror WebSphere registry as they occur.  This is *not* the
> recommended
> way of replicating UDDI registries.
>
> I cannot recommend a way to initially populate your WebSphere
> registry, but
> I assume there are tools that help you do it in both WASP UDDI and in
> WebSphere.  There are people on this mailing list who are more intimately
> familiar with both of these products.  Hopefully they will add to my
> statements.
>
> If there are any assumptions you can make about the data in the registry
> (i.e., whether all of it must be categorized in some taxonomy), then you
> would be able to implement a less generic, but more efficient
> solution that
> uses polling.
>
> Regards,
> Daniel
>
>
> > -----Original Message-----
> > From: Chohan, DB (Dharmesh) [mailto:D.B.Chohan@dl.ac.uk]
> > Sent: Friday, March 14, 2003 11:28 AM
> > To: 'Daniel Feygin'; Chohan, DB (Dharmesh);
> > uddi-dev@lists.oasis-open.org
> > Subject: RE: [uddi-dev] UDDI Linkup
> >
> >
> > Hi Daniel,
> >
> > Currently I am in a process of porting the information in
> > WASP registry to Websphere.  The other UDDI registry uses
> > WASP. Both registry uses UDDI version 2.  I am using UDDI4J
> > to develop the registry. Is UDDI replication API part of
> > version 2 and how does the replication works ?
> >
> > Thanks
> > Dharmesh
> >
> > -----Original Message-----
> > From: Daniel Feygin [mailto:feygin@unitspace.com]
> > Sent: 11 March 2003 11:27
> > To: 'Chohan, DB (Dharmesh)'; uddi-dev@lists.oasis-open.org
> > Subject: RE: [uddi-dev] UDDI Linkup
> >
> >
> > Dharmesh,
> >
> > You should check with your registry's vendor for this type of
> > functionality. Unless your registries are V3 (which is
> > unlikely), your options are limited
> > to:
> > 1) UDDI replication API if it is supported by the
> > implementation you use;
> > 2) database-level replication.
> >
> > Daniel
> >
> >
> > > -----Original Message-----
> > > From: Chohan, DB (Dharmesh) [mailto:D.B.Chohan@dl.ac.uk]
> > > Sent: Tuesday, March 11, 2003 1:46 PM
> > > To: 'uddi-dev@lists.oasis-open.org'
> > > Subject: [uddi-dev] UDDI Linkup
> > >
> > >
> > > Hi,
> > >
> > > Within our organisation, we have got 2 separate UDDI
> > > registries and would like to link the 2 registries together.
> > > Please can anyone advise how to  do it.
> > >
> > > Thanks
> > >
> > > -----------------------
> > > Dharmesh Chohan        |
> > > Software Engineer      |
> > > Grid Technology        |
> > > Daresbury Laboratory   |
> > > Daresbury, Warrington  |
> > > Cheshire WA4 4AD       |
> > > Tel: 01925 603207      |
> > > -----------------------
> > >
> > >
> > >
> >
> >
>