ugs - teamcenter's soa

7/31/2019 UGS - Teamcenter's SOA

1/12

UGS PLM Software

UGS Teamcenter

www.ugs.com/teamcenter

UGS TeamcentersService Oriented ArchitectureIntegrating UGS Teamcenter-managed product design anddevelopment with your mainstream business processes

Todays companies are discovering they can more flexibly perform their business

processes with less IT intervention if they use a service oriented architecture (SOA)

as the technological foundation for their digital product design and development

environment. UGS Teamcenter software's SOA services provide an open, high-

performance, coarse-grained interface to the Teamcenter system's Business Logic

Server. These services enable you to access Teamcenter-driven capabilities and integrate

them with your existing business processes as well as to create customized, task-

specific programs to meet your business needs.

w h i t e p a p e r


2/12

Table of contents

Executive summary 1

Introducing UGS Teamcenter's SOA 2

Using UGS Teamcenter'sSOA services 5

A final evaluation 9

UGS Teamcenters Service Oriented Architecture


3/12

1

The biggest challenge for todays corporate IT organizations is to provide

improved real-time visibility into their companys business operations. IT

leadership is especially concerned with managing the software

application lifecycle and controlling its cost.

Research indicates that the vast majority of IT executives and other senior

managers are convinced that a service oriented architecture (SOA) is the

right technology approach for improving IT agility and lowering that

portion of the IT budget (40 percent) associated with application

integration. Increasingly companies are discovering that their business

becomes more nimble and their processes become more flexible when

they implement SOA as the technological foundation for key computing

environments (such as the product design and development

environment). Equally important, SOAs are able to facilitate these

improvements with less IT intervention than was previously possible.

To address these rising IT requirements, UGS PLM Software has developed

an SOA infrastructure for UGS Teamcenter, UGS PLM Software's flagship

software for facilitating product lifecycle management (PLM) and sup-

porting the PLM-driven business processes adopted by its customer base.

Teamcenter is industrys most widely used PLM solution with an

integrated suite of applications that leverage technologies such as 3D

visualization, community collaboration, supplier management and

collaborative product data management (cPDM) to drive business

productivity.

Teamcenters SOA services provide a new coarse-grained interface to

Teamcenters Business Logic Server. Teamcenters SOA services represent

UGS PLM Softwares go-forward strategy for enabling client and external

applications to access a Teamcenter-managed environment. These

services can be used to:

Integrate Teamcenter capabilities into your existing business processes,

as well as for creating custom, task-specific client programs

Embed Teamcenter-managed information and status results into

existing clients, portals and executive dashboards

Integrate the Teamcenter portfolio and its application solutions with

diverse external functionality, including CAD systems, collaborative

design management tools (such as Teamcenters own community

collaboration capabilities), manufacturing planning solutions (such as

Tecnomatix) and highly popular business applications (such as

Microsoft Office). As a result, you can establish a single cohesive

environment capable of supporting all of your digital lifecycle

management initiatives

Teamcenters SOA is based on industry standards for Web Services,

primarily adhering to WS-1 and other WS-x standards and best practices.

SOA services also are accessible through numerous language-specific

libraries that make it easy for programmers with C, C++, C# and Java

experience to incorporate Teamcenter functionality into new and existing

applications.

Why a service-oriented architecture is important

Teamcenters SOA services provide new capabilities that allow you to

deploy higher performing and more scalable WAN-friendly and firewall-

friendly applications in a Teamcenter environment. Because these

capabilities adhere to industry standards and established best practices,

Teamcenter services are now accessible to a wider development

community.

In turn, wider accessibility increases the likelihood that more robust and

comprehensive services will evolve at a faster rate. Similarly, the

worldwide development community will be able to access and leverage

these services without having to learn how to use a proprietary language

or protocol; no special training is required.

What you can do with UGS Teamcenters SOA services

Teamcenters SOA is a coarse-grained API that openly exposes

Teamcenters Business Logic Server capabilities to Web Services, as well

as to language-specific programs. This provides an ideal solution for

enabling a wide range of applications to access your Teamcenter

environments product design and development information.

Teamcenter itself functions as the engine and repository that connects all

of your environments design and product development information in a

flexible and loosely coupled manner while providing your entire global

environment with a single point of access to these connected assets.

Because Teamcenters SOA services are exposed as both WS-1 compliant

WSDL1 and language-specific interfaces, project teams are able to

leverage an interface that best meets their own needs while assuring that

the Teamcenter operations being called are the same and that their

results will be the same regardless of the language or binding being

used. In addition, Teamcenters SOA easily supports batch, or non-

interactive applications, as well as highly interactive end-use applications

on the desktop.

Gaining UGS Teamcenters SOA advantage

Organizations that adopt Teamcenters SOA gain the advantages inherent

in the use of a consistent, comprehensive set of interfaces that leverage

Teamcenters powerful product design and development services.

Regardless of what language you use to call these services (and that

choice is entirely up to you), the business logic and results received from

Teamcenters SOA will be the same.

You no longer need to worry about your project teams skill sets or any

language-related dependencies. Teamcenters SOA provides a single set

of entry points for use by all clients and applications regardless of their

heritage.

As new services are exposed via Teamcenters SOA, they will be

immediately available in all supported programming languages, as well

as through industry-standard WSDL.

Executive summary

1 Web Services Description Language (WSDL)


4/12

Figure 1: UGS Teamcenter SOA Framework Components

2

Introducing UGS Teamcenters SOA

What is a service-oriented architecture?

A service-oriented architecture is a system design pattern that emphasizes

the following attributes along with other considerations:

Appropriate functional granularity appropriate to the task at hand Separation of the interface definition from its implementation

Support for the concept of service providers and service consumers

who are distinct from each other

Standards-driven compliance

Service-oriented architectures also reflect a specific:

Software framework

Set of policies

Set of best and accepted practices

Teamcenters Service Oriented Architecture (SOA) embodies all of these

principles and characteristics. It is built upon a framework consisting of

the entire client and service infrastructure that contributes to consistent,reliable and high-performance interaction between the application clients,

service consumers and Teamcenter Business Logic Server (the service

provider in this scenario).

This framework enables application developers to concentrate on creating

specific business functionality rather than worrying about the low-level

communications and data management activities going on beneath them.

Teamcenters SOA characteristics reflect two additional factors:

Messaging via standard protocols

Message content formats

Like the implementations of most service-oriented architectures,Teamcenters SOA uses standard HTTP/S communications protocols

to send XML documents back and forth between the service provider and

the service consumer. Use of these standards contributes to the openness,

flexibility and scalability necessary for both the local and global

deployment of Teamcenter. It is this open, standards-based messaging

environment that allows service providers and service consumers to be

implemented in differing technologies while retaining their

interoperability.

This messaging environment also allows existing applications in one

technology to be quickly adapted so that they can interact with newer and

richer technologies and programming languages which helps your

company preserve its investments in existing programs and processes.

As a result of this flexibility, you can incrementally enhance your product

design and development environment at a speed that virtually matches

your business real-world evolution. This alignment is largely facilitated by

the arms-length, loosely coupled relationship that exists between service

providers (like Teamcenters Business Logic Server) and service consumers

(like Teamcenter clients, CAD systems, Microsoft Office and your own

portal and dashboard applications).


5/12

A technical look at UGS Teamcenters SOA

Teamcenters SOA consists of the following client-side and server-side

components that follow well-defined patterns using standards-based

protocols, languages and data formats.

SOA Frameworkprovides the communications and infrastructure

functionality that enables application developers to concentrate on

creating business solutions rather than dealing with underlying

communications/messaging issues

SOA Language Bindings provide language-specific functions (.NET, C++,

and Java) used by service consumers to invoke an SOA service and

properly handle the ensuing response

SOA Client Data Model (CDM) and Data Model Managerprovide

managed type-safe storage on the service consumer side for all data

returned by service responses from Teamcenters Business Logic Server

SOA Toolkit provides tools that enable Teamcenter developers to auto-

generate all of the artifacts necessary for exposing new Teamcenter

business logic as SOA services

In addition to these major components, Teamcenters SOA

environment also includes documentation on each of the language

bindings, WSDL and various XML Schema Definitions (XSDs) used

throughout the system.

The relationships between the environment and its major components are

illustrated in figure 2.

The accompanying table describes the major components in Teamcenters

SOA major in more detail.

3

Component Function

SOA Framework Consists of the client-side libraries, as well as the communications infrastructure andserver-side libraries that make up a full-featured request/response pipeline. All SOA

Framework components are auto-generated by the SOA Toolkit and are completely opaqueto both the author of the service and consumer of the service.

SOA Language Bindings Represents the client-side components required to execute a service request from anapplication. Because the SOA Toolkit auto-generates these components, the components

are functionally equivalent across all supported languages. Initially, UGS provides bindingsfor C++, .NET and Java.

UGS Teamcenters Data Model Manager Populates and updates the client-side data store with objects returned from TeamcentersBusiness Logic Server on each SOA service call. Object identity is maintained so that whenan existing object is returned, its properties are updated in the data store rather thancreating a new/identical item.

Data Model Manager is also responsible for maintaining the meta-model of type and

property information. Optionally, it can fire events on object creation, deletion ormodifications. Client applications can register listeners for these events and react to themas appropriate.

UGS Teamcenters Client Data Model Generated from Teamcenters Data Model formally defined within Teamcenters Business(CDM) Modeler/IDE, Teamcenters SOA supports two types of CDM for client application use a

generic model and a type-safe model.

The generic model consists of simple objects and their properties. Utility functions areprovided to determine an objects Teamcenter type, to query the type hierarchy and toaccess the characteristics of each property on an object.

Derived from the generic model, the type-safe model adds strongly-typed accessors for allobjects and their properties. This models class hierarchy matches Teamcenters Business

Logic data model formally defined in Teamcenters Business Modeler/IDE. The accessorsfor each property return the language-specific equivalent of the native Teamcenter type

of property.

UGS Teamcenters SOAs major components


6/12

4

Server

Schema binderModel binder Service binder

Client

Client service bindingClient data model

TcBar .xxx FooRestBindingStub .xx

Client binding management

Event managementClient data model populator

Schema binder

T2LServices

FooCorbaBindingSkel

svc definitionssvc implementations

FooImpl .cxx Foo .hxx

xsd binding

CoreCore metamodel

bar .cxx

TcFooServie .xsd

Wire schama

SOABase .xsd

FooService .xsd

WS Presentation

FooService .xid

TestTcFooService .xxx

autotest framework

Figure 2: UGS Teamcenter SOA Functional Components


7/12

5

Using UGS Teamcenters SOA services

Logical deployment architecture

Organizations typically deploy the Teamcenter environment using a four-

tier logical architecture that consists of:

Client application Web application server

Enterprise Tier

Resource Tier

Figure 3: UGS Teamcenter SOA Runtime Deployment

Client application. Most client applications, including applications

developed by UGS and its partners, are language-based, rather than WSDL

based. As a result, they typically incorporate one of Teamcenters SOA

client libraries along with the CDM. Custom integrations developed using

the WSDL approach usually do not use client libraries or the CDM. Since

both types of clients are HTTP/S based, they can easily and effectively

access Teamcenter across low or high latency network connections as

well as securely traverse corporate firewalls without needing to open

additional application-specific ports in those firewalls.

Web application server. Teamcenter deployments use web application

servers to expose the SOA service endpoints for all client types. Both REST-

style (standard HTTP POST) and SOAP-style requests are supported by

Teamcenter components executing on industry-standard application

servers, such as Microsoft IIS, as well as servers based on Java and J2EE

technology. SOA Framework components running on these application

servers are responsible for normalizing the request into a single common

format, which is passed directly onto Teamcenters Business Logic Server

that resides in the Enterprise Tier.

Enterprise Tier. Teamcenters Business Logic Server along with

Teamcenters SOA server-side components, resides in the Enterprise Tier.

All of the actual SOA services are implemented in C++ as part of

Teamcenters Business Logic Server.

Resource Tier. The Resource Tier houses the Teamcenter database and

bulk-data file repositories. No SOA components are part of the Resource

Tier.


8/12

ApplicationsClassification : : Classification

Core : : DocumentManagementDocumentManagement : : DocumentTemplatesProjectManagement : : ScheduleManagementRequirementsManagement : : RequirementsManagement

Application supportAllocations : : Allocation MultiSite : : ObjectDirectoryQuery : : SavedQuery MultiSite : : TransferReports : : BOMRollup Workflow : : WorkflowReports : : CRFReportsStructureManagement : : RestructureStructureManagement : : GlobalAlternatesStructureManagement : : RedininingCalendarManagement : : CalendarManagement

PlatformCore : : SessionCore : : DocumentManagementCore : : FileManagementCore : : ReservationCore : : ManagedRelation

Application integrationAI : : AI

CAD : : DataManagementCAD : : StructureManagement

System administration

System definition

6

UGS Teamcenters SOA service areas

Teamcenters SOA services are organized into the following six

functional areas.

Platform

Application support

Applications

Application integration

System administration

System definition

Each of these functional areas is further broken down into one or more

libraries that contain the actual services and operations exposed by

Teamcenters Business Object Server. The accompanying diagram

indicates how the six functional areas are organized, as well as the

representative library and service names that pertain to key areas.

As the diagram illustrates, services are provided for fundamental needs

(such as session and file management), for supporting capabilities (such

as queries and reporting), and for specialized services (such as PLM

system definition and administration). Over time, UGS will introduce

additional libraries and services for each of these areas especially in the

application and application support areas.

UGS Teamcenters SOA service invocation

Before discussing how Teamcenters SOA services are invoked, it is helpful

to understand some of the basic principles that drive UGS design of

Teamcenters SOA services.

First, Teamcenters SOA provides set-based services meaning that

virtually all services accept multiple input objects that can be operated on

by the Business Logic in a single call. On both inbound and outbound

sides of a request/response cycle, it is advantageous to be able to submit

or respond with more than one item at a time. This flexibility is especially

important when invoking services over high-latency wide-area network

connections.

Adopting a set-based default design for all services also supports a loose-

coupling and infrequent communications pattern. At the same time, it

reduces the overall size of the service set by not eliminating the

requirement for both single item and multi-item interfaces for the same

operation. A set-based operation can easily handle a set-of-one without

requiring a separate interface.

Figure 4: UGS Teamcenter services functional areas


9/12

7

Second, Teamcenters SOA services are coarse-grained services

meaning that they perform operations that, from a developer and end-

user perspective, are relatively complete in and of themselves. The service

consumer asks for something to be done and Teamcenters Business Logic

Server does it. Teamcenters SOA services eliminate intermittent networkchatter that plagues many ordinary client/server applications.

UGS PLM Software designed Teamcenters SOA services so that the

response to a user operation (for example, highlighting a set of objects or

hitting the delete button) is performed in a single request/response

cycle. In other architectures and system designs, an operation like this

might take hundreds of request/response cycles to individually submit and

acknowledge the deletion of each highlighted or selected object.

Third, Teamcenters SOA services support the partial errorsconcept

meaning that a set-based operation can be only carried out on a subset of

the input items when an error condition arises. Again, drawing on the

delete button example, if some of the items selected for deletion are

locked or have outstanding dependencies or relationships, it often is

neither wise nor possible to delete these items as requested. In these

cases, it is important to tell the service consumer which items were not

operated on and the reasons why. Efficient and consistent partial error

handling is a crucial principle that drives Teamcenters SOA Framework

and Business Logic Server as well as the client libraries and data model.

Using UGS Teamcenters SOA client-side libraries

Regardless of what specific language binding is used in the application,

developers perform the following consistent steps when they leverage

Teamcenters SOA client-side libraries.

Connection. The client application first requests a connection object,

which contains the parameters that can be used to connect to the server.

The SOA client framework instantiates the connection object and returns

it to the application where subsequently it can be used to invoke

appropriate services.

Authentication. Since Teamcenter is a secure environment, any service

invocation must be preceded by an authentication request. Successful

authentication returns a token that is used on all service requests across

the established connection. Teamcenters SOA supports all Teamcenter

authentication models, including single sign-on (SSO) and synchronized

LDAP.

Service invocation. Before invoking a service, the client application must

build the necessary input structures required by the service, as well as set

parameters on each item being input as part of the set-based call. Once all

of the data has been properly structured, it is passed to a service stub for

submission to the Business Logic Server.

Over-the-wire. The service stub works in conjunction with the SOA

Framework to marshal the service request into a REST XML document and

sends it over HTTP/S to the Web Tier.

Web Tier. SOA Framework forwards the request to an available/assigned

instance of the Business Logic Server.

Enterprise Tier. SOA Framework forwards the request to the appropriate

services skeleton, where the XML document is un-marshaled. Then, the

service endpoint or implementation is called and the services business

logic is executed. Once the business logics execution is complete, the

service skeleton marshals the results (including any information on

exceptions or partial failures) to a REST XML document and passes it back

through the Web Tier.

Web Tier. SOA Framework receives the service response and properly

formats it for an HTTP/S POST response.

Client framework. The service stub un-marshals the response, uses the

SOA Framework to process it into the Client Data Model (including anyerror information), and returns control to the client application.

Using UGS Teamcenters SOA

from WSDL-based applications

With just a few adjustments to the components, you can use the same set

of steps described above (in the Using UGS Teamcenters SOA client-side

libraries discussion) to invoke an SOA service from a WSDL-based web

services application. These adjustments include the following differences.

First, WSDL-based applications generally do not make use of the

Teamcenter client-side libraries. Instead, they use utility functions within

each of the major web services toolkits to automatically build the

necessary connection objects and input/output structures for a servicedirectly from the Web Services Description Language (WSDL). As you

might expect, tools such as Microsofts Visual Studio can greatly assist the

developer by reading the WSDL for a service and auto-generating the

necessary artifacts transparently.

Second, the only other difference between the REST and SOAP paths is the

entry point into the Web Tier. Unlike the REST entry points (described

earlier), the SOAP request is processed by the SOAP engine on the Web

Tier. The SOAP engine un-marshals the SOAP XML document and forwards

it to the Web Services endpoint that is auto-generated by Teamcenters

SOA Toolkit.

At the service endpoint, the request is marshaled to a REST XML

document and routed to Teamcenters Business Logic Server in the same

manner as the REST example described earlier. Information about whether

the request came through a SOAP endpoint or a REST endpoint is never

passed to the Business Logic Server. This practice helps ensure that service

innovations are always processed in the same manner regardless of what

type of client invokes the request.


10/12

8

With respect to the service response, the Web Service endpoint returns

control to the SOAP engine, where it is properly formatted for a SOAP-

over-HTTP response. Once the response is received, utilities in the web

services toolkit (i.e. in the toolkit is being used to build the client

application) un-marshal the response into structures directly usable by theclient application. Since the Client Data Model and the Data Manager

Model are part of the SOA Framework, no additional processing is

necessary for handling the business objects returned on the response.

Supported Configurations

Teamcenters SOA services are fully supported on all standard four-tier

Teamcenter deployments as discussed throughout this white paper. In

addition, Teamcenters SOA services also are supposed in Teamcenters

two-tierconfiguration sometimes used by Teamcenter users migrating

up from Teamcenter Engineering.

Two-tier deployments combine the Teamcenter client and a Business Logic

Server instance on each end-users computer; the shared database and file

stores remain on a centralized resource tier. Typically, this configuration

uses CORBA/IIOP communications rather than HTTP/S and eliminates the

Teamcenter Web Tier altogether. As a result, client implementations in this

type of deployment must use one of the supplied language binds rather

than a WSDL-based client implementation.


11/12

9

A final evaluation

A final evaluation

By applying an effective SOA to their PLM processes, companies can

support more business capabilities, reduce IT complexity and accelerate IT

implementation as well as re-use more applications (via web services)

and better align their PLM initiatives with other business activity.

Teamcenters SOA services provide a robust, flexible and highly-scalable

interface into your digital design and development processes and

their related information assets. The SOAs secure, WAN-friendly and

firewall-friendly attributes are especially appropriate for meeting the most

rigorous demands of both large and small companies.

On the technical side, Teamcenters SOA is a state-of-the-art

implementation that is based on and compliant with the latest industry

standards for web services interoperability. By adopting Teamcenter as the

backbone for your digital enterprise, you can immediately reap the benefits

of web services technology through an infrastructure that facilitates lower

cost of ownership, as well as greatly improved integration between your

business systems and the technical systems that power your product

design/development initiatives.

UGS PLM Software has initially focused Teamcenters SOA on the robust

capabilities and high performance required to deliver a core architecture

and service-based design capable of supporting both large and small

deployments. The services exposed by Teamcenters SOA cover a broad

range of Teamcenter functionality with particular attention to streamlining

your product design and development processes.

Future releases of Teamcenters SOA will add value to your organization by

exposing additional Teamcenter functions, supporting more language

bindings, invoking additional tiers in the Teamcenter stack and facilitating

interoperation with other external application offerings as these programsconverge toward accepted industry standards.


12/12

AmericasGranite Park One5800 Granite ParkwaySuite 600Plano, TX 75024800 498 5351Fax 972 987 3398

EuropeNorwich House Knoll RoadCamberley, SurreyGU15 3SYUnited Kingdom+44 (0) 1276 702000Fax +44 (0) 1276 705150

Asia-PacificSuites 3601-2, Citibank TowerCitibank Plaza, 3 Garden RoadHong Kong852 2230 3333Fax 852 2230 3210

RegionsDivision headquarters

United StatesGranite Park One5800 Granite ParkwaySuite 600Plano, TX 75024972 987 3000Fax 972 987 3398

About UGS PLM Software

UGS PLM Software, a division of Siemens

Automation and Drives (A&D), is a leading

global provider of product lifecycle

management (PLM) software and services

with 4.4 million licensed seats and 47,000

customers worldwide. Headquartered inPlano, Texas, UGS PLM Softwares vision is

to enable a world where organizations and

their partners collaborate through global

innovation networks to deliver world-class

products and services while leveraging

UGS PLM Softwares open enterprise

solutions, fulfilling the mission of enabling

them to transform their process of

innovation. For more information on

UGS PLM Software products and services,

visit www.siemens.com/ugs.

BE COMPLIANT GET OPTIMIZED GO GLOBALMOVE FASTER

Siemens and the Siemens logo are registered trademarks of Sie mens AG. UGS, Femap, Geolus, I-deas, JT, NX, Parasolid, Solid Edge, Teamcenter, Tecnomatix, UGS NX,UGS Solid Edge, UGS Teamcenter, UGS Tecnomatix and UGS Velocity Series are trademarks or registered marks of UGS Corp. or its subsidiaries in the United States andin other countries. All other logos, trademarks, registered trademarks or service marks belong to their respective holders. 2007 UGS Corp. All rights reserved.

UGS PLM Softwareleads to greater innovationThere is no single road to innovation, but there

are signs youre headed in the right direction.

Leading innovators get to market faster,

manage compliance, optimize resources and

achieve globalization. Theyre also four times

more likely to use PLM software to

plan, define, build and support their

products. UGS PLM Softwares family

of PLM solutions helps businesses

establish Global Innovation

Networks that transform their

process of innovation.

Drive your business to

greater innovation

and accelerate

your growth.

ugs - teamcenter's soa

Documents