170 likes | 300 Views
Enterprise Integration Using Third Party Transformation. Session: 101960. Save the Date. APRIL 7-11, 2014 Sands Expo and Convention Center Las Vegas, Nevada. QuestDirect.org/COLLABORATE.
E N D
Enterprise Integration Using Third Party Transformation Session: 101960
Save the Date APRIL 7-11, 2014 Sands Expo and Convention Center Las Vegas, Nevada QuestDirect.org/COLLABORATE COLLABORATE 14- Quest Forum is THE source for PeopleSoft roadmaps & news. It matters where you register! All PeopleSoft education and events run through Quest
Agenda • Wells Fargo Profile • Our issue • Alternatives explored • IBM DataPower • Historical Path/Future Direction
Wells Fargo & Company • Wells Fargo & Company (NYSE: WFC) Wells Fargo & Company is a diversified financial services company providing banking, insurance, investments, mortgage, and consumer and commercial finance through more than 9,000 stores and more than 12,000 ATMs and the Internet (wellsfargo.com) across North America and internationally serving over 70 million customers. • We employ over 282,000 team members in more than 35 countries across our 80+ businesses • Current US population consists of • 265,000 full-time employees • 16,000 part-time employees • 1800 flexible employees
PeopleSoft Installations • MVS/DB2 platform • Initially installed PeopleSoft version 2.0 in 1993 (HR/Payroll/Benefits) • Multiple upgrades to 4.5, 6.0, 7.5, and 8.3 throughout the years • Upgraded to PS version 8.9 in 2007 • Upgrade to version 9.2 projected go live May 2014
Problem • Needed to publish an asynchronous message to MQ series for our identity management system (onboarding) • Integration with MQ for Asynchronous required large infrastructure support from PS team • WebLogic tweaks and MQ agents • Wells Fargo specific SOAP message – WFXML • PeopleTools doesn’t support external WSDL and XSD not generated by itself if producer of service
Alternatives • Create customized method to build WFXML • Didn’t allow for other formats • Methods created to do this, had to be maintained through tools upgrades • Mod to import different WSDL – needed to be maintained with tools upgrades • Worked okay with tweaking for each new service
Alternatives • Use PS delivered integration with JDeveloper to create XSLT • Clunky method, includes running an app engine as part of message • 3rd party transformation • Software to create XSLT and import • SOA device to do transformation • Wells Fargo already using DataPower
What is DataPower ? • An IBM Integration Appliance that provides security and integration gateway capabilities • Optimized High performance hardware, firmware, embedded OS • Easier and quicker configuration based development and administration • High speed transformation and processing using dedicated, hardware-based accelerators
PS/DP Integrations in Production • NRT(Near Real Time) publishing from PeopleSoft to OUI and IAM Subscribers via MQ • PeopleSoft Integration broker connects to DataPower via https and sends PS XML message. • DataPower Transforms the message to two WFXML messages and publish to OUI and IAM MQ topics respectively.
PS/DP Integrations in Production • TurboTax(Intuit) integration with PeopleSoft for real time retrieval of W2 • TurboTax(Intuit) sends OFX request to DataPower which it transform in to PS XML request and call the PS IB via F5. • W2 Response from PS was transformed to OFX and sent back to TurboTax
Historical Path • First project was to implement connection to MQ for Async message • Started to install MQ client software • Used PS delivered connectors • Started to realize ongoing cost of maintenance and special configuration needed • Discovered DataPower comes with built in hook to MQ (imagine that) • Used DataPower device to connect to MQ not for transformation, only had to change routing definition, no software installation • Insulated from changes to MQ
Historical Path • Fix for PeopleTools8.52 Bug • Internal service used WFXML • Upgraded to tool 8.52, missed testing service • Service started failing, discovered bug that put an extra SOAP envelope around the SOAP envelope • Changed to message through DataPower. DataPower stripped the extra wrapper. No code changes on either side. Connected to different end points. • First use of transformation capabilities
Historical Path • W2 OFX message • Used existing build of W2 online rowsets • Needed specific format for OFX standard • Using DataPower, could use existing code and do not have to maintain changes to standard in PS
Impacts to Future • DataPower now standard for all our external services. • Removing WFXML PS mod • Single communication point, allows for easier certificate maintenance etc. • All XML based messages will now use part message • Strips PSCAMA stuff out • Allows for cleaner XML out of PS • Can structure more like XML needed • rowsetbased – utilize existing skill • Experts doing the right work • Our DataPower staff is really good at transformation and communication services • Our PeopleSoft staff is really good at PeopleSoft • Integration with 3rd Party recruiting • Moving to a SaaS model for recruiting • 30+ integration points, all will use DataPower. • CI as a service • Anticipate use of this more extensively
Contacts • wayne.fuller@wellsfargo.com • (612) 667-4668 Please complete your evaluation: Session 101960 Thank you!