|
A database account is a location in a physical RDBMS where appdata or metadata of an application are kept in a set of database tables.
Such a location is identified at RDBMS level by a database schema (SQL Server) or a database user account (Oracle). Delivery Manager only supports database accounts in the SQL Server and Oracle RDBMSs.
In Delivery Manager, in the same way as in USoft Binder, a database account is identified by the combination of a username, password, and database connect string.
Relationships between database accounts and applications are not registered in the Delivery Manager data model. Rather, you imply such a relationship at the time when you come to call an action, when you are usually asked to pass the combination of 2 parameters: Application and Database Account.
To define or view database accounts in Delivery Manager, choose Define, Database accounts from the menu.
A database account defined in Delivery Manager has the following properties.
A string name that uniquely identifies the database account in Delivery Manager. This name is not used outside Delivery Manager.
|
The database user name of the database account.
|
The password of the database account. This password is kept in the Delivery Manager table.
|
Either 'Oledb' ( = SQL Server) or 'Oracle'.
|
The database connect string that identifies the database that the database account is in. This is the same database connect string as used in other USoft tools, eg., USoft Binder.
|
The owner of the application, as specified in USoft Authorizer for the database account and as used in USoft Binder.
|
A computed text string that Delivery Manager uses when compiling INVOKE calls for executing actions in the database account. You can view the complete INVOKE calls in the Define Tasks window (choose Define, Tasks from the menu).
|
An optional field for notes about the database account.
|
|
