App Connect

App Connect

Join this online user 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.


#Applicationintegration
#App Connect
#AppConnect
#Integration
#Automation
 View Only
  • 1.  IBM App Connect Enterprise Edition Compute Node

    Posted 12/15/20 02:25 PM

    Hi Team,
    I would like to inform you that we are using IBM App Connect Enterprise Edition v11.0.0.6. We did a small POC with MQInput/FileInput=>ComputeNode=>MQOutput/FileOutput. Nodes which converts the message from CSV to XMLNSC. We have specified mandatory properties in code and written below code in compute node but when we test this flow, nothing (content) is going into destination queue or file and not even exception. When we see the messages in MQExplorer also, we could see there is no MQSTR assigned to the Message Format but when we deploy same in previous versions, the content is going as expected. Kindly check and let us know the way forward on this.

    Flow:

    ESQL Code:

    CREATE COMPUTE MODULE CSVTOXMLFlow_Compute

    CREATE FUNCTION Main() RETURNS BOOLEAN

    BEGIN

    CALL CopyMessageHeaders();

    CALL CopyEntireMessage();

    RETURN TRUE;

    END;

    CREATE PROCEDURE CopyMessageHeaders() BEGIN

    DECLARE I INTEGER 1;

    DECLARE J INTEGER;

    SET J = CARDINALITY(InputRoot.*[]);

    WHILE I < J DO

    SET OutputRoot.*[I] = InputRoot.*[I];

    SET I = I + 1;

    END WHILE;

    END;

    CREATE PROCEDURE CopyEntireMessage() BEGIN

    DECLARE inRef REFERENCE TO InputRoot.DFDL.CSV.record;

    CREATE LASTCHILD OF OutputRoot NAME 'XMLNSC';

    DECLARE outRef REFERENCE TO OutputRoot.XMLNSC;

    WHILE LASTMOVE (inRef) DO

    CREATE LASTCHILD OF OutputRoot.XMLNSC AS outRef NAME 'Details';

    SET outRef.FName = inRef.field1;

    SET outRef.LName = inRef.field2;

    SET outRef.City = inRef.field3;Hi 

    MOVE inRef NEXTSIBLING;

    END WHILE;

    --SET outRef.MSG = 'Hello';

    END;

    END MODULE;


    MQ Explorer Output Queue:


    Thanks & Regards,
    Padma

     



    ------------------------------
    Padma Maggari
    ------------------------------


  • 2.  RE: IBM App Connect Enterprise Edition Compute Node

    Posted 12/16/20 05:26 AM
    You suspect that ESQL is the problem?
    How did you transform your Message Flow from version 10 to version 11?
    Did you also test the Message flow inside the Broker Toolkit?

    SET outRef.City = inRef.field3;Hi

    I guess the Hi is a typo.

    You probably had to share the whole flow with us to find / discuss any issues.



    ------------------------------
    Matthias Jungbauer
    ------------------------------



  • 3.  RE: IBM App Connect Enterprise Edition Compute Node

    Posted 12/16/20 08:00 AM
      |   view attached

    Hi Team,

    Please find attached the flow. Kindly verify and revert.

     

    Thanks & Regards,

    Padma

     




    Attachment(s)

    zip
    TestApp.zip   2 KB 1 version


  • 4.  RE: IBM App Connect Enterprise Edition Compute Node

    Posted 12/17/20 05:00 AM

    Hi Padma

    The message flow in the zip is not related with DFDL, right?
    It is MQ to MQ with an ESQL that transforms a XML
    The code does not contain a reference to a queue manger, so I assume it is working with a local queue manager.
    Once you put a message into TEMPQ - is it possible that something else consumes the message?
    Or that you put the message into the wrong queue managers TEMPQ queue.
    Are you working parallel with IIB 10 and ACE 11 ?

    Do you have a sample of your failing input message?



    ------------------------------
    Matthias Jungbauer
    ------------------------------



  • 5.  RE: IBM App Connect Enterprise Edition Compute Node

    Posted 12/17/20 05:23 AM
      |   view attached

    Thanks for the response. Sorry for the wrong attachment. Please find attached the same. Please find my answers below.

     

    Thanks & Regards,

    Padma

     




    Attachment(s)

    zip
    DFDL.zip   4 KB 1 version


  • 6.  RE: IBM App Connect Enterprise Edition Compute Node

    Posted 12/18/20 05:27 AM

    Per eye sight, I don't see an issue in the files you provided.

    I would suggest a regression test on CSV.xsd:

    When you have defined your DFDL schemas, test them in the editor before they are used on a production system.

    https://www.ibm.com/support/knowledgecenter/SSTTDS_11.0.0/com.ibm.etools.mft.doc/df20065_.html



    ------------------------------
    Matthias Jungbauer
    ------------------------------



  • 7.  RE: IBM App Connect Enterprise Edition Compute Node

    Posted 12/21/20 01:19 AM

    HI Team,

    Thanks for the update. Then why we are unable to view the messages in the destination in ACE 11.0.0.6?

     

    Thanks & Regards,

    Padma