Manually create the CAM configuration file cam.cfg.
search cancel

Manually create the CAM configuration file cam.cfg.

book

Article ID: 39483

calendar_today

Updated On:

Products

CA Client Automation - IT Client Manager CA Client Automation

Issue/Introduction

Does the cam.cfg automatically gets created or do I have to manually create it?

Environment

CA Client Automation - All Versions

Cause

CAM (CA Message Queuing) provides (logically) connection-less application-to-application messaging in that no direct link exists between the applications. Instead, applications communicate with a CAM server, which adds filtering, queuing, routing and quality of service attributes to the message exchange. The CAM server will deliver the message to the recipient application, either directly, if the recipient is on the same machine, or by delegating the task to a remote CAM server. However, the minimum service level provided gives a degree of reliability such that where both applications are running then messages will be passed between them.

cam.cfg

Main CAM configuration file. Configures most aspects of CAM's operation, including basic configuration settings, routing rules, logging and tracing control, port and transport layer control, and so forth.

Resolution

Cam.cfg file can be generated manually by the Administrator.

NOTE: The file can also be copied from another machine if one exists as these are not machine specific.

In order to create it from a cmd prompt, the following steps/commands can be used:

  1. caf Stop & caf kill all
  2. camclose & cam start -c -l            
  3. Run 'camsave config'.  This will create a save.cfg file in the directory "%CAI_MSQ%."
  4. Rename this file to cam.cfg.
  5. camclose & cam start -c -l
  6. caf start

Note: When you create a cam.cfg it puts all active connections in the file, so clearing the cam queue first will save you from having to delete all connections using the default UDP connection, which should not be stored in a cam.cfg file.

Additional Information

If the file was copied from another machine, make sure to remove any custom items under  PATHS or ROUTING sections that might be present in the source file copied, if they are not relevant for the target machine. By default these sections are empty.

Powered by Wolken Software