Jde e1 technical change mgmt
Download as PPT, PDF0 likes310 views
The document discusses EnterpriseOne technical change management practices at Cenovus Energy including maintaining multiple environments, managing a large number of custom objects and modifications, and processes for packaging, testing, deploying changes on a weekly schedule, and applying software updates and service packs. Standard practices include organizing custom objects by project, tracking all modifications, following change control processes for moving changes between environments, and conducting package builds and web generations on a regular schedule.
Jde e1 technical change mgmt
- 1. JD Edwards EnterpriseOne Technical Change Management Sue Shaw, Cenovus Energy Inc
- 2. EnterpriseOne Implementation at a company Change Management Rules Object Management Workbench Usage Package Schedule HTML Web Generation Tam File Management Software Updates Service Packs Q&A Agenda:
- 3. EnterpriseOne at a Company: Using JDEdwards (World A73) since 1994, live in 1995 On 4th release of OW - Xe live in July 2001 Approx. 4200 users, about 740 concurrent Using both Citrix and Web clients Running WebSphere on the iSeries Large IT support group for JDE & iSeries (50+) Over 800 years of JDE experience 7x24 Availability (one 6 hour outage per week) System i: 595 64-way, 512G main memory Application Service Provider for another company 170 remote sites, 5 time zones
- 4. Challenges we face: Coexistence Large databases. PD - 2 terabytes, F0911 with 545m records (500m arch) 250 Interfaces including 3 rd party and legacy integrations 45 environments for 10 pathcodes Pervasive use of modules, French language Many modifications. Over 800 so far, including C code Many E1 custom objects. Over 7500 so far. Some are clones of JDE code, some call JDE code 75 OW Developers 9 packages weekly – 4 DV, 4 PY, 1 PD
- 5. Change Management Rules: Keep pathcodes in sync everywhere No changes in PD pathcode directly Only PO changes in PY pathcode No Batch Version overrides No Web Versions anywhere – secure out Business sign off for PD moves Track all modifications carefully – QA Keep DV tidy Education of Developers, especially Contractors
- 6. Documentation Standards: Custom Application ‘Modified Objects’ (MO) for: Header to compare against for ESUs Detail with type: CBC Called by Custom Code CUS Custom Code EVO English Vocab Overrides FVO French Vocab Overrides MOD SCL Modification QUE Job Queue Change SAR JDE Code Fix UOV User Override Detail is Media Object linked to Word documents on the LAN with sufficient detail to redo from scratch Time Records for future retrofit estimates
- 7. OMW Project-Object Organization: In order to facilitate package builds and web generations, we ask the Developers to organize their objects into the following groups, by project: Tables – so global table tam files are rebuilt only when necessary Menus & Interactive Versions – no package build required Data Dictionary Items – DV/PY share Test DD and DD changes require DD tam file build All other object types UDCs and User Overrides are not maintained through OMW
- 8. Standard OMW Status Codes: 21 Programming 28 QA Complete 23 Build into DV Pkg 29 Move to Production 23S DV Pkg Assembly 30 Product Staging (Menus,IVs) 24 Objects in DV Pkg 37 Production Save 25 Move to Prototype 38 In Production 26 Transferred to PY 39 Objects in PD Pkg 27 Objects in PY Package 01 Complete,Release Tokens 21=>23 =>23S=>24 =>25 =>26=>27 =>28 =>29 =>30=>37=>38=>39=>01 Developers , CNC, QA , Business Approval
- 9. Other OMW Status Codes: 11 New Project 42 Xfer PY to DV 22 Build into Both DV & PY 43 Xfer Pristine to DV 37R Restore PDSAVE to PD 45 Pristine Get 38R Restored to PD 46 Prototype Get 40 Production Development 91 Cancelled 41 Xfer PD to PY 92 Cancelled - Pristine ESU These are all special case status codes. Developers can do 11, 22, 45, 46, 91. The rest belong to CNC.
- 10. Package Schedule 1: All controlled with OMW status codes Automated package assembly All Deploys are Mandatory JD – full package monthly DV – Monday through Thursday Updates Cut-off at 8:00am – status 22 or 23 Deployed same day at 12:00pm PY – Monday through Thursday Updates Cut-off at 10:00am – status 25 Deployed same day at 12:30pm Ready to test on web client at 1:00pm same day
- 11. Package Schedule 2: PD – Weekly Updates Cut-off at 9:00am on Fridays – status 28 (QA) Cut-off at 1:00pm on Fridays – status 29 (Business Approval) Objects transferred and package built Friday afternoon Deployed during IPL outage, Sunday 12:30 to 2:00pm Non-OL objects (menus & interactive versions) transferred to PD during Sunday IPL outage Emergency Packages possible but difficult DV, PY, PD – full packages quarterly Check In removed from Allowed Actions during DV Full Package
- 12. Web Generations 1: Bulk Gen file tied to Package Builds Package installed on eGen machine, Bulk Gen file specifies objects for generation CNC Controlled DV/PY – WebSphere recycled during noon outage PD – generated during Sunday outage WAS comes up at the end of the outage window
- 13. Web Generations 2: Data Dictionary Items require special treatment Updated TAM files on Gen machine Core, DDs, TBLEs, BSVWs, NERs, all Appls using DDs Learn how to look up things in your Serialized Object Files (F989998,F989999) Working on Access utility to review the gen logs Full Generations done with Service Packs to alternate Central Object libraries
- 14. TAM File Management (8.11 or earlier): Global Tables Triggered by update packages containing tables Deleted on the Enterprise Servers during Sunday outage Data Dictionary Developers can only do Jargon Codes Recorded in spreadsheet CNC does all adds and changes so they know when the DD tam files need to be built Built on request Recopied on the Enterprise Servers during Sunday outage
- 15. Miscellaneous Maintenance: The following should be cleaned up while EnterpriseOne is down: SQL Packages U* and QACX* files from QGPL Clear the F00095 Record Reservation File
- 16. Other Considerations: Vocab Overrides Invalidates Project-Object Ownership (modcmt) Do the VO change from the correct OMW project Blue arrow it out of your default project Check out and back in again in correct OMW project Avoid one client only options, ie menus CNC controlled table and index gens CNC controlled deletion outside of DV Custom BSFNs in custom DLL lib – H92/PL
- 17. Software Updates: Analysis prior to application Software Update Analysis Tool, Menu GH9612 No checkouts, no tokens, correct merge flags Apply to JD Assign tokens to hold objects while applying to DV All output is reviewed by CNC and Requestor Requester made owner on DV ESU created OMW project Treated as a regular project Developer looks after OMW objects, CNC’s Technical Change Coordinator does all other pieces 560+ ESUs applied, Updates and Baselines included
- 18. Service Packs: Separate Test and Prod iSeries so multi-foundation is easy For SP22_Q1 we learned how to split security properly Apply SP to Test iSeries Test for one week Apply SP to Prod iSeries No code transfers to PD during ‘SP test week’ Have set up new path code for true multi-foundation Done for SP23 due to difficulties in installation
- 19. Questions?