Setting up JRun 3.1


Note:  JRun is not a Unanet supported product.  Unanet will run with a number of Servlet Engines.  This information is included for your convenience only.  Please refer to the Macromedia site for detailed platform configuration and tuning recommendations.  Note: If you are interested in JRun pricing through a reseller, please contact support@unanet.com for more information. 


The material on this page is intended to assist you with configuring JRun for use with your Unanet system.  The topics covered on this page include:

You may also be interested in learning more about:


Setting up the Java Runtime Environment (JRE)

This needs to be done prior to the JRun installation.

The JRE is a part of the Java Development Kit (JDK) and is used to support java applications.   The Java Runtime Environment 1.3 can be obtained at http://java.sun.com/j2se/1.3/.  After downloading, simply run the executable to install in the location you desire.


Downloading JRun 3.1

Once this process is complete, you may proceed with the installation of JRun. If you have not downloaded and installed this product you can obtain it at http://www.macromedia.com/software/jrun/. If you do not have any prior experience with setting up this product, it is suggested that you accept the defaults that are given when prompted. 


Setting Up JRun

Before running the JRun's setup program, first Shutdown the Web Server.  If you have any previous versions of JRun installed it is important that they are shut down, uninstalled, and totally removed.

There are different configurations for different Web Servers. Please refer to the JRun Set Up Guide that comes with JRun for further configuration of setup type and connectors (each web server is different). 

Note 1: The interface will ask you if you want to set up connectors at the end of the connector process, or close the browser and setup the connectors in the JRun Management Console for connector setup. Choose the option to set up the connectors in the JRun Management Console and the interface comes up right away. The first option seems to hang and not setup the connectors properly. 

Note 2: The Administrator username will be “admin”. Remember the password that is entered during the setup as this will be important when using the JRun Management Console to configure Unanet. 

Note 3: Check out the Tuning Guidelines section below if you expect large data volumes. 


Testing JRun 3.1

To verify the JRun connection to the web server, type the following in the browser.

http://<YourWebServerMachineName>.<YourDomain>/demo/index.html

Example: If the machine name or the web server is joe and the domain is juneau.com, then the following would be entered:

http://joe.juneau.com/demo/index.html

Important Note:  Test to enter the sample pages on the index.html. If they do not appear correctly, do not continue with the following instructions.  Get the servlet working first.  Consult any JRun documentation or contact Macromedia for assistance on their product. 

When using the Microsoft IIS 5.0 (Internet Information Server) on Windows 2000 platform, if your server returns a "500 internal server" or "404 Page not found" message when verifying your JRun connection, please refer to this article. http://www.macromedia.com/v1/Handlers/index.cfm?ID=21895&Method=Full


Setting up the JRun Classpath and Alias

Open the JRun Management Console, or in a browser, go to <machine.domain name:8000>, login with the admin username and the password that was set earlier. 

Classpath

In the JRun Management Console, go to JRun Default Server\Java Settings. In the "name" column, click "classpath". An edit window will pop up. Go to the edit window, navigate down to the bottom line and enter the following text (if c:\ is the drive you are working with, this tends to be the default)  c:\unanet\unanet.jar, and click "update".

It should look similar to this.

{jrun.rootdir}/servers/lib
{jrun.server.rootdir}/lib
c:\unanet\unanet.jar

Alias

Still in the JRun Default Server, expand Web Applications and in Default User Application, choose servlet definitions. Click the edit button, and in the following fields enter the following information:

Name - unanet  

Class Name - com.unanet.unatime.servlet.UnaTimeServlet

Display Name - unanet

Description - Unanet 

Init Arguments - (remove or overwrite the current information) properties=c:\unanet\properties

Click "update".

Stop and restart JRun.


Once JRun is setup, the system is ready for the Unanet installation.


JRun Tuning Guidelines:

Depending on your data configuration and expected volumes, you may want to consider changing a few of the default JRun parameters in order to improve your system performance.  For complete information about tuning JRun, we recommend that you refer to the Macromedia site.  You may want to increase the defaults for the following parameters in particular. 

Increase your JRun timeout parameters

Go to your JRun Management Console > JRun Default Server > Web Applications > Default User Application > Session Settings > Session Timeout(min) to make changes to the JRun timeout parameters. The maximum settings for these parameters are not displayed in Macromedia's JRun documentation.  This may be necessary if you have very large data volumes and as a result, encounter long data imports or other long running Unanet processes.

Increase JVM memory allocation

Go to your JRun Management Console > JRun Default Server > Java Settings > Java Arguments. Click on Java Arguments, and you will see an example that you can place in the arguments field of -Xmx 128M. Entering this argument is the maximum number allowed.  Increasing this parameter will allocate additional memory to your JVM and potentially improve performance for system processes.  Keep in mind total system memory needs when configuring this parameter.  Check with the  Macromedia site for additional information.  


If you are having any problems, contact support@unanet.com for assistance.

Back to Installation Table of Contents


Copyright © 1998-2002 Computer Strategies, Inc., All Rights Reserved.
Last revised: September 13, 2002.