webMethods

 View Only
  • 1.  Universal Messaging port change post installation

    Posted Wed September 18, 2024 02:18 AM

    Hi Guys,
    I want to change my universal messaging default port 9000 to something else, as the port 9000 is being occupied by some other application.
    Please let me know the process of doing that, FYI I am using WM 10.15 on Windows system.

    Thanks.


    #webMethods
    #Universal-Messaging-Broker


  • 2.  RE: Universal Messaging port change post installation

    Posted Wed September 18, 2024 02:36 AM

    Hi,
    Have you tried creating new Interface from Enterprise manager? Just try creating new nhp interface under “interfaces” tab and remove old one.

    Thanks,
    Yogesh


    #webMethods
    #Universal-Messaging-Broker


  • 3.  RE: Universal Messaging port change post installation

    Posted Wed September 18, 2024 05:25 AM

    Thanks you so much I created the new instance and its working.

    For others who are looking to create a new instance use below file:
    SoftwareAG\UniversalMessaging\tools\InstanceManager\ninstancemanager.bat


    #webMethods
    #Universal-Messaging-Broker


  • 4.  RE: Universal Messaging port change post installation

    Posted Wed September 18, 2024 10:45 AM

    FYI, creating a new instance isn’t the right answer for this question. You can create a new interface from Enterprise Manager, even without deleting the current port. They will work the same depending on the configuration.


    #webMethods
    #Universal-Messaging-Broker


  • 5.  RE: Universal Messaging port change post installation

    Posted Fri September 20, 2024 02:54 AM

    If for creating new interface, I have to open the EM of the default UM(i.e. umserver), then its not opening because port 9000 is occupied by some other application. So I am not able to open the EM of the default UM instance.

    Is there any other way of creating a new interface then please let me know.

    Because although I have created new UM instance my flow services are not working they are throwing below error:

    Could not run ‘testPublish’
    com.wm.app.b2b.server.ServiceException: [ISS.0153.9009] Unable to send message to webMethods Messaging alias UMServer2_Alias: com.wm.app.b2b.server.dispatcher.exceptions.MessagingSubsystemException: com.pcbsys.nirvana.client.nChannelNotFoundException: Channel could not be found on the server:Find : /wm/offline/Practice/docs/sampleDocumentFromXml


    #webMethods
    #Universal-Messaging-Broker


  • 6.  RE: Universal Messaging port change post installation

    Posted Fri September 20, 2024 11:10 AM

    If you are creating new instance, you need to sync all the documents you publish from IS and recreate/copy all the JMS queues/topics if you have any.

    Correct way to fix your issue is to stop the other app that is using port 9000, and then create the new port using Enterprise Manager, and then delete port 9000. If you can’t kill the process that is using port 9000, then you can update the port from the file system I presume, but I don’t know the location and the name of the file, so better check the documentation if you need that. You can also use UMTool or CommandCentral to update this setting.


    #webMethods
    #Universal-Messaging-Broker