If you are on the receiving side of an exported archive file from a different Portal Studio installation, use the Portal Studio–Deploy dialog box to import portal entities into your Portal Studio installation. You must place the archived XML file that you want to import on the same server as your Portal Studio installation.
Importing a file into Portal Studio
Log in to the Portal Studio as a user that has the StudioAdmin and PortalAdmin role.
Select Build | Portlets from the Portal Studio left pane.
Click Deploy on the Portlet Manager toolbar.
When the Portal Studio–Deploy window displays, click the Import tab.
Complete these fields:
File Name – enter the name of the XML file to import, or click Browse to locate the file using the Choose File dialog box.
Click View to view the XML file contents.
Click Upload to upload the file to Portal Studio. When a prompt confirms that the upload was successful, click OK.
Import Catalog As Active – make the imported catalog the default display catalog. The imported XML document can contain more than one catalog, but only one catalog is marked as the default display catalog—approved and active. If you import this catalog as active, it deactivates the current default catalog and replaces it with the new catalog.
Override Existing Entities – have imported entities (pages, page groups, applications, and agents) replace an equivalent entity with the same name; for example, replace a page with an imported page with the same name. These entities do not use versioning.
Import Entities As Active – import the new entities as active but the catalog as inactive, which makes the imported entities (but not the catalog) available to Portal Interface users.
Set Deferred Update For All Portal Users – indicates whether to notify all portal users of a change in the portal content so that they can refresh their view the next time they log in to the portal.
During the import process, if you do not select Set
Deferred Update For All Portal Users, the Portal Interface user
must perform an Update for each guest page or guest page group.
Click Import. When a prompt confirms that the import was successful, click OK.
Click View Log to review the import operation’s activities.
Click Close to exit the Portal Studio–Deploy window.
Select Build | Catalogs from the Portal Studio left pane.
Select Approved from the Catalog Manager Status menu. If you chose to import a new catalog as active, you should see the catalog in the detail view with a check mark in the Active column.
If you chose to import the catalog as active, click Update on the Catalog Manager toolbar to update Portal Interface on the same application server with the new default display catalog.
When you see confirmation that the operation was successful, click OK.
Log in to Portal Interface.
You can add portlets only to your personal page and page group.
If the page.group global property is turned on, create a page group, then add a new page to that page group.
If the page.group property is turned off, create a new page.
See Appendix A, “Configuring Global Properties,” for more information about setting
the page.group property.
Click Add Portlet. When the Add Portlet window appears, it should display the contents of the new default display catalog.
When you import portal objects (templates, catalogs,
and so on) they maintain their original owner; that is, the Owner
column in the detail view for objects lists the person who originally
created the object, not the person performing the import.
