3.1.2 Directory structure and default profilesIf you have worked with previous versions of WAS, you will notice a difference in the directory structure. First, all packages (Base, Express, and ND) specify the same default root directory during installation. For example, in Windows installations, this is commonly c:\Progam Files\IBM\WebSphere\AppServer. In this IBM Redbook, we refer to this root directory as the <was_home> directory. In addition to the traditional directories under the <was_home> directory (bin, config, installedapps, and so on), you now have a profiles directory containing a subdirectory for each profile you create and allow to use the default home location. The directory structure for each profile resembles the primary structure. In other words, there is a bin, config, installedApps, and other directories required for a unique run time under each profile. For example, if you installed on a Windows system, and created a profile named AppSrvr01, you would normally see a directory structure like that shown in Figure 3-3.
Figure 3-3 Directory structure However, profiles can be stored in any folder, so we suggest storing them in a more friendly structure (by default, there are at least six levels). We refer to the root of each profile directory (by default <was_home>/profiles/profile) as <profile_home>. Why do we emphasize this point? If you enter commands while in the <was_home>/bin directory, they are executed against the run time defined by the default profile. The default profile is determined by the following:
To make sure command line operations are executed for the correct run time, do one of two things:
|
