Setup Scenarios

In this article

One database for Head Office and all POS

Separate Head Office and POS databases

There are two scenarios available for Member Management setup: via Web Service or locally.

Member Management validation, creation of cards or contacts, and validation of accounts and points is always done via Web Service if the POS database is local. If, however, the POS runs as a client on a central database, the validation is done locally in that database.

If Web Service is offline, customers cannot use their member card or member points nor is any validation or creation of the member possible.

Note: Transaction Server is not supported within Member Management.

The two setup scenarios are described in the following.

One database for Head Office and all POS

  1. Open the POS Functionality Profile List, and double-click the profile you wish to modify. The Profile Card opens.
  2. On the action menu, click Profile - Web Servers.
  3. Enter a value in the Priority field, and select the Local Request check box.

When a member transaction is posted and point calculation is done, an entry is created in the Member Process Order Entry table. The processing of the queue should be scheduled. See Member Process Order Entries.

Separate Head Office and POS databases

In this case, all member information is stored in the Head Office database. The POS then uses Web Requests to gather the needed data. In this setup, a Dist. Location entry must be added in the Functionality Profiles:

  1. Open the POS Functionality Profile List, and double-click the profile you wish to modify. The Profile Card opens.
  2. On the action menu, click Profile - Web Servers.
  3. Enter a value in the Priority column, clear the Local Request check box, and select the Head Office in the Dist. Location column.
  4. Open the Head Office's Distribution Location Card, and make sure it is correctly configured for Web Services to work.

The Web Service URL is built from the fields Company Name (on the Replication FastTab), Web Server Computer Name, Web Server Port, and Web Server Name (on the Web Server FastTab).

Transaction data (not Member Management data) can be replicated to Head Office either via Data Director or via Web Services. Member Management data are never replicated by Data Director; the data are always updated by web services. The Member Process Order Entries created at Head Office at the end of a transaction cannot be processed until the transaction data have been uploaded.

The system is not designed to support Store servers as the endpoints for Member Management web services. The system is designed to have all Member Management information in one central database. Member Management information is always updated using web services only; this information should not be updated using Data Director.

If Web Services are used for Transactions, the Member Process Order entry is processed automatically. In that case no scheduling is needed at Head Office to process the queue in the Process Order Entry table.