Script Portlet installation in WebSphere Portal 8.0.0.1 CF11 or on Portal V8.5

I wanted to install Script Portlet into my local WebSphere Portal instance to explore this further and so I followed following steps. To work with Script portlet, you should have the WebSphere Portal 8.0.0.1 CF11 or Portal V8.5.


2. Un-archive the above downloaded file locally and this should contain the “scriptportlet-app-x.x-SNAPSHOT.paa” paa file.

3. Go to your Portal profile ConfigEngine directory <WAS_HOME>/<wp_profile>/ConfigEngine and execute following ConfigEngine install-paa command –

In Linux or AIX:
./ConfigEngine.sh install-paa -DPAALocation=<paa_file_location> -DWasPassword=password -DPortalAdminPwd=<password>
Once above install-paa command executed successfully, then execute deploy-paa command as below –
./ConfigEngine.sh deploy-paa -DappName=scriptportlet-app -DWasPassword=password -DPortalAdminPwd=password

In Windows:
ConfigEngine.bat install-paa -DPAALocation=<paa_file_location> -DWasPassword=<password> -DPortalAdminPwd=<password>
Once above install-paa command executed successfully, then execute deploy-paa command as below –
ConfigEngine.bat deploy-paa -DappName=scriptportlet-app -DWasPassword=password -DPortalAdminPwd=password

4. Now exclude the Script portlet from Portal Development Mode applications –
a.     Open the wp.base_TargetMapExclList.properties file from <WAS_HOME>/<wp_profile>//PortalServer/config/StartupPerformance/
b.     Add “scriptportlet” to end of the file and save and close the file.

5. Now let’s restart your portal server.
Above steps 1 to 5 will install the Script Portlet in your Base Portal and will create WCM library called “Script Portlet Library” inside the Base Portal.

6. In case of using the Script Portlet inside the Virtual Portal, execute the above 1 to 5 steps first then create the WCM Script Portlet Library inside the Virtual Portal using following ConfigEngine task 
In Linux or AIX:
./ConfigEngine.sh sp-content -DVirtualPortalContext=virtual portal context
In Windows:
ConfigEngine.bat sp-content -DVirtualPortalContext=virtual portal context
Note –
      While executing the deploy-paa command, I was getting error “EJPCE0036W: There are no components available, check that the values in the components.properties file for your assembly are correct” and scriptportlet ear  was not deploying successfully, though deploy-paa ConfigEngine task existing with Build Successful message.

To fix this,
a. I opened the components.properties file from the path - <WAS_HOME>\<WP_PROFILE>\paa\scriptportlet-app\ into a text editor.
b. And modified the “components/scriptportlet” value from false to true.
c. Ran the deploy-paa command once again and this time script portlet deployed successfully in Portal Server.

Comments

Post a Comment

Popular posts from this blog

Extending LDAP attributes to WebSphere Portal

I wanted to extend the Portal VMM attributes by adding new attributes from LDAP to our Portal env. Out of the box WebSphere Portal VMM is configured with a default attribute schema. You can extend the VMM attribute by adding new attributes that you can map between WebSphere Portal and your user registry. I followed below steps to extend the VMM attributes from the LDAP - Open the command prompt and go to <WP_PROFILE>/ConfigEngine directory. Run the wp-la-install-ear ConfigEngine tasks- In Linux env - ./ConfigEngine.sh wp-la-install-ear -DWasPassword=dmgr_password -DServerName=dmgr_server_name -DNodeName=node_name In Windows env - ConfigEngine.bat wp-la-install-ear -DWasPassword=dmgr_password -DServerName=dmgr_server_name -DNodeName=node_name Restart the Portal Server profile. Go to <WP_PROFILE>/ConfigEngine/properties directory in your Portal installation and open the wkplc.properties file in amy text editor. For safer side take a back of...
Read more

Installing and Un-installing Portal Application Archive (PAA) file

Basically .paa file installation process consists of two steps, install and deploy. 1. Copy the .paa file into some temp directory in your Portal box in case of installing the portal application archive file. 2. Open a command prompt and navigate to Portal profile ConfigEngine directory <WAS_HOME>/<wp_profile>/ConfigEngine and execute following ConfigEngine install-paa command – a) Installation of the .paa file In Linux or AIX ------------------- ./ConfigEngine.sh install-paa -DPAALocation=<paa_file_location> -DWasPassword=<password> -DPortalAdminPwd=<password> ./ConfigEngine.sh deploy-paa -DappName=<paa_app_name> -DWasPassword=<password> -DPortalAdminPwd=<password> In Windows: ---------------- ConfigEngine.bat install-paa -DPAALocation=<paa_file_location> -DWasPassword=<password> -DPortalAdminPwd=<password> ConfigEngine.bat deploy-paa -DappName=<paa_app_name> -DWasPassword=...
Read more

WCM Syndication issue in WebSphere Portal V 8001 with CF06 or CF07

Last week we faced issue while creating new syndication in WebSphere Portal 8001 with CF06 in one of Production deployment.  In WebSphere Portal CF6 there is an issue while creating new Syndicator and Subscriber pair with having two different domain name of Subscriber and Syndicator. Once you create syndication, in Syndicator side subscriber url get updated with the fully qualified domain name.  Basically, Syndication will be created perfectly fine, but when you execute the update WCM library , you will see following error in Portal SystemOut log -  IWKWC0004I: Code #405, phrase: Unrecognized sender, detail: Failed to retrieve subscriber. Cause: com.ibm.workplace.wcm.services.content.ItemNotFoundException: Failed to find controllable{746aeb11-629d-4759-9865-aeb754e094ea, com.aptrix.pluto.control.Controllable}in vp instance: 0 with context pathnull and hostname: null ) To fix this issue, we have to manually edit the syndicator and correct the subscriber ur...
Read more