Installing DevPartner Java Edition · viii Installing DevPartner Java Edition Conventions Used In...

InstallingDevPartner

Java EditionRelease 3.3

Please direct questions about DevPartner Java Edition or comments on this document to:

Customer SupportCompuware Corporation

One Campus MartiusDetroit, MI 48226

1-888-686-3427

For telephone support numbers outside the USA, Canada, and Latin America, see Compuware's FrontLine Web site: http://frontline.compuware.com/.

© 2001, 2004 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.

Process Explorer © 1996-2001 by Sysinternals LLC.

Acrobat® Reader copyright © 1987–2004 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.

December 6, 2004

CWM6IX3D

Table of Contents

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

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

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

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

Supported Operating Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2

Supported Java Virtual Machines . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3

Supported Application Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Supported Integrated Development Environments . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Supported Browsers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Supported Languages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

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

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

Integrating DevPartner Java Edition with IDEs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

Installing the DevPartner Java Edition License . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

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 DevPartner Java Edition License . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Single-Seat License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Server License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19Concurrent License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

Installing the Java Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Uninstalling DevPartner Java Edition on Solaris . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

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


Installing the DevPartner Java Edition License . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Single-Seat License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Server License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25Concurrent License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Installing the Java 2 Runtime Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Uninstalling DevPartner Java Edition on Linux . . . . . . . . . . . . . . . . . . . . . . . . . . . 28

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


Installing the DevPartner Java Edition License . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Server License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Concurrent License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

Uninstalling DevPartner Java Edition on AIX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32

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


Installing the DevPartner Java Edition License . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

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

iv Installing DevPartner Java Edition

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

Creating a Server Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40Apache Tomcat . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Apache Tomcat as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41BEA WebLogic 7 or 8.1.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42BEA WebLogic 8.1.x as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43IBM WebSphere 5.x . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43IBM WebSphere 5.x as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43JBoss . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44JBoss as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Oracle Application Server (OC4J Integrated) . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Oracle OC4J Standalone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45Sun ONE 7 as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Sun Java System Application Server Platform Edition 8 . . . . . . . . . . . . . . . . . . 46Generic Application Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Generic Application Server as a Windows Service . . . . . . . . . . . . . . . . . . . . . . . 48

Index. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

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 at http://frontline.compuware.com/nashua/.

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 Operating Systems� Supported Java Virtual Machines� Supported Application Servers� Supported Integrated Development Environments� Supported Browsers� Supported Languages� Licensing

Hardware RequirementsWindows DevPartner Java Edition requires the following minimum configuration

for Windows systems:

� Intel Architecture 32-bit

� Pentium III 500 MHz or equivalent

� 256 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




1

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

� Intel Architecture 32-bit

� Pentium III 500 MHz or equivalent




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

� AIX 5.1 and 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 Operating SystemsDevPartner 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 8 and 9

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

� Red Hat Linux 9.0 (Personal and Professional Editions)

2 Installing DevPartner Java Edition

� AIX 5.1 and 5.2

If you are running AIX 5.1, you must install X11.base.rte version 5.1.0.36 or later before installing DevPartner Java Edition.

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.1 and 5.2), the SDK should be version 1.3.1.6 or higher.

� HP-UX Release 11i

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.

Supported Java Virtual MachinesDevPartner 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 and 1.4 (32-bit) HP-UX 11i

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

• Windows 2000, Windows XP, and Windows 2003 Server

• AIX 5.1 and 5.2

• Red Hat Linux 9.0

• Red Hat Enterprise Linux 3.0

IBM 1.4 (32-bit) • Windows 2000 and Windows 2003 Server

• Solaris 8 and 9

• AIX 5.1 and 5.2


• HP-UX 11i

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

• Solaris 8 and 9


Chapter 1� System Requirements 3

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

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

• Solaris 8 and 9



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

• Solaris 8 and 9



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


Supported Application ServersDevPartner Java Edition can profile applications running on the following application servers.

Table 1-2. Supported Application Servers

These Application Servers Run on These Operating Systems

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

• Solaris 8 and 9



• AIX 5.1 and 5.2

• HP-UX 11i

BEA WebLogic Server 7.0 • Windows 2000, Windows XP, and Windows 2003 Server

• Solaris 8 and 9

• HP-UX 11i

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

• Solaris 8 and 9


• AIX 5.2

• HP-UX 11i

IBM WebSphere 5.0 Standard and Enterprise Editions (see note below)


• Solaris 8 and 9

• AIX 5.1 and 5.2

IBM WebSphere 5.1 Standard and Enterprise Editions

• Windows 2000 and Windows 2003 Server

• Solaris 8 and 9


• AIX 5.1 and 5.2

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


Oracle OC4J Standalone v9.0.3 • Windows 2000 and Windows XP

• Solaris 8


Note: To run Memory analysis profiling for WebSphere 5.0 on Linux and Windows platforms, you must apply the WebSphere Application Server Version 5.0 Fix Pack 1 (Version 5.0.1), which is available for download. This Fix Pack contains a new IBM JVM that is required.

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

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

• Windows 2000 and Windows XP

• Solaris 8 and 9

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

• Solaris 8 and 9

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


• Solaris 8 and 9

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

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

• Windows 2000 and Windows XP

• Solaris 8 and 9

Sun Java System Application Server Platform Edition 8


• Solaris 8 and 9

Table 1-2. Supported Application Servers (Continued)

These Application Servers Run on These Operating Systems

Table 1-3. Supported Integrated Development Environments

These IDEs Run on These Application Servers

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

• Sun ONE 7

• Apache Tomcat 4.1

• BEA WebLogic 7.0 and 8.1.x

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


• BEA WebLogic 7.0 and 8.1.x


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

• JBoss 3.2

• Apache Tomcat 4.0.6

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

• JBoss 3.2


• BEA WebLogic 8.1.x

• IBM WebSphere v5.1 Advanced Single Server Edition (integrated)

Eclipse 2.1.3 • Apache Tomcat 4.1

Eclipse 3.0 • Apache Tomcat 4.1 and 5.0

• BEA WebLogic 8.1.x

• JBoss 3.2 and 4.0

IBM WebSphere Studio Application Developer 5.0

• Apache Tomcat 4.1 and 5.0


IBM WebSphere Studio Application Developer 5.1


• IBM WebSphere v5.0 and v5.1 Advanced Single Server Edition (integrated)

IBM WebSphere Application Server 5 - Express


• IBM WebSphere Application Server - Express Server 5.0

IBM WebSphere Application Server 5.1 - Express


• IBM WebSphere Application Server - Express Server 5.1

IBM WebSphere Studio Application Developer 5.0 Integration Edition



Oracle JDeveloper 9.0.4 • Oracle OC4J Standalone 9.0.4

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

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 Run on These Application Servers


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

� Internet Explorer Version 6 with or without SP1

� Netscape 7.0, 7.0.1, 7.0.2, and 7.1

� Mozilla 1.7

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 user interface is only supported on the following operating systems:

� Windows 2000, Windows XP, and Windows 2003 Server

� Solaris 8 and 9

� Red Hat Enterprise Linux 3.0 and Red Hat Linux 9.0

Note: On Windows, Solaris, and Linux, you must register one of the Java plug-ins (listed in “Supported Java Virtual Machines” on page 3) with the browser you are going to use for DevPartner Java Edition to work. See the documentation for your browser for specific instructions on registering a Java plug-in with that browser.

Supported LanguagesDevPartner 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.dat, is provided by Compuware License Management for each license that you purchase.

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.

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 number of users, up to the number of concurrent licenses purchased and installed, can launch DevPartner Java Edition, create or view session files, and create or use configuration files on a single local machine. Users cannot access the DevPartner Java Edition server machine remotely with a concurrent license.

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

Concurrent licensing requires Compuware License Manager. A license is consumed while each user is accessing the DevPartner Java Edition Web server and is released when the user exits the program.

Server Any user with access to the DevPartner Java Edition server machine (through a browser) can create or view session files, and can create or use configuration files on the DevPartner Java Edition server. This allows you to use a browser to access the DevPartner Java Edition server machine remotely if you have a server 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 have other products that use FlexLM licensing and you choose to store your Compuware license file in the same folder as those other license files, we recommend that you rename the Compuware license file to prevent conflicts or accidental merging or replacing of license files.

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 (LICINST.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 WindowsNote: You will need to restart the computer after installing DevPartner Java

Edition.

If you are running a previous version of DevPartner Java Edition, uninstall your previous version and restart your machine. For more information, see “Uninstalling DevPartner Java Edition on Windows” on page 16.

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.

11

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 13.


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”.

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.

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

IDE Entry in IDE Installation List

Borland JBuilder 9.0 or X Borland JBuilder

Compuware OptimalJ 3.2 and 3.3 Compuware OptimalJ

Eclipse 2.1.3

Eclipse 3.0

Eclipse 2.1.3

Eclipse 3.0

Chapter 2� Installing DevPartner Java Edition on Windows 13

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.

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

To install a single-user, concurrent, or server license on Windows, you must use the License Administration Utility (LAU), which is installed by default in C:\Program Files\Common Files\Compuware. Information on the LAU is provided in the Compuware Distributed License Management Installation Guide (LICINST.PDF), installed by default in C:\Program Files\Common Files\Compuware.

If you will be using concurrent licensing (that is, sharing the DevPartner Java Edition server), you must install a License Manager before using DevPartner Java Edition unless you are planning to use an existing License Manager.

Note: It is highly recommended that no previous versions of the License Manager exist on this machine.

IBM WebSphere Application Developer v5.0 Basic Edition

IBM WSAD v5.0

IBM WebSphere Application Developer v5.1 Basic Edition

IBM WSAD v5.1

IBM WebSphere Application Developer Integration Edition v5

IBM WSAD Integration Edition 5.0

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

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

IDE Entry in IDE Installation List


Refer to the Distributed License Management License Installation Guide for information on installing the License Manager.

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.

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

Chapter 2� Installing DevPartner Java Edition on Windows 15

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.3.

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 do not need these files, you can delete this folder after restarting your computer. If you are reinstalling DevPartner Java Edition, your configurations and session files will be available in the new installation.


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

Required: 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 are running a previous version of DevPartner Java Edition, uninstall your previous version before installing this version. For more information, see “Uninstalling DevPartner Java Edition on Solaris” on page 22.

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 comment line, run DPJS.BIN.

3 On the Introduction screen, click Next.


17

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.

7 On the License Setup screen, select the type of user license to use. A user license enables DevPartner Java Edition on your local machine.

� By default, DevPartner Java Edition installs a 14-day evaluation license. After 14 days, you must specify a valid Compuware user license file to continue using the product.

� To specify a user license, click User License and enter the path to the license file you are going to use, or browse to select the path; then click Next.

Note: If you selected the 14-day evaluation license, the installation procedure skips the next step.

8 On the Server License Setup screen, select the type of server license to use. A server license enables you to access DevPartner Java Edition from a remote machine.

� By default, DevPartner Java Edition installs a 14-day evaluation server license, even if you specified a user license in the previous step. After 14 days, you must specify a valid Compuware server license file to continue using the remote access capabilities of the product.

� To specify a server license, click DevPartner Java Edition Server License and enter the path to the server license file you are going to use, or browse to select the path; then click Next.

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

10 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.



Installing the DevPartner Java Edition LicenseWhen you install DevPartner Java Edition, a 14-day evaluation license is automatically installed. This license is only valid for 14 days. You can use the DPJ utility to transition to a single-seat license, a concurrent license, or a server license.

If you will be using concurrent licensing (that is, sharing the DevPartner Java Edition server), you must install a License Manager before using DevPartner Java Edition.

Single-Seat License

To install a single-seat license:

1 Install the single-seat license file you received from Compuware onto your hard disk, if it is not already installed.

2 Exit all DevPartner Java Edition browsers.

3 From a console, log in as root.

4 Enter the following command at the prompt, where licensefilename is the full path and name of the license file you installed:

dpj -setlicense licensefilename

Server License

To use a server license:

1 Install the server license file you received from Compuware on the machine to be used as the DevPartner Java Edition server, if it is not already installed.



Chapter 3� Installing DevPartner Java Edition on Solaris 19

4 Enter the following command at the prompt, where serverlicensefilename is the full path and name of the server license file you installed, port is the port number you have set for the License Manager (typically 7166), and host is the host name of the machine where the DevPartner Java Edition user license was installed:

dpj -setlicense serverlicensefilename:port@host

Concurrent License

Concurrent licensing requires use of a Compuware License Manager.

Install the Compuware License Manager unless you are planning to use an existing License Manager.


1 Change to the subdirectory

dir/LicMgr/SunOS

where dir is the directory where the CD is mounted.

2 To untar the file, run

tar xvf sl_lm33.tar

3 Create the directory /usr/local/cwlm for the License Manager (root access is required to create the directory).

4 Copy the files from where you untarred the tar file (/LicMgr/SunOS) to the /usr/local/cwlm directory.

5 Create the /usr/local/flexlm/licenses directory and copy the license file (sent to you by Compuware) to it. Rename the license file as License.dat or set the LM_License_File environment variable. If you need instructions on setting this environment variable, see the Distributed License Management License Installation Guide (LICINST.PDF) on the DevPartner Java Edition CD.

The License Manager must be running whenever a client requests a license checkout. You can configure the License Manager to start automatically each time the server boots, or to start manually.

1 To start the License Manager manually (required each time the server reboots), enter (as one line):

lmgrd -c /usr/local/flexlm/licenses/license.dat > license.log &


2 To prevent users from stopping the License Manager, enter the -p -2 option directly after the lmgrd string. If this option is selected, only Administrators with root privileges can stop the License Manager:

nohup path_to/lmgrd -p -2 -c /usr/local/flexlm/licenses/license.dat > license.log &

When a License Manager and concurrent license are installed, you can use the DPJ utility to complete license installation.

1 On the DevPartner Java Edition server, exit all DevPartner Java Edition browsers.


3 Enter the following command, where port is the port number you have set for the License Manager (typically 7166) and host is the host name of the machine where the License Server was installed:

dpj -setlicense port@host

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 have to 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 are thrown informing 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



Chapter 3� Installing DevPartner Java Edition on Solaris 21


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

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 do not need these files, you can delete this folder after restarting your computer. If you are reinstalling DevPartner Java Edition, your configurations and session files will be available in the new installation.


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 are running a previous version of DevPartner Java Edition, uninstall your previous version. For more information, see “Uninstalling DevPartner Java Edition on Linux” on page 28.

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


2 From the command line, run DPJL.BIN.



23

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.












Installing the DevPartner Java Edition LicenseWhen you install DevPartner Java Edition, a 14-day evaluation license is automatically installed. This license is only valid for 14 days. You can use the DPJ utility to transition to a single-seat license, a concurrent license, or a server license.

If you will be using concurrent licensing (that is, sharing the DevPartner Java Edition server), you must install a License Manager before using DevPartner Java Edition. For details, see “Concurrent License” on page 26.

Single-Seat License

To install a single-seat license:

1 Install the single-seat license file you received from Compuware onto your hard disk, if it is not already installed.



4 Enter the following command at the prompt, where licensefilename is the full path and name of the license file you installed:

dpj -setlicense licensefilename

Server License





Chapter 4� Installing DevPartner Java Edition on Linux 25

4 Enter the following command at the prompt, where serverlicensefilename is the full path and name of the server license file you installed, port is the port number you have set for the License Manager (typically 7166), and host is the host name of the machine where the DevPartner Java Edition user license was installed:

dpj -setlicense serverlicensefilename:port@host

Concurrent License

Concurrent licensing requires use of a Compuware License Manager. Install the Compuware License Manager unless you are planning to use an existing License Manager.



dir/LicMgr/SunOS



tar xvf lin_lm33.tar


4 Copy the files from where you untarred the tar file (/LicMgr/Linux) to the /usr/local/cwlm directory.













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 have to 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 are thrown informing 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



Chapter 4� Installing DevPartner Java Edition on Linux 27


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

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



./UninstallDPJ .





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 are running a previous version of DevPartner Java Edition, uninstall your previous version before installing this version. For details, see “Uninstalling DevPartner Java Edition on AIX” on page 32.

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


2 From the command line, run DPJA.BIN.




29









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.



Installing the DevPartner Java Edition LicenseWhen you install DevPartner Java Edition, a 14-day evaluation license is automatically installed. This license is only valid for 14 days. You can use the DPJ utility to transition to a concurrent license or a server license.

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

Server License

To install a server license:




4 Enter the following command at the prompt, where licensefilename is the full path and name of the server license file you installed, port is the port number you have set for the License Manager (typically 7166), and host is the host name of the machine where the DevPartner Java Edition user license was installed:

dpj -setlicense licensefilename:port@host

Concurrent License

Concurrent licensing requires use of a Compuware License Manager.

Install the Compuware License Manager unless you are planning to use an existing License Manager.



dir/LicMgr/AIX



tar xvf aix_lm33.tar


4 Copy the files from where you untarred the tar file (/LicMgr/AIX) to the /usr/local/cwlm directory.

Chapter 5� Installing DevPartner Java Edition on AIX 31












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 33

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 are running a previous version of DevPartner Java Edition, uninstall your previous version before installing this version. For details, see “Uninstalling DevPartner Java Edition on HP-UX” on page 37.

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


2 From the command line, run DPJH.BIN.



35










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 AIX.

Note: Once 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 DevPartner Java Edition browser on HP-UX.



Installing the DevPartner Java Edition LicenseWhen you install DevPartner Java Edition, a 14-day evaluation license is automatically installed. This license is only valid for 14 days. You can use the DPJ utility to transition to a server license.

Note: Single-seat licenses are not supported on HP-UX.

Running the Compuware License Manager on HP-UX is 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. For instructions, see the appropriate chapter for the selected platform.




3 Enter the following command at the prompt, where licensefilename is the full path and name of the server license file you installed, port is the port number you have set for the License Manager (typically 7166), and host is the host name of the machine where the DevPartner Java Edition user license was installed:

dpj -setlicense licensefilename:port@host

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 37

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.

39

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.

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 41� “Apache Tomcat as a Windows Service” on page 41� “BEA WebLogic 7 or 8.1.x” on page 42� “BEA WebLogic 8.1.x as a Windows Service” on page 43� “IBM WebSphere 5.x” on page 43� “IBM WebSphere 5.x as a Windows Service” on page 43� “JBoss” on page 44� “JBoss as a Windows Service” on page 44� “Oracle Application Server (OC4J Integrated)” on page 45� “Oracle OC4J Standalone” on page 45� “Sun ONE 7 as a Windows Service” on page 46� “Sun Java System Application Server Platform Edition 8” on page

46� “Generic Application Server” on page 46� “Generic Application Server as a Windows Service” on page 48


Apache Tomcat

Required: It is only possible to profile 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.

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.

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 41

BEA WebLogic 7 or 8.1.x

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.




BEA WebLogic 8.1.x 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.



IBM WebSphere 5.xNote: WebSphere is not supported on HP-UX.

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 5.x as a Windows Service

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




JBoss

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 Service

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 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

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 48).

� 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 46) 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 39AIX

application servers supported 5, 39DevPartner Java Edition license 31hardware requirements 2JVMs supported 3uninstalling DevPartner Java Edition 32versions supported 2

Apache Tomcatconfiguring 41configuring as a Windows service 41

application serversAdministration Console 39configuring

Apache Tomcat 41Apache Tomcat as a Windows service 41BEA WebLogic 42BEA WebLogic as a Windows service 43generic server 46generic server as a Windows service 48IBM WebSphere 43IBM WebSphere as a Windows service 43JBoss 44JBoss as a Windows service 44Oracle Application Server 45Oracle OC4J Standalone 45Sun ONE 7 as a Windows service 46

supported 5, 39

BBEA WebLogic

configuring 42configuring as a Windows service 43versions supported 5

Cconfiguring application servers

Apache Tomcat 41Apache Tomcat as a Windows service 41BEA WebLogic 42BEA WebLogic as a Windows service 43generic server 46generic server as a Windows service 48IBM WebSphere 43IBM WebSphere as a Windows service 43JBoss 44JBoss as a Windows service 44opening the Administration Console 39Oracle Application Server 45Oracle OC4J Standalone 45Sun ONE 7 as a Windows service 46

contacting Technical Support viii

Hhardware requirements 1

49

HP-UXapplication servers supported 5, 39DevPartner Java Edition license 37hardware requirements 2JVMs supported 3uninstalling DevPartner Java Edition 37versions supported 2

IIBM WebSphere

configuring 43configuring as a Windows Service 43versions supported 5

IDEintegrating DevPartner Java Edition 13supported 6

installing Java Runtime EnvironmentLinux 27Solaris 21Windows 15

installing the DevPartner Java Edition licenseAIX 31HP-UX 37Linux 25Solaris 19Windows 14

Integrated Development Environment – See IDE

JJava Runtime Environment

Linux 27Solaris 21Windows 15

JBossconfiguring 44configuring as a Windows service 44versions supported 5

JRockit version supported 4JVMs supported 3

Llanguages supported 8

licensing 9AIX 31HP-UX 37Linux 25Solaris 19Windows 14

Linuxapplication servers supported 5, 39DevPartner Java Edition license 25hardware requirements 2Java Runtime Environment 27JVMs supported 3uninstalling DevPartner Java Edition 28versions supported 2

Ooperating systems supported 2Oracle Application Server

configuring 45versions supported 5

Oracle OC4J Standaloneconfiguring 45versions supported 5

Rremoving session files

AIX 32HP-UX 37Linux 28Solaris 22Windows 16

requirementsapplication servers 5hardware 1IDE 6JVM 3operating systems 2Web browsers 8


SSolaris

application servers supported 5, 39DevPartner Java Edition license 19hardware requirements 1Java Runtime Environment 21JVMs supported 3uninstalling DevPartner Java Edition 22versions supported 2

Sun application serversversions supported 6

Sun Java System Application Server Platform Edition 8 46

Sun ONE 7configuring as a Windows service 46

system configuration 1

TTechnical Support viii

Uuninstalling

AIX 32HP-UX 37Linux 28Solaris 22Windows 16

WWeb browsers supported 8WebSphere

See IBM WebSphereWindows

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

Index 51

Installing DevPartner Java Edition · viii Installing DevPartner Java Edition Conventions Used In...

Documents

Transcript of Installing DevPartner Java Edition · viii Installing DevPartner Java Edition Conventions Used In...