search cancel

OPS/MVS MTC-A Attempting to connect multiple LPARS to MTCA

book

Article ID: 134320

calendar_today

Updated On:

Products

OPS/MVS Event Management & Automation

Issue/Introduction

After getting MTCA up and running successfully, I attempted to install Message Service Server (and its prerequisite Data Mover) on another mainframe to connect it to MTCA also. However, after getting ZMSSTART installed on mainframe B, and recycling MTCA Tomcat, I am not seeing mainframe B in system list and job output showed MTCA only discovering original system, mainframe A. I also tried recycling ZMSHUB, but each time MTCA will only discover either mainframe A or B but not both. Is there an incorrect setting that I'm missing?

Cause

Customer deployment strategy involved cloning the MessageService Server to subsequent LPARs.

Environment

Release : 13.0

Component : MAINFRAME TEAM CENTER AUTOMATION

Resolution

Customer cloned the Message Service Server from one LPAR to another. The hubnode.log showed where the messageServiceHubNode was "already connected." Customer had to delete brokerData and database directories in the cloned instance/MessageService directory.    The following message was displayed in the hubnode.log:


javax.jms.InvalidClientIDException: Broker: messageServiceHubNode - Client: EMBEDDED_BROKER_3b8eed91-1b2d-459b-96ad-8c6f25d75aba_localhost_outbound already connected from tcp://###.###.###:#####      (where ###.###.###:##### is the IPAddress)

Additional Information

This could occur in any release of the Mainframe Team Center Automation product.