Defining the Library directory for properties files

The Library directory entry in a remote portal server configuration is required for WebSphere® Portal v5.1 servers; it is optional, but recommended for WebSphere Portal v5.0 servers.

When you define a WebSphere Portal Server Attach server, or a WebSphere Portal for Import, Export & Deploy server, the Library directory entry on the Publishing Settings page defines the location of the remote server's properties files, which are used for translated strings. Properties files are in the portal_installation_directory/shared/app/nls directory of the remote portal server.

When you import a portal site, you must have copy or FTP access to the websphere_installation_directory/installedApps/node/wps.ear directory on the remote server. For WebSphere Portal v5.1 servers, you must also have copy or FTP access to the portal_installation_directory/shared/app/nls directory of the remote server. The access method (copy or FTP) must be the same for both directories; you cannot use FTP for one directory and copy for another.

When you deploy a portal site, if you have write access to the Library directory, the workbench will automatically deploy the property files to the target portal server.

If you are importing or deploying to a WebSphere Portal v5.1 server, the Library directory must be specified. In this version of WebSphere Portal, the import operation extracts the contents of portal_installation_directory/shared/app/wp.ui.jar into the project and then accesses the portal_installation_directory/shared/app/nls directory and retrieves the *.properties files from it.

If you are importing or deploying to a WebSphere Portal v5.0 server, it is recommended that you specify a Library directory. For this version of WebSphere Portal, if a Library directory is specified, the workbench automatically imports or deploys the properties files to and from the portal_installation_directory/shared/app/nls directory. If you do not specify a Library directory, you must manually copy the properties files, as described below.

To manually copy property files for import or deploy operations using WebSphere Portal v5.0,
  • To manually copy properties files before an import operation, copy the contents of the portal_installation_directory/shared/app/nls directory of the portal server to the websphere_installation_directory/installedApps/node/wps.ear/wps.war/WEB-INF/classes/nls directory of the portal server. Then proceed with the import operation.
  • To manually copy properties files after an import operation,
    1. Copy the property files from the portal_installation_directory/shared/app/nls directory of the portal server to the Project/PortalContents/WEB-INF/classes/nls directory in the workspace.
    2. Copy these same files to the Project/JavaSource/nls directory in the workspace.
    3. Refresh the project.
  • To manually copy properties files after a deploy operation, copy the contents of websphere_installation_directory/installedApps/node/wps.ear/wps.war/WEB-INF/classes/nls to portal_installation_directory/shared/app/nls on the remote system after the deploy operation completes.
Related tasks
Defining servers for publishing or importing portals
Defining remote servers for testing portals
Importing portal sites

(C) Copyright IBM Corporation 2002, 2005. All Rights Reserved.