Skip to main content
Kofax

Why are my notifications ending up in the TC_TO_FI folder and not in the NOTIF folder

Article # 3036085 - Page views: 41

Issue

Why are my notifications ending up in the TC_TO_FI folder and not in the NOTIF

Customer sends messages via any TC/LINK (SC, SC7, MX7, LN,...) and they would like to get also the notification to be stored and archived in a file.

The TC/LINK, which is posting the message to KCS recognizes a KCS shadow user and the user has defined "Delivery- and Nondelivery Notification" events, which
send the notifications to the TC/LINK-FI queue.

But the TC/LINK-FI handles these notifications as normal messages and places them to the TC_TO_FI folder and not to the configured NOTIF folder.
Also the NFINFO element is missing within the generated files and therefore also important information about the message delivery is missing.

Example for such a Notification file, as it is stored in the TC_TO_FI folder:
SUBJECT="KCS delivery notification: Sending from SAP, additional Notification to FI", TYPE=NORM, DATE=150421, TIME=105039, NPAGE=2, SUSPDUPL=0, MCORR=00037556332
FROM: ACTIVE=YES, NAME=AT 18664555383, SERVICE=FAX, NUMBER=+4318664555383, ACTIVE=YES
TO: ACTIVE=YES, P=NORM, NF=NO, ARCHIVE=NEG, RESOLUTION=NORM, SCOPY=YES, HLINE=YES, CCTR=, EXDATE=610119, EXTIME=031407, REMMSG=NO, C1=023D1079, C2=00000592, SERVICE=TCFI, NUMBER=SAP7Message, ACTIVE=YES
TXT:
KCS Delivery Notification
-----------------------------------------------------------
Message 00037556332 sent to AT 18664555383 +4318664555383,-004318664555383     e96
Time sent: 15-04-21 10:50:28
Subject: Sending from SAP, additional Notification to FI

Costs:      0 for Costcenter
Sending channel: 11
-----------------------------------------------------------
:ATT: NAME=C:\TCLFI\TC_TO_FI\TCFI009A.TIF, APPLICATION=IMAGE000.TIF, COMMENT=TCLINK Image, ATTSIZE=5676 

 

Cause

  • This behavior works as intended and is implemented in the general TCLINK module (TCLINK.EXE)
  • If a message is posted to KCS, the posting TCLINK instance (e.g. TC/LINK-SC) stores its own Linkgroup in the TS_CORREL_6 field of the recipient.
    The Linkgroup is configured within the registry value HKLM\SOFTWARE\TOPCALL\TCLINKxx\General\LinkGroup
  • You can see this in the "Converted Message from Mail" trace of those TCLINK instance posting the original outbound message to KCS, if the registry value
    HKLM\SOFTWARE\TOPCALL\TCLINKxx\TOPCALL\TCSIDebug=1

    21/10:50:26.737 (19b4/6c0) ----- Converted Message from Mail    -----
    21/10:50:26.737 (19b4/6c0) set_entry_ms_mail = (
    21/10:50:26.737 (19b4/6c0)  cl_time/time_created = "150421:085010",
    21/10:50:26.737 (19b4/6c0)  cl_integer/int_npag = 2,
    21/10:50:26.737 (19b4/6c0)  cl_textstring/ts_rec_queue = "TCLSC7Q4",
    21/10:50:26.738 (19b4/6c0)  l_env_cont/un_content = (
    21/10:50:26.738 (19b4/6c0)   set_header = (
    21/10:50:26.738 (19b4/6c0)    cl_textstring/ts_ref = "Sending from SAP, additional Notification to FI",
    21/10:50:26.738 (19b4/6c0)    cl_textstring/ts_message_id = "<ADR40000000000047001000C29F14E501EE4...C@sap.sb.local>",
    ...
    21/10:50:26.741 (19b4/6c0)    l_recipients = (
    21/10:50:26.742 (19b4/6c0)     set_entry_rs = (
    21/10:50:26.742 (19b4/6c0)      cl_textstring/ts_fullname = "AT 18664555383",
    21/10:50:26.742 (19b4/6c0)      cl_textstring/ts_xfield = "AT 18664555383",
    21/10:50:26.742 (19b4/6c0)      cl_integer/int_del_type = 1,
    21/10:50:26.742 (19b4/6c0)      cl_integer/int_active = 1,
    21/10:50:26.742 (19b4/6c0)      cl_integer/int_type = 5,
    21/10:50:26.742 (19b4/6c0)      cl_textstring/ts_correl_4 = "000C29F14E501EE4BA806E554BC24E8C",
    21/10:50:26.742 (19b4/6c0)      cl_textstring/ts_correl_5 = "ORCPT=rfc822;fax=+4318664555383@sc7.sb.local",
    21/10:50:26.742 (19b4/6c0)      cl_integer/int_termination = 1023,
    21/10:50:26.743 (19b4/6c0)      cl_integer/int_options = 16391,
    21/10:50:26.743 (19b4/6c0)      cl_integer/int_priority = 49,
    21/10:50:26.743 (19b4/6c0)      cl_textstring/ts_correl_6 = "TCLINKSC7",
    21/10:50:26.743 (19b4/6c0)      cl_time/time_latest = "610119:031407",
    21/10:50:26.743 (19b4/6c0)      cl_textstring/ts_cost_center = "GUEST",
    21/10:50:26.743 (19b4/6c0)      l_full_addr = (
    21/10:50:26.743 (19b4/6c0)       set_full_address = (
    21/10:50:26.744 (19b4/6c0)        cl_integer/int_active = 1,
    21/10:50:26.744 (19b4/6c0)        cl_textstring/ts_service = "FAX",
    21/10:50:26.744 (19b4/6c0)        set_fax_address/un_public_address = (
    21/10:50:26.744 (19b4/6c0)         cl_textstring/ts_fax_number = "+4318664555383"
    21/10:50:26.744 (19b4/6c0)        )
    21/10:50:26.744 (19b4/6c0)       )
    21/10:50:26.744 (19b4/6c0)      )
  • Once the outbound message has been sent, the notification is put into the queue polled by TC/LINK-FI (this is done, because the delivery Notification event has been defined)
    If the notification is picked up by TC/LINK-FI, it will still contain the Linkgroup of the posting TCLINK instance in the TCSI field TS_CORREL_6.
  • TC/LINK-FI will check the contents of the TS_CORREL_6 and compares it against its own Linkgroup settings, as defined in the registry value
    HKLM\SOFTWARE\TOPCALL\TCLINKFI\General\LinkGroup

     
    • If the string in TS_CORREL_6 of the notification matches the LinkGroup registry setting of TC/LINK-FI,
      the TC/LINK-FI will handle this notification as a real notification and will also place the file into the NOTIF folder.
    • On the other hand, if the TS_CORREL_6 string does not match the LinkGroup registry setting of TC/LINK-FI,
      the notification will be treated as "normal" message and consequently placed into the TC_TO_FI folder.
    • This behavior is a general TCLINK.EXE behavior, not specific to TC/LINK-FI

 

Solution

Can I turn off this check against the Linkgroup registry setting, so that notifications are still handled as notifications? 

  • Yes, there is a possibility to turn off this check, so that notifications are still handled as notifications and not converted to "normal" messages.
  • On the TC/LINK Instance, which is processing the Notification (in our example TC/LINK-FI) configure the LinkGroup registry value to the hardcoded value ALL
    Take care that all characters must be defined upper case and the TC/LINK must be restarted afterwards:
    HKLM\SOFTWARE\TOPCALL\TCLINKFI\General\LinkGroup=ALL
  • Once you do this, the Notification will be placed into the NOTIF folder (as defined under registry value HKLM\SOFTWARE\TOPCALL\TCLINKFI\Options\TCLFI_Notif)
    and it will also contain a NFINFO element, see attached an example of such a notification.

    SUBJECT="KCS delivery notification: Sending from SAP2, additional Notification to FI", TYPE=NOTIF, DATE=150421, TIME=111502, MCORR=00037556552
    FROM: ACTIVE=YES, NAME=AT 18664555383, SERVICE=FAX, NUMBER=+4318664555383, ACTIVE=YES
    TO: ACTIVE=YES, P=NORM, NF=NO, ARCHIVE=NEG, RESOLUTION=NORM, SCOPY=YES, HLINE=YES, CCTR=, EXDATE=610119, EXTIME=031407, REMMSG=NO, C1=023D1155, C2=000007D4, SERVICE=TCFI, NUMBER=SAP7Message, ACTIVE=YES
    NFINFO: STATUS=DEL, TIME=150421:111450, DOCNR=302-002, LNOTE=004318664555383     e96, COST=     0, MCORR=00037556552, C4=000C29F14E501EE4BA80DB047234EE8C, C5="ORCPT=rfc822;fax=+4318664555383@sc7.sb.local"
    TXT:
    KCS Delivery Notification
    -----------------------------------------------------------
    Message 00037556552 sent to AT 18664555383 +4318664555383,-004318664555383     e96
    Time sent: 15-04-21 11:14:50
    Subject: Sending from SAP2, additional Notification to FI

    Costs:      0 for Costcenter GUEST
    Sending channel: 11
    -----------------------------------------------------------
    :ATT: NAME=C:\TCLFI\NOTIF\TCFI003A.TIF, APPLICATION=IMAGE000.TIF, COMMENT=TCLINK Image, ATTSIZE=5708

What can I do, if I have no shadow user recogntion for the TCLINK instance, posting the message to KCS, as it is typically the case for TC/LINK-SC/SC7.
Is it still possible to get the notification message as a file in the NOTIF folder? 

  • Yes also this is possible. You simply have to define a delivery- and nondelivery event for the default queue user of those TCLINK instance posting the message to KCS.
    So in case of using TC/LINK-SC7, this would be an additional delivery- and nondelivery event defined for the TC/LINK-SC7 queue user TCLSC7Q4. The events use then the service TCFI.
    By defining these events, you will still get back the notifications to SAP, so the notifications to TC/LINK-FI are additionally and do not replace the standard notification events going back to SAP.

 

Level of Complexity 

Moderate

 

Applies to  

Product Version Build Environment Hardware
Kofax Communication Server ALL      
  • Was this article helpful?