Installing DevPartner Java Edition - Micro Focus · iv Installing DevPartner Java Edition Chapter 3...

InstallingDevPartner

Java EditionRelease 4.1

Technical support is available from our Technical Support Hotline or via our FrontLine Support Web site.

Technical Support Hotline:1-888-686-3427

Frontline Support Web Site:http://frontline.compuware.com

© 2001, 2004, 2005, 2006 Compuware Corporation. All rights reserved. Unpublished - rights reserved under the Copyright Laws of the United States.

U.S. GOVERNMENT RIGHTS

Use, duplication, or disclosure by the U.S. Government is subject to restrictions as set forth in Compuware Corporation license agreement and as provided in DFARS 227.7202-1(a) and 227.7202-3(a) (1995), DFARS 252.227-7013(c)(1)(ii)(OCT 1988), FAR 12.212(a) (1995), FAR 52.227-19, or FAR 52.227-14 (ALT III), as applicable. Compuware Corporation.

THIS PRODUCT CONTAINS CONFIDENTIAL INFORMATION AND TRADE SECRETS OF COMPUWARE CORPORATION. USE, DISCLOSURE, OR REPRODUCTION IS PROHIBITED WITHOUT THE PRIOR EXPRESS WRITTEN PERMISSION OF COMPUWARE CORPORATION. ACCESS IS LIMITED TO AUTHORIZED USERS. USE OF THIS PRODUCT IS SUBJECT TO THE TERMS AND CONDITIONS OF THE USER’S LICENSE AGREEMENT WITH COMPUWARE CORPORATION.

US Patent Nos.: 6,186,677, 6,314,558, and 6,016,466

Compuware, DevPartner, and OptimalJ are trademarks or registered trademarks of Compuware Corporation.

UNIX is a registered trademark of The Open Group in the U.S. and other countries.

Java is a trademark of Sun Microsystems Inc.

Acrobat® Reader copyright © 1987–2006 Adobe Systems Incorporated. All rights reserved. Adobe, Acrobat, and Acrobat Reader are trademarks of Adobe Systems Incorporated.

All other company or product names are trademarks of their respective owners.

January 20, 2006

CWM6IX4B

Table of Contents

PrefaceWhat This Manual Covers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . vii

Conventions Used In This Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Customer Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . viii

Chapter 1System RequirementsHardware Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1

Supported Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2Java Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4Integrated Development Environments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6Web Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Chapter 2Installing DevPartner Java Edition on WindowsInstalling DevPartner Java Edition on Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . 11

Preparing to Install . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11Performing the Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12

Configuring Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Integrating DevPartner Java Edition with IDEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

Installing the DevPartner Java Edition License . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Installing the Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

Uninstalling DevPartner Java Edition on Windows . . . . . . . . . . . . . . . . . . . . . . . . 16

iii

Chapter 3Installing DevPartner Java Edition on SolarisInstalling DevPartner Java Edition on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17




Installing the Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19

Uninstalling DevPartner Java Edition on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Chapter 4Installing DevPartner Java Edition on LinuxInstalling DevPartner Java Edition on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21




Installing the Java 2 Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23

Uninstalling DevPartner Java Edition on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . 24

Chapter 5Installing DevPartner Java Edition on AIXInstalling DevPartner Java Edition on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25




Uninstalling DevPartner Java Edition on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Chapter 6Installing DevPartner Java Edition on HP-UXInstalling DevPartner Java Edition on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29




Uninstalling DevPartner Java Edition on HP-UX . . . . . . . . . . . . . . . . . . . . . . . . . . 31

iv Installing DevPartner Java Edition

Chapter 7Configuring Application ServersDevPartner Java Edition Administration Console . . . . . . . . . . . . . . . . . . . . . . . . . . 33

Creating a Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34Apache Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35Apache Tomcat as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35BEA WebLogic 8.1.x and 9.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36BEA WebLogic 8.1.x and 9.0 as a Windows Service . . . . . . . . . . . . . . . . . . . . . 37IBM WebSphere 5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37IBM WebSphere 6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38IBM WebSphere as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39JBoss as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39Oracle Application Server (OC4J Integrated) . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Oracle OC4J Standalone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Sun ONE 7.0 as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Sun Java System Application Server Platform Edition 8.0 . . . . . . . . . . . . . . . . . 41Generic Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Generic Application Server as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . 43

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45

Table of Contents v

vi Installing DevPartner Java Edition

Preface

� What This Manual Covers

� Conventions Used In This Manual

� Customer Support

What This Manual CoversThis manual contains the following chapters:

� Chapter 1, System Requirements — Minimum hardware requirements, and supported application servers, Integrated Development Environments (IDEs), Web browsers, and licensing information.

� Chapter 2, Installing DevPartner Java Edition on Windows.

� Chapter 3, Installing DevPartner Java Edition on Solaris.

� Chapter 4, Installing DevPartner Java Edition on Linux.

� Chapter 5, Installing DevPartner Java Edition on AIX.

� Chapter 6, Installing DevPartner Java Edition on HP-UX.

� Chapter 7, Configuring Application Servers.

vii

Conventions Used In This ManualThis book uses the following conventions to present information.

� Screen commands and menu names appear in bold typeface. For example:

From the Tools menu, choose Item Browser.

� Computer commands appear in monospace typeface. For example:

At the command line, enter dpjadmin.

� File and path names appear in bold monospace typeface. For example:

In Windows, the default product directory is C:\Program Files\Compuware\DevPartner Java Edition.

� Variables (for which you must supply values appropriate for your installation) within computer commands and file names appear in italic monospace type. For example:

Enter http://servername/cgi-win/itemview.dll in the Destination field.

Customer SupportCustomer Support can assist you with all your technical problems, from installation to troubleshooting.

Before contacting Customer Support, please read the relevant sections of the product documentation and the Release Notes (ReadMeDPJ.htm).

You can contact Customer Support by:

E-Mail Send as many details as possible to [email protected]

World Wide Web Submit issues and access our support knowledge base through FrontLine, http://frontline.compuware.com/.

Telephone Telephone support is available as a paid* Priority Support Service from 8:00 am to 5:00 pm Eastern time, Monday through Friday. Have your product release number ready. In the U.S. and Canada, call: 1-888-686-3427For telephone support numbers outside the USA, Canada, and Latin America, see Compuware's FrontLine Web site: http://frontline.compuware.com/.

* Customer Support handles installation and setup issues free of charge.

viii Installing DevPartner Java Edition

Before contacting Customer Support, please obtain the following information:

� Product name (or edition), release, or service pack� System configuration: operating system, network configuration,

amount of RAM, environment variables, and paths� Name and version of your compiler and linker and the options you

used in compiling and linking� Problem details: settings, error messages, stack dumps, and the

contents of any diagnostic windows� If the problem is repeatable, the details of how to create the problem

Preface ix

x Installing DevPartner Java Edition

Chapter 1

System Requirements

� Hardware Requirements� Supported Environments� Licensing

Hardware RequirementsWindows DevPartner Java Edition requires the following minimum configuration

for Windows systems:

� Intel Architecture 32-bit

� Pentium III 500 MHz or equivalent

� 512 MB total system memory

� 100 MB of free disk space

� 800 x 600 graphics resolution

Solaris DevPartner Java Edition requires the following minimum configuration for Solaris systems:

� Sparc Ultra 5




Linux DevPartner Java Edition requires the following minimum configuration for Linux systems:

� Intel Architecture 32-bit

� Pentium III 500 MHz or equivalent

1




AIX DevPartner Java Edition requires the following minimum configuration for AIX systems:

� AIX 5.2 (for RS/6000 Power and P Series)



HP-UX DevPartner Java Edition requires the following minimum configuration for HP-UX systems:

� HP-UX 11i for PA/RISC



Supported EnvironmentsThe following supported environments are described below:

� Operating Systems

� Java Virtual Machines (page 3)

� Application Servers (page 4)

� Integrated Development Environments (page 6)

� Web Browsers (page 7)

� Languages (page 8)

Operating Systems

DevPartner Java Edition supports the following operating systems:

� Microsoft Windows XP Professional Edition, with SP1 or SP2

� Microsoft Windows 2000 SP3 or SP4, Professional, Server, and Advanced Server Editions

� Microsoft Windows 2003 Server (Standard and Enterprise Editions)

� Solaris 9 and 10

� Red Hat Enterprise Linux 3.0 and 4.0 (AS, ES, and WS Editions)

2 Installing DevPartner Java Edition

� AIX 5.2 and 5.3

If you are running AIX 5.2, you must install X11.base.rte Version 5.2.0.1 or later before installing DevPartner Java Edition.

For both versions of AIX (5.2 and 5.3), the SDK should be Version 1.3.1.6 or higher.

� HP-UX Release 11i v1 or 11i v2

The HP-UX 11i v1 Quality Pack (GOLDQPK11i) patch bundle, December 2003. Patch PHSS_30049 is required. All HP-UX 11 patches required by the JVM should be installed. Consult the vendor for the list of required patches.

The SDK should be Version 1.3.1.6 or higher.

Java Virtual Machines

DevPartner Java Edition requires one of the following Java Virtual Machines (JVMs).

Table 1-1. Supported Java Virtual Machines

These JVMs... Run on These Operating Systems

HP 1.3.1, 1.4, and 5.0 (32-bit) HP-UX 11i and 11i v2

IBM 1.3.1 (32-bit) Only with IBM WebSphere on these operating systems:

• Windows 2000, Windows XP, and Windows 2003 Server

• Red Hat Enterprise Linux 3.0 and 4.0

IBM 1.4 (32-bit) With all supported application servers:

• AIX 5.2 and 5.3

Only with IBM WebSphere:


• Solaris 9


• HP-UX 11i

Sun 1.3.1 (32-bit) • Windows 2000, Windows XP, and Windows 2003 Server

• Solaris 9

Sun 1.4 (32-bit) • Windows 2000, Windows XP, and Windows 2003 Server

• Solaris 9 and 10


Chapter 1� System Requirements 3

1 Because of an issue in Sun's release of Java 5.0, Memory analysis may not work cor-rectly if class data sharing is enabled. The Win32 release of the Sun J2SE 5.0 enables class data sharing by default and it must be explicitly disabled. To disable class data sharing, pass -Xshare:off as a command line parameter to Java. With DevPartner Java Edition, you can also disable class data sharing by creating a global environ-ment variable named NM_VM_OPTIONS and setting it to -Xshare:off.

Application Servers

DevPartner Java Edition can profile applications running on the following application servers.

Sun 5.0 (32-bit)[See Note 1 below]




JRockit 1.4.2_05 (32-bit) • Windows 2000, Windows XP, and Windows 2003 Server


Table 1-1. Supported Java Virtual Machines (Continued)

These JVMs... Run on These Operating Systems

Table 1-2. Supported Application Servers

These Application Servers... Run on These Operating Systems

Apache Tomcat 5.0 and 5.5 • Windows 2000, Windows XP, and Windows 2003 Server



• AIX 5.2 and 5.3

• HP-UX 11i and 11i v2

BEA WebLogic Server 8.1.x • Windows 2000, Windows XP, and Windows 2003 Server

• Solaris 9


• AIX 5.2 and 5.3

• HP-UX 11i and 11i v2

BEA WebLogic Server 9.0 [See Note 1]




• HP-UX 11i and 11i v2 [See Note 2]


1 You must use Sun JDK with WebLogic 9.0. WebLogic uses JRockit 5.0 by default, but because of a JRockit bug, Memory analysis cannot be performed on applica-tions running under this JVM. On Windows 2000, Weblogic 9.0 requires

2 For HP-UX 11i v2, you must use WebLogic 9.1.

IBM WebSphere 5.1 Standard and Enterprise Editions

• Windows 2000 and Windows 2003 Server

• Solaris 9


• AIX 5.2 and 5.3

• HP-UX 11i

IBM WebSphere 6.0 Standard Edition


• Solaris 9


• AIX 5.2 and 5.3

• HP-UX 11i

IBM WebSphere Portal 5.1 Only with IBM Radical Application Developer 6.0:


JBoss 3.2 and 4.0 • Windows 2000, Windows XP, and Windows 2003 Server


Oracle OC4J Standalone v9.0.4 • Windows 2000, Windows XP, and Windows 2003 Server

• Solaris 9

• Red Hat Enterprise Linux 4.0

Oracle Application Server (called OC4J Integrated in DevPartner Java Edition), v9.0.4 Standard, Enterprise, and Java Editions


• Solaris 9


Sun ONE 7.0 (also called Java System Application Server Platform Edition 7.0)

• Windows 2000 and Windows XP

• Solaris 9

Sun Java System Application Server Platform Edition 8.0


• Solaris 9

Table 1-2. Supported Application Servers (Continued)

These Application Servers... Run on These Operating Systems


Integrated Development Environments

DevPartner Java Edition can be used with the following Integrated Development Environments (IDEs). IDE integration is supported only on Windows platforms.

Table 1-3. Supported Integrated Development Environments

These IDEs... On These Application Servers

Borland JBuilder X, Enterprise, Enterprise Studio, Foundation, and Developer Editions

• BEA WebLogic 8.1.x

Borland JBuilder 2005, Enterprise, Enterprise Studio, Foundation, and Developer Editions

• Apache Tomcat 5.0


Compuware OptimalJ 3.3.01 (Architecture, Professional, and Developer Editions)

• JBoss 3.2 and 4.0


• IBM WebSphere Application Server 5.1

Compuware OptimalJ 4.0 (Architecture, Professional, and Developer Editions)

• JBoss 4.0


• IBM WebSphere Application Server 6.0 (integrated)

Eclipse 3.0 • BEA WebLogic 8.1.x

• JBoss 3.2

Eclipse 3.1 • BEA WebLogic 8.1.x and 9.0

• JBoss 3.2 and 4.0

IBM Rational Application Developer 6.0

• Apache Tomcat 5.0

• IBM WebSphere Application Server 5.1 and 6.0 (integrated)

• IBM WebSphere Portal 5.1 - Test Environment

IBM WebSphere Application Server - Express 5.1

• IBM WebSphere Application Server - Express 5.1

IBM WebSphere Studio Application Developer 5.1

• IBM WebSphere Application Server 5.1 (integrated)

Oracle JDeveloper 9.0.4 • Oracle OC4J Standalone 9.0.4

• Oracle Application Server 9.0.4 (called OC4J Integrated in DevPartner Java Edition)


Web Browsers

The user interface for DevPartner Java Edition requires one of the following Web browsers:

� Internet Explorer Version 6 with or without SP1

� Mozilla 1.7

� Netscape 7.1

Required: If the browser includes a popup blocker, configure it to disable blocking for the DevPartner Java Edition window. If the popup blocker is enabled, DevPartner Java Edition will not operate correctly.

The Web-based user interface is only supported on the following operating systems:

� Windows 2000, Windows XP, and Windows 2003 Server

� Solaris 9 and 10

� Red Hat Enterprise Linux 3.0 and 4.0

DevPartner Java Edition requires one of the following Sun JRE plug-ins for your Web browser:

� 1.3.1� 1.4.0� 1.4.1� 1.4.2� 5.0

Note: When you upgrade DevPartner Java Edition, you should clean out the Java plug-in's cache. If the cache contains applets from a previous release, the browser-based UI may not be displayed correctly. You may also be able to disable the plug-in's option to cache applets. See the documentation for your plug-in for further information.

Oracle JDeveloper 9.0.5 • Oracle OC4J Standalone 9.0.4

• Oracle Application Server 9.0.4 (called OC4J Integrated in DevPartner Java Edition)

Table 1-3. Supported Integrated Development Environments (Continued)

These IDEs... On These Application Servers


Languages

This release of DevPartner Java Edition only has localization support for English (United States — en-us).

LicensingThe following license types are available for DevPartner Java Edition.

DevPartner Java Edition is installed with a 14-day evaluation license. To use the program beyond the evaluation period, you must obtain a permanent license. A license file, license.xml, is provided by Compuware License Management for each license that you purchase.

Table 1-4. License Types

License Type Description

User DevPartner Java Edition has two types of user licenses:

• Single-seat — The DevPartner Java Edition Web server, control service, and browser must be on one machine.

Single-seat licensing requires a license file for each installation.

This license type is not supported on AIX and HP-UX.

• Concurrent — Any users, up to the maximum specified by the license, can launch DevPartner Java Edition, create or view session files; and create or use configuration files on a single local machine.

To access a remote DevPartner Java Edition server, a server license must be installed on that remote machine.

Server A server license enables a user with remote access (through a browser) to the DevPartner Java Edition server machine to create or view session files, and to create or use configuration files on the DevPartner Java Edition server.

DevPartner Java Edition has two types of server licenses:

• Node-locked — The license is installed on a specific DevPartner Java Edition server machine, and can be used only with that machine.

• Concurrent — The license is installed on the license server. Any user can connect with any DevPartner Java Edition server, up to the maximum number of connections specified in the license. When a user accesses a DevPartner Java Edition server, a license is checked out until that connection is ended. After the license is freed by ending the server connection, it can be used with any other DevPartner Java Edition server.


Your license file(s) will arrive by e-mail around the time that your installation kit arrives, and is delivered to the person you designated when you placed your order.

Note: If you purchased DevPartner Java Edition from a reseller, request a license file by calling Compuware Worldwide License Management at 1-800-538-7822. You can also register over the Web at http://www.compuware.com/license.

If your license file has not arrived by the time you want to install DevPartner Java Edition, contact Worldwide License Management at 1-800-538-7822. Outside the USA and Canada, contact your local Compuware office or agent.

If you already have a licensed Compuware product and want to merge the license files, contact Technical Support at 1-888-686-3427 for assistance.

For information about installing and using Compuware licenses, refer to the Distributed License Management License Installation Guide. This document is available on the installation CD as CPWR_License_Install.pdf.


Chapter 2

Installing DevPartner Java Edition on Windows

� Installing DevPartner Java Edition on Windows

� Configuring Application Servers

� Integrating DevPartner Java Edition with IDEs

� Installing the DevPartner Java Edition License

� Installing the Java Runtime Environment

� Uninstalling DevPartner Java Edition on Windows

Installing DevPartner Java Edition on Windows

Preparing to Install

If you have a previous release of DevPartner Java Edition, uninstall the previous release and restart your machine before beginning installation. For more information, see “Uninstalling DevPartner Java Edition on Windows” on page 16.

Configurations and session files created in a previous release cannot be used with this release. After you uninstall, delete the folders and files remaining inside the \DevPartner Java Edition directory.

You will need to restart the computer after installing DevPartner Java Edition.

11

Performing the Installation

Use the following procedure to install DevPartner Java Edition on Windows:

1 Insert the DevPartner Java Edition CD to start the installation wizard. The Setup screen appears automatically. From this screen, you can perform the following optional tasks in addition to installing DevPartner Java Edition Java Edition:

� Display or print the DevPartner Java Edition Installation Guide.

� Install the Java 2 runtime environment. You must have Java 2 runtime environment V1.31_02 or higher on your system. For details, see “Installing the Java Runtime Environment” on page 15.

Note: The installation file for the Windows edition of DevPartner Java Edition is named DPJW.exe.

2 On the Setup screen, click Install Compuware DevPartner. The Welcome screen appears.

3 Click Next. The License Agreement appears.

4 Read and accept the License Agreement, then click Next. The Customer Information screen appears.

5 Enter your name and company information and click Next. The Destination Folder screen appears.

The default path for installing DevPartner Java Edition is displayed in the Destination Folder screen. If you want to install the product in a different location, click Change and browse to the desired location.

6 Click Next. The Post-Install Setup screen appears. This screen provides three options for configuring DevPartner Java Edition as part of the installation process. If you do not need any of the options, or if you prefer to perform the tasks after installation is complete, clear the selections as desired.

7 Click Next. The Ready to Install the Program screen appears.

8 Review your installation settings; use Back to return to a previous screen and change a setting if necessary. When you have confirmed that your selections are correct, click Install. A progress meter on the Installing Compuware DevPartner Java Edition screen shows the progress of the installation.

Note: During the installation, certain portions of the process continue without advancing the progress bar on the installation wizard. If you think the install is not responding, check the Windows Task Manager before stopping the installation.


9 When installation is completed, the InstallShield Wizard Completed screen appears. Click Finish.

If you selected Integrate DevPartner Java Edition with your IDE option, you must integrate at least one IDE with DevPartner Java Edition.

1 When the DevPartner Java Edition IDE Addin Installation screen appears, select an IDE from the list, then click Continue.

2 In the next screen, enter the path of the IDE installation (root directory) in the field; or browse to find the directory. Click Install.

3 Select another IDE and repeat step 1–2; or click Exit.

For more details, see “Integrating DevPartner Java Edition with IDEs” on page 14.

If you selected the Set up application servers for analysis option, set up one or more application servers to be analyzed by DevPartner Java Edition (see the instructions for your application server in Chapter 7, “Configuring Application Servers”). If you cleared this option, the installation process skips this step. You can configure an application server at any time after installation is completed.

To skip setting up application servers and continue the installation process, click Cancel.

If you are prompted to make the changes effective, click Yes.

Compuware DevPartner Java Edition opens in your default browser when your system restarts.

Configuring Application ServersAfter completing installation, you can configure application servers for use with DevPartner Java Edition. You must perform this task in order to use the features in the Application Server Testing tab of the Start page. For instructions, see Chapter 7, “Configuring Application Servers”.

Chapter 2� Installing DevPartner Java Edition on Windows 13

Integrating DevPartner Java Edition with IDEsAfter installing DevPartner Java Edition, you can integrate it with an IDE so you can use DevPartner Java Edition features from within the IDE interface. Use the Java IDE Add-in Manager for this task.

1 Select Start>Programs>Compuware DevPartner Java Edition>Utilities>Java IDE Add-in Manager. The IDE Addin Installation screen appears.

2 From the list, select the appropriate IDE. Table 2-1 lists the supported IDEs.

3 Click Continue.

4 Enter the path of the IDE installation (root directory) in the field, or click the browse button to find the directory.

5 Click Install.

6 If you have no other IDEs to configure, click Exit to close the utility. Otherwise, repeat step 2–5 as needed.

Table 2-1. Entries for IDEs in the IDE Add-in Installation Screen

IDE Entry in IDE Installation List

Borland JBuilder X or 2005 Borland JBuilder

Compuware OptimalJ 3.3.01 and 4.0 Compuware OptimalJ

Eclipse 2.1.3

Eclipse 3.0

Eclipse 2.1.3

Eclipse 3.0

IBM Rational Application Developer 6.0

IBM RAD v6.0

IBM WebSphere Application Developer v5.1 Basic Edition

IBM WSAD v5.1

IBM WebSphere Application Server 5.0 and 5.1 - Express

IBM WAS Express

Oracle JDeveloper v9.0.4 Oracle9i JDeveloper v9.0.4

Oracle JDeveloper v9.0.5 Oracle10G JDeveloper v9.0.5


Installing the DevPartner Java Edition LicenseWhen you install DevPartner Java Edition, an evaluation license is automatically installed. This license is only valid for 14 days.

To install a single-seat, concurrent, or server license, refer to the Distributed License Management License Installation Guide: Chapter 3, “License Installation and Configuration for Windows”. This document is installed as LicInst4.pdf in C:\Program Files\Common Files\Compuware; it is also available on the installation CD as CPWR_License_Install.pdf.

After upgrading to a server license, you must stop and restart the NCSP process:

1 In the Windows Control Panel, double-click Administrative Tools.

2 In the Administrative Tools window, double-click Services.

3 In the Services window, right-click Compuware DevPartner Java Edition Control Service and select Stop.

4 Right-click Compuware DevPartner Java Edition Control Service again and select Start.

Installing the Java Runtime EnvironmentDevPartner Java Edition requires Java runtime environment V1.3.1_02 or higher to be installed on your machine. To install the Java 2 runtime environment from the DevPartner Java Edition CD:

1 Insert the DevPartner Java Edition CD to start the installation wizard. The Setup screen appears automatically.

2 Click Java 2 Runtime Environment. An Extracting Files screen appears while files are extracted from the setup file.

3 On the Welcome to the InstallShield Wizard for Java 2 Runtime Environment, SE v1.4.0 screen, click Next.

4 Read and accept the License Agreement. Click Next.

5 Accept the default on the Choose Destination Location screen, or browse for a directory into which to install the Java 2 Runtime Environment; then click Next.

6 Select the browser that will have the Java 2 runtime environment as its default runtime. Click Next.

Chapter 2� Installing DevPartner Java Edition on Windows 15

7 The Setup Status screen displays the progress of the installation. The installation procedure displays a confirmation message when the installation successfully completes.

Uninstalling DevPartner Java Edition on WindowsTo remove DevPartner Java Edition from your machine:

1 From the Windows Control Panel, open Add/Remove Programs.

2 Select Compuware DevPartner Java Edition.

3 Click Remove. When you are prompted to confirm, click Yes.

4 Restart your computer if prompted.

When you uninstall DevPartner Java Edition, session files and configuration information stored in the \var subdirectory of the product directory are not deleted. If you are reinstalling the same release of DevPartner Java Edition, your configurations and session files will be available in the new installation. If you do not need these files, you can delete this folder.

Note: Configurations and session files from a previous release cannot be used with this release.


Chapter 3

Installing DevPartner Java Edition on Solaris

� Installing DevPartner Java Edition on Solaris



� Installing the Java Runtime Environment

� Uninstalling DevPartner Java Edition on Solaris

Installing DevPartner Java Edition on Solaris


To install DevPartner Java Edition and to configure an application server using the dpjadmin utility, you must first install a GUI that is based on the X Window System and is compatible with Java Swing.

If you have a previous release of DevPartner Java Edition, uninstall the previous release before beginning installation. For more information, see “Uninstalling DevPartner Java Edition on Solaris” on page 20.

Configurations and session files created in a previous release cannot be used with this release. After you uninstall the previous release, delete the folders and files remaining inside the /DPJ directory.


Use the following procedure to install DevPartner Java Edition on Solaris:

1 Mount the DevPartner Java Edition CD and change to the subdirectory dir/Setup, where dir is the directory where the CD is mounted.

2 From the command line, run DPJS.BIN.

17

3 On the Introduction screen, click Next.


5 On the Picking a Browser screen, select YES to specify a browser during installation or NO to skip specifying a browser. If you specify a browser, you can use the DevPartner Java Edition user interface locally. Click Next.

6 If you selected YES in the previous step, enter the path or browse to find the path to your browser on the Choose Your Browser screen. Click Next.

If you selected NO in the previous step, this screen does not appear.

Caution: If you do not specify a browser through the installation wizard, you can create the nmDefaultBrowser script to launch a supported browser when you start DevPartner Java Edition. The script must contain arguments as in the following example (which specifies Netscape as the browser):#!/bin/sh exec /usr/local/netscape/netscape $*

7 On the Ready to Install screen, verify the installation settings and click Install. A progress meter shows the progress of the installation.

8 On the Install Completed Successfully screen, click Done. DevPartner Java Edition has been installed in /opt/Compuware/DPJ. The DevPartner Java Edition user interface appears.




To install a single-seat, concurrent, or server license, refer to Chapter 4, “License Installation and Configuration for UNIX”, of the Distributed License Management License Installation Guide. This document, CPWR_License_Install.pdf, is available on the DevPartner Java Edition installation CD.

Installing the Java Runtime EnvironmentDevPartner Java Edition requires that Java runtime environment V1.3.1_02 or higher be installed on your machine. If you do not have it, you must install it. You can install the Java 2 runtime environment from the DevPartner Java Edition CD.

Use the following procedure to install the Java 2 runtime environment on your machine:

1 Mount the DevPartner Java Edition CD and change to the subdirectory dir/JRE, where dir is the directory where the CD is mounted.

2 Copy j2re-1_4_1_03-solaris-sparc.sh to your local system.

Caution: Do not run the executable from the CD. If you try to run the executable from the CD, errors occur and a message informs you that the file could not be extracted or installed.

3 To install the Java 2 runtime environment, run the following from the command line:

j2re-1_4_1_03-solaris-sparc.sh




7 The Setup Status screen displays the progress of the installation. When the installation successfully completes, the installation procedure displays a confirmation message.

Chapter 3� Installing DevPartner Java Edition on Solaris 19

Uninstalling DevPartner Java Edition on SolarisUse the following procedure to remove DevPartner Java Edition from your machine:

1 Set your directory to /opt/Compuware/DPJ/bin.

2 At the command line, enter

./UninstallDPJ

3 When you are prompted to confirm, enter YES.

4 The system displays the message “Uninstallation Complete” when DevPartner Java Edition has been removed from your machine.

When you uninstall DevPartner Java Edition, session files and configuration information stored in the var/opt/Compuware/DPJ subdirectory of the product directory are not deleted. If you are reinstalling the same release of DevPartner Java Edition, your configurations and session files will be available in the new installation. If you do not need these files, you can delete this folder.



Chapter 4

Installing DevPartner Java Edition on Linux

� Installing DevPartner Java Edition on Linux



� Installing the Java 2 Runtime Environment

� Uninstalling DevPartner Java Edition on Linux

Installing DevPartner Java Edition on Linux



If you have a previous release of DevPartner Java Edition, uninstall the previous release before beginning installation. For more information, see “Uninstalling DevPartner Java Edition on Linux” on page 24.



Use the following procedure to install DevPartner Java Edition on Linux:


2 From the command line, run DPJL.BIN.

21



5 On the Picking a Browser screen, select YES to specify a browser during installation or NO to skip specifying a browser. If you specify a browser, you can use the DevPartner Java Edition user interface locally. Click Next.

6 If you selected YES in the previous step, enter the path or browse to find the path to your browser on the Choose Your Browser screen. Click Next.

If you selected NO in the previous step, this screen does not appear.

Caution: If you do not specify a browser through the installation wizard, you can create the nmDefaultBrowser script to launch a supported browser when you start DevPartner Java Edition. The script must contain arguments as in the following example (which specifies Netscape as the browser):#!/bin/sh exec /usr/local/netscape/netscape $*






To install a single-seat, concurrent, or server license, refer to Chapter 4, “License Installation and Configuration for UNIX”, of the Distributed License Management License Installation Guide. This document, CPWR_License_Install.pdf, is available on the DevPartner Java Edition installation CD.

Installing the Java 2 Runtime EnvironmentDevPartner Java Edition requires that Java runtime environment V1.3.1_02 or higher be installed on your machine. If you do not have it, you must install it. You can install the Java 2 runtime environment from the DevPartner Java Edition CD.

Use the following procedure to install the Java 2 runtime environment on your machine:

1 Mount the DevPartner Java Edition CD and change to the subdirectory dir/JRE, where dir is the directory where the CD is mounted.

2 Copy j2re-1_4_1_03-linux-i586.bin to your local system.

Caution: Do not run the executable from the CD. If you try to run the executable from the CD, errors occur and a message informs you that the file could not be extracted or installed.

3 To install the Java 2 runtime environment, run the following from the command line:

j2re-1_4_1_03-linux-i586.bin




7 The Setup Status screen displays the progress of the installation. When the installation successfully completes, the installation procedure displays a confirmation message.

Chapter 4� Installing DevPartner Java Edition on Linux 23

Uninstalling DevPartner Java Edition on LinuxUse the following procedure to remove DevPartner Java Edition from your machine:



./UninstallDPJ



When you uninstall DevPartner Java Edition, session files and configuration information stored in the var/opt/Compuware/DPJ subdirectory of the product directory are not deleted. If you are reinstalling the same release of DevPartner Java Edition, your configurations and session files will be available in the new installation. If you do not need these files, you can delete this folder after restarting your computer.



Chapter 5

Installing DevPartner Java Edition on AIX

� Installing DevPartner Java Edition on AIX



� Uninstalling DevPartner Java Edition on AIX

Installing DevPartner Java Edition on AIX



If you have a previous release of DevPartner Java Edition, uninstall the previous release before beginning installation. For details, see “Uninstalling DevPartner Java Edition on AIX” on page 26.



Use the following procedure to install DevPartner Java Edition on an AIX server:


2 From the command line, run DPJA.BIN.

25





Note: After DevPartner Java Edition has been installed, run the DevPartner Java Edition browser (DPJserver:21578/ui) on one of the other supported platforms. You cannot run the browser on AIX.



To install a concurrent or server license, refer to Chapter 4, “License Installation and Configuration for UNIX”, of the Distributed License Management License Installation Guide. This document, CPWR_License_Install.pdf, is available on the DevPartner Java Edition installation CD.

Note: Single-seat licenses are not supported on AIX.

Uninstalling DevPartner Java Edition on AIXUse the following procedure to remove DevPartner Java Edition from your machine:



./UninstallDPJ






Chapter 5� Installing DevPartner Java Edition on AIX 27

Chapter 6

Installing DevPartner Java Edition on HP-UX

� Installing DevPartner Java Edition on HP-UX



� Uninstalling DevPartner Java Edition on HP-UX

Installing DevPartner Java Edition on HP-UX



If you have a previous release of DevPartner Java Edition, uninstall the previous release before beginning installation. For details, see “Uninstalling DevPartner Java Edition on HP-UX” on page 31.



Use the following procedure to install DevPartner Java Edition on an HP-UX server:


2 From the command line, run DPJH.BIN.

29





Note: After DevPartner Java Edition has been installed, run the DevPartner Java Edition browser on one of the other supported platforms. You cannot run the browser on HP-UX.



To install a concurrent or server license, refer to Chapter 4, “License Installation and Configuration for UNIX”, of the Distributed License Management License Installation Guide. This document, CPWR_License_Install.pdf, is available on the DevPartner Java Edition installation CD.

Note: Single-seat licenses are not supported on HP-UX. Running the Compuware License Manager on HP-UX is also not supported. To use a concurrent license for HP-UX, you must install and run the Compuware License Manager on one of the other supported platforms for DevPartner Java Edition.


Uninstalling DevPartner Java Edition on HP-UXUse the following procedure to remove DevPartner Java Edition from your machine:



./UninstallDPJ





Chapter 6� Installing DevPartner Java Edition on HP-UX 31

Chapter 7

Configuring Application Servers

� DevPartner Java Edition Administration Console

� Creating a Server Configuration

DevPartner Java Edition Administration ConsoleTo profile applications running through an application server, you must have a DevPartner Java Edition configuration for the server.

To determine whether your application server is supported, see Table 1-2 in Chapter 1, “System Requirements”. If your application server is not listed, you can configure it as a generic application server. Note, however, that support is not guaranteed for a server that is not included in the list.

Use the DevPartner Java Edition Administration Console to create server configurations. You can also use this utility to modify configurations (although you cannot change the name of an existing configuration) and delete them.

When you open the Administration Console, it automatically detects the application server(s) installed on the same machine as DevPartner Java Edition and creates the configuration(s). (If more than one instance of an application server is installed, a configuration is created only for the most recent instance.) To save these default configurations, click OK.

To create additional configurations, use the procedures described in the next topic.

33

Creating a Server ConfigurationTo create a server configuration:

1 Open the Administration Console.

� UNIX or Windows — Open a console and enter dpjadmin at a command prompt.

� Windows — Click Start>Programs>Compuware DevPartner Java Edition>Utilities>Administration.

2 From the list in the Administration Console window, select your application server. If your application server is not listed, select <Generic App Server> or <Generic App Server as Windows Service>, as appropriate.

Note: The list of available application servers varies by platform.

3 Click New Configuration. The New Configuration dialog box appears.

4 The default name for the application server appears in the Configuration Name field. Change the name as needed to uniquely identify the configuration.

5 Provide the specific configuration settings for your application server, as described below:

� “Apache Tomcat” on page 35� “Apache Tomcat as a Windows Service” on page 35� “BEA WebLogic 8.1.x and 9.0” on page 36� “BEA WebLogic 8.1.x and 9.0 as a Windows Service” on page 37� “IBM WebSphere 5.1” on page 37� “IBM WebSphere 6.0” on page 38� “IBM WebSphere as a Windows Service” on page 38� “JBoss” on page 39� “JBoss as a Windows Service” on page 39� “Oracle Application Server (OC4J Integrated)” on page 40� “Oracle OC4J Standalone” on page 40� “Sun ONE 7.0 as a Windows Service” on page 41� “Sun Java System Application Server Platform Edition 8.0” on

page 41� “Generic Application Server” on page 41� “Generic Application Server as a Windows Service” on page 43


Apache Tomcat

Required: You can only profile programs running on Tomcat if it is configured with a Java Virtual Machine that is compatible with DevPartner Java Edition. This includes the Sun JDK 1.3 or above (this release of DevPartner Java Edition supports JDK 5.0). If you are running an earlier version of Java, check the Release Notes (ReadMeDPJ.htm) for compatibility information.

For Tomcat 5.5, you must have JDK 5.0.

1 In the Install Location field, type the path of the Tomcat server installation (root directory); or browse to locate the directory.

2 In the Java Home field, type the path of the Java installation directory; or browse to locate the directory.

3 Click OK to save the information and close the New Configuration dialog box.

The configuration name is added to the Application Servers Configuration list. When you select the name, the definition is displayed in the Configuration Properties pane.

Apache Tomcat as a Windows Service

Required: You can only profile programs running on Tomcat if it is configured with a Java Virtual Machine that is compatible with DevPartner Java Edition. This includes the Sun JDK 1.3 or above (this release of DevPartner Java Edition supports JDK 5.0). If you are running an earlier version of Java, check the Release Notes (ReadMeDPJ.htm) for compatibility information.

For Tomcat 5.5, you must have JDK 5.0.

1 In the Service Name field, enter the name of the Tomcat Windows service. You must use the name that identifies the Tomcat server in the Windows Services Control Panel.



Chapter 7� Configuring Application Servers 35

BEA WebLogic 8.1.x and 9.0

Required: The start script for BEA WebLogic must include the password for the server. In WebLogic 8, if the password is not in the script, a message prompts you to add the user and password to the WebLogic startup script. DevPartner Java Edition will not start without this information.

To add a user and password to the script, add lines similar to the following to your start script:

set WLS_USER=usernameset WLS_PASSWORD=password

Replace username and password with an actual username and valid password.

1 If WebLogic is installed in the default installation directory, DevPartner Java Edition automatically enters the directory path in the Bea Home field. If the field is blank or if you need to change the location, click the browse button to locate the directory.

2 If DevPartner Java Edition detects a valid start script, it automatically enters the path in the Start Script field. If the field is blank or you want to select a different script, click the browse button to locate the start script.

3 By default, DevPartner Java Edition enters the path to the start script in the Domain Path field. If the field is blank or you want to specify a different path to a WebLogic domain, click the browse button to locate the domain.



Note: WebLogic 9.0 uses the JVM JRockit 5.0 by default. Because of an issue with this version of JRockit, Memory analysis cannot be performed on Java applications running under it. To perform Memory analysis, point the JVM to Sun in the WebLogic script (default location BEA_domain\bin\SetDomainEnv.cmd).


BEA WebLogic 8.1.x and 9.0 as a Windows Service

1 In the Service Name field, enter a name for the WebLogic service. You must use the name that identifies the WebLogic server in the Windows Services Control Panel.



Note: WebLogic 9.0 uses the JVM JRockit 5.0 by default. Because of an issue with this version of JRockit, Memory analysis cannot be performed on Java applications running under it. To perform Memory analysis, point the JVM to Sun in the WebLogic script (default location BEA_domain\bin\SetDomainEnv.cmd).

IBM WebSphere 5.1

1 If WebSphere is installed in the default installation directory, DevPartner Java Edition automatically enters the path in the Install Location field. If the field is blank or you need to specify a different location, click the browse button to locate the directory.

2 DevPartner Java Edition automatically enters the default name of the WebSphere server (server1) in the Server field. If you need to specify a different name, select it from the list.




IBM WebSphere 6.0

1 If WebSphere is installed in the default installation directory, DevPartner Java Edition automatically enters the path in the Profile Location field. If the field is blank or you need to specify a different location, click the browse button to locate the directory. The usual default locations are:

� Windows\Program Files\IBM\WebSphere\AppServer\profiles\default

� AIX/usr/IBM/WebSphere/AppServer/profiles/default

� UNIX platforms other than AIX/opt/IBM/WebSphere/AppServer/profiles/default

2 DevPartner Java Edition automatically enters the default name of the WebSphere server (server1) in the Server field. If you need to specify a different name, select it from the list.

Note: If the server has been already configured to run as a Window service, the following message appears:

“The Windows service exists for this WebSphere Application Server V6.”

Click Cancel and configure this server as a Windows service.



IBM WebSphere as a Windows Service

1 In the Service Name field, enter a name for the WebSphere application server. You must use the name that identifies the Tomcat server in the Windows Services Control Panel.




JBossNote: In JBoss 4.0, the installed file jar_versions.xml may contain the

informational string France Telecomm R&D within the <contributor> tag. To ensure that the Administration Console does not encounter problems parsing the jar_versions.xml file, replace the & character with the code for this character (&): France Telecomm R&D.

1 If JBoss is installed in the default installation directory, DevPartner Java Edition automatically fills in the Install Location field with the directory path. If the field is blank or if you need to specify a different location, click the browse button to locate the directory and enter the information in the field.

2 For the Java Home field, click the browse button to navigate to and select the directory for your Java installation.

3 Click OK to save the server information and close the New Configuration dialog box.


JBoss as a Windows ServiceNote: In JBoss 4.0, the installed file jar_versions.xml may contain the

informational string France Telecomm R&D within the <contributor> tag. To ensure that the Administration Console does not encounter problems parsing the jar_versions.xml file, replace the & character with the code for this character (&): France Telecomm R&D.

1 If the Service Name field does not already contain the correct service name for JBoss, select the service name from the list or type the name in the field. Use the name that identifies the JBoss application server in the Windows Services Control Panel.




Oracle Application Server (OC4J Integrated)

Required: Make sure you have permission to read the Oracle Home Directory. If you do not have permission to read, the Administration Console cannot configure DevPartner Java Edition with this application server.

1 In the Install Location field, type the path of the OC4J Integrated server installation (root directory); or click the browse button to locate the directory.

2 In the Container Name field, enter the name of the OC4J / J2EE Container; or select the name from the list.



Oracle OC4J Standalone

1 In the Install Location field, enter the path of the OC4J Standalone server installation (root directory); or click the browse button to locate the directory.

2 In the Java Home field, enter the path of the Java installation directory; or click the browse button to locate the directory.




Sun ONE 7.0 as a Windows Service

1 If DevPartner Java Edition detects the default service name, it is automatically entered in the Service Name field. If the field is blank or if you need to specify a different name, select the name from the list. Use the name that identifies the Sun ONE application server in the Windows Services Control Panel.



Sun Java System Application Server Platform Edition 8.0

1 By default, the path of \domain1 is entered in the Domain Directory field. To specify a different domain directory, click the browse button to navigate to the directory and enter the path in the field.



Generic Application Server

Before you configure a generic application server, note the following:

� If an application server is installed as a Windows service, do not use this procedure; configure it as a Windows service (see page 43).

� If the start or stop script for an application server includes a pause for user input, you must edit the script to remove the need for user input.

� You do not need to provide the entire command line, only enough to uniquely identify the process (that is, to distinguish this process from any other process executing on the machine). The command line tokens are case-sensitive and can be listed in any order.


To create a generic configuration for an application server:

1 In the Start Command field, type the command that starts the application server; or click the browse button to navigate to and select the command file (for example, a .bat file). Include the necessary argument(s).

2 In the Stop Command field, type the command that stops the application server; or click the browse button to navigate to and select the command file.

3 In the Install Location field, type the top level of the application server directory; or click the browse button to navigate to and select the directory.

4 The Java Home field should display the directory for your Java installation, as detected in the registry; if you have more than one Java Home, the field lists the first directory detected. If you want to use a different Java Home than what is listed, click the browse button to navigate to and select the desired directory.

Caution: Some application servers specify the Java Home directory in their startup scripts or configuration files. That setting may override this configuration.

5 In the Process Executable field, type the name of the executable of the process you want to profile. For example:

� Windows — c:\<path>\java.exe com.classname -param1

Type java.exe in the field.

� UNIX — <path>/java com.classname -param1

Type java in the field.

6 In the text area, type as many command line tokens as necessary to uniquely identify the application server process you want to profile. For example, for the command line in step 5, the tokens com.classname and -param1 may uniquely identify the java process.

Note: If necessary, you can use Process Explorer (from Sysinternals, http://www.sysinternals.com) or a similar utility to determine the command line.

7 Default timeout values are entered for stopping and starting the application server. Some application servers require more time to complete the startup process, so change these values if necessary.


8 The shutdown procedures of some application servers prevent DevPartner Java Edition from capturing a final snapshot of the profiling session. If necessary, therefore, select the option to detach the session before the server stops, so the active profiling session will terminate before the application server’s stop script executes.

Note: If you detach the session before terminating the server, the profiling session will not include data from the server shutdown.

9 If the application server has a bootstrap process that terminates before the main processes are up and running, select the Does bootstrap process terminate? option.

10 Click OK to save the server definition and close the dialog box.


Generic Application Server as a Windows Service

To use this procedure for an application server, the server must be installed as a Windows service. If it is not a Windows service, use the preceding procedure (“Generic Application Server” on page 41) to configure it for DevPartner Java Edition.

Limitation: You cannot profile a service that starts more than one Java process.

To define the application server as a Windows Service:

1 In the Configuration Name field, type a name to identify the application server.

2 The Service Name list includes the names of all detected Windows services. Select the appropriate name.

3 Click OK to save the server definition and close the dialog box.



Index

AAdministration Console 33AIX

application servers supported 4, 33DevPartner Java Edition license 26hardware requirements 2JVMs supported 3uninstalling DevPartner Java Edition 26versions supported 2

Apache Tomcatconfiguring 35configuring as a Windows service 35

application serversAdministration Console 33configuring

Apache Tomcat 35Apache Tomcat as a Windows service 35BEA WebLogic 36BEA WebLogic as a Windows service 37generic server 41generic server as a Windows service 43IBM WebSphere 37IBM WebSphere as a Windows service 38JBoss 39JBoss as a Windows service 39Oracle Application Server 40Oracle OC4J Standalone 40Sun ONE 7.0 as a Windows service 41

supported 4, 33

BBEA WebLogic

configuring 36configuring as a Windows service 37

Cconfiguring application servers

Apache Tomcat 35Apache Tomcat as a Windows service 35BEA WebLogic 36BEA WebLogic as a Windows service 37generic server 41generic server as a Windows service 43IBM WebSphere 37IBM WebSphere as a Windows service 38JBoss 39JBoss as a Windows service 39opening the Administration Console 33Oracle Application Server 40Oracle OC4J Standalone 40Sun ONE 7.0 as a Windows service 41

contacting Technical Support viii

45

Hhardware requirements 1HP-UX

application servers supported 4, 33DevPartner Java Edition license 30hardware requirements 2JVMs supported 3uninstalling DevPartner Java Edition 31versions supported 2

IIBM WebSphere

configuring 37configuring as a Windows Service 38

IDEintegrating DevPartner Java Edition 14supported 6

installing Java Runtime EnvironmentLinux 23Solaris 19Windows 15

installing the DevPartner Java Edition licenseAIX 26HP-UX 30Linux 22Solaris 18Windows 15

Integrated Development Environment – See IDE

JJava Runtime Environment

Linux 23Solaris 19Windows 15

JBossconfiguring 39configuring as a Windows service 39versions supported 5

JREs supported 7JRockit version supported 4JVMs supported 3

Llanguages supported 8licensing 8

AIX 26HP-UX 30Linux 22Solaris 18Windows 15

Linuxapplication servers supported 4, 33DevPartner Java Edition license 22hardware requirements 1Java Runtime Environment 23JVMs supported 3uninstalling DevPartner Java Edition 24versions supported 2

Ooperating systems supported 2Oracle Application Server

configuring 40Oracle OC4J Standalone

configuring 40

Rremoving session files


requirementsapplication servers 4hardware 1IDE 6JVM 3operating systems 2Web browsers 7


SSolaris

application servers supported 4, 33DevPartner Java Edition license 18hardware requirements 1Java Runtime Environment 19JVMs supported 3uninstalling DevPartner Java Edition 20versions supported 2

Sun application serversversions supported 5

Sun Java System Application Server Platform Edition 8.0 41

Sun ONE 7.0configuring as a Windows service 41

system configuration 1

TTechnical Support viii

Uuninstalling


user interface supported environments 7

WWeb browsers supported 7Windows

application servers supported 4, 33DevPartner Java Edition license 15hardware requirements 1integrating IDEs 14Java Runtime Environment 15JVMs supported 3uninstalling DevPartner Java Edition 16versions supported 2

Index 47

Installing DevPartner Java Edition - Micro Focus · iv Installing DevPartner Java Edition Chapter 3...

Documents

Transcript of Installing DevPartner Java Edition - Micro Focus · iv Installing DevPartner Java Edition Chapter 3...