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.  Retry parameter for running map with JMS adapter

    Posted 04/26/05 07:58 AM

    Originally posted by: SystemAdmin


    I am runing a map to put messages on a JMS queue using the RUN function. I need to be able to override the JMS adapter settings to add a retry of once in 5 secs. I was going to use -Y but the manual says

    quote:14662db263The Retry execution command (-Y) is used to specify the retry rate for non-data files accessed during map execution. This includes the compiled map file, as well as, work files, the trace file, and the audit log. If one of these files cannot be accessed at execution time, an attempt is made to access the file as specified.[/quote:14662db263]

    That doesn't sound as though it's going to retry the JMS adapter.
    Anyone any ideas?
    Thanks
    Jan
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 2.  Re: Retry parameter for running map with JMS adapter

    Posted 04/26/05 10:41 AM

    Originally posted by: SystemAdmin


    Check out the Execution Commands guide (1007.pdf). Chapter 2 > Execution Commands > List of Execution Commands > Output Target Override - Message.

    This section outines the card level overrides that you can specify when running a map from the command line or a RUN function.

    I haven't tried it with JMS but I think what you want is the Ri:206060dba8count[/i:206060dba8]:i:206060dba8interval[/i:206060dba8] option.
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange


  • 3.  Re: Retry parameter for running map with JMS adapter

    Posted 04/27/05 12:37 AM

    Originally posted by: SystemAdmin


    I had already tried

    RUN("MERC_JMS_08.mmc",
    ECHOIN(1,PACKAGE(createPrompt)) + " " + ECHOIN(2, TEXT(MESSAGEID Column:MERC_MSGSTORE)) + " -OMJMS1 R1:5"))

    but it gives an error in the JMS trace file of

    <3200-3172>: | | jms:MAdapterImpl.dispalyCmdLine
    <3200-3172>: | | | Adapter cmdline is:
    <3200-3172>: | | | R1:5
    <3200-3172>: | | jms:MAdapterImpl.dispalyCmdLine (rc = 0) OK
    <3200-3172>: | | ****First entry on the cmdline is not in the expected -xyz syntax
    <3200-3172>: | | ****Error in cmdline or adapter properties: java.lang.Exception: ****First entry on the cmdline is not in the expected -xyz syntax
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender
    #DataExchange


  • 4.  Re: Retry parameter for running map with JMS adapter

    Posted 04/27/05 12:43 AM

    Originally posted by: SystemAdmin


    Ah there shouldn't be a space between the OMJMS1 and the R1:5. So it should be -OMJMS1R1:5
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender


  • 5.  Re: Retry parameter for running map with JMS adapter

    Posted 04/27/05 08:37 AM

    Originally posted by: SystemAdmin


    Haven't tested this but if the original adapter is file (in the map called by the RUN statement) and it is set to retry, the RUN over-ride should still contain the retry. Adapter command can be modified or added to in an over-ride but not subtracted: if you have a -T in the original command line, you can change it to -TV (if the adapter supports this) but you
    can't --T
    #IBM-Websphere-Transformation-Extender
    #IBMSterlingTransformationExtender
    #DataExchange


  • 6.  Re: Retry parameter for running map with JMS adapter

    Posted 04/27/05 09:20 AM

    Originally posted by: SystemAdmin


    Haven't tested this but if the original adapter is file (in the map called by the RUN statement) and it is set to retry, the RUN over-ride should still contain the retry. Adapter command can be modified or added to in an over-ride but not subtracted: if you have a -T in the original command line, you can change it to -TV (if the adapter supports this) but you
    can't --T[/quote:2536876487]

    Take note, the File Adapter's Retry option does NOT work on Windows. I had an issue with this because it works on Unix but not on Windows. If the file is not there it will not retry. If the file does exist, but is locked by another application, it will (supposedly) retry. But it works just like the documentation says on Unix and will retry, even if the file does not exist.

    However, that being said, I don't think Jan is using the file adapter, I think she is using JMS adapter.
    #DataExchange
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender


  • 7.  Re: Retry parameter for running map with JMS adapter

    Posted 04/27/05 09:30 AM

    Originally posted by: SystemAdmin


    What I was trying to say was that the original adapter for the RUN map should be file (rather than sink) or JMS so that when you over-ride the command in a RUN statement, the retries will already be in place.
    From a Support viewpoint, RUN maps should be able to run stand-alone, with default settings, then the RUN statement would change any required parameters. Obviously, if you are using a generic blob in blob out map to redirect a message to different adapters, the default would be file.
    #IBMSterlingTransformationExtender
    #IBM-Websphere-Transformation-Extender
    #DataExchange