Overview of Coherence Web 3.7

Coherence*Web is an HTTP session management module dedicated to managing session state in clustered environments. Built on top of Oracle Coherence, Coherence*Web:

1) Enables session sharing and management across different web applications, domains and heterogeneous application servers;
2) Brings Coherence data grid's data scalability, availability, reliability and performance to in-memory session management and storage;
3) Supports all the mainstream application servers such as Oracle WebLogic Server, IBM WebSphere, Tomcat etc. (Coherence Web Support Matrix);
4) Supports numerous portal containers including Oracle WebLogic Portal.
5) Allows session state to be managed in the various caching topologies available in Coherence (i.e. Replicated, Partitioned, Near Caching, Read-Through, Write-Through, Write-Behind and Refresh-Ahead Caching etc.);
6) Allows storage of session data outside of Java EE application server – freeing up application server heap space and enabling server restarts without session data loss;
7) Supports multiple advanced session models which define how the session state is physically managed, serialized and deserialized in the cluster;
8) Supports fine-grained session and session attribute scoping by way of pluggable policies

Coherence*Web is an alternative to the WebLogic Server in-memory HTTP state replication services. Consider using Coherence*Web if you are encountering any of these situations:

1) Your application works with large HTTP session state objects
2) You run into memory constraints, due to storing HTTP session object data
3) You want to offload HTTP session storage to an existing Coherence cluster
4) You want to share session state across enterprise applications and Web modules

Refer the below mwntioned links to read more about Coherence Web:

1) http://www.oracle.com/technetwork/articles/entarch/session-management-092739.html
2) http://coherence.oracle.com/display/COH35UG/Coherence*Web+Session+Models
3) http://tomhofte.blogspot.com/2009/11/oracle-coherenceweb-easy-in-memory.html

Other useful documents are listed below:

1) Coherence Web Push Replication:
2) Caching HTTP Sessions with Coherence Web 3.7 Example
3) Coherence Management from Weblogic Console
4) JMX Monitoring and Running Examples
5) Customer Success

Oracle OSB Sample Examples (Getting Started with Oracle OSB)

http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/examples/samples.html
http://download.oracle.com/docs/cd/E13159_01/osb/docs10gr3/tutorial/tutGettingStarted.html
http://www.oracle.com/technology/sample_code/products/osb/samples/osb_examples_tutorials_0.pdf
http://www.oracle.com/technology/products/soa/service-bus/collateral/osbsamples.html
http://www.oracle.com/technetwork/articles/jumpstart-for-osb-development-page--084104.html

Guide to install Eclipse for Oracle OSB

http://blogs.oracle.com/middleware/entry/installing_eclipse_for_osb_development

How to start viewing Composite Name on the EM Console/Dashboard?

You need to set the ora:setCompositeInstanceTitle("Composite Name") in the BPEL pocess or mediator using the Assign activity to a dummy variable as under,

WSDL Caching in SOA Server

Yes all the partner WSDLs are cached in the SOA Server and by default they are cached for 24 hours. In order to change the cache time do the following,

Farm_soa_domain > Weblogic Domain > soa_domain* > Right Mouseclick > System MBean Browser > Application Defined MBeans > oracle.as.soainfra.config > Server: soa_server > SoaInfraConfig > soa-infra > Attributes

There is an Attribute "UddiCacheLifetime" defining the external WSDL cache time. By default, the value is set to 24 hours and the minimum time of 300 seconds could be set.

Accessing Custom JAVA Code in BPEL (Eg. ora:custom code)

If you would like to use some code in your BPEL processes (Eg: ora:custom implementation, Java Embedded Activity) then create a JAR file of your Java project and do the following,

1) cd to /soa/modules/oracle.soa.ext_11.1.1
2) Copy in your custom jar file
3) run ant (make sure ant is installed and available in this directory) on command prompt. This will run the build.xml file located in the above directory
4) Restart the Server

A "readme" file, is available in the above directory that provides instructions to add the custom jar to manifest of oracle.soa.ext.jar that is picked up the class loader.

Where can you find the older versions of Java?

http://www.oracle.com/technetwork/java/archive-139210.html