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

GetProcAddress failed - Webmethods - JDE Demo Jr

  • 1.  GetProcAddress failed - Webmethods - JDE Demo Jr

    Posted 01/29/03 04:41 PM

    hi

    I am using webMethods with JDE Demo JR
    to create and integration using
    JDE adapter

    i have done all the required settings
    but not able to run the JDE adapter

    when i run the JDE adapter in webMethods adapter configuration tool
    noting is displayed on screen
    but in enterprise integrator i am not able to create any configured operations, etc

    i have set the nettrace=5 in [JDENET] jde.ini
    and get the following output in jdedebug.log

    Jan 29 16:18:27 ** 1628/3372 Socket 400,event-FD_ACCEPT,error-0
    Jan 29 16:18:27 ** 1628/3372 createSocket-connections used: 3 of 102
    Jan 29 16:18:27 ** 1628/3372 acceptConnection for Socket 400
    Jan 29 16:18:27 ** 1628/3372 connection handled by net: 1628
    Jan 29 16:18:27 ** 1628/3372 putQueue 01B2CD14,msg-1,reqpid-3372
    Jan 29 16:18:27 ** 1628/3372 Socket 632,event-FD_WRITE,error-0
    Jan 29 16:18:27 ** 1628/3372 getQueue 01B2CD14,msg-1,reqid-3372
    Jan 29 16:18:27 ** 1628/3372 Socket 632,send-36,rc-(36),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,send-8,rc-(8),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,send-5,rc-(5),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,send-8,rc-(8),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-36,rc-(36),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-8,rc-(8),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-8,rc-(8),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-8,rc-(8),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-5,rc-(5),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-8,rc-(8),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-5,rc-(5),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-8,rc-(8),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-2,rc-(2),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-8,rc-(8),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-5,rc-(5),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-8,rc-(8),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-13,rc-(13),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-8,rc-(8),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-5,rc-(5),err-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-8,rc-(8),err-0
    Jan 29 16:18:27 ** 1628/3372 putQueue 6179C668,msg-1,reqpid-0
    Jan 29 16:18:27 ** 1628/3372 getQueue 6179C668,msg-1,reqid-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,event-FD_WRITE,error-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:27 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:27 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:27 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:27 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:27 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:27 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:28 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:28 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:28 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:28 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:28 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:28 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:28 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:28 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:28 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:28 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:28 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:28 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:28 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:28 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:28 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:28 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:28 ** 1628/3372 Socket 632,event-FD_READ,error-0
    Jan 29 16:18:28 ** 1628/3372 Socket 632,recv-36,rc-(-1),err-10035
    Jan 29 16:18:28 ** 1628/1664 GetProcAddress failed - ‘_JDENET_DispatchMessage@DFT’
    Jan 29 16:18:28 ** 1628/1664 msgType 904 not processed by dispatch Function ‘_JDENET_DispatchMessage@DFT’
    Jan 29 16:18:28 ** 1628/1664 putQueue 6179C318,msg-1,reqpid-0

    what i am guessing is webMethods is trying to make a connection with JDE and failing at that

    can anyone help me on this
    thanks


    #Adapters-and-E-Standards
    #Integration-Server-and-ESB
    #webMethods


  • 2.  RE: GetProcAddress failed - Webmethods - JDE Demo Jr

    Posted 01/30/03 04:44 AM

    I think it does not matter what you do with any release of the OneWorld adapter, it will not be able to function with DemoJnr. The issue is that the adapter sets up sockets to communicate with the kernels of a OneWorld Enterprise server. Kernel 6 runs business functions, Kernel 16 generates lists from the Table Conversion engine and Kernels 19 and 20 handle the two event notification models. I don’t know whether you have taken this adapter from webMethods or from JDE but even if you have the more primitive webMethods adapter you will not be able to use it with standalone. DemoJnr has no OneWorld server component - it is just a client - so there are no services running. JDE got away with this by putting the business, control and object tables in Access, which does not require database software to run it, just an ODBC driver. With the minimum tinkering they were able to get the fat client to operate entirely on its own without an Enterprise server and that gave them the standalone version. Hope this helps but sorry it is bad news. What you can do, provided you have no license issues, is to install SQLServer, OneWorld Xe server and OneWorld client all on your laptop with webMethods Enterprise Broker and so on. Then you will have a complete personal sandbox. You will need at least 512Mb RAM (a gig would be better) and maybe 30Gb of free disk but this is a fraction of the spec of most new laptops. Who needs mainframes these days?

    Jules


    #Adapters-and-E-Standards
    #webMethods
    #Integration-Server-and-ESB