The CAFT process does not start up automatically when a request for cube transfer is sent from an agent system.

book

Article ID: 52729

calendar_today

Updated On:

Products

Advantage Data Transport CA Unicenter NSM

Issue/Introduction

Description

The CAFT process does not startup automatically when a transfer request is sent from an agent system for cube transfer.

Solution

CAFT is an application or utility which runs under a user's domain, unlike CAM, which is a service that runs under a SYSTEM account. CAFT is intended to run on demand and it is normally started by default when a request is sent to it. Therefore, CAFT should start automatically when it receives a new request.

It will close down after a period of idleness (one hour by default) and it can be started manually as required with the command: caftf.

If you want the CAFT application to always be up and running, then the computer should be logged on with a user and CAFT should be started manually from that user's domain. The CAFT process stops after this user logs off from the computer.

In some cases, CAFT does not start automatically when it receives a new request. If this happens, the system will not receive any cube files. To fix this issue, make sure that the following statement is present in the file camclient.cfg: CAIFTRANS "x:\%CAI_MSQ%\bin\caft.exe" CAIFTRANS and that the statement includes the appropiate CAFT executable path.

To achieve this:

  1. Remove the existing CAFT entry by its key value:

    camclient -d -k CAIFTRANS

  2. Append the entry back as:

    camclient -k CAIFTRANS -a "C:\Program Files\CA\SharedComponents\CAM\bin\caft.exe" -o CAIFTRANS

  3. Recycle CAM with the commands:

    camclose
    cam start

    After this change CAFT start automatically upon receipt of some requests from its clients.

Environment

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