Question

in mendix we can get till workspace objects only can we get the objects or any other using SOA calls without tc java actions ?

0

QuestionIn Mendix, can we retrieve model objects and business objects through SOA calls without using Teamcenter Java actions? Currently, we can only access workspace objects. Are there alternative methods, such as REST services or other approaches, that would let us call Teamcenter services directly?ContextThe user is working with Mendix and Teamcenter integration and wants to understand the limitations and available options for retrieving different object types beyond workspace objects.Desired OutcomeClarification on whether SOA calls can bypass Java actions to fetch model and business objects, and identification of any available alternative methods for accessing these object types through Mendix.

asked 2026-03-20

Ashok mukka

2 answers

Krishna Kumar S · Answer 1 · 2026-03-20

No, you cannot directly call Teamcenter SOA from Mendix in a standard way. REST alone won’t solve it either unless you build an additional layer.

Teamcenter SOA is not REST, it is session-based, uses complex JSON structures, and relies on object property policies.

This is based on my understanding. If anyone has additional insights or alternative approaches, please share, would be great to learn more.

Ahmet Kudu · Answer 2 · 2026-03-20

No, you can’t use Teamcenter SOA without Java actions in Mendix.

SOA access in Mendix is handled through the Teamcenter Connector Java actions. If the object or service you need is not exposed by the Extension, the usual next step is to use CallTeamcenterService and map it yourself.

The reason you only see workspace objects is most likely because the Teamcenter Extension has a limited scope. It does not expose every Teamcenter object type.

I would suggest this approach:

First check whether the object you need is already supported by the standard Teamcenter Connector actions. If not, try CallTeamcenterService instead of relying only on the Extension. That usually gives you more flexibility for unsupported object types.

If your Teamcenter environment also exposes REST APIs, that can be another option, but that would be a custom integration path rather than the standard Mendix Teamcenter setup.

So in practice:

no Java actions = no standard SOA access

and for unsupported objects, it is usually better to move from the Extension to the Connector + CallTeamcenterServiceapproach.

If this resolves your issue, please mark it as accepted.