This chapter includes the following sections:
Parent topic: Using Coherence REST
DefaultHttpServer
(backed by Oracle's lightweight HTTP server)
GrizzlyHttpServer
(backed by Grizzly HTTP server and recommended for production environments)
SimpleHttpServer
(backed by Simple HTTP server)
JettyHttpServer
(backed by Jetty HTTP server)
The HTTP server must be enabled on a Coherence proxy server. To enable the HTTP server, edit the proxy's cache configuration file and add an <http-acceptor>
element, within the <proxy-scheme>
element, and include the host and port for the HTTP server. The <address>
element also supports external NAT addresses that route to local addresses; however, both addresses must use the same port number.
The following example configures the HTTP server to accept requests on localhost 127.0.0.1
and port 8080
. The example explicitly defines the HTTP server class and Jersey resource configuration class and uses /
as the context path for the Coherence REST application. However; these are default values and need not be included. The context path can be changed as required and additional Coherence REST applications can be defined with different context paths. See http-acceptor in Developing Applications with Oracle Coherence.
<proxy-scheme> <service-name>ExtendHttpProxyService</service-name> <acceptor-config> <http-acceptor> <class-name> com.tangosol.coherence.rest.server.DefaultHttpServer</class-name> <local-address> <address>127.0.0.1</address> <port>8080</port> </local-address> <resource-config> <context-path>/</context-path> <instance> <class-name> com.tangosol.coherence.rest.server.DefaultResourceConfig </class-name> </instance> </resource-config> </http-acceptor> </acceptor-config> <autostart>true</autostart> </proxy-scheme>
If you are using POF, make sure that the pof-config.xml
file includes the location of the REST POF types. See Configuring REST Server Access to POF-Enabled Services.
This section includes the following topics:
Create a managed Coherence server in your WebLogic Server domain that will host Coherence REST. The server should be configured as a storage disabled member of a Coherence cluster. If more than one managed Coherence server is required for a Coherence REST solution, then the servers should be managed as a tier in a WebLogic Server cluster. See Setting Up a Coherence Cluster in Administering Clusters for Oracle WebLogic Server.
To package the Coherence REST Web application:
To deploy the Enterprise application:
http://
host
:
port
/rest/
{cacheName}
.This section includes the following topics:
Coherence REST can be deployed to any servlet container by packaging Coherence REST as a WAR file. See Packaging Coherence REST for Deployment. Refer to your vendors documentation for details on deploying WAR files. In addition, See the Jersey user guide for additional servlet container deployment options:
http://jersey.java.net/nonav/documentation/latest/user-guide.html#d4e194
coherence-rest-pof-config.xml
file that is located in the coherence-rest.jar
library and is automatically loaded at runtime.To configure the REST default user types, edit the pof-config.xml
file to include the coherence-rest-pof-config.xml
POF configuration file. For example:
<pof-config> <user-type-list> <include>coherence-pof-config.xml</include> <include>coherence-rest-pof-config.xml</include> ... </user-type-list> </pof-config>