A term in italic font means that it is explained somewhere else in the glossary.
access point
See service access point.
ACID properties
Acronym for the fundamental properties of a transaction: atomicity, consistency, isolation and durability.
advanced program-to-program communication (APPC)
Another name for the LU6.2 protocol and the underlying architecture.
APPC
See advanced program-to-program communication (APPC).
appender
Log4j message destination. The logging messages transferred to a logger are output by the appender(s) assigned to the logger.
application entity
An application entity represents all the aspects of a real application which are relevant to communications. An application entity is identified by a globally unique name ("globally" is used here in its literal sense, i.e. worldwide), the application process title (APT). Every application entity represents precisely one application process. One application process can encompass several application entities.
application entity qualifier (AEQ)
According to the OSI standard, the application entity qualifier identifies a service access point within an application.
application entity title
An application entity title is a globally unique name for an application entity ("globally" is used here in its literal sense, i.e. worldwide). It is made up of the application process title (APT) of the relevant application process and the application entity qualifier (AEQ).
application process
The application process represents an application in the OSI reference model. It is uniquely identified globally by the application process title (APT).
application process title (APT)
According to the OSI standard, the application process title is used for the unique identification of applications on a global (i.e. worldwide) basis.
association (OSI)
An association is a communication relationship between two application entitys.
application server
An application server (Java EE Server) is the basic component of an EJB architecture. The application server offers the services of enterprise applications to the EJB clients.
application server cluster
Cluster consisting of multiple application servers. In such a cluster, n instances of the application server can be assigned to m proxy instances.
asynchronous job
Job carried out by the job receiver at a later time. Processing is carried out independently of the job submitter.
asynchronous service
A service in UTM which processes a background job.
authentication
See system access control.
authorization
See data access control.
Basic Communication Access Method (BCAM)
BCAM forms the basis for the data communication system for BS2000 hosts.
basic conversation
A basic conversation is a type of APPC conversation in which the CICS application must add control bytes to the application data for transmission to the partner.
BCAM
see Basic Communication Access Method (BCAM).
BCAM trace
The logging of all connection-oriented activities within the proxy container is called BCAM trace.
BeanConnect Management Console
The BeanConnect Management Console is the tool for administering and configuring the BeanConnect components. It provides a graphical user interface and a command line interface.
BeanConnect proxy
A BeanConnect proxy is the BeanConnect component which communicates with the resource adapter within the application server as well as with the EIS. A BeanConnect proxy consists of a proxy container based on the transaction monitor openUTM.
During communication with an EIS partner of type CICS, a BeanConnect proxy consists additionally of an openUTM-LU62 Gateway and the communication service.
BeanConnect proxy container
The BeanConnect proxy container is the core of the BeanConnect proxy. The proxy container comprises the definitions of the objects used for outbound communication and inbound communication and the configuration of the communication partner (resource adapter and EIS partners).
BeanConnect resource adapter
The BeanConnect resource adapter is the BeanConnect component that is running on the application server and that implements the JCA-compliant interfaces. In the case of outbound communication via the OSI-TP protocol and in the case of outbound communication, the BeanConnect proxy is additionally needed for the connection between the EIS and the resource adapter.
CCI
See common client interface (CCI).
CICS
See Customer Information Control System (CICS).
cluster
A cluster is a number of networked computers that are seen as a single computer from the outside for many purposes. As a rule, the individual elements in a cluster are connected to each other over a fast network. The aim of establishing a cluster is to increase CPU capacity or availability.
See also application server cluster and proxy cluster.
CMX
See Communications Manager for Unix Systems (CMX).
common client interface (CCI)
CCI is a component of the Java EE connector architecture (JCA) and provides an EIS independent client API for accessing EISs.
communication service
Service required by a BeanConnect proxy for communication between the proxy container and a CICS partner. The communication service works directly with the openUTM-LU62 Gateway and is provided by the IBM Communications Server or SNAP-IX independently of the platform. SNAP-IX or the IBM Communications Server represent software prerequisites for BeanConnect if communication is to be performed with CICS partners. However, they are not supplied with BeanConnect.
Communications Manager for Unix Systems (CMX)
CMX is the basic product for communication software running on operating systems like Solaris. A license is required for its use.
component
Reusable software unit with standardized interfaces that can usually be manipulated in a development environment.
configuration property
Configuration properties are used to configure the resource adapter. A configuration property is set in a configuration file by means of XML tags.
connection factory
A connection factory is used by an EJB of an application server to open a connection to an external data source (EIS). The connection factory is provided when the application server is started in the JNDI name directory.
connection pooling
Connection pooling manages connections that are expensive to create and destroy. Connection pooling is used to improve scalability and performance in an application environment.
connector architecture
See Java EE connector architecture (JCA).
container.properties
Configuration file of a BeanConnect proxy. Many of the changes you make using the BeanConnect Management Console are saved in the container.properties file.
contention winner / contention loser
Each connection between two partners is managed by one of the partners. This partner is called the contention winner, while the other partner is referred to as the contention loser. Jobs can be initiated by both partners. If both partners submit a job at the same time, priority is given to the contention winner.
control point (CP)
The control point is responsible for managing the end node and its resources in an APPN (advanced peer-to-peer-networking) network.
conversation
A conversation is a logical connection between two transaction programs in an LU6.2 session. A conversation begins with Allocate and ends with Deallocate. A conversation allocates a session for its entire life and locks out all other users.
CP
See control point (CP).
Customer Information Control System (CICS)
CICS is the IBM transaction monitor. CICS is available for various platforms such as CICS/ESA for the z/OS operating system. An OLTP application based on CICS is called a CICS application.
data access control
The application server checks whether a communication partner/client is authorized to access a particular business method. The access rights are set as part of the configuration.
data link control (DLC)
Data link control is the service provided by the data link layer. The data link layer corresponds to layer 2 of the Open Systems Interconnection model for network communication (LAN, Enterprise Extender for example).
deployment descriptor
A deployment descriptor is a file in XML format that is used for the deployment of EJBs or resource adapters. A deployment descriptor provides configuration information that is not contained in the EJB code or the resource adapter code.
dialog service
Service which processes a job interactively (synchronously) in conjunction with the job submitter. A dialog service processes dialog messages received from the job submitter and generates dialog messages to be sent to the job submitter. A dialog service comprises at least one transaction. In general for openUTM, a dialog service encompasses at least one dialog step.
dialog step
A dialog step starts when a dialog message is received by the UTM application. It ends when the UTM application responds.
distributed program link (DPL)
DPL is a program interface that enables a CICS program to call another CICS program which may reside on a remote CICS system. DPL is like calling a subprogram.
distributed transaction
See global transaction.
distributed transaction processing (DTP)
with UTM partners:
Transaction-oriented distributed processing with global transactions. Distributedprocessing means that jobs are processed by several different applications.
with CICS partners:
Distributed transaction processing is a programming interface that enables a CICS transaction to invoke another CICS transaction (possibly in another CICS system).DTP supports the handling of global transactions. It is similar to the client-server programming model.
DLC
See data link control (DLC).
DPL
See distributed program link (DPL).
DTP
See distributed transaction processing (DTP).
EIS
See Enterprise Information System (EIS).
EJB
See Enterprise JavaBeans (EJB).
EJB container
Runtime environment for EJB components. It is embedded in an application server.
Enterprise Information System (EIS)
This is a term used to describe external data sources such as ERP systems (Enterprise Resource Planning systems such as SAP), OLTP applications such as UTMCICS applications or database systems such as Oracle DB, SESAM, UDS.
An EIS that communicates with the application server by means of BeanConnect is called an EIS partner.
Enterprise JavaBeans (EJB)
Enterprise JavaBeansTM (EJB) is a component technology that allows the development of cross-platform, multitier, distributed server applications within a modular architecture.
function unit commit
A function group in the OSI-TP protocol that is required to create distributed transactions. Whether or not the functional unit commit may be used is negotiated when an association is set up between the two partners. OSI-TP dialogs can run with or without the functional unit commit in an association in which the functional unit commit was agreed to. An association is a communication relationship between two applications.
function unit handshake
A function group in the OSI-TP protocol that can be used by the communication partners to coordinate the processing of a dialog at application level. This function makes it possible to request processing confirmations and send positive or negative confirmations. No inter-application transaction management is linked to this function.
global transaction
A global transaction is a transaction extending over more than one application.
IBM Communications Server
IBM Communications Server is an IBM product that connects applications in SNA networks with applications in TCP/IP networks. In BeanConnect, the IBM Communications Server is used for communication between a BeanConnect proxy and a CICS partner application using the LU6.2 protocol on Linux and Windows systems.
IDE
Integrated Development Environment. In the case of BeanConnect, this is the open source development environment NetBeans IDE.
inbound communication
Inbound communication is communication from an EIS to a Java EE application server.
inbound message endpoint
An inbound message endpoint is an endpoint of the inbound communication within the Java EE application server.
For each inbound message endpoint in the application server, an identically named inbound message endpoint must be configured in the BeanConnect proxy by means of the BeanConnect Management Console. A BeanConnect proxy may have several endpoints.
inbound service
Inbound services represent the objects addressed by the EIS partners during inbound communication. The inbound services known to the Management Console are defined implicitly by the inbound message endpoints.
Exactly one inbound message endpoint is assigned to each inbound service.
inbound user
An inbound user is a user name and password that can be delivered from the EIS to the BeanConnect proxy during inbound communication.
J2EE TM
Old name for Java EE.
Java EE
Java Platform, Enterprise Edition, abbreviated to Java EE (previously J2EE), is the specification of a software architecture for the transaction-based execution of applications programmed in Java.
Java EE connector architecture (JCA)
Java EE connector architecture
Defines a standard architecture for connecting the Java EE platform to heterogeneous Enterprise Information Systems.
Java Development Kit (JDK)
Standard development environment from OracleTM for developing applications written in Java.
Java Naming and Directory Interface (JNDI)
JNDI is a standard Java extension that provides a uniform API for accessing the directory and naming services of different vendors.
JCA
See Java EE connector architecture (JCA).
JDK
See Java Development Kit (JDK).
JMX
Java Management Extensions (JMX) is a specification developed by the Java Community Process (JSR-3) for managing and monitoring Java applications.
JMX client
Client that can access a JMX server and make use of its services. In BeanConnect, the Management Console represents the JMX client implementation.
JMX server
Instance in a Java application that provides services for monitoring the application. In a BeanConnect environment, the application server implements the JMX server functionality.
JNDI name
Name of a Java object in a programming environment in which the Java Naming and Directory Interface (JNDI) is used.
job-receiving service
A job-receiving service is a service started by a job-submitting service of another server application.
job-submitting service
A job-submitting service is a service which requests another service from a different server application (job-receiving service) in order to process a job.
Jython
Jython (formerly JPython) is a pure Java implementation of the Python programming language and therefore makes it possible to execute Python programs on all Java platforms. Python is a universal, usually interpreted, highlevel programming language.
KDCA
Default name of the KDCFILE.
KDCDEF
UTM generation tool resp. generation tool of the BeanConnect proxy container.
KDCFILE
Configuration file of a BeanConnect proxy container. The file contains data required by the proxy container for execution. The file is created with the generation tool KDCDEF.
with UTM partners:
Configuration file of an UTM partner application. The file contains data required by the UTM partner application for execution. The file is created with the UTM generation tool KDCDEF.
KDCS
Universal UTM program interface compliant with the national DIN 66 265 standard and which includes some extensions. KDCS (compatible data communications interface) allows dialog services to be created, for instance, and provides calls for distributed processing. In BeanConnect, KDCS is only used as an internal interface.
Log4j
BeanConnect uses the software product Log4j to provide trace and logging functionality. Log4j is a component of the Apache Jakarta project. Log4j provides interfaces for logging information (runtime information, trace records etc.) and for configuring the log output.
Log4j is configured by means of the BeanConnect Management Console.
logger
A logger is a Log4j message source. Programs that must write logging information retrieve logger objects with predefined names from Log4j and output their messages via these objects. The destination to which Log4j sends the messages is transparent to the program.
logical unit (LU)
A logical unit is a logical virtual port which provides a user with access to network services in an SNA network. The logical unit corresponds with the control point (CP) and a partner logical unit representing, for example, a user program.
LU
See logical unit (LU).
LU6.2 protocol
The LU6.2 protocol is a component of the IBM network. LU6.2 defines methods for program-to-program communication between applications on different computers.
Management Console Command Line Interface (MC-CLI)
Management Console command line interface (MC-CLI)
Set of Jython which can be used to start BeanConnect Management Console functions from a Java script.
mapped conversation
A mapped conversation is a type of APPCconversation in which the data passed to and received from another APPC application is simply user data. The user is not concerned with the internal data formats demanded by the architecture.
MBean
Managed Bean which represents a resource of a JMX server.
MC-CLI
Command Line Interface of the Management Console.
MC-CLI recording
Recording of Management Console actions The recordings are created in the form of MC-CLI functions.
MC-CmdHandler
The MC-CmdHandler is a BeanConnect component which is required in order to administer another, remote BeanConnect component using the BeanConnect Management Console. In this case, the function scope is the same as when administering a local component.
message
A message is a data packet that consists of a header and a body. The header contains addressing data, the network routing and possibly data on the message format. The body contains the actual message in the form of business data or system messages.
message-driven bean
A message-driven bean is a component of the Enterprise JavaBeans specification from OracleTM.
Message-driven beans are beans for the reception of messages. Messagedriven beans are only called by the EJB container and therefore have no home or remote interfaces.
message endpoint
message endpoint
A message endpoint is a message-driven bean application deployed in an application server.
message listener
message listener
Message consumer. The message listener object is sent messages as soon as they become available. Message-driven beans are message listeners.
message listener interface
message listener interface
Interface that a message listener must implement. Inbound resource adapters provide specific message listener interfaces which message listeners must implement if they are to consume messages from this resource adapter.
mode name
The mode name is a symbolic name for a list of session properties and is required for all interconnection requests over SNA. The mode name is used by the initiator of a session.
multiple resource adapter mode
Configuration in which a BeanConnect proxy interacts with multiple resource adapters. These resource adapters may be located on different application servers.
multi-step transaction
A multi-step transaction is a transaction which comprises more than one dialog step.
naming
Mapping of names to object references. The mapping is usually performed via a naming service.
network name
A network name is a name identifying an SNA network and is a component of the logical unit name, see logical unit (LU).
OLTP message-driven bean
OLTP message-driven beans are EJBs that receive and process jobs from OLTP applications (UTM/CICS applications). The OLTP application addresses the OLTP message-driven bean via an inbound message endpoint.
openUTM
Transaction monitor from Fujitsu Siemens Computers and basic component of the BeanConnect proxy container.
openUTM-LU62 Gateway
openUTM-LU62 is a BeanConnect proxy component which acts as the interconnection with partner applications supporting the SNA protocol LU6.2, particularly with CICS applications.
Oracle WebLogic Server
Java EE 6-compliant application server from Oracle Corporation.
OSI-LPAP partner
OSI-LPAP partners are the addresses of the OSI-TP partners generated in the BeanConnect proxy container. In the case of distributed processing via the OSI-TP protocol, an OSI-LPAP partner for each partner application must be configured in the proxy container. In the case of UTM partners, the OSI-LPAP partner in the proxy container represents the partner application and in the case of CICS partners, it mirrors the openUTM-LU62 Gateway instance. During communication, the partner application is addressed by the name of the assigned OSI-LPAP partner and not by the application name or address.
OSI reference model
The OSI reference model provides a framework for standardizing communications in open systems. ISO, the International Organization for Standardization, described this model in the ISO IS7498 standard. The OSI reference model divides the necessary functions for system communication into seven logical layers. These layers have clearly defined interfaces to the neighboring layers.
OSI-TP
Open System Interconnection Transaction Processing.
A communication protocol defined by ISO for distributed transaction processing. A partner of an application that communicates with the BeanConnect proxy container via the OSI-TP protocol is called an OSI-TP partner.In the case of UTM partners this is the EIS partner and in the case of CICS partners it is the openUTM-LU62 Gateway.With CICS, this protocol is used for communication between the BeanConnect proxy container and the openUTM-LU62 Gateway.
OSS
OSI Session Service
OSS forms the basis for OSI-TP data communication in the BeanConnect proxy container.
outbound communication
Outbound communication is communication from the Java EEapplication server to the EIS.
outbound communication endpoint
An outbound communication endpoint is a symbolic name representing a service of the partner EIS.
outbound service
An outbound service object describes a service (transaction code) inside the EIS partner for outbound communication.
PCMX
The basis for communication software which runs on the Solaris, Linux and Windows operating systems.
physical unit (PU)
Every node in an SNA network contains a physical unit as an addressable SNA instance. Before two logical units (LUs) can open a communication relationship in the SNA network, a communication relationship must first be opened between the corresponding PUs.
proxy cluster
Cluster consisting of more than one BeanConnect proxy and which is administered via the BeanConnect Management Console.
proxy container
See BeanConnect proxy container.
PU
See physical unit (PU).
resource adapter
Resource adapters (also referred to as connectors) connect the application server to an EIS, see also BeanConnect resource adapter.
resource manager
Resource managers (RMs) manage data resources. Database systems are examples of resource managers.
RFC1006
A protocol defined by the IETF (Internet Engineering Task Force) belonging to the TCP/IP family that implements the ISO transport services (transport class 0) based on TCP/IP.
schema
see XML Schema.
service
Services process the jobs that are sent to a server application. Services can be requested by clients or by other servers. A service of an UTM application or of a CICS application comprises one or more transactions. The first transaction is called with the service TAC or transaction program name. With openUTM, there are two types of services: dialog services and asynchronous services. openUTM provides the program units of a service with common data areas.
service access point
In the OSI reference model, a layer has access to the services of the layer below at the service access point. In the local system, the service access point is identified by a selector. During communication, the UTM application links up to a service access point. A connection is established between two service access points.
session
A session is understood to be a communication relationship between two LUs, more generally between two addressable SNA instances.
single-step transaction
transaction which encompasses precisely one dialog step.
SNA
See Systems Network Architecture (SNA).
SNAP-IX
SNAP-IX is a product from Data Connection that connects applications in SNA networks with applications in TCP/IP networks.
In BeanConnect, SNAP-IX is used for communication between a BeanConnect proxy and a CICS partner application using the LU6.2 protocolon Solaris systems.
synchronization level (sync-level)
Designation in LU6.2 that characterizes the transaction security for distributed processing:
For sync-level 0 (none), only net data and error messages may be sent. Acknowledgments are not allowed.
For sync-level 1 (confirm), simple acknowledgments may also be sent in addition to net data and error messages.
For sync-level 2 (sync point), full transaction security is activated for distributed transactions.
synchronization point (sync point)
A logical point within the flow of a distributed process at which the common resources are brought to a defined state. The term "end of transaction" is used instead in openUTM.
system access control
This involves the application server checking whether a user ID is authorized to work with the application server.
Systems Network Architecture (SNA)
SNA is the designation for a series of communication protocols defined by IBM.
TAC
See transaction code (TAC).
transaction
Processing section within a service which has the ACID properties. If, during the course of a transaction, changes are made to the application information, they are either made consistently and in their entirety or not at all (all-or-nothing rule). The end of the transaction forms a synchronization point (sync point).
transaction code (TAC)
Name by means of which a service of an UTM application can be called.
user ID
Identifier for a user defined in the configuration for the UTM / CICS application (with an optional password for system access control) and to whom special data access rights (data access control) have been assigned. A client must specify this ID (and any password which has been assigned) when signing on to the UTM application/CICS application.
USP
See UTM socket protocol (USP).
UTM
See openUTM.
UTM application
An OLTP application based on the transaction monitor openUTM of Fujitsu Technology Solutions.
UTM socket protocol (USP)
A protocol used by UTM partner applications to convert byte streams into messages that require the TCP/IP transport system
Virtual Telecommunications Access Method (VTAM)
The component in an IBM host system that is responsible for remote data processing.
Web Service Description Language (WSDL)
The Web Services Description Language (WSDL) defines a platform, programming language and protocol-independent XML specification for the description of network services (Web services) for message exchange.
XML
XML (eXtensible Markup Language) is a metalanguage standardized by W3C (WWW Consortium) in which the interchange formats for data and the associated information can be defined.
XML Schema
XML Schema is a W3C recommendation for the definition of XML document structures. The structure is described in the form of an XML document. In addition, a large number of data types are supported.