IBM webMethods Hybrid Integration

IBM webMethods Hybrid Integration

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



#Automation


#Applicationintegration
#webMethods
#Integration
 View Only
Expand all | Collapse all

Unableto create a wsdl

  • 1.  Unableto create a wsdl

    Posted 01/06/14 01:39 AM

    I am trying to create a WSDL and getting the below error
    [ISC.0081.9164] Exception occurred during generation of WSDL for service contract: [ISC.0124.9005] Document to XSD error: Field in Abc.doc.createSample cannot be represented in XML Schema. The field name contains a prefix but an XML Namespace property is not assigned to the field
    Intially I have generated the wsdl with the xml schema.I worked fine.And due to some reasons I have deleted the package in which the wsdl is generated.After package creation,when trying to generate the wsdl, I am getting the above error. Request for an Immediate solution. Below is the schema

    XML Schema
    <xs:schema attributeFormDefault=“unqualified” elementFormDefault=“qualified” xmlns:xs=“XML Schema” >
    <xs:element name=“cms-data”>
    xs:complexType
    xs:sequence
    <xs:element name=“ABC” maxOccurs=“unbounded” minOccurs=“1”>
    xs:complexType
    xs:sequence
    <xs:element name=“products”>
    xs:complexType
    xs:sequence
    <xs:element type=“xs:string” name=“product-id” maxOccurs=“unbounded” minOccurs=“0”/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name=“Cust”>
    xs:complexType
    xs:sequence
    <xs:element type=“xs:short” name=“ocn” maxOccurs=“unbounded” minOccurs=“0”/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name=“custaff”>
    xs:complexType
    xs:sequence
    <xs:element type=“xs:string” name=“colt-bu” maxOccurs=“unbounded” minOccurs=“0”/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    <xs:element name=“POC”>
    xs:complexType
    xs:sequence
    <xs:element type=“xs:string” name=“country” maxOccurs=“unbounded” minOccurs=“1”/>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    <xs:attribute type=“xs:short” name=“id” use=“required”/>
    <xs:attribute type=“xs:byte” name=“revision” use=“required”/>
    <xs:attribute type=“xs:string” name=“old-ref” use=“optional”/>
    <xs:attribute type=“xs:string” name=“new-ref” use=“optional”/>
    <xs:attribute type=“xs:short” name=“ocn” use=“required”/>
    <xs:attribute type=“xs:string” name=“legal-entity” use=“required”/>
    <xs:attribute type=“xs:string” name=“type” use=“required”/>
    <xs:attribute type=“xs:string” name=“title” use=“optional”/>
    <xs:attribute type=“xs:string” name=“start-date” use=“required”/>
    <xs:attribute type=“xs:byte” name=“term” use=“optional”/>
    <xs:attribute type=“xs:string” name=“end-date” use=“optional”/>
    <xs:attribute type=“xs:string” name=“status” use=“required”/>
    </xs:complexType>
    </xs:element>
    </xs:sequence>
    </xs:complexType>
    </xs:element>
    </xs:schema>


    #soa
    #API-Management
    #webMethods


  • 2.  RE: Unableto create a wsdl

    Posted 06/24/14 12:17 PM

    Hi Experts,

    Getting the same error while creating the provider.

    Please suggest the solution.

    Thanks,
    Abdul Pasha


    #soa
    #API-Management
    #webMethods


  • 3.  RE: Unableto create a wsdl

    Posted 06/25/14 04:19 AM

    from where you trying generate (designer or developer) , which version?
    while generating provider, which soap version you selected?

    Please drop additional details to get answers from others.

    Best
    ~Raj


    #API-Management
    #webMethods
    #soa


  • 4.  RE: Unableto create a wsdl

    Posted 06/25/14 04:58 AM

    Hi Abdul,

    Can you share the below details:

    webMethods version?
    Do you want to expose your flow service as a provider?


    #soa
    #webMethods
    #API-Management


  • 5.  RE: Unableto create a wsdl

    Posted 06/25/14 05:06 AM

    Hi Raj/Mahesh,

    Thanks for your response,

    We are using webMethods 8.2 and am trying to expose my flow service as a provider.

    Am trying in both Developer and Designer getting the same error.

    Am using SOAP 1.1, HTTPS, Document/Literal while creating provider.

    Please suggest the solution.

    Thanks,
    Abdul Pasha


    #API-Management
    #soa
    #webMethods


  • 6.  RE: Unableto create a wsdl

    Posted 06/25/14 05:48 AM

    Send Error log, and snapshot would really help in addition.


    #API-Management
    #webMethods
    #soa


  • 7.  RE: Unableto create a wsdl

    Posted 06/25/14 09:05 AM

    How many services are you exposing as the provider…

    Can you re-try again on developer and share us the screen shot…

    From when are you facing this issue…? Where you able to create the same in the past…?

    Also share your IS fix levels from IS admin page (about)


    #API-Management
    #webMethods
    #soa


  • 8.  RE: Unableto create a wsdl

    Posted 07/22/15 08:13 AM

    Hi,

    I am also getting the same error.

    com.wm.app.b2b.server.ServiceException: [ISC.0081.9164] Exception occurred during generation of WSDL for service searchCriteriaProviderWSD: [ISC.0124.9005] Document to XSD error: Field InvoiceTrackingStatus.Documents:searchCriteriaPage cannot be represented in XML Schema. The field name contains a prefix but an XML Namespace property is not assigned to the field
    at wm.server.nsimpl._putNode(nsimpl.java:6035)
    at wm.server.nsimpl.makeNode(nsimpl.java:4881)
    at sun.reflect.GeneratedMethodAccessor720.invoke(Unknown Source)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:439)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:635)
    at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:41)
    at com.wm.ps.serviceMock.ServiceInterceptor.process(ServiceInterceptor.java:343)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)
    at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:238)
    at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:51)
    at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
    at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:272)
    at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:30)
    at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:399)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:539)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:384)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:234)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:94)
    at com.wm.app.b2b.server.Service.doInvoke(Service.java:652)
    at com.wm.app.b2b.server.Service.doInvoke(Service.java:540)
    at wm.server.ws.is2wsd(ws.java:2527)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
    at java.lang.reflect.Method.invoke(Method.java:597)
    at com.wm.app.b2b.server.JavaService.baseInvoke(JavaService.java:439)
    at com.wm.app.b2b.server.invoke.InvokeManager.process(InvokeManager.java:635)
    at com.wm.app.b2b.server.util.tspace.ReservationProcessor.process(ReservationProcessor.java:41)
    at com.wm.ps.serviceMock.ServiceInterceptor.process(ServiceInterceptor.java:343)
    at com.wm.app.b2b.server.invoke.StatisticsProcessor.process(StatisticsProcessor.java:44)
    at com.wm.app.b2b.server.invoke.ServiceCompletionImpl.process(ServiceCompletionImpl.java:238)
    at com.wm.app.b2b.server.invoke.ValidateProcessor.process(ValidateProcessor.java:51)
    at com.wm.app.b2b.server.invoke.PipelineProcessor.process(PipelineProcessor.java:171)
    at com.wm.app.b2b.server.ACLManager.process(ACLManager.java:272)
    at com.wm.app.b2b.server.invoke.DispatchProcessor.process(DispatchProcessor.java:30)
    at com.wm.app.b2b.server.AuditLogManager.process(AuditLogManager.java:399)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:539)
    at com.wm.app.b2b.server.invoke.InvokeManager.invoke(InvokeManager.java:384)
    at com.wm.app.b2b.server.ServiceManager.invoke(ServiceManager.java:234)
    at com.wm.app.b2b.server.comm.DefaultServerRequestHandler.handleMessage(DefaultServerRequestHandler.java:119)
    at com.wm.app.b2b.server.HTTPMessageHandler.process(HTTPMessageHandler.java:160)
    at com.wm.app.b2b.server.HTTPDispatch.handleRequest(HTTPDispatch.java:195)
    at com.wm.app.b2b.server.Dispatch.run(Dispatch.java:358)
    at com.wm.util.pool.PooledThread.run(PooledThread.java:131)
    at java.lang.Thread.run(Thread.java:662)

    Please help me resolve it.
    I am using 8.0 and trying to create the provider in developer.

    Regards
    Jyoti


    #webMethods
    #API-Management
    #soa


  • 9.  RE: Unableto create a wsdl

    Posted 07/22/15 08:30 AM

    You must provide some extended settings to IS, try and get back:

    watt.core.schema.createSchema.omitXSDAny=true


    #webMethods
    #soa
    #API-Management


  • 10.  RE: Unableto create a wsdl

    Posted 07/22/15 08:31 AM

    You must provide some extended settings to IS, try and get back:

    watt.core.schema.createSchema.omitXSDAny=true


    #soa
    #API-Management
    #webMethods


  • 11.  RE: Unableto create a wsdl

    Posted 07/22/15 07:51 PM

    i had faced the same issue few days back. it is a behavior in 8.2 which got introduced in one of the fix to support WSDL generated in earlier versions.

    check your field for which you are getting error. you have set namspace key but no value or vice versa. so either clean it up and then generate or complete the key value pair.

    few other option you can try if you are not in position to edit document

    watt.server.soap.decodeElementWithPrefix=true - set in extended setting and restart IS. this may work depending if you created this service in earlier version vs if it is a new one. i guess yours is a newly created in 8.2. this setting didn’t work for me.

    Let me know if this work for you.

    My suggestion will be to clean up your documents to have a proper key/value pair of namespace as this is a new implementation and you will save yourself from future issues.


    #API-Management
    #webMethods
    #soa