References in product information to app_server_root, profile_root,
and other directories imply specific default directory locations.
This topic describes the conventions in use for WebSphere® Application
Server.
Default product locations (distributed)
The
following file paths are default locations. You can install the product
and other components or create profiles in any directory where you
have write access. Multiple installations of WebSphere Application
Server Network Deployment products
or components require multiple locations. Default values for installation
actions by root and non-root users are given. If no non-root values
are specified, then the default directory values are applicable to
both root and non-root users.
- app_client_root
-
Table 1. Default installation root
directories for the WebSphere Application Client. This table shows the default installation root directories
for the WebSphere Application Client.
User |
Directory |
Root |
/usr/IBM/WebSphere/AppClient (Java EE Application client only)
/opt/IBM/WebSphere/AppClient (Java EE Application client only)
C:\Program Files\IBM\WebSphere\AppClient
|
Non-root |
user_home/IBM/WebSphere/AppClient (Java EE Application client only)
C:\IBM\WebSphere\AppClient
|
- app_server_root
-
Table 2. Default installation directories
for WebSphere Application Server. This
table shows the default installation directories for WebSphere Application
Server Network Deployment.
User |
Directory |
Root |
/usr/IBM/WebSphere/AppServer
/opt/IBM/WebSphere/AppServer
C:\Program Files\IBM\WebSphere\AppServer
|
Non-root |
user_home/IBM/WebSphere/AppServer
C:\IBM\WebSphere\AppServer
|
- cip_app_server_root
- A customized installation package (CIP) is an installation
package created with IBM® WebSphere Installation Factory that contains
a WebSphere Application Server or feature pack product bundled with
one or more maintenance packages, an optional configuration archive,
one or more optional enterprise archive files, and other optional
files and scripts.
Table 3. Default installation
root directories for a CIP. This table shows the default
installation root directories for a CIP.
User |
Directory |
Root |
/usr/IBM/WebSphere/AppServer
/opt/IBM/WebSphere/AppServer
C:\Program Files\IBM\WebSphere\AppServer
|
Non-root |
user_home/IBM/WebSphere/AppServer
C:\IBM\WebSphere\AppServer
|
- component_root
- The component installation root directory is any installation
root directory described in this topic. Some programs are for use
across multiple components. In particular, the Update Installer for WebSphere Software is for use with WebSphere Application Server Network
Deployment, Web server plug-ins, the Application Client, and
the IBM HTTP Server. All of these components are
part of the product package.
- gskit_root
- IBM Global Security Kit (GSKit) can now be installed
by any user. GSKit is installed locally inside the installing product's
directory structure and is no longer installed in a global location
on the target system. The following list shows the default installation
root directory for Version 7 of the GSKit, where product_root is
the root directory of the product that is installing GSKit, for example IBM HTTP
Server or the Web server plug-in.
product_root/gsk7
product_root\gsk7
- if_root
- This directory represents the root directory of the IBM WebSphere Installation Factory. Because
you can download and unpack the Installation Factory to any directory
on the file system to which you have write access, this directory's
location varies by user. IBM WebSphere Installation Factory is an Eclipse-based
tool which creates installation packages for installing WebSphere Application
Server in a reliable and repeatable way, tailored to your specific
needs.
- iip_root
- This directory represents the root directory of an integrated
installation package (IIP) produced by the IBM WebSphere Installation Factory. Because
you can create and save an IIP to any directory on the file system
to which you have write access, this directory's location varies by
user. An IIP is an aggregated installation package that can include
one or more generally available installation packages, one or more
customized installation packages (CIPs), and other user-specified
files and directories.
- profile_root
-
Table 4. Default profile directories. This table shows the default directories for a profile named profile_name on
each distributed operating system.
User |
Directory |
Root |
/usr/IBM/WebSphere/AppServer/profiles/profile_name
/opt/IBM/WebSphere/AppServer/profiles/profile_name
C:\Program Files\IBM\WebSphere\AppServer\profiles\profile_name
|
Non-root |
user_home/IBM/WebSphere/AppServer/profiles/
C:\IBM\WebSphere\AppServer\profiles\
|
- plugins_root
-
Table 5. Default installation root
directories for the Web server plug-ins. This table
shows the default installation root directories for the Web server
plug-ins for WebSphere Application Server.
User |
Directory |
Root |
/usr/IBM/WebSphere/Plugins
/opt/IBM/WebSphere/Plugins
C:\Program Files\IBM\WebSphere\Plugins
|
Non-root |
user_home/IBM/WebSphere/Plugins
C:\IBM\WebSphere\Plugins
|
Note: If the Web server plug-ins are installed as part of
the IBM HTTP Server installation, the installation location is inside
the IBM HTTP Server installation location. For example:
/opt/IBM/HTTPServer/Plugins
- updi_root
-
Table 6. Default installation root
directories for the Update Installer for WebSphere Software. This table shows the default installation root directories
for the Update Installer for WebSphere Software.
User |
Directory |
Root |
/usr/IBM/WebSphere/UpdateInstaller
/opt/IBM/WebSphere/UpdateInstaller
C:\Program Files\IBM\WebSphere\UpdateInstaller
|
Non-root |
user_home/IBM/WebSphere/UpdateInstaller
C:\IBM\WebSphere\UpdateInstaller
|
- web_server_root
Table 7. Default installation root
directories for the IBM HTTP Server. This
table shows the default installation root directories for the IBM HTTP
Server.
User |
Directory |
Root |
/usr/IBM/HTTPServer
/opt/IBM/HTTPServer
C:\Program Files\IBM\HTTPServer
|
Non-root |
user_home/IBM/HTTPServer
C:\IBM\HTTPServer
|