Directory structure

|This section describes the program directory structure |and the directory structure for SSL files that was implemented in |version 8.5.1. This section applies if you are upgrading from version |8.3 or 8.4. If you are upgrading from version 8.5 or 8.5.1, this directory |structure already exists.

Program directory

When you upgrade the Dynamic Workload Console to the current version, a new program directory structure is created. During the upgrade process, components of the Dynamic Workload Console are moved from the old directory structure and then updated into the new directory structure. The Dynamic Workload Console program files remain in the original installation directory.

If you have any custom configurations (for example, custom scripts or backup processes) existing in your Dynamic Workload Console structure, you must update them so that they work in the new directory structure.

For example, if you originally installed the Dynamic Workload Console into the default directory c:\Program Files\IBM\webui\, you have a directory structure as follows:

c:\Program Files\IBM\TWA\webui\appserver
c:\Program Files\IBM\TWA\webui\wastools
c:\Program Files\IBM\TWA\webui\_webuiutils
c:\Program Files\IBM\TWA\webui\_webuiuninst
c:\Program Files\IBM\TWA\webui\_jvm

When you upgrade the Dynamic Workload Console, the new directory structure is:

c:\Program Files\IBM\TWA\eWAS
c:\Program Files\IBM\TWA\wastools
c:\Program Files\IBM\TWA\TDWC
c:\Program Files\IBM\TWA\TDWC\_tdwcscripts
c:\Program Files\IBM\TWA\TDWC\_tdwcuninst
c:\Program Files\IBM\TWA\TDWC\_tdwcutils
c:\Program Files\IBM\TWA\TDWC\_jvm

The new directory structure includes new embedded WebSphere Application Server tools that are common to Tivoli Workload Scheduler.

Directory for SSL files

When you upgrade to the current version, a new directory for SSL files is created. The following describes the old and new directory structures.

Note:
Before upgrading you must backup any customized SSL keys and copy them to the default installation path.

After upgrading, the old SSL files stored in PCKS12 format are imported into new SSL files in JKS format.

The old PCKS12 files are also copied to the new directory as a backup. The key.p12 file becomes TWSServerKeyFile.jks. The trust.p12 files becomes TWSServerTrustFile.jks.

Previous directory structure
  • TWSInstallationPath\appServer\profiles\webuiprofile\config\cells\CellName\nodes\NodeName\key.p12
  • TWSInstallationPath\appServer\profiles\webuiprofile\config\cells\CellName\nodes\NodeName\trust.p12
|New directory structure
| |
    |
  • TWSInstallationPath\eWAS\profiles\TIPProfile\config\cells\TIPNode\nodes\TIPCell\key.p12
    • |
  • TWSInstallationPath\eWAS\profiles\TIPProfile\config\cells\TIPNode\nodes\TIPCell\trust.p12
    • |
  • TWSInstallationPath\eWAS\profiles\TIPProfile\etc\TWSServerKeyFile.jks
    • |
  • TWSInstallationPath\eWAS\profiles\TIPProfile\etc\TWSServerTrustFile.jks
|
|
Note:
|
The files key.p12 and trust.p12 are not used by the Dynamic Workload Console, but |are backed up.