11.2.1 Creating an scCashRegister Object

The first step to register new Point of Service hardware is to define the name and model type of the Point of Service terminal. The scCashRegister object stores information about Point of Service hardware. Typically, you should define a scCashRegister object for each type of terminal used on the Novell Linux Point of Service system; however, if a Point of Service terminal does not have an scCashRegister object for its specific hardware type, it uses the configuration defined in the default scCashRegister object.

The scCashRegister objects are stored in the Global container so they can be accessed by all Branch Servers.

Table 11-1 lists the scCashRegister attributes.

The following example adds a default scCashRegister object below the global container (type the command all on one line):

posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret 
--base cn=global,o=mycorp,c=us --add --scCashRegister 
--cn crtype3 --scCashRegisterName 1234567 
--scPosImageDn cn=browser,cn=global,o=mycorp,c=us --default

11.2.2 Creating an scRAMDisk Object

The scRamDisk object stores configuration information for a Point of Service terminal RAM disk. If no hard disk is available, you must configure a RAM disk for the Point of Service terminal.

Table 11-2 lists the scRamDisk attributes.

The following example adds an scRamDisk object below the Hardware Reference object, crtype3 (type the command all on one line):

posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret 
--base cn=crtype3,cn=global,o=mycorp,c=us  
--add --scRamDisk --cn ram --scDevice /dev/ram1 

11.2.3 Creating an scHarddisk Object

The scHarddisk object stores configuration information for a Point of Service terminal hard disk.

Table 11-3 lists the scHarddisk attributes.

The following example adds an scHarddisk object below the scCashRegister object, crtype3 (type the command all on one line):

posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret 
--base cn=crtype3,cn=global,o=mycorp,c=us --add --scHarddisk 
--cn hda --scDevice /dev/hda2 --scHdSize 9000 
--scPartitionsTable ’1000 82 swap swap;4000 83 / ext3;’ 

11.2.4 Creating an scConfigFileTemplate Object

The scConfigFileTemplate is an optional object used when you run services, such as the X Window system, that require hardware-dependent configuration files. An scConfigFileTemplate object contains the configuration file data that a Point of Service terminal needs to run a given service.

When you define the scConfigFileTemplate object, you designate a source configuration file (--scConfigFileData). posAdmin extracts the configuration data from the source file and stores it in the scConfigFileTemplate object. When a Point of Service terminal registers with a Branch Server (or when you run posAdmin.pl --updateconfig or posldap2crconfig.pl --dumpall), the Branch Server retrieves the configuration data in the scConfigFileTemplate object to create a configuration file in /tftpboot/CR/MAC_address/ directories on the Branch Server.

Using TFTP, the configuration file is then distributed from the Branch Server to the appropriate Point of Services terminals at boot time.

Table 11-4 lists the scConfigFileTemplate attributes.

The following example adds a scConfigFileTemplate object below the Hardware Reference object, crtype3 (type the command all on one line):

posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret 
--base cn=crtype3,cn=global,o=mycorp,c=us 
--add --scConfigFileTemplate --cn XF86Config 
--scConfigFile /etc/X11/XF86Config --scBsize 1024 
--scConfigFileData /mydata/XF86Config.1234567

11.2.5 Creating an scConfigFileSyncTemplate Object

The scConfigFileSyncTemplate is an optional object used when you run services, such as the X Window system, that require hardware-dependent configuration files. This object points to the configuration file that a Point of Service terminal needs to run a given service. This object differs from scConfigFileTemplate objects because the configuration data is not stored in the object; rather, the object points to a configuration file outside the LDAP directory.

When a Point of Service terminal registers with a Branch Server (or when you run posAdmin.pl --updateconfig or posldap2crconfig.pl --dumpall), the Branch Server uses RSYNC to transfer the configuration file designated in the scConfigFileSyncTemplate object from the /opt/SLES/POS/rsync/config/ directory on the Administration Server to /tftpboot/CR/MAC_address/ directories on the Branch Server.

Using TFTP, the configuration file is then distributed from the Branch Server to the appropriate Point of Service terminals at boot time.

Table 11-5 lists the scConfigFileSyncTemplate attributes.

The following example adds an scConfigFileSyncTemplate object below the hardware reference object, crtype3 (type the command all on one line):

posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret 
--base cn=crtype3,cn=global,o=mycorp,c=us  
--add --scConfigFileSyncTemplate --cn XF86Config 
--scConfigFile /etc/X11/XF86Config --scMust TRUE --scBsize 1024 
--scConfigFileLocalPath /opt/SLES/POS/rsync/config/XF86Config.1234567

11.2.6 Creating scPosImage Objects

Images are managed in LDAP with scPosImage objects. Each scPosImage object stores information about an image stored on the Administration Server. Every client image that you want to distribute to Point of Service terminals must have a corresponding scPosImage object in the LDAP directory.

The scPosImage objects that correspond to the client images you want to distribute to Point of Service terminals are typically organized within Distribution Container objects under the Global container in the LDAP tree.

After the installation and configuration of the Novell Linux Point of Service, an scPosImage object for the Minimal image is automatically added to the Default Distribution Container. This default LDAP entry is intended to serve as an example and should not be deleted. You must manually add an scPosImage object for each client image you want to distribute to Point of Service terminals.

Table 11-6 lists the scPosImage attributes.

The following example adds a scPosImage object below the Global container for a modified Java client image (type the command all on one line):

posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret 
--base cn=global,o=mycorp,c=us --add --scPosImage --cn myJava 
--scImageName myJava --scPosImageVersion "2.0.21;active" 
--scDhcpOptionsRemote /boot/pxelinux.0 --scDhcpOptionsLocal LOCALBOOT
--scImageFile myJava --scConfigFile /etc/X11/XF86Config

11.2.7 Activating Images

Each image can be available in several versions, as shown in Table 11-7. The scPosImageVersion attribute in each scPosImage object must be set to either active or passive. Active versions are downloaded by the Branch Server. If there are multiple active versions of a single image, the Branch Server selects the highest active version. Passive image versions are never downloaded to the Branch Server unless they are explicitly configured in the scWorkstation entry for the individual Point of Service terminal.

To activate a registered image, set its scPosImageVersion attribute to active. This is done with posAdmin using the modify and multivalue options as follows (type the command all on one line):

posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret 
--modify --scPosImage --multival 
--scPosImageVersion '2.3.10;passive=>2.3.10;active' 
--DN cn=browser,cn=default,cn=global,o=mycorp,c=us

To activate the new image version on a Branch Server, run posldap2crconfig.pl with the --dumpall option and possyncimages.pl as follows:

posldap2crconfig --dumpall
possyncimages

11.2.8 Assigning an Image to a Point of Service Terminal

You can assign a specific image to a Point of Service terminal through its scWorkstation object.

For example, the following command assigns browser image 2.3.10 to the CR001 scWorkstation object in the boston1 container (type the command all on one line):

posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret 
--modify --scWorkstation 
--scPosImageDn cn=browser,cn=global,o=mycorp,c=us
--scPosImageVersion 2.3.10 
--DN  cn=CR001,ou=boston1,ou=boston,o=mycorp,c=us

When you explicitly assign an image in the scWorkstation entry, the active or passive flag set for the scPosImage object in the global container is ignored.

11.2.9 Removing an Assigned Image

To remove the image assigned to a workstation, run the following command (type the command all on one line):

posAdmin.pl --user cn=admin,o=mycorp,c=us --password secret
--remove --scWorkstation --scPosImageDn --scPosImageVersion  
--DN cn=CR001,ou=boston1,ou=boston,o=mycorp,c=us