Explorer chooses a Java Runtime Environment (JRE) to use. Instructions for explicitly specifying a JRE are also given. Introduction Teamprise Explorer is normally launched by running a native launcher executable (for example, TeampriseExplorer.exe on Windows). One of the things this

Explorer is normally launched by using the native launcher executable that ships with Teamprise Explorer. However, it is possible to bypass the launcher executable when running Teamprise Explorer. This allows certain kinds of errors to be captured more easily. You may be asked

Explorer Client Overview The Teamprise Explorer Client runs on a variety of operating systems, using Sun's Java virtual machine and libraries to provide much of this cross-platform advantage. Teamprise Explorer uses the Standard Widget Toolkit (SWT), a set of Java

Explorer uses the Motif windowing toolkit, Teamprise Explorer may appear to hang or not accept mouse and keyboard input when it loads. This problem is due to an incompatible window manager. The problem appears more often when using X server

Explorer by editing the startup configuration file. In Finder, navigate to the installation location for Teamprise Explorer. (For example: `/Applications`.) Right-click on Teamprise Explorer and select "Show Package Contents". A finder window displaying the contents of the application bundle

Explorer, Teamprise Plug-in for Eclipse, and Teamprise Command-line Client) runs on a variety of operating systems, using Sun's Java virtual machine and libraries to provide much of this cross-platform advantage. Teamprise Explorer and Plug-in for Eclipse

Explorer When installing Teamprise Explorer, the first step is to download Teamprise Explorer application using the following link: http://www.teamprise.com/download/index.html You will need to select the appropriate package classified by operating system. Installing Teamprise Explorer Extract the contents of the .zip file

Explorer. Users may wish to have files opened from within Teamprise Explorer launched from a program other than the system's default viewer. In addition, configuring external viewers may be necessary in situations where the Teamprise Explorer client is unable

Explorer 2.2 is an Eclipse Rich Client Platform application is built on version 3.3 of the Eclipse platform. Starting with Eclipse 3.3, stand-alone RCP applications no longer run on HP-UX on the PA-RISC architecture. The Teamprise Command

Explorer is run from that install location. Reason When Teamprise Explorer runs for the first time, it detects whether it can write some configuration information to the directory where it is installed. If it can write to the install directory