Banner Glossary of Terms

Banner Glossary of Terms Definition Term ActionWeb Interactive service that SCT clients use to communicate with SCT and to access business critical ...
Author: Norman Hamilton
22 downloads 2 Views 65KB Size
Banner Glossary of Terms Definition

Term ActionWeb

Interactive service that SCT clients use to communicate with SCT and to access business critical information. The ActionWeb can be used to perform searches and find answers to questions quickly and efficiently. The Banner 7.0 Information Center is located under the Extended Search portion of the ActionWeb.


A component that converts one interface to another. In the context of integration, an adapter adapts an application's protocol to another. Adapters, when used for Enterprise Application Integration (EAI), adapt the application's interface (e.g., SQL using ODBC) to a "messaging interface" (e.g., XML messages transmitted using Message Oriented Middleware (MOM) that complies with the Java Message Service (JMS) specification). SCT has developed an OpenEAI adapter for Banner that is implemented by two separate components: • •

Banner Gateway consumes messages. Banner Messaging Service publishes messages.


Application programming interface. Set of methods through which an application exposes business logic and/or data. For Banner, this refers to the Banner Common Business APIs that all client application types (including messaging clients) must use. These APIs provide consolidated business logic to make Banner "messaging enabled".


Application service provider. An application vendor that provides application functionality to multiple clients by centrally hosting the application instead of deploying instances of the application to each client facility. An example of an ASP is Higher Markets, an eprocurement vendor that focuses on the higher education market.

Banner Business Entity

The smallest, most granular group of information that Banner application clients can independently modify. A Banner business entity is the "noun" (person, place, or thing) on which the business process operates. Business entities are the "pebbles" that support all Banner application client programs. They can be identified by analyzing information on one form or in one block on a form. Examples of business entities include identifier, address, e-mail, and phone.

SCT Banner 7.0 Glossary of Terms

Page 1

Business entity common operations support create, retrieve, update, and delete functions plus business rules validation. Banner Business Entity View

A database view that includes all fields within a Banner business entity. These views are used to construct the consolidated business entity view.

Banner Common Business API

The APIs used in Banner to consolidate business logic and leverage the Banner messaging architecture to message enable Banner. The development of this API is part of the Banner Evolution project.

Banner Gateway

An adapter that consumes OpenEAI Message Protocol messages and invokes the appropriate Banner Common Business API procedures. The Banner Gateway is a multi-threaded Java application built on the OpenEAI foundation software.

Banner Messaging API

An API used within Banner to message enable Banner. The Banner Common Business API procedures use this API to register Banner business entities that are being modified within a transaction. The Banner Messaging API procedures (referred to as Banner Messaging Support) send the modified Banner business entities to the external Banner Messaging Service.

Banner Messaging Service

An adapter that publishes OpenEAI Message Protocol messages. This component receives Banner business entity data from Banner Messaging Support via a remote method invocation. The Banner Messaging Service is a multi-threaded Java application built on the OpenEAI foundation software.


The surface in Oracle Forms on which interface items and prompts are drawn. Canvases are displayed in a window.


Cost-Based Optimizer. An SQL Query optimizer that uses data statistics to identify the query plan with the lowest execution cost. The cost is based on the number of rows in a table, index efficiency, etc. All applications should be converted to use CBO, as RBO will not be available in Oracle 10 and above.


A level of recognition indicating that a third party vendor's product has successfully passed a rigorous certification process managed by SCT. Certification indicates that SCT is confident that the certified integration solution is robust, supports necessary throughput, is functionally correct, and does not cause data integrity concerns. Certification is accomplished through the partnership program.


A formal program in which third party vendors participate with SCT

SCT Banner 7.0 Glossary of Terms

Page 2


to ensure that integration solutions are functionally correct and perform within SCT integration requirements.


A preselected Web page that can automatically send updated information for immediate display on request. A major component of the usability initiative for Banner 7.0 is the channelization of Banner content. Clients who implement the Luminis Platform will be able to use a series of Banner channels to be released with Banner 7.0. These channels will allow constituents to view information and perform business processes without leaving the portal. These channels will take one of the following forms: • • •

A navigational channel links to a Banner form or self-service page. An informational channel (for example, a grades channel for students) displays read-only data. A transactional channel provides the ability to perform a business function (for example, registration or gift processing).


A term previously used within SCT to refer to a specific integration solution with third party vendors. SCT had initial "connections" with WebCT and Blackboard.

Consolidated Business Entity

A grouping of one or more Banner business entities into a largergrained "object". This grouping is used to extract data to the Operational Data Store (ODS). A consolidated business entity may also be represented by an enterprise object.

Consolidated Business Entity View

A database view of a consolidated business entity that supports the data extraction of the entity for population in the Operational Data Store (ODS).


An acronym used to indicate create, retrieve, update and delete functions.

Data Mart

A subset of information, relevant to a group of users, that is transferred to a separate departmental server. The database can be relational, although a multi-dimensional OLAP server is often more appropriate. A range of end-user tools can be used to access the data in a data mart.

Data Warehouse

A separate database dedicated to decision support. Data is transferred from transaction processing systems and integrated. A data warehouse can provide management information via report writers, query tools, data access and retrieval tools, OLAP servers, and enterprise information systems.

SCT Banner 7.0 Glossary of Terms

Page 3


Document type definition. Schema used to constrain XML documents. DTDs are in widespread use, but the newer XML schema is the preferred schema approach.


Enterprise application integration. An overloaded term that refers to integrating multiple applications within an enterprise, usually by using middleware and a "publish and subscribe" communication model. This term is sometimes limited to "asynchronous messaging" based solutions and (incorrectly) sometimes differentiated from "Web services" based solutions.


Electronic business XML. Set of specifications that are being developed as a joint initiative of the United Nations and OASIS to enable an electronic business framework. This initiative enables a global electronic marketplace where enterprises of any size and any geographic location can conduct business with each other via the exchange of XML-based messages. Similar to, but more ambitious than SOAP (Simple Object Access Protocol), ebXML supports multiple attachments and binary types as well as guaranteed delivery of messages.


An enterprise Operational Data Store (ODS) used to provide a consistent data model for all SCT ERP systems. The EDS data model and data values are consistent for all ERP systems that feed the EDS. This database can provide enterprise-wide reporting requirements and new enterprise analytical applications that span individual ERPs.


Enterprise Java bean. An application object that executes inside an EJB container within a J2EE application server. EJB is a key aspect of J2EE. Types of EJBs include: • •

Session beans, which provide remote access to coarse-grained logic. Entity beans, which should not be invoked remotely and are intended to hold fine-grained logic.

Enterprise Object

An OpenEAI messaging term used to define the agreed upon data definition rules for synchronizing data between disparate systems within an enterprise.

Enterprise Object Catalog

A library of message definitions.


Enterprise Resource Planning. An information system that integrates all related applications for an entire enterprise.

SCT Banner 7.0 Glossary of Terms

Page 4


Fine-grained access control. Oracle functionality that provides the ability to define access policies that allow individuals or groups of users to views and tables.


An adapter used to provide access into, and perhaps out of, an application. SCT developed the Banner Gateway to adapt Banner to the OpenEAI Message Protocol.


Graphical user interface. A computer working environment, such as Windows that represents files and operations visually, using icons, buttons, windows, and other imagery that you can manipulate with a mouse or other device.


The IMS Global Learning Consortium develops and promotes the adoption of open technical specifications for interoperable learning technology. SCT’s integration with learning management systems is based on IMS specifications.


Internet-native Banner. The deployment of SCT Banner through Oracle Web forms rather than through client/server architecture. Banner forms are served up from a Web server to users running an Internet browser. INB has the following advantages over client/server mode: • • • • • •

Oracle’s stated future direction Better performance More stable Less resources required on client PC Ease of maintenance Good feedback from clients who have implemented INB


Java 2 Enterprise Edition. A distributed object computing specification against which J2EE application servers are certified. J2EE application servers provide a standard set (at a minimum) of features and behaviors required by the specification. Key features of J2EE include EJBs, servlets, JNDI, JMS, and JDBC.


Java Database Connectivity. An industry standard for databaseindependent connectivity between the Java platform and a wide range of databases.


Java Message Service. A specification that defines the features, behavior, and standard API of message-oriented middleware (MOM) products. MOM products supporting JMS are referred to as JMS providers. Almost all MOM products have adopted JMS, with Microsoft being a notable exception. Examples of JMS providers are

SCT Banner 7.0 Glossary of Terms

Page 5

SonicMQ, MQSeries, WebLogic, and iPlanet JMQ. JMS Provider

A message-oriented middleware (MOM) product that complies with the Java Message Service.


Java naming and directory interface. A standard way for accessing directory-based information to look up EJBs, RMI objects, or LDAP entries.


Lightweight Directory Access Protocol. A software protocol that helps anyone locate organizations, individuals, and other resources such as files and devices in a network, whether on the public Internet or on a corporate intranet.


Luminis Data Integration Suite Protocol. This protocol is an implementation of the IMS Enterprise Specification that is supported by the Luminis Message Broker (LMB). This protocol replaces the IMS implementation used with the Mercury Message Broker.


Luminis Data Integration Suite is part of the Luminis Product Family. LDIS is a collection of products that support integration between SCT systems and products from third-party vendors.


Luminis Message Broker. The Sun One Message Queue packaged within the Luminis Data Integration Suite (LDIS).


An array of flexible software solutions that unify, extend, and manage the digital campus. The Luminis family includes: • • •

Luminis Platform (portal) Luminis Data Integration Suite Luminis Content Management

Luminis is also the brand name under which SCT's asynchronous messaging solutions fall. This includes MMB, LMB, and OpenEAI based solutions. Message Set

A group of messages that together support application-to-application integration within a business area such as e-procurement or library system integration. Message sets comprise schema defining the XML instances, and are supported by APIs within an SCT information system.

Messaging Enterprise

The systems that participate in data synchronization activities using messaging technologies.

SCT Banner 7.0 Glossary of Terms

Page 6

Messaging Protocol

The structure and rules for effective communication between systems.


Data that describes other data. Data definitions are sometimes referred to as metadata. Examples of metadata include schema, table, index, view, and column definitions.


Mercury Message Broker. A middleware component developed by SCT to support the SCT Alliance program. MMB provides point-topoint message routing and security in support of SCT/Campus Pipeline/WebCT integration. MMB is being replaced by Luminis and the Luminis Data Integration Suite Protocol (LDIS-P).


Message-oriented middleware. Message brokers that support asynchronous messaging at their lowest common denominator. Most MOM products support the Java Message Service (JMS) specification and are consequently referred to as JMS Providers.

Multiple PIDM

The situation where a single entity (person or non-person) is assigned two or more internal identification records in Banner, thereby treating this single entity as multiple entities. Since multiple names and external IDs can be associated with a single PIDM in Banner, each entity should have one and only one PIDM.


Open Applications Group integration specification. A specification that provides standard message formats in the form of business object documents (BODs) that reflect common business exchanges. The specification was developed by the Open Applications Group, which includes various vendors working to provide interoperability between their packages.


Organization for the Advancement of Structured Information Systems. An organization that promotes and encourages the use of structured information standards such as XML, SGML, and CGM. An important part of its mission is the development of vertical industry applications, conformance tests, interoperability specifications, etc. that make those core standards useable. OASIS hosts the Web site.


Operational data store. An updateable set of integrated operational data used for enterprise- wide tactical decision-making. Contains live data, not snapshots, and has minimal history retained. A database used to provide a denormalized view of transactional ERP systems data. The denormalized view reduces the complexity of reporting requirements by giving end users the ability to use ad hoc reporting tools. The ODS is ERP-specific since it still uses the ERP systems’ application values. Data transformations to enterprise values do not

SCT Banner 7.0 Glossary of Terms

Page 7

occur in this database. See EDS. OLAP

Online analytical processing. Computer processing that helps a user easily and selectively extract and view data from different points-ofview.


An open source project that defines a message protocol, provides foundation software and reference implementations used to develop messaging applications and gateways, and provides guidance with respect to methodology and deployment strategies.

OpenEAI Message Protocol

A message protocol co-developed by SCT and the University of Illinois and contributed to the OpenEAI open source project. The protocol is very robust and is intended to ensure data integrity while supporting data synchronization across an enterprise. Details of the protocol can be found in the OpenEAI Message Protocol specification version 1.0 at


Postsecondary Electronic Standards Council. The PESC XML Forum for Education is developing XML standards for the higher education community. SCT participates in this forum and contributed to the technical specification.


Person Identification Master. The internal identifier used to identify a person or a non-person in the Banner database. Multiple external IDs and names may be associated with a single PIDM.


Personally identifiable information.


Protection of privacy.


Gateway for a Web site that is or proposes to be a major starting site for users when they connect to the Web or that users tend to visit as an anchor site.


A channel within a portal.


Syntax that specifies a subset of rows to be returned. Predicates are specified in the WHERE clause of a SQL statement.

Publish and Subscribe

A communication model, or domain, supported by asynchronous messaging. A supplier publishes a message to a message broker with no knowledge of the recipients of the message. Subscribers register their interest in certain messages with the message broker, and are informed when those messages are available. Most publish and subscribe (pub/sub) communication models are supported by message-oriented middleware that provides a high quality of service

SCT Banner 7.0 Glossary of Terms

Page 8

(QoS) guaranteeing message delivery. RMI

Java Remote Method Invocation. A distributed object model for Java program to Java program, in which the methods of remote objects written in the Java programming language can be invoked from other JavaTM virtual machines, possibly on different hosts.


A term that describes the structure of XML instances and constrains what they can contain. Two types of schema are used to constrain XML: • •

Document type definition (DTD) XML schema

SCT Pillar Institutions

A group of forward-thinking institutions that define strategic trends and opportunities. The feedback, direction, and collaboration resulting from this program are primary drivers in creating the solutions that support the comprehensive e-education infrastructure.


Software Developers Kit. Documentation, sample code, and any necessary tools needed to write an interface.


Simple Object Access Protocol. A protocol that allows synchronous and asynchronous requests and responses over the information network.


Single sign-on.


User interface. Everything designed into an information device with which a human may interact. UI includes display screen, keyboard, mouse, light pen, appearance of a desktop, illuminated characters, help messages, and method an application program or a Web site invites interaction and responds to it.


Value based security. An optional security feature that allows installations to secure information based on specific data values in secured records. For example, an institution may offer undergraduate and graduate programs with separate admissions offices for undergraduate and graduate processing. VBS allows the institution to restrict access to applications (which are stored in a single application table) so that personnel in the Undergraduate Admissions Office can access only undergraduate applications and personnel in the Graduate Admissions Office can access only graduate applications.


Virtual private database. A database that allows multiple users to access a single schema while preventing them from accessing data that

SCT Banner 7.0 Glossary of Terms

Page 9

is not relevant to them. XML

Extensible Markup Language. A language that enables topical communication over the information network. XML and XML-based schema languages provide a strong set of technologies that enable the description and exchange of structured information between collaborating applications or business partners. XML loosely refers to a family of specifications. For example, XSL (XML Stylesheet Language) is similar to Cascading Style Sheets and separates display instructions from the content designation covered by XML. The separation of presentation from content is one of the most powerful aspects of XML. The same data can be displayed in as many different formats as style sheets are defined for various purposes.

XML Instance

An XML document that is constrained by a schema. XML instances represent a document or data. SCT asynchronous message-level integration solutions pass XML instances as the payload of the messages sent to or from another application.

XML Schema

A W3C recommendation providing an improved approach to constraining an XML instance. XML schema enables finer grained constraints, improved reusability, and data typing. XML itself uses XML syntax. XML schema is preferred over DTD, particularly for data-oriented XML used in integration.


XML Stylesheet Language. A language based on XML and used to specify markup that affects another document (typically, another XML document). XSL is commonly used to translate XML content into HTML, PDF, or another XML format. SCT uses XSL transformations within relay components to transform OpenEAI Message Protocol messages to and from third party vendor format messages.


XSL Stylesheet Language: Transformation. The process of applying an XSL stylesheet to a document to transform the content to another format. This is accomplished using an XSLT engine, or transformation engine. Transformation engines have been implemented in many languages, including Java. SCT uses an open source transformation engine developed by the Apache program, called Xalon. If you are reading this glossary as an HTML page, you are reading the output of an XSL Transformation.

SCT Banner 7.0 Glossary of Terms

Page 10