action
A single Action Diagram statement.
action block
A stand-alone action diagram that other diagrams use. It defines the logic of an algorithm or specifies logic that is common to many action diagrams.
Action Diagram (AD)
A set of view definitions and procedural instructions that use the language and constructs provided by CA Gen for the purpose of implementing a procedure step, elementary process, or action block. An Action Diagram is an ordered collection of actions, which define the logic of an elementary process, procedure step, or action block.
ActiveX\COM Proxy—see COM Proxy
AD—see Action Diagram
AEF—see Application Execution Facility
AEFAD—see Application Execution Facility Asynchronous Daemon
AEFC—see Application Execution Facility Client
AEFUF—see Application Execution Facility User Funnel
Application Execution Facility (AEF)
A CA Gen application environment that supports interactively loading and execution of generated applications in a non-MVS (CICS, IMS or TSO) environment.
Application Execution Facility Client (AEFC)
A CA Gen application that provides presentation of IBM's 3270 data streams. AEFC is a 3270 emulator that interfaces with ASCII terminals. The ASCII terminals can either be directly connected to a host system or provided using a TCP/IP Telnet ASCII terminal emulator. The AEFC software handles the presentation of 3270 messages sent to or received from a CA Gen block mode application.
Application Execution Facility Asynchronous Daemon (AEFAD)
A CA Gen application that provides a facility to interactively load and execute generated applications. The AEFAD supports the execution of block mode and Distributed Processing Server (DPS) applications. The AEFAD is a TCP/IP socket application. It does not spawn a unique process for each connected user, rather it manages the messages coming and going to all connected users. The AEFAD multiplexes messages to/from multiple clients in an independent and concurrent manner.
Application Execution Facility User Funnel (AEFUF)
A CA Gen application that multiplexes AEFC and AEFAD connections onto one TCP/IP connection. AEFUF manages many client connections providing a critical scaling component funneling many user messages to a target AEFAD environment. Distributed Processing Client (DPC) applications must connect to an AEFUF.
CFB—see Common Format Buffer
Client Manager (CM)
A workstation application, offered by CA Gen, to service cooperative flow requests initiated by one or more CA Gen generated GUI applications operating on the desktop.
Common Format Buffer (CFB)
A dynamically constructed, in memory storage area use by CA Gen runtime during the processing of a cooperative flow. The CFB is an encoded buffer used to exchange the import and export views between a Distributed Processing Client (DPC) and Distributed Processing Server (DPS). The CFB is designed to provide a platform independent byte stream transferred between a DPC and a DPS. The CA Gen runtime will make use of a CFB based on the application's execution environment and selected transport type.
Communications Interface (COMMINF)
A set of "internal use" API's and associated dynamically loaded implementations, used by CA Gen runtime, to process a cooperative flow between a Distributed Processing Client (DPC) and Distributed Processing Server (DPS). Collectively COMMIF refers to the set of CoopFlow and MsgObj implementations offered by CA Gen.
Communications Interface (CIF)
A dynamically loaded software layer used by CA Gen Client Manager and Communications Bridge to handle the outbound communication with a target server environment. The Client Manager provides CPI/C (LU 6.2) and TCP/IP support, while the Communications Bridge provides CPI/C (LU 6.2), CICS ECI and TCP/IP.
Communications Bridge (Comm. Bridge)
A gateway application offered by CA Gen to concurrently service cooperative flow requests initiated from a variety of CA Gen distributed Processing Client (DPC) applications that are executing on one or more client workstations.
Common System Utilities (CSU)
A CA Gen runtime layer that exposes a common interface to a set of platform specific operations. For example, the operations provided within the CSU layer include tracing, locking, and dynamic loading of other runtime libraries. CSU is implemented and used within CA Gen's C/C++, Java, and .NET runtimes.
COM Proxy
(1) A CA Gen product that supports the generation of a COM object that can be used by non-CA Gen applications to flow to a procedure step that is packaged within a CA Gen generated Distributed Processing Server (DSP) application. (2) The generated COM code that provides a COM automation interface to a specific server procedure step. A COM proxy can be used by Web applications with Active Server Pages or any OLE-enabled client to access CA Gen generated Distributed Processing Server (DSP) applications.
cooperative processing
A term referring to client/server applications and their packaging. A cooperative application has a client component and a server component that work together across platforms. Cooperative processing is a synonym for Distributed Processing. See Distributed Processing (DP) Application.
cooperative flow
A type of flow used within CA Gen applications that facilitate the remote execution of a Distributed Processing Server (DPS) application. Cooperative flows result from modeling a dialog flow or PStep Use that targets a PStep that is packaged in a separately packaged server manager.
CoopFlow (Cooperative Flow)
A component of CA Gen's ODC architecture. CoopFlow is a generic term used to identify the software load modules that implement the various transport mechanisms supported within CA Gen (TCP/IP, MQSeries, Client Manager, ECI, Web Services, Tuxedo, JavaRMI). See Open Distributed Computing (ODC).
CSU—see Common System Utilities
dialog flows
A flow control technique used to transfer control, and possibly data, between procedure steps in the same CA Gen business system (internal flows) or between procedure steps within a different business system (external flows). There are two types of dialog flows; links and transfers.
Distributed Processing (DP) Application
A term used to describe a type of client/server application characterized by its processing being divided into two or more separate application parts. Each application part has a specific role in the overall application. The execution of the application is "distributed" amongst its various application parts. Some parts serve as Distributed Processing Clients (DPC), others serve as Distributed Processing Servers (DPS). Each application part is implemented in a procedure step and is physically packaged into a separate load module. In most cases each load module making up the distributed processing application is physically located on more than one computer.
Distributed Processing Client (DPC)
A generic term that describes the Distributed Processing application component that makes a request of the Distributed Processing Server (DPS) component. CA Gen supports many types of DPC applications (GUI Clients, Web Clients, hand written applications by way of a Gen Proxy Client, Distributed Processing Server (DPS)).
Distributed Processing Server (DPS)
A generic term that describes the generated Distributed Processing application component that processes cooperative flow requests initiated from Distributed Processing Client (DPC) applications. CA Gen supports many target environments capable of hosting a generated DPS application (for example, CICS, IMS, EJB, MQSeries, DCE, Tuxedo, Transaction Enabler).
DPC—see Distributed Processing Client
DPS—see Distributed Processing Server
elementary process
The smallest unit of processing activity that has meaning to a user such that when it is complete it leaves the associated business processing in a consistent state. For every elementary process, there is an associated action diagram.
export view
A type of view, within a distributed processing application, that contains the collection of attributes that are returned from an execution of a Distributed Processing Server (DPS).
Graphical User Interface (GUI)
A graphics based user interface that incorporates icons, pull-down menus and a mouse. GUI's have become the preferred way users interface with most computer systems. Some major GUI styles include Windows, Macintosh, Motif, and Web browser presentation of HTML. CA Gen supports Windows and Web Browser as graphics based user interfaces.
GUI—see Graphical User Interface
GUI client
A type of generated CA Gen Distributed Processing Client (DPC) application that operates under the control of a generated Window Manager. This type of application contains one or more cooperative flow requests that target a procedure step that are packaged in one or more generated Distributed Processing Server (DPS) applications.
import view
A view, within a distributed processing application, that contains the collection of attributes that are provided as input to an execution of a Distributed Processing Server (DPS).
Java Proxy
(1) A CA Gen product that supports the generation of two Java-based interfaces that can be use by non-CA Gen Java applets, applications, servlets, and EJB's to flow to a procedure step that is packaged within a CA Gen generated Distributed Processing Server (DSP) application. (2) The generated Java-based interface code that provides the Java interface to a specific server procedure step.
.jvf file
A Tuxedo Jolt file containing the CA Gen view definitions to be processed by its associated generated Tuxedo server. This file is the Java equivalent to the .tvf file used by the generated C Tuxedo servers.
Load Module
(1) a type of software file that is capable of being brought into, or "loaded" into, a computer's memory area. Load modules can be executed as programs. Others contain data. Executable load modules consist of an assembly of machine instructions and implement some logic. (2) In CA Gen, load module is a general term to indicate one or more procedure steps combined (packaged) into an identifiable unit. After being generated and installed, a load module is an executable file. The process for defining the packaging is known as load module packaging, or packaging for short.
Message Object (MsgObj)
A component of CA Gen's ODC architecture. The MsgObj is responsible for creating and parsing the message buffer being exchanged as part of the cooperative flow. MsgObj is a generic term used to identify the software load modules that implement the various types of data representation techniques employed as part of a cooperative flow (CA Gen's CFB, Tuxedo's View32,). See Open Distributed Computing (ODC).
MsgObj—see Message Object
Multi-Instance Client Manager
A user-modified version of CA Gen's Client Manager application. The user modification is in the form of a user exit. In a multi-user system, such as Windows 2000 with Terminal Service enabled, the user exit lets a customer implement a technique that distinguishes one user from another. Typically, the implementation techniques make use of the logon user-id or session-id associated with a specific instance of a user. After the Multi-Instance Client Manager has been customized, multiple copies of the Client Manager application can execute with a multi-user system. In a multi-user system, the Multi-Instance Client Manager for a given user behaves the same as the single user version of the Client Manager.
Open Distributed Computing (ODC)
A CA Gen architecture used to externalize, and normalize, the processing by which CA Gen runtimes service cooperative flows. ODC exposes a common API. This API is used by the various runtimes responsible for processing cooperative flows. Using this normalized API lets the runtimes perform cooperative flows without concern for the underlying middleware or communications mechanism being employed to service cooperative flows.
ODC is an object-oriented implementation that separates the processing of a cooperative flow into two main components. These components are known as the MsgObj (Message Object) and the CoopFlow (cooperative flow). The MsgObj is responsible for creating and parsing the message buffer being exchanged as part of the cooperative flow. The CoopFlow is responsible for handling the communications between a DPC and DPS. CA Gen supports a variety of middleware and transport mechanisms. Each cooperative flow determines which MsgObj and CoopFlow will be used to process a flow request. CA Gen supplies different MsgObj and CoopFlow implementations to support the variety of supported middleware and transport mechanisms.
Procedure
A method by which one or more elementary processes is carried out using a specific implementation technique.
PStep—see Procedure Step
Procedure Step (PStep)
A subdivision of a procedure that performs a discrete and definable amount of work necessary to complete a procedure. Each procedure step is contained within a procedure. Procedures can be implemented using multiple PSteps.
proxy
A CA Gen supported coding interface that enables a non-CA Gen application to flow to a CA Gen Distributed Processing Server (DPS). Proxies are generated interfaces and runtimes. CA Gen can generate proxies for use in the following implementation technologies; C/C++ programs, applications capable of using COM objects, applications that use client JavaBeans, applications that use Application JavaBeans, and applications that use .NET.
runtime
A term used to describe those software components that are logically part of a CA Gen application but are not part of the application's generated code. Some of these components are physically linked to the application, other are dynamically loaded depending on the execution characteristics of the application (middleware runtime). Runtime can also refer to the execution environments that support the execution of the application (Transaction Enabler, Tuxedo, CICS, IMS, MQSeries).
server manager
A CA Gen non-window load module that contains one or more PSteps. A Server Manager PStep is the target processing of a cooperative flow request. Server Manager is a synonym for Distributed Processing Server (DPS).
server-to-server flow
A server-to-server flow is a cooperative flow that is initiated from within a PStep that is packaged as part of a Distributed Processing Server (DPS) application.
services table
A generated table that is part of the ODC architecture. The Services table contains transport specific data for each TranEntry record.
target server
A term that refers to the Distributed Processing Server (DPS) applications involved in a given cooperative flow. It refers to the server portion of a client/server request. Target server can be used to refer to the physical hardware hosting the DPS application.
TE—see Transaction Enabler
T I T D—see CA Gen's CICS MQSeries Transaction Dispatcher
TranEntry Table
A generated table that is part of the ODC architecture. The TranEntry contains entries for each cooperative PStep understood by the application component being generated. Each record of a TranEntry table holds information needed to accomplish one side of a cooperative flow. A DPC will have a TranEntry table that contains a record for each cooperative PStep the DPC can execute. A DPS can have two TranEntry Tables. One table hold TranEntry records for each PStep available for use by a DPC. The other TranEntry table contains entries if the DPS executes any server-to-server flows.
Transaction Enabler (TE)
A collection of software components offered by CA Gen that are collectively known as the Transaction Enabler. The TE is made up of the AEFC, AEFUF, AEFAD, and the Tuxedo Proxy Client.
trancode
Within CA Gen, trancode, is used by the Dialog Manager to manage flows (links, transfers, and external flows) between PSteps.
transport
A generic term that refers to the layer of software that interfaces to the physical network infrastructure.
Tuxedo Proxy Client
A TCP/IP software component offered by CA Gen that serves as a gateway application for cooperative flows targeting Distributed Processing Server (DPS) applications executing under the control of the Tuxedo TP monitor.
User Funnel (UF)
A TCP/IP software component offered by CA Gen that serves as a gateway application for cooperative flows targeting Distributed Processing Server (DPS) applications executing under the control of CA Gen's Asynchronous Daemon. See Application Execution Facility User Funnel (AEFUF).
view
A collection of associated attributes from one or more entity types that are input or output from a business process.
View Matching
A process used by a CA Gen user to map views of the source (action diagrams) to the import view of the destination (action diagram). View matching insures that the destination process or procedure (action diagram) has the data necessary to execute. It maps the export view of the action block to views in the source action diagram to return the results of the destination action block execution.
View Definition File (VDF)
A generated file that contains source code made up of data structures that externally describe the cooperative flows occurring within its associated distributed processing application component. A VDF file is created for each generated window manager (Distributed Processing Client (DPC)) and for each generated server manager (Distributed Processing Server (DPS)). The VDF file is compiled and linked into its respective application component. The VDF file contains a ViewDef table, TranEntry table(s) (for a DPS with server-to-server flows there are two TranEntry tables), and a Services table.
ViewDef Table
A table that is part of the ODC architecture. The ViewDef is a generated table that contains entries for each import view and export view associated with a component of a cooperative flow. The ViewDef is used by the ODC MsgObj to map the attribute values to and from the communications buffer and the associated view storage area within the associated distributed processing application component (either the DPC or DPS).
Window Manager
A generated CA Gen application that operates as a Windows GUI applications. Applications containing a window manager can be packaged as stand-alone Windows application or packaged as a cooperative application. For the latter, the application containing the window manager is capable of containing one or more cooperative flows. A window manager packaged as a cooperative application operates as the Distributed Processing Client (DPC) application when flowing to a remote PStep, where that PStep is located in a Distributed Processing Server (DPS).
.VDF—see View Definition File
|
Copyright © 2014 CA.
All rights reserved.
|
|