This has caught me out several times in recent weeks.
TeamWorksConfiguration.running.xml is a fabulously useful file, as it provides one with the current state of a running IBM BPM environment, including all the configuration changes from 00Static.xml, 80Database.xml, 99Local.xml, 100Custom.xml etc.
For me, the file is found at the App Server profile level, in config/cells/nodes/servers: -
/opt/IBM/WebSphere/AppServer/profiles/AppSrv01/config/cells/ProcessCenter/nodes/AppSrv01.NodeProcessCenter.AppTarget.AppSrv01.Node.0/process-center/TeamWorksConfiguration.running.xml
/opt/IBM/WebSphere/AppServer/profiles/Custom01/config/cells/localhostCell01/nodes/localhostNode01/servers/ProcessCenter.AppTarget.localhostNode01.0/process-center/TeamWorksConfiguration.running.xml
However, the key thing that I learned to my cost is ….
If one performs a Full Resynchronize of the WAS cell, the file gets removed.
This is because it's part of the node-level configuration, and a full resync. deletes all the Node configuration files and then replaces them from the Deployment Manager, from whence the cell is managed.
TeamWorksConfiguration.running.xml is absolutely, definitely a run-time file, which only ever exists at the Node level ( it's created by the AppTarget cluster which hosts the BPMN run-time and, if available, the PDW application/cluster )
Bottom line, if you ever sync. your nodes during normal operation, expect TeamWorksConfiguration.running.xml to disappear until the next time you restart your cluster(s)