CAA V5 Encyclopedia

Managing Your Installed CAA V5 APIs

Abstract

When installing CAA APIs, three new tab pages are added to the Software Management tool. They allow you to get information and manage the CAA APIs you have installed.

Getting the List of Installed Configurations and Products
Checking Your Installation Integrity
Committing or Rolling Back Service Packs
Running Software Management Tools in Batch Mode
In Short

To get the Software Management dialog box:

With Windows, either:
- Click Start, point to Programs, then to the product line you have installed, that is CATIA, DELMIA, or ENOVIA, point to Tools and click Software Management V5R19, possibly suffixed with the identifier you have entered when installing the run time part (for example Software Management V5R19_INSTALL2)
- Run InstallRoot\intel_a\code\bin\CATSoftwareMgt.exe
  where InstallRoot is the directory in which you have installed the run time part or the product line.
With UNIX:
1. Log on as root or end user
2. Enter the command:
```
$InstallRoot/$OS/code/command/catstart -run "CATSoftwareMgt"
```
  where:
  - InstallRoot is the directory in which you have installed the run time part or the product line
  - OS is the directory containing the installed code
    - aix_a for AIX
    - hpux_b for HP-UX
    - solaris_a for Solaris.

Getting the List of Installed Configurations and Products

The CAA tab page lists:

The solutions whose CAA APIs are installed
The products whose CAA APIs are installed.

[Top]

Checking Your Installation Integrity

This checks the overall integrity of your software.

There are three integrity check levels:

Level 1: only control files are checked. The quickest
Level 2: checks existence of all installed files
Level 3: checks existence and validity of all installed files. May take several minutes.

The message:

Integrity is OK

confirms there is no integrity problem. However, when the message:

Integrity is KO

appears, your installation has been corrupted (for example, some files are missing), it will be followed by troubleshooting information helping you to identify the problem.

When running a level 3 integrity check on a remote computer from a Windows client, a read error may occur on several files due to a saturation problem.

These errors may cause the following message to appear:

unable to open this file in reading mode

The problem may be resolved by deactivating the cache of the network redirector on the client computer, by modifying the following registry key as follows:

Open the registry at the following location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Lanmanworkstation\parameters

Modify the following value:

Value name: UtilizeNTCaching
Data type: REG_DWORD
Data: 0

Please exercise extreme caution when editing the registry. It is only recommended for advanced users with the proper authorization: deactivating the network cache may cause the computer's performance on the local network to deteriorate.

[Top]

Committing or Rolling Back Service Packs

Click Commit to commit a Service Pack, or Rollback to uninstall the service pack and restore the previous level.

Commit and Rollback Rules

Keep the following rules in mind when committing and rolling back service packs:

If you install a GA level, then "Service Pack 1", and then intend to install "Service Pack 2", you must commit "Service Pack 1" before installing "Service Pack 2"
Let's assume you install a GA level, then "Service Pack 1", and commit the service pack; if you then add configurations or products to your installation, you will be prompted at the end of the installation to reinstall "Service Pack 1"; when you reinstall "Service Pack 1", the service pack is committed automatically
You always need to commit the run time part of the configurations and products before the CAA APIs part, and conversely roll back the CAA APIs part before the run time part.

You can also choose to commit a service pack automatically during service pack installation. The consequences of choosing to automatically commit a service pack at installation are:

The service pack overwrites any previous level (GA or service pack): if you have already decided to commit the new service pack, and you do not want to keep the previous version, this allows you to save disk space
Once you have automatically committed the service pack, you cannot roll back to the previous level (GA or service pack)
When you add products after automatically committing a service pack, the new software is also automatically committed.

If running processes are detected in the installation directory when you choose the Rollback option, you will be prompted to kill running processes.

[Top]

Running Software Management Tools in Batch Mode

You can run the Software Management tools in batch mode as follows:

With Windows:
- Run InstallRoot\intel_a\code\bin\CATSoftwareMgtB.exe -option
  where InstallRoot is the directory in which you have installed the run time part or the product line and -option is one of the options described below
With UNIX:
1. Log on as root or end user
2. Enter the command:
```
InstallRoot/OS/code/command/catstart -run "CATSoftwareMgtB -option"
```
  where:
  - InstallRoot is the directory in which you have installed the run time part or the product line
  - OS is the directory containing the installed code
    - aix_a for AIX
    - hpux_b for HP-UX
    - solaris_a for Solaris
  - -option is one of the options described below

The available options are:

Option	Meaning
`-L`	To get the list of installed configurations and products
	To check your installation integrity
`-caaI1 or -caaI`	Level 1 integrity: only control files are checked (quickest)
`-caaI2`	Level 2 integrity: existence of all installed files are checked
`-caaI3`	Level 3 integrity: existence and validity of all installed files are checked (may take several minutes)
	To commit or roll back Service Packs
`-caaR`	Roll back Service Packs
`-caaC`	Commit Service Packs

[Top]

In Short

Using the Software Management dialog box, you can:

Get information about the configurations and products whose CAA APIs are installed
Check the installed configurations and products integrity
Commit of roll back Service Packs

[Top]

History

Version: 1 [Aug 2002]	Document created
[Top]