ALERT: Some images may not load properly within the Knowledge Base Article. If you see a broken image, please right-click and select 'Open image in a new tab'. We apologize for this inconvenience.

How to set up CAM to bind to a different IP address.

book

Article ID: 53336

calendar_today

Updated On:

Products

Advantage Data Transport CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Unicenter NSM

Issue/Introduction

Description:

By default, CA Message Queuing (CAM) will bind to the IP address that is the highest in the order.
Sometimes it is necessary to force CAM to bind to a different IP but changing the binding order is not acceptable.

Solution:

To force CAM to bind to a different IP address

  1. Determine what IP address CAM is currently binding to by issuing the command:

    camping -a <hostname>
    The hostname can be the local server hostname. The camping output shows the IP address that CAM is using.

  2. If you need to have CAM use another IP address, run the command:

    camsave persist
    This will create a cam.cfg file located for Windows under %CAI_MSQ%

    Find the location for UNIX by issuing the command:
    more /etc/catngcampath

  3. Open the file cam.cfg and add the following under the *ROUTING section:
    *ROUTING
    forward 127.0.0.1= <local IP address to use>

Example:
forward 127.0.0.1=192.168.1.56

  1. Save and close the file.

  2. Recycle the CA Message Queuing Server service.

  3. Run the camping - a test again:

    camping -a <hostname>
    If the correct IP address is displayed, you are finished.

  4. If the correct IP address is not showing, open the file cam.cfg again and edit the *ROUTING line as follows:

    forward 127.0.0.1=<local IP address to use><local IP again>

Example:
forward 127.0.0.1=192.168.1.56 192.168.1.56

  1. Save and close the file cam.cfg.

  2. Recycle the CA Message Queuing Server service.

  3. Rerun the camping -a test and verify that the correct address is now in use:

    camping -a <hostname>

Environment

Release: TNGEXO05500-11.2-Management-for Microsoft Exchange
Component: