Skip to main content
S
Sha1114-Alexandrite
14-Alexandrite
February 7, 2025
Solved

Why middleware in Integrations?

  • February 7, 2025
  • 3 replies
  • 907 views

Hi folks,

 

I just have a simple question in hand, why should we have a middleware in place when Windchill is being integrated with a downstream system. I know that it has the below advantages, are there any other points that speaks to the merit of using a middleware.

 

i) System configurations does not need any update between different Windchill servers as the source and target system mapping can be done with a middleware.

ii) The formatting and translation of the transferred content can be done and maintained in middleware.

 

Any inputs is appreciated.

 

TIA.

 

Best answer by tarik_p

Hello @Sha11 , the middleware is not needed, Windchill PLM integrates with many applications without any middleware such as the integration with the Workgroup Manager (SOAP Services), the integration with ThingWorx Navigate via RESTful Services etc.

 

The middelware is required in the integration with ERP Systems, but also not required as you can stick with ERP Connector only (uni-directional communication) or you can use REST Framework if your ERP is REST-Based.

 

+ The middleware is required in the integration of Windchill PLM with Codebeamer/PTC RV&S or PTC Modeler, PTC calls this integration "Digital Product Traceability (DPT). And the middelware here is not the ESI one is Thingworx Foundation + Flow.

 

All those integrations are ESI, just because the ERP integration was old it takes the same name whereas the integration with PTC products is called DPT.

 

Because two different middlewares are used, PTC thinks to make one unified middleware for all kinds of these integrations.

 

tarikwifakp_0-1739451415104.png

 

 

 

I encourage you to read this LinkedIn article

and see the graphic of Digital Thread: Microsoft OneDrive

3 replies

R
rhart16-Pearl
16-Pearl
February 11, 2025

We're using a JMS between Windchill and the ERP system.

When ERP is offline, having the JMS there means Windchill can continue the send ESI transaction messages normally, regardless of any issues at the receiving end. When ERP comes back online it can pickup the backlog of queued messages from the JMS and both ends continue like nothing happened.

    V
    vnamboodheriCommunity Manager
    Community Moderator
    February 12, 2025

    Hello @Sha11,

     

    It looks like you have a response from a community member. If it helped to answer question please mark the reply as the Accepted Solution. 

    Of course, if you have more to share on your issue, please let the Community know so other community members can continue to help you.

    Thanks,
    Vivek N.
    Community Moderation Team.

    T
    tarik_p14-AlexandriteAnswer
    14-Alexandrite
    February 13, 2025

    Hello @Sha11 , the middleware is not needed, Windchill PLM integrates with many applications without any middleware such as the integration with the Workgroup Manager (SOAP Services), the integration with ThingWorx Navigate via RESTful Services etc.

     

    The middelware is required in the integration with ERP Systems, but also not required as you can stick with ERP Connector only (uni-directional communication) or you can use REST Framework if your ERP is REST-Based.

     

    + The middleware is required in the integration of Windchill PLM with Codebeamer/PTC RV&S or PTC Modeler, PTC calls this integration "Digital Product Traceability (DPT). And the middelware here is not the ESI one is Thingworx Foundation + Flow.

     

    All those integrations are ESI, just because the ERP integration was old it takes the same name whereas the integration with PTC products is called DPT.

     

    Because two different middlewares are used, PTC thinks to make one unified middleware for all kinds of these integrations.

     

    tarikwifakp_0-1739451415104.png

     

     

     

    I encourage you to read this LinkedIn article

    and see the graphic of Digital Thread: Microsoft OneDrive

      Terms & ConditionsAccessibility statement