Active Workspace Architecture Overview
Active Workspace Architecture Overview
AW environments ->
https://mycommunity.ugs.com/products/tc/common/QA/envinfo/qainfo/qainfo_US/Lists/P
roduct%20TE%20Pages%20%20Teamcenter%2020071/Active%20Workspace.aspx
Find what you need faster Make smarter decisions PLM anytime anywhere
Simplified access to product data and processes for the extended enterprise
• Ease of Use / Intuitive
• Task oriented
• Leverages common user interface paradigms used on the web
• Find what you’re looking for quickly and easily
Time to value/deployment
• No local client or plugin installation required
• Accelerated user adoption/acceptance
• No training requirements for casual users
• Zero install
Personalized Ux
• Speak my language
• Bring me the information I need
• Show me only what’s needed
• Give me only the right actions
Graphically Engaging Ux
• Make it interesting
• Make it enjoyable
• Make it easy
Multi-Device Ux
• Work across all my devices
Industry-Tailored Ux
• Speak the language of my industry
Restricted © Siemens AG 2015
Page 9 20XX-XX-XX Siemens PLM Software
Architecturally Significant Business Drivers
World class performance
User Interaction
Goal - Login Page should come up
within 2 seconds
Goal - Every user action irrespective
of data size should respond within 2
seconds
Global deployment
Operating over high latency WAN
and low bandwidth connections
IT security
Firewall friendly. No special casing
needed for browser plugins
Service
Runtime Web Content Requests Teamcenter
Environment (Non Embedded) Web Server
Browser
Embedded
Content
Embedded
Streaming
Browser
Active Request Visualization
Service Workspace Server
Requests
(Embedded) Upload and
Download Files
Host Teamcenter
Commands, Selections
FMS
NX
Active
Browser
Client
Workspace
Hosted
Teamcenter Gateway
Client
Browser
Web
Vis Pool VisVis
Server
Enterprise
FSC Server
Manager Vis Server
Vis Server
Server Pool
Manager
1. Login ig n
A ss
4. 5. Start
7. Create Session
Teamcenter
Database
Server Pool
10. Verify
3. Redirect
1. Launch 5. SSO token Manager
s i gn
s
7. A 8. Start
Web Browser AW Web App
2. Login 6. SSO Login Web App Server 9. SSO Login
Active Server Teamcenter
Teamcenter
Workspace SSO Server
Gateway
Client Authenticator
Teamcenter
Database
Restricted © Siemens AG 2015
Page 18 20XX-XX-XX Siemens PLM Software
Logical View
Communication Diagram - Full Text Search
3. Create Query/filters
1. Perform Search
6. Load objects
Teamcenter
Database
Restricted © Siemens AG 2015
Page 19 20XX-XX-XX Siemens PLM Software
Logical View
Communication Diagram - Visualization
Model (.vvi)
Active Workspace
VisServer port
Client http(s)
SOA
SOA BOM Tc Pool
Proxy Load Manager
Servlet
TcServer.exe
TcServer.exe
Restricted © Siemens AG 2015
Tc Server
Client technology
• GWT, HTML5, CSS & JavaScript
Communication
• Consumes Teamcenter SOA Services
• JSON payload
• HTTPS POST
• REST
Search
• Apache Solr™ Indexing & Facets
AW Server templates
• BMIDE templates
• C++ libraries
• Schema
4G Relationshi
Level 4 Reports Markup Change Classification Social Viewer
SDPD
SDPD
Foundation p Browser SDPD
Project
Inbox & Teamcenter Digital Structure
ACE Subscription Manageme …
Workflow Search Signature Viewer
nt
Level 3
Active Workspace Teamcenter Framework
AW Tc Framework
AW Tc Framework
Optionally installable
Teamcenter
Active Workspace Framework
Optionally installable
Optionally installable
But this was not optimum Adobe Illustrator Teamcenter Rich Client
• More development
• More support
• More training
Services
• Communication between the host and web
content uses services.
• Service Contracts will describe the messages
exchanged by the service.
• Service contract marshaled as JSON
• Services are versioned. Allows for host to support
multiple versions of a service simultaneously
• Shares host’s server (NX, RAC)
Host Environments
• Java
• C# / .Net
• C++
• JavaScript
1) Configuration
• Home tiles, stylesheets, cell properties, table columns, search filters &
indexes
2) HTMLPanel in stylesheets
• iframe integration, HTML custom panel solution
3) SDK
• Supports Code-full Customization of the Teamcenter AW Client
• Customization Guide contains detailed AW architecture overview
• Command line Tools for code scaffolding for key scenarios
• Samples & Step by Step explanation of key scenarios
• Requires skills in Web development + Java + GWT + Teamcenter concepts
• Access to a set of API and code that AW developers from Application teams
leverage
• Style sheets
• Properties
• Summary layout
• Info area layout
• By Object type
• By group, role, project
<object>.CellProperties
Configure Search
Types
Facets
Filters
Pre-Filters
Column Configuration
Hide/unhide
Reorder
Column width
Column Configurations at
Site level
Group level
<htmlPanel src=”https://www.mycorp.com/info?id={{selected.properties[‘item_id’]}}”/>
Restricted © Siemens AG 2015
Page 43 20XX-XX-XX Siemens PLM Software
Customization
Code scaffolding
SDK contains command line Tools for code scaffolding for key scenarios
Tools create a skeleton starter code for customizing the following capabilities:
Active Workspace release kits consists of both Client and Server Components
• They have to be updated in the customer install environments at the same time
Upgrading to a newer minor or patch version of the Platform does not require
upgrading Active Workspace AW 2.3
• Customer can upgrade from Tc10.1.2.3 to Tc10.1.4 and can still use AW 2.3
Target -1 Target
Release Release
Active Workspace server code is binary compatible with all newer minor and
patch versions of the Platform Stream
• Uses published API from Platform Tc9.1.3.1+ Tc10.1.2.3+
• Published API from Platform cannot change in minor and patch versions of
the Platform Stream
Tc10.1.5+ Tc11.2.1+
Teamcenter Teamcenter
Number Internal Name Date
9.x 10.x
9.1.2.3
2.0 Delaware Aug. 15, 2013 10.1
9.1.2.4
9.1.2.7 10.1.1.1
2.1 Michigan Mar. 10, 2014
9.1.2.8 10.1.1.2
2.2 Pennsylvania Aug. 29, 2014 9.1.2.10+ 10.1.2.1+
2.3 New Jersey Nov. 26, 2014 9.1.3.1+ 10.1.2.3+
April 30, 2015 (10.1.4) 9.1.3.4+ 10.1.4+
2.4 Georgia May 30, 2015 (9.1.3.4) (same date as 2.4) (same date as 2.4)
See section on API Visibility – annotation, maturity and visibility in chapter Part 04 – Common Coding Patterns from
How to use the Client Framework
https
://mycommunity.ugs.com/products/tc/smp/nizami/thinclient/Shared20Documents/ClientDocumentation/Part%2004%20-%20Common%20C
oding%20Patterns.docx
Experimental Internal
This indicates that the API is experimental and internal to Siemens PLM Development and should not be used by
modules which are not authored by Siemens PLM Development.
The experimental state indicates that the API is still under construction. There will be no deprecation for
Experimental API.
The API can be modified or removed in the next build/release. A replacement might not be provided for the API.
The Experimental API that are removed or modified will be noted in the release notes for the build/release.
DO NOT use Experimental API for Production Use. It is only meant for Experimenting.
Mature Internal
This indicates that the API is Mature and internal to Siemens PLM Development and should not be used by
modules which are not authored by Siemens PLM Development.
This API will not change. If changes are needed, the existing API will be deprecated and an alternative API will
be identified. The alternative will be available in the same build/release that the API is deprecated.
An announcement to the SPLM development client teams will be made to highlight the deprecation of the API.
This announcement will specify the time frame after which the deprecated API will be removed. Minimum
duration for its removal and default will be 2 Sprint cycles. The 2 Sprint Cycle starts at the point the deprecation
changes are included and published in the build of the integration node.
Experimental Public
This indicates that the API is experimental and public. It can be used outside the GWT module by any module
(internal or third party or customer).
The experimental state indicates that the API is still under construction. There will be no deprecation for
Experimental API.
The API can be modified or removed in the next build/release. A replacement might not be provided for the API.
The Experimental API that are removed or modified will be noted in the release notes for the build/release.
DO NOT use Experimental API for Production Use. It is only meant for Experimenting.
Mature Public
This indicates that the API is mature and public. It can be used outside the GWT module by any module (internal
or third party or customer).
This API will not change. If changes are needed, the existing API will be deprecated and an alternative API will
be identified. The alternative will be available in the same build/release that the API is deprecated.
The build/release notes will identify the time frame after which the deprecated API will be removed. The
deprecation will be 2 major releases of the client(1.0, 2.0, ...) (not Teamcenter releases)