Are You Technically Clean

1
Are You Technically Clean?

• Technical Purges and Routine Cleanup
• Session 30910

2
Who Am I

• Teri Fall
• Technical Team Lead
• ManageForce
• www.ManageForce.com

3
Topics

• Presentation key
• Why bother?
• Retention periods and clean-up cycles
• General clean up recommendations
• Technical clean up processes/procedures
• Questions

4
Presentation Key

• The tables that are used by the various reports
  and applications are list. Just because they are
  listed does not mean the report will delete from
  them, they may be used as a join in order to give
  you better data selection, processing options and
  output information. The table that will most
  likely be affected by the purge directly is the
  one that matches the purge. Example R9312 uses
  the tables F9312 and F0092, however it only
  deletes from F9312.
• This symbol means you will need to pay attention
  here things will break if you dont. It can
  also mean you need bring down the services.
• This symbol means environment specific so you
  are going to need to log into each environment.

5
Why Bother?

• Overall performance
• More efficient and effective troubleshooting
• Swifter root cause analysis
• Swifter incident management
• Effective problem remediation
• Peace of Mind
• Reduced production outages

6
Retention Periods and Clean-up Cycles

• What is a good retention period?
• days, weeks, months, years
• How often should I perform clean-up?
• Daily, weekly, monthly, yearly
• Should I run every purge every time?

7
General Recommendations

• Create and publish a retention and destruction
  policy
• Be sure you have a good backup prior to starting
  the clean-up process
• Keep a log book
• Create a maintenance plan
• Schedule your tasks

8
General Recommendations Cont.

• Create your own version of the reports being ran
• Keep your naming convention consistent and apply
  version security
• Be sure to promote through all environments
• Log into your development environment
• Most purge process can be ran from development,
  select few require you to be logged into the
  environment intended for cleanup

9
Submitted Jobs Clean-up

• Submitted Jobs Keeping the Submitted Jobs
  Master table limited to data from the past XX
  days
• Process
• R9861101 / R9861102 Job Master Purge
• PrintQueue Directory (script) Manual Purge the
  .PDF, .LOG and .CSV from the PrintQueue
  directory
• Tables
• R9861102 F9861101

10
Subsystem Jobs Clean-up

• Subsystem This helps to keep the Job Master
  table accurate by removing incorrect entries
  created by the subsystem
• Process
• Manually clear out old jobs running (waiting) in
  the JDE subsystem? These are the jobs that get
  added to JDE subsystem but always stay in a
  waiting status (this is normal)
• Database level script
• Tables
• P986116 F9860, F986101, F98611
• P986113 F986113

11
Scheduler Jobs Clean-up

• Scheduler This will help keep the scheduled job
  tables clean and speed up any queries touching
  these tables
• Process
• R91300A Print scheduler jobs
• R91300B Purges the completed scheduler jobs
  older then XX days.Check your Data
  Selection
• Remove any test scheduled setup for
  non-production environments
• Tables
• R91300B F91320

12
Work Center/Work flow Clean-up

• Work Center Purge- Purges the work center
  messages
• Process
• This is environment specific (Control
  Tables)
• R01131P work center messages/tasks
• R98860P work center processes
• Tables
• F01131 - PPAT Message Control File
• F01131M - JDEM Multi Level Message
• F01131T - Message Attachment Tag File
• F01133 - PPAT Message Text File
• R01131P F01131, F01131M
• R98860P F98860, F98865

13
OMW Clean-up

• OMW This will help keep the OMW application
  clean/organized and load quicker
• Process
• Promote all projects at status 38 to 01 Status
  38 means project has been moved to Production
  Status 01 means the project is complete
• R98222B - Purge default projects
• R98220A - to view all projects at specific status
• R98210B - Purge OMW Logging
• Tables
• R98222B F98222
• R98220A F98220

14
OMC Clean-up

• Verify and clean up your OMW configurations using
  the P98230 OMC.
• Process
• Remove any unused status
• Remove any unused transfer activity rules
• Verify allowed actions
• Verify constants
• Tables
• P98230 F98210, F98223, F98224, F98225, F98230,
  F9829, F983051, F98800

15
Package Builds Clean-up

• Package Builds This will help keep the package
  tables clean and conserve disk space
• Process
• R96225 - Package Build History R96225
• Package Deletions manually delete old packages
  from the Deployment Server, full and updates.
• R98825E/R98826E - Package Deployment Scheduling
• Tables
• R96225 F96215, F96225
• R98825E F98825
• R98826E F98826

16
Software Updates

• Managing ESUs/ASUs on the system.
• Process
• Apply ESUs/ASUs to Pristine Environment
• Remove OMW projects
• Remove packages
• Remove Database Data Sources
• Dont forget the Planner

17
Environment Path Code Maintenance

• Keep your environment clean and in synch with
  planner.
• Process
• OCMs P986110- Clear OCM of disabled mappings and
  old environment mappings
• R98611A OCM Comparison
• R9861130 Verify OCM
• R986101 to compare OCM between planner and system
• R986112 compare data sources
• Remove all old Data Sources both logical and
  database
• Remove any old environments and path code
• Machine Master remove old clients and servers
• R9650 remove machine based on update date

18
Environment Path Code Maintenance Cont.

• Tables
• R9650 F9650
• R986112 F98611
• P9654A F9650, F9651, F9654
• P986110 F9860, F986101, F98611

19
User Removal- Clean-up

• There are a lot of forgotten areas when it comes
  to user removal
• Process
• Disabled role/group
• R98222B - Clear the users default project
• Delete default projects (script)
• P98950 - Remove UO and Favorites (script)
• P00950 - User specific security
• P400951 - Business Unit Defaults
• P00241 Posting Rights
• P00095 Record Locks
• Default Printers
• P0092-LDAP user cleanup
• Tables
• R98222B F98222
• R90351 F9001, F9005
• R959212 F95921
• R95921 F95921

20
Security History

• Assuming you have security history turned on via
  the jde.ini and depending on audit requirement
  you can purge your security history table
• Process
• R9312 Purge security history
• Tables
• R9312 F9312, F0092

21
Log File Clean-up

• Log file Purge Delete all JDE, Jas, Http,
  Websphere, OAS logs
• Services need to be stopped
• Remove logs from App/Enterprise Server
• Remove Jas/WebSphere/OAS/HTTP logs
• Remove Broker logs
• Consider pointing logs to a central location
• Consider saving issue logs
• Check log filters server manager

22
Server Clean-up

• Purge/check Temp directories (script)
• Clear temp directories (including under documents
  and settings) check environment variables for
  additional temp locations
• Clear SQL packages(AS400)(services will need to
  be down)
• Purge Print Queue directories (script)
• Clear Print queue directories (WTS, Citrix, Web,
  Deployment Servers)
• Check your C root for JDE temp/work files
• Empty Recycle Bin
• Check disk fragmentation

23
Rebuild Cross Reference

• Rebuilding cross reference is very helpful for
  your developers and you when you need to look at
  impact.
• Process
• Path Code Specific (Central Objects)
• R98001 cross reference rebuild
• All Objects
• Individual Records Versions
• Custom Objects
• R980011B cross reference purge.
• Tables
• R980011 F9860, F9861
• R980011B F9860.

24
Post Clean-up Recommendations

• Surface Test all environments
• Verify you can log in
• Submit a simple UBE(R0006P) to server
• Open a few interactive applications
• Verify tables check and verify what you
  intended to remove is gone
• Build/Deploy a Full Production Package

25
Administrative Recommendations

• Ensure you have database and directory/library
  level backups
• Ensure you are backing up server manager/change
  assistant directories
• Standardize your inis
• Document, document, document
• Create save locations
• Ensure technical tools/reports are secured
  (R98403)

26
Purge and Archive Solutions

• Email for referenced scripts
• ArcTools
• http//www.arctools.com/home.htm
• PurgeIT from Klik-IT Ltd
• www.klik-it.co.uk
• Optim
• http//www.princetonsoftech.com/Solutions/index.as
  p
• ArchiveJinni
• http//www.solix.com/solix_enterprise_archiving.ht
  m
• Many more

27
????Questions????Session 30910

• For questions regarding this presentation
  contact
• Teri Fall tfall_at_manageforce.com
• For questions about ManageForce contact
• Phone [phone]
• Email tfall_at_manageforce.com
• info_at_manageforce.com
• Website www.manageforce.com