Adobe 38000382 JRun Guide - Page 63

Strategies for working with the JMC custom tags, Finding services, classes, and methods

Get Adobe 38000382 - Macromedia JRun - Mac PDF manuals and user guides
UPC - 718659575946
View all Adobe 38000382 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 63 highlights

Strategies for working with the JMC custom tags The JMC custom tags provide power and flexibility when working with JRun services and objects. This section describes some strategies for working with this custom tag library. Finding services, classes, and methods To find the possible attributes for services, look in the following places: • HtmlAgentService Use this web-based interface to access services using JMX. You can use the HtmlAgentService to determine services availability, and which attributes of those services are writable. For more information on the HtmlAgentService, see JRun Administrator's Guide. • jrun.xml file Read the jrun.xml file to see services and their attributes that are defined for each JRun server. For more information on the jrun.xml file, see JRun Administrator's Guide. • JMC source code Read the JMC source code to see how the JMC uses the JRun tags described in this section. For information on reading the JMC source code, see "JMC source code overview" on page 42. • JMC Javadocs Use the JRun API Javadocs to explore services and methods available to JRun objects such as servers. The SDK includes a special set of Javadocs for the JMC objects. You can access these from the sdk_root/docs/jmc-javadocs directory. • JRun API Javadocs The retail version of JRun includes Javadocs for most JRun APIs. You can access these from the jrun_root/docs/Javadocs directory, or from the documentation homepage (/docs/dochome.htm). Using the service and server attributes The service attribute specifies a JRun service on which to invoke the tag. The service attribute does not refer only to a service name; it is a service path. A service path is a service that is specified in jrun.xml (or other XML configuration file) by its name and the names of its ancestors. The service paths use the following syntax: ParentService[.ChildService[.GrandChildService[...]]] The following table shows several service paths: Service path JRunServer JRunServer.ClusterManager JRunTransactionService.PrivateJmsDomain Description A top-level service. A service underneath a top-level service. A service underneath a top-level service. When you specify a service attribute in a JMC custom tag, you can also specify a server attribute. Strategies for working with the JMC custom tags 49

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
Strategies for working with the JMC custom tags
49
Strategies for working with the JMC custom tags
The JMC custom tags provide power and flexibility when working with JRun services
and objects. This section describes some strategies for working with this custom tag
library.
Finding services, classes, and methods
To find the possible attributes for services, look in the following places:
•
HtmlAgentService
Use this web-based interface to access services using JMX. You
can use the HtmlAgentService to determine services availability, and which attributes
of those services are writable. For more information on the HtmlAgentService, see
JRun Administrator’s Guide
.
•
jrun.xml file
Read the jrun.xml file to see services and their attributes that are
defined for each JRun server. For more information on the jrun.xml file, see
JRun
Administrator’s Guide
.
•
JMC source code
Read the JMC source code to see how the JMC uses the JRun
tags described in this section. For information on reading the JMC source code, see
“JMC source code overview” on page 42
.
•
JMC Javadocs
Use the JRun API Javadocs to explore services and methods
available to JRun objects such as servers. The SDK includes a special set of Javadocs
for the JMC objects. You can access these from the
sdk_root
/docs/jmc-javadocs
directory.
•
JRun API Javadocs
The retail version of JRun includes Javadocs for most JRun
APIs. You can access these from the
jrun_root
/docs/Javadocs directory, or from the
documentation homepage (/docs/dochome.htm).
Using the service and server attributes
The
service
attribute specifies a JRun service on which to invoke the tag.
The
service
attribute does not refer only to a service name; it is a
service path
. A service
path is a service that is specified in jrun.xml (or other XML configuration file) by its
name and the names of its ancestors.
The service paths use the following syntax:
ParentService[
.
ChildService[
.
GrandChildService
[...]]]
The following table shows several service paths:
When you specify a
service
attribute in a JMC custom tag, you can also specify a
server
attribute.
Service path
Description
JRunServer
A top-level service.
JRunServer.ClusterManager
A service underneath a top-level service.
JRunTransactionService.PrivateJmsDomain
A service underneath a top-level service.