> Hi Bruce
Hi.
> I guess you would have made it by now.
Nope. Not even close.
> Just in case…
I appreciate the help.
> a) You need two flow services.
check.
> First to be called when the insert notification if fired and
> Second to be called to subscribe to the document published
OK.
> b) You need two triggers. (if the entities are seperated in
> two package)
What entities do you mean? So far I have an insert notification, an insert service, and two flows. All of them are in the same package.
> First to assign to our first flow service with the document type
> that is published
OK, this would, I assume, be the publishable document type that was created when I created the insert notification, yes?
> Second to assign to our second flow service with the
> subscribe document type
Is this the same document type used in the first trigger? If not, when do I create a second document type?
> c) The first flow if needed might reformat the document
There shouldn’t be any reformatting needed as the source and target tables have the same structure.
> and publish it (locally if broker is not involved)
I’m finding the documentation on publishing a document somewhat inadequate. The documentation says,
“The publish service expects to find a document (Data object) named document in the pipeline. If you are building a flow service, you will need to use the Pipeline Editor to map the document you want to publish to document.”
I don’t see anything in the documentation for the pipeline editor that explains how to add fields to the document called “document” so that I can map my publishable document’s fields to it. Or am I on the wrong track here?
> d) The second flow will subscribe to this document (using
> settings from trigger)
So will I wind up with two triggers, each having the original publishable document (from the insert notification) as their condition, but one triggering flow1 (the publish flow) and the other triggering flow 2 (the subscribe flow)?
> and will call your insert adapter service
OK, this part at least seems straightforward.
> It might give you a better picture (if I am not making it clear
> here) referencing the ISBuildingIntegrations.pdf
Well, I’m looking at that, and at ISDeveloperGuide.pdf, and at WMJDBCAdapterUserGuide.pdf, but I’m having a difficult time assembling a coherent picture. I didn’t have this kind of difficulty when learning to use WM 4.1; the quality of the documentation really seems to have deteriorated between releases.
> Good luck
Thanks again for your help.