®
1 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
The Application Long Tail
Situational apps form a long tail in the application space
WebSphere sMash is a platform for creating and running
situational applications
2 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
Speed, Simplicity and Agility
WebSphere sMash is an agile platform for developing, assembling
and executing web applications quickly and simply
Speed
Dynamic scripting languages
Convention over configuration
Pre-built services and templates
Simplicity
Browser-based composition tools
Visual tools for web page construction
Assemble for workflow scripting activities
REST architecture – simple ways to expose and consume services
Agility
Application-centric runtime (application is the server)
Runtime characteristics (clean, cost effective, short-lived)
3 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
Implementing Web Applications
WebSphere sMash is a dynamic scripting platform
Two scripting languages are supported:
Groovy for people that prefer Java
PHP for the 3 million (and growing!) existing PHP programmers
Java is positioned as the system language
Use Java for system extensions and application libraries
Entire applications can be written in Java, if desired
4 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
The PHP Engine
Why PHP in sMash?
Gartner predict that within 5 years 60% of 5.5 million PHP developers will
work in corporate IT (up from 13% of 3 million today)
Vast amounts of PHP available for search/copy/paste development
Wikipedia, Facebook, Flickr, Yahoo, phpBB, SugarCRM…
Why write a PHP engine in Java for sMash?
Dynamic languages + JVM = ♥
Excellent interop with any Java code!
http://php.net - the de facto standard PHP engine
Open source, written in C
Vast array of extension functions
String, image manipulation, LDAP, database and many more
5 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
Application Centric Runtime
WebSphere sMash is an application-centric runtime
You create an application and run it
You do not package and deploy applications to a server!
Each application runs in its own process (JVM)
Runtime is designed to be short lived
WebSphere sMash is a full stack runtime
Everything needed to run the application is provided by sMash
Including the Web server HTTP stack
An external proxy can be used for clustering
6 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
Runtime Characteristics
Instant On
Application available for service in less than 1 second
0.672 seconds on a MacBook Pro
Application JVM starts in about 1 second
1.3 seconds on a MacBook Pro
Clean
Graceful recovery, isolation, tolerates bad code
Short lived processes
Runs for fixed number of requests or idle timeout then restarts
No state lost on restart!
Cheap
Cost effective to run in small and large quantities
Idle application footprint ~380KB
Running application JVM ~28MB
7 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
Simple Deployment
Essentially the deployment is zip and copy
No machine specific information bound in the application
Default mode is shared dependencies
Application dependencies can be pre-loaded in repository of deployment
machines or pulled off the network if needed
Standalone mode is supported as well
All application dependencies are included in the ZIP
Nothing is needed on the target machine except a JVM!
Commands simplify creating ZIP files for deployment:
zero package for shared mode
zero package standalone for standalone mode
8 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
Connecting to SAP NetWeaver
9 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
Connecting to SAP NetWeaver
The SAP JCo JAR must be in the sMash
application lib directory (an update step
adds the JAR to the sMash application!)
There is a missing Java class in the SAP
JCo JAR (see next slide)
The main JCo class is imported into the
PHP application – this gives us access to
the createClient(…) method
The code is extremely naïve! It does not
use any connection pooling or single sign
on (the user name and password are hard
coded in the script)
10 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
Missing Java Class in the SAP JCo Library!
11 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
SAP Remote Function Call (RFC)
12 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
SAP Remote Function Call (RFC)
Script invokes RFC_SYSTEM_INFO
This RFC does not require have any
input arguments but they could also be
provided by the script if appropriate
The fields returned from the RFC are
formatted in a simple HTML table
As with the previous example, the
security is also extremely simplistic!
13 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
Deploying to Drupal as a Blog Post
14 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
Creating a New Story In Drupal
15 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
Set the Input Format to PHP
Blog posts are normally filtered HTML (for security reasons)
For this demonstration we create a PHP blog post
This requires the phpfile module to be installed
Drupal evaluates the PHP when it wants the post rendered
16 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
Copy and Paste the PHP
17 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
Finished Blog Post in Drupal
18 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash

®
19 © 2009 IBM Corporation
SAP NetWeaver and IBM WebSphere sMash