1. Are You Ready For QXtend? What To Do And What To Avoid Gary Yang, Roundview Technologies

2. Agenda  QXtend – What Is It?  QXtend Architecture  What Can QXtend Do For You?  QXtend Inbound  QXtend Outbound  Messaging Middleware Are You Ready For QXtend?

3. What is QXtend?  Is the QAD Interoperability “Framework” A generic set of ‘modular building blocks’ and standards to provide connectivity across QAD products  SOA (Service Oriented Architecture) Based Uses web services to plug components together  Enabling Flexible and Quick-to-Market Solutions Allows anything to plug to QAD products with minimal effort Are You Ready For QXtend?

4. Manufacturing Demand / Supply Financials QXtend (QXI/QXO) Supplier Schedules Supplier Self Service EDI Supplier Consignment Customer Schedules Customer Self Service EDI Customer Consignment Shared Services Compliance Ware- housing JIT/S Lean Distributed Order Mgmt Purchasing Forecasting Supply Chain Planning Service, Support & Returns Financials Multi- National Production Planning “Core” QAD EA

5. QXtend Inbound (QXI) QAD Custom Programs QAD App QDoc SOAP (XML) Over HTTP QXtend Inbound QAD App QXtend Outbound Enterprise Interfaces Are You Ready For QXtend?

6. QXtend Inbound Architecture Are You Ready For QXtend? 3 rd Party integrations MFG/PRO QAD DB Set J2EE App Server 0 to X QAD EA’s or QAD Sessions Logging/Auditing Security UI/Administration ExternalSystems JMS Synchronous WS messages UI Adapter is QXtend Progress code added to QAD client installation Adapter call to QAD application server Async Dir Service Web Service Transaction Manager Routing Manager UI Adapter SI Adapter QDoc

7. QXtend Outbound (QXO) Are You Ready For QXtend? Order Confirm Allocation Shipping Invoicing QAD EA Sales Order Life Cycle

8. QXO: Multi-Sources And Multi-Destinations Are You Ready For QXtend? QAD EA #1 QAD EA #2 QAD EA #3 JIT/S #1 QAD Add-On QXO Server Adapter QAD SE / EE (via QXI) JIT/S (via QXI) Messaging Broker Web App (web-service enabled)... SubscriberSource Application QDocs QXO UI

9. QXO Architecture Are You Ready For QXtend?

10. What Can QXtend Do For You?  Third Party System Integrations  Master Data Replications  Intercompany (Cross Domain) Transactions  Customizations  Data Load / Conversions  Data Inquiries (Get Rid Of ODBC) Are You Ready For QXtend?

11. QXtend Inbound – DO NOT  Put On The Same Tomcat Instance As.Net UI  Use UI API When SI Is Possible  When Using Query Service, Avoid Inter-System Recursion  Multi-Threading On Transactional Data With Possibility Of Record Locking  Customize QAD Program With Out Testing QXI  Do Not Follow QGen Qdoc and Iteration Naming Conventions  Blame QXtend For All Performance Issues Are You Ready For QXtend?

12. QXtend Inbound – DO  Give Enough Memory To Tomcat  Turn On Debug Mode Log – Yes, Even For Production  Monitor Connection Pool And AppServer Agents  Use Connection Pool “maxuses” To Control The Number Of Invocations From On Agent  Comply With QAD Customization Standards  Use SI For More Complex Queries Are You Ready For QXtend?

13. QXtend Outbound – DO NOT  Use Replication Triggers Without Considering Performance  Using Event Based Approach For High Volume Data Objects  Include All Fields In A Table  Reversed Scan In Dataset Query  Use Default Profile  Excessive Use Of Calculation Fields  Use Event Triggers For EE Related Objects (such as ad_mstr) Are You Ready For QXtend?

14. QXtend Outbound – DO  Use Event Filter Or Modify Replication Trigger To Eliminate Unwanted Events  Use DDP (Direct Data Publish) For High Volume Messages  Use Tokens Instead Of Multiple Profiles  Use Custom Parsers To Report Response Message More Accurately  Monitor The AppServer And QXO Sessions Via Automated Scripts  Create Delete / Archive Policy  Enable Business User Visibility Of The Integration Process Are You Ready For QXtend?

15. Messaging Middleware – Why We Need It?  QXtend Web Service Is Synchronous - SOAP over HTTP(s)  Need For Queuing Mechanism  QXtend Is Only An Adapter  Exception Handling Can Be A Challenge For Third Party Caller  We May Need A Transformation Layer – Dealing With Text Files, For Example  Need For Data Encryption  Enterprise Service Bus Is Becoming A Standard In Corporate IT Are You Ready For QXtend?

16. Messaging Middleware Are You Ready For QXtend?

17. Dell Boomi  QAD’s Recommendation Of Messaging Middleware To Work With QAD  Cloud Based Solution With On Premise Deployment Options  Has Load Balancing Via Boomi Molecule and Atoms  WYSIWYG User Interface For Mapping and Development  We Have Certified Boomi Consultant On Our Team Are You Ready For QXtend?

18. Conclusion  MUST Understand The Architecture  How To Implement QXtend Can Make A Big Difference  Consider Using Message Middleware  Once Done Right, QXtend Can Make The Life Easier For Corporate IT Are You Ready For QXtend?

19. Questions? Gary Yang At gary.yang@roundviewtech.com / LinkedIngary.yang@roundviewtech.comLinkedIn