Evaluating PHP as a technology platform for SOA implementations

Vedanta Barooah

Hewlett-Packard Company

Evaluating PHP as a Technology Platformfor SOA Implementations

Introduction

• Myself:

� Hewlett-Packard (Consulting & Integration)

� Consultant for Open Source Services• Linux

• Middleware

• PHP, Scripting• PHP, Scripting

• Java/ J2EE (Learning… ☺)

• Enterprise Directories

• Databases

• Open Source Governance

� Systems and Network Infrastructure

� Past: Web Developer, System Admin

11-Oct-07 Evaluating PHP as a Technology Platformfor SOA Implementations

PAGE 2


• SOA and SOA @ HP

• The SOA Sandbox

• Component Evaluations

• Conclusions


PAGE 3

Why SOA? - The Business Benefits

• Reduce time-to-market for new products and services

• More revenue from better

• Reduce IT resource costs for maintenance

Increase agility

Reduce costs


PAGE 4

• More revenue from better operational capability

• More revenue from newly enabled capabilities

• Increase IT innovation spend

• Reduce costs related to providing new functionality

• Eliminate redundant systems and architectures

SOA – Technical Characteristics

• Abstraction of functionality into services

• Loose coupling

• Composition of new services

• Portable business logic • Portable business logic

• Interfaces are robust to change


PAGE 5

Example : Transaction Taxes in the Enterprise

Tax Calculation

ERP 1 ERP 2 Finance E CommBefore

11-Oct-07

USA Korea Brazil GermanyTax Reporting


PAGE 6

Example : Transaction Taxes in the Enterprise

Tax Calculation

ERP 1 ERP 2 Finance E Comm

Tax Calculation Service

After

11-Oct-07

USA Korea Brazil GermanyTax Reporting

Tax Calculation Service

Data

Warehouse


PAGE 7

Implementation

Business Application 1 Business Application N

BA Adapter BA Adapter

11-Oct-07 NAME OF THE SESSION COMES HERE PAGE 8

XML Router

Adapter Adapter

Tax Engine 1 Tax Engine N

Data Buffer

Data Warehouse

SOA @ HP – Why are we doing this?

• HP’s Adaptive Infrastructure Strategy

• Significant investments in SOA

• Technology agnostic – supports both Open

Source and commercial platforms

• Need for characterization of SOA Infrastructure • Need for characterization of SOA Infrastructure

Components

11-Oct-07Evaluating PHP as a Technology Platform

for SOA ImplementationsPAGE 9

Evaluation Criteria

Functionality •Feature set

•Relevance to test app

Adaptability •Programmatic APIs

•XML APIs

•GUIs

RAS •Reliability/Stability

11-Oct-07

RAS •Reliability/Stability

•(High) Availability

•Scalability / Performance

Manageability •Built-in management and monitoring functions

•Relevance to test app

Developments Tools •IDE support

•Other tools support

Cost •License costs

•Support/training costs


PAGE 10

The SOA Sandbox

What is it?

• A test and validation sandbox for SOA

infrastructure components

• A development environment and runtime

environment for web services and clients

• A demonstration environment

11-Oct-07 Evaluating PHP as a Technology Platform


• A demonstration environment

The SOA Eco System

Client 1 Client 2 Client N Client Layer



Service1 Web Services LayerService 2 Service 3 Service M

Infrastructure Components: Service Bus, Registry, Workflow/BPM, Security,

Management, etc.

SOA

Infrastructure

Components

Sample Application

“Quickloans” Banking Application

• Business Processes

• Server Components

• Client Components

• Web Services



• Web Services

• Commercial and Open Source Technologies

Business Processes

Start

Customer

Registration

Customer

Loan

Application

Customer Bank Manager Bank VP



Credit Score

Check

High Credit Score

Low Credit Score

Loan Approved

Manual

Loan

Approval

Logout

Stop

Technology View

VIEW CONTROLLER MODEL

Frontend (PHP)MySQL

LDAP

Reports (PHP)

Hibernate

JNDI

Web Services



Reports (PHP)

WAP (PHP)

PHP5 / SOAP

JNDI

Web Services

PHP

MySQL

C#

J2EE

Software Components

PHP5

SOAPSOAP

PHP5

NuSOAP

PHP

Credit Score WS

Autho

rization

WS

Registra

tion

WS

LoanA

pplica

tion

WS

LoanQ

ueryWS

LoanRep

orting

WS

Auto

LoanA

pproval

WS

Manua

lLoanA

pproval

WS

Mobile ClientFrontend UI (Customer UI & VP Reports)

XFire

Java

Manager Approve/ Reject UI



Business Logic

Hibernate

JNDI

SUN/BEA JVM

JBoss Web Services

NuSOAP

C#

ASP .Net

Credit Score WS

Autho

rization

WS

Registra

tion

WS

LoanA

pplica

tion

WS

LoanQ

ueryWS

LoanRep

orting

WS

Auto

LoanA

pproval

WS

Manua

lLoanA

pproval

WS

OpenLDAP Directory

MySQL Database

Core Application

SOA Evaluation Scenario

PHP

PHP UDDI

Service #1

Service #2


for SOA Implementations

PHP

PHP (WAP)

Clients

UDDI

Rule Engine

ESB

Service n

Component Evaluation

PHP Components

• Most web clients, reporting and mobile client

• Simpler web services in PHP

• Services written using NuSOAP and PHP5 SOAP

Extn

• Clients written in PHP5 SOAP extensions• Clients written in PHP5 SOAP extensions



Java Components

• JBossWS Web Services Library

• Web/EJB Container – JBoss AS

• Wrapper services

� Authentication / Authorization using LDAP

� Data access using Hibernate/MySQL� Data access using Hibernate/MySQL

• Tomcat / XFire for building Java client

• Used JSR-181 annotations to simplify coding,

auto-generate WSDL and XML metadata



Why PHP?

• Rapid development and debugging

(Compared to Java)

• Wide availability of libraries for integration and

extension (XML, String,… extensions)

• Many frameworks (Report Generation, Web • Many frameworks (Report Generation, Web

Services, Frontend, RAD, MVC)

• Lesser lines of code due to the dynamic nature

of the language

• Extensive API with custom extensions

• Popular language with a “not so steep” learning

curve



Java

Lesser LOC and Maintenance Effort

http://server/wsdl

User[ ] getUsers(role) # using PHP5 Soap$wsdl = “http://server/wsdl”;$input = array(role=>“admin”);$cl = new SoapClient($wsdl);$users = $cl->__soapCall(‘getUsers’, $input);var_dump($users);

PHP

WSDL tool•Proxy Class (stub)

11-Oct-07

var_dump($users);•Proxy Class (stub) •User class

Import ProxyImport User

Proxy p = new Proxy();User [ ] p.getUsers(“admin”);

Client.java


PAGE 23

PHP for Web Services

• Easier to create (compared to Java)

• Fewer lines of code

• WSDL generation on the fly

• Platform of choice when not integrating with

legacy systems.legacy systems.


PAGE 24

PHP SOAP Implementations

• PHP5 SOAP Extensions

• PEAR::SOAP

• NuSOAP

• Others



PHP5 SOAP

• Native PHP Extension

• Faster than any other PHP implementation

• Support - SOAP 1.1 , SOAP 1.2, WSDL 1.1

• Uses Gnome’s libxml

• Provides both server and client function• Provides both server and client function

• WSDL has to be hand crafted



Example : PHP 5 SOAP

Server



Client

PEAR::SOAP

• Part of the PEAR repository

• Written in PHP

• Provides both client and server functions

• Does not depend on any PHP extension

• Depends on Pear – Mail, Mail_Mime, Net_DIME, • Depends on Pear – Mail, Mail_Mime, Net_DIME,

Net_SMTP, Auth_SASL, Mail_mimeDecode

• Works with PHP 4



NuSOAP

• Written in PHP

• Works with PHP4

• Creates WSDL on the fly

• Provides server and client functions

• A class name clash with PHP5 soap• A class name clash with PHP5 soap



Sample Code: PHP WS (NuSOAP)



J2EE for Web Services

• Industry wide acceptance

• Stable, mature and scalable platform

• Integration with legacy applications

• Enterprise Features

� High Availability / Failover� High Availability / Failover

� Messaging

� Robust web services platform

� Business Process Management / Orchestration

11-Oct-07 NAME OF THE SESSION COMES HERE PAGE 31

PHP : Experiences so far

• Compact code – fewer lines compared to Java

• Reduced maintenance effort

• Fast code, test and debug cycle

• nuSOAP did not work with complex services

• Easy WSDL generation with nuSOAP• Easy WSDL generation with nuSOAP

• PHP5 SOAP extensions faster than nuSOAP



Java, C# : Experiences so far

• JBossWS simplifies web services creation

compared to old J2EE 1.4 model

• Annotations are easy, compared to XML

hacking

• Lack of in-depth JBoss documentation• Lack of in-depth JBoss documentation

• Visual Studio .net tooling is very flexible for C#

Web Services creation



PHP WS Clients : Best Practices

• Reuse – API, Extensions, Classes

• Wrap Consumer Classes – simplify objects

• Layer UI and Logic - use Template Systems and

MVC frameworks



SOA Infrastructure Components

• jUDDI - Registry

• HP SOA Manager (HP SOAM)



UDDI/Registry

• jUDDI used as a UDDI registry

• Eclipse WST to publish web services - Also works

for PHP web services

• jUDDI client API to query registry

• PEAR::UDDI client API to query registry• PEAR::UDDI client API to query registry

11-Oct-07

ws.apache.org/juddi/


PAGE 36

HP SOA Manager

• Management critical for all SOA infrastructure

components

• Ability to integrate into upstream enterprise level

management platform

• Monitors transaction counts and latency• Monitors transaction counts and latency

• Broker-based integration

11-Oct-07

www.managementsoftware.hp.com/products/soa/


PAGE 37

HP SOAM : Use Case

Client 1 Client 2 Client N Client Layer

11-Oct-07

Service1Web Services Layer

Service 2 Service 3 Service MEvaluating PHP as a Technology Platform


SOAM – Broker based integration

Client LayerClient 1 Client 2 Client 3 Client 4

11-Oct-07

Web Services LayerService1 Service 2 Service 3 Service M

SOAM Broker Services LayerBroker1 Broker2 Broker3 BrokerM


PAGE 39

SOAM – Experiences so far

• Seamless operation with Sandbox WS platforms

• Non-intrusive (no changes to WS required)

• GUI for creating proxy (broker) services

• Latency impact for broker based integration

• Run SOAM broker on the same machine that • Run SOAM broker on the same machine that

runs the web service to be monitored

� Risk of significant networking overhead impacting end-to-end processing times

• Use multiple broker instances for scalability and

high availability



Conclusions

Conclusions

• Open Source technologies for web services and web services clients are valid implementation platforms

• Open Source SOA infrastructure components are often API-centric and require custom coding for integration and user interfaces

• Commercial SOA infrastructure components provide for

11-Oct-07

• Commercial SOA infrastructure components provide for business process changes out of the box

• Interoperability between web services written in different languages is not always straightforward


PAGE 42

PHP SOA Components

• SOAP for PHP

� PHP SOAP Extensions (php.net/soap)

� PEAR::SOAP (pear.php.net/package/SOAP)

� NuSOAP (dietrich.ganx4.com/nusoap/)

� eZ SOAP (ez.no)

• Pear UDDI (pear.php.net/package/UDDI)• Pear UDDI (pear.php.net/package/UDDI)

• XML-RPC Toolkit (phpxmlrpc.sourceforge.net)

• Zend Framework (framework.zend.com)

• Blackbird ESB (blackbirdesb.org)

• Eclipse PDT, WST (eclipse.org)

• SDO (php.net/sdo)



Questions and Resources

• Questions?

• HP & Open Source (hp.com/go/opensource)

• HP & SOA (hp.com/go/soa)



Date post:	17-Dec-2014
Category:	Documents
Upload:	zubin67
View:	915 times
Download:	1 times

Evaluating PHP as a technology platform for SOA implementations

Documents