Running the deploy-paa task for each virtual portal
If you do not want to export the Script Portlet Library and DnD page and import them to every virtual portal, you can run the portal configuration engine deploy-paa task again on each virtual portal on which you want to install Script Portlet.
About this task
When you run the deploy-paa task with the forceDeploy option, as you do in this procedure, the application EAR for Script Portlet on the base portal is redeployed, which can temporarily make the Script Portlet unavailable to users of the Script Portlet who are using any portal on that server. It can also reset Script Portlet author role mappings, or groups that are allowed to use the editor, that you set previously. If these side effects interrupt the Script Portlet on your base portal or other virtual portals on the same server, then it is better to use the alternative procedure in Installing on a virtual portal to export and import the Script Portlet Library and DnD Configuration page to each additional portal, instead of running the additional deploy-paa commands described here.