Entering content frame

Background documentation Additional Features Locate the document in its SAP Library structure

You can use an API that enables you to register a plug-in. This plug-in can be called during the generation of a PAR file. It enables you to extend the original portal application development model. You can interfere with both processes concerning the packing and unpacking of the PAR file. During the packing operation, the additional tool is called before the final packing of the PAR file. During the unpacking operation, the additional tool is called after the initial unpacking of the PAR file. In order to create such a tool, you have to use the PAR plug-in add-on. This add-on is another SAP NetWeaver Developer Studio plug-in and follows the following rules:

...

       1.      It must be loaded at SAP NetWeaver Developer Studio startup

       2.      It must be registered to the PAR plug-in

       3.      It must implement two interfaces, one for the packing and another for the unpacking

In the plugin.xml the following extension point has to be added:

This graphic is explained in the accompanying text

<extension

   point="org.eclipse.ui.startup">

</extension>

You must implement the org.eclipse.ui.Istartup interface with its method earlyStartup() in the base class of the add-on plug-in (the first class that is called when the add-on plug-in is started, and where org.eclipse.ui.plugin.AbstractUIPlugin is extended).

Register

Call of the static method of com.sap.portal.developmentTools.ideSpecific.eclipse.PortalPlugin class registerPlugin(String pluginId, IParIdePlugin aPlugin). The plug-in ID must be unique.

The Interface to be Implemented

To register, an add-on plug-in must implement the com.sap.portal.developmentTools.general.api.IparIdePlugin and give the implementation class as a parameter when it registers.

This graphic is explained in the accompanying text

The add-on plug-in has to specify the final state of the operation clearly using the method setFinalState(int status) from the class com.sap.portal.developmentTools.general.api.IfinishResult. If the final state is OK or Warning then the PAR process continues; otherwise, it is stopped. Inside the IfinishResult, you can also add as many messages with their level as you want. These will be displayed in the task view of SAP NetWeaver Developer Studio.

 

 

Leaving content frame