Object mapping

Although a single CO typically corresponds to a single physical resource, as shown in Figure 1, this is not mandatory. You can have the attributes of a single physical resource correspond to the attributes of several COs, as shown in Figure 1. In this example, a single physical resource (FaxY) is represented as two separate COs (Fax1 and Fax2). These two COs are independent of each other, and each can use FaxY in its own way.

Figure 1. Two COs used to represent one real world object

       The Real World
        BANKA
         fax
           FaxY
             fax queue for PrinterY
             authorization to use FaxY


       FTM SWIFT Configuration Objects
organization:  BANKA
object type :    fax
object      :      Fax1
attribute   :        FaxQueue=FaxQ1
attribute   :        fax
object      :      Fax2
attribute   :        FaxQueue=FaxQ1
attribute   :        fax

Similarly, if an attribute of a database table such as an update flag is to be instantiated (so that different users each have a different flag), but the table is not (so that all users share the same table), you might choose to split the table and this one attribute of that table into two separate configuration objects.

There are also situations in which you might choose to group several real-world objects into a single configuration object. For example, a queue and a database table are two separate objects in the real world, but if they are always used together, and exclusively, you might find it simplifies your configuration if you group them into a single CO.