You are correct i have installed TRADACOMS 9 ORDHDR docuTYpe and schema in my IS and show up in TNC as well as i have created processing rule to identify document type but still processing rule is not getting invoke and doctype is identify is “EDIINT” and i am using AS2 connection
Indeed but still transaction is unable to recognize documentType in Trading Network Console with contentType = application/edi-x12 when i send above attached Tradacoms 9 ORDHDR In sender and receiver partner profile is getting recognize but actual DocumentType “Tradacoms 9 ORDHDR” is unable to recognize it’s selecting default document Type in TN Console “EDIINT”.
I like to mention few more details i am getting EDI messages via RI AS2 connection so i too believe tht i am having issue with EDIINT payload in TN. while GXS team sending message with sign&encrypted format.here is my TN profile setting look like sender A and receiver B TN profile, IN A profile Extended Field S/MIME"sing&encrypted" and GXS certificate installed and B Profile S/MIME"plain" with our Orgn certificate installed we have done hand shake of certificate as well and i have tried with all test cases by modifying profiles A & B S/MIME setting 1 sign&encrypted plain → same result
2 sign&encrypted sign&encrypted → same result 3 plain plain → same result.i am able to see EDINT and EDINT MDN message in TN but can’t able to recognize TRADACOMS 9 ORDHDR documentType with processing rule.Find the TN Console screen short for EDIINT and EDIINT MDN activity logs
i have few more business transaction with same setup and it’s working fine only difference it that TN profile is set with S/MIME = plain and payload data is processing fine without any issue but in this case we are getting sign&encrypted data where certificate handshake is done and S/MIME is set to sign&encrypted format.
while i am sending plain data from my local IS to TN console → work fine but when i set my TN profile and set to sign&encrypted installed certificate To and Fro getting exception as " Error encountered in wm.tn.security:getSigningKeyAndChain. Private key not defined. Please call wm.tn.security:getVerifyingChain" but private key is define very well in TN.
Are you testing this internally or with TP also?
yeah i am doing end to end testing with extenal TP as well but getting
transaction in TN Console as show in attached screen shot.
2 positive EDIINT MDN
but somewhere actual documentType is missing “TRADACOMS 9 ORDHDR” which invoke processing rule.
External TP sending data with sign&encrypted format in following ContentType