0% found this document useful (0 votes)
65 views56 pages

Active Workspace Architecture Overview

Active Workspace Architecture Overview

Uploaded by

amitbankapur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
65 views56 pages

Active Workspace Architecture Overview

Active Workspace Architecture Overview

Uploaded by

amitbankapur
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd

Active Workspace

High Level Architecture


Shaishav Shah

Restricted © Siemens AG 2015 Realize innovation.


Agenda

• Introduction to Active Workspace


• Architecturally Significant Business Drivers
• Architecture Views
• System & Environment
• Physical Views
• Logical Views
• Development Views
• Hosting & Embedding
• Platform compatibility
• Extensibility
• Configuration & Customization

Restricted © Siemens AG 2015


Page 2 20XX-XX-XX Siemens PLM Software
Introduction to Active Workspace

Restricted © Siemens AG 2015


Page 3 20XX-XX-XX Siemens PLM Software
Active Workspace – Important Links

 AW home page ->


https://mycommunity.ugs.com/products/tc/planning/TcPlanning/ActiveWorkspaceClient/th
inclient/WikiLibrary/Home.aspx

 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

Restricted © Siemens AG 2015


Page 4 20XX-XX-XX Siemens PLM Software
Active Workspace

Find what you need faster Make smarter decisions PLM anytime anywhere

• Intelligent charts • See all relevant information in • Web-intuitive, configurable UI


• Shopping cart-like filters on context • Identical experience on any
properties, shape & • Easily participate in PLM – device with no client install
classification dashboards, signoffs, workflow, • Embeddable components
• Results ranking visualization, SDPD, SLM,
• Visually navigate structures and social collaboration, …
relationships

Restricted © Siemens AG 2015


Page 5 20XX-XX-XX Siemens PLM Software
Business Challenges Addressed

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

Simplified decision making – visibility


• Find the information you need to make a decision – easier than ever
• Presents the right information in the right context at the right time
• Easy access to relevant data stored in multiple external systems
• Access for ALL members of the decision making process…

Restricted © Siemens AG 2015


Page 6 20XX-XX-XX Siemens PLM Software
Architecturally Significant Business Drivers

Restricted © Siemens AG 2015


Page 7 20XX-XX-XX Siemens PLM Software
Architecturally Significant Business Drivers

• Superior user experience

• World class performance

• Zero install

• Device & browser independence

Restricted © Siemens AG 2015


Page 8 20XX-XX-XX Siemens PLM Software
Architecturally Significant Business Drivers
Superior User Experience

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

Restricted © Siemens AG 2015


Page 10 20XX-XX-XX Siemens PLM Software
Architecturally Significant Business Drivers
Zero install

No IT cost for client install


 No per desktop IT administration and
maintenance cost
 Reduced cost of ownership

IT security
 Firewall friendly. No special casing
needed for browser plugins

Restricted © Siemens AG 2015


Page 11 20XX-XX-XX Siemens PLM Software
Architecturally Significant Business Drivers
Device & browser independence

Work across devices


 Desktop and mobile
 Bring PLM to the user across all
devices

Support all modern browsers


 Allow customers to use the browser
of choice based on their internal IT
needs

Restricted © Siemens AG 2015


Page 12 20XX-XX-XX Siemens PLM Software
Architecture Views

Restricted © Siemens AG 2015


Page 13 20XX-XX-XX Siemens PLM Software
System & Environment
High Level Context View

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

Restricted © Siemens AG 2015


Page 14 20XX-XX-XX Siemens PLM Software
Physical View
Deployment Diagram

NX
Active
Browser
Client

Workspace
Hosted

Active Workspace WAR

HTML/JS/CSS FMS Proxy SOA Proxy Vis Proxy


Web

Teamcenter Gateway

Pool TcServer FSC Vis Pool Vis Server


Enterprise

TcServer FTS Indexer Vis Server


Manager TcServer Manager Vis Server
TcServer Vis Server
SOLR
Resource

DB Solr Index Volume


Restricted © Siemens AG 2015
Page 15 20XX-XX-XX Siemens PLM Software
Physical View
Deployment Diagram – Forward Deployment

Client
Browser

Active Workspace WAR

SOA Proxy FMS Proxy HTML/JS/CSS Vis Proxy

Web
Vis Pool VisVis
Server

Enterprise
FSC Server
Manager Vis Server
Vis Server

Web Teamcenter Gateway

Pool TcServer FSC


Enterprise

TcServer FTS Indexer


Manager TcServer
TcServer
SOLR
Resource

DB Solr Index Volume

Restricted © Siemens AG 2015


Page 16 20XX-XX-XX Siemens PLM Software
Logical View
Communication Diagram - Login

Server Pool
Manager

1. Login ig n
A ss
4. 5. Start

Web Browser 2. Login 3. Login


AW Web App Web App Server 6. Login
Active Teamcenter
Server Teamcenter
Workspace Server
SOA proxy Gateway
Client

7. Create Session

Teamcenter
Database

Restricted © Siemens AG 2015


Page 17 20XX-XX-XX Siemens PLM Software
Logical View
Communication Diagram – SSO Login

Web App Server 4. Redirect Identity Provider


Teamcenter (LDAP, Kerberos,
Security Services SiteMinder…)

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

11. Create Session

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

2. Perform Search 4. Query + filters


Active Teamcenter
Solr
Workspace Server
7. Results + facets 5. Results + facets

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)

http(s) Vis Pool


Model Launch Vis
Manager
Rotation Proxy socket
Servlet
VisServer.exe
F
camera
C
VisServer.exe
C
. Non-Vis
. Operations awc.war JT Files
. VisServer

SOA
SOA BOM Tc Pool
Proxy Load Manager
Servlet
TcServer.exe

Web Server TcServer.exe

TcServer.exe
Restricted © Siemens AG 2015
Tc Server

Page 20 20XX-XX-XX Siemens PLM Software


Development View
Technology

Client technology
• GWT, HTML5, CSS & JavaScript

Forward deployment proxies


• J2EE & IIS*

Restricted © Siemens AG 2015


Page 21 20XX-XX-XX Siemens PLM Software
Development View
Technology

Communication
• Consumes Teamcenter SOA Services
• JSON payload
• HTTPS POST
• REST

Restricted © Siemens AG 2015


Page 22 20XX-XX-XX Siemens PLM Software
Development View
Technology

Search
• Apache Solr™ Indexing & Facets

AW Server templates
• BMIDE templates
• C++ libraries
• Schema

Restricted © Siemens AG 2015


Page 23 20XX-XX-XX Siemens PLM Software
Development View
Installable packages – Client – Desired architecture

CAD Teamcenter Electronic


Requirement Library Viewer
Level 5 SDPD
SDPD
SDPD Integration for Work NGP
SDPD SDPD
SDPD s Management Admin
s SDPD Simulation Instructions

Document Schedule Service Service Work Easy


IPD
SDPD
SDPD …
SDPD Management Manager Manager Instructions Plan

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

Level 2 Graphing Rich Text Shape


Search Charts PDF.js …
Component Editor Search

Level 1 Active Workspace Framework

Restricted © Siemens AG 2015


Page 24 20XX-XX-XX Siemens PLM Software
Development View
Installable packages – Client – Desired architecture

Domain Specific Components

Cross Domain Components

AW Tc Framework

Generic Cross Domain Components

Restricted © Siemens AG 2015 AW Framework


Page 25 20XX-XX-XX Siemens PLM Software
Development View
Installable packages – Client – Step 1

Domain Specific Components

Cross Domain Components

AW Tc Framework

Restricted © Siemens AG 2015


Page 26 20XX-XX-XX Siemens PLM Software
Development View
Package components – Client - Desired architecture

Active Workspace Framework

Base client framework components that


forms the foundation of Active
Workspace.

Can be used for Teamcenter and non-


Teamcenter purposes.

Restricted © Siemens AG 2015


Page 27 20XX-XX-XX Siemens PLM Software
Development View
Package components - Client – Desired architecture

Generic Cross Domain Components

Components that can be used across various


domains

Can be used for Teamcenter and non-Teamcenter


purposes

Optionally installable

Restricted © Siemens AG 2015


Page 28 20XX-XX-XX Siemens PLM Software
Development View
Package components - Client – Desired architecture

Teamcenter
Active Workspace Framework

Base client framework components that


form the foundation of Active Workspace
for Teamcenter.

Integral part of any Teamcenter Active


Workspace web applications.

Restricted © Siemens AG 2015


Page 29 20XX-XX-XX Siemens PLM Software
Development View
Package components - Client – Desired architecture

Cross domain components

Components that can be used across


various domains

Optionally installable

Restricted © Siemens AG 2015


Page 30 20XX-XX-XX Siemens PLM Software
Development View
Package components - Client – Desired architecture

Domain specific components

Components targeting a specific domain

Optionally installable

Restricted © Siemens AG 2015


Page 31 20XX-XX-XX Siemens PLM Software
Hosting & Embedding

Restricted © Siemens AG 2015


Page 32 20XX-XX-XX Siemens PLM Software
Active Workspace Everywhere
Hosting in other applications

Consistent user experience, Less training

Previously we tried to “hide” Teamcenter


in other applications
• Look like the application
• Work like the application

But this was not optimum Adobe Illustrator Teamcenter Rich Client
• More development
• More support
• More training

A common interface is more efficient


• Consistent behavior
• Consistent capabilities
• Less Training
NX Teamcenter Visualization
Restricted © Siemens AG 2015
Page 33 20XX-XX-XX Siemens PLM Software
Active Workspace Everywhere
Hosting in other applications

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

Restricted © Siemens AG 2015


Page 34 20XX-XX-XX Siemens PLM Software
Active Workspace Everywhere
Hosting other applications in Active Workspace

Accessing data from external sources


• To do their work, Users need to access related data in
other systems efficiently
• Bring the right related information to the users instead of
making them go look for it

Embed HTML panel via XML Stylesheet


• Connect to other business systems with Rest/Soap
API’s
• Embed iFrames with dynamic URL generation using
Example usage
object and session parameters
• Inventory
• Current orders
Siemens Web Application Components (SWAC)
• Integration of web components from different appservers • Customer information
• Two way communication across web components • People information
• CRM

Restricted © Siemens AG 2015


Page 35 20XX-XX-XX Siemens PLM Software
Configuration & Customization

Restricted © Siemens AG 2015


Page 36 20XX-XX-XX Siemens PLM Software
AW Customization Guide scope

Spans the configuration / customization spectrum

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

Restricted © Siemens AG 2015


Page 37 20XX-XX-XX Siemens PLM Software
Configuration
XRT Style Sheets

• Style sheets
• Properties
• Summary layout
• Info area layout
• By Object type
• By group, role, project

see Customization Guide

Restricted © Siemens AG 2015


Page 38 20XX-XX-XX Siemens PLM Software
Configuration
Home Tiles

• Configure the Launch Page


• Show, Hide tiles by user, role,
group
• Define new tiles

See Customization Guide

Restricted © Siemens AG 2015


Page 39 20XX-XX-XX Siemens PLM Software
Configuration
Cell Properties

• Configure object tiles


• Which properties
• By Type
• By group, role, project

see Deployment Guide

<object>.CellProperties

Restricted © Siemens AG 2015


Page 40 20XX-XX-XX Siemens PLM Software
Configuration
Search - Apache Solr™ Indexing & Facets

 Configure Search
 Types
 Facets
 Filters
 Pre-Filters

see Deployment Guide

Restricted © Siemens AG 2015


Page 41 20XX-XX-XX Siemens PLM Software
Configuration
Column configuration

 Column Configuration
 Hide/unhide
 Reorder
 Column width

 Column Configurations at
 Site level
 Group level

see Deployment Guide

Restricted © Siemens AG 2015


Page 42 20XX-XX-XX Siemens PLM Software
HTML Panel
Integration

 New XRT element


 Supports URL and HTML content
 HTML custom panel solution
 Iframe integrations
 With data binding

see Customization Guide

<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:

1. Create a new Theme


2. Create One Step Command
3. Create Tool and Information Command
4. Create Navigation Command
5. Custom Type Icons
6. Custom Locations and Sub-locations

Restricted © Siemens AG 2015


Page 44 20XX-XX-XX Siemens PLM Software
Platform Compatibility

Restricted © Siemens AG 2015


Page 45 20XX-XX-XX Siemens PLM Software
Platform Compatibility

Active Workspace releases asynchronously from Teamcenter Platform


• Has its own release cadence
• Has its own versioning

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

9.1.2.10 9.1.3.1 9.1.3.4 10.1.5


Teamcenter 10.1.1 10.1.2 10.1.2.1 10.1.2.3 10.1.4 11.2 11.2.0.2

2014 2015 2016

Active Workspace 2.1 2.2 2.3 2.4 3.0

Restricted © Siemens AG 2015


Page 46 20XX-XX-XX Siemens PLM Software
Platform Compatibility
Binary compatibility with Platform releases

Active Workspace server code requires a minimum minor/patch release of the


Platform Stream

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

Restricted © Siemens AG 2015


Page 47 20XX-XX-XX Siemens PLM Software
Platform Compatibility
Customers do not want to upgrade Platform to use Active Workspace

Currently we require a minimum minor/patch release of the platform


• This minimum minor/patch release changes from Active Workspace release to AW 3.0
release
• Upgrading platform is a big cost for customers and partners
• Changing minimum required platform release is undesirable
Tc10.1.5+ Tc11.2.1+
Active Workspace can expose capabilities that only exist in a newer minor/patch
release
• Capabilities (Schema and API) can be added in a newer minor/patch platform
AW 3.1
release
• Exposing these newer capabilities in Active Workspace cannot change the
minimum required minor/patch platform release

Tc10.1.5+ Tc11.2.1+

Restricted © Siemens AG 2015


Page 48 20XX-XX-XX Siemens PLM Software
Platform Compatibility
Release Alignment – 2.0 Stream

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)

Restricted © Siemens AG 2015


Page 49 20XX-XX-XX Siemens PLM Software
Platform Compatibility
Release Alignment – 3.0 Stream

Teamcenter 10.x Teamcenter 11.x


Number Internal Name Date Minimum Full Minimum Full
Version Featured Version Featured
October 30,
3.0 Connecticut 10.1.5 10.1.5 11.2.1 11.2.1
2015
April 29,
3.1 Massachusetts 10.1.5 10.1.6 11.2.1 11.2.2
2016
October 28,
3.2 Maryland 10.1.5 10.1.7 11.2.1 11.2.3
2016
TBD South Carolina Spring 2017 TBD 10.1.8 TBD 11.2.4
TBD New Hampshire Fall 2017 TBD TBD TBD TBD

Restricted © Siemens AG 2015


Page 50 20XX-XX-XX Siemens PLM Software
API Exposure

Restricted © Siemens AG 2015


Page 52 20XX-XX-XX Siemens PLM Software
Server API Exposure

Schema and API exposed by Active Workspace Server components


• Follow same rules as Platform server components
• API => ITK, C++ Interfaces, SOA

Published API signature and behavior cannot change after release


• If behavior change is needed, a new Published API needs to be created and
existing Published API needs to be deprecated
• Deprecated API can be removed after 2 major releases

For Active Workspace the major releases are every 6 months


• Example: AW 2.3, AW2.4, AW3.0

Restricted © Siemens AG 2015


Page 53 20XX-XX-XX Siemens PLM Software
Component Contract

 Components need to publish APIs for other components to consume


 The API that is published needs to go through a deprecation policy before changing
 All classes in an “internal” package are internal to the GWT module and should not be referenced
outside the GWT module
 As a best practice, components should expose only the necessary API in published packages. This is
the component’s contract and needs to contain only the limited set of interfaces that the component
authors expect consumers of the component to use
 All classes in the “published” package are published based on the ApiVisibility annotation that must be
added on all the classes/interface and its methods

 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

Restricted © Siemens AG 2015


Page 54 20XX-XX-XX Siemens PLM Software
Component Contract

Maturity Publish Scope Description

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.

Restricted © Siemens AG 2015


Page 55 20XX-XX-XX Siemens PLM Software
Component Contract

Maturity Publish Scope Description

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)

Restricted © Siemens AG 2015


Page 56 20XX-XX-XX Siemens PLM Software
Thank You

Restricted © Siemens AG 2015


Page 57 20XX-XX-XX Siemens PLM Software

You might also like