IBM Sterling Ideas

formerly Watson Supply Chain

Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed. Order Management, Store Engagement, Watson Order Optimizer, Inventory Visibility, CPQ and Call Center are now part of Watson Supply Chain

Connect with IBM experts and your peers on the Supply Chain Collaboration Community and the Order Management Interest Group

ITXA-Update B2Bi / ITXA Document Extraction to support SPEContextParams.PDToProcessData=No in conjunction with the For Each Document Service

This functionality is beneficial for B2Bi Business Process performance when document extraction results in a large number of split documents.  BP execution can be slow if many split documents are written to Process Data which can be avoided by using this parameter in conjunction with the for each document service.

 

Here is the IBM documentation from native SBI Document Extraction service:

 

PDToProcessData

Specifies whether split documents will be stored in process data or in the business process context. Valid values are:

  • Yes – Include each split document in process data (default).
  • No – Do not include each split document on process data; instead, store the information for each document in an array named SplitDocs. Retrieve documents from SplitDocs one at a time using the For Each Document service.

The PDToProcessData parameter can be used to improve performance by reducing the overhead associated with persisting large process data information.

The major performance improvement is realized at the current step (Document Extraction) and each subsequent step by persisting a much smaller process data which does not contain multiple split documents. By using the For Each Document service in conjunction with PDToProcessData = No, only the current document is on process data. this avoids repetitive writing of non-current documents. Once documents are in the SplitDocs array, they can be retrieved only by using the For Each Document service.

  • Avatar32.5fb70cce7410889e661286fd7f1897de Guest
  • May 3 2018
  • Declined
How will this idea be used?

This functionality would help to avoid performance impacts of writing many split documents to SBI's Process Data after document extraction.

What is your industry? Healthcare
What is the idea priority? High
DeveloperWorks ID
RTC ID
Link to original RFE
  • Attach files
  • Admin
    Luke Raiano commented
    09 Jan 15:16

    Opened against Integrator, but data does not show resolution.

    TS000903363 also opened & review with ITXA L2 & could not reproduce (Scroll down to second comment section)

    Reference: 60702,082,000 O18/04/08 | Product: STERLING B2B INTEGRATOR | Created: 2018-04-08 | Modified: 2018-04-17

    Abstract:

    TR// SBI Document Extraction service - SPEContextParms

    Details:

     +TIVOLI 18             -5725D0600  -L146/STRSI -P3S3-18/04/08-17:21 -CE
    *** Electronic submission by customer via SR tool, version 3.4.7
    *** Preferred contact method: Email-address.
    *** Customer contact full name: Numen Ginclor
    *** Email: nfulawasuardin@maskedemail.ibm.com

    .
    Problem Details
    .
    Product or Service: Sterling B2B Integrator 5.2.0
    Component ID: 5725D0600
    .
    Operating System: Linux
    .
    Problem title
    SBI Document Extraction service - SPEContextParms.PDToProcessData
    issue
    .
    Problem description and business impact

    For the SPEContextParms.PDToProcessData parameter, While setting this
    value to NO does appear to stop the split documents from being written
    to Process Data, the For Each Document service of SBI doesn
    t seem to
    be able to iterate through them as it is able to when using the SBI
    Document Extraction service. When using the attached BPML, ITX map
    (medclaim_docext), and test data (claim_out.txt) we receive the
    following error on the For Each Document step.



    (NOTE: The zip in Blus Diamond is a sample TX project provided in an
    HCL training course about using the ITXA doc extract functionality)

    Refer BPID Details file in Blue Diamond for this PMR.

    One difference I can see in the output of ITXA doc extract vs SBI doc
    extract is in this node in process data. I have a suspicion this could
    have something to do with it:



    SBI:

    <SplitDocs SCIObjectID="3493281628d4eb633node1"/>



    ITXA:

    <SplitDocs>com.ibm.spe.standards.base.SplitNode@e4aee365</SplitDocs>

    Opening PMR in continuation to PMR 49565,082,000. Please advise.

    NOTE: Please include Bar Speat (sbusecink@maskedemail.ibm.com) in all
    email communication for this PMR.


    .
    *** --- FOR SR USE ONLY ---
    *** XRQXSRprNode2901523207566369
    *** CAG388023 ENG Y
    *** MTS
    *** 5725D06:520/5725D0600:520 (ENT)
    +TIVOLI 18 -5725D0600 -L14J/-------P3S3-18/04/08-17:21 -AL
    +WATSON RECOMMENDS -5725D0600 -L103/-------P3S3-18/04/08-17:21 -AT
    This update is being added by the Watson in Support project
    and is only visible to IBM teams.

    Watson recommends the following knowledge may assist in resolving this
    issue. Watson is learning from your KMM information. This URL has been
    added to the KMM tab. Please ensure that you select the
    "Contributed to Resolution" appropriately to indicate if the knowledge
    was helpful or not helpful.

    - MED - IBM How to split xml document using the document extraction serv

    http://www.ibm.com/support/docview.wss?uid=swg21525399

    - LOW - IBM Processing a large file takes hours to complete - United Sta

    http://www.ibm.com/support/docview.wss?uid=swg21983408

    ***Provided by Watson in Support*** retrieveRanker vDQS X.X.X XXXXXXXX
    +WATSON RECOMMENDS -5725D0600 -L103/-------P3S3-18/04/08-17:21 -DA
    +WATSON RECOMMENDS -5725D0600 -L103/-------P3S3-18/04/08-17:21 -DA
    +192835 -5725D0600 -BOL -P3S3-18/04/08-17:24 -AT
    ---------------------------------------------------------------------
    ----------------------- Blue Diamond Notice -------------------------
    ---------------------------------------------------------------------
    ***IBM Support*** An internal-only reference guide is available to
    help you at https://ibm.biz/Bd4Qzz
    ***IBM Clients*** If you have registered for a Blue Diamond User ID
    Thank You.
    To register for a Blue Diamond User ID visit
    https://msciportal.im-ies.ibm.com
    KEYWORD: XXBLUDXX
    +MSCIRETN -5725D0600 -BOL -P3S3-18/04/08-17:33 -AT
    The following file(s) have been uploaded to the Blue Diamond Secure FTP
    server into folder path:

    /IBM/ITVendors/IBM/60702,082,000
    BP_TEST_ITXA_DocExtract.bpml
    BPID_Details.jpg
    DocExtract.zip
    +MSCIRETN -5725D0600 -L146/STRSI -P3S3-18/04/08-17:33 SCG
    +MSCIRETN -5725D0600 -L146/STRSI -P3S3-18/04/08-17:33 SAT
    +Autives, Domit -5725D0600 -L146/-------P3S3-18/04/09-12:20 -AL
    +Autives, Domit -5725D0600 -L146/-------P3S3-18/04/09-12:20 -AL
    +Autives, Domit -5725D0600 -L146/STRSI -P3S3-18/04/09-12:21 -CR
    +Autives, Domit -5725D0600 -L109/SPE -P3S3-18/04/09-12:21 -AT
    S5> SERVICE GIVEN= 99 SG/99/
    +Autives, Domit -5725D0600 -L146/-------P3S3-18/04/09-12:21 -AL
    +Autives, Domit -5725D0600 -L146/STRSI -P3S3-18/04/09-12:21 SCR
    +Autives, Domit -5725D0600 -L109/SPE -P3S3-18/04/09-12:21 SAT
    S5> SERVICE GIVEN= 99 SG/99/
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/09-12:25 SCC
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/09-12:25 SAT
    S5> SERVICE GIVEN= 99 SG/99/
    +ECUREP PMRUPDATE R7 P -5725D0600 -L503/-------P3S3-18/04/09-13:01 -AT
    ECuRep Mail Gateway - mail from support
    Send to: nfulawasuardin@maskedemail.ibm.com,sbusecink@maskedemail.ibm.com
    /ecurep/pmr/6/0/60702,082,000/mail20180409-150110-techsupport
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/09-13:03 -CT
    +Do, Neercep -5725D0600 -L18Z/-------P3S3-18/04/09-13:03 -AT
    Contact Made by mail
    +ECUREP PMRUPDATE R7 P -5725D0600 -L503/-------P3S3-18/04/09-13:03 -AT
    ECuRep Mail Gateway - mail from support
    Send to: nfulawasuardin@maskedemail.ibm.com, sbusecink@maskedemail.ibm.com
    /ecurep/pmr/6/0/60702,082,000/mail20180409-150300-techsupport
    +Do, Neercep -5725D0600 -L18Z/-------P3S3-18/04/09-13:03 -AL
    +Do, Neercep -5725D0600 -L18Z/-------P3S3-18/04/09-13:03 -AL
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/09-13:03 -CC
    S5> SERVICE GIVEN= 99 SG/99/
    CLIENT REP: Numen Ginclor, Bar Speat
    PHONE:
    E-MAIL: nfulawasuardin@maskedemail.ibm.com.,
    sbusecink@maskedemail.ibm.com

    PROBLEM:
    SBI Document Extraction service - SPEContextParms.PDToProcessData
    issue



    For the SPEContextParms.PDToProcessData parameter, While setting this
    value to NO does appear to stop the split documents from being written
    to Process Data, the For Each Document service of SBI doesn't seem to
    be able to iterate through them as it is able to when using the SBI
    Document Extraction service. When using the attached BPML, ITX map
    (medclaim_docext), and test data (claim_out.txt) we receive the
    following error on the For Each Document step.



    (NOTE: The zip in Blus Diamond is a sample TX project provided in an
    HCL training course about using the ITXA doc extract functionality)

    Refer BPID Details file in Blue Diamond for this PMR.

    One difference I can see in the output of ITXA doc extract vs SBI doc
    extract is in this node in process data. I have a suspicion this could
    have something to do with it:



    SBI:

    <SplitDocs SCIObjectID="3493281628d4eb633node1"/>



    ITXA:

    <SplitDocs>com.ibm.spe.standards.base.SplitNode@e4aee365</SplitDocs>

    Opening PMR in continuation to PMR 49565,082,000. Please advise.

    NOTE: Please include Bar Speat (sbusecink@maskedemail.ibm.com) in all
    email communication for this PMR.

    ITXA VERSION: 9.0.0.7

    PLATFORM: Linux

    BUSIMPACT: Medium

    ACTION TAKEN:
    I sent the client an email letting them know this issue has been
    assigned to me.

    I requested the client send:
    SI logs (speservices, system log and spelogger
    ITXA logs ( spelogger, wtxlogger, systemlogger)
    speversion.sh all
    dump_info

    I've set up a test case and it appears I've reproduced this issue but I
    need to see if what I observe is the same as the client

    EMAIL SENT TO CLIENT REP:
    Hello Heena and Don

    Thank you for contacting the ITXA Remote Support Team. My name is Tim
    Rabbitt and this issue has been assigned to me.

    To assist you with this issue can you please send me:
    SI logs (speservices, spelogger, system log from when this issue occurs)
    ITXA logs (spelogger, wtxlogger, systemlogger)
    Results from the command: speversion.sh all
    Results from the SI, dump_info.sh command

    Regards,
    Ker Blocelf

    Hello Don and Heena:

    I forgot to mention that I'd like to get the status report from the BP
    run as well.


    Regards,
    Ker Blocelf



    ACTION PLAN:
    ITXA L2 support to contact the client no later than April 12, 2018 if
    the following has not been received by then.

    SI logs (speservices, system log and spelogger
    ITXA logs ( spelogger, wtxlogger, systemlogger)
    speversion.sh all
    dump_info
    status report

    Compare client test results versus what I observe
    +ECUREP PMRUPDATE R7 P -5725D0600 -L503/-------P3S3-18/04/10-18:54 -AT
    ECuRep Mail Gateway - Received Mail and stored in ECuRep
    Mail From: "Numen Ginclor2" <nfulawasuardin@maskedemail.ibm.com>
    /ecurep/pmr/6/0/60702,082,000/mail20180410-205418-Heena_Chandna2
    File: mail.html 8304 bytes
    +ECUREP PMRUPDATE R7 P -5725D0600 -L109/SPE -P3S3-18/04/10-18:54 -CG
    +ECUREP PMRUPDATE R7 P -5725D0600 -L109/SPE -P3S3-18/04/10-18:54 -AT
    +ECUREP PMRUPDATE R7 P -5725D0600 -L503/-------P3S3-18/04/10-18:55 -AT
    ECuRep Mail Gateway - Received Mail and stored in ECuRep
    Mail From: "Numen Ginclor2" <nfulawasuardin@maskedemail.ibm.com>
    /ecurep/pmr/6/0/60702,082,000/mail20180410-205510-Heena_Chandna2
    File: mail.html 8848 bytes
    +ECUREP PMRUPDATE R7 P -5725D0600 -L109/SPE -P3S3-18/04/10-18:55 SCG
    +ECUREP PMRUPDATE R7 P -5725D0600 -L109/SPE -P3S3-18/04/10-18:55 SAT
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/10-19:25 SCC
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/10-19:25 SAT
    S5> SERVICE GIVEN= 99 SG/99/
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/10-19:27 -CC
    S5> SERVICE GIVEN= 99 SG/99/
    CLIENT REP: Numen Ginclor, Bar Speat
    PHONE:
    E-MAIL: nfulawasuardin@maskedemail.ibm.com.,
    sbusecink@maskedemail.ibm.com


    ACTION TAKEN:
    Heena sent the same email twice in which she cc'd support asking her
    colleague to provide us with the info/logs to reproduce this issue

    EMAIL RECEIVED FROM CLIENT REP:
    ++ Roydan.

    Request you to recreate the scenario and provide logs with the help of
    Tech admin team.

    Thanks & Regards,
    Numen Ginclor



    ACTION PLAN:
    ITXA L2 support to contact the client no later than April 13, 2018 if
    the following has not been received by then.

    SI logs (speservices, system log and spelogger
    ITXA logs ( spelogger, wtxlogger, systemlogger)
    speversion.sh all
    dump_info
    status report

    Compare client test results versus what I observe. L2 support has
    already set up a test case
    +ECUREP PMRUPDATE R7 P -5725D0600 -L503/-------P3S3-18/04/11-12:05 -AT
    ***************** Blue Diamond Enhanced Secure Support *****************
    DevNode1Logs.zip
    for a Blue Diamond ESS Client was sent to ECuRep by mistake and will be
    deleted. Please inform the client to re-send the file to
    msciftpgw.im-ies.ibm.com Ask them to register for a
    Blue Diamond User ID at https://msciportal.im-ies.ibm.com if needed.
    +ECUREP PMRUPDATE R7 P -5725D0600 -L503/-------P3S3-18/04/11-12:05 -AT
    ECuRep Mail Gateway - Received Mail and stored in ECuRep
    Mail From: Bar Speat <sbusecink@maskedemail.ibm.com>
    /ecurep/pmr/6/0/60702,082,000/mail20180411-140503-Don_Smith
    File: DevNode1Logs.zip 549983 bytes
    File: mail.html 14374 bytes
    File: mail.wri 4284 bytes
    +ECUREP PMRUPDATE R7 P -5725D0600 -L109/SPE -P3S3-18/04/11-12:05 -CG
    +ECUREP PMRUPDATE R7 P -5725D0600 -L109/SPE -P3S3-18/04/11-12:05 -AT
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/11-12:37 -CT
    +Do, Neercep -5725D0600 -L18Z/-------P3S3-18/04/11-12:37 -AT
    Contact Made by mail
    +ECUREP PMRUPDATE R7 P -5725D0600 -L503/-------P3S3-18/04/11-12:38 -AT
    ECuRep Mail Gateway - mail from support
    Send to: Bar Speat <sbusecink@maskedemail.ibm.com>
    /ecurep/pmr/6/0/60702,082,000/mail20180411-143732-techsupport
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/11-12:38 -CC
    S5> SERVICE GIVEN= 99 SG/99/
    CLIENT REP: Numen Ginclor, Bar Speat
    PHONE:
    E-MAIL: nfulawasuardin@maskedemail.ibm.com.,
    sbusecink@maskedemail.ibm.com


    ACTION TAKEN:
    Bar Speat sent an email stating that he's sending the logs through
    Heena. I let him know I got his update.

    EMAIL RECEIVED FROM CLIENT REP:
    Hi Tim,



    The failed step in the test BP doesn?t have a status report. I?ve
    included a screenshot of that in the zip file along with the logs, etc.
    I believe Heena has also uploaded all of the objects that you would need
    to recreate this easily in a system on your side, please let us know if
    you don?t have those objects.



    Heena, could you please upload the attached zip to blue diamond?



    Thanks,

    Don

    EMAIL SENT TO CLIENT REP:
    Hello Don:

    I received your update and yes I do have the artifacts to reproduce this
    issue and I believe I have but I want to review your logs versus mine to
    ensure we're seeing the same exact behavior as I continue with the
    investigation.

    I look forward to getting the logs from Heena.

    Regards,
    Ker Blocelf

    ACTION PLAN:
    ITXA L2 support to contact the client no later than April 13, 2018 if
    the following has not been received by then.

    SI logs (speservices, system log and spelogger
    ITXA logs ( spelogger, wtxlogger, systemlogger)
    speversion.sh all
    dump_info
    status report

    Compare client test results versus what I observe. L2 support has
    already set up a test case
    +ECUREP PMRUPDATE R7 P -5725D0600 -L503/-------P3S3-18/04/11-13:57 -AT
    ECuRep Mail Gateway - Received Mail and stored in ECuRep
    Mail From: "Numen Ginclor2" <nfulawasuardin@maskedemail.ibm.com>
    /ecurep/pmr/6/0/60702,082,000/mail20180411-155648-Heena_Chandna2
    File: mail.html 16391 bytes
    +ECUREP PMRUPDATE R7 P -5725D0600 -L109/SPE -P3S3-18/04/11-13:57 -CG
    +ECUREP PMRUPDATE R7 P -5725D0600 -L109/SPE -P3S3-18/04/11-13:57 -AT
    +MSCIRETN -5725D0600 -BOL -P3S3-18/04/11-14:06 -AT
    The following file(s) have been uploaded to the Blue Diamond Secure FTP
    server into folder path:

    /IBM/ITVendors/IBM/60702,082,000
    DevNode1Logs.zip
    +MSCIRETN -5725D0600 -L109/SPE -P3S3-18/04/11-14:06 SCG
    +MSCIRETN -5725D0600 -L109/SPE -P3S3-18/04/11-14:06 SAT
    +ECUREP PMRUPDATE R7 P -5725D0600 -L503/-------P3S3-18/04/11-14:22 -AT
    ECuRep Mail Gateway - mail from support
    Send to: "Numen Ginclor2" <nfulawasuardin@maskedemail.ibm.com>
    /ecurep/pmr/6/0/60702,082,000/mail20180411-162159-techsupport
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/11-14:22 -CT
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/11-14:24 -CR
    S5> SERVICE GIVEN= 99 SG/99/
    CLIENT REP: Numen Ginclor, Bar Speat
    PHONE:
    E-MAIL: nfulawasuardin@maskedemail.ibm.com.,
    sbusecink@maskedemail.ibm.com


    ACTION TAKEN:
    Heena sent sent an email stating the files have been uploaded to the BD
    site. I have received them and I informed Heena of this.


    EMAIL RECEIVED FROM CLIENT REP:
    Zip file uploaded to Blue Diamond.

    Thanks & Regards,
    Numen Ginclor


    EMAIL SENT TO CLIENT REP:

    Hello Heena;

    I have received the logs and I'll look into this issue.


    Regards,
    Ker Blocelf


    ACTION PLAN:

    ITXA L2 support to investigate and provide an update no later than April
    16, 2018
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/11-14:24 SCC
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/11-14:24 SAT
    S5> SERVICE GIVEN= 99 SG/99/
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/11-15:43 -CR
    S5> SERVICE GIVEN= 99 SG/99/
    ACTION TAKEN:
    Client has a 9.0.0.8 build 10 runtime and 9.0.0.7 build 20 UI


    Reviewing logs and researching




    ACTION PLAN:
    ITXA L2 support to investigate and provide an update no later than April
    16, 2018
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/12-02:49 -CC
    S5> SERVICE GIVEN= 99 SG/99/
    ACTION TAKEN:
    Client has a 9.0.0.8 build 10 runtime and 9.0.0.7 build 20 UI


    Reviewing logs and researching




    ACTION PLAN:
    ITXA L2 support to investigate and provide an update no later than April
    16, 2018
    =Untan, Sell -5725D0600 -L109/-------P3S3-18/04/12-09:31 -AL
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/12-18:01 -CR
    S5> SERVICE GIVEN= 99 SG/99/
    ACTION TAKEN:
    Client has a 9.0.0.8 build 10 runtime and 9.0.0.7 build 20 UI


    Reviewing logs and researching




    ACTION PLAN:
    ITXA L2 support to investigate and provide an update no later than April
    16, 2018
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/12-19:27 -CR
    S5> SERVICE GIVEN= 99 SG/99/
    ACTION TAKEN:
    Reviewing logs and researching




    ACTION PLAN:
    ITXA L2 support to investigate and provide an update no later than April
    16, 2018
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/12-23:52 -CR
    S5> SERVICE GIVEN= 99 SG/99/
    ACTION TAKEN:
    Reviewing logs and researching




    ACTION PLAN:
    ITXA L2 support to investigate and provide an update no later than April
    16, 2018
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/13-01:50 -CR
    S5> SERVICE GIVEN= 99 SG/99/
    ACTION TAKEN:
    Reviewing logs and researching

    I sent an inquiry to Barry and Andrea to see if they have any insight


    ACTION PLAN:
    ITXA L2 support to investigate and provide an update no later than April
    16, 2018
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/13-18:32 -CC
    S5> SERVICE GIVEN= 99 SG/99/
    ACTION TAKEN:
    Reviewing logs and researching

    I sent an inquiry to Barry and Andrea to see if they have any insight


    ACTION PLAN:
    ITXA L2 support to investigate and provide an update no later than April
    16, 2018

    Any feedback from Barry/Andrea?
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/16-14:40 -CR
    S5> SERVICE GIVEN= 99 SG/99/
    ACTION TAKEN:
    Researching - working with SI (Barry/Andrea)


    ACTION PLAN:
    ITXA L2 support to investigate and provide an update later tonight
    (April 16, 2018)

    Any feedback from Barry/Andrea?
    +Do, Neercep -5725D0600 -L109/SPE -P3S3-18/04/17-02:10 -CC
    S5> SERVICE GIVEN= 99 SG/99/
    CLIENT REP: Numen Ginclor, Bar Speat
    PHONE:
    E-MAIL: nfulawasuardin@maskedemail.ibm.com.,
    sbusecink@maskedemail.ibm.com





    ACTION TAKEN:
    I'm still working with Barry/Andrea to see if they have any insight to
    this issue.

    I let the client know we are stil investigating.



    EMAIL SENT TO CLIENT REP:
    Hello Heena:

    Just letting you know that I'm continuing to look into this invalid
    iterator issue for you. I'll keep you updated on our progress.


    Regards,
    Ker Blocelf



    ACTION PLAN:
    ITXA L2 support to investigate and provide an update no later than April
    19, 2018

    Any feedback from Barry/Andrea?
    +ECUREP PMRUPDATE R7 P -5725D0600 -L503/-------P3S3-18/04/17-02:10 -AT
    ECuRep Mail Gateway - mail from support
    Send to: "Numen Ginclor2" <nfulawasuardin@maskedemail.ibm.com>
    /ecurep/pmr/6/0/60702,082,000/mail20180417-041033-techsupport
  • Admin
    Luke Raiano commented
    09 Jan 15:16

    Reference: TS000903363 | Product: Transformation Extender Advanced | Created: 2018-04-08 | Modified: 2018-12-14

    Description:

    05:21 pm04/08

    *** Electronic submission by customer via SR tool, version 3.4.7        
    *** Preferred contact method: Email-address.
    *** Customer contact full name: Heena Chandna
    *** Email: tsalumbeessalf@maskedemail.ibm.com

    .
    Problem Details
    .
    Product or Service: Sterling B2B Integrator 5.2.0
    Component ID: 5725D0600
    .
    Operating System: Linux
    .
    Problem title
    SBI Document Extraction service - SPEContextParms.PDToProcessData
    issue
    .
    Problem description and business impact

    For the SPEContextParms.PDToProcessData parameter, While setting this
    value to NO does appear to stop the split documents from being written
    to Process Data, the For Each Document service of SBI doesnt seem to
    be able to iterate through them as it is able to when using the SBI
    Document Extraction service. When using the attached BPML, ITX map
    (medclaim_docext), and test data (claim_out.txt) we receive the
    following error on the For Each Document step.



    (NOTE: The zip in Blus Diamond is a sample TX project provided in an
    HCL training course about using the ITXA doc extract functionality)

    Refer BPID Details file in Blue Diamond for this PMR.

    One difference I can see in the output of ITXA doc extract vs SBI doc
    extract is in this node in process data. I have a suspicion this could
    have something to do with it:



    SBI:

    <SplitDocs SCIObjectID="3493281628d4eb633node1"/>



    ITXA:

    <SplitDocs>com.ibm.spe.standards.base.SplitNode@e4aee365</SplitDocs>

    Opening PMR in continuation to PMR 49565,082,000. Please advise.

    NOTE: Please include Bar Speat (sbusecink@maskedemail.ibm.com) in all
    email communication for this PMR.


    .
    *** --- FOR SR USE ONLY ---
    *** XRQXSRprNode2901523207566369
    *** CAG388023 ENG Y
    *** MTS
    *** 5725D06:520/5725D0600:520 (ENT)

    Resolution Description:

    09:03 pm05/16

    ITXA development has looked into this and they have stated that ITXA is currently not unable to duplicate what SI is doing because ITXA's ProcessData cannot hold a true Object - like an ArrayList.  When DocumentExtractionService calls SPEContext.setWFContent with the ArrayList, it can only put in String values of the objects in the list,  which is why you see "com.ibm.spe.standards.SplitNode@d12c1bd1".                               <br>                                                                          <br>ITXA development group has suggested that you use SPEContextParams.PDToProcessData=YES.    <br>They said this because this is essentially what occurs anyway when SI's ForEach service runs after SI's DocExtractService and it reads the        <br>SplitDocs ArrayList for each SplitNode object (which holds the document) in the ArrayList.                       <br><br>Although it is recommended that  SPEContextParams.PDToProcessData be set to YES, the SI team has documented this does incur a performance penalty