UDDI Questions - WL 7.0 - Help

Question

Hello,
I am looking at UDDI implementation which is part of WL 7.0 and have following questions.
Any help is greatly appreciated!
thanks
dora potluri
1. Can the UDDI registry be deployed across the weblogic cluster? We like to do that
for better performance and more importantly to provide redundancy. I see no place
on the console that would let me do that.
2. What is the default UDDI persistence (storage) mechanism? How is data shared/synchronized
when UDDI is deployed on multiple instances in the cluster?
3. Can I configure UDDI to use external LDAP in the backend? If so, how do I accomplish
that? This way we can implement our own replication schemes to aid us in local or
geo failovers.
4. From the information, I infer that BEA has bundled in the acumen technologies
UDDI registry. Are there are key differences between the one that is bundled in WL
7.0 and the one offered by acumen??
5. Security model. How can I implement a security model for UDDI. We like to restrict
our internet users to find methods, and not allow them to update the UDDI registry.
Any documentation or insight on how we can accomplish this??

Answer 1

Please find below the answers to your question:
1) Acumen UDDI (AUDDI) out of the box in a WLS installation is configured to
point to WLS's built-in LDAP as its back-end repository. In the clustered
environment if you configure your cluster to have a single LDAP back-end,
then all your UDDI data goes to the same instance. However, it seems from
your question that you want to have redundant data for UDDI as well. I will
be glad to help you on that once I know and understand you specific scenario
better. In general though, the back-end for the UDDI is all configurable via
the file called "uddi.properties" in the WebLogic700\Server\lib directory.
2) As mentioned above the default is WLS's LDAP.
3) See above.
4) The version bundled in BEA WLS is our AUDDI 1.0 release. We have release
the AUDDI 1.1 version last week. A uddi.war will be available on our site
for download by Friday that is ready to replace the version that is bundled
with WLS. The 1.1 version has a built-in browser that is user friendly and
allows you to perform full UDDI 2.0 functions. Support for user Quota and a
redesigned User Profile that works with WLS has been added in this release
as well. I highly recommend you to use the new version and will be glad to
help you getting it working.
5) To program into UDDI, you need to write soap commands. You can find
documentation on UDDI SOAP API from this link
http://uddi.org/specification.html.
6) In the 1.1 release you can find examples for businesses that you can use
to publish. There is also a command line UDDI client tool that you can use
to submit those samples to the repository.
Nasser Keshmirshekan
[email protected]
"Dora Potluri" <[email protected]> wrote in message
news:[email protected]...
>
>
Hello,
I am looking at UDDI implementation which is part of WL 7.0 and havefollowing questions.
Any help is greatly appreciated!
thanks
dora potluri
1. Can the UDDI registry be deployed across the weblogic cluster? We liketo do that
for better performance and more importantly to provide redundancy. I seeno place
on the console that would let me do that.
2. What is the default UDDI persistence (storage) mechanism? How is datashared/synchronized
when UDDI is deployed on multiple instances in the cluster?
3. Can I configure UDDI to use external LDAP in the backend? If so, how doI accomplish
that? This way we can implement our own replication schemes to aid us inlocal or
geo failovers.
4. From the information, I infer that BEA has bundled in the acumentechnologies
UDDI registry. Are there are key differences between the one that isbundled in WL
7.0 and the one offered by acumen??
5. Security model. How can I implement a security model for UDDI. We liketo restrict
our internet users to find methods, and not allow them to update the UDDIregistry.
Any documentation or insight on how we can accomplish this??