IBM Web Experience Factory


Installation Guide
Version 8 Release 5
IBM Web Experience Factory


Installation Guide
Version 8 Release 5
 Note
Before using this information and the product it supports, read the information in “Notices” on page 17.

Notice
This edition applies to version 8.5 of IBM(r) Web Experience Factory (product number 5724-O03) and to all
subsequent releases and modifications until otherwise indicated in new editions.
© Copyright IBM Corporation 2014, .
US Government Users Restricted Rights – Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Web Experience Factory Product Installation Guide
Use this guide to install IBM® Web Experience Factory Version 8.5.

This guide contains the following installation topics.

“1.0 Installation overview”
“2.0 Installing Web Experience Factory” on page 2
“3.0 Installation notes” on page 11
“4.0 Removing IBM Web Experience Factory” on page 13
“5.0 Upgrading plug-in files, projects, and portlets” on page 13
“6.0 Enabling IBM Tivoli License Manager tracking” on page 15
“7.0 Using JAWS For Windows during installation” on page 16

1.0 Installation overview

This guide applies to Web Experience Factory, but the installation may involve
installing other products.

1.1 Installation steps

Installation involves the following steps:
Step 1 - Install Web Experience Factory Designer
Run the installation program to install Web Experience Factory Designer.
Step 2 - Create and deploy a Web application project
Use the tutorial provided to create a web application project that you
deploy to your application server or WebSphere® Portal server.

1.2 Pre-installation information

The default installation selection includes a supported version of Eclipse.
Alternatively, Web Experience Factory can be installed into a supported version of
one of the following IDEs.
v IBM Rational® Application Developer
v IBM Rational Software Architect
v IBM Rational Web Developer
v Eclipse (Eclipse SDK versions only) with the following software:
– Eclipse 4.2.2 or later
– Graphical Editing Framework (GEF) 3.8.2 or later
– Web Tools 3.4.2 or later
– Data Tools 1.10.2 or later
– Eclipse Model Framework (EMF) 2.8.3 or later
– EMF XML Schema Definition (XSD) 2.8.3 - or later

For more information about installing Eclipse, see Manually installing Eclipse.

For more information about supported versions, see the System Requirements.

© Copyright IBM Corp. 2014, 1

 Prior to installation, you must install IBM WebSphere Portal or one of the
supported application servers. Refer to the detailed system requirements section in
the product release notes topic for application server versions and patch levels.

Note: To install Web Experience Factory into a Rational IDE on a system using a
language other than English, you must first edit the file installer.properties and
modify the path specified on the line which starts with PRODUCTREG_PATH= to
accurately specify the path on your system.

1.3 Existing installations of Web Experience Factory

If you have an existing installation of Web Experience Factory, do not install the
new version over the old one in the same directory.

If you want to use the same directory for the new installation, follow these steps.
1. Consider a backup of your existing installation.
2. Back up any private files, such as SAP libraries.
3. Remove the old version using the process detailed in Section 4.
4. Install the new version using the process detailed in Section 2.
5. Move any backed up private files into the correct directory in the new
installation.

2.0 Installing Web Experience Factory

First, follow the steps described in one of the following sections to install Web
Experience Factory on the desired platform.
v “Step 1 - Installing Web Experience Factory on Windows systems”
v Installing on Linux platforms
– “Step 1 - Installing Web Experience Factory on Linux systems” on page 4
– “Installing Web Experience Factory into Rational Application
Developer/Rational Software Architect on Linux systems” on page 5
v “Installing silently from the command line” on page 10

Then, you can follow the steps described in “Step 2 - Run the tutorial: creating a
Web application project” on page 11 to begin exploring the product.

Step 1 - Installing Web Experience Factory on Windows

systems
1. If you are on the Microsoft Vista system, run with Administrator account
rights.
To run Web Experience Factory Designer on the Microsoft Vista system, you
must install Web Experience Factory to run with Administrator account rights
and the user running the application must have Administrator rights.
2. Launch the installation executable (Factory.exe).
3. When you are prompted, select your preferred language for using the product,
then click OK.
4. An introduction page displays with copyright and other information. To
proceed with installation, click Next
5. Read the license agreement and select I accept the terms of the License
Agreement to proceed with installation, then click Next.

2 IBM Web Experience Factory: Installation Guide

 Note: If you do not accept the license terms, you are prompted to quit the
installation.
6. You can choose one of the following options.
v Standard installation provides everything needed to get started quickly
Select this option to include Eclipse and IBM WebSphere Application Server
Liberty Profile with your Web Experience Factory installation. If this option
is selected, the installation program installs Eclipse, Web Experience Factory
Designer, WebSphere Application Server Liberty Profile, and IBM Support
Assistant. If you choose this option, skip to step 11 after you review the
installation directory choice.
v Custom installation enables you to choose features and installation
options
Select this option if you need to specify in detail your software options and
their installation location.
v Select installation directory
In the field, to change the location to install Web Experience Factory files,
click Choose or edit the path and click Next.
7. In the Specify install items screen, select an integrated development
environment (IDE) to use with Web Experience Factory Designer.
You can choose one of the following options.
v Install Designer with a new copy of Eclipse
Select this option if you do not have an IDE. If this option is selected, the
installation program installs Eclipse and Web Experience Factory Designer.

Note: If you select this option and select a directory that contains an
existing installation of Eclipse, a warning message displays. Choose a
different directory to continue the installation.
v Install into existing IBM Rational Application Developer*
Select this option if you want to use a Rational Development Environment
you have already installed. This includes Rational Application Developer,
Rational Software Architect, and Rational Web Developer. The installation
program adds to the current version of your Rational Development
Environment menu items specific to Web Experience Factory.
v Install into existing Eclipse
Select this option to use a version of the Eclipse-based IDE that is already
installed. The installation program adds to the current version of your
Eclipse IDE menu items specific to Web Experience Factory Designer.
8. In the Specify IDE screen, specify the IDE location and click Next.
If you need to browse for the location, click Choose.
9. In the Test Server Install Option screen, click Install the Liberty Profile as a
development test server and choose the install location if you want to install
WebSphere Application Server Liberty Profile.

Note: WebSphere Application Server Liberty Profile is supplied to enable

quick and easy development and testing of applications solely for the purpose
of getting started with Web Experience Factory Designer. It is a best practice
to utilize a local development environment that matches the target production
deployment platform. (For example, you should utilize IBM WebSphere Portal
as your local development environment if applications are to be ultimately
deployed to IBM WebSphere Portal in production).

Web Experience Factory Product Installation Guide 3

 10. In the IBM Support Assistant Install Option screen, click Install IBM Support
Assistant to assist support.
You can use this option to collect information that is needed by support
representatives.
On the next screen, you can choose a different location to install the option.
11. In the Pre-Installation Summary screen, review the choices.
v If all information is correct, click Install. An Install progress screen is
displayed and, once installation is complete, the Install Complete screen is
displayed.
v If a choice is not correct, click Previous to return to the related screen to
change the choice and click Next to return to this screen to begin the
installation.
12. Click Done to close the installer.
A browser opens and displays a getting started page that contains information
about the product. Upon successful installation, an install log is created in the
install location (for example, C:\Program Files\IBM\Web Experience Factory).
13. If you install into an existing Eclipse-based Web Experience Factory Designer
installation, you must upgrade Web Experience Factory Designer plug-ins if
you are installing over a previous version of Web Experience Factory.
For information about the steps required to upgrade plug-ins, refer to “5.0
Upgrading plug-in files, projects, and portlets” on page 13.

Step 1 - Installing Web Experience Factory on Linux systems

Before you install Web Experience Factory, you should install:
v An application server such as WebSphere Application Server Liberty Profile or
IBM WebSphere Portal.
v Eclipse with Web Tools or Rational Application Developer. Check the Web
Experience Factory release notes topic for the detailed system requirements that
describe the supported Eclipse release.

A 32-bit version of Eclipse for Linux is packaged with Web Experience Factory. See
Manually Installing Eclipse for more information.

To install Web Experience Factory into an existing Rational Application Developer

or Rational Software Architect installation on Linux systems, follow the procedures
described in “Installing Web Experience Factory into Rational Application
Developer/Rational Software Architect on Linux systems” on page 5.
1. If you are deploying to WebSphere Portal, establish correct permissions.
Perform the following steps.
a. Create a group for your user, for example wpfDev.
This group will have write permissions to the WebSphere directories.
b. With WebSphere Application Server running, open the administration
console, and navigate to: Application servers > WebSphere_Portal >
Process Execution.
1) Change the umask value to 002.
2) Change the 'run as group'' to wpfDev.
3) Perform the same step for server1.
This allows you to change the file permissions for the WebSphere Portal
server. Any file written by the WebSphere Portal server now has read,
write, and execute permissions for the WebSphere Portal user, and the
group to which the WebSphere Portal user belongs.

4 IBM Web Experience Factory: Installation Guide

 c. Stop the WebSphere Portal server.
d. Make yourself a member of the newly created group (wpfDev in this
example).
e. From a command line, run the following commands as root.
chgrp -R wpfDev WP_INSTALL_DIR/AppServer/
chgrp -R wpfDev WP_INSTALL_DIR/PortalServer/

If the directories are not writable by group, then run the following
commands.
chmod -R g+w WP_INSTALL_DIR/AppServer/
chmod -R g+w WP_INSTALL_DIR/PortalServer/
This allows write access to the those folders after the WAR files are
deployed.
f. Restart WebSphere Portal server.
2. Launch the installer.
./Factory.bin
The installer checks for space and other prerequisites and displays the first
panel.
3. When prompted, select your preferred language for using the product. Then
click OK
An introduction page displays with copyright and other information.
4. Click Next to proceed with installation.
5. Read the license agreement and select I accept the terms of the License
Agreement to proceed with installation, then click Next.

Note: If you do not accept the license terms, you are prompted to quit the
installation.
6. In the Choose Install Folder screen, specify the location to install Web
Experience Factory files and click Next.
7. Specify the location where Eclipse with Web Tools is installed and click Next.
If you are using Rational Application Developer, choose the default and click
Next.
8. In the Choose Liberty screen, specify if you want the liberty server to be
installed and click Next.
9. In the IBM Support Assistant Install Option, specify if you want the support
assistant to be installed and click Next.
10. Review the Pre-Installation Summary screen, and, if all information is correct,
click Install.
An Install progress screen is displayed and, once installation is complete, the
Install Complete screen is displayed.
11. Click Done to close the Factory installer.
A browser opens and displays a Welcome page containing information about
Next Steps. Upon successful installation, an install log is created in the install
location (for example, /root/IBM/).

Installing Web Experience Factory into Rational Application

Developer/Rational Software Architect on Linux systems
If you are installing Web Experience Factory into an existing Rational Application
Developer or Rational Software Architect installation on a Linux system, perform
these steps.

Web Experience Factory Product Installation Guide 5

 1. If you are deploying to WebSphere Portal, establish correct permissions.
Perform the following steps.
a. Create a group for your user, for example wpfDev.
This group will have write permissions to the WebSphere directories.
b. With WebSphere Application Server running, open the administration
console, and navigate to: Application servers > WebSphere_Portal >
Process Execution.
1) Change the umask value to 002.
2) Change the 'run as group'' to wpfDev.
3) Perform the same step for server1.
This allows you to change the file permissions for the WebSphere Portal
server. Any file written by the WebSphere Portal server now has read, write,
and execute permissions for the WebSphere Portal user, and the group to
which the WebSphere Portal user belongs.
c. Stop the WebSphere Portal server.
d. Make yourself a member of the newly created group (wpfDev in this
example).
e. From a command line, run the following commands as root.
chgrp -R wpfDev WP_INSTALL_DIR/AppServer/
chgrp -R wpfDev WP_INSTALL_DIR/PortalServer/

If the directories are not writable by group, then run the following
commands.
chmod -R g+w WP_INSTALL_DIR/AppServer/
chmod -R g+w WP_INSTALL_DIR/PortalServer/
This allows write access to the those folders after the WAR files are
deployed.
f. Restart WebSphere Portal server.
2. Install Web Experience Factory with the user account of the Web Experience
Factory user.
The Eclipse installation location should be a directory that the user account has
write access to. You may need to choose a location other than the Rational
Application Developer installation location. There does not need to be an
existing Eclipse in this location.
3. If you chose to install Eclipse into the Rational Application Developer install
location in the previous step, skip this step.
Do one of the following steps.
v Using an account with write privileges to the Rational Application Developer
install location, copy the links directory created by the installer to the correct
directory in the Rational Application Developer install location.
The links folder should be located just within the Rational Application
Developer installation directory.
v You can also copy the Web Experience Factory link file directly to a
previously created links directory within Rational Application Developer.
4. Start Rational Application Developer with the -clean flag as root (or the
Rational Application Developer owner) and verify Web Experience Factory is
installed.
Use Help > About to verify that the Web Experience Factory button displays.

6 IBM Web Experience Factory: Installation Guide

 5. Restart Rational Application Developer with the -clean flag as the Web
Experience Factory user, if it is not the user in the previous step, and verify as
in the previous step.
6. Restart Rational Application Developer normally as the Web Experience Factory
user.
You do not need to use the -clean flag at this point.

Manually installing Eclipse

A 32-bit version of Eclipse for Windows and a 32-bit version of Eclipse for Linux
are packaged with Web Experience Factory.

You can manually install Eclipse on platforms other than Windows and Linux,
such as 64-bit Mac OS X, by using components provided in the Web Experience
Factory install image and components obtained from IBM or eclipse.org.

The config directory of the Web Experience Factory installation image contains the
following files:
eclipse.zip
Contains Windows 32-bit Eclipse SDK
eclipse_linux.tgz
Contains Linux 32-bit Eclipse SDK
eclipse_plugins.zip
Contains additional Eclipse plugins as required by Web Experience Factory
(Graphical Editing Framework (GEF), Web Tools, Data Tools, Eclipse
Modeling Framework (EMF), XML Schema Definition (XSD))
jre.zip
Contains Windows 32-bit Java™ JRE
jre_linux.tgz
Contains Linux 32-bit Java JRE

To install the 32-bit Eclipse version, make a new target directory and expand the
archives appropriate for your operating system into the new target directory:
v On Windows, expand eclipse.zip, eclipse_plugins.zip and jre.zip into the
new Eclipse target directory, for example, C:\IBM\WEF\Eclipse.
v On Linux, expand eclipse_linux.tgz, eclipse_plugins.zip and jre_linux.tgz
into the new Eclipse target directory. For example, run the following commands
to install a copy of 32-bit Eclipse for Linux:
mkdir ~/WEF
mkdir ~/WEF/eclipse
cd ~/WEF/eclipse
tar -xvf <path to config>/eclipse_linux.tgz
unzip <path to config>/eclipse.plugins.zip
tar -xvf <path to config>/jre_linux.tgz
v You can install Eclipse for other platforms by using the components provided in
the Web Experience Factory install image with components obtained from IBM
or eclipse.org:
1. Obtain a Java 1.6 JRE for your platform. For example, download the IBM
64-bit JRE for Linux from http://www.ibm.com/developerworks/java/jdk/
linux/download.html#java6.
2. Obtain a copy of the base Eclipse SDK for your platform. For example,
download the 64-bit Eclipse SDK from http://www.eclipse.org/downloads/
packages/eclipse-classic-422/junosr2.

Web Experience Factory Product Installation Guide 7

 3. Expand the .tar.gz file downloaded from eclipse.org into the eclipse
directory.
4. Expand the eclipse_plugins.zip included in the config directory of the Web
Experience Factory installation image into the eclipse directory.
5. Expand the JRE obtained from ibm.com into the eclipse directory.

Step 1 - Installing Web Experience Factory on Mac OS X

systems
Before you install Web Experience Factory, you should install:
v Java. You can download Java from https://developer.apple.com/search/
index.php?q=java.
v An application server such as WebSphere Application Server Liberty Profile.
v Eclipse IDE for Java EE Developers. Refer to the Web Experience Factory
detailed system requirements for Eclipse releases that are supported.
1. Download Factory.zip. Double-click Factory. The compressed installer should
be recognized by Stuffit Expander and should be automatically expanded after
downloading. If it is not expanded, you can expand it manually using StuffIt
Expander 6.0 or later.
2. Launch the installer. If you have any problems launching the installer once it
has been expanded, make sure that the compressed installer was expanded
using Stuffit Expander.
./Factory.bin
The installer checks for space and other prerequisites and displays the first
panel.
3. When prompted, select your preferred language for using the product. Then
click OK
An introduction page displays with copyright and other information.
4. Click Next to proceed with installation.
5. Read the license agreement and select I accept the terms of the License
Agreement to proceed with installation, then click Next.

Note: If you do not accept the license terms, you are prompted to quit the
installation.
6. In the Choose Install Folder screen, specify the location to install Web
Experience Factory files and click Next.
7. Specify the location where Eclipse with Web Tools is installed and click Next.
8. In the Choose Liberty screen, specify if you want the liberty server to be
installed and click Next.
9. In the IBM Support Assistant Install Option, specify if you want the support
assistant to be installed and click Next.
10. Review the Pre-Installation Summary screen, and, if all information is correct,
click Install.
An Install progress screen is displayed and, once installation is complete, the
Install Complete screen is displayed.
11. Click Done to close the Factory installer.
A browser opens and displays a Welcome page containing information about
Next Steps. Upon successful installation, an install log is created in the install
location (for example, /root/IBM/).

8 IBM Web Experience Factory: Installation Guide

When running the Web Experience Factory Designer on Mac OS X, there are
additional setup steps required to publish your project to a WebSphere Application
Server or IBM WebSphere Portal Server.

The publish action in the Web Experience Factory Designer must establish a secure
connection to the WebSphere Application Server to install the application. When
running the Designer under a non-IBM JRE (as is required on Mac OS X), the IBM
WebSphere SSL stack is not available. This prevents the Designer from
automatically accepting the SSL certificates presented by the WebSphere
Application Server during the publish process. In order to successfully publish to a
WebSphere Application Server, the SSL certificate used by the server must be
manually added to the trust store used by the JRE. The following steps describe
this process.
12. Determine the JRE that Eclipse is using:
a. In Eclipse, select Eclipse > About Eclipse.
b. On the About dialog, click Installation Details.
c. Switch to the Configuration tab.
d. Locate the java.home property, for example, /System/Library/Java/
JavaVirtualMachines/1.6.0_jdk/Contents/Home.
13. Obtain the SSL certificate used by the target application server.
a. Open a web browser and connect to the HTTPS port of the target
application server. For example, connect to https://localhost:10029/wps/
portal.
b. Using Firefox:
1) Open Firefox and connect to the HTTPS port of the target application
server. For example, connect to https://host.ibm.com:10029/wps/
portal.
2) The browser should prompt you to accept the certificate used by the
server. Expand the I Understand the Risks section and click Add
Exception....
3) On the dialog panel, click View... to view the certificate.
4) Activate the Details tab.
5) Click Export....
6) Save the certificate to a folder.
c. Using Safari:
1) Open Safari and connect to the HTTPS port of the target application
server. For example, connect to https://host.ibm.com:10029/wps/
portal.
2) The browser should open a dialog that prompts you to accept the
certificate used by the server. Click Show Certificate.
3) Drag the certificate icon located next to the certificate information to
the Desktop or another folder. This creates a .cer file.
14. Import the SSL certificate into the JRE trust store.
a. Open a Terminal window.
b. Navigate to the JRE home directory as determined in step 12. Then change
to the lib/security subdirectory. For example: cd /System/Library/Java/
JavaVirtualMachines/1.6.0_jdk/Contents/Home/lib/security.

Web Experience Factory Product Installation Guide 9

 c. Run the following command to import the SSL certificate for your
application server into the JRE trust store: sudo keytool -import
-noprompt -keystore cacerts -storepass changeit -file
<path_to_saved_cert>
d. keytool should echo a success message indicating that the SSL certificate
was added.
e. Run the following command to verify that the new SSL certificate is
present in the trust store: keytool -list -v -keystore cacerts
-storepass changeit
f. Restart the Web Experience Factory Designer and again try the publish
action.

Installing silently from the command line

You can perform a silent installation of Web Experience Factory using one of the
following pre-configured property files stored under the directory containing the
installation executable file.
config/win_silent_install.properties
config/linux_silent_install.properties

The property files contain default responses to the installation program. For
information on generating your own response file for a silent installation, see
“Optional: Creating an installation response file” on page 11.
1. Edit the desired pre-configured property file to match your installation
environment.
v Set the license agreement property.

Note: For silent installation to work correctly, the license agreement property
must be set to true to indicate acceptance of the license agreement.
# License agreement. Please see documentation for more info.
LICENSE_ACCEPTED=true

By default, this value is set to false in the supplied files.

v If you are installing into an existing Rational IDE, set the following values.
USER_INSTALL_ECLIPSE=0
USER_EXISTING_PRODUCT=1
USER_EXISTING_ECLIPSE=0

Specify the path to the existing IDE. For example, on Windows systems, set
the path using the following format.
USER_MAGIC_FOLDER_1=C:\\Program Files\\IBM\\SDP

These values are not automatically set even if you specify that you are
installing into a supported version of an IDE.
2. Indicate the location of the response file in the installation command.
On Windows systems, open a command line and enter the following command.
c:\Factory.exe -f c:.\config\win_silent_install.properties
On Linux systems, enter the following command.
sh ./Factory.bin -f ./config/linux_silent_install.properties
This path can be absolute or relative to the location of the installer.
3. Run the installation in silent mode.
v On Windows systems, open a command line and enter the following
command.
Factory.exe -i Silent -f config\win_silent_install.properties
10 IBM Web Experience Factory: Installation Guide
 v On Linux systems, enter the following command.
./Factory.bin -i Silent -f config/linux_silent_install.properties

The installation program installs everything to the target location without showing
the user any output. You know that the installation is complete when the log file is
created in the root of the installation directory.

Optional: Creating an installation response file

You can run the installation executable file, select the options desired, and save
those options to a text file that can be used to install the product silently.
1. Use the following command-line argument to write the response file to a
different directory.
On Windows systems
factory.exe -r full path to the response file destination
On Linux systems
/Factory.bin -r full path to the response file destination
For example, the following command writes the responses that you supply to
the file myresponse.txt in the specified directory.
factory.exe -r c:\temp\myresponse.txt
2. Complete the installation with your responses.
3. After the response file is generated, add to the generated file the following
lines.
INSTALLER_UI=silent
LICENSE_ACCEPTED=true

Follow the procedure in “Installing silently from the command line” on page 10 to
run a silent installation with your response file rather than the supplied property
file.

Step 2 - Run the tutorial: creating a Web application project

Once you successfully install the Web Experience Factory Designer, you must
create a new project. In creating a project, you provide application server-specific
and WebSphere Portal server-specific information about your installation. This
process completes the deployment phase of Web Experience Factory installation.

The Web Experience Factory Designer provides a New Project wizard to help you
create a project. This multiple page wizard walks you through the steps involved
in project creation and deployment and also builds the project for you. F1 Help
that describes project settings and parameters is available for each page of the
wizard. Refer to F1 Help to learn about the settings on a given page and to access
links to additional information.

The best way to create your first project is to run the tutorial that describes this
process. If you are using a Windows client, this tutorial is available from the
Welcome page, or from Start. Click Start > Programs > IBM > Web Experience
Factory > Tutorials. If you are using a Linux client, this tutorial is available from
the Web Experience Factory Help system.

3.0 Installation notes

You may have to perform a few tasks after the installation.

Web Experience Factory Product Installation Guide 11

 3.1 Native language support for Eclipse
Web Experience Factory Designer supports the following languages: German,
Spanish, French, Italian, Japanese, Korean, Portuguese (Brazil), Traditional Chinese,
and Simplified Chinese.

To use Eclipse in a language other than English, you must download a language
pack from the Eclipse web site, and install that pack into your Eclipse IDE.
1. In Web Experience Factory Designer, click Help > Install New Software.
2. In the Install dialog, click Add.
3. In the Add Site dialog, in Name, enter text to describe your package (for
example, Language FR) and, in Location, enter the following URL.
http://download.eclipse.org/technology/babel/update-site/R0.8.1/helios
4. Click OK to have the list of available languages made available.
This operation can take several minutes.
5. In the list of available languages, expand the language that you want and, from
the list of available language packs, select the following item.
Babel language pack for eclipse language (%)

This selection provides all the requisite code.

6. Click Next to load the language and click Next again to install the language.
7. Accept the license agreement and click Finish.
8. After the installation completes, restart Eclipse and add to the start command
the -nl option with the language designation, for example, -nl fr.

Note: If the Microsoft Windows system is configured to use a non-English

Group 1 language, Eclipse now can run in that language.

Note: Multiple-byte characters are not supported for project names or the
names of folders in the path.
9. Optional: You can force Web Experience Factory Designer to run in any Group
1 language by adding a language identifier to the Eclipse startup command.
For example, if you add the following identifiers to the startup command, you
can run Web Experience Factory Designer in Spanish, regardless of the
language the system is configured to use.
-Duser.language=es -Duser.country=ES

Note: The same languages are supported in IBM Rational Application

Developer. If you want to install language support into Rational Application
Developer, use the Installation Manager (or install it when you install Rational
Application Developer). See to the Rational Application Developer
documentation for instructions on installing language support.

3.2 Eclipse double byte language issues on Linux systems

Linux installations of Web Experience Factory on double byte languages may not
display correct fonts. Possible solutions include:
v Install all available fonts for the language you are using.
v Start the installer with a JRE on your system that is compatible with your
language selection. For example:
/Factory.bin LAX_VM $JAVA_HOME/bin/java

12 IBM Web Experience Factory: Installation Guide

 Note: The same languages are supported in IBM Rational Application Developer.
Refer to the Rational Application Developer documentation for instructions on
installing language support.

4.0 Removing IBM Web Experience Factory

Follow the steps in “4.1 Removing Web Experience Factory Designer for Windows
systems” or “4.1.1 Removing Web Experience Factory Designer for Linux systems”
(depending on your client platform) and then “4.2 Removing project WAR files” to
remove Web Experience Factory Designer files and project WAR files.

4.1 Removing Web Experience Factory Designer for Windows

systems
1. Use the Windows Control panel to access Add/Remove Programs.
2. Select the product to uninstall and click Change/Remove.
3. When the Uninstall window appears, click Uninstall.
Product files, registry entries, and shortcuts are removed from your system.

Note: When you uninstall Web Experience Factory, WebSphere Application

Server Liberty is also uninstalled.

4.1.1 Removing Web Experience Factory Designer for Linux

systems
With a Linux installation, you will need to manually remove certain files and
directories created by the installer.
1. Delete the Designer directory and the log file in the installation directory.
2. Delete the original install directory/license directory if desired
3. Delete the Web Experience Factory link file called
com.bowstreet.designer.link which is located in the IDE_INSTALL_DIR/links
directory. For example, /opt/IBM/SDP75/links

4.2 Removing project WAR files

1. Use your application and portal server administration tools to remove
installable and installed WAR files.
2. The administration tool removes only the installed applications, so it may be
necessary to manually delete any remaining application or portlet related
directories and files.

5.0 Upgrading plug-in files, projects, and portlets

This section discusses the procedures required to upgrade IBM Web Experience
Factory plug-in files if you have installed a new version of Web Experience Factory
into an IDE (Eclipse or IBM Rational) that has a previous version installed. This
section also describes how to update a project built with a previous version of Web
Experience Factory Designer to the latest project version. Finally, this section
describes how to upgrade portlets to the Java Portlet Standard API.

Web Experience Factory Product Installation Guide 13

 5.1 Upgrading a project from versions 5.12, 6.0.0, 6.0.1, 6.0.2,
6.1.0, 6.1.2, 6.1.5, 7.0, and 7.0.1
When upgrading 'flat' projects, create a new project and migrate your content to it
using the Export > Web Experience Factory Archive function. A flat project is a
5.12 or 6.0 project that does not have a WebContent directory. You will not get the
added benefits of facet support if you upgrade a flat project.

You must modify any projects that you created using the old plug-in files so that
these projects can include changes related to the new plug-in files and feature sets.
1. Open an existing project into Web Experience Factory Designer.
2. Right-click the project entry in the Project Explorer and click Web Experience
Factory Project > Upgrade Project Version.
3. A summary information displays. Click Next.
4. Update the deployment information for this project if necessary. Check the
deployment configuration and click Finish in the upgrade wizard.
5. Before the upgrade process completes, you may be prompted to overwrite any
Web Experience Factory files in the project that have changed, including files
that were changed by Web Experience Factory functionality, not necessarily files
that you have changed manually.
6. You will need to redeploy the project to the servers. Click Yes when prompted
to redeploy.
7. Right-click the project in the workspace.
8. Click Properties > Web Experience Factory Properties > Feature Info.
9. Set Refresh installed Feature Sets and then click OK.

If you have added any jar files to /WEB-INF/work/lib, you will need to manually
add them to the build path after a project upgrade.

5.2 Upgrading portlets to the Java Portlet Standard API

WebSphere Portal has support for the Java Portlet Standard API for WebSphere
portlets. While portlets designed for use in the deprecated WebSphere Native
portlet API may continue to run in WebSphere Portal, it is recommended that any
new portlets be built using the Java Portlet Standard API.

You can easily upgrade portlets built using the deprecated WebSphere Native
Portlet API to the Java Portlet Standard API. To do so, you must modify the project
that contains the portlet models.

Note: If you have already upgraded the project, you can switch to Java Portlet
Standard API by switching the project to a Java Portlet Standard API. Change the
server configuration by uninstalling the old WAR as described in the following
steps and update the project to use the Java Portlet Standard API server
configuration. Publish the project when prompted.

To upgrade a portlet built in a previous version of the Web Experience Factory to

use the Java Portlet Standard API, perform the following steps.
1. Load the project containing the portlet model into the Web Experience Factory
Designer.
2. Select the project and click Web Experience Factory Project > Upgrade project
version.
3. Using the WebSphere Portlet Administration tool, remove the old portlet WAR
file from the WebSphere Portal server.

14 IBM Web Experience Factory: Installation Guide

 (If the project has already been upgraded, switch the project to a Java Portlet
Standard API server configuration, then update the project to use the Java
Portlet Standard API server configuration and redeploy when prompted.)
4. In Web Experience Factory Designer, use one of the export commands to
update portlet WAR file to the WebSphere Portal server.
5. Use the WebSphere Administration tool to place the updated portlets on
WebSphere Portal pages.

5.3 Regenerating a portlet model

If you have a model that uses the Cooperative Portlet Source builder or the
Cooperative Portlet Target builder and the project uses the Java Portlet Standard
2.0 API (JSR 286), regenerate the model.

These steps are required to capture new event metadata that did not exist in prior
releases of Web Experience Factory.
1. For each model in your project that contains the Cooperative Portlet Source
builder or the Cooperative Portlet Target builder, open the model.
2. Force a regeneration.
For example, click Model > Generate Model or open any builder and click OK.
3. Save the model and publish or export the project again.

This procedure captures the new event metadata.

6.0 Enabling IBM Tivoli License Manager tracking

IBM Tivoli® License Manager (ITLM) recognizes and monitors what products and
their versions, releases, and fix packs are installed, and used, on a system. This
allows IBM to communicate updates for products installed in its customer base,
and appropriately bill for the product and the amount of usage. It also prevents
billing for multiple installations of the same product that is bundled with various
IBM software packages.

The usage of applications and portlet WAR files created with the IBM Web
Experience Factory can be monitored and tracked by Tivoli License Manager. To
enable this capability, you must place at the root level of an application or portlet
EAR file certain files that are generated by the Web Experience Factory and
recognizable by Tivoli License Manager.

To enable Tivoli License Manager usage tracking, perform the following operation:

Drag the WEB-INF\bin\itlm\ directory and its contents to the root of the deployed
EAR file.

Note: Ensure that the WEB-INF\bin\itlm\ directory is in one location only. You see
a dual usage error if multiple copies of this directory exist in an EAR file.

Note: Tivoli License Manager provides only inventory tracking if you do not move
the WEB-INF\bin\itlm\ directory to the root of the EAR file.

For more information about using Tivoli License Manager, see your IBM
WebSphere Portal documentation.

Web Experience Factory Product Installation Guide 15

7.0 Using JAWS For Windows during installation
If you want to install Web Experience Factory and use the JAWS screen reader for
accessibility, you need to perform the following additional step to correctly start
the installation.

You need to have Java Access Bridge for Microsoft Windows Operating System
software installed on your system. Java Access Bridge for Microsoft Windows
Operating System is provided by Oracle, Copyright (c) 2006 Oracle and/or its
affiliates.

Use the following command to start the Web Experience Factory installation:

Factory.exe LAX_VM installDir-for-java\java.exe

Where installDir-for-java\ is your local Java installation directory.

This command forces the installation to use the JVM that you specified and that
works with the Java Access Bridge.

16 IBM Web Experience Factory: Installation Guide

Notices
This information was developed for products and services offered in the U.S.A.

IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.

IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:

IBM Director of Licensing

IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.

For license inquiries regarding double-byte (DBCS) information, contact the IBM
Intellectual Property Department in your country or send inquiries, in writing, to:

Intellectual Property Licensing

Legal and Intellectual Property Law
IBM Japan Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan

The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law: INTERNATIONAL
BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS"
WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED,
INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF
NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR
PURPOSE. Some states do not allow disclaimer of express or implied warranties in
certain transactions, therefore, this statement may not apply to you.

This information could include technical inaccuracies or typographical errors.

Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.

Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.

© Copyright IBM Corp. 2014, 17

 IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.

Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:

IBM Corporation
Office 4360
One Rogers Street
Cambridge, MA 02142
U.S.A.

Such information may be available, subject to appropriate terms and conditions,

including in some cases, payment of a fee.

The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.

Any performance data contained herein was determined in a controlled

environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.

Information concerning non-IBM products was obtained from the suppliers of

those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.

All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.

All IBM prices shown are IBM's suggested retail prices, are current and are subject
to change without notice. Dealer prices may vary.

This information is for planning purposes only. The information herein is subject to
change before the products described become available.

This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.

COPYRIGHT LICENSE:

This information contains sample application programs in source language, which

illustrate programming techniques on various operating platforms. You may copy,

18 IBM Web Experience Factory: Installation Guide

 modify, and distribute these sample programs in any form without payment to
IBM, for the purposes of developing, using, marketing or distributing application
programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.

If you are viewing this information softcopy, the photographs and color
illustrations may not appear.

Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the Web at “Copyright and
trademark information” at www.ibm.com/legal/copytrade.shtml.

Notices 19
20 IBM Web Experience Factory: Installation Guide



Printed in USA