Topic
  • 3 replies
  • Latest Post - ‏2016-02-09T19:30:48Z by mkhatibi@ca.ibm.com
azghar
azghar
3 Posts

Pinned topic Exposing Data Extensions as WS

‏2013-05-01T17:32:44Z | mdm mdm-migration workbench

Attachments

  • azghar
    azghar
    3 Posts

    Re: Exposing Data Extensions as WS

    ‏2013-05-01T17:34:01Z  

    HI Everybody,

    I have created a Data Extension for ProductAdminSysKey and workbench has generated related WS projects, converters, **Deser.class etc

    I have changed ProductPort.wsdl to import new xsds and changed object at AddProductAdminSyskey to XproductAdminSyskey

    When I inovke the addProductAdminSyskey with extension object i get following error

    <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:soapenc="http://schemas.xmlsoap.org/soap/encoding/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
    <soapenv:Header/>
    <soapenv:Body>
    <soapenv:Fault>
    <faultcode xmlns:p303="http://www.ibm.com/xmlns/prod/websphere/wcc/common/intf/schema">p303:ProcessingException</faultcode>
    <faultstring>com.ibm.wcc.service.intf.ProcessingException</faultstring>
    <detail encodingStyle="">
    <p891:ProcessingException xmlns:p891="http://www.ibm.com/xmlns/prod/websphere/wcc/common/port">
    <applicationMessage>
    <type code="SYSERR"/>
    <details>com.uhg.mdm.product.dataextension.product.service.ext.to.convert.XProductAdminSysKeyBObjExtConverter</details>
    <componentType code="108"/>
    <severity code="0"/>
    <reason code="4914">Construct transaction response failed.</reason>
    <languageCode>100</languageCode>
    </applicationMessage>
    </p891:ProcessingException>
    </detail>
    </soapenv:Fault>
    </soapenv:Body>
    </soapenv:Envelope>

    changes are in WSDL are as follows

    1. <xsd:import namespace="http://www.uhc.com/services/mdm/product/Product/Ext/schema" schemaLocation="ProductDataExtensions_ProductExt.xsd"/>

    2. at xsd schema

    xmlns:ProductRelAdmin=http://www.**.com/services/mdm/product/Product/Ext/schema

    3.

    <elementname="AddProductAdminSysKey">

    <complexType>

    <sequence>

    <elementname="control" type="common-intf:Control"/>

    <elementname="request" type="ProductRelAdmin:XProductAdminSysKey"/>

    </sequence>

    </complexType>

    </element>

    Please help me in this regrad thanks

    Azghar

  • N7DW_Roberto_Rasi
    N7DW_Roberto_Rasi
    2 Posts

    Re: Exposing Data Extensions as WS

    ‏2016-02-06T09:02:49Z  

    Hi Azghar,

    I see the post date is 2 years ago, but there are no reply.

    I found the same problem now that we are migrating an existing project from version 8.5 to MDM 11.4

    I generate code for legacy web-service, the additions work well.

    But with data extensios, I had the sam problem that you found.

     

    Did you find a solution?

     

  • mkhatibi@ca.ibm.com
    mkhatibi@ca.ibm.com
    3 Posts

    Re: Exposing Data Extensions as WS

    ‏2016-02-09T19:30:48Z  

    Hi Azghar,

    I see the post date is 2 years ago, but there are no reply.

    I found the same problem now that we are migrating an existing project from version 8.5 to MDM 11.4

    I generate code for legacy web-service, the additions work well.

    But with data extensios, I had the sam problem that you found.

     

    Did you find a solution?

     

    Hello,

    What's your soap response? If it's similar to the earlier post, it's likely caused by the actual logic in XProductAdminSysKeyBObjExtConverter class that you must have developed for your extension. What exception traces do you see in your SystemOut.log or trace.log?