IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

Join this online group to communicate across IBM product users and experts by sharing advice and best practices with peers and staying up to date regarding product enhancements.


#TechXchangePresenter
 View Only
  • 1.  Delivery by preferred protocol for email delivery

    Posted Thu March 11, 2004 03:48 PM

    When I deliver a flat file by email via TN, it sets the sender as tn@webmethods.com and the file name is ATTXXXXX.dat with no subject line. Is there any way to configure this? Is the workaround to just email within the flow services instead of using the built-in delivery service?

    Will


    #Integration-Server-and-ESB
    #B2B-Integration
    #webMethods


  • 2.  RE: Delivery by preferred protocol for email delivery

    Posted Thu March 11, 2004 04:33 PM

    Will,

    You can change the sender email address by opening up TN Console. Go to the menu TOOLS_SERVER SETUP

    Choose the middle tab and change the E-mail sender address. You can also add a subject line there as well.

    I don’t think there is a way to change the output file name, but if you find out, let me know. Thanks.

    Ray


    #webMethods
    #B2B-Integration
    #Integration-Server-and-ESB


  • 3.  RE: Delivery by preferred protocol for email delivery

    Posted Thu March 11, 2004 05:50 PM

    Thanks Ray - doesn’t look like this is available anymore in 6.1 but I found the properties to edit in 2 of the TN config files. It’d be nice to edit this per rule though for specific subjects and filenames…


    #Integration-Server-and-ESB
    #webMethods
    #B2B-Integration


  • 4.  RE: Delivery by preferred protocol for email delivery

    Posted Thu March 11, 2004 09:26 PM

    Will,
    You can use pub.client:smtp.


    #webMethods
    #B2B-Integration
    #Integration-Server-and-ESB


  • 5.  RE: Delivery by preferred protocol for email delivery

    Posted Thu March 11, 2004 09:53 PM

    Of course I can Surya. I’m trying to use TN where I can submit a doc to TN and have it email based on a company’s profile. This way the doc is in TN for audit purposes and triggers the email. Using smtp means I have to do more work myself in a flow service which is not as slick, but I guess it would give me more control over the subject line/filename.

    Thanks


    #webMethods
    #B2B-Integration
    #Integration-Server-and-ESB


  • 6.  RE: Delivery by preferred protocol for email delivery

    Posted Fri April 09, 2004 08:49 AM

    Will and Ray

    I have a way to so-call customise the TN build-in delivery methods, including email. But I am highly not recommanded unless of couse you are desperated. What I did is

    1. rename the wm.tn.transport:secondarySmtp (For Secondary Email) to wm.tn.transport:secondarySmtpTN
    2. create a new service call wm.tn.transport:secondarySmtp
    3. modify required fields (email title, address, attach filename)
    4. invoke wm.tn.transport:secondarySmtpTN in wm.tn.transport:secondarySmtp

    For Step 3, you might need some work to determine what variables original wm.tn.transport:secondarySmtp takes in (eg.saveToPipleline).

    Here you go. dangerous and unconventional. To avoid the depolyment problem, i suggest you create another package with same namespace wm.tn.transport, in case your service been overwrite by the standard one.


    #B2B-Integration
    #webMethods
    #Integration-Server-and-ESB