A COS Server data instance defines the location of the Windows XP or Windows 2003 Server on which the PegaDISTRIBUTION Manager program runs. This instance also defines a directory on that computer that can receive correspondence files (in ZIP format) for printing or other processing.
In addition to defining this data instance, update the database/databases elements of the prconfig.xml file to indicate how Pega 7 finds, logs into, and updates the COS database.
The simple COS database in PegaDISTRIBUTION Manager can use Microsoft Access 2003, Microsoft SQL Server 2003 or Oracle 8.1.7 or later. You also need to set up a Data Set Name on the Pega 7 server that references this database.
Consult the PegaDISTRIBUTION Manager Installation and Configuration Guide 3.3.5 for details on the installation and setup of COS.
The Data-COS-Admin-Server class holds COS Server data instances. This class is part of the SysAdmin category.
When you save a COS Server data instance, if the Associated RuleSet is [none]
, the system completes this field with a ruleset from the current application. This association assists with application packaging. You can update the associated ruleset using the field in the upper right corner of the form. See Identifying parts of rule and data forms.
If there is no ruleset associated with the data instance (for example, for existing instances not previously associated with a ruleset), the Associated RuleSet displays [none]
.