Installing the IBM Script Portlet V 1.3 on a virtual portal

To install the IBM Script Portlet Version 1.3 on a virtual portal, you must install the library and drag configuration to add virtual portals. There are two alternative procedures depending on the needs of your virtual portal. You can export the Script Portlet Library and DnD page and import them to each virtual portal, or you can run the deploy-paa command again for each virtual portal.

Before you begin

You must install the Script Portlet on your base portal first. Installing the Script Portlet deploys the portlet and creates an IBM® Web Content Manager content library named Script Portlet Library and creates a drag configuration for the web content viewer used to render Script Portlets.

You can install the Script Portlet on your virtual portal by either of two options:

You can export the Script Portlet Library and DnD page and import them to each virtual portal. This process requires more manual steps, but does not risk overwriting virtual portals that already use Script Portlet.
Alternatively, you can run the configuration engine task deploy-paa again for each virtual portal with the forceDeploy option.

To manually import the Script Portlet Library and DnD page to each virtual portal, use the following steps.

Procedure

Exporting and importing the Script Portlet Library and DnD configuration page

Export the Script Portlet Library. To do so, run the following portal configuration engine task:

Windows

ConfigEngine.bat export-wcm-data -DWasPassword=password -DPortalAdminPwd=password -Dexport.libraryname="Script Portlet Library" -Dexport.directory=path

AIX® Linux Solaris

./ConfigEngine.sh export-wcm-data -DWasPassword=password -DPortalAdminPwd=password -Dexport.libraryname="Script Portlet Library" -Dexport.directory=path

Import a copy of the Script Portlet Library into the virtual portal context. To do so, run the following portal configuration engine task. Repeat this task for each virtual portal where you want to use the Script Portlet.
- Windows
```
ConfigEngine.bat import-wcm-data -DWasPassword=password -DPortalAdminPwd=password -Dimport.directory=path -DVirtualPortalContext=virtual portal
    context
```
- AIX Linux Solaris
```
./ConfigEngine.sh import-wcm-data -DWasPassword=password -DPortalAdminPwd=password -Dimport.directory=path -DVirtualPortalContext=virtual portal
    context
```
Note: You must complete this step if you are using Managed Pages. Managed Pages is enabled by default. With Managed Pages, Web Content Manager creates and updates content in the mapped site area. If you do not use Managed Pages, you must manually configure a Web Content Manager context mapping for each portal page where a Script Portlet is used.
Verify that the Script Portlet Library was created. Click the Administration menu icon. Then, click Portal Content > Web Content Libraries.
After installing the Script Portlet on your base portal, use the Manage Pages portlet to select and export the page named Script Portlet Content DnD Configuration. It is located in Content Root > Hidden Pages > DnD Configuration. Do not export the entire page hierarchy.
In your virtual portal, open the WebSphere® Portal Settings Administration portlet and click Import XML. Then click Choose File and select the XML page that you exported in the previous step.
Verify that you imported the configuration correctly by using Manage Pages on your virtual portal. Script Portlet Content DnD Configuration Content Root > Hidden Pages > DnD Configuration