Planning OUs

Use an organizational unit (OU) to represent an entity such as a company or department for which data and access to services needs to be segregated. Determine which OUs you need, then assign a name to each OU. Choose names carefully, as they are difficult to change (doing so would entail deleting and recreating many vital resources). Each OU name can have up to eight characters or digits, and must be unique within the scope of an instance. The OU name is used later in the names of:
  • The interface queues of the services used by the OU
  • The names of the audit and message warehouse tables
  • The names of the configuration scripts
In addition to business OUs, which represent entities such as companies or departments, FTM SWIFT requires the following system OUs:
SYSOU
System OU for the product.
DNFSYSOU
System OU for some extending features of the product.
Each of these system OUs is created automatically during customization. Neither of them can be used as a business OU.

If you use dual authorization, each OU requires at least two FTM SWIFT security administrators. For SYSOU, the user IDs of the first two security administrators are specified when you create the instance. For each additional OU, you must identify security administrators and assign the user IDs to the appropriate roles. How to do this is described in Administrator roles.

Each OU uses a separate message audit log and set of message warehouse tables.

When processing FIN messages with MERVA ESA:
  • A single OU typically processes the messages of only one MERVA ESA system.
  • Several OUs can share a single MERVA ESA system.
  • There must be at least one Bridge process for each OU that is to send FIN messages from MERVA ESA.