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
3 answers
0

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.

answered
0

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.


answered
0

Hi,


Short answer: No — you cannot realistically bypass Teamcenter Java actions (TC Connector) and directly retrieve all model/business objects via SOA from Mendix alone. What you’re seeing (only workspace objects accessible) is expected.

Let me explain clearly based on how this integration actually works in projects.

Why you are limited to workspace objects

When you use Mendix + Teamcenter:

  • The Teamcenter Connector (Java actions) wraps SOA calls
  • It handles:
    • Session management
    • Authentication (ticket / SSO)
    • Object mapping (UID → Mendix objects)
    • Complex response parsing

Without this layer, Mendix cannot directly consume full SOA responses properly.

That’s why:

You only see workspace-level objects → because connector exposes them

Can you call SOA directly from Mendix?

Technically:

  • You can call SOA endpoints using:
Call Web Service (SOAP)
or
Call REST (if exposed)

But practically:

  • Teamcenter SOA is not simple SOAP/REST
  • It uses:
    • Complex types
    • Session tokens
    • Stateful communication
    • Internal service contracts

Mendix microflows cannot handle this cleanly

What happens if you try without Java actions

You will face:

  • Authentication/session issues
  • Complex XML parsing problems
  • Missing object mapping (UID → business object)
  • No lifecycle/service handling

So even if call succeeds:

You won’t get usable structured data in Mendix

Correct approaches

Option 1 — Use Teamcenter Java actions (recommended)

  • This is the standard and supported way
  • Extend existing Java actions if needed
  • Add custom SOA calls inside Java layer

Option 2 — Build custom middleware

If you don’t want Java inside Mendix:

  • Create external service (Java/.NET)
  • That service:
    • Talks to Teamcenter SOA
    • Converts response → simple REST

Then Mendix calls:

REST API → clean JSON

Option 3 — Use Teamcenter REST APIs

Newer Teamcenter versions expose limited REST APIs.

  • You can call via:
Call REST

But:

  • Coverage is limited
  • Not all business/model objects are exposed

Important clarification

“Can we bypass TC Java actions using SOA directly?”

Practically: No (not in a maintainable way)

Architecturally correct answer:

SOA must be handled in Java layer or middleware

  • Direct SOA calls from Mendix without Java → not practical
  • Workspace objects limitation → expected behavior
  • Correct solution → extend Java actions OR use middleware
  • REST alternative → only if Teamcenter exposes required APIs


answered