[[
middleware:devel:ed:registry-change
]]
MiddlewareWiki
Trace:
»
ws
»
groups
»
registry-repl
»
ticket-scheduler
»
employee-manage
»
edauth
»
prov-groups
»
password-expire
»
architecture
»
registry-change
Table of Contents
Registry Change Bean
Requirements
Problem Statements
Functional Requirements
Nonfunctional Requirements
Useful links
Comments
Registry Change Bean
Author
Daniel Fisher
Date
2005/05/24
Requirements
Problem Statements
There exists no business component to centrally manage replication from the Registry to other systems.
There exists no way to determine if a record has already been replicated.
Functional Requirements
Ability to receive a DSML messages from the
Registry Replication MDB
Ability to configure
n
number of adapters which represent external systems.
each adapter should write to a JBossMQ Topic with a message selector that explicitly designates the adapter
each adapter must be configured with
XSL
, which when applied to the received DSML will result in a SPML message sent to the Topic
if the
XSL
transform results in an empty message, no message should be sent
Ability to determine if an exact record has previously been processed.
Nonfunctional Requirements
Must be implemented as a clustered stateless session bean.
Useful links
Javadocs
Replication Diagram
Comments
middleware/devel/ed/registry-change.txt · Last modified: 2009/10/07 17:17 (external edit)
Except where otherwise noted, content on this wiki is licensed under the following license:
CC Attribution-Noncommercial-Share Alike 3.0 Unported