Creating A Custom Jrun Interface; Hiding The Jmc; Deploying Applications Outside The Jrun Directory Structure - Adobe 38000382 - Macromedia JRun - Mac Manual

Creating a custom JRun interface

To let your customers interact with the JRun servers and services but still maintain your
application's brand, you can do one of the following:
Build a JRun management interface using the JMC custom tag library. For more
information, see
Rebrand the JMC using the JMC source code.

Hiding the JMC

You might not want your customers to have access to the JMC at all. In this case, remove
the JMC merge module (Windows) or the JMC fileset (UNIX) before creating your
installer.
You can include the JMC if you plan to use it for troubleshooting. You can include the
JMC, and then disable the admin JRun server, so that you (or your field technical
support) can access it only when necessary.

Deploying applications outside the JRun directory structure

To deploy your application outside of the JRun hierarchy, you can use the
addDeployDirectory
access to the DeployerService, or you can modify the jrun.xml file that defines the
DeployerService's settings.
The following JSP page uses the
deploy directory:
<%@ taglib prefix="jmcmgmt" uri="WEB-INF/lib/jmcmgmt.jar" %>
...
<jmcmgmt:invoke server="default"
<jmcmgmt:parameter value="C:\MyApplication\deploy"/>
</jmcmgmt:invoke>
<% if (error == null) {
out.println("successfully added directory");
} else {
error.printStackTrace();
out.println("failed - " + error.getMessage());
} %>
The preceding code adds the following line to the DeployerService's definition in the
jrun.xml file:
<attribute name="deployDirectory">c:/MyApplication/deploy</attribute>
JRun deploys this application when you add a web application to this directory. You are
not required to restart the JRun server to deploy the application.
For more information about using the JMC tag library, see
Custom Tag Library" on page
For more information on using the DeployerService, see JRun Administrator's Guide.
44 Chapter 5 Embedding JRun
Chapter 6, "Using the JMC Custom Tag Library" on page
method of the DeployerService. JRun provides programmatic
invoke
mbean="DefaultDomain:service=DeployerService"
method="addDeployDirectory" errorId="error">
47.
tag in the JMC custom tag library to add a hot
Chapter 6, "Using the JMC
47.