[Courtesy: Oracle Docs]
[caption id="attachment_113" align="aligncenter" width="468"]
Fig. Network Protocols[/caption]
NOTE: For more details on Networking protocols please follow the section "Network Communications Technologies" in the URL:https://docs.oracle.com/cd/E13222_01/wls/docs81/intro/chap1.html
Having understanding of the network communication mechanism, lets move on to understand Data and Access Services w.r.t Weblogic Server.
[Courtesy: Oracle Docs]
NOTE: For detailed understanding on these please follow the section "Data and Access Services" in the URL: https://docs.oracle.com/cd/E13222_01/wls/docs81/intro/chap1.html
[Courtesy: Oracle Docs]
The J2EE messaging technologies provide standard APIs that WebLogic Server applications can use to communicate with one another as well as with non-WebLogic Server applications. The messaging services include the following APIs:
NOTE: For details on JMS please refer the section "JMS" in the URL: https://docs.oracle.com/cd/E13222_01/wls/docs81/intro/chap1.html
- Client applications connect with WebLogic Server using standard networking protocols over TCP/IP.
- WebLogic Server listens for connection requests at a network address that can be specified as part of a Uniform Resource Identifier (URI).
- A URI is a standardized string that specifies a resource on a network, including the Internet. It contains a protocol specifier called a scheme, the network address of the server, the name of the desired resource, and optional parameters. The URL you enter in a Web browser, for example,
http://www.bea.com/index.html, is the most familiar URI format. - Web-based clients communicate with WebLogic Server using the HTTP protocol. Java clients connect using Java RMI (Remote Method Invocation), which allows a Java client to execute objects in WebLogic Server. CORBA-enabled clients access WebLogic Server RMI objects using RMI-IIOP, which allows them to execute WebLogic Server objects using standard CORBA protocols.
- In the following table, the scheme in a URI determines the protocol for network exchanges between a client and WebLogic Server.
[caption id="attachment_113" align="aligncenter" width="468"]
Fig. Network Protocols[/caption]NOTE: For more details on Networking protocols please follow the section "Network Communications Technologies" in the URL:https://docs.oracle.com/cd/E13222_01/wls/docs81/intro/chap1.html
Having understanding of the network communication mechanism, lets move on to understand Data and Access Services w.r.t Weblogic Server.
Data and Access Services:
[Courtesy: Oracle Docs]
WebLogic Server implements standard J2EE technologies to provide data and access services to applications and components.
These services include the following APIs:
- Java Naming and Directory Interface (JNDI)
- Java Database Connectivity (JDBC)
- Java Transaction API (JTA)
- J2EE Connector Architecture
- eXtensible Markup Language (XML)
NOTE: For detailed understanding on these please follow the section "Data and Access Services" in the URL: https://docs.oracle.com/cd/E13222_01/wls/docs81/intro/chap1.html
Messaging Technologies:
[Courtesy: Oracle Docs]
The J2EE messaging technologies provide standard APIs that WebLogic Server applications can use to communicate with one another as well as with non-WebLogic Server applications. The messaging services include the following APIs:
- Java Message Service (JMS)
- JavaMail
NOTE: For details on JMS please refer the section "JMS" in the URL: https://docs.oracle.com/cd/E13222_01/wls/docs81/intro/chap1.html
No comments:
Post a Comment