![]() |
![]() |
[ Bottom of Page | Previous Page | Next Page | Contents ]
V2.1 contains a new catalog manager. The most important difference is that it now acts directly on the master catalog, so there is no need for the importing and exporting activities performed in V1.1.1. You still import a new IBM catalog from time-to-time, but any changes you make to products using the catalog manager are saved directly into the administration server database.
The catalog itself has also changed quite significantly. The details are as follows:
Product name | Version |
---|---|
Lotus(R) Notes(R) | 3.5 |
The migration behaves differently, depending on whether product in the V1.1.1 COMPONENT table has a version field that is in a valid format for V1.1.1:
Thus, for example, for the above entry for Lotus Notes, version 3.5 it would create the following entries in the V2.1 COMPONENT table:
Product | Version | Tree level |
---|---|---|
Lotus Notes | * | 1 |
Lotus Notes | 3.* | 2 |
Lotus Notes | 3.5.* | 3 |
Where, the Tree level value has the following meaning:
In this example, a license specifically assigned to Lotus Notes, version 3.5 would be assigned to the release entity.
Product | Version |
---|---|
Lotus Notes | Beta 3.5 |
Product | Version | Tree level |
---|---|---|
Lotus Notes | * | 1 |
Lotus Notes | Beta 3.5.* | 2 |
Lotus Notes | Beta 3.5 | 3 |
There are some additional rules:
Any other changes that you may observe will come from the IBM catalog that you have imported, where the version field may have been changed by IBM into the valid structure.
The following are some examples:
Version 1.1 | Version 2.1 | Notes | |||
---|---|---|---|---|---|
Product | Version | Product | Version | Tree level | |
$tock Exchange 32 | 2.0 | $tock Exchange 32 | * | 1 | This is a product in the IBM catalog with a valid version. |
$tock Exchange 32 | 2 | 2 | |||
$tock Exchange 32 | 2.0.* | 3 | |||
IBM DB2 UDB Enterprise Edition for HP | 7.2.5 | IBM DB2 UDB Enterprise Edition for HP | * | 1 | This is a product in the IBM catalog with a valid version. |
IBM DB2 UDB Enterprise Edition for HP | 7.* | 2 | |||
IBM DB2 UDB Enterprise Edition for HP | 7.2.* | 3 | |||
123-Talk |
1.2 2.0 |
123-Talk | * | 1 | This is a product in the IBM catalog with 2 valid versions. |
123-Talk | 1.* | 2 | |||
123-Talk | 2.* | 2 | |||
123-Talk | 1.2.* | 3 | |||
123-Talk | 2.0.* | 3 | |||
Accounting | B.10.10 | Accounting | * | 1 | This is a product that has had its version number changed when the new IBM catalog was imported. The new version number is "10.1.*", and so is in a valid format, even though the old catalog entry had a non-valid format. |
Accounting | 10.* | 2 | |||
Accounting | 10.1.* | 3 | |||
- | - | Microsoft Windows Notepad | * | 1 | This is a product generated by the migration because another product had a module associated with it that the migration recognized as belonging to a product in the IBM catalog. |
Microsoft Windows Notepad | 4.* | 2 | |||
Microsoft Windows Notepad | 4.0.* | 3 | |||
myApplication1 | 1.1 | myApplication1 | * | 1 | This is a custom product with a valid version number. |
myApplication1 | 1.* | 2 | |||
myApplication1 | 1.1 | 3 | |||
myApplication2 | B 1.1 | myApplication2 | * | 1 | This is a custom product with a non-valid version number. |
myApplication2 | B 1.1.* | 2 | |||
myApplication2 | B 1.1 | 3 | |||
myApplication3 |
1.2.1 1.2.3 1.2.4B |
myApplication3 | * | 1 | This is a custom product with 2 versions in valid formats and one version in a non-valid format. |
myApplication3 | 1.* | 2 | |||
myApplication3 | 1.2.4B.* | 2 | |||
myApplication3 | 1.2.1 | 3 | |||
myApplication3 | 1.2.3 | 3 | |||
myApplication3 | 1.2.4B | 3 |
When IBM catalog entries are merged, if the entitlement settings are the same, the merged entry will have that value. However, if the entitlement settings on the different merged products are not the same, the following decisions are made:
Conflicting entitlement settings | Values in V1.1.1 | Value given to merged entries in V2.1 |
---|---|---|
Software Monitoring | If all values are No | No |
If at least one value is Yes | Yes | |
License control | If all values are User-defined | User-defined |
If at least one value is Default | Default | |
Run offline | If all values are No | No |
If at least one value is Yes | Yes | |
Server response | If all values are Required | Required |
If at least one value is Not required | Not required |
Similar sets of non-IBM catalog entries are not collapsed. They are migrated to the new catalog just as they are, because each entry may have a different license or be associated with different modules, that cannot be merged.
[ Top of Page | Previous Page | Next Page | Contents ]