1. Denise Luther Senior IT Consultant denise.luther@cistech.net Practical Technology Enablement with Enterprise Integrator

2. Denise Luther Professional Experience 30+ Years in Information Technology 5 Years XA Experience Software Design and Development MAPICS Expertise Enterprise Integrator Trainer Technical Strategies for working with XA Recent Customer Success Saia-Burgess – Implemented custom supplier web portal using Enterprise Integrator and System-Link My technical background in the iSeries/XA environment allows me to help IT professionals implement new technologies for continued business success.

3. Agenda Data Sources Transaction Broker Transaction Objects Host Jobs and Reports Header/Detail Relationships Managing Environments Add polish to your applications

4. Data Sources Other Platforms Files on another iseries Files in another XA environment

5. Acquire drivers from the database provider Place them in /MAPICS/driverlib IFS directory where MAPICS is installed They will work for all environments Drivers are no-charge and can be downloaded from the web Data Sources - Drivers

6. iSeries – already installed Access – already installed SQL Server – SQL Server Driver for JDBC Oracle – need 9i driver PostgreSQL – need driver for JDBC3 Platform Data Sources - Drivers

7. Data Sources – SQL Drivers

8. Data Sources [dsh]:[port] Database [Password] [user ID] Database owner

9. Data Sources

10. Display SQL Server Views, subsets, sorts Full navigation Navigation history Workbenches Code files Graph cards Compound cards Attachments Column functions

11. Navigate to SQL Server table

12. SQL table from within an object Show data in context Cards can be external data sources Drill-down capability across platforms

13. Transaction Broker User Exit Code Generation No source downloads More control More Exits Consistency Exported with object Enterprise Integrator extends these advantages to your custom objects (no more triggers) Generate program Compile program Display Compile listing

14. User Exit Source

15. Transaction Objects Transaction vs. object maintenance –Think IM transaction vs. Item Warehouse maintenance Action on a menu Like IM transaction… –Has own attributes separate from object –Has own logic separate from object –Can update multiple objects

16. Transaction Objects Item Warehouse Maintenance Create, update or delete an item warehouse record Logic applies to database fields RM Inventory Transaction Data is not part of MO or Item Warehouse objects –Where is Quantity stored? Logic is not part of an order object –IM transactions have unique edits –Doesn’t make sense to include logic in MO or Item Warehouse maintenance Update applies to many objects

17. Transaction Objects Need to be able to transfer inventory from one location to another. Allow user to select Item Location records by subset or individual selection, enter the To location, create TRDATA TW transaction record and kick off the PMC process. Secure this function and authorize selectively

18. Transaction Objects

19. Transactions card in object card file Don’t select a maintenance ID, just click Create

20. Transaction Objects Name entered will be default menu text

21. Transaction Objects Card file like Business objects but is independent of Standard actions

22. Attributes Used to send information to user exits

23. Edits Edit to require entry for To Location

24. Relationships Provides search for location entry

25. User Exits User exits structured like standard exits

26. User exit source to process the transfer User Exits

27. AftEXT0043TXN – code to create TW TRDATA record User Exits

28. CLOFIL – Send dataq to process transfer User Exits

29. Select row(s) for transfer Click the toolbar button to execute the transfer Run Time

30. Popup will ask for Transfer To Location Search provided to lookup valid location Run Time

31. Enter or select location and click continue User exits will process the TW transfer Process from buffer runs from client Run Time

32. Secure the action To lock down this action independently of the standard maintenance, Lock and authorize the Task/Subtask Client Extension Object Security Area

33. Replacement for Program actions Allows creating attributes date sub-type – forces valid date entry Discrete domain/Code files Standard edits Custom edits for error reporting Default data generation Search functionality (relationships) Process from buffer user exit – code that would normally in the program action host program Object transactions

34. Host Jobs and Reports Host Reports and Host Jobs are processes that are invoked from the client to run on the host Host Reports typically read data from the server and print a report based on that data PO Print Host Jobs typically perform work that alters data on the server PO purge Add custom Host Reports and Jobs to Business Objects

35. Adding Host Reports Select the Host Processes card and the Reports sub-card

36. Enter the name of the host report on the Create Business Object Host Report prompt This is the name that appears on the Host Reports tab Adding Host Reports

37. General card contains information about the Host Report

38. Attributes Create “attributes” using the Attributes card Appear as options when the user runs the Host Report

39. Edits Standard Integrator - define simple edits on single attributes EI - define Custom edits that will be processed by the server using the Validate user exit

40. Relationships Enable the users to lookup values instead of directly keying them

41. User exit programs can be generated and compiled like user exit programs for other types of Business Objects User Exits

42. Host Reports are executed from the Host Print option on that object’s File menu List of the available reports for that object positioned alphabetically in the list of available reports Attributes that were created in Integrator for the report will show as options (currently in alphabetic order) for the report Name attributes to control order in run-time list Host Reports

45. Email Same confirmation and email notification available

46. Adding a custom Integrator Host Job to a Business Object is done in the same way as a Host Report Use the Jobs tab on the Host Process tabbed card. Attributes, relationships, and edits are added in the same way as a Host Report User exit programs are the same Host Jobs

49. Host Job are executed using the Host Job option on that object’s File menu Host job will show up as one of the available jobs for that object in alphabetic order Attributes that were created in Integrator for the report will show up as options, currently in alphabetic order, for the job Using Host Jobs

52. Business Object Host Reports/Jobs require some CAS host records in order to correctly process transactions Created and maintained automatically during a save to host Security authorization record to limit who has access to run the custom Host function Security class = ‘REPORT’ or ‘JOB’ Security category = EXTxxxxRPT (Host Report) or EXTxxxxJOB (Host Job) xxxx=extension for host process Client Extension Object Security area of CAS Area and task authorizations Host Records

53. “Process buffer” user exit –Host process runs in batch –Transaction object runs in client Process multiple records –Host process presents attributes (options) once –Transaction object presents attributes for each selected records (like quick change) Run-time execution –Host process run from File menu option –Transaction runs from toolbar button Host Process–Transaction Differences

54. Header/Detail Relationships Special 1 to Many relationship Create custom detail type relationships between user defined header and detail objects

55. Copy transaction copies both header and details Delete transaction deletes both header and details Locking header locks corresponding details Allows detail objects to be created and validated at the same time as the header Transactions for changed detail objects include changed header fields in TRNDTA for use with user exits Available for overview cards Header/Detail Relationships

56. Primary object type Transaction Broker/None Maintenance Methods Detail business object must have the same keys in same order as the header, plus any extra key fields Header can have multiple detail business object relationships Rules

57. Project Tracking Start project tracking from Enterprise Object Maintenance Card Maintenance History

58. Project Tracking Create a project for each application or series of object maintenance

59. Project Tracking Select a project each time you save to host Maintenance history records tells what changed Project tied to the maintenance

60. Project Tracking

61. Improved management for environments Import/Export individual objects Use subsets or selected records to limit export

62. Presentation Schemes, Attributes Colors, Bold Fonts Lower Case

63. Compound Cards Combine multiple cards, views onto one card Only contains what user needs to see Customize Titles and Banners Use appropriate icon and toolbar buttons

64. Thank You! Technical Information Denise.Luther denise.luther@cistech.net 704-814-0017 Sales Information Ben McCormick ben.mccormick@cistech.net 704-814-0016