INT403 - Adapter Development Kit (e-ADK): Easily Adapting Systems into an Integrated World

1. INT403 - Adapter Development Kit (e-ADK): Easily Adapting Systems into an Integrated World Duncan CarterTechnical Support Engineerdcarter@sybase.com/(303)409-743408/16/2003

2. What is an Adapter • Single point of entry into an application • Single point of entry into the Integrated world • Helps to automate design time processes • Allows for realtime manipulation of data to fit your needs • Allows you to do whatever you need to do, within the C++ code

3. The Existing world Transaction Systems Fixed Assets Deposits/ Receipts Spot Fixed Income Equities Payroll Manual TX AS400 DOS DOS AS400 AS400 DOS Loans Accts Payable Sybase DOS FX Option Funds Manager SQL MS Access Futures Swaps MS Access Sybase Management Systems IRS Cash Flow System G/L

4. The Integrated world Transaction Systems Fixed Assets Deposits/ Receipts Spot Fixed Income Equities Payroll Manual TX Loans Accts Payable FX Option Funds Manager e-Biz Integration Server Futures Swaps Management Systems IRS Recon- ciliation Cash Flow System G/L

5. Adapter Key Components • Application • THE application you want to use the adapter for • Adapter • The adapter code that you write • e-ADK shell • The pre-packaged shell that calls your adapter code • Transport • The method of getting the message data out of the adapter

6. Application • Any Application can be used • You need to know the application entry and exit points • API’s • Database connections • Socket connections • Any connection information • Usernames • .dll locations • Environment variables • Format the application needs to have the data in • How to get the format the application uses for receiving/sending data • Any other application limits

7. Adapter • C++ written .dll to be called by the e-ADK • Needs to have some specific functions available to it • initAdapter • shutdownAdapter • acquireSchema • This is the actual entry mechanism to the application • Single .dll, but is only limited by the functions required by the e-ADK and C++ logic • Any data manipulation that you need to do can be done within your functions • External .dll’s may be called and utilized

8. e-ADK Adapter Modes • Schema • Loads/Unloads message formats into eBiz Integrator • Acquire • Takes data messages from the applications, and places them on the transport • Deliver • Takes data messages from the transport, and sends them to the application • Process • Combination of the Acquire and Deliver modes • Takes a message off of the transport, and sends it to the application. Then, will wait for the response back, to put to another transport

9. e-ADK Schema Mode • Responsible for loading/unloading formats • Can build a format based on • DTD • Text files • Any other method that makes sense to you and allows you to determine the schema • Will create all of the formatter components needed • NDO needs to be created to pass to the ADK for completion • Actual schema can be built based on NCF, DTD, or XML format

10. e-ADK Acquire Mode • Retrieves or receives data from the application • Called by using the acquireBuffer or acquireData API’s

11. e-ADK Deliver Mode • Delivers data to the application • Called by using the deliverData or deliverBuffer API’s

12. e-ADK Process Mode • Combination of Deliver and then Acquire modes • Delivers data to the application • Waits for a reply back from the application to pass back to the ARE

13. E-ADK Buffer vs NDO • Buffer • Entire chunk of data passed in as a buffer • No data manipulation or parsing done by the ADK • NDO • Passes the data as an NDO object • Data will be parsed out to NDO object for easier access to elements • Allows the adapter to put the messages out in NCF or XML format

14. e-ADK Serialization/Deserialization • The process of changing NDO to a string and vice-versa • Takes an NDO object and combines each of the elements into a single string • Takes a string and parses it to populate an NDO object • To be able to put to a transport, the data needs to be in a string format • OPT_MSG_TYP is used to look up the schema in the repository

15. e-ADK Serialization • NDO Object • Serialized NCF • Serialized XML

16. e-ADK Executing Adapter • Startup • NNSYAdapter39 –file = <config file name> [-trace] • Config file read order • Command line • NNSYAdapter.cfg in local • nnsyreg.dat in local • nnsyreg.dat in NNSY_ROOT • Setup as NT Service • All dll’s/transports/networking options must be available • NNSYAdapter39 -install [-n|-name] serviceName [-d|-display] serviceDisplayName -p paramFile • Default name is NNSYADK

17. Open Transport Transport Options • Method of taking data to or from the adapter • transport.in.name • transport.out.name • Configurable within the config file • Allows for multiple transports • MQSeries • File • Any JVM capable application

18. Open Transport Configurability • Two points of configuation • Config file • Adapter code • Config file • Used to configure connection information • Logical transport name gets used by the ARE • Adapter code • Used to modify any of the message options • OPT_MSG_TYP • RFH/RFH2 option • MQMD options • Functions available to both get and set these options

19. The Adapter Troubleshooting • Error messages • NNSYMessageLog.nml • -trace option on command line • Compiling your own adapter specific log file • Verifying the environment • NNSY_ROOT • PATH • NNSY_CATALOGUES

20. The Adapter Deploying the Adapter • Adapter dependancies must be met • Any client libraries must be available • Any transport libraries must be available • ARE must be on deployed to machine • ARE can be retrieved from the installation cd, and running the are_redist.cmd • Redeploy package needs to contain all adapter libraries along with files that are now in the NNSY_are39 directory

21. Current Sybase Adapters • SAP Adapter • Siebel Adapter • XML Adapter • Flat File Adapter • eMail Adapter • Database Adapter • EDI Adapter