CA Client Automation

Hello guys,

I'm having trouble making software deployment, was looking at some machines and found that the DTS is not enable ... Then I used the following command to enable, as shown, but dtsagent service does not start.

Also, how can I create a query to find the machines that is not enabled with the plugin?

C:\Windows\system32>caf status dtsagent

CA DSM r12 Common Application Framework 12.8.1.100

Copyright (c) 2013 CA Technologies. All rights reserved.

Querying caf for status information...

-------------------

[1]  Data Transport transfer agent (dtsagent)

        Properties: enabled,auto,maxInstances:1,restartable

        Version   : -

        State     : stopped

        Started   : -

        Depends on: ccnfagent

        Running as: -

        Info      : -

-------------------

******************************************************************

C:\Windows\system32>caf start dtsagent

CA DSM r12 Common Application Framework 12.8.1.100

Copyright (c) 2013 CA Technologies. All rights reserved.

Starting dtsagent...

Worker process executable not found or failed to start.

The command failed.

******************************************************************

Hello Alex,

It looks like file tngdta.exe is not found on the machine.

With command "caf getprop dtsagent" it is possible to know the command line for plugin dtsagent :

C:\Users\Administrator>caf getprop dtsagent

CA DSM r12 Common Application Framework 12.9.0.338

Copyright (c) 2014 CA Technologies. All rights reserved.

Properties for DSM service dtsagent:

commandline: C:\Program Files\CA\SC\DTS\bin\tngdta.exe

communicable: 1

dependencies: ccnfagent

description: Data Transport transfer agent

enabled: 1

...

Check with this command the path for file tngdta.exe and check if this file exists on the machine (ex: C:\Program Files\CA\SC\DTS\bin\tngdta.exe)

Thanks.

Regards,

Jean-Yves

DTS Plugin is not installed by default with the agent packages (either full or just the SD) - only on Scalabilities (this includes DM/EM). You need to explicitely install the CAF + DTS Plugin package to the agent in order to have it available on the agent.

Are you sure you want to use DTS for the endpoints.  This is generally a bad idea to use dts for software delivery to the end points.  DTS at the endpoints is normally used if you need to bring files back from the end points.

Richard Lechner

Principal Engineering Services Architect

CA Technologies

Mobile: +1 703 655 7161 | Richard.Lechner@ca.com

<mailto:Richard.Lechner@ca.com>[CA]<http://www.ca.com/us/default.aspx>[Twitter]<http://twitter.com/CAInc>[Slideshare]<http://www.slideshare.net/cainc>[Facebook]<https://www.facebook.com/CATechnologies>[YouTube]<http://www.youtube.com/user/catechnologies>[LinkedIn]<http://www.linkedin.com/company/1372?goback=.cps_1244823420724_1>[Google]<https://plus.google.com/CATechnologies>[Google+]<http://www.ca.com/us/rss.aspx?intcmp=footernav>

I agree with Richard Lechner

are you sure you want to use DTS or has this only come up in your troubleshooting your SD issue?

Can you tell us what the initial challenge \ issue was?

regards

Rich

Hi all,

Actually you're right is not necessary to use DTS. I'm having trouble making deploy, many machines are in state: DTS status: File transfer has completed successfully.
State: Execution Order Staged

I thought it might be the dts.

Thanks.

That status in a job usually indicates the package has been successfully transferred (by DTS) from the Domain Manager to the Scalability Server. You get that status when the package was not pre-staged at the Scalability Server which means it must be transferred at deployment time.

Steve McCormick, ITIL

CA Technologies

Principal Services Consultant

Tel: +1-731-676-4223

Stephen.McCormick@ca.com

<mailto:Stephen.McCormick@ca.com>

I would not concentrate on DTS, There seems to be an issue on your scalability server that is not triggering the jobs

I would raise this as a support case

regards

Rich

I agree with Richard and Richard's comments - you should not be looking at DTS at the endpoints unless there is a specific need for it. It is mostly used to transfer files FROM the endpoints. In your case it looks like something is wrong on the Scalability Server(s) and they are not triggering package deliveries. One possibility is an endpoint-based firewall is preventing the Scalability Server from triggering the delivery. Host-based firewalls allow the Agent to reach the Scalability Server so they don't affect delivery of inventory but they do prevent software deliveries unless the Agent establishes contact first, and they do prevent Remote Control sessions, unless they are configured to allow our ports (4728 TCP and 4104 UDP by default) access.