Skip Navigation Links | |
Exit Print View | |
About Oracle Java CAPS Communication Adapters Java CAPS Documentation |
About Oracle Java CAPS Adapter for CICS
The Oracle Java CAPS Adapter for CICS
IBM CICS Transaction Gateway (CTG)
Oracle Java CAPS CICS Listener
z/OS CICS Security Considerations
Security Considerations for Oracle Java CAPS CICS Listener
Security Considerations for IBM CICS Transaction Gateway
About Oracle Java CAPS Adapter for COM/DCOM
The Oracle Java CAPS COM/DCOM Adapter
About Oracle Java CAPS Adapter for e-Mail
How does the e-Mail Adapter connect?
About Oracle Java CAPS Adapter for File
About Oracle Java CAPS Adapter for Batch
About Oracle Java CAPS Adapter for IMS
About Information Management System (IMS)
About Oracle Java CAPS Adapter for LDAP
Entries, Attributes, and Values
Distinguished Names and Relative Distinguished Names
Java Naming and Directory Interface
Third-Party License File Agreement
About Oracle Java CAPS Adapter for MSMQ
About Microsoft Message Queuing (MSMQ)
About Oracle Java CAPS Adapter for TCP/IP
About Oracle Java CAPS Adapter for TCP/IP HL7
About Oracle Java CAPS Adapter for HTTPS
Cookie Expiration Date Checking
This topic provides conceptual information about SNA and its Oracle Java CAPS Adapter.
SNA is a data communications architecture developed by IBM to specify common conventions for communication between various IBM hardware and software products. It is specifically designed to address issues of reliability and flexibility of sharing data between components and their peripherals. Many vendors other than IBM also support SNA, allowing their products to interact with SNA networks.
An addressable unit on an SNA network is called a node, and is made up of four functional components forming a hierarchy.
To establish a communications session, SNA uses Logical Units (LUs) as entry points into the network. There are several types of LUs, currently type 0 through type 6.2. Most of the LU types are specific to IBM operating environments, but type 6 is intended for use in a distributed data processing environment.
Generally, an LU can communicate only with another LU of the same type, but specific exceptions to this rule exist with type 6.2. LU6.2 is the least-restrictive of the various LU types, and also supports multiple concurrent sessions. As a result, it is the LU most widely supported by other system vendors.
Like the OSI model, SNA functions are divided into seven hierarchical layers, but the layers are not identical. The Transport Network handles the lower three layers, while the Network Accessible Units (NAU) implement the upper four layers by using the services of the Transport Network to establish communication between nodes.
SNA defines formats and protocols between these layers that allow equivalent layers in different nodes to communicate with each other. Also, each layer provides services to the layer above, and requests services from the layer below.
SNA uses a standard method for the exchange of data within a network. This standard method defines how to establish a route between components, how to send and receive data reliably, how to recover from errors, and how to prevent flow problems.
Originally designed for networks in which a mainframe computer controls the communications relationships, SNA has since evolved to incorporate protocols and implementations to allow two user processes to communicate with each other directly. These two different networking models, or roles, are referred to as hierarchical and peer-oriented, respectively. The peer-oriented model is designed to allow distributed control of the communications process independent of the mainframe.
The peer-to-peer connection between two user processes is known as a conversation, while the peer-to-peer connection between two LUs is known as a session. A session is generally a long-term connection between two LUs, while a conversation is generally of shorter duration.
A User Process is also known as a Transaction Program (TP). Also, the interface between a User Process and an LU is known as Presentation Services.
LU 6.2, also known as APPC (Advanced Program-to-Program Communication), is used for Transaction Programs communicating with each other in a distributed data processing environment. In a CPIC (Common Programming Interface for Communications) implementation, CPIC provides the API that contains the commands, known as verbs, that are used by LU 6.2 to establish communication sessions.
Two types of Presentation Service interfaces are possible with LU6.2: mapped conversations and unmapped, or basic, conversations. The following table summarizes the set of LU6.2 commands for basic conversations. Equivalent commands for mapped conversations have the prefix <MC_> added to the command name. Note that “control operator verbs” are not listed.
Table 1 LU6.2 Commands
|
The SNA Adapter enables the Oracle Java CAPS ESB system to access an SNA network environment to drive entire transactions, including conversational transactions.
The SNA Adapter is an interface that makes calls to an SNA Server. The SNA Server acts as a high-speed gateway between distributed SNA Clients and the SNA network having a mainframe host system.
In a typical data exchange using the SNA Adapter, the Adapter invokes the LU6.2 protocol--through the invocation of CPI-C calls--to enable the SNA client to send requests to the SNA server. For outbound Adapters, the Adapter can be triggered by any incoming message. For inbound Adapters, the Adapter is triggered by established conversation activity.