Seeburger 1.8.2 Upgrade: Subject missing in AS2 Ack

Question

Hi All,
After upgrading our PI environment with Seeburger 1.8.2, we started facing an issue in the Ack Report (MDN Response) received in response to the AS2 messages posted to our partner.
We have a scenario, where HTTPS AS2 messages are posted through the Seeburger AS2 Adapter receiver channel to an external partner with 'Handle received MDN option' set as "Refer to XI system".
We have another AS2 Adapter sender Reports channel which receives these MDN and provides confirmation on posting of these messages to the end-users.
After the upgrade, the Subject value is missing in the Ack Reports XML.
Please find below the Ack Reports XML pre-upgrade:
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DtReport xmlns="http://uri.seeburger.com/dt/master/schema">
    <correlationId>4ce4a7f9-9dd1-6fb3-e100-00000f8de046</correlationId>
    <category>DeliveryReport</category>
    <state>SUCCESS</state>
    <finalReport>true</finalReport>
    <freeText>Received synchronous MDN successfully.</freeText>
    <specificData>
        <key>messageID</key>
        <value>&lt;[email protected]&gt;</value>
    </specificData>
    <specificData>
        <key>subject</key>
        <value>DBDCRI SD=Sender,RV=Receiver,MF=XXX,MT=YYY,FN=0215_0215_2010-11-18T07:35:01.887Z</value>
    </specificData>
    <specificData>
        <key>channelID</key>
        <value></value>
    </specificData>
    <specificData>
        <key>channel</key>
        <value>DBDC_MDNReport_AS2_Sender</value>
    </specificData>
    <specificData>
        <key>originalchannel</key>
        <value>DBDC_PaymentRunFromgSAPAndUlysses_AS2_Receiver</value>
    </specificData>
    <specificData>
        <key>to</key>
        <value>DBDC</value>
    </specificData>
    <specificData>
        <key>from</key>
        <value>Syngenta</value>
    </specificData>
</DtReport>
And please find below the Ack Reports XML pre-upgrade (where the subject is missing now):
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<DtReport xmlns="http://uri.seeburger.com/dt/master/schema">
    <clientId>000</clientId>
    <correlationId>eec9b8da-a217-4b48-3729-a2c5e55b10f1</correlationId>
    <category>DeliveryReport</category>
    <state>SUCCESS</state>
    <finalReport>true</finalReport>
    <freeText>Received synchrone MDN successfully.</freeText>
    <specificData>
        <key>messageID</key>
        <value>&lt;[email protected]&gt;</value>
    </specificData>
    <specificData>
        <key>subject</key>
        <value/>
    </specificData>
    <specificData>
        <key>channelID</key>
        <value></value>
    </specificData>
    <specificData>
        <key>channel</key>
        <value>DBDC_MDNReport_AS2_Sender_Test</value>
    </specificData>
    <specificData>
        <key>originalchannel</key>
        <value>DBDC_PaymentRunFromgSAPAndUlysses_AS2_Receiver_Test</value>
    </specificData>
    <specificData>
        <key>to</key>
        <value>DBDC</value>
    </specificData>
    <specificData>
        <key>from</key>
        <value>Syngenta</value>
    </specificData>
    <reportAttachment refID="79282d90-f65a-11df-8fa1-9a790f8de00a">
        <ns1:objectInfo charset="binary" creation="2010-11-22T17:03:48.457+00:00" location="MEMORY" size="1237" type="INLINE" xmlns:ns1="http://uri.seeburger.com/bisas/message/schema"/>
    </reportAttachment>
</DtReport>
As part of Seeburger upgrade, the below shown latest SCAs have already been deployed:
AS2AdapterXI.sca
SeeBaseToolsXI.sca
SeeExtendedToolsXI.sca
SeeModuleCollectionXI.sca
SeeSolutionIdModuleXI-as2.sca
After the Seeburger upgrade, we have updated the AS2AdapterMetadata.xml within our repository.
Also, we have imported the latest version of the below XSDs into the repository:
dtreport.xsd
dtglobaltypes.xsd
attachments.xsd
dtarchiving.xsd
Could you please help me in resolving this, in case anyone of you have encountered a similar issue previously.
Thanks & Regards,
ROSIE SASIDHARAN

Answer 1

Actually, I saw the rant in the bug reporting tool on dropping pam_userdb.
I understand fully the decision:
- PAM should not have plentora of dependencies: nobody would integrate
  pam-sqlite, pam-postgresql or other pam modules with external dependencies
  into the 'pam' base package
- Berkley DB has licensing issues, so AUR is a good place for it
- ArchLinux is a bleeding edge distribution, there is no such rule as "keep features for
  the current main release".
I'm personally opting for an AUR project 'pam-userdb' which just provides this one module,
so nobody has to migrate 200 users on his production system.
And a short notice on the main page about the dropping of db support in PAM and the
availability of the separate module.
Last edited by andreas_baumann (2014-06-07 12:15:06)