Storing Data

Viewing 1 reply thread
  • Author
    Posts
    • #22189

      Hi, Can anyone suggest the easiest/best way of storing data that can be used later for a different message.. i.e. a user places and order that has a order reference that order reference has to be stored somewhere so that it can used in the invoice produced..

      I’m guessing store it in sql, but not sure of the best way of doing it..

      Thanks..

    • #22190

      I assume your ordering system is not capable of storing this reference and returning it with the invoice.

      One option is to store the reference in the orchestration instance and reuse this orchestration instance to process the invoice. Have a long running orchestration that receives the order, saves the reference in an orchestration variable, sends the order, waits for the invoice (correlating on order number) receives the invoice, injects the order reference and send the invoice.

      Otherwise create a SQL table with three columns, order number and order reference. Insert the order number and reference when processing the order When processing the invoice retrieve the order reference using the order number and when the invoice send successfully completes delete the row from the database. Use SQL adapter with three stored procedures to insert, retrieve and delete..

      • #22193

        Thanks, so would it just be a case of creating the Schema to only contain those fields in SQL?

        Would you have an example of a stored procedure that I could have a look at please as I have only used the updategrams so far..

        Thanks.

Viewing 1 reply thread
  • The forum ‘BizTalk 2004 – BizTalk 2010’ is closed to new topics and replies.