The ww.dll installer (Install_Siriusware_ww_xxxx.msi) installs ww.dll on a “fresh” system. It creates Program Files\Siriusware\ww and ProgramData\Siriusware\ww directories the same way the other Siriusware® Inc. installers do. It also adds a shortcut to the desktop that enables you to update ww.dll by simply clicking on the icon. The installer also creates the Siriusweb user and run the create_AppRole_SiriusSQL.sql. Because ww.dll and SiriusSQL database typically reside on different computers, you are able to browse for and connect to a database on a remote server.

ww.dll is normally pooled as a web garden under IIS. Directions on installing ww.dll as a web garden can be found here:

 

 

The ww.dll is installed on your E-Commerce server and you can make calls to it using Siriusware’s XML format to retrieve information or to submit information to the database. Calls are available to, for example:

 

Note: In order to utilize emailing in E-Commerce module you must install MessengerService. Sales Host utility now uses Messenger Service application for email processing.

 

Important: The ww.dll and Web Sales Host (WSH) are no longer able to share the same salespoint ID due to complications with Max4Sale and Points4Sale functionality limits and Real Time Inventory Tracking. The ww.dll now adds the salespoint ID that it is configured to use (from the ww_system.ini file, DefaultInfo=<operator>WEBOP</operator><salespoint>WWSP</salespoint> setting) to the sale string that is passed in for processing by WSH unless the pages have already added a salespoint ID to the sale string via the salespoint key. The salespoint ID will appear in the sale string like this,

 

 

If the salespoint ID in the sale string is the same as the salespoint ID configured for WSH, an error will occur when WSH tries to process the sale indicating that there is a conflict, and then WSH will shut down. Either the salespoint ID in the sale string will need to be changed or the salespoint ID of WSH will need to be changed and the sale resubmitted. For all future sales, the salespoint IDs of the ww.dll and WSH need to be unique.

 

The Salesware ww.dll is used to provide Internet (TCP/IP) access to the SiriusSQL database. ww.dll functions provide an interface to perform many of the operations that you perform from a Classic salespoint: pass and ticket sales, guest lookups and modifications, private lesson reservations, In-House Cards item purchases and so on. The Salesware E-Commerce and Rentals (Self Entry component) modules use ww.dll functions, but the ww.dll functions are also available to clients who wish to write their own custom Internet applications. ww.dll communications with the SiriusSQL database can be across a LAN or across the web. With ww.dll, you can create a small set of web pages to provide very specific functionality or you can duplicate most of the functions of a Classic salespoint, but with a web interface.

To use this manual, you need a copy of the SiriusSQL Data Dictionary, available from Siriusware Inc. While SiriusSQL tables and fields are defined to some extent in this document (especially in the case of calculated fields that are passed back as the result of execution of a stored procedure), the Data Dictionary is the final word on the structure, makeup and definition of the SiriusSQL database.

To use this document, you need to understand how a Classic salespoint operates. You then use the ww.dll functions to mimic these operations from custom web pages that implement some mechanism for acquiring items, such as a shopping cart. You can learn how a Classic salespoint operates by reading the Salesware User and Ticketing Guide for Beginning Users, Salesware User Guide for Advanced Users and the other documents available from http://www.siriusware.com/docs. Most developers use ASP.NET and VB.NET from within a Microsoft Visual Studio project to leverage the API and generate the web pages that are then read by an Internet Explorer, Netscape or Firefox browser.