Re: DSO Stages 1 through 8

2007-06-05 Thread Mahan, Janet L [EQ]
I am trying to archive records between forms on the same server.  When
the archive field is selected on form A, the record should be copied to
form B and deleted from Form A using DSO.  The transfer fails at Stage 7
of 8.  I cannot figure out why it fails when we have other DSO mappings
that work.  Any clue as to what I should look for?



From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Ibrahim Akar
Sent: Wednesday, December 20, 2006 11:28 AM
To: arslist@ARSLIST.ORG
Subject: DSO Stages 1 through 8


** 
Stage Descriptions

The following is a high level description of each stage and what
occurs within DSO.

STAGE #0
Go to the pending schema and get a list of the items (control
records) that DSO needs to transfer. 
Detailed description - Retrieve a list of pending transfers.
This is done by retrieving a list of all the entries that exist in the
Distributed Pending form. DSO gets a list of the Request Id's of
all the pending records (control records). DSO does not retrieve 
the details of the pending definition nor the details of the data
record to transfer, it simply gets the list of things that are
pending.

STAGE #1
Get the details of the pending item.
Detailed description - DSO retrieves the details of the 
pending item (control record) identified by the specified id in the
Distributed Pending form. If there is no item (control record)
found, an error is returned.

STAGE #2
Get the definition of the source form. 
Detailed description - Get the details of the source form and
it's structure. This information is important to perform an
efficient and accurate mapping. The definitions are cached
locally. If the definition has changed it will be reloaded into the 
cache.

STAGE #3
Get the details of the data record to transfer.
Detailed description - Retrieve the details of the entry (data
record) that was identified as the entry to be mapped and
transferred to the target machine. If the type of the mapping is a 
move master, remote update, or delete, the entry is checked for
existence. If the entry (data record) does not exist an error is
returned. Otherwise, the existence is confirmed and the full
details of the entry are retrieved. 

STAGE #4
Get the mapping information.
Detailed description - Retrieve the mapping details which are
used to map fields between the source and the target forms. The
mapping definition is cached. The DSO will make sure that a 
mapping definition exists and is the most current in the cache. If
the mapping information is not current or does not exist in the
cache, the DSO will retrieve the mapping definition and load it
into the cache. 

STAGE #5
Perform some checks to make sure that this DSO transfer should
continue to the next stage (stage #6).
Detailed description - Make certain that this DSO transfer is
ready to go to the next stage (stage #6). Check times and 
definitions. Check to see if this DSO operation should be done
immediately or timed. If the operation is timed, has the time
arrived or not?

STAGE #6
Get the definition of the target form.
Detailed description - Get the details of the target form and 
it's structure. This information is important to perform an
efficient and accurate mapping. The definitions are cached
locally. If the definition has changed it will be reloaded into the
cache.

STAGE #7 
Perform the mapping and transfer the entry (data record) from
the source server to the target server.
Detailed description - The mapping of the fields between the
source and the target forms will be performed and the entry (data 
record) will be transferred from the source machine to the target
machine. In the case of Copy+Delete DSO transfers, the entry
(data record) will be deleted from the source machine at this
stage.

STAGE #8 
Tag the DSO operation as being completely done.
Detailed description - Tag the DSO operation as being
completely successful. The tagging will be done immediately after
successfully completing the mapping stage (stage #7). Delete the 
pending item (control record) from the pending schema.

-- 
-Ibrahim Akar

__20060125___This posting was submitted with HTML in
it___ 

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the 
Answers Are"


DSO Stages 1 through 8

2006-12-20 Thread Ibrahim Akar

Stage Descriptions

The following is a high level description of each stage and what
occurs within DSO.

STAGE #0
Go to the pending schema and get a list of the items (control
records) that DSO needs to transfer.
Detailed description – Retrieve a list of pending transfers.
This is done by retrieving a list of all the entries that exist in the
Distributed Pending form. DSO gets a list of the Request Id's of
all the pending records (control records). DSO does not retrieve
the details of the pending definition nor the details of the data
record to transfer, it simply gets the list of things that are
pending.

STAGE #1
Get the details of the pending item.
Detailed description – DSO retrieves the details of the
pending item (control record) identified by the specified id in the
Distributed Pending form. If there is no item (control record)
found, an error is returned.

STAGE #2
Get the definition of the source form.
Detailed description – Get the details of the source form and
it's structure. This information is important to perform an
efficient and accurate mapping. The definitions are cached
locally. If the definition has changed it will be reloaded into the
cache.

STAGE #3
Get the details of the data record to transfer.
Detailed description – Retrieve the details of the entry (data
record) that was identified as the entry to be mapped and
transferred to the target machine. If the type of the mapping is a
move master, remote update, or delete, the entry is checked for
existence. If the entry (data record) does not exist an error is
returned. Otherwise, the existence is confirmed and the full
details of the entry are retrieved.

STAGE #4
Get the mapping information.
Detailed description – Retrieve the mapping details which are
used to map fields between the source and the target forms. The
mapping definition is cached. The DSO will make sure that a
mapping definition exists and is the most current in the cache. If
the mapping information is not current or does not exist in the
cache, the DSO will retrieve the mapping definition and load it
into the cache.

STAGE #5
Perform some checks to make sure that this DSO transfer should
continue to the next stage (stage #6).
Detailed description – Make certain that this DSO transfer is
ready to go to the next stage (stage #6). Check times and
definitions. Check to see if this DSO operation should be done
immediately or timed. If the operation is timed, has the time
arrived or not?

STAGE #6
Get the definition of the target form.
Detailed description – Get the details of the target form and
it's structure. This information is important to perform an
efficient and accurate mapping. The definitions are cached
locally. If the definition has changed it will be reloaded into the
cache.

STAGE #7
Perform the mapping and transfer the entry (data record) from
the source server to the target server.
Detailed description – The mapping of the fields between the
source and the target forms will be performed and the entry (data
record) will be transferred from the source machine to the target
machine. In the case of Copy+Delete DSO transfers, the entry
(data record) will be deleted from the source machine at this
stage.

STAGE #8
Tag the DSO operation as being completely done.
Detailed description – Tag the DSO operation as being
completely successful. The tagging will be done immediately after
successfully completing the mapping stage (stage #7). Delete the
pending item (control record) from the pending schema.

--
-Ibrahim Akar

___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers 
Are"