Importing new Liferay portlets

[Anon Anon]

Was looking for something totally unrelated, and I stumbled across a post that Dustin had replied to with the following:

 

*****Begin Quoted Text******

As for adding custom portlets, I did some digging and here is what dev wrote on this topic:

 

-----------------------------------------------------------------------------------------------------------------------------------

You can add a webapp/portlet to UMP by doing the following:

 

Let's call this webapp NewOne.

 

Drop your newone.war file into the directory :

 

   C:\Program Files\Nimsoft\probes\service\wasp\webapps

 

You must add an entry in the wasp.cfg file, in the <webapps> section, such as:

 

<webapps>

      ...

      <newone>

          reloadable = true

          cross_context = true

          load_on_startup = true

          unpack_war = true

          path = /newone

      </newone>

      ...

</webapps>

 

Note that the XML comment syntax is ** NOT ** allowed in this file.

Also, blank lines are ** NOT ** allowed in this file.

 

When adding a portlet, make sure there is not a duplicate path definition in the file.

 

When a webapp has been added you must:

    - Deactivate the wasp probe

    - Wait until it has stopped

    - Activate the wasp probe

 

Once a webapp has been added to the wasp process, you can stop and start individual webapps in the wasp configuration GUI, including newone. However there won't be a way for the user to deploy the new webapp/portlet, as it won't be in our list of portlets in the Monitoring section of Add Application.

 

So to make the new portlet appear in the portal, you'd have to login to the portal and then use the  "WebContent" portlet that's in the  Add

 

Application -> Monitoring  section, and set the URL to:

 

   /newone/

-----------------------------------------------------------------------------------------------------------------------------------

 

I haven't personally tested those directions out so best of luck!

 

Dustin

 

********End Quoted Text********

 

I was able to get through most of the instructions, and have the new WAR files seen by WASP and initialized, but I can't get them to show up on the portal.  I followed the directions on adding a new 'WebContent' portlet and configuring it to point to the new portlet, but i just get a 404 not found error upon saving.  Anyone been able to get this to work?

[Anon Anon]

I am also interested in getting this working and once put it in the WebContent it gives 404 error. Does anyone have info on how to use Custom Portlets? 

[Anon Anon]

I was able to get this working a while back for a few portlets i tried.  I know there is also some portlets there that are just turned off right now.  I believe it's a portlet.xml file you just need to find the portlet and change false to true.  I did this for a document repo portel that appears to work pretty well.  You may want to verify the version of portlet and if it supports ump liferay portal which I believe is 5.2.3.

[Anon Anon]

I figured it out.  Do the steps to get the new portlet uploaded to the correct directory and then added to the the wasp.cfg file.

 

Then, open the portal-ext.properties file on the machine with WASP installed (in webapps\ROOT\WEB-INF\classes directory), and change the auto.deploy.enabled option from false to true.

auto.deploy.enabled=true

 

Reload WASP, and then log into the UMP.  Go to Control Panel --> Plugins Installation, the option to install a new portlet will appear towards the top (it wasn't there before changing the auto.deploy option).  I've had to manually upload the WAR file to the portal, and then it appears as an application that you can add.

 

One other note, all the plug-ins I've been able to download come as zip files, just change the extenstion to war and they work fine.

 

Joel

[Anon Anon]

Oh, and our company is on UMP 2.0, I have no idea if this works with 1.5.

 

Joel

[Anon Anon]

 When I go to Control Panel, I don't see "Plugins Installation" as one of the items under "Server" on the left.   What configuration could I change to make it show up?