(ats3-dev07) web service delivery with the accelrys enterprise platform

(ATS3-DEV07) Pipeline Pilot as a Web Service Delivery Platform

Mike PeelerSenior Director, Platform R&Dmichael.peeler@accelrys.com

The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision.

• Context: Pipeline Pilot Clients• Pipeline Pilot Protocols as Web Services– Parameter-centric– Document-centric

• Client Libraries• SOAP Services• RESTful Services

Agenda

Pipeline Pilot Integration Points

DBs

Pipeline Pilot Enterprise Server

Protocol Runtime Environment

VB Script (On

Client)

Run Program Java Perl Python

VB Script (On

Server)

Admin Portal Help PortalWeb Apps Web Services API

.NET SOAP & HTTP

Telnet / FTP SSH / SCP ODBC /

JDBC

VB Script Cmd Line Java Classes

Perl Scripts

.NET Classes

RESTService

SOAP Service Cmd Line

Server IntegrationExtend pipelines with new components that integrate your code, data and services.

Professional Client

Run Protocol Command Line

Client

Web Browser

Web Port

JavaScript Client SDK

JavaScript Client

.NET Client SDK

.NET Client

Java Client SDK

Java ClientSOAP Client

Client IntegrationBuild clients that connect to Pipeline Pilot and run protocol services.

HTTP Client

Client Interfaces & Application Integration

Pro

Web Port

Web Part

SharePoint & JSR-168 Portals

Client Written with .NET, Java, etc.

Leve

l of C

usto

miz

ation

User Scale and Scope

Personal Productivity

Workgroup

Enterprise

Brid ge

Accelrys

Third-Party

SOA

Http

SOAP APIs

Web Services API & Client SDKs

XMLProtocolDatabase

Java SDK

Allows cross-platform access to Pipeline Pilot services

Java Servlets, JSPJava Applications

.NET Applications

Web Applications

Perl SOAP::Lite & other SOAP libs

JavaScript SDK

.NET SDK Pipeline PilotServer

Browsers, Http Clients

Client Server

Authentication Layer

• Mapping protocols to Web Services– “Visual” Services– Parameter Style– Document Style

Protocols as Web Services

• “Visual” service• Parameter-style protocol

– Protocol web service settings

• Document style protocol

Demo

SOAP Services

• WSDL generation for parameter style – Inspect Web Service• WSDL-first for document style• Protocol & Folder versions• Security

• Inspect Web Service• Working a protocol SOAP service from

SoapUI

Demo

• Common client object model• .NET• Java• JavaScript

Client SDK Libraries

Client SDK Object Model

Pipeline Pilot Server

Pipeline Pilot Session

Job

Component Database

XmldbItem

0..1

*

ComponentInfo

ParameterInfo

1

*Job Result

Job Status

1

*

1 1

1

0..1

11

1

1Pipeline Pilot Server Config

Remote File Manager

1 1

1

1

1

*

• Calling a protocol from .NET client• Help Center – Client SDKs

Demo

• Beyond the CGI model• Representational State Transfer• Typically pass documents (eg XML, JSON) between client

& server that represent state of a resource• Uses existing verbs rather than creating arbitrary function

names – GET, PUT, POST, DELETE• Resources identified by URI, so URI mapping required to

underlying functions

RESTful Services

• Working a protocol service from REST browser plugin

Demo

• Client SDKs wrap server web services• Various styles of protocol execution via Web Services

– Parameter-centric/Document-centric– Fixed/Predefined WSDL– Blocking/Polling– Security models– SOAP/REST

• Developer Section of Help Center– Client Side Integration

Summary

The information on the roadmap and future software development efforts are intended to outline general product direction and should not be relied on in making a purchasing decision.

For more information on the Accelrys Tech Summits and other IT & Developer information, please visit:https://community.accelrys.com/groups/it-dev