SAP Inside Track
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share

SAP Inside Track

  • 2,746 views
Uploaded on

These slides were presented at the London SAP InsideTrack event in April 2009. They walk through some of the key features of WebSphere sMash (Project Zero). ...

These slides were presented at the London SAP InsideTrack event in April 2009. They walk through some of the key features of WebSphere sMash (Project Zero).

The screen shots are from a demonstration of a PHP application integrating with SAP NetWeaver ABAP. A PHP script that invokes a SAP RFC is also deployed as a blog post within Drupal, the open source content management system.

More in: Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
2,746
On Slideshare
2,680
From Embeds
66
Number of Embeds
7

Actions

Shares
Downloads
51
Comments
0
Likes
0

Embeds 66

http://www.projectzero.org 42
http://jisi.dreamblog.jp 10
http://www.slideshare.net 5
http://www.linkedin.com 4
http://www.slashdocs.com 2
https://www.linkedin.com 2
http://www.slideee.com 1

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. ® 1 © 2009 IBM Corporation SAP NetWeaver and IBM WebSphere sMash
  • 2. ® 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
  • 3. ® 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
  • 4. ® 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
  • 5. ® 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
  • 6. ® 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
  • 7. ® 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
  • 8. ® 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
  • 9. ® Connecting to SAP NetWeaver 9 © 2009 IBM Corporation SAP NetWeaver and IBM WebSphere sMash
  • 10. ® 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
  • 11. ® Missing Java Class in the SAP JCo Library! 11 © 2009 IBM Corporation SAP NetWeaver and IBM WebSphere sMash
  • 12. ® SAP Remote Function Call (RFC) 12 © 2009 IBM Corporation SAP NetWeaver and IBM WebSphere sMash
  • 13. ® 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
  • 14. ® Deploying to Drupal as a Blog Post 14 © 2009 IBM Corporation SAP NetWeaver and IBM WebSphere sMash
  • 15. ® Creating a New Story In Drupal 15 © 2009 IBM Corporation SAP NetWeaver and IBM WebSphere sMash
  • 16. ® 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
  • 17. ® Copy and Paste the PHP 17 © 2009 IBM Corporation SAP NetWeaver and IBM WebSphere sMash
  • 18. ® Finished Blog Post in Drupal 18 © 2009 IBM Corporation SAP NetWeaver and IBM WebSphere sMash
  • 19. ® 19 © 2009 IBM Corporation SAP NetWeaver and IBM WebSphere sMash