Understanding SOA in Teamcenter and How It Works with Active Workspace (AWC)

What is SOA in Teamcenter?

Service-Oriented Architecture (SOA) in Teamcenter is a framework that exposes core PLM business logic as reusable services. These services can be consumed by different clients—Active Workspace (AWC), Rich Client, custom applications, or external enterprise systems.

Why SOA Matters in a Teamcenter + AWC World

In real projects, you rarely work only with out-of-the-box Teamcenter. You extend, integrate, and customize. SOA is what keeps everything consistent and safe while you do that.

• Consistency – AWC, Rich Client, and custom integrations rely on the same service logic.
• Security – Authentication and authorization are handled centrally at the SOA/TC server level.
• No direct DB access – You work at the PLM object level, not with SQL queries.
• Cloud-ready – SOA is built for distributed, multi-tier, and Teamcenter X environments.

How Active Workspace (AWC) Uses SOA Behind the Scenes

Active Workspace is a web UI built using modern web technologies (HTML, JavaScript, ViewModels, JSON). However, AWC never talks directly to the Teamcenter database. Instead, it communicates with the Teamcenter server through REST, which in turn uses SOA services internally.

Step-by-Step Request Flow

1. User action in AWC: User opens a structure, creates an item, revises a part, or starts a workflow.
2. ViewModel prepares JSON: AWC uses ViewModel XML and JavaScript actions to build a JSON request for the operation.
3. REST Gateway receives the call: AWC sends the JSON to the Teamcenter REST API endpoint.
4. REST → SOA translation: The REST layer maps the request to the corresponding SOA service and method.
5. SOA executes business logic: Teamcenter validates permissions, applies rules, reads BMIDE configuration, and talks to the database.
6. Response returns to AWC: SOA returns the result → REST formats the response → AWC updates the UI ViewModel and refreshes the screen.

Common SOA Services Used by AWC

Almost every click in AWC maps to one or more SOA operations. Some of the frequently used services are:

When you see loading spinners or network calls in AWC for things like “Open in Structure Manager” or “Revise Item”, under the hood you are watching SOA services in action.

Example: Creating an Item in AWC Using SOA

Let’s walk through a common real-world scenario.

1. User Action in the UI

The user clicks “Create Item” in AWC. They fill in the item type, name, description, and then click Create.

2. AWC Builds the Request

The ViewModel and JavaScript action handler prepare JSON input that contains:

• Item type (e.g., Item, Design)
• Property values (ID, name, description, owning user, etc.)
• Context (folder / project where it will be created)

3. REST Gateway Forwards to SOA

The REST API endpoint receives the JSON and maps it to a SOA call, typically the createObjects operation in DataManagementService.

{
  "objects": [
    {
      "type": "Item",
      "properties": {
        "object_name": "My New Part",
        "object_desc": "Description for the new part"
      }
    }
  ]
}

(This is a conceptual example; actual payloads are more detailed and schema-driven.)

4. Teamcenter Handles the Logic

• Generates Item ID and Revision ID (based on ID rules).
• Checks the user’s permissions and group membership.
• Applies BMIDE rules and default values.
• Saves the object in the database.

5. AWC Shows the New Item

The SOA layer returns the created object information → REST formats it → AWC updates the ViewModel and opens the new item summary page for the user.

How Developers Use SOA in AWC Customization

If you’re a Teamcenter technical consultant or developer, here’s where SOA shows up in your AWC work:

1. Custom Commands and Actions

You create a new AWC command (button / menu) and wire JavaScript actions or ViewModel handlers. These actions ultimately call REST endpoints which map to SOA operations in the backend.

2. Extended Business Logic

You can build custom SOA operations or use existing ones, then trigger them from AWC based on specific user flows (e.g., auto-creating related objects, validating BOMs, etc.).

3. Integration with External Systems

Middleware (like a Python Flask API, Node.js, or Java microservice) can call Teamcenter via SOA or REST to synchronize:

• Item/BOM data with ERP.
• Change objects with MES or QMS.
• Documents and specifications with DMS or external portals.

SOA vs REST in Teamcenter AWC

Modern Teamcenter versions strongly promote REST, especially for web and cloud integrations, but SOA is still the core engine.

So, you can think of it like this: REST is the modern interface you see, but SOA is the engine room that actually runs the PLM logic.

Conclusion

Want to Learn SOA & AWC Customization in Depth?