- A
- Activity
- A complete, functional unit of processing within an orchestration.
Activities include flow-control (logic) activities; data activities
to facilitate consumption and transmission of data; and activities
that enable integration with database systems, enterprise systems,
Web servers, email servers, and other systems. An orchestration comprises
a series of activities.
- Assets
- Supplemental configuration files, scripts, or other materials
associated with a specific activity. For example, the buffer table
scripts created for a database insert activity are assets. Assets
are controlled by the Web Management Console (WMC). Access privileges
to assets can be given to users beyond the users of the WMC. For example,
DBAs can be given privileges to the assets associated with a database
activity so that they can create the required tables or triggers.
- B
- Buffer table
- An auxiliary table used in conjunction with various database activities,
such as the single-table insert, update, or delete database activities.
When you configure one of the database DML (data manipulation language)
activities, Studio generates a SQL script that can be used to create
the appropriate trigger on the database table; the buffer table gets
populated when the triggering event (INSERT, UPDATE, DELETE) occurs.
The buffer table provides the means to capture database changes and
initiate processing by the orchestration.
- C
- Command-line interface
- A text-based alternative to the Web Management Console (WMC) for
configuring, managing, and querying an Integration Appliance.
- Control table
- A database table that facilitates using database endpoints in
integrations. As it does with buffer tables, Studio generates scripts
to create control tables that can be used to ensure that inserts,
updates, and deletes to specific tables occur once and only once.
- Copy parameters
- Copy creates new default orchestration variables that match the
output from the parameters.
- D
- Deploy
- Create an instance of an integration project (instantiate) on
an Integration Appliance.
- Document
- Any of the XML Schema files, DTDs, and other configuration files
that comprise integration projects.
- Dynamic delimiter
- A delimiter that is obtained from within the fields of the message
itself, such as an HL7 PID (patient ID) message header that denotes
the beginning of a new record in a file containing a batch of electronic
health records.
- E
- Empty Placeholder
- Appears in activities that have multiple branches as an initial
placeholder for the activities in that branch. Dropping other activities
on this icon removes it.
- Endpoint
- Represents the properties of an external system, such as a database
server, FTP server, email system, or enterprise application that is
either the source of data to the Integration Appliance or the target
of processing by the Integration Appliance.
- F
- For Each
- A function that iterates over a message structure.
- Flat File
- A file containing non-XML data. Flat Files are typically of two
types: delimited, in which a comma, tab, white space, or other delimiter
is used to separate variable-length fields and records; or positional,
in which fields and records have a fixed width.
- Flat File Schema
Defines how to interpret a specific set of Flat Files. WebSphere® Cast Iron Studio
creates Flat File Schema (XML Schema) based on the configuration you
define in the Flat File Schema Editor. A Flat File Schema is used
by the Read Flat File activity to convert a
source Flat File into XML.
- Function
- String, mathematical, and miscellaneous functions provided by
Studio that you can use in defining processing in your orchestrations.
In addition to the pre-built functions, Studio lets you build your
own custom functions and add lookup tables.
- I
- Integration project
- The various inputs, outputs (endpoints), mapping and schema definitions
(transformations, message formats), orchestrations, and configuration
information that comprise an integration solution as designed in Studio
and deployed to the Integration Appliance.
- J
- Job
- A specific run-time instance of an orchestration.
- M
- Map
- A component that lets you bind input parameters to variables,
and variables to the orchestration. Many Studio activities contain
embedded maps that you must configure at design time, in the context
of an orchestration, to define how actual parameters should map to
variables, and how the variables should be processed in the orchestration.
In addition to the embedded activity maps, Studio has a stand-alone
Map Variables activity that can be used to
bind any type of input and output to the orchestration
- N
- Node
- All data input to or output from the Integration Appliance is
materialized in Studio as a series of nodes, as in a tree-like, hierarchical
structure. In many cases, the nodes represent the structure and content
of an XML document, but in many cases they don't (e.g., rows
in a database table are displayed as nodes). Nodes in Studio convey
information about structure; the type of content that can be supported;
or additional characteristics of the data.
- Notification policy
- Applies across an entire orchestration. Rules are based on event
levels from 0 (no logging) to 9 for complete logging information.
- O
- Orchestration
- The specific sequence of processing activities (such as data mapping,
transformation, and control logic activities), endpoints, and data
types defined and configured using Studio and deployed to run on the
Integration Appliance.
- P
- Parameter
- A value passed to an activity or to an orchestration. For example,
Filename and data are two of the parameters that can be passed from
an FTP endpoint to an orchestration.
- Parameterized query
- A database SQL statement that contains input or output database
parameters. The Execute Query activity supports parameterized
queries.
- Parse
- The converse of serialize. To convert to constituent pieces according
to some established rules.
- Pick
- An activity that chooses from two or more alternatives. Typically
used to start an orchestration, the Pick activity can support
either synchronous or asynchronous messaging.
- Project
- An integration project defined and created using WebSphere Cast Iron Studio. Each project
has a properties file (filename.sp3) and several additional metadata
files and folders that comprise all integration elements - orchestrations,
endpoints, XML schemas, flat files - and their specific configuration
(variables, parameters)
- Publish
- Copy all project files from Studio to an Integration Appliance
or to an intermediate staging area, such as a shared directory on
a file server, for subsequent runtime configuration and deployment
to a specific environment. The Publish process encompasses validating
the project; creating a .par file of project configuration documents;
and sending the package to the Integration Appliance specified.
- R
- Raw message
- The configuration that defines the character encoding for raw
messages
- Record identifier
- A special field that delimits records in certain types of flat
files, such as EDI (electronic data interchange) or HL7 (Health Level
7) files. For example, an HL7 PID (patient ID) number is a record
identifier.
- Repetition delimiters
- A delimiter in a flat file that is used when the data lacks a
unique value, such as record ID, to distinguish one record from another.
- Replace
- Appears in activity branches as an initial placeholder for the
endpoint activity to receive a message for that branch. Dropping a Receive
endpoint activity on this icon removes it.
- Reply
- Sends an acknowledgement when it receives a message.
- Repository
- Persistent storage for various types of data. WebSphere Cast Iron Appliance has a configuration
repository and a message repository.
- S
- Serialize
- The converse of parse. Serialization assumes that the data is
in XML format
- Stored procedure
- A functional code unit that resides in a database and is started
explicitly by name. Stored procedures can be used to populate buffer
tables when specific insert, update, or delete activities occur on
a particular database table.
- System store
- A repository containing Appliance configuration information. Same
as configuration repository.
- T
- Terminate
- Stops orchestration processing.
- Toolbox
- The five-tab-set of Project, Activities, Variables, Functions,
and Verify available in the right-hand corner of Studio. These tabs
provide access to all the entities you need to create new projects,
create new orchestrations within projects, and develop the processing
logic.
- Trigger
- A type of database stored procedure that is called implicitly
when a triggering event occurs such as an INSERT, UPDATE, or DELETE
on a table.
- V
- Variable
- Used to pass data values processed by an orchestration. Variables
are used by maps to identify the source and target. Some Activities
create variables automatically.
- W
- WebSphere Cast Iron
Studio
- An integrated development environment (IDE) for creating, configuring,
and publishing integration projects and the orchestrations they comprise.
Studio projects run on the WebSphere Cast
Iron Appliance.
- While Loop
- Initiates and continually processes any children activities for
as long as a specified condition is true.