Adobe 38000382 Getting Started Guide - Page 34

JRun servers, Using JRun servers

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 34 highlights

− EJB JRun provides a runtime environment for EJB components. The EJB specification defines a software component model whereby you can deploy server-side application logic (enterprise beans) using EJB-compliant application servers. The JRun EJB container provides automation of services, including component lifecycle, naming, transaction management, messaging, resource management, security, distribution, state management, and persistence. • Web services JRun lets you publish and consume web services, which are distributed software components that provide platform- and location-independent computing, using XML and standard Internet protocols such as HTTP. Using JRun, you can reuse existing Java code as a web service or write new code specifically to publish as a web service. You also can create object- and tag-based clients that can invoke methods on remote web services, even when those services reside on non-Java platforms, such as Microsoft .NET. The following sections contain detailed descriptions of these components. JRun servers A JRun server provides the services necessary for a web server to process J2EE applications containing servlets, JSPs, and EJBs. The JRun server runs in its own process outside any web server process. Running the JRun server in a separate process offers the following advantages: • Increased stability of the web server • The ability to start and stop a web server independently of JRun • The ability to modify an application without restarting the web server • The ability for a single JRun server to communicate with multiple web servers A single installation of JRun supports multiple JRun servers. One reason to create multiple JRun servers is to isolate applications within the processes of separate computers. For example, each JRun server has associated with it a single Java Virtual Machine (JVM) that executes all servlets, JSP pages, and EJBs for that server. The JVM, also known as a JRE, is the software implementation of a CPU. It contains everything necessary to run programs written for the Java platform. By deploying applications on multiple JRun servers, and therefore, in their own JVMs, you can prevent one application from adversely affecting another. Additionally, you can define classpaths, data sources, EJBs, and other resources for each application at the server level. Another reason to execute applications on different JRun servers is that each JRun server can implement its own user-authentication mechanism or set of user-authentication rules. Thus, you can take advantage of a particular server's authentication settings. For more information on authentication, see JRun Administrator's Guide. Using JRun servers JRun provides utilities to start, stop, and perform other functions on the JRun servers. This section describes these utilities for the different JRun platforms. 20 Chapter 2 JRun Programming Model

  • 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
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
20
Chapter 2
JRun Programming Model
−
EJB
JRun provides a runtime environment for EJB components. The EJB
specification defines a software component model whereby you can deploy
server-side application logic (enterprise beans) using EJB-compliant application
servers. The JRun EJB container provides automation of services, including
component lifecycle, naming, transaction management, messaging, resource
management, security, distribution, state management, and persistence.
•
Web services
JRun lets you publish and consume web services, which are
distributed software components that provide platform- and location-independent
computing, using XML and standard Internet protocols such as HTTP. Using JRun,
you can reuse existing Java code as a web service or write new code specifically to
publish as a web service. You also can create object- and tag-based clients that can
invoke methods on remote web services, even when those services reside on non-Java
platforms, such as Microsoft .NET.
The following sections contain detailed descriptions of these components.
JRun servers
A JRun server provides the services necessary for a web server to process J2EE
applications containing servlets, JSPs, and EJBs. The JRun server runs in its own process
outside any web server process. Running the JRun server in a separate process offers the
following advantages:
•
Increased stability of the web server
•
The ability to start and stop a web server independently of JRun
•
The ability to modify an application without restarting the web server
•
The ability for a single JRun server to communicate with multiple web servers
A single installation of JRun supports multiple JRun servers. One reason to create
multiple JRun servers is to isolate applications within the processes of separate
computers. For example, each JRun server has associated with it a single Java Virtual
Machine (JVM) that executes all servlets, JSP pages, and EJBs for that server. The JVM,
also known as a JRE, is the software implementation of a CPU. It contains everything
necessary to run programs written for the Java platform. By deploying applications on
multiple JRun servers, and therefore, in their own JVMs, you can prevent one application
from adversely affecting another. Additionally, you can define classpaths, data sources,
EJBs, and other resources for each application at the server level.
Another reason to execute applications on different JRun servers is that each JRun server
can implement its own user-authentication mechanism or set of user-authentication
rules. Thus, you can take advantage of a particular server’s authentication settings. For
more information on authentication, see
JRun Administrator’s Guide
.
Using JRun servers
JRun provides utilities to start, stop, and perform other functions on the JRun servers.
This section describes these utilities for the different JRun platforms.