search cancel

Deploy Message Service Servers to remote machines

book

Article ID: 230614

calendar_today

Updated On:

Products

Mainframe Operational Intelligence COMMON SERVICES FOR Z/OS

Issue/Introduction

When maintenance is applied to the Message Service Server (MSS) and/or the Data Mover then it's needed to deploy this to the lpars it's installed on and the lpars that also are connection to the application that is using them, like MOI (Mainframe Operational Intelligence)..
How to accomplish this...

Environment

z/OS
Mainframe Operational Intelligence 
CA Common Services

Resolution

After the SMPE installation of the maintenance it's needed to copy 5 ZFS file systems from the SMPE environment to the runtime environment:

MOUNT FILESYSTEM('ZFS.CA90.DEPLOY.CCSZFSJ') +             
      MOUNTPOINT('/cai/prod/cff6') +                        
      TYPE(ZFS) MODE(RDWR)                                          
MOUNT FILESYSTEM('ZFS.CA90.DEPLOY.CCSZFS') +              
      MOUNTPOINT('/cai/prod/cff5') +                        
      TYPE(ZFS) MODE(RDWR)                                           
MOUNT FILESYSTEM('ZFS.CA90.INSTANCE.CCSZFS') +            
      MOUNTPOINT('/cai/prod/cff5/instance') +               
      TYPE(ZFS) MODE(RDWR)                                  
 
Only needed for MOI:
        
MOUNT FILESYSTEM('ZFS.CA90.DEPLOY.CCSZFSB') +             
      MOUNTPOINT('/cai/prod/cfgb/messageService') +         
      TYPE(ZFS) MODE(RDWR)                                          
MOUNT FILESYSTEM('ZFS.CA90.INSTANCE.CCSZFSB') +            
      MOUNTPOINT('/cai/prod/cfgb/instance/messageService') +
      TYPE(ZFS) MODE(RDWR)                
 
The DEPLOY can be shared in R/O only mode between different LPARs - the INSTANCE must be unique for every LPAR.
To prevent a data flow stoppage issue, it's needed to delete the server-id.txt file from the MSS instances in USS to prevent duplicate server ID's.
A new service id is created when those MSS instances are restarted.   

The server-id.txt file can be found in the following MSS USS directory:  <mount_point>/cfgb/instance/messageService/broker/

It's also recommended to delete the contents of the directory <Install_Dir>/cfgb/instance/messageService/brokerData.

This directory has a sub-directory with ActiveMQ database and it changes with the new server-id. So the old directory would stay without being deleted.
It does not do any harm but it takes up some space.

 

Additional Information

The preferred way, to avoid the situation with the server-id file is that each MSS should be deployed on the LPAR that it is going to run on per the following MSS doc: