Accessibility
 
Home > Products > JRun > Support > Getting Started with JRun
Macromedia Director Support Center - Getting Started with JRun
Property migration chart

The following table lists JRun properties, whether the migration tool converts them, and their respective configuration files in JRun 3.1 and JRun 4. For the directory locations of each configuration file, see JRun 3.1 configuration file directories and JRun 4 configuration file directories.

 

Property Migrated JRun 3.1 location JRun 4 location

WebService port

Yes

local.properties:

web.endpoint.main.port

jrun.xml:

WebService

The port value is reset.

ProxyService port

Yes

local.properties:

jcp.endpoint.main.port

jrun.xml:

ProxyService

The port value is reset.

JNDI port

Yes

local.properties:

control.endpoint.main.port

jndi.properties:

java.naming.provider.url

The port value is reset.

Method timing

No

global.properties:

method timing

jrun.xml:

InstrumentationService

Global web application properties

No

global.properties, local.properties

default-web.xml

Global web application properties are only server-wide in JRun 4.

Default security roles and users

Yes

users.properties

jrun-users.xml

JRun 4 uses server-wide security rather than global security. To emulate 3.1 functionality, users and roles are added to all JRun servers during migration.

You cannot use the wildcard character (*) as a user name.

You must rewrite custom security modules to use the Java Authentication and Authorization Service (JAAS); for more information, see JRun Administrator's Guide.

JRun Tag Library Global Mapping

No

global.properties:

webapp.path-mapping./WEB-INF/
jrun/jruntags.jar

You must manually copy the jruntags.jar file to the WEB-INF/lib directory of your web applications that use the JRun Tag Library. Macromedia recommends that you use the new JSP Standard Tag Library rather than the JRun Tag Library for new projects; for more information, see http://jakarta.apache.org/taglibs/doc/standard-doc/intro.html.

Web application context root

Yes

local.properties:

jrun.webapp-mapping

jrun-web.xml:

context-root

For enterprise applications, set the context root in the application.xml file.

Web application hotdeploy settings

No

global.properties:

Web application hot-deploy settings

jrun.xml:

DeployerService

By default, hot deploy is enabled.

Web application virtual paths

Yes

local.properties:

Web Application Settings

webapp.properties:

webapp.path-mapping

jrun-web.xml:

virtual-mapping

The use-web-server-root property used in JRun 3.1 does not exist in JRun 4. The virtual-mapping property replaces it. You must manually replace use-web-server-root settings with virtual-mapping settings.

Launcher classpath settings

No

global.properties:

Java VM Settings

jvm.config:

java.home

java.args

classpath.dirs

java.library.path

You can also configure these properties in the JRun Management Console (JMC).

Disable JSP translation

No

webapp.properties:

webapp.servlet-mapping.*.jsp=jsprt

default-web.xml:

JSPServlet init-param:

translationDisabled

Keep generated JSP .java files

No

JRun 3.1 always keeps the generated .java files.

default-web.xml:

JSPServlet init-param: keepGenerated

By default, JRun 4 does not keep the generated .java files.

JDBC data sources

Yes

local.properties:

JDBC DataSource Binding Service

jrun-resources.xml:

datasource

You must remove the java:comp/env prefix from the JNDI lookups in your code.

JavaMail sessions

No

local.properties:

JavaMail Session Binding Service

jrun-resources.xml:

mailSession

You must remove the java:comp/env prefix from the JNDI lookups in your code.

JMS settings

No

local.properties:

JMS Queue/Topic Binding Service

jrun-resources.xml:

jmsDestination

jmsConnectionFactory

You must remove the java:comp/env prefix from the JNDI lookups in your code.

Logging settings

No

global.properties, local.properties:

logging services

jrun.xml:

LoggerService

Services to start automatically

No

global.properties, local.properties:

list of services to start

jrun.xml:

A service listed in jrun.xml starts automatically unless the deactivated attribute is set to true.

SSL settings

Yes

local.properties:

ssl.endpoint.main.port

ssl.keyStorePassword

jrun.xml:

SSLService

The port is set to 9100. You must manually set it to a unique port number.


 
JRun 3.1 configuration file directories
The following table lists the directories that contain the JRun 3.1 configuration files referenced in the Property migration chart:

Filename Directory

local.properties

jrun_root/servers/jrun_server

global.properties

jrun_root/lib

users.properties

jrun_root/lib

webapp.properties

jrun_root/servers/jrun_server/web_app/WEB-INF


 
JRun 4 configuration file directories
The following table lists the directories that contain the JRun 4 configuration files referenced in the Property migration chart:

Filename Directory

default-web.xml

jrun_root/servers/jrun_server/SERVER-INF

jndi.properties

jrun_root/servers/jrun_server/SERVER-INF

jrun.xml

jrun_root/servers/jrun_server/SERVER-INF

jrun-resources.xml

jrun_root/servers/jrun_server/SERVER-INF

jrun-users.xml

jrun_root/servers/jrun_server/SERVER-INF

jrun-web.xml

jrun_root/servers/jrun_server/web_app/WEB-INF

jvm.config

jrun_root/bin

To Table of Contents Back to Previous document Forward to next document