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
  • 1.  Error in Configuration of Remote WorkFlow Server Alias

    Posted 12/20/03 12:37 AM

    Hi,
    I have started with wM workflow. I tried to configure remote server aliases. I have configured to alias one for IS and one for WorkFlow Server. When I test for IS, it works. When I tested workflow server connection, it failed with following error:

    Unable to connect to remote server WFServer: com.wm.net.NetException: [ISC.0064.9324] Server Error: Not Implemented

    I have attached the screenshot of configuration and error.
    Please take a look.
    Any kind of help is appreciated.

    Regards,
    Nilesh

    Remote Alias configuration Error
    Remote WorkFlow Server Configuration Error.zip (7.6 k)


    #webMethods
    #MWS-CAF-Task-Engine
    #webMethods-BPMS


  • 2.  RE: Error in Configuration of Remote WorkFlow Server Alias

    Posted 12/20/03 08:14 AM

    hi nilesh,

    From the error message u get it looks like the server is not present on port 6000, check again whether it is running.

    regards
    Jayesh


    #webMethods-BPMS
    #webMethods
    #MWS-CAF-Task-Engine


  • 3.  RE: Error in Configuration of Remote WorkFlow Server Alias

    Posted 12/20/03 08:59 AM

    Jayesh,
    Thanks for response.

    I checked worklflow server is running. I am able to connect to server from workflow client without any problem. I can open workflow designer, workflow users,etc.

    Any other clue or idaea ???

    Regards,
    Nilesh


    #webMethods-BPMS
    #webMethods
    #MWS-CAF-Task-Engine


  • 4.  RE: Error in Configuration of Remote WorkFlow Server Alias

    Posted 06/23/04 02:11 PM

    This error can safely be ignored. You should have been able to successfully register the physical Workflow server and assign a Logical Workflow server to this physical server.

    The error happens because physical servers are implemented as Integration Server remote server aliases, regardless if the physical server is a Workflow server or an IS server. When the WmAdmin server tries to verify the connection between the WmAdmin server and the remote WF server (usually by calling wm.server:ping on the remote server) it fails with the error you’re seeing, for the obvious reason that you can’t call the IS service wm.server:ping on a Workflow server.


    #webMethods
    #webMethods-BPMS
    #MWS-CAF-Task-Engine