Node installation failure with MQ registry connection type

Jean-Philippe Plourde
Jean-Philippe Plourde
in AppWorks #1

We are trying to install a new node on MQ server, with the Enterprise node located on another server/QM.

 

Channels are defined between the 2 QMs and we can exchange messages. When installing the node, the step that tries to contact the Registry services would fail because the Registry service would not respond within the time limit.

 

When looking at the problem, we discovered that the message sent by the process ends up in the DLQ of the Enterprise node QM because it tries to deliver to the MIM.NewNodeName.DIRECTORY.SERVICE, which of course doesn't exist.

 

Does anybody have an idea what is happening?

Tagged:

Comments

  • Ethan Beisher
    Ethan Beisher E Community Moderator
    #2

    What version of MIM and MQ?

     

    Can you post your config.rsp for your new node? Can you display the log of the failed Registry Service attempt?

  • Jean-Philippe Plourde
    Jean-Philippe Plourde
    #3

    MIM 8.5.1  & MQ 7.0.1

     

    config.rsp;

    #########################
    # DO NOT EDIT THIS FILE #
    #########################
    :Install
      install_type               = runtime,nodeagents,serveragents,workbench
      install_path               = D:\PM4DATA
      data_path                  = D:\PM4DATA
      this_install_version       = 8.5.1.0
      registry_type              = mqserver
      transport_type             = mqserver

    :Variables
      local_qmgr                 = ENT_SVR
      unique_node_name           = ENT_SVR
      q_prefix                   = MIM.
      jmx_port                   = 10012
      pm_webserver_port          = 10010
      pm_webserver_shutdown_port = 10011
      user_registry              = Application1
      registry_qmgr              = $(local_qmgr)
      manager_qmgr               = $(local_qmgr)
      mqserver_hostname          = MIMSERVER.test.com
      mqserver_channelname       = SYSTEM.DEF.SVRCONN
      mqserver_port              = 1414
      local_hostname             = $(mqserver_hostname)

    DatabaseDriver
      schema                     = PM4DATA
      user                       = admin
      password                   = ***_Removed_Password_***
      Driver.dataSourceName      = PM4DATA
      Driver.type                = db2luwdd
      Driver.serverName          = MIMSERVER
      Driver.portNumber          = 50000
      Driver.databaseName        = PM4DATA
     
     
      nodeagent.log
      INFO  17 Jan 2012 14:20:34,962 [main] - Node Agent Version: 8.5.2.0.20110506
      INFO  17 Jan 2012 14:20:34,962 [main] - Build Date: 05/06/2011 11:04:26
      FATAL 17 Jan 2012 14:21:07,838 [main] - Error reading Launcher.xml, exiting...
      com.commercequest.xmdirectory.XMDirectoryIOException: MQ Error communicating with remote directory service: MQJE001: Completion Code '2', Reason '2033'.
          at com.commercequest.xmdirectory.client.XMDirectoryMQ.processRequest(XMDirectoryMQ.java:154)
          at com.commercequest.xmdirectory.client.XMDirectoryBase.executeRequestList(XMDirectoryBase.java:561)
          at com.commercequest.xmdirectory.client.XMDirectoryBase.executeRequest(XMDirectoryBase.java:542)
          at com.commercequest.xmdirectory.client.XMDirectoryBase.getObject(XMDirectoryBase.java:230)
        at com.metastorm.nodeagent.NodeAgent.main(NodeAgent.java:374)

  • Ethan Beisher
    Ethan Beisher E Community Moderator
    #4

    Is this the config for the new node or the Enterprise Server? I noticed the local qmgr is ENT_SVR and the Registry uses the same qmgr.

  • Jean-Philippe Plourde
    Jean-Philippe Plourde
    #5

    That's the Entreprise node config. Couldn't find a config.rsp on the client node - maybe that's part of the problem.

  • Ethan Beisher
    Ethan Beisher E Community Moderator
    #6

    What platform is it?

  • Jean-Philippe Plourde
    Jean-Philippe Plourde
    #7

    win 2003 for server and xp sp3 for client node.

  • Ethan Beisher
    Ethan Beisher E Community Moderator
    #8

    The file is located at [install_dir]\bin\config.rsp.

     

    If you don't see it, please post a listing of your bin directory.

     

    By the way is your XP 32 bit or 64 bit?

  • Jean-Philippe Plourde
    Jean-Philippe Plourde
    #9

    32 bits for client and server

     

    We re-ran the install and got a config.rsp file this time;

    :Install

      install_type               = runtime,nodeagents
      install_path               = C:\Program Files\Metastorm\MIM
      data_path                  = C:\Program Files\Metastorm\MIM
      this_install_version       = 8.5.1.0
      registry_type              = mqserver
      transport_type             = mqserver

    :Variables
      local_qmgr                 = NODE_TEST
      unique_node_name           = NODE_TEST
      q_prefix                   = MIM.NODET.
      jmx_port                   = 10012
      registry_qmgr              = ENV_TEST
      manager_qmgr               = $(local_qmgr)
      mqserver_port              = 1400
      local_hostname             = client.test.com

  • Ethan Beisher
    Ethan Beisher E Community Moderator
    #10

    This appears to be your problem:

     

    q_prefix                   = MIM.NODET.

     

    You need to use the same Queue Prefix as your server node.

     

    You can either re-run the installation or simply edit the config.rsp and run the configure command shell program.

     

    Ethan

     

     

  • Jean-Philippe Plourde
    Jean-Philippe Plourde
    #11

    You were right. Worked fine after changing the prefix to MIM.

     

    Looks like we didn't read the installation guide properly...

  • Doug Johnson
    Doug Johnson
    #12

    Thanks for reporting your results back to the community [J-P Plourde].  Much appreciated.

     

    Sounds like you're having beter success now.

Categories

image
OpenText CE Products
AppWorks
Gateway & Platform