[
https://issues.apache.org/jira/browse/JUDDI-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13875982#comment-13875982
]
Alex O'Ree edited comment on JUDDI-725 at 3/1/14 2:44 PM:
----------------------------------------------------------
i setup a rig to test this and it's still unclear how to do this.
Node A on 8080
Node B on 9080
Node B, registered a business, service and binding template for the
subscription listener on Node A 8080
Node B, created a subscription for find business, callback to Node A's sub
listener
Node B, created a new business
Log output:
Node A, Authentication Token required. I'm assuming this means that the
notifier (Node B) needs to get an auth token from Node A.
After looking at the code, it's pretty obvious that it's not quite there yet. I
started typing up the asciidoc documentation for this scenario.
To configure this type of setup, use the following procedure.
Assumptions, we have two UDDI nodes, Node A and Node B. Node A has content that
Node B wants to keep synchronized. Node A supports asynchronous subscriptions,
Node B provides a Subscription Listener API endpoint.
# Setup two instances of UDDI, at least one has to be jUDDI. We'll assume they
both are for this example. Both nodes should have unique Node Ids
# Setup two user accounts, one on each node
# Create a business, service and binding template on Node A. The binding
template's access point must point to Node B's subscription listener service.
# Create a subscription on Node A for Find_Business, approximateMatch find
qualifier, (wild card, null) name. Specify the binding key of the binding
template we just created.
# Launch Node B's admin console at /juddiv3/admin, click on "Admin"
# Login
# Select "save_ClientSubscriptionInfo"
Open issues, if we are notifying B on changes to A, B must control
access/validate the notifications from A, otherwise a malicious user can inject
whatever they want into the registry. Presumably, node A needs to get an auth
token from B before sending the notification. So we have a few additional
requirements that shake out of this
# we need to have the security api of Node B registered in A
# we need credentials for Node B stored at Node A (encrypted)
It looks like both of these can be fulfilled by saveClientSubscriptionInfo,
SaveClerk and SaveNode, however it doesn't look like the code exists to do so.
was (Author: spyhunter99):
i setup a rig to test this and it's still unclear how to do this.
Node A on 8080
Node B on 9080
Node B, registered a business, service and binding template for the
subscription listener on Node A 8080
Node B, created a subscription for find business, callback to Node A's sub
listener
Node B, created a new business
Log output:
Node A, Authentication Token required. I'm assuming this means that the
notifier (Node B) needs to get an auth token from Node A.
After looking at the code, it's pretty obvious that it's not quite there yet. I
started typing up the asciidoc documentation for this scenario.
To configure this type of setup, use the following procedure.
Assumptions, we have two UDDI nodes, Node A and Node B. Node A has content that
Node B wants to keep synchronized. Node A supports asynchronous subscriptions,
Node B provides a Subscription Listener API endpoint.
# Setup two instances of UDDI, at least one has to be jUDDI. We'll assume they
both are for this example.
# Setup two user accounts
# Create a business, service and binding template on Node A. The binding
template's access point must point to Node B's subscription listener service.
# Create a subscription on Node A for Find_Business, approximateMatch find
qualifier, (wild card, null) name. Specify the binding key of the binding
template we just created.
# Launch Node B's admin console at /juddiv3/admin, click on "Admin"
# Login
# Select "save_ClientSubscriptionInfo"
TODO example?
> Add/support subscription api to synchronize two instances of juddi using
> callbacks
> ----------------------------------------------------------------------------------
>
> Key: JUDDI-725
> URL: https://issues.apache.org/jira/browse/JUDDI-725
> Project: jUDDI
> Issue Type: New Feature
> Components: documentation
> Reporter: Alex O'Ree
> Assignee: Kurt T Stam
> Fix For: 3.2.1, 3.3
>
>
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
