See
Also
To define a repository
version:
1.
|
From the Repository Manager menu, select Define, Repository
Versions. |
The Repository Versions
window opens.
2.
|
Specify a unique Code for the repository version. |
For example: TRAVEL8_DEV
3.
|
Specify a Repository, or use the lookup button to select one
from the available repository definitions. |
For example: TRAVEL
4.
|
Specify a Version Nr.
for this repository version. This can be any number or code. |
For example: 8.0.2, 1.0 BETA,
DEV, QA, PROD.
5.
|
Specify the USoft Version in which this repository is made.
This can be a USoft 8 or 7.0/7.1 version. |
IMPORTANT:
|
If you plan to export USoft 7.0/7.1 repositories, you have to
specify the path to your USoft 7 installation folder in the
following file once:
|
<usoft version 8 installation folder>\
USoftApplications\RepositoryManager\scripts\us7path.bat
6.
|
You can select the Production Version checkbox to specify that
this repository version is a production version. |
For a production version, the
repository definition is NOT taken from the database, but from
another repository version or release.
In the case of a production
version, specify this other repository version or release by
clicking the button to the right of the Production Version checkbox.
7.
|
Optionally, specify a Description. |
The repository version is now
listed in the catalog.
9.
|
If this repository version is currently stored in a database
account, or if you plan to do so, you can now specify the database
account settings similarly as you would do in USoft Binder: |
·
|
User: The user name
you use when connecting to this repository version. This user must
be able to log on to the repository version. |
For example: TRAVEL_008
·
|
Password: The password
for this user, echoed in asterisks. |
·
|
RDBMS: The RDBMS type.
Choose one from the dropdown list. |
·
|
Database: The connect
string to your database. |
On Oracle, for example, this
can also be a long string like:
(DESCRIPTION=(ADDRESS=(PROTOCOL=TCP)(HOST=cmpxy39)
(PORT=1521))(CONNECT_DATA=(SID=P)))
·
|
Special: This is where
you can list any additional startup options when exporting this
repository version. For example: |
-ddfile -owner DBOWNER
10.
|
Optionally, select the Current Release & Backup checkbox to
generate a CURR(ent) release with backup facility for this version,
including a backup comparison. |
This CURR(ent) release can be
used to export the current version of the repository. If a
CURR(ent) release is exported, first a copy is made of the existing
release (if any). It is copied to a document with name:
<rep
version>_CURR.old.xml
The backup comparison
compares the current (= most recently exported) release with the
previously exported release. This can be used within daily
scheduled task sets, for example to view last day's changes.
If the Current Release &
Backup checkbox is cleared, the generated release and backup
comparison are automatically deleted.
|