STP/Stardust/KnowledgeBase//Customization/Portal/CustomLaunchPanelUsingPlugin

Extending the Workflow Perspective with a custom launch panel using a portal plugin

Project Setup

Use a project of type Utility Project and link it into your RAD environment:

In this example the project was named exampleCustom.

You can use the standard project structure created by eclipse or change it into a maven folder structure. Add the utility project as a J2EE module dependency to your dynamic web project. This way it will automatically be built and included as a jar in the web application's WEB-INF\lib folder.

Create the following folder structure under the project’s source folder:

META-INF
MEAT-INF\spring  (for spring configuration files)
MEAT-INF\xhtml\yourPluginName (for markup files used by your plugin)

Then create a file yourPluginFileName.portal-plugin. The file contents should be the relative path to your plugin’s markup folder starting from the src folder:

/META-INF/xhtml/yourPluginName/

Any xhtml file placed into this folder can later be referenced and accessed via

/plugins/yourPluginFileName/markupFileName.xhtml

Spring Configuration

Create two spring configuration files:

META-INF\spring\yourPluginName-context.xml
META-INF\spring\yourPluginNameUi-context.xml

The backing beans for the custom pages will be decaled in yourPuginName-context.xml.
UI extensions to the Infinity Process Platform portal will be declared in yourPluginNameUi-context.xml.

By default the contextConfigLocation parameters in the IPP web application is configured to include META-INF/spring/*-context.xml. Therefore these context files will be added to the spring context automatically and no configuration changes should be required.

JSF markup, backing beans and message bundle

TBD

Linking Extensions into the Portal

TBD