Installing JRun
Connecting JRun to External Web Servers

Running the Web Server Configuration tool

When you run the Web Server Configuration tool, you specify the ProxyService of the JRun server that is configured for SSL. The Web Server Configuration tool configures the web server connector to use SSL between the web server and the JRun server.

Note:   If you configured your web server using the Web Server Configuration tool and then decide to enable SSL, open the web server connector configuration file (for example, jrun.ini, httpd.conf, or obj.conf), and set the ssl property to true.

If you configure a cluster, you must enable SSL for the Proxy Service for all or none of the JRun servers in the cluster.

For more information, see JRun Administrator's Guide.

To install the Web Server Configuration tool on the web server:

1. Start the JRun installation procedure for your web server platform.

   For details, see Chapter 2, "Installing JRun".

2. In the Setup Type window, select Custom.
3. Select to install the Web Server Configuration tool, and specify the install location.
4. Finish the installation.
5. Start the Web Server Configuration tool in one of the following ways:
   • (Windows) Select Start�> Programs�> Macromedia JRun 4�> Web Server Configuration Tool
   • From the command line, change directories to jrun_root/lib, and enter:

        javaw -jar wsconfig.jar
     

   Note:   jrun_root is the directory into which JRun 4 installs.

   For information on running the Web Server Configuration tool from the command line, see "Command line options".

   The JRun Web Server Configuration tool window appears:

   

6. Click Add.

   The Add Web Server Configuration dialog box appears:

   

7. In the JRun Server drop-down list box, select the JRun server or cluster name that you want to configure. Individual server names in a cluster do not appear.

   Note:   The JRun server or cluster does not have to reside on the web server system.

8. In the Web Server Properties area, enter your web server information, and click OK.

   For instructions on configuring JRun with your specific web server, see the appropriate following sections.

Command line options

You can run the Web Server Configuration tool from the command line using the following syntax:

java -jar jrun_root/lib/wsconfig.jar [command line options]

The following table lists the command line options:

Option	Definition
-ws <IIS|apache|NES|iPlanet|Zeus>	Web server type.
-dir <dirname>	Apache conf, NES, or Zeus config directory.
-site <site-name>	IIS website name. (If the website name contains spaces, use quotation marks.) Use All (English version only) or 0 to configure global filter or application mappings for all websites.
-host <ipaddr|DNS host>	JRun server address (default=localhost).
-server	JRun server name (default=default).
-cluster	JRun cluster name.
-l	Enable verbose logging in connector log.
-a	Enable native OS memory allocation.
-map	IIS application mappings list (no spaces); (.ext1 [,.extn]). If -map is not specified with IIS, a filter is implied.
-bin <filename>	(Optional) Apache binary file. If not specified, the default search algorithm locates the apache.exe (Windows) or httpd (UNIX) executable file.
-script <filename>	(Optional) Apache control script file for starting and stopping the web server.
-service	The Windows service name for Apache (only for Apache in Windows; default=Apache).
-v	Verbose output from Web Server Configuration tool.
-norestart	Do not change web server status. For example, do not start, restart, or stop web server.
-list	List all configured web servers.
-list -host <server-host>	List all JRun servers on the specified host.
-r	Remove configuration (-ws and -dir or -site).
-u	Uninstall all configured connectors.
-info	Print JRun version information.
-h	List all parameters.

To use a property file for options, enter the following command:

java -jar jrun_root/lib/wsconfig.jar -f property-file

The following table lists the property file tags:

Property file tag	Command line equivalent
ws	-ws
dir	-dir
site	-site
host	-host
server	-server
cluster	-cluster
map	-map
service	-service
bin	-bin
alloc	-a
verbose	-l
debug	-v
remove	-r
list	-list
uninstall	-u

Enclose file pathnames in quotation marks, particularly if they contain spaces. In Windows-style pathnames, add a backslash; for example:

ws=apache
dir="c:\\program files\\apache group\\apache\\conf"
host=localhost
server=default
l=true

Verifying the connection between JRun and your external web server

After running the Web Server Configuration tool on your external web server, you can verify the connection between JRun and the web server.

To verify the connection:

1. Ensure that your web server is running.
2. Open a web browser on the web server host to the following URL: http://web-server-hostname.

   Note:   This procedure assumes that the external web server is listening for connections on the default port 80. If not, use http://web-server-hostname:webserver-port-number.

   The default page for the web server to which you connected appears, showing that you successfully configured the connection between JRun and your external web server.

Web Server Configuration directory structure

By default, JRun creates the following directories and files in jrun_root/lib/wsconfig:

Directories and files	Description
1, 2, ..., n	Contains one directory for each web server configured. The numbers might not be consecutive because you can remove a configuration in any order.
wsconfig.log	Contains the log of the Web Server Configuration tool installations.
wsconfig.properties	Contains the database that the Web Server Configuration tool uses to maintain web server configuration information.

The following table describes the files in the jrun_root/lib/wsconfig/n directory:

File	Description
.dll or .so (Windows) .so (all other platforms)	Contains the native connector.
jrunserver.store	Contains information that the Web Server Configuration tool uses for clustering web servers.
README.txt	Contains web server configuration information.
jrunxxxx.log (IIS only)	Contains Web Server Configuration tool log information (IIS only; others reside in their web server logs).
jrun.ini (IIS only)	Contains configuration information.

For more information, see JRun Administrator's Guide.

Removing a web server configuration

After you configure a web server using the Web Server Configuration tool, you must delete the configuration before you can configure the web server again.

You can remove the web server configuration in one of two ways:

• Using the Web Server Configuration tool:

  

  Select the web server configuration or configurations that you want to remove, and click Remove.

• Using the command:

  When removing the configuration, you specify the same directory or website that you specified when you initially configured the web server (listed in the README.txt file for each web server configuration).

  Web server	Command
  Apache	java -jar jrun_root/lib/wsconfig.jar -ws apache -dir apache_root/conf -r
  IIS	java -jar jrun_root\lib\wsconfig.jar -ws iis -site sitename -r
  NES/iPlanet	java -jar jrun_root/lib/wsconfig.jar -ws nes -dir nes_root\https-xxxx/config -r (The name of the NES server is https-xxxx.)
  Zeus	java -jar jrun_root/lib/wsconfig.jar -ws zeus -dir zeus_root/ns-config/https-xxxx/config -r (The name of the Zeus server is https-xxxx.)

  Delete the initial configuration as follows, depending on your web server:

Comments

Add Comment

SconeCutter said on Dec 3, 2003 at 1:21 PM :

Documentation incorrect:

javaw -jar wsconfig.jar

I believe it should be

java -jar jrun_root/lib/wsconfig.jar [command line options]

Robin Hilliard said on Mar 10, 2004 at 9:37 PM :

I'm trying to set multiple JRun connectors up with virtual hosts on
Apache - will keep looking for instructions but would be good to put
pointers to virtual host instructions on this page.

jrunrandy said on Mar 11, 2004 at 5:13 AM :

Try http://livedocs.macromedia.com/jrun/4/JRun_Administrators_Guide/connectors.htm

EduDog said on Jun 29, 2004 at 6:42 AM :

Section on Verifying Web Server Connection is incorrect. It does not establish that the web server is connected to the JRun server, since it would only display the web server's default page.

alubell said on Nov 28, 2004 at 6:48 PM :

FLEX: If you selected the Flex 1.5 installation with Integrated JRun server, none of this information is valid. The Integrated version of Jrun does not give you the necessary tools to do this.

dio said on Jan 21, 2005 at 12:13 PM :

if deploying cf on jrun, is this step necessary for running a site other than
the cf administrator. my install seems to work fine on my MAC. however,
i need to set up a site that does not require, the cfusion context root in
the url (http://hostname:portnumber/contextroot/pagename.cfm). any
ideas? not sure if i have to config apache for this...?

RSS feed | Send me an e-mail when comments are added to this page | Comment Report

Current page: http://livedocs.adobe.com/jrun/4/Installing_JRun/servconf3.htm

Add Comment