Importing portal sites
Use the Import wizard to retrieve an existing portal site from a WebSphere® Portal server.
To create a new portal project, it is recommended that you import an existing portal site from WebSphere Portal server into Rational® Software Delivery Platform. Importing is also useful for updating the configuration of a project that already exists in your workspace. While importing from Websphere Portal Server 6.1, the static pages defined on the server also get imported with their contents.
The portal site configuration on WebSphere Portal server contains the following resources: the global settings, the resource definitions, the portal content tree, and the page layout. Importing these resources from WebSphere Portal server to Rational tools overwrites duplicate resources within the existing portal project. Non-duplicate resources from the server configuration are copied into the existing portal project. Likewise, resources that are unique to the portal project are not affected unless you choose the Delete project on overwrite option in the Import wizard.
Rational tools use the XML configuration interface to import a portal site configuration, and optionally retrieves files under the Web application directory. When creating a new portal project, retrieving files is mandatory. For more details on defining a Portal server for import, see Defining servers for publishing or importing portals.
- Select
File | Import.
- Within the Select page, click
Portal for your import source; then click Next.
- Within the Import Portal Project page, select a portal server that you want to use. If the server dialog box is empty, click New to define a server. For more information on defining a server for import, refer to Defining servers for publishing or importing portals.
- From the
Portal project combo box, either choose the name of the portal project or enter a name for your portal project for import.
- Under
Import Options, choose whether you want to import the configuration and files, or the configuration only.
If you choose to import the configuration and files, the files under the Web application directory are imported. The files include the JSP, CSS, and image files for themes and skins. Also within the
Import Options dialog box is a check box labeled
Delete project on overwrite. This option is only active if you are importing to an existing portal project. If you select this option, the existing portal project and all of its artifacts are completely deleted before the overwrite.
Notes and Limitations
- The Portal configuration in an imported project does not contain all of the configuration information from the Portal server. If you deploy the imported project to another server, it won't have complete configuration information.
- If the portal server has more than one label or page of the same ordinal, the order of top level labels and pages in the newly imported portal project may be different from the order that was on the portal server.
- If JSP files or Java™ classes within the portal server refer to classes that are in external JAR files, there may be compilation errors after the project is imported. You need to import any external JAR files, which can be located in the
websphere_installation_directory/lib or
portal_installation_directory/shared/app directories on the remote portal server, to your development machine, and add them to Java build path of your portal project. To set the Java build path, follow these steps:
- From the Project Explorer view, highlight the project, right-click and select
Properties.
- In the left pane, select
Java Build Path.
- In the right pane, select the
Libraries tab.
- Add the referenced JAR.
- Click OK to save the configuration.
Related tasks
Defining servers for publishing or importing portals
Related reference
Related information