Directory structure
This topic shows the naming conventions used to denote the location of files on the servers and the types of resources you can find in those directories.
- WebSphere Portal root directory (PORTAL_HOME)
- WebSphere Portal profile directory (WP_PROFILE)
- WAS directory structure (WAS_HOME)
- Lotus Domino directory structure (domino_server_root and domino_data_root)
- Directories for languages
WebSphere Portal root directory (PORTAL_HOME )
Throughout this documentation, the installation location for the portal server component of 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 PORTAL_HOME_user .
The following information shows the default location if it is not otherwise specified during installation:
AIX®/usr/IBM/WebSphere/PortalServer
Linux™/opt/IBM/WebSphere/PortalServer
Solaris/opt/IBM/WebSphere/PortalServer
Windows™C:/IBM/WebSphere/PortalServer
IBM i
- portal_server_root (ProdData)
- /QIBM/ProdData/WebSphere/PortalServer/V7/<product offering>/Portal
- Where <product offering> is Server, Content, or Express
- PORTAL_HOME_user (UserData)
- WAS v7.0 for Base and Express:
- /QIBM/UserData/WebSphere/AppServer/V7/Base/profiles/wp_profile/PortalServer
- WAS v7.0 for Network Deployment:
- /QIBM/UserData/WebSphere/AppServer/V7/nd/profiles/wp_profile/PortalServer
WebSphere Portal profile directory (WP_PROFILE)
Throughout this documentation, the profile location is noted as WP_PROFILE. The following information shows the default profile location if another location it is not specified during installation:
AIX/usr/IBM/WebSphere/wp_profile
Linux/opt/IBM/WebSphere/wp_profile
Solaris/opt/IBM/WebSphere/wp_profile
WindowsC:/IBM/WebSphere/wp_profile
IBM i
- WAS v7.0 for Base and Express:
- /QIBM/UserData/WebSphere/AppServer/V7/Base/profiles/wp_profile
- WAS v7.0 for Network Deployment:
- /QIBM/UserData/WebSphere/AppServer/V7/nd/profiles/wp_profile
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 on Windows and UNIX
WebSphere Portal has the following directory structure after installation.Directory structure Root directory for WebSphere Portal | +-- ap | +-- base | +-- bin WebSphere Portal tools | +-- bp | +-- cmapi | +-- doc Javadoc and sample XMLAccess input files | +-- ext | +-- filesForDmgr | +-- firstSteps First Steps Launcher (Windows and Linux only) | +-- installableApps Source portlet application files prior to deployment | +-- installer | +-- jcr Resources for the Content Repository | +-- license WebSphere Portal license agreement | +-- log WebSphere Portal log files | +-- lwo | +-- lwp04.infra | +-- package Response files and utilities for install | +-- pcc.api | +-- pcc.impl | +-- people | +-- prereq | +-- prereqs.infra | +-- 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 | +-- theme | +-- ui | +-- uninstall Resources for uninstalling WebSphere Portal | and components | +-- version Version information for various components | +-- wcm Source Web application files for web content management | +-- wps.properties
WebSphere Portal directory structure after installation on i
WebSphere Portal has the following directory structure after the installation:ProdData's Directory structure Root directory for WebSphere Portal | +-- depcheck Dependency checker files | +-- dist Install binary files | +-- doc WebSphere Portal | Information Center and Javadoc | +-- img Image files | +-- license WebSphere Portal license agreement | +-- log Log files | +-- package Response files and utilities for install | +-- uninstall Resources for uninstalling | WebSphere Portal and components UserData's Directory structure Root directory for WebSphere Portal user's data | +-- ap | +-- base | +-- bin WebSphere Portal tools | +-- bp | +-- cmapi | +-- config | +-- deployed | +-- derby | +-- doc WebSphere Portal | Information Center and JavaDoc | +-- ext | +-- installableApps WAR files prior to deployment | +-- installer | +-- jcr Resources for the Content Repository | +-- log Log files | +-- lwo | +-- lwp01.infra | +-- META-INF | +-- migration Scripts used to assist in migrating from previous releases | of WebSphere Portal +-- package Response files and utilities for install | +-- pcc.api | +-- people | +-- prereq | +-- prereqs.infra | +-- pzn Personalization runtime and resources | +-- 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 | +-- theme | +-- ui | +-- version Version information for various components | +-- wizard
WAS directory structure (WAS_HOME )
Throughout this documentation, the install location for WAS is noted as WAS_HOMEThe following table shows the WAS installation directory:
IBM iThe install location for WAS 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 variable below refers to the name given to the WAS profile in use.
WAS profile directory
Throughout this documentation, the location for the WAS 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 Dominoserver software is noted as domino_server_root .For 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:
AIX/opt/IBM/Lotus/
Linux/opt/IBM/Lotus/
Solaris/opt/IBM/Lotus/
WindowsC:/Lotus/Domino
IBM i
The Lotus Domino server data directory is noted as domino_data_root .
- domino_server_root (ProdData)
- /QIBM/ProdData/Lotus/DOMINOrelease_number
For 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:
AIX/opt/IBM/Lotus/Domino/data
Linux/opt/IBM/Lotus/Domino/data
Solaris/opt/IBM/Lotus/Domino/data
WindowsC:/Lotus/Domino/Data
IBM i
- domino_data_root (UserData)
- WAS for Base and Express:
- /QIBM/USERDATA/LOTUS/NOTES
- WAS for Network Deployment:
- /QIBM/USERDATA/LOTUS/NOTES
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 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
removed wps.war directory details as it is read only - d277688