Wpf Install

8/2/2019 Wpf Install

1/24

WebSphere WebSphere Portlet Factory

Installation Guide

Version 6.1.5


2/24


3/24

WebSphere WebSphere Portlet Factory

Installation Guide

Version 6.1.5


4/24

NoteBefore using this information and the product it supports, read the information in Notices, on page 13.

First Edition

This edition applies to version 6.1.5 of IBM WebSphere Portlet Factory and to all subsequent releases andmodifications until otherwise indicated in new editions.

Copyright International Business Machines Corporation 2000, 2009.US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contractwith IBM Corp.


5/24

Contents

WebSphere Portlet Factory ProductInstallation Guide . . . . . . . . . . 1

1. Installation overview . . . . . . . . . . . 11.1 Installation steps . . . . . . . . . . . 11.2 Pre-installation information . . . . . . . 11.3 Existing installations of WebSphere PortletFactory . . . . . . . . . . . . . . . 2

2. Installing WebSphere Portlet Factory . . . . . 2Step 1 - Installing WebSphere Portlet Factory onWindows . . . . . . . . . . . . . . 2Step 1 - Installing WebSphere Portlet Factory onLinux . . . . . . . . . . . . . . . . 4Installing WebSphere Portlet Factory into RationalApplication Developer/Rational SoftwareArchitect on Linux . . . . . . . . . . . 5Installing silently from the command line. . . . 6

Step 2 - Run the tutorial: creating a Webapplication project . . . . . . . . . . . 7

3. Installation notes . . . . . . . . . . . . 73.1 WebSphere Portal configuration . . . . . . 7

3.2 Apache Tomcat . . . . . . . . . . . 73.3 Native language support for Eclipse . . . . 7

3.4 Eclipse Double byte language issues on Linux 84. Removing IBM WebSphere Portlet Factory . . . 84.1 Removing WebSphere Portlet Factory Designerfor Windows . . . . . . . . . . . . . 94.1.1 Removing WebSphere Portlet FactoryDesigner for Linux . . . . . . . . . . . 94.2 Removing project WAR files . . . . . . . 9

5. Upgrading plug-in files, projects, and portlets . . 95.1 Upgrading a project from versions 5.12, 6.0.0,6.0.1, 6.0.2, 6.1.0, and 6.1.2 . . . . . . . . 105.1 Upgrading portlets to the Java PortletStandard API . . . . . . . . . . . . . 105.2 Regenerating a portlet model . . . . . . 116. Enabling IBM Tivoli License Manager tracking 11

7. Using JAWS For Windows during installation . . 12

Appendix. Notices . . . . . . . . . . 13Trademarks . . . . . . . . . . . . . . 14

Copyright IBM Corp. 2000, 2009 iii


6/24

iv WebSphere Portlet Factory Installation Guide


7/24

WebSphere Portlet Factory Product Installation Guide

Use this guide to install IBM WebSphere Portlet Factory

About this task

This guide applies to WebSphere Portlet Factory, but the installation may involveinstalling other products.

1. Installation overview

2. Installing WebSphere Portlet Factory on page 2

3. Installation notes

4. Removing IBM WebSphere Portlet Factory on page 8

5. Upgrading plug-in files, projects, and portlets on page 9

6. Enabling IBM Tivoli License Manager tracking on page 11

7. Using JAWS For Windows during installation on page 12

1. Installation overview

About this task

This guide applies to WebSphere Portlet Factory, but the installation may involveinstalling other products.

1.1 Installation stepsAbout this task

Installation involves the following steps:

Step 1 - Install WebSphere Portlet Factory DesignerRun the installation program to install WebSphere Portlet Factory Designer.

Step 2 - Create and deploy a Web application projectUse the tutorial provided to create a Web application project that youdeploy to your application server or portal server.

1.2 Pre-installation informationAbout this task

The default Installation selection will include a supported version of Eclipse.Alternatively, WebSphere Portlet Factory can be installed into a supported version

of one of the following IDEs:IBM Rational Application Developer

IBM Rational Software Architect

IBM Rational Web Developer

Eclipse (Eclipse SDK versions only)

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

Copyright IBM Corp. 2000, 2009 1


8/24

Note: To install WebSphere Portlet Factory into a Rational IDE on a system using alanguage other than English, you must first edit the fileinstaller.properties and modify the path specified on the line whichstarts with PRODUCTREG_PATH= to accurately specify the path on your system.

1.3 Existing installations of WebSphere Portlet Factory

About this taskIf you have an existing installation of WebSphere Portlet Factory do not install thenew 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 newinstallation.

2. Installing WebSphere Portlet Factory

About this task

First, follow the steps described in one of the following sections to installWebSphere Portlet Factory on the desired platform.

v Step 1 - Installing WebSphere Portlet Factory on Windows

v Installing on Linux platforms

Step 1 - Installing WebSphere Portlet Factory on Linux on page 4

Installing WebSphere Portlet Factory into Rational ApplicationDeveloper/Rational Software Architect on Linux on page 5

v Installing silently from the command line on page 6

Then, you can follow the steps described in Step 2 - Run the tutorial: creating aWeb application project on page 7 to begin exploring the product.

Step 1 - Installing WebSphere Portlet Factory on WindowsAbout this task

1. If you are on the Microsoft Vista system, run with Administrator accountrights.

To run WebSphere Portlet Factory Designer on the Microsoft Vista system, youmust install WebSphere Portlet 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 prompted, select your preferred language for using the product.

4. An introduction page displays with copyright and other information. Toproceed with installation, then click Next

5. Read the license agreement and select I accept the terms of the LicenseAgreement to proceed with installation, then click Next.

Note: If you do not accept the license terms, you will be prompted to quit theinstallation.

2 WebSphere Portlet Factory Installation Guide


9/24

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 WebSphere Application ServerCommunity Edition with your WebSphere Portlet Factory installation. If thisoption is selected, the installation program installs Eclipse, WebSpherePortlet Factory Designer, and IBM WebSphere Application Server

Community Edition (WAS CE) . If you choose this option, skip to step 9.v Custom installation enables you to choose features and installation

options

Select this option if you need to specify in detail your software options andtheir installation location.

In the Select installation directory field, specify the location to installWebSphere Portlet Factory files and click Next.

7. In the Specify install items screen, select an integrated developmentenvironment (IDE) to use with WebSphere Portlet Factory Designer. You canchoose 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, theinstallation program installs Eclipse and WebSphere Portlet FactoryDesigner.

Note: If you select this option and select a directory that contains anexisting installation of Eclipse, a warning message displays. Choose adifferent directory to continue the installation.

v Install into existing IBM Rational Application Developer*

Select this option if you want to use a Rational Development Environmentyou have already installed. This includes Rational Application Developer,Rational Software Architect, and Rational Web Developer. The installationprogram will add Portlet Factory-specific menu items to the current versionof your Rational Development Environment.

v Install into existing Eclipse

Select this option to use a version of the Eclipse-based IDE that is alreadyinstalled. The installation program adds to the current version of yourEclipse IDE menu items specific to WebSphere Portlet Factory Designer.

8. In the Specify IDE screen, specify the IDE location and click Next. If you needto browse for the location, click Choose.

9. The option to install IBM WebSphere Application Server Community Edition(WAS CE) displays (Windows only). WAS CE is an open source Java 2Platform, Enterprise Edition (J2EE) application server based on ApacheGeronimo. You can use WAS CE to enable quick and easy development andtesting of applications. Click Install WAS CE as a development test serverand choose the install location if you want to install WAS CE.

10. Review the Pre-Installation Summary screen, and, if all information is correct,click Install. An Install progress screen is displayed and, once installation iscomplete, the Install Complete screen is displayed.

11. Click Done to close the Factory installer.

A browser opens and displays a Welcome page containing information aboutNext Steps. Upon successful installation, an install log is created in the installlocation (for example, C:\Program Files\IBM\WebSphere Portlet Factory).

12. If you install into an existing Eclipse-based WebSphere Portlet FactoryDesigner installation, you must upgrade WebSphere Portlet Factory Designer

WebSphere Portlet Factory Product Installation Guide 3


10/24

plug-ins if you are installing over a previous version of WebSphere PortletFactory. For information about the steps required to upgrade plug-ins, seeAppendix A.

Step 1 - Installing WebSphere Portlet Factory on LinuxBefore you begin

Before you install WebSphere Portlet Factory, you should install:

v An application server such as Tomcat, WAS CE or IBM WebSphere Portal.

v Eclipse with Web Tools or Rational Application Developer. Check the WebSpherePortlet Factory release notes for the supported Eclipse release.

About this task

To install WebSphere Portlet Factory into an existing Rational ApplicationDeveloper/Rational Software Architect installation on Linux, follow the proceduresdescribed in Installing WebSphere Portlet Factory into Rational ApplicationDeveloper/Rational Software Architect on Linux 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 havewrite permissions to the WebSphere directories.

b. With WebSphere Application Server running, open the administrationconsole, and navigate to: Application servers WebSphere_Portal Process Execution. Change the umask value to 002. Change the run asgroup to wpfDev. Perform the same step for server1.

This will allow you to change the file permissions for the portal server. Anyfile written by the portal server will now have read / write executepermissions for the portal user, and the group to which the 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 /AppServer/chgrp -R wpfDev /PortalServer/

If the directories are not writable by group, then run the followingcommands:

chmod -R g+w /AppServer/chmod -R g+w /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 otherprerequisites and displays the first panel.

3. When prompted, select your preferred language for using the product.

4. An introduction page displays with copyright and other information. Toproceed with installation, then click Next

5. Read the license agreement and select I accept the terms of the LicenseAgreement to proceed with installation, then click Next.



11/24

Note: If you do not accept the license terms, you will be prompted to quit theinstallation.

6. In the Choose Install Folder screen, specify the location to install WebSpherePortlet Factory files and click Next.

7. Specify the location where Eclipse with Web Tools is installed and click Next Ifyou are using Rational Application Developer choose the default and click Next

8. Review the Pre-Installation Summary screen, and, if all information is correct,click Install. An Install progress screen is displayed and, once installation iscomplete, the Install Complete screen is displayed.

9. Click Done to close the Factory installer.

A browser opens and displays a Welcome page containing information aboutNext Steps. Upon successful installation, an install log is created in the installlocation (for example, /root/IBM/).

Installing WebSphere Portlet Factory into Rational ApplicationDeveloper/Rational Software Architect on Linux

About this task

If you are installing WebSphere Portlet Factory into an existing RationalApplication Developer/Rational Software Architect installation on Linux, performthese steps.

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 havewrite permissions to the WebSphere directories.

b. With WebSphere Application Server running, open the administrationconsole, and navigate to: Application servers WebSphere_Portal Process Execution. Change the umask value to 002. Change the run asgroup to wpfDev. Perform the same step for server1.

This will allow you to change the file permissions for the portal server. Anyfile written by the portal server will now have read / write executepermissions for the portal user, and the group to which the portal user

belongs.

c. Stop the WebSphere Portal server.

d. Make yourself a member of the newly created group (wpfDev in thisexample).

e. From a command line run the following commands as root:

chgrp -R wpfDev /AppServer/chgrp -R wpfDev /PortalServer/

If the directories are not writable by group, then run the following

commands:chmod -R g+w /AppServer/chmod -R g+w /PortalServer/

This allows write access to the those folders after the WAR files aredeployed.

f. Restart WebSphere Portal server.

2. Install WebSphere Portlet Factory with the user account of the WebSpherePortlet Factory user.



12/24

The Eclipse installation location should be a directory that the user account haswrite access to. You may need to choose a location other than the RationalApplication Developer installation location. There does not need to be anexisting Eclipse in this location.

3. If you chose to install Eclipse into the Rational Application Developer installlocation 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 correctdirectory in the Rational Application Developer install location.

The links folder should be located just within the Rational ApplicationDeveloper installation directory.

v You can also copy the WebSphere Portlet Factory link file directly to apreviously created links directory within Rational Application Developer.

4. Start Rational Application Developer with the -clean flag as root (or theRational Application Developer owner) and verify WebSphere Portlet Factory isinstalled.

Use Help About to verify that the WebSphere Portlet Factory button displays.

5. Restart Rational Application Developer with the -clean flag as the WebSpherePortlet Factory user, if it is not the user in the previous step, and verify as inthe previous step.

6. Restart Rational Application Developer normally as the WebSphere PortletFactory user.

You do not need to use the -clean flag at this point.

Installing silently from the command lineAbout this task

You can perform a silent installation of WebSphere Portlet Factory.

1. Create a install response file. In Windows, open a command line and enter:c:\Factory.exe -r c:\myinstaller.properties or in Linux enter sh./Factory.bin -r /myinstaller.properties where you specify the location ofyour response file, in this example, myinstaller.properties. Complete theinstallation as desired.s

2. Indicate the location of the response file. For Windows, open a command lineand enter c:\Factory.exe -f c:\installer.properties , for Linux enter: sh./Factory.bin -f \installer.properties , This path can be absolute orrelative to the location of the installer.

3. Run the installation in silent mode: In Windows open a command line andenter: c:\Factory.exe -i silent or in Linux enter: sh ./Factory.bin -iconsole

Results

The installer installs everything to the target location without showing the user anyoutput. You know the installation is complete when the log file is created in theroot of the installer directory.



13/24

Step 2 - Run the tutorial: creating a Web application projectAbout this task

Once you successfully install the WebSphere Portlet Factory Designer, you mustcreate a new project. In creating a project, you provide application server-specificand portal server-specific information about your installation. This process

completes the deployment phase of WebSphere Portlet Factory installation.

The WebSphere Portlet Factory Designer provides a New Project wizard to helpyou create a project. This multi-page wizard walks you through the steps involvedin project creation and deployment and also builds the project for you. F1 Helpthat describes project settings and parameters is available for each page of thewizard. Refer to F1 Help to learn about the settings on a given page and to accesslinks to additional information.

The best way to create your first project is to run the tutorial that describes thisprocess. If you are using a Windows client, this tutorial is available from theWelcome page, or from Start. Click Start Programs IBM WebSphere PortletFactory Tutorials. If you are using a Linux client, this tutorial is available from

the WebSphere Portlet Factory Help system.

3. Installation notes

About this task

You may have to set class loading order for IBM WebSphere Application Server orprovide additional configuration steps for IBM WebSphere Portal.

3.1 WebSphere Portal configurationAbout this task

The following additional configuration step is required for WebSphere Portal 6:

Configure heap size

By default, WebSphere Portal 6 sets 512 MB as the maximum allowed size for theheap. Raise this maximum to 1 GB.

Use the WebSphere Administrative console to set the heap size. For moreinformation about configuring the heap size, see the WebSphere AdministrativeConsole Help.

3.2 Apache TomcatAbout this task

After you run the WebSphere Portlet Factory Designer New WebApp Projectwizard, restart Tomcat. This ensures that all libraries are loaded correctly.

3.3 Native language support for EclipseAbout this task

WebSphere Portlet Factory Designer supports the following languages: German,Spanish, French, Italian, Japanese, Korean, Portuguese (Brazil), Traditional Chineseand Simplified Chinese.



14/24

To use WebSphere Portlet Factory Designer in a language other than English, youmust download a language pack from the Eclipse Web site, and install that packinto your Eclipse IDE. To enable Group 1 language support:

1. Halt WebSphere Portlet Factory Designer.

2. Access the Eclipse.org Web site home page and navigate to Downloads AllVersions 3.2 Language Packs.

3. In the Language Packs: 3.2.x screen, download the NL-1 pack zip files for theWindows platform.

Two zip files are required.

4. Extract these archive files to your Eclipse installation location and ensure thatyou use the correct directory level.

5. Start WebSphere Portlet Factory Designer. If Microsoft Windows is configuredto 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 thenames of folders in the path.

6. Optional: You can force Eclipse to run in any Group 1 language by adding alanguage identifier to the Eclipse startup command.

For example, if you add the following identifiers to the startup command, youcan run Eclipse in Spanish, regardless of the language the system is configuredto use:

-Duser.language=es -Duser.country=ES

Note: The same languages are supported in IBM Rational ApplicationDeveloper. If you want to install language support into ApplicationDeveloper, use the Installation Manager (or install it when you installApplication Developer). See to the Application Developer documentationfor instructions on installing language support.

3.4 Eclipse Double byte language issues on Linux

About this task

Linux installations of WebSphere Portlet Factory on double byte languages may notdisplay 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 yourlanguage selection. For example:

/Factory.bin LAX_VM $JAVA_HOME/bin/java

Note: The same languages are supported in IBM Rational Application Developer,and for users to refer to the Application Developer documentation forinstructions on installing language support.

4. Removing IBM WebSphere Portlet Factory

About this task

Follow the steps in 4.1 Removing WebSphere Portlet Factory Designer forWindows on page 9 or 4.1.1 Removing WebSphere Portlet Factory Designer forLinux on page 9 (depending on your client platform) and then 4.2 Removingproject WAR files on page 9 to remove WebSphere Portlet Factory Designer filesand project WAR files.



15/24

4.1 Removing WebSphere Portlet Factory Designer forWindows

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: You can uninstall WebSphere Portlet Factory and not uninstallWebSphere Application Server Community Edition. You can then installa new version of WebSphere Portlet Factory and not install WebSphereApplication Server Community Edition (because you already have aversion). If you run WebSphere Application Server Community Editioneither from the Start menu or from WebSphere Portlet Factory, you getan error that WebSphere Application Server Community Edition cannotfind the java.exe file.

To avoid this problem, open the file \wasceInstallDir\bin\setenv.batand edit the following line.

set WASCE_JAVA_HOME=

Set the value to a JRE on the system. For example, use the one installedin Eclipse (C:\Program Files\eclipse\jre).

4.1.1 Removing WebSphere Portlet Factory Designer for LinuxBefore you begin

With a Linux installation, you will need to manually remove certain files anddirectories created by the installer.

1. Delete the Designer directory and the log file in the installation directory.

2. Delete the /license directory if desired

3. Delete the WebSphere Portlet Factory link file calledcom.bowstreet.designer.link which is located in the /linksdirectory. For example, /opt/IBM/SDP75/links

4.2 Removing project WAR files1. 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 benecessary to manually delete any remaining application or portlet relateddirectories and files.

5. Upgrading plug-in files, projects, and portletsAbout this task

This section discusses the procedures required to upgrade IBM WebSphere PortletFactory plug-in files if you have installed a new version of WebSphere PortletFactory 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 ofWebSphere Portlet Factory Designer to the latest project version. Finally, thissection describes how to upgrade portlets to the Java Portlet Standard API.



16/24

5.1 Upgrading a project from versions 5.12, 6.0.0, 6.0.1, 6.0.2,6.1.0, and 6.1.2

Before you begin

When upgrading flat projects, create a new project and migrate your content to itusing the Export WebSphere Portlet 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 theadded benefits of facet support if you upgrade a flat project.

About this task

You must modify any projects that you created using the old plug-in files so thatthese projects can include changes related to the new plug-in files and feature sets.To upgrade a project, do this:

1. Open an existing project into WebSphere Portlet Factory Designer.

2. Right-click the project entry in the Project Explorer and click WebSpherePortlet Factory Project Upgrade Project Version.

3. A summary information displays. Click Next.

4. Update the deployment information for this project if necessary. Check thedeployment configuration and click Finish in the upgrade wizard.

5. Before the upgrade process completes, you may be prompted to overwrite anyWebSphere Portlet Factory files in the project that have changed, including filesthat were changed by WebSphere Portlet Factory functionality, not necessarilyfiles that you have changed manually.

6. You will need to redeploy the project to the servers. Click Yes when promptedto redeploy.

7. Right-click the project in the workspace.

8. Click Properties WebSphere Portlet Factory Properties Feature Info.

9. Set Refresh installed Feature Sets and then click OK.

What to do next

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

5.1 Upgrading portlets to the Java Portlet Standard APIAbout this task

As of WebSphere Portal 6, there is support for Java Portlet Standard API forWebSphere portlets. While portlets designed for use in previous version ofWebSphere Portal and built using the deprecated WebSphere Native portlet APIcontinue to run in WebSphere Portal 6, 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 NativePortlet API to the Java Portlet Standard API. To do so, you must modify the projectthat contains the portlet models.

Note: If you have already upgraded the project, you can switch to Java PortletStandard API by switching the project to a Java Portlet Standard API Portaldeploy configuration by uninstalling the old WAR as described in the



17/24

following steps and updating the project to use the Java Portlet StandardAPI deploy configuration. Redeploy when prompted

To upgrade a portlet built in a previous version of the WebSphere Portlet Factoryto use the new Java Portlet Standard API, perform the following steps:

1. Load the project containing the portlet model into the WebSphere PortletFactory Designer.

2. Select the project and click WebSphere Portlet Factory Project Upgradeproject version.

3. Using the WebSphere Portlet Administration tool, remove the old portlet WARfile from the WebSphere Portal server. (If the project has already beenupgraded, switch the project to a Java Portlet Standard API Portal deployconfiguration, then update the project to use the Java Portlet Standard APIdeploy configuration and redeploy when prompted.)

4. In WebSphere Portlet Factory Designer, use the Project DeploymentConfigurations dialog to deploy the updated portlet WAR file to theWebSphere Portal server.

5. Use the WebSphere Administration tool to place the updated portlets on

WebSphere Portal pages.

5.2 Regenerating a portlet modelIf you have a model that uses the Cooperative Portlet Source builder or theCooperative Portlet Target builder and the project uses the Java Portlet Standard2.0 API (JSR 286), regenerate the model.

About this task

These steps are required to capture new event metadata that did not exist in priorreleases of WebSphere Portlet 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.

Results

This procedure captures the new event metadata.

6. Enabling IBM Tivoli License Manager trackingAbout this task

IBM Tivoli License Manager (ITLM) recognizes and monitors what products andtheir versions, releases, and fix packs are installed, and used, on a system. Thisallows 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 variousIBM software packages.

The usage of applications and portlet WAR files created with the IBM WebSpherePortlet Factory can be monitored and tracked by Tivoli License Manager. To enable



18/24

this capability, you must place at the root level of an application or portlet EAR filecertain files that are generated by the WebSphere Portlet 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 seea 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 movethe WEB-INF\bin\itlm\ directory to the root of the EAR file.

What to do next

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

7. Using JAWS For Windows during installation

If you want to install WebSphere Portlet Factory and use the JAWS screen readerfor accessibility, you need to perform the following additional step to correctlystart the installation.

Before you begin

You need to have Java Access Bridge for Microsoft Windows Operating Systemsoftware installed on your system. Java Access Bridge for Microsoft WindowsOperating System is provided by Sun Microsystems, Inc, Copyright (c) 2006 SunMicrosystems, Inc.

About this task

Use the following command to start the WebSphere Portlet Factory installation:

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

Results

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

What to do next

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



19/24

Appendix. 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 inother countries. Consult your local IBM representative for information on theproducts and services currently available in your area. Any reference to an IBMproduct, program, or service is not intended to state or imply that only that IBMproduct, 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 users responsibility to evaluate and verify theoperation of any non-IBM product, program, or service.

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

IBM Director of LicensingIBM CorporationNorth Castle DriveArmonk, NY 10504-1785U.S.A.

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

IBM World Trade Asia CorporationLicensing2-31 Roppongi 3-chome, Minato-kuTokyo 106-0032, Japan

The following paragraph does not apply to the United Kingdom or any othercountry where such provisions are inconsistent with local law:INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THISPUBLICATION AS IS WITHOUT WARRANTY OF ANY KIND, EITHEREXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESSFOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express orimplied warranties in certain transactions, therefore, this statement may not applyto you.

This information could include technical inaccuracies or typographical errors.Changes are periodically made to the information herein; these changes will beincorporated in new editions of the publication. IBM may make improvementsand/or changes in the product(s) and/or the program(s) described in thispublication at any time without notice.

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

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

Copyright IBM Corp. 2000, 2009 13


20/24

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

IBM CorporationOffice 4360One Rogers StreetCambridge, MA 02142U.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 information and all licensed materialavailable for it are provided by IBM under terms of the IBM Customer Agreement,IBM International Program License Agreement, or any equivalent agreement

between us.

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

Supplemental Copyrights and Acknowledgments

The following Copyrights and Acknowledgments apply to various softwarecomponents included in IBM WebSphere Portlet Factory, but neither created norowned by IBM.

This offering is based on technology from the Eclipse Project (http://

www.eclipse.org/).

This product includes software developed by the Apache Software Foundation(http://www.apache.org).

Portions of this software provided by JDOM. Copyright (C) 2001 Brett McLaughlin& Jason Hunter. All rights reserved. Portions of this software provided by themembership of the XML-DEV mailing list. You can obtain a copy of the SAXcopyright status at http:// www.megginson.com /SAX/.

Trademarks

The following terms are trademarks of International Business Machines

Corporation in the United States, other countries, or both:

IBMLotusWebSphereWorkplacePortlet Factory

Microsoft and Windows are trademarks of Microsoft Corporation in the UnitedStates, other countries, or both.



21/24

Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in theUnited States, other countries, or both.

Other company, product, or service names may be trademarks or service marks ofothers.

Appendix. Notices 15


22/24



23/24


24/24

Printed in USA

Wpf Install

Documents

Transcript of Wpf Install