Failed to deliver change set

[glyncostello]

Since updating to iFix 13 on 6.0.6.1 I've been unable to use the TSM.

java -jar tsm.jar -command importTypeSystemByDescription -url https://[rooturl]/rm -user XXXX -password XXXX sourceTag TSSource_DTS1_1 -targetTag TSTarget_DTS1_1

The change set is created in the stream, but it fails to deliver with:

The tracker https://[rooturl]/rm/taskTracker/7cc0ec21-721e-4281-859f-c257bc2c4a10 reports an error 'Tracker: 'https://[rooturl]/rm/taskTracker/7cc0ec21-721e-4281-859f-c257bc2c4a10'state: http://open-services.net/ns/auto#complete verdict: http://open-services.net/ns/auto#complete[{"type":"bnode","value":"_:-231772ab_17c7961acb1_1cd"}]{ Copy type system task }' Tracker verdict : 'http://open-services.net/ns/auto#error' Failed to Import into change set 'https://[rooturl]/rm/cm/changeset/_DySfgCwQEeyOG8HPIsGjBg'.

If I go into the stream editor, I can manually deliver the change set without a problem.

I'm embarking on a project with many components/streams and this tool is ideal for maintaining a consistent type system across components and project areas.

[rsjazz]

The error message seems to indicate that there is an error happening during import of the changes into the change set. So that you can deliver the change set is of no relevance. The question is, if you can do the import.

I don't fully understand the message at the moment. You can use the tracker URI in a REST client like POSTMAN. And query the tracker URI yourself btw.

[glyncostello]

The change set includes all the necessary type system changes, so it seems like the change set import has worked.

Using Talend, do I need to include any headers in the request? At the moment, just returns "No content"

[rsjazz]

The DNG tracker API is explained here: https://jazz.net/wiki/bin/view/Main/DNGServerAPI specifically here: https://jazz.net/wiki/bin/view/Main/DNGTaskTracker

The tracker is only available for a while. It expires. You will likely have to authenticate against the system first. RESTCLIENT in Firefox allows to do that and then to reuse the session in your own calls.

I have no clue what happened here. If only one error happened and you where able to solve this, I would say this is sufficient. I am not able to reproduce this anyway and even setting up a test system to try would take a lot of time.