TeamcenterKnowledge

System Administration > File Management System > Administering FMS > Auditing FSCs

FSC audit log transaction IDs

Transaction IDs are the key to associating all the audit information together across the FMS network. Early in the request processing, the FSC looks for a transaction ID in the request headers. If it finds one, it appends the local FSC ID and uses that as its base transaction ID. If a previous one is not found, it increments an internal count and appends its FSC ID. The internal count starts based on a secure random number. There is no guarantee duplicate IDs are not generated, but given the range of a 64-bit value collisions, duplicates are very rare and even more unlikely in close proximity in time. When you search for transactions, if a collision occurs, the timestamps can be used to identify the different transactions. Any suboperation appends [n+1] to the end of each transaction ID. A transaction ID supplies exact information on how a request is routed though the network. The following is an example of how a transaction ID propagates through a number of servers and shows the resulting transaction ID information. Given the following FSCs: FSC_emdbangfms_tcdba FSC_spandfms_tcdba FSC_flodup_tcdba FSC_yagmlsp_tcdba FSC_wndisxk_tcdba The first FSC (FSC_emdbangfms_tcdba) generates a new ID. Copy (342342349932)FSC_emdbangfms_tcdba It then performs a subordinate operation (subop), appends [1] to the transaction ID, and sends the request. Copy (342342349932)FSC_emdbangfms_tcdba[1] The next FSC (FSC_spandfms_tcdba) receives and joins the existing transaction ID. Copy (342342349932)FSC_emdbangfms_tcdba[1]>FSC_spandfms_tcdba It then performs a subop. Copy (342342349932)FSC_emdbangfms_tcdba[1]>FSC_spandfms_tcdba[1] A third FSC (FSC_flodup_tcdba) receives and joins the existing transaction ID. Copy (342342349932)FSC_emdbangfms_tcdba[1]>FSC_spandfms_tcdba[1]>FSC_flodup_tcdba It then performs a subop. Copy (342342349932)FSC_emdbangfms_tcdba[1]>FSC_spandfms_tcdba[1]>FSC_flodup_tcdba[1] And another subop. Copy (342342349932)FSC_emdbangfms_tcdba[1]>FSC_spandfms_tcdba[1]>FSC_flodup_tcdba[2] The forth FSC (FSC_yagmlsp_tcdba) received the prior subop ([1]). Copy (342342349932)FSC_emdbangfms_tcdba[1]>FSC_spandfms_tcdba[1]>FSC_flodup_tcdba[1]> FSC_yagmlsp_tcdba A fifth FSC (FSC_wndisxk_tcdba) received the prior subop ([2]). Copy (342342349932)FSC_emdbangfms_tcdba[1]>FSC_spandfms_tcdba[1]>FSC_flodup_tcdba[2]> FSC_wndisxk_tcdba This shows that the transaction ID on any server provides an indication of the path through the network. Even if intermediate FSCs do not have auditing enabled, transaction IDs are still generated or propagated along with the requests.

Source: https://docs.sw.siemens.com/documentation/external/PL20251212545240207/en-US/tc_help/AWAdmin/fhs4814155880506/uuc1737238583853/fhe1737238587390/ooj1737238590573/xid454897.html · retrieved Fri Jul 31 2026 00:00:00 GMT+0000 (Coordinated Universal Time)