Elliott eStore Checklist

Release Date: 5/22/2017

- I would like to implement the Elliott eStore. What do I need?

A - To implement eStore, please go over the following checklist.

Setup Elliott Web Service 

Elliott Web Service is a building block for any Elliott Internet solution, and it's a required component for the Elliott eStore. If you do not already have Elliott Web Service, you will need to get it set up. For more information on Elliott Web Service requirements, please refer to the Knowledge Base article here.

Determine Who Will Host the eStore

The eStore can either be hosted by you or by Netcellent. To help you choose, please consider the following questions:

Do you have an IT admin who is knowledgeable about web hosting (Windows / IIS / MSSQL / networking)?

If No, consider hosting by Netcellent.
Do you have an IT admin who is knowledgeable in troubleshooting web-hosting related issues?

When the web site experiences performance issues, can they (your IT admin staff) narrow down the cause? (e.g., Is it a DNS problem? Is it a network issue on the user side? Is the web server running out of CPU resources? Is the database server running out of memory or disk space? Is it because of a traffic spike? etc.)
If No, consider hosting by Netcellent.
Do you require the best possible performance / network latency? If Yes, consider hosting yourself.
When the eStore is hosted by Netcellent, there is additional network latency for the data to travel from the web service server hosted at your office to the web server hosted by Netcellent.
Determine eStore URL
There are two options.
  1. Find an available domain and register it. There are many domain registrar services that would allow you to do that, such as  www.thatismydomain.com. 
  2. Use the sub domain of an existing URL. If your company already owns an URL, you can have the eStore URL be a sub domain of that URL. For example, if your company URL is www.mycompany.com, the eStore URL could be store.mycompany.com. The advantage is you don't have to register additional domains.

Web Server (If Hosted by You)

The web server should satisfy the following requirements:
  1. Must run on Windows 2008 R2 server or later OS.
  2. Must have IIS is installed.
  3. Must have .NET Framework 4.5 or later is installed.
  4. Must have access to MSSQL server. If you have an existing MSSQL server on your network, you can create the eStore database on the same database server. Otherwise, you can install a new instance of MSSQL Express Edition.

Networking (If Hosted by You)

  1. Allow HTTP(S) from the web server to the web service server. 
  2. Allow HTTP(S) access from anywhere to the web server.
  3. (Optional) Allow terminal server access to Netcellent for easier support (we have a static IP range).
If hosted by Netcellent:
  1.   Allow HTTP(S) from the web server to the web service server.  
  2.   (Optional) Allow terminal server access to Netcellent for easier support (we have a static IP range).


If the web site is hosted by you, configure the DNS to point to your web server. If hosted by Netcellent, configure the DNS to point to the Netcellent web server (IP will be given to you by Netcellent). 

SSL Certificate

Acquire an SSL certificate for the URL that you choose.  


Developer Documentations

  1. Received Code 9999 with Web Services Call
  2. Received Return Status Code 3 When Using Elilogin Login Method
  3. Elliott Web Service Requirements
  4. Elliott eStore Checklist
  5. LN API
  6. FN API
  7. RN API
  8. IN and DF API Change (V9.0)
  9. FA API Changes (V9.0)
  10. VA API Changes (V9.0)
  11. CartService
  12. EliarachService
  13. ElicshtxService
  14. EliattrbService
  15. ElisyscdService
  16. EliNoteService
  17. El2rstimService
  18. EliOrderService
  19. ItemInquiry
  20. EliitmiqService
  21. EliShiptoService
  22. El2getfrService
  23. Steps Required to Test ReportWriter in V8.2
  24. Installation of ElliottService, NETcellent’s Web Services for Elliott
  25. ResellerFinder
  26. EliaptrxService
  27. VendorInquiry
  28. EliloginService
  29. ElislsmnService
  30. EliserhsService
  31. EliatpobService
  32. ElievprcService
  33. ElihdtrxService
  34. ElicuswlService
  35. QueryTurnaround
  36. InvoiceInquiry
  37. ElicustmService
  38. EligetcdService
  39. OrderInquiry
  40. EliordiqService
  41. EliecontService
  42. EliautdpService
  43. El2CrCrdService
  44. Log-Timer / ElliottTimer.Ini Support
  45. Alpha Document Number Support (V8.5/V9.0)
  46. ElliottService System.TypeInitializationException
  47. Feature - Printing API to Dynamically Set Number of Copies
  48. The Values and Meanings of Distribution Types - ARDISFIL, APDISFIL, IMDISFIL, BMDISFIL
  49. DD API Changes (V9.0)
  50. PA API (8.5)
  51. Validate License API
  52. AP API
  53. TP API: Temporary Path
  54. Data Structures for Report Desk Defaults and Enforcements
  55. COBOL to VB Interface Programs
  56. IN API: Option to Support Files and Folders Validation
  57. FF API: File Functions
  58. ID API
  59. LK: Links API
  60. FFLNearYou
  61. Report Desk: Registry Settings
  62. Developing a New Elliott V8.6 Report Desk User Defined Report (UDR)
  63. CustomerInquiry
  64. Elliott API (JSON Web Service)
  65. Animating COBOL Code in Elliott V8.5
  66. Preliminary Programming Changes for Elliott 8.6
  67. CV API
  68. System Lock File Requirements
  69. How to Write Test Codes for C# ESS Projects
  70. Solving the Inability to Debug Elliott on a New Server
  71. Report Desk: Developing Custom Reports
  72. Report Desk Tables
  73. Report Desk Database Delivery Strategy
  74. Logging I-O Logic Errors
  75. Report Desk: Developer Documentation Roadmap
  76. Report Desk: Resolution of Pervasive.Data.SqlClient.dll
  77. TB API
  78. Creating HTML Emails for Professional Presentation
  79. EM API - Create and Send an Email
  80. DN API (Document Number Handling)

Feedback and Knowledge Base