ITANA - WSO2 Follow Up Discussion - Nov 19, 2013

Attendees:  Aws Al-Attar, Joel Banez, Glenn Donaldson, Ashish Pandit, Dave Perhne, Jon Terrones

UMICH - Dave Perhne and Aws Al-Attar

    WSO2 Status:

  • Went through WSO2 Implementation of API Manager/ESB/Data Services via Quick Start.  Picked use case and went through implementation via Quick Start.  
  • UMICH had needs for custom security mediation and was able to have WSO2 assist in development, specifically mapping to their identity provider
  • WSO2 was able to patch during Quick Start.  25K
  • WSO2 Developers took tasks back to WSO2
  • if had to do it again, would be more specific of defining use cases, too generic.  Can share use case doc
  • API Manager had an issue with Javascript injection
  • UMICH - live last Friday

    Take aways from WSO2 Con:

  • Focus on Developer Studio and it's deployment practices seems to be the preferred methodology for integration work, i.e.  migrate proxy services into Dev Studio

    Followup question:

  • Curious about who is currently working with security mediations to PeopleSoft


UCSD - Ashish Pandit

    WSO2 Status:

  • WSO2 implementation via Quick Start

    Take Aways from WSO2 Con:

  • Limitation of Development Studio:  
    • No visual data mapping?  
    • In testing, did not see a solid unit testing capabilities.  Talked to WS02 product manager and they are aware of that
    • No step by step debug tools.  On WSO2 agenda.
  • Liked AppFactory Demo.  Potential to manage the app life cycle and customers via that application

Westmont - Joel Banez

    WSO2 Status:

  • Currently in consideration


  • Did UMICH feel that they got enough out of Quick Start.  Yes.
  • Dave P. mentioned that next time they would have examined more complex/detailed use cases
  • Anyone using any of the SalesForce connectors?  No.

OSU - Glenn Donaldson

  • Interested in whether or not people have added a layer of abstraction to their Peoplesoft services using WS02.  
  • No one currently using WSO2 in that manner, but we talked a bit on the fragility of not doing this layer of abstraction.


  • Follow up question after Google Hangout re: what people are planning on doing for support structure.
    • Can you share your current or planned support model, staffing roles & numbers for your WSO2 deployment?
    • What unit/department is the support in?  Is this part of your project request flow?
    • Do you have a business case for ESB or SOA that you can share?

UW Madison - Jon Terrones

    WSO2 Status:

  • Test infrastructure of ESB and Governance Registry cluster deployed.  Build out of production infrastructure underway.

    Take Aways from WSO2 Con:

  • Interest in WSO2's new campus in Bloomington, IN for support purposes
  • Liked App Factory's ability to assist in the entire software development lifecycle
    • Takes away burden of provisioning source code management, issue tracking, run time environments, etc.
    • Hit home with the amount of time it takes to provision infrastructure here at DoIT
    • Provides a store like facade for promoting apis to customers
  • Deployment techniques
    • Use of Hazelcast for cluster management
    • Dropping of registry based deployment sync in favor of SVN
  • Interesting partnership with cloud dev community/codeenvy. 
    • Basically WSO2 specific tooled Eclipse in the cloud. 
    • Minimizes time to development for developers who struggle with building out their development environment dependencies and configuration.
  • Support
    • WSO2 doesn't care if you run without support
    • Maintains that serious customers will benefit
    • Immediate fixes

Future:  Once a month meetings via Google Hangouts or similar.

  • Discussion to continue around everyone's WSO2 implementation efforts.
  • Further discussion needed on support structure to address Glenn D's questions.
  • No labels