Database Tab

Previous Next

The Database tab of the Project Properties sheet in USoft Binder is used to specify the following properties:

Separate Properties for Repository and Application

Choose this option box if you want to use different database accounts for repository tables and runtime application tables. Runtime application tables are used during development for testing and prototyping. If you choose this option, the Definer, Windows Designer and USoft Batch tables are placed in one account, and the application tables in the other account.

IMPORTANT: If you choose this option, you need Authorizer tables in BOTH accounts. You must run Create Tables for the Authorizer twice, once with the Authorize for Repository option for the Authorizer item checked, to create Authorizer tables for the repository user, and once with the Authorize for Repository option for the Authorizer item unchecked.

The separate database accounts may be on different types of databases, for example, Oracle vs. Sybase.

See also Defining a Separate User Environment.

Common Properties for Repository and Application

Choose this option box if you want to use the same database account for repository tables and application tables. In this case, development team members share this account not only for development but also for application testing and prototyping.

The following 6 properties, called database properties, apply to both repository and application if you have selected "Common Properties...". If you have selected "Separate Properties...", press the Define button to specify separate database properties for the repository and for the application (12 in total).

 

 

collapseUser

This is where you type the user name you use when connecting to the database. This is not necessarily the same as the owner of the application you connect to (see Owner). For some RDBMS types this parameter is case sensitive.

In the Separate Properties for Repository and Application dialog:

•The Repository User is the database user name to be used by USoft Binder to log on to the development repository. This is not necessarily the repository owner (see Owner).

•The Application User is the database user name to be used by USoft Binder to log on to application tables. Often, when using separate properties for repository and application, each development team member has an individual application for testing and prototyping, and in this case the Application Owner is the same as the Application User and does not need to be specified.
collapsePassword

This where you can type the password you use when connecting to the database. If you leave this box blank, you will be prompted for a password when the connection is initiated. Note that unless you check the "Use Password Next Time" box, any password typed here is only valid for this session. As soon as you leave the USoft Binder the password you typed in here is lost. For some RDBMS types this parameter is case specific.
collapseUse Password Next Time

Check this box if you want the password to be saved with the project. Note that this password is stored as plain text, and security could be compromised.
collapseRDBMS

This is where you specify the RDBMS type you are connecting to. Choose one from the dropdown list.

Note that the RDBMS type you specify here must be the same as the type you specified when you installed the USoft Developer Series.
collapseDatabase

This is where you specify the connect string that identifies the database to which you are connecting. You may use USoft Binder variables when specifying a value in this field.

Oracle

For Oracle, the connect string may be an alias if this alias can be expanded used on information in the tnsnames.ora file. In many cases, the connect string alias for a locally installed Oracle Express database is

XE

 

An alternative for using an alias is to provide the complete connect string. For example:

( DESCRIPTION =

  ( ADDRESS_LIST =

    ( ADDRESS = (PROTOCOL = TCP)(HOST = COMPUTER_22)(PORT = 1521) )

  )        

  ( CONNECT_DATA = (SERVICE_NAME = XE) ) 

)

 

The advantage of a complete connect string is that it will work if you send the Binder file to a different team member on the same company network who may not have the same alias settings in tnsnames.ora.

For Oracle over SQL*Net TCP/IP version 1, the connect string is of the form:

T:machine-name:database-sid

 

For SQL*Net Version 2, it is of the form:

machine_name database-sid

 

In the Database field, the ORACLE_SID may be offered as a suggestion.

 

SQL Server

For SQL Server, the connect string depends on whether default instances or named instances are used.

If you are using a default instance, the connect string is of the form:

computer-name : database-name

 

The default instance of the SQL Server 2000 database engine operates the same way as the database engines in earlier versions of SQL Server. The default instance is identified solely by the name of the computer on which the instance is running, it does not have a separate instance name. When applications specify only the computer name in their requests to connect to SQL Server, the SQL Server client components attempt to connect to the default instance of the database engine on that computer. This preserves compatibility with existing SQL Server applications.There can only be one default instance on any computer, the default instance can be any version of SQL Server.

If you are using a named instance, the connect string is of the form:

computer-name \ instance-name : database-name

 

All instances of the database engine other than the default instance are identified by an instance name that is specified during installation of the instance. Applications must provide both the computer name and the instance name of any named instance to which they are attempting to connect.

There can be multiple named instances running on a computer, but only the SQL Server 2000 database engine can operate as a named instance. The database engines from earlier versions of SQL Server cannot operate as a named instance.

ODBC

For ODBC, the dropdown list in the Database field may offer sources from the registry as a suggestion.

Derby

An example database connect string for a Derby database (that you could distribute along with the USoft Binder file) is:

jdbc:derby://localhost:{port}/{systemdir}\ExampleBinders\MyDb1;create=true

 

NOTE: In this example, {port} is a user-defined variable that must be set using the Variables project property and {systemdir} is a predefined variable.
collapseOwner

This is where you specify the owner of the tables that you want USoft Binder to access. Leave this field empty if you connect as the owner yourself, i.e., if the tables are in the account of the user you specified. For some RDBMS types this parameter is case specific.

In the Separate Properties for Repository and Application dialog:

•The Repository Owner is the database account where the development repository tables are located. Leave this field empty if you connect as the repository owner yourself.

•The Application Owner is the database account where the application tables to which you want to connect are located. Often, when using separate properties for repository and application, each development team member has an individual application for testing and prototyping, and in this case the Application Owner is the same as the Application User and does not need to be specified.