XA System-Link A Powerful Development Tool

1. XA System-Link A Powerful Development Tool Denise Lutherdenise.luther@cistech.net

2. What is System-Link? • Bridge between XA and other systems • Inquiry • Maintenance • XML – Standard interface • Other ERP systems • Other platforms • Part of Power Architecture • CSM, PM, OBPM, EPDM, MM… • CO’s, PO’s, MO’s, Engineering…

3. Why use System-Link • Replacement for offline load • Access any object available in Power-Link • Only certain files are available for offline load • Secondary objects can be accessed • Extra fields defined by user • Non-XA Primary objects can be accessed • Add, Change and Delete are supported • Power-Link edits are enforced • Including user defined edits

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

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

6. System-Link References • System-Link User Guide – Release 7.7 • Download from Infor website • Documentation • Product Manuals • Miscellaneous • SYSL • System-Link Installation Instructions R7 • Configuring WAS 5.0 Express on W2K for System-Link R7 (SH14777) Servlet information

7. Managing System-Link • Use Link Manager to manage System-Link processes By environment By machine Distribute server load across resources

8. Managing System-Link • System-Link processes must be started • Autostart System-Link • Options at environment level

9. Managing System-Link • Link Manager • Green circle means started • Right click to start/stop/restart/Move

10. Managing System-Link

11. System-Link Simulator • URL points to your host server • Make a desktop shortcut or bookmark

12. Using System-Link Simulator • Display PO’s for vendor 100 – Restricted List, navigate from Vendor object • Navigation/System-Link request • Not required to create System-Link requests but it makes the job easy

13. System-Link REQUEST

14. Paste from clipboard

15. Variables

16. Check the response

18. Make adjustments Deleted e

19. Request has errors – Check the response

20. Update System-Link Command

21. Requesting System-Link from Card File

22. Copying a Create System-Link Command

23. System-Link sessions • ODBCJOBR7/WRKODBCJOB command will allow you to manage System-Link jobs.

24. System-Link sessions • IP address of auxiliary server will be System-Link sessions • View job log (Option 10) for troubleshooting • Errors from associated Integrator user exits will be in QSYSOPR message queue

25. 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 or error • Maintenance – Create records, Update an attribute – Receive confirmation or error

26. LPI Parameters

27. LPI sample • Available as a download • SH14873 • Illustrate one way of using System-Link with your RPG programs • Send a request - Send XML request to LPI • Parse the response - Receive and parse XML response from LPI • Create a report of PO’s for a vendor • Only change required – Supply data for login substitutions

28. Writing your programs • Sample parsing program USRLPI1R is written generically • Can be used for just about any object (use it for yours) • V5R4 New XML functions for parsing %XML, XML-INTO, %HANDLER, XML-SAX • Sample print program calls the parser field-by-field • You can use this technique in your programs • There are other techniques

29. <Response_sessionHandle='1a5f739:fc75bbe92b:_7aef‘_workHan <QueryListResponse_name='queryList_PurchaseOrderGeneral‘_r <DomainEntity_domainClass='com.mapics.pm.PurchaseOrder' <Key> <Property_path='order'> <Value><![CDATA[P000349]]></Value> </Property> </Key> <Property_path_='order'> <Value><![CDATA[P000349]]></Value> </Property> <Property_path='vendor'> <Value><![CDATA[100]]></Value> </Property> <Property_path='vendorName'> <Value><![CDATA[Hi_Tech_Corp]]></Value> </Property> <Property_path='orderStatus'> <Value><![CDATA[20]]></Value> Starts a new record Field values

30. FetchNext • Don’t ask for too many records at once. • You set the limit with MaxReturned • LPI tells you if there are more. • ‘FetchNext’ is the way to get more. • Our sample programs shows you how. • Create loop that processes until P#MRQR = *NO

31. Supplier Portal - Web application • Login information used to construct Login tag • System-Link request to retrieve P.O. lines • Auto content security determines what rows

32. System-Link request returns rows

33. Transactions • User actions on the web page are used to construct a System-Link request to create records in a custom transaction file. • Custom transaction file is a business object with Integrator user exits. • User exits are used to perform work on the host (update flags, dates, create attachments) • Integrator user exits execute if object is being maintained via PowerLink, System-Link or NetLink.

34. Custom Forecast Object Custom objects can be used with System-Link

35. Thank YouQuestions? Denise Lutherdenise.luther@cistech.net