Reference Guide

Java Bridge Use Cases
Zend Server Reference Manual
This section describes some of the common uses for the Java Bridge. The usage scenarios and
examples discussed here provide a framework for the Java Bridge’s uses, rather than a complete picture.
Real world experience indicates that companies are finding more and more applications for the Java
Bridge, beyond what was initially anticipated.
Usage Scenarios
There are two usage scenarios that describe the most common applications for the PHP/Java Bridge:
Integration with Existing Java Infrastructure - PHP is a fully featured scripting language
engineered to cover virtually all of an enterprise’s requirements. At the same time, many
enterprises have a long history of application development in Java. The Java Bridge enables
enterprises to continue to use their Java infrastructure - applications, databases, business logic
and various Java servers (WebLogic, JBoss, Oracle Application Server, etc.).
Accessing Java Language and Architecture - Some enterprises require the full set of PHP
capabilities, yet have a specific need for select Java based applications. SIP signaling in the
communications industry or JDBC for creating connectivity to SQL databases are two examples
of impressive, industry specific products. The Java Bridge enables enterprises to adopt a PHP
standard and to use their preferred Java based applications.
Activities
This section describes two sample activities that indicate some of what you can do with the PHP/Java
Bridge. In the sample activities, it is important to differentiate between Java and J2EE. The difference will
impact on architecture and in turn, on the script code.
The important differences are:
Java is a programming language. Java applications created in Java for the enterprise are not
bound to a specific framework. Therefore, it is possible and perhaps preferable for an enterprise
to relocate code libraries to the server that runs Zend Server.
J2EE is a structured framework for application scripts developed for J2EE. It is preferable that
J2EE servers be left intact.
217