The EditLive! WCM integration is packaged as a standard JEE EAR file. To install the EditLive! integration you can use either the IBM Integrated Solutions Console or your own installation process. The documentation below outlines how to perform an installation using the WebSphere Application Server.

Step 1 - Install the EAR file

The server running WebSphere_Portal needs to be started before you begin the install process.

Load up your web browser and login to the WebSphere Application Server. This is a separate service running on your webserver. The port for this will vary based on your server and WebSphere Portal version. In a standard installation, the url for the console will be: WebSphere Application Server 6.1 https://\[server\]:9043/ibm/console_

After logging in to the console, you will be able to install the application following the process below.

  1. Navigate to the New Application link in the console. This will involve clicking on the "Install New Application" link.
  2. From the "Choose Application" form, choose the new version of the EphoxEditLiveJEE.ear file and click on "Next".
  3. You now will begin the wizard for installing a new application. The EAR file has had been packaged to run well with as many default options as possible.
    • In the first step the defaults are all suitable. Simply click the "Next" button.
    • In step 2, you will need to ensure that the modules are deployed to the server running WebSphere Portal. Typically this will be the server called "WebSphere_Portal". If this server does not appear in the list, it may not have been started yet. To ensure that the ear is deployed to the right location, you will need to select the server, select the module, and then click the "Apply" button.

      After doing this, you will expect the server section to look as indicated in the screenshot below. You can then press the "Next" button to go to step 3.
    • The default options in Step 3 should be suitable, so you will typically be able to click the "Next" button and continue the wizard.
    • In step 4 you are presented with a summary. After confirming the details, click "Finish" to complete the installation.
  4. After finishing the wizard, the installation will take place, presenting the following in your browser. To ensure that the changes are applied correctly, you will need to save the configuration to the master configuration. Click the "Save" link.
  5. After installing the application, you will need to start it up. This can be done via the manage applications screen. First, navigate to the manage applications screen, clicking the WebSphere enterprise applications link.

    Then select the EphoxEditLiveJEE application and click the "Start" link.

    After starting the application you will see the application status now has a green arrow.

Step 2 - Specify the EditLiveJavaEditor.jsp File in WCM

  1. Log into Websphere Portal as a user with administrative WCM permissions
  2. Navigate to the Web Content Management Authoring Portlett
  3. Click the Configure link (nearby the Help link)
  4. Expand the Rich Text Options section.
  5. Select Custom Editor from the drop-down
  6. In the text field displayed, enter /editlive/;jsp/html/EditLiveJavaEditor.jsp (The semi-colon is not a typo).
  7. Click OK.

If you haven't clicked the Configure link for WCM before, this may cause the current default Library associated with the WCM portlet to be removed. To reassign the default Library assign to the WCM portlet, once inside the configure page expand the Library tab, select Web Content, and click the Add button.

Client-Side Requirements

The EditLive! Client-Side Requirements can be found in the Install Guide.

Although EditLive! itself supports a variety of JRE versions, WCM itself only supports a subset of the available JRE versions.

Visit the WCM 6.1 Information Center for an up to date list of the JRE versions supported by WCM.

Attachments:

choose_application.png (image/png)
choose_application.png (image/png)
choose_application.png (image/png)
final-step.png (image/png)
final-step.png (image/png)
final-step.png (image/png)
wizard-2b.png (image/png)
wizard-2b.png (image/png)
wizard-2b.png (image/png)
start_application.png (image/png)
start_application.png (image/png)
start_application.png (image/png)
wizard-1.png (image/png)
wizard-1.png (image/png)
wizard-1.png (image/png)
wizard-2a.png (image/png)
wizard-2a.png (image/png)
wizard-2a.png (image/png)
application_started.png (image/png)
application_started.png (image/png)
application_started.png (image/png)
wizard-4.png (image/png)
wizard-4.png (image/png)
wizard-4.png (image/png)
was_7_application_option.png (image/png)
was_7_application_option.png (image/png)
was_7_application_option.png (image/png)
WebSphere_enterprise_applications.png (image/png)
WebSphere_enterprise_applications.png (image/png)
WebSphere_enterprise_applications.png (image/png)
install_fast_path.png (image/png)
install_fast_path.png (image/png)
install_fast_path.png (image/png)
wcm_configure_link.png (image/png)
wcm_configure_link.png (image/png)
wcm_configure_link.png (image/png)
wizard-3.png (image/png)
wizard-3.png (image/png)
wizard-3.png (image/png)
enterprise_applications7.png (image/png)
enterprise_applications7.png (image/png)
enterprise_applications7.png (image/png)
specify_ear_was7.png (image/png)
specify_ear_was7.png (image/png)
specify_ear_was7.png (image/png)
customEditor_dropdown.png (image/png)
customEditor_dropdown.png (image/png)
customEditor_dropdown.png (image/png)