CAL Deployment Order

By default, all internal CAL packages have a deployment order of 0 (zero) and custom CAL packages have a deployment order of 1000. Using a deployment order that differs from the best practices recommended order can result in packages going to POS client workstations in an undesirable order. Packages need to deploy to POS client workstations in a specific order. Assigning an order enables Simphony to create and place certain files or folders for one package, which are used later by another package in order to succeed.

Oracle Hospitality recommends deploying CAL packages in the following order:

Table 3-1 CAL Deployment Order in Simphony 18.2 and 18.2.1

CAL Package Name	Deployment Order Number
CAL Version Fixer	0
CAL Client	0
ServiceHost Prerequisites	10
CAPSOnIIS	20
Service Host	30
Service Host Hotfix (Custom Package)	31
Device Information	35
Language Translation	40
KDS Handler	50
WS KDS Display (Win32)	60
Simphony KDS Client	70
Media Viewer	80
Biometrics	90
CM Lite	100
Custom CAL Packages (not hotfixes) start at	1000

Simphony Standard Cloud Service (Hosted) and Premium Cloud Service (Hosted) Environments

Simphony (Self-Hosted) Environments

In Simphony Standard Cloud Service environments, the CAL Package Deployment Order field is grayed out and is not configurable at the organization level. The CAL Package Deployment Order is configurable for Simphony Premium Cloud Service environments.

To change the CAL Package Deployment Order, log in to the EMC as a SuperOrg user. Changing the CAL Package Deployment Order as a SuperOrg user performs this change on all organizations associated with the SuperOrg.

Figure 3-1 CAL Package Configuration

Privileged Simphony (self-hosted) users always have the CAL Package Configuration Deployment Order field available for configuration or editing.