Teamcenter–Mendix Integration: Retrieving Physical Dataset Files via Custom ITK API

0
Hi everyone,I have a use case related to Teamcenter integration using the TC Connector in a Mendix application, and I’m looking for some guidance.The client has Design Revision Items, under which Datasets are available with a nested structure. The actual physical files are stored in the Teamcenter database/volume.The challenge we are facing is that the client’s OOTB Teamcenter query is not working with the TC Connector because of their specific Teamcenter structure. We also tried using a custom/user query, but Mendix/TC Connector does not support accepting the required custom query in this scenario.As an alternative, we are planning to use a custom ITK API.With the custom ITK API, we are currently able to retrieve the Part Revision and Dataset information successfully. However, we are not clear on the correct approach for retrieving the physical files associated with the Dataset.Specifically, we would like to understand:How can we access the physical files associated with a Dataset through the ITK API?Since the files are stored in the Teamcenter volume/database, what is the recommended way to retrieve/download them at runtime?Is there a specific ITK API/functionality that can be used to get the file reference and stream/download the physical file?How does the TC Connector handle this internally when the OOTB query is used, since it is able to identify the Dataset structure and bring the associated files?Is there any recommended architecture where the custom ITK API retrieves the file and exposes it to the Mendix application without directly accessing the Teamcenter database/volume?Has anyone faced a similar scenario with Mendix + Teamcenter TC Connector + custom ITK API, particularly when dealing with nested Datasets and physical files?Any guidance or reference implementation would be greatly appreciated.Thank you!
asked
2 answers
0

Hi,


ITK is a server-side API.

Mendix has access to the SOA web services (the rest version used by AWC).

So mendix can't access ITK API directly, unless you expose it as a web service extension in BMIDE.


Back to the original requirement, Mendix connector can run any Teamcenter query, standard or custom.

Mendix can also get the physical file by navigating to the named reference, and download the physical file from FMS.

Sample project has sample for this.


answered
0

I may be missing something, but I’m not sure why a custom ITK service is needed here.


If the Design Revision is already known, could you not use the TC Connector/SOA services to navigate the Teamcenter relationships from the Design Revision to the Dataset, then to the Named Reference , ImanFile, and let FMS handle the actual file download?


In that case the main question seems to be whether the Dataset can be reached through the available Teamcenter relations/services, rather than whether the physical file needs to be retrieved through ITK.


Also, regarding the query issue, is the “User Query” fundamentally different from a normal Teamcenter Saved Query/custom query exposed through SOA?


If so, it would be useful to understand that distinction, because otherwise I would expect the TC Connector to remain the preferred route.

answered