Steps for the implementation and deployment of the Panatracker API
- Install the “SubmitFromWebService” license
- Populate the appropriate Panatracker “Trx” tables with transactions that have a status of “Queued”. That is, column named “TransactionStatus” = “1”.
- To trigger the submission, the web API endpoint needs to be called. Here’s an example call for T18: http://t18:81/api/submit/SubmitQueued?companyName=PRODUCTION&trxsToSubmit=20. The parameters are fairly obvious: companyName and trxsToSubmit. The “trxsToSubmit” defines a limit for the transactions to submit in a single batch to avoid overloading the process. The limit of 20 is a pretty good number to start. Ideally, call the API submit trigger often enough so that there are only a very few to be processed at once.
- There are a couple options to trigger the above call:
- Use a SQL Job that runs every few minutes to call the submit webservice.
- Change an application that you’d like to integrate with the PGP API to invoke the web service whenever a transaction needs to be queued. (This would most-closely mimic how PGP actually works.)
- Write a Windows Service application that would run and periodically call the web service. This is not the optimal method.
- When the API is called and processes one or more transactions, it can send out an email indicating the transaction codes it created.