IBM Sterling Transformation Extender

Sterling Transformation Extender

Come for answers, stay for best practices. All we're missing is you.


#Sterling
#Supplychain
 View Only
  • 1.  Transactions not rolling back.

    Posted 04/09/12 04:15 PM

    Originally posted by: brian1305


    I'm running WTX version 8.1, and I'm having an issue with transactions rolling back in some cases. In cases of 'Target not available', the transactions previous to the one that generates the error are still being committed. The map is being called via a run map. I would appreciate any help that can be offered. Thanks.
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 2.  Re: Transactions not rolling back.

    Posted 04/10/12 09:58 AM

    Originally posted by: repanzer1


    So many of the questions on this message board I could answer perfectly if it were at the time I was working with the same item that is the topic, but it's always been years since I worked with it.
    I'm going to make an assumption that you're writing to a message queue.
    From what I recall and I could be wrong, if you had an input file with multiple records and you pulled each record into a functional map and did a PUT("MSG QUEUE), it runs the entire map and prepares each record to put on the queue, then as the final step before completion of the map, it does all the PUTs to the queue.
    From a parent map, you are running a map that does the PUT, and each time the run map executes, it does the PUT as it completes, even though you may have more records that the parent map is going to execute. If the parent map has an issue at the 5th record, it already pushed the 4 records before it to the run map and that run map completed, which put the data on the message queue and cannot roll back. In order to do what you're trying to do, you may have to put it all in one map, rather than run a map that puts to the output adapter.
    There are 10 types of people in this world. Those who understand binary and those who don't.
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender


  • 3.  Re: Transactions not rolling back.

    Posted 04/10/12 12:23 PM

    Originally posted by: brian1305


    Actually, I'm writing to SQL. The specific error that it's running across is a Datetime field overflow. What's causing THAT error is an invalid date sent by our trading partner (this is an EDI transaction).
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender


  • 4.  Re: Transactions not rolling back.

    Posted 04/10/12 12:42 PM

    Originally posted by: repanzer1


    Writing to SQL? What does the mean exactly?

    When you say rollback and commit, I think messages (or any group of related data) being written to an adapter, whether it's a message queue, database, file, FTP, etc. There is no adapter for SQL.
    There are 10 types of people in this world. Those who understand binary and those who don't.
    #DataExchange
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender


  • 5.  Re: Transactions not rolling back.

    Posted 04/11/12 09:17 AM

    Originally posted by: paul.brett


    I am going to assume that you are writing (using the DB adapter) to a MS SQL Server database.

    You have a master map, that has a repeating element on output, each one using a RUN() function to call a child map? Each child map is doing one or more updates to the database? If any update fails, you want the whole lot to roll back?

    Assuming all the above to be correct, then I think all you need to do is ensure that the RUN() functions are wrapped in a VALID()/FAIL() pair.

    Please be more specific about the scenario if any of my assumptions are incorrect.

    Thank-you.
    #IBM-Websphere-Transformation-Extender
    #DataExchange
    #IBMSterlingTransformationExtender


  • 6.  Re: Transactions not rolling back.

    Posted 04/16/12 02:55 PM

    Originally posted by: jvanboga


    If the question isn't answered yet, in this case 'Target not available' means it can't connect to the database. Turn the database trace file option on where you DB connection is identified (either in the rule or card that points to the MDQ/DBID file)

    The problem could be that the map can't find or connect to the DB and/or table. If ID/PW combo used in the rule or MDQ is correct you'll need to make sure the machine executing the connection has access to the DB server.
    #IBM-Websphere-Transformation-Extender
    #DataExchange
    #IBMSterlingTransformationExtender