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.
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.
Does the cam.cfg automatically get created or do I have to manually create it?
CA Client Automation - All Versions
Cam.cfg file must be generated manually by a user. (the file can also be copied from another machine if one exists as these are not machine specific)**
From a cmd prompt do the following:
- CAF Stop
- camclose & cam start -c -l
- Run 'camsave config'. This will create a save.cfg file in the directory "%CAI_MSQ%."
- Then just rename the file to cam.cfg .
- CAMCLOSE & CAM start -c -l
- CAF start
Note: When you create a cam.cfg it puts all active connection in the cam.cfg 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.
**Make sure to remove any custom PATHS or ROUTING section items that might be present in the CAM.CFG you copy if they are not relevant for the target machine. By default these sections are empty.