apc.htm

corba比较入门级的介绍详细间接了corba访问发布各种细节。

	mapping will enable developers to build distributed applications directly in Java
	and communicate via IIOP. By generating IDL from Java code, many languages have access
	to these Java-written components.<BR>
	<BR>
	
	<LI><I>DCE/CORBA Interworking RFP (ORBOS RFP6)</I>.<B> </B>This RFP solicits proposals
	for the following: Application Level Interworking, CORBA clients interacting with
	DCE servers and DCE clients interacting with CORBA servers, provisioning CORBAservices
	and CORBAfacilities (for example, security, naming, time) with existing DCE components
	(for example, security services, directory services, distributed time facility).<BR>
	<BR>
	
	<LI><I>Persistent State Service, Version 2.0 RFP (ORBOS RFP7)</I>.<B> </B>The intent
	of this RFP is to solicit proposals that provide coherent and pragmatic specification
	for CORBA persistence. The RFP focuses on a facility to be used by the object implementer
	that wishes to achieve and maintain persistence. It is important to address whether
	and, if so, how the PSS interacts with other OMG specifications, such as the POA,
	the Concurrency Service, the Transaction Service, and the Objects-by-Value Service.<BR>
	<BR>
	
	<LI><I>CORBA Component Model RFP (ORBOS RFP8)</I>.<B> </B>This RFP solicits proposals
	for a distributed component model that is based on the OMA and is capable of interoperating
	with other emerging component technologies, particularly the JavaBeans component
	model.<BR>
	<BR>
	
	<LI><I>CORBA Scripting Language RFP (ORBOS RFP9)</I>.<B> </B>This RFP is intended
	to form part of a coordinated strategy to introduce a component model into the OMA.
	The RFP solicits proposals for a scripting language that is capable of scripting
	CORBA components.<BR>
	<BR>
	
	<LI><I>Minimum CORBA RFP (ORBOS RFP10)</I>.<B> </B>This RFP solicits proposals for
	the following: A reduced CORBA core specification that implements basic client/server
	functionality, enabling configurations of subsets of the full OMG IDL definition,
	and the effect on existing CORBA and Common Object Services resulting from configuring
	out CORBA capabilities. Minimum CORBA is intended to help build embedded systems.<BR>
	<BR>
	
	<LI><I>Realtime CORBA 1.0 RFP</I>. This RFP's intent is to standardize realtime CORBA
	extensions and promote the use of the OMA in the realtime area. For example, Chorus's
	COOL is a commercial example of a CORBA ORB with realtime facilities, and this and
	other non-standard realtime CORBA variants are already being used in applications
	such as in-flight radar tracking software on board AWACS planes.<BR>
	<BR>
	
	<LI><I>Data Interchange Facility and Mobile Agent Facility RFP</I>.<B> </B>The Data
	Interchange Facility is a facility supporting interoperability between objects. The
	key elements of the service include the data interchange interfaces, the data object
	type, the life cycle of data objects, and the data translation interfaces. The use
	of metadata is another important area. To implement mobile agents, three key features
	need to be supported by ORB: launching and loading of agents on what is traditionally
	thought of as the client side of the ORB, time asynchrony, and notifying senders
	and receivers of arrival of packets intended for them. The mobile agent facility
	proposes these changes.<BR>
	<BR>
	
	<LI><I>Input Method Manager Facility RFP</I>.<B> </B>This RFP solicits proposals
	for specifications for the common features of the Input Method Manager Facility that
	enables management of input methods for (but not limited to) multi-octet Asian characters
	on CORBA platforms.
	<LI><I>Firewall RFP</I>. This RFP solicits proposals for the following: Specification
	of the use of IIOP in network firewalls, for the purpose of controlling limited use
	from the Internet or intranet of an organization's CORBA-based applications, and
	optionally, similar specifications with respect to any other inter-ORB protocols.<BR>
	<BR>
	
	<LI><I>Printing Facility RFP</I>.<B> </B>An RFP soliciting proposals for printing
	facility objects. This facility handles management (scheduling, spooling, locating)
	of print servers and routing of print jobs. The printing facility should be able
	to meet a range of printing requirements from simple documents up to high volume
	production printing.
</UL>

<H4><FONT COLOR="#000077">Analysis and Design Platform Task Force</FONT></H4>
<P>The Object Analysis and Design Task Force's charter states that its mission is
to enable developers to better understand how to develop applications using OT, thereby
increasing the market; to recommend technology for adoption to enable interoperability
across the life cycle of, and to enable reuse of, designs/work products developed
using OA&amp;D tools; to recommend technology for adoption of common semantics, metamodels,
and abstract syntax for OA&amp;D methodologies; to leverage existing OMG specifications;
to facilitate advances in the state of the art of OA&amp;D methodologies; and to
recommend liaison with other appropriate organizations. Certainly this is a hefty
responsibility to be taken on by the OMG's newest Task Force. Already this Task Force
has generated two Requests for Proposals, involving a framework for analysis and
design tools and a meta-object facility that would enable further interoperability
between CORBA tools and applications.</P>
<P>The current RFPs generated by the Analysis and Design Platform Task Force include
the following:

<UL>
	<LI><I>Analysis and Design Task Force RFP1</I>.<B> </B>This Request for Proposals
	focuses on creating a framework for analysis and design-tool semantic interoperability,
	through an Analysis and Design Facility. This facility will contain the interfaces
	and semantics needed to support the creation and manipulation of OA&amp;D models
	that define the behavior of object applications with the Object Management Architecture.
	This includes a set of notations that can be used to describe these models in a consistent
	fashion.<BR>
	<BR>
	
	<LI>This RFP has already been successfully completed with the adoption of OMB UML
	1.0, proposed by Rational, IBM, Objectime, and other submitters. The formal spec
	should be published in early 1998.
</UL>

<H3><A NAME="Heading6"></A><FONT COLOR="#000077">Task Forces of the Domain Technology
Committee</FONT></H3>
<P>The work of the Domain Technology Committee comes to fruition in the form of CORBAfacilities,
particularly in the vertical facilities such as health care, manufacturing, and telecommunications.</P>
<P>Currently, the Domain Technology Committee has chartered the following Task Forces:

<UL>
	<LI>Business Object Task Force
	<LI>Electronic Commerce Domain Task Force
	<LI>Financial Domain Task Force (CORBAfinancials)
	<LI>Manufacturing Domain Task Force (CORBAmanufacturing)
	<LI>CORBAmed Task Force (Healthcare)
	<LI>Telecommunications Task Force (CORBAtel)
	<LI>Transportation Domain Task Force (CORBAtransport)
</UL>

<P>(Note that many of the Task Forces composing the Domain Technology Committee are
organized around vertical domains.)
<H4><FONT COLOR="#000077">Business Object Domain Task Force</FONT></H4>
<P>Again referring to the OMG Web site, the mission of the Business Object Task Force
is to define the domain of OMG Business Objects. It will work to facilitate and promote
the use of OMG-distributed object technology for business systems; commonality among
vertical domain task force standards; simplicity in building, using, and deploying
business objects for application developers; interoperability between independently
developed business objects; the adoption and use of common business object and application
component standards; and issuance of requests and evaluation of responses and proposals
for adoption by the OMG specifications for objects, frameworks, services, and architectures
applicable to a wide range of businesses.</P>
<P>Certainly the role of the Business Object Domain Task Force is an important one.
Because the purpose of most distributed enterprise-level applications is to facilitate
the communication between business objects, the goals of the Business Object Domain
Task Force have much in common with the goals of the distributed application developer:
to enable the development and deployment of robust, interoperable business objects.</P>
<P>The current RFPs and RFIs issued by the Business Object Domain Task Force include
the following:

<UL>
	<LI><I>Common Business Object and Business Object Facility RFP</I>.<B> </B>This RFP
	solicits proposals for Common Business Objects, those objects representing business
	semantics that can be shown to be common across most businesses, and a Business Object
	Facility that provides the infrastructure required to support business objects operating
	as cooperative application components in a distributed object environment.<BR>
	<BR>
	
	<LI><I>Workflow Management Facility RFP</I>.<B> </B>The Workflow Management Facility
	defines interfaces and their semantics required to manipulate and execute interoperable
	workflow objects and their metadata. The Workflow Management Facility will serve
	as a high-level integrating platform for building flexible workflow management applications
	incorporating objects and existing applications. This RFP solicits proposals for
	the Workflow Management Facility.<BR>
	<BR>
	
	<LI><I>Common Business Objects RFI (CBO RFI)</I>.<B> </B>The Common Business Object
	Working Group is attempting to define a reference architecture that provides a concise
	and effective framework within which the dependencies between individual domains
	can be understood and reconciled. The Working Group invites input from individuals
	and organizations with insights or information that could provide a basis for work
	in this area.
</UL>

<H4><FONT COLOR="#000077">Manufacturing Domain Task Force</FONT></H4>
<P>The Manufacturing Domain Task Force, the successor to the Manufacturing Special
Interest Group, has a mission to foster the emergence of cost-effective, timely,
commercially available, and interoperable manufacturing domain software components
through CORBA technology; to recommend technology for adoption that enables the interoperability
and modularity of CORBA-based manufacturing domain software components; to encourage
the development and use of CORBA-based manufacturing domain software components,
thereby increasing the object technology market; to leverage existing OMG specifications;
and to recommend liaison with other appropriate organizations in support of the preceding
goals.</P>
<P>Current RFPs and RFIs generated by the Manufacturing Domain Task Force include
the following:

<UL>
	<LI><I>Manufacturing High-Level Requirements RFI (MFG RFI1)</I>.<B> </B>This Request
	for Information seeks input on clarifying and revising the Manufacturing Object Model
	as well as identifying a high-level partitioning of that model and improving the
	list of infrastructure requirements. This partitioning will be used as the basis
	for a road map and future RFPs from the Task Force.<BR>
	<BR>
	
	<LI><I>Manufacturing DTF RFI-2</I>. This RFI solicits input from ERP users and vendors
	on recommendations for the number of RFPs and subject areas to be covered by RFPs,
	and on ERP systems to be issued by the Manufacturing DTF. ERP includes systems referred
	to as Materials Requirements Planning (MRP) and Manufacturing Resource Planning (MRP-II).
	ERP's major relationship is to the Production Planning business process.<BR>
	<BR>
	
	<LI><I>Product Data Management Enablers RFP (MFG RFP1)</I>.<B> </B>This RFP looks
	to establish standard interfaces for the services provided by Product Data Management
	(PDM) systems. These interfaces, made available through ORBs, will provide the standard
	needed to support a distributed product data-management environment, as well as provide
	standard interfaces to differing PDM systems.