1. Report Distribution Report Distribution in PeopleTools 8.4 Doug Ostler & Eric Knapp 7264

2. Page 2 Agenda  What is it?  How does it work?  Key Features  Steps to setup

3. Page 3 What Is It?  Starting with tools 8.1, all batch processes are run on centralized servers  Infrastructure to allow reports and log files to be viewed in a browser  Allows reports to be shared by many users  Provides centralized and secure short-term storage of reports

4. Page 4 How does it work?  An extension of the Process Scheduler  Cobol is no longer required to run the Process Scheduler  Works with all supported batch environments  Distribution Agent  Companion process to the Process Scheduler  Transfers files to the Report Repository  Files can be transferred via HTTP(S), FTP or XCOPY

5. Page 5 Report Repository  Where the reports are stored  Reports are served up through a PIA web server  Multiple Process Schedulers can share a single Report Repository

6. Page 6 Architecture Database Application Server PIA Web Server PeopleSoft Application Server Batch / Reporting Server Process Scheduler Batch Process Batch Process Batch Process Output Report Repository PIA Web Server Distribution Agent

7. Page 7 Process Request Page  When scheduling a report, select ‘Web’ as the output type  Client is no longer an option  File and Printer are still available

8. Page 8 Process Monitor  The place you go to check to status of your scheduled process  Filter on: Server, Process Type, Process Name, Run Status, Time span, Process Instance and User ID (if you have access)

9. Page 9 Process Monitor  Detail page can be used to view reports or log files

10. Page 10 Report Manager  The place you go to access all of the reports you have security rights to see  New in PeopleTools 8.1  It’s expanded in PeopleTools 8.4  Explorer  List  Administration  Now under the “Reporting Tools” menu

11. Page 11 Report Manager, Administration  Renamed from “Report List”  Filter on: Status, Process Type, Folder Name, Most Recent, Process Instance

12. Page 12 Index Page  Replaces index page from 8.1  Translated for each user

13. Page 13 The output!  Can be viewed in Browser or downloaded

14. Page 14 Report Manager, Roles  The ReportAdmin role allows access to all reports in the report manager  The ReportSuperUser role allows a user update the reports that they have access to view  Delete report  Change expiration date  Update distribution list

15. Page 15 Report Manager, List and Explorer  Can show reports from multiple databases  Groups reports in folders  Powered by Integration Broker  Must have a Pub/Sub service running  Administration page only works on a single database

16. Page 16 Report Manager, List  Shows all of your reports in a list  Filter on: Folder, Name, Process Instance, Creation Date, Most Recent

17. Page 17 Report Manger, Explorer  Shows all of your reports in folders

18. Page 18 System Settings, Report Folders Administration  Folders are managed by a system administrator

19. Page 19 Window Output Type  Allows reports to be viewed as soon as they are done, without navigating to the Report Manager  All of the same capabilities of ‘Web’  Great for self-service

20. Page 20 Window Output Type  Achieved through a specialized web server  Same technology as Multi-Channel Framework  No code on the client  Not a ‘push’ technology, very low network load

21. Page 21 My Reports Paglet  Shows the most recently run reports  Delivered with the Portal Pack or Enterprise Portal  Configurable for number of reports and time span

22. Page 22 Distribution Lists  Reports can be distributed to Users or Roles  Distribution Lists can be added at run time or in the process definition

23. Page 23 Email Distribution  Emails report output to distribution list  Distribution list can be set at runtime or in Process Definition

24. Page 24 Email Link  When using web or window distribution, emails a link to the distribution list

25. Page 25 Output Types PrinterFileEmailWebWindow AE Crystal nVision SQR Query

26. Page 26 Most Report Distribution Issues stem from configuration!

27. Page 27 Common Issues  Blank Page Displays  Error 404 – Not Found  Signon Screen

28. Page 28 Configuration  Report Repository  Distribution Agent  Report Node Definition  Server Definition  Process Scheduler  configuration.properties  ReportRepositoryPath  FTP Service – Necessary for Unix to NT or OS390 to NT transfers

29. Page 29 Configuration – Report Node Definition What information do I need to configure a Report Node Definition?  Machine name of your Report Repository Webserver  Port number that your Report Repository Webserver is running on  Your PIA Location

30. Page 30 What the heck is my PIA Location?  PeopleSoft Internet Architecture  Your PIA Location is defined when configuring your webserver  Your PIA Location is shown in your PeopleSoft signon URL  http://machinename:PORT/PIALocation

31. Page 31 Configuration – Server Definition The Distribution Agent will not start unless a Report Node Definition is attached to a Server Definition.

32. Page 32 Blank Page Displayed We usually see this when using FTP to transfer reports. This indicates that the reports did not make it to the report repository.

33. Page 33 Blank Page Displayed – What to check!  Home Directory field in Report Node  ReportRepositoryPath in configuration.properties  Changes to FTP ID and Password  Permissions on Report Repository

34. Page 34 Error 404—Not Found Indicates a valid server connection. The reports have been transferred, but they can’t be viewed.

35. Page 35 Error 404—Not Found - What to Check!  Is the Report Node URL correct?  Verify machine name, Port, PIA Location  Operating System of the Report Server

36. Page 36 Signon Screen  This is not a bug!  Designed to authenticate the user ID  It will display until Single Signon is configured

37. Page 37 Signon Screen – What to check!  Is the local message node trusted?  Does the Report Server reside in the same domain as the other Webservers?  Be consistent with your machine names  AuthTokenDomain=.peoplesoft.com