Practical Technology Enablement with Enterprise Integrator

1. Practical Technology Enablement with Enterprise Integrator Denise Luther Senior Consultant, Technical Services Denise.Luther@cistech.net

2. Auto Content Security • Special attribute classes are assigned • On-the-fly security subsets based on values assigned to a user • Global across all objects • User can be setup to view all warehouse data but only allowed to maintain data in certain warehouses

3. Auto Content Security

4. Auto Content Security Assign warehouse values for this user Turn Maintenance on or off by warehouse

5. The subset is still (all records) i.e., all the records this user is authorized to. They can still subset from here. Using a security subset Only warehouse 1 records appear in the list

6. Deployment Profiles • Object/field assumes everything authorized • Deployment Profile assumes nothing authorized UI What the user chooses to see Deployment Profile What is presented to the user Object security What user is authorized to Database All objects and attributes

8. Deployment Profiles

9. Object list • Content • Object list • Content • Navigation • Object list • Content • Navigation • Maintenance • Object list • Content • Navigation • Maintenance • Fields • Object list Deployment Profiles

10. Security for: Powerlink

11. …and Security for: Netlink

12. …and Security for: System-Link

13. PO P012345 for $11,283.19 needs approval Alerts – Integrator Subscriptions • Via e-mail, cell phone text or system message • Can also run a program ERP

15. Alerts – Integrator Subscriptions NMS must be started

16. Data Sources • Other Platforms • Files on another iseries • Files in another XA environment • Install Drivers in IFS

17. Data Sources • Create the Data Source – server location, login • Build objects the normal way

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

19. Enterprise Integrator User Exits • Create custom applications in Power-Link • Modernize existing or 3rd party applications • Common interface for user • Write your business rules • Users can perform host processes • Email, lists, on the fly analysis information, • System-link requests • Exported with object

20. Enterprise Integrator User Exits • Create Custom Applications

21. Generate program Compile program Display Compile listing Enterprise Integrator User Exits

22. Enterprise Integrator User Exits • Want to do embedded SQL in user exits? • Change the Call Program type (may need to add to the card)

23. Object Transactions • Processes outside normal business object flow • Better way to do Program actions • Requires EI • Transactions Card in Integrator • Parameters defined as attributes • Edits • Default generation • User Exits

24. Object Transactions • Toolbar button to execute • Unique set of user exits

25. Object transactions • Attribute (Number of copies) is required entry • Update User Exit calls the host print program • Edit User Exit – Required value for Number of copies

26. Logical Transactions • Subset of Standard Transaction • Create, Change, Copy, Delete, Mass • Allows for one click update or prompt user • Use template to supply data

29. What is System-Link? • Program to program interface between XA and other systems. • Inquiry/Maintenance • Replacement for offline load • XML • Other ERP systems • Other platforms • Part of Power Architecture • CSM, PM, OBPM, EPDM, MM… • CO’s, PO’s, MO’s, Engineering… • The other client – NetLink, PowerLink

30. Why use System-Link • Off Line Load • Any object available in Power-Link can be loaded • Only certain files are available for offline load • System-Link has a standard interface • Every application is a different flavor of offline load • Secondary objects can be loaded • Extra fields defined by user • Non-XA Primary objects can be loaded • Add, Change and Delete are supported • Power-Link edits are enforced • Including user defined edits

31. Why use System-Link • System-Link handles: • Database files and fields • Logical fields • Business rules • User Exits • Editing • Security • You also get Release Transparency • No worries about release upgrades

32. Methods to connect • System-Link Simulator • Use for testing/troubleshooting • To web server via XML • Web pages – Java/HTML • Directly to System-Link via LPI • RPG/CL programs • Web Services • Anything Microsoft-enabled • Requires Enterprise Integrator • IBM’s WebSphere MQ • Global enterprises • Requires IBM products

33. Local Program Interface • RPG program you call from anywhere • PSVPSR1R in AMALIBx • Parameters for the XML to send and receive • Inquiry – Request rows (view) or details (cards) – Receive the results • Maintenance – Create records, Update an attribute – Receive confirmation • Send is the Request - Receive is the Response

34. Web Services • MS Excel Worksheet containing pricing data • A button on the worksheet sends data to an XA Pricebook • XA edits the data • Accepts some • Rejects some • Error messages are returned

35. Prerequisites • On the server… • Enterprise Integrator • Deployment Profile generated WS catalog • System-Link • Interface to data – Creates price book data • On the client… • Microsoft Office • Microsoft Office XP Web Services Toolkit 2.0

37. Price book version after Host edits, subscriptions…everything works

38. Additional questions or comments? Thank you!!