JDE & Peoplesoft 1 _ Michael Plon _ JDE EnterpriseOne in the big bad world of SOA.pdf

The most comprehensive Oracle applications & technology content under one roof The most comprehensive Oracle applications & technology content under one roof

JD Edwards in the Big Bad World of SOA

Michael Plon Jonathan Fuller

Oil Search Limited

The most comprehensive Oracle applications & technology content under one roof

Oil Search Overview

•  An oil and gas produc;on, development and explora;on company opera;ng in Papua New Guinea since 1929

•  Par;cipant in the $US 15 billion PNG LNG Project with ExxonMobil with target first LNG sales in 2014

•  1,100 full;me staff and over 1,500 contractors in mul;ple loca;ons

•  Market capitalisa;on of $US8.28 billion, 2011 first half revenue of US$371.1 million

•  Oil Search’s vision is to be an acknowledged leader in oil and gas explora;on and development in developing countries


Oil Search Opera;ons


Reasons for JD Edwards EnterpriseOne v9 Upgrade Completed 11/2010

•  Access to business services •  New and improved func;onality •  Oracle BI Publisher •  Extended Applica;on Cer;fica;on •  Broader pla]orm cer;fica;on for JD Edwards EnterpriseOne tools

•  Cer;fica;on with Oracle Fusion Middleware •  Compatability with Oracle Applica;on Integra;on Architecture (AIA)


What is SOA?

Traditional Architecture

Standards

IEEE1394

HDMI

PAL

RCA

SCART

Component Based Architecture


Oil Search Applica;on Architecture •  Re-‐usable services are the basis of Oil Search systems which

will be “connected” to compose “end to end” processes •  Stop doing point to point integra;ons and think

architecturally •  3rd party applica;ons are to be configured not customised,

where possible. Customisa;ons will be implemented as business services that interoperate with 3rd party applica;ons, where possible

•  All 3rd party applica;ons to be implemented must have the ability to consume and publish web services

•  “Buy and integrate” versus “build”


Oil Search’s SOA Strategy


Example Integra;on Without Business Services

•  Integra;on of Lotus Domino invoice rou;ng solu;on with JD Edwards

•  Based on popula;on of “Z” tables in JD Edwards

•  Developed to replace manual process •  Inten;on to reuse solu;on as other Oil Search systems need to integrate with JD Edwards in the same way


How The Integra;on Was Built


Benefits Realised from Integra;on •  Elimina;on of duplicate data entry and associated reduc;on in data entry errors

•  Resource savings of 384 hours per month allowing resources to be redeployed

•  Increased visibility of where supplier invoices are in the payment process reducing AP enquiries

•  Improved control over and repor;ng on the supplier invoice approval and payment process

•  Improvement to a “broken” process

•  Link between JDE and internally developed system for transac;on drilldown

•  Further proof for Oracle SOA Suite as a middleware pla]orm


JD Edwards in a SOA World

The JD Edwards EnterpriseOne implementa;on of a SOA approach provides a standards based pla]orm that allows business services to be developed, published, discovered and consumed by each other in a loosely coupled way in order to facilitate the crea;on of orchestrated business processes.


JD Edwards in Oil Search’s SOA Environment


JD Edwards Business Services •  Business services are objects that enable interoperability between JD Edwards EnterpriseOne and third-‐party applica;ons and systems or other Oracle applica;ons

•  Business services enable soiware applica;ons that are wrijen in various programming languages and running on various pla]orms to exchange informa;on

•  Approximately 70 pre-‐built business services are now delivered with JD Edwards EnterpriseOne


Available Business Services


Benefits of Business Services

•  Improved interoperability through standards based technology

•  Simplified integra;on architecture •  Fusion Path – the current direc;on of Oracle’s next genera;on applica;ons is based on this architecture offering a simplified migra;on path to these applica;ons should that be the chosen pla]orm, in the future, for an organisa;on’s enterprise applica;on


JD Edwards Business Services – Technical Implementa;on

•  Steps to selng up and invoking a JD Edwards Business Service – Terminology – Oil Search E1 Environment –  Install Business Services Server – Build and Deploy a E1 Business Service –  Invoke a Standard E1 Business Service – Develop a Custom E1 Business Service


JD Edwards Business Services – Technical Implementa;on (cont’d)

•  Terminology •  E1 Business Services -‐ includes the capabili;es to develop (Java-‐based business func;ons), publish, consume, and administer Web services directly from JD Edwards

•  E1 Business Services Server – J2EE server that allows E1 to produce and consume web services

•  WSDL -‐ WSDL is a document wrijen in XML. The document describes a web service. It specifies the loca;on of the service and the opera;ons (or methods) the service exposes

•  SOAP -‐ XML-‐based communica;on protocol to let applica;ons exchange informa;on messages over HTTP



•  Environment –  IBM iSeries 550 running JD Edwards Enterprise server and database

– Windows 2008 64 bit running Weblogic 10.3.2 –  JD Edwards E9.0.1 with Tools Release 8.98.4.2 – Server Manager 8.98.4.2 running on Deployment Server.



•  Install a Business Services Server –  Install Jrockit 1.6.0.17 –  Install WebLogic 10.3.2 64 bit



•  Installing a BSSV Server (con;nued) – Configure E1_Apps WebLogic domain –  Install JD Edwards Server Manager Agent



•  Once Server Manager can communicate with the managed agent it should appear similar to below.



•  Installing a BSSV Server (con;nued) (Next steps are all done in JD Edwards Server Manager) – Register the new WebLogic server – Create a J2EE Server (WebLogic Managed Server ) – Create an EnterpriseOne Business Services Server managed instance.



•  Build and Deploy a Business Service – Webdev feature must be working on your local fat client.

–  Jdeveloper must be installed –  ini file configura;on [MTR VALIDATION] and JDBC drivers must be available



•  Build and Deploy a Business Service (Con;nued) –  Make sure to include at least one published BSSV object in the

Business Services Assembly Applica;on –  In the package build defini;on for a Business Services package,

under build loca;on the Client op;on must always be selected –  Once the package has built review the build logs ..package_Name

\work\sbf\wls\wls_BusinessService.log –  Server Manager access ( The E1 user account that you use to

deploy the package needs to have access to server manager ) ( 'viewGroupMembers' and 'webProductInstance' )



•  Build and Deploy a Business Service (con;nued) –  Once the Package is deployed to the business services server the

managed instance can be started. –  In WebLogic you can verify that the BSSV applica;on has been

deployed



•  Note you can see the current package deployed to the Business Services Server in Server Manager



•  Calling a standard E1 Business Service – To use Business Services with WebLogic the SSL port should be enabled (WLS only allows hjps protocol to ‘consume’ Business Services’)



•  Grant the E1 user that will be calling the business service access in Security Workbench to the published BSSV.



•  Invoke a business service via SOAPUI –  First get the path to the Business Service WSDL. The loca;on can

be found in WebLogic.



•  Open soapUI and create a new project



•  Create a new request to getAddressBook Details. By default it will look like this.



•  Add in the required soap header to pass in username and password

•  <soapenv:Header> <wsse:Security xmlns:wsse="hjp://docs.oasis-‐open.org/wss/2004/01/oasis-‐200401-‐wss-‐wssecurity-‐secext-‐1.0.xsd" xmlns="hjp://docs.oasis-‐open.org/wss/2004/01/oasis-‐200401-‐wss-‐wssecurity-‐secext-‐1.0.xsd" xmlns:env="hjp://schemas.xmlsoap.org/soap/envelope/" soapenv:mustUnderstand="1"> <wsse:UsernameToken xmlns:wsse="hjp://docs.oasis-‐open.org/wss/2004/01/oasis-‐200401-‐wss-‐wssecurity-‐secext-‐1.0.xsd" xmlns="hjp://docs.oasis-‐open.org/wss/2004/01/oasis-‐200401-‐wss-‐wssecurity-‐secext-‐1.0.xsd"> <wsse:Username>JDE_LOGIN</wsse:Username> <wsse:Password Type="hjp://docs.oasis-‐open.org/wss/2004/01/oasis-‐200401-‐wss-‐username-‐token-‐profile-‐1.0#PasswordText">JDE_PWD</wsse:Password> </wsse:UsernameToken> </wsse:Security> </soapenv:Header>



•  Execute the request and review the result



•  Another example -‐ getItemAvailability



•  Result -‐



•  Develop a Custom Business Service to call a JD Edwards Business Func;on



•  Develop a Published Business Service to call a Business Service



•  When checking in a Published Business Service remember to set the publish op;on. (When this is built it appears as a published business service that can be called)


Any Ques;ons?

JDE & Peoplesoft 1 _ Michael Plon _ JDE EnterpriseOne in the big bad world of SOA.pdf

Documents

Transcript of JDE & Peoplesoft 1 _ Michael Plon _ JDE EnterpriseOne in the big bad world of SOA.pdf