CTN Control Database

The CTN software system uses one control database that stores all of the configuration information for all of the CTN applications. All CTN demonstration applications use CTNControl as the default control database; the default can be overwritten with a command line argument.

Parts of the CTN Control Database

The ApplicationEntity table is used by CTN to define all application entities that are known by CTN. This includes applications that execute on CTN as well as applications that are defined by external systems. Any CTN application will be defined in the ApplicationEntity table. Furthermore, any external applications need to be defined in this table to be recognized by CTN applications.

The SecurityMatrix table contains the list of external applications that are allowed to make connections to a CTN application. For each CTN application that acts as a DICOM responder, this table defines the set of applications that are allowed to make a connection. Other tables defined below will indicate what privileges the external applications may have once an Association is eestablished. This table only defines an application's right to establish an Association.

Each row in the SecurityMatrix table defines a connection that can be initiated by an external application and accepted by a CTN application. This means that a popular CTN application (e.g., an image server) will have a number of rows in the SecurityMatrix table with different values for Requesting Application and the same value in the Responding Application column.

Application Entity Table

Title This is the Application Entity title that identifies an application. it is used as a part of an association negotiation as either a "called title" or the "calling title." This title uniquely identifies an application that can exist in only one place on the network. Two applications may not run on different nodes and share the same title.
Node This is the node name where the application is found. This is the name as found in the UNIX hosts table for making and receiving network connections. The node name can be a simple name (orbit) or a fully qualified name (orbit.cs.unc.edu). The CTN software does not demand a fully qualified name. Maintainers may wish to use full domain names for CTN applications that will accept connections from other domains.
Port This field identifies the TCP/IP port number at which a DICOM acceptor is listening for a TCP level connection. The CTN software does not assume the DICOM default TCP/IP port number and requires that this field be entered for DICOM acceptors. The field can be empty for applications that are only initiators of an association.
Comment Just what it says. Comments that the maintainer might wish to use to identify various aspects of the application

Security Matrix Table

Requesting Application This field lists the Application Title of an application that is requesting an association with a CTN application. Requesting applications are considered to be external applications
Responding Application This field lists the application titlte of the CTN application that can accept associations.

The following is a general model for the CTN server applications which are accepting requests from external applications. The application entity titles are External Client and Ctn Server. These applications should be defined in the Application Entity table of the CTN Control Database. You should also have an entry in the Security Matrix table to support connections from External Client to CTN Server, because External Client is defined outside the domain of CTN.

To learn about configuring the database, continue on to Configuring your MIND System