+

Search Tips   |   Advanced Search

Directory structure

This topic shows the naming conventions used to denote the location of files on the servers and the types of resources we can find in those directories.

  1. WebSphere Portal root directory (PortalServer_root)
  2. WebSphere Portal profile directory (wp_profile_root)
  3. WebSphere Portal Configuration Engine root directory (ConfigEngine_root)
  4. WebSphere Portal Configuration Engine profile directory
  5. WebSphere Application Server directory structure (AppServer_root)
  6. Lotus Domino directory structure (domino_server_root and domino_data_root)
  7. Directories for languages


WebSphere Portal root directory (PORTAL_HOME)

Throughout this documentation, the installation location for the portal server component of IBM WebSphere Portal is noted as PORTAL_HOME.

For the IBM i platform, an additional variable is used to indicate the user data directory. The user data directory is noted as PortalServer_root_user.

The following information shows the default location if it is not otherwise specified during installation:


WebSphere Portal profile directory (wp_profile_root)

Throughout this documentation, the profile location is noted as wp_profile_root. The following information shows the default profile location if another location it is not specified during installation:

wp_profile is the default profile name but is used here as an example since there may be multiple profiles with self described or incremental names (for example, wp_profile1, wp_profile2, and so on).


WebSphere Portal Configuration Engine root directory (ConfigEngine_root)

Throughout this documentation, the installation location for the Configuration Engine component is noted as ConfigEngine_root.


WebSphere Portal Configuration Engine profile directory

The Configuration Engine profile directory is the location of the ConfigEngine task.

wp_profile is the default profile name but is used here as an example since there may be multiple profiles with self described or incremental names (for example, wp_profile1, wp_profile2, and so on).


WebSphere Portal directory structure after installation

WebSphere Portal has the following directory structure after installation:

On the Linux and IBM i operating systems, all directories are r/o.

PORTAL_HOME          Root directory for WebSphere Portal  |
 +-- ap
 |
 +-- base
 |
 +-- bin                    WebSphere Portal tools
 |
 +-- bp
 |
 +-- doc                    Javadoc and sample XMLAccess input files
 |
 +-- ext                    
 |
 +-- filesForDmgr            
 |
 +-- installer  
 |
 +-- jcr                    Resources for the Content Repository
 |
 +-- license                WebSphere Portal license agreement
 |
 +-- lwo   
 |
 +-- lwp04.infra        
 |
 +-- people                 
 |
 +-- prereq                 
 |
 +-- prereqs.infra         
 |
 +-- profileTemplates          
 |
 +-- properties            
 |
 +-- pzn                    
 |
 +-- pzn.ext                
 |
 +-- search                 
 |
 +-- shared                 Shared resources, including runtime JARs, TLDs, 
 |                          and other resources. 
 |                          The /app subdirectory is the application server's 
 |                          WPSLib shared library for WebSphere Portal  |
 +-- solutionInstaller
 +-- theme 
 |
 +-- ui 
 |
 +-- version                Version information for various components
 |
 +-- wcm                    Source Web application files for web content manager
 |
 +-- wps.properties                   


WebSphere Application Server directory structure (APPSERVER_ROOT)

Throughout this documentation, the install location for WebSphere Application Server is noted as APPSERVER_ROOT

The following table shows the WebSphere Application Server installation directory:

IBM i

The install location for WebSphere Application Server is noted as app_server_root and refers to the UserData path, unless otherwise specified in the topic where you see it. The profile_root following variable refers to the name given to the WebSphere Application Server profile in use.


WebSphere Application Server profile directory

Throughout this documentation, the location for the WebSphere Application Server profiles is noted as was_profile_root.


Lotus Domino directory structure (domino_server_root and domino_data_root)

Throughout this documentation, the install location for the IBM Lotus Domino server software is noted as domino_server_root.

For IBM i, the install location for the Lotus Domino server software is noted as domino_server_root and refers to the ProdData path, unless otherwise specified in the topic where you see it.

The following information shows the default location if it is not otherwise specified during installation:

The Lotus Domino server data directory is noted as domino_data_root.

For IBM i, The Lotus Domino server data directory is noted as domino_data_root and refers to the UserData path, unless otherwise specified in the topic where you see it.

The following information shows the default location of the Domino data directory if it is not otherwise specified during installation:


Directories for languages

The following shows the languages supported by WebSphere Portal and the directories used for storing locale-specific resources. These directories are used in portlet Web application directories and in the WebSphere Portal enterprise application (themes, skins, and other Web application resources).

Language (locale) Directory
Arabic /ar
Danish /da
English /en
French /fr
Italian /it
Kazakh /kk
Korean /ko
Polish /pl
Romanian /ro
Slovenian /sl
Turkish /tr
Traditional Chinese /zh_TW
Catalan /ca
German /de
Spanish /es
Croatian /hr
Hebrew /iw
Dutch /nl
Portuguese /pt
Russian /ru
Swedish /sv
Ukrainian /uk
Czech /cs
Greek /el
Finnish /fi
Hungarian /hu
Japanese /ja
Norwegian /no
Brazilian Portuguese /pt_BR
Slovak /sk
Thai /th
Simplified Chinese /zh


Parent: Reference