Web services features and tools JRun lets you publish and consume web services. Redesigned Web Server Configuration tool with connectors for all major web servers The new JRun Web Server Configuration tool prefills information and provides a much simpler user interface than previous web server connector installers. Load balancing and failover based on object clustering and web server connectors JRun provides enterprise-class server clustering for maximum reliability and scalability.
Clustering is built into both the web server connectors and the JRun kernel: At the web server connector level, clustering enables load balancing and automatic failover between the web server and the web containers. In-memory session replication ensures that state information is preserved if the web server fails over to another web container in the cluster. At the kernel level, clustering enables load balancing and automatic failover for clusterable server objects, such as EJBs, JNDI trees, or any clusterable custom service.
The object state for example, the state of a stateful EJB is automatically replicated in an optimized manner to provide the highest level of reliability while maintaining performance. JRun servers use the Jini technology to dynamically locate their peers in the cluster, eliminating the risk inherent to a single point of failure.
Top 10 Open Source Java and JavaEE Application Servers
JRun 3. Filters - allow pre- and post-processing of servlet requests. For more information, see the following resources: Java Servlet 2. J2EE Connector Architecture 1. For more information, see the the following resources: Java Message Service 1. JavaMail 1. JAXP 1. If the proxy sample included in the web service samples required a username and password, you would instantiate the stubFactory and stub in the client JSP like this: proxy. If you specify an incorrect resultType and Axis knows the correct type, the tag functions correctly.
What is an Application Server?
ResultTypeNamespace is only required when a resultType is not an Axis built-in data type in the default xsd namespace. This is the case for complex user-defined data types. Known limitations You cannot generate a proxy from a Microsoft.
Working with clusters Known limitations When using unicast peers, the granularity of peers is based on the hostname or IP address, which causes all servers on a particular host or IP address to get added to a cluster whether you intend to add them or not. There is no failover for JMS in a cluster. Message-driven beans are clustered but share the same JMS backend. For more information about the security. When manually deploying modules to a cluster, you should copy modules to the cluster deploy directory of a single server, or master server, to simplify administration.
When you use a cluster deploy directory on a master server in a cluster, you should disable the local hot deploy feature set the jrun.
If you do not disable hot deploy on the other servers in the cluster, modules are undeployed when the master server goes down. With hot deploy enabled on the master server, module changes result in redeployment to the other servers in the cluster; this is fine during development, but as stated in JRun Administrator's Guide , hot deploy should not be used in a production environment. Before removing a module or changing its name in the cluster deploy directory of a master server while the server is down, you should bring down all the servers in the cluster.
You should then restart the master server and restart the other servers. When using JMS and a cluster deploy directory, the master JMS server should be the server that contains the cluster deploy directory.
Running clustered servers When using JMS in a cluster, you should always start the JMS master server first and wait for it to complete startup before starting other servers in the cluster. You should always start the servers in a cluster separately. Session replication Session replication only happens at the end of a request when setAttribute or removeAttribute is called on the current session. The only time you must be aware of this feature is when making a change to an existing attribute.
In JRun Administrator's Guide , there is an example showing session replication in which the jrun-web. Do not use an asterisk in production environments. Session failover requires that a server and its session replication buddies form a group. ServerC must have buddies serverA and serverB.
Session failover is not available when using the JRun web server.
Configuring web applications Servlet reloading and compiling JRun Assembly and Deployment Guide states that the jrun-web. Servlet path mapping JRun checks servlet path maps in the following order: Check for an exact match. Configuring EJBs The elements of the jrun-ejb-jar. Notable changes include: The ejb-container section, which lets you set bean persistence properties is directly under the jrun-ejb-jar element, not under the entity and session elements. The cache-size element was added under the entity and session elements.
It lets you set cache sizes for entity beans and stateful session beans. The file-cache-size element no longer exists and its functionality is now under the cache-size element. Configuring resource adapters The JRun Assembly and Deployment Guide states that in order to deploy a resource adapter without a jrun-ra. Note: You should not enable persistXML indefinitely because it increases system overhead.
Restart the JRun server to redeploy the modules and generate deployment descriptors. Manually creating deployment descriptors outside archive files You can use deployment descriptors outside of module archive files even if you create them manually rather than automatically as described above. Redeploying J2EE modules To redeploy a module on a running JRun server with hot deploy enabled, save a deployment descriptor file in an expanded directory or overwrite a module archive file. Important : If a machine listed in a jrun. If you specify an IP address rather than a machine name, the machine is picked up as trusted host.
Macromedia suggests that you use IP addresses instead of host names when specifying trusted hosts. This is very important when setting up a cluster where one or more of the machines might not be running when other servers in the cluster are started. When working with clusters, the security.
If there is no security. When an invalid subnet mask is specified, JRun uses the default value of Modify the new. You can specify one or more server names separated by commas. Using server configuration descriptors Changes to the JRun server configuration descriptors include: In the jrun-resources. In the jrun-resources. In the jrun-users. In the jrun-jms. These new attributes control the behavior of a new limiting mechanism which can prevent overwhelming of the JMS subsystem with incoming messages and pushing the JRun server into an out-of-memory condition.
Also in the jrun-users.
Java for the Web with Servlets, JSP, and EJB: A Developer's Guide
DB2Driver macromedia. InformixDriver macromedia. OracleDriver macromedia. SQLServerDriver macromedia.
- Inquiring into Human Enhancement: Interdisciplinary and International Perspectives.
- The Arithmetic of Dynamical Systems (Graduate Texts in Mathematics)?
- Recent Studies in Bioclimatology: A Group.