Register a custom Web content class

 

+

Search Tips   |   Advanced Search

 

You must register custom Web content class to be able to use them with functions such as custom workflow actions and Web content plug-ins.


Method 1: Deploy the ear file in the Administrative Console

To ensure the new Web content class is available each time your server is started you can register the ear file in the Administrative Console:

  1. Select...

      Applications | New Application | New Enterprise Application | EAR_file

  2. Select next until you reach step 2...

      Map modules to servers

  3. Select the tickbox for the custom action module.

  4. In the Clusters and servers section, select WebSphere_Portal and select Apply.

  5. Keep selecting Next until the end when you select Finish.

  6. The screen titled Installing will be shown. Select Manage Applications

  7. Locate and click the application you just installed. The default name is the display name defined in the application.xml file in your ear file.

  8. Under Detail Properties select Startup behavior.

  9. Under General Properties modify the Startup order to be the same weight as "wcm" and select Apply. By default, the weight is 20.

  10. Select Save directly to master configuration.

  11. To immediately start the application you just installed, select the application and click Start.


Update an existing ear file:

  1. Select...

      Applications | Application Types | WebSphere enterprise applications | appname

  2. Select the tickbox for the custom action application and click on Update.

  3. Select Replace the entire application and browse for the ear file.

  4. Keep selecting Next until the end when you select Finish.

  5. The screen titled 'updating' will be shown. Select Save to Master Configuration and then click save.


Method 2: Deploy jar files

This method is simpler, but is not automatically clustered. It is useful for testing a new Web content class on a single server in a development or test environment. If you use clustered servers, perform these steps on each server in the cluster.

  1. Create a jar containing the custom Web content class, any supporting classes and a plugin.xml file in the jar root.

  2. Copy the jar below the server's WCM shared app directory:

  3. Restart the server. The Eclipse plug-in framework will register the class.


Parent topic:

Creating custom plug-ins