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.

 View Only
Expand all | Collapse all

webMethods Messaging subsystem was not initialized

  • 1.  webMethods Messaging subsystem was not initialized

    Posted Fri February 05, 2016 08:35 AM

    The webMethods Messaging subsystem was not initialized.

    We have developed a new 9.8 server (DEV) and installed IS and broker components.

    while I am trying to configure the Broker Messaging in IS console below error occured in IS 9.8 Version. Please assist on this issue.

    Gwm.server.messaging:getConnectionAliasReport
    class com.wm.app.b2b.server.ServiceException
    [ISS.0153.9012] The webMethods Messaging subsystem was not initialized. No webMethods Messaging features are available. Attached the screenshot.


    #B2B-Integration
    #Integration-Server-and-ESB
    #webMethods


  • 2.  RE: webMethods Messaging subsystem was not initialized

    Posted Fri February 05, 2016 08:43 AM

    No worries, its a known issue to me, modify dispatch.cnf and change all “-1” to “0”.

    Hope you know where dispatch.cnf file exists?


    #webMethods
    #Integration-Server-and-ESB
    #B2B-Integration


  • 3.  RE: webMethods Messaging subsystem was not initialized

    Posted Fri February 05, 2016 08:46 AM

    hey … we have tried this option already but no luck…I see no “-1” at all in dispatch.cnf however.

    Please let me know an alternative solution


    #webMethods
    #B2B-Integration
    #Integration-Server-and-ESB


  • 4.  RE: webMethods Messaging subsystem was not initialized

    Posted Fri February 05, 2016 08:51 AM

    You may also delete the dispatch.cnf file from config after backup and then start the IS.

    Let me know the results.


    #Integration-Server-and-ESB
    #webMethods
    #B2B-Integration


  • 5.  RE: webMethods Messaging subsystem was not initialized

    Posted Fri February 05, 2016 08:52 AM

    Hi,
    Share me the location of dispatch.cnf file where you actually located?


    #webMethods
    #Integration-Server-and-ESB
    #B2B-Integration


  • 6.  RE: webMethods Messaging subsystem was not initialized

    Posted Fri February 05, 2016 08:52 AM

    Already done this… but no luck as i said


    #Integration-Server-and-ESB
    #webMethods
    #B2B-Integration


  • 7.  RE: webMethods Messaging subsystem was not initialized

    Posted Fri February 05, 2016 09:00 AM

    Did you try the dispatch file from backup i.e, <IS_Instance_Name>/config/backup

    Looks strange to me as it worked for me in the past :slight_smile:

    Nevertheless attach your server.log for further analysis.


    #Integration-Server-and-ESB
    #webMethods
    #B2B-Integration


  • 8.  RE: webMethods Messaging subsystem was not initialized

    Posted Tue October 03, 2017 05:45 PM

    I am facing the same issue in webMethods Mediator version 9.12. I tried to uninstall and then reinstall the server, but the same thing is happening again. Have you guys managed to fix this issue? Please, can you share any suggestions? Thanks in advance!


    #B2B-Integration
    #Integration-Server-and-ESB
    #webMethods


  • 9.  RE: webMethods Messaging subsystem was not initialized

    Posted Thu October 05, 2017 12:14 PM

    I found the solution. The sw license keys provided to me did not have permissions to configure the Messaging configuration, so this explains the issue. It would have been nice if the option to configure the Messaging would have been greyed out or removed based on what the sw license allows, so we would not be lead (or misled) to believe the feature was corrupted. Next time, check the license key more thoroughly before! :slight_smile:


    #Integration-Server-and-ESB
    #B2B-Integration
    #webMethods