|
Provided by: InvariantLogic CORBA Training in IndiaTrain the Trainer |
 |
Training
Provided by InvariantLogic
This class covers the essential concepts necessary to understand CORBA objects or/and CORBA components, and then interface design and specification.
The class addresses such questions as:
What is a CORBA object? (Differences from other object models)
Do I have to use an object-oriented programming language like C or Java?
What should I be thinking about when I design my object s/component s interfaces?
How should I design my objects/component?
What techniques and tools are there for component design?
How do I use UML to model CCM components?
How to implement/configure/distribute/deploy objects/components
This class is taught seminar-style, with a fast flow of concepts and principles, and descriptions of techniques.
This 5-day class covers the following topics:
Introduction to CORBA Concepts
ORB
IDL and Language Translation
CORBA servers and clients
POA concept, architecture and usage
Servant Activator and Servant Locator
CORBA services
Dynamic CORBA - DII & DSI, Any, DynAny, Interface Repository, Implementation Repository
CORBA Component Model
Component Model
Container Model
Packaging
Assembly, Configuration & Deployment
Domain Models
UML, CORBA & MDA
Domain standards like TMF 513 & JIDM etc
The class addresses such questions as:
What is a CORBA object? (Differences from other object models)
Do I have to use an object-oriented programming language like C or Java?
What should I be thinking about when I design my object s/component s interfaces?
How should I design my objects/component?
What techniques and tools are there for component design?
How do I use UML to model CCM components?
How to implement/configure/distribute/deploy objects/components
This class is taught seminar-style, with a fast flow of concepts and principles, and descriptions of techniques.
This 5-day class covers the following topics:
Introduction to CORBA Concepts
ORB
IDL and Language Translation
CORBA servers and clients
POA concept, architecture and usage
Servant Activator and Servant Locator
CORBA services
Dynamic CORBA - DII & DSI, Any, DynAny, Interface Repository, Implementation Repository
CORBA Component Model
Component Model
Container Model
Packaging
Assembly, Configuration & Deployment
Domain Models
UML, CORBA & MDA
Domain standards like TMF 513 & JIDM etc
|
|
||||||||||||||||||
CORBA Training in India
We offer flexible combination of topics of interest and duration of training as per trainees requirement (valid only for on-site training)
Training Program For CORBA based Enterprise Systems
---------------------------------------------------
Distributed Systems and CORBA Architecture
A remarkable number of real-world, mission-critical systems use CORBA. Including distributed
real-time and embedded systems, e.g., telecom/datacomm, aerospace, defense, control systems,
industrial automation, online financial services, gaming and multimedia, robotics, automotive
systems. Know who-who of the worlds largest enterprises are using CORBA. Learn about that
and CORBA Architecture in the first session of the programme.
Middleware as distributed OS
Design Issues for Distributed Systems
CORBA vs Web Services/.NET/J2EE
OMA Object Management Architecture
ORB Object Request Broker
CORBA Services and Facilities
OMG IDL Interface Definition Language
Mapping of IDL to specific language
Clients
Object Implementations
Object References
Communication Protocol GIOP/ IIOP
Dynamic Capabilities
o Any
o DynAny
o DII Dynamic Interface Invocation
o DSI Dynamic Skeleton Invocation
POA Portable Object Adapter
o POA Manager
o POA Policies
o Reference Creation
o Request Processing
o Object Activation
Servant Manager
o Default Servant Manager
o Servant Activator
o Servant Locator
Interface Repository
Implementation Repository
CORBA and Link to MDA
---------------------
Although MDA can target every middleware platform and will map to all that have significant
market presence, CORBA plays a key role as a target platform because of its programming
language-, operating system-, and vendor-independence.
CORBA provides powerful programming model that reduces writing infrastructure codes. The
object-activation model (Servant managers) and other idioms eases programmers from writing
low level codes and so enables rapid development and high productivity.
CORBA in Telecom
----------------
Long considered to be bread & butter for CORBA. Its commonly said that if you make a call,
CORBA has been used somewhere.
Recent adoption of CORBA as choice of technology by TEC (Telecom Engineering
Communications (India) makes it mandatory for Telecom Equipment manufacturers to be
TMF513 business interface compliant. Learn about that and also how to enable CORBA
applications interworking with TMN Systems Specification.
TMF JIDM
o Overview o Overview
o Architecture o Architecture
o Business problem o JIDM CORBA Facilities
o Business processes .
Overview
o Process definition .
JIDM Gateways (Manager
o Mapping of process to eTOM
o ETOM business process framework
Requirement
side and Agent side)
o SNMP CORBA Facilities
CORBA Component Model (CCM)
---------------------------
CCM is a specification to build server side robust, scalable application. It simplifies system
specification, programming model, assembly framework, packaging and deployment of software
systems. This makes it possible to design, develop and deploy complex softwares over
heterogeneous infrastructures.
Component Model Component categories
o Component definition, identity, o Service component
navigation. o Session component
o Component Levels (basic and
extended)
Facets
Receptacles
o Process component
o Entity component
Integrating with EJB
o Introduction
Event Publisher (Emitter and Publisher) o EJB view of CORBA component
Event Consumer (Event Sink) o Compare EJB with CCM
Component configuration Packaging of component
Component Implementation Framework o Package descriptor
o Component Implementation Definition o Component descriptor
o Component Executor o Deployment descriptor
o Composition structure Assembly
o State information o Component Assembly Packaging
o Component Home o Assembly Descriptor
Container Programming Model Application/Assembly deployment
Component containers o Assembly Deployment descriptor
o Component lifetime management o Collocation mechanism for deployment
o Transaction QoS
o Security o Stream ports
o Events
o Persistence
Distributed Event Notification Service
--------------------------------------
The main design goal is to allow asynchronous communication between clients and server.
Service Description Sharing subscriptions
Architecture Features Filtered Typed Events
Overview The Event Type Repository
Structured Events Interfaces Overview
Event Filtering with Filter Objects
Quality of Service Administration
o CosNotification Module
o CosNotifyFilter Module
o CosNotifyComm Module
o CosNotifyChannelComm Module
o CosTypedNotifyChannel Module
CORBA Fault Tolerance Service
-----------------------------
Many different kinds of applications, developed by the members of the OMG and the users of
CORBA, have a need for fault tolerance. These applications range from very large critical
systems (such as air traffic control and defense systems) to smaller critical systems (such as 911
and medical systems) to embedded applications (such as aircraft instrumentation and
manufacturing control applications) to communication systems (such as telephony and
networking systems) to enterprise applications (such as financial and supply chain applications).
A standard that attempts to meet all of the requirements of this wide spectrum of applications
Overview Replication Management
Architecture of basic FT o Object Group Manager
Use Cases Fault management
ORB specific
------------
The vendors provide their own propriety implementation of standard to satisfy specific needs,
driven by actual use cases and real life situations. The result is very pragmatic implementations
that solve very real problems.
Service Description Implementation Repository
CORBA QoS Policies
Building Multithreaded Application
Configuring Application
IDL
---
The OMG Interface Definition Language (IDL) is the language used to describe the interfaces that
client objects call and object implementations provide. An interface definition written in OMG IDL
completely defines the interface and fully specifies each operation s parameters.
An OMG IDL interface provides the information needed to develop clients that use the interface s
operations.
Overview
IDL Designing
Import Declaration
Module Declaration
Interface Declaration
Value Declaration
Constant Declaration
Type Declaration
o Designing IDL for Performance
Exception Declaration
Granularity
Operation Declaration
o Designing IDL for Batching
Attribute Declaration
IDL Patterns
Event Declaration
o IDL Operations
Component Declaration
o IDL Inheritance
Home DeclarationValuetypes
o IDL Exceptions
o Architecture
o IDL Callbacks
o Standard Value Box Definitions
o IDL Distributed Iterators
o Language Mappings
o Custom Marshalling
Any
Abstract Interface Semantics
o Overview
o Semantics of Abstract Interface
o Usage Guidelines
IDL to C
----------
The C mapping tries to avoid limiting the implementation freedoms of ORB developers. For
each OMG IDL and CORBA construct, the C mapping explains the syntax and semantics of
using the construct from C .
The design of the C mapping was driven by a number of considerations, including a design
that achieves reasonable performance, portability, efficiency, and usability for OMG IDL-to-C
implementations. Several other considerations are outlined in this section.
POA
---
The ORB is an abstraction visible to both the client and server. The POA is an object visible to
the server. User-supplied implementations are registered with the POA. Learn all about POA and
its capabilities
POA Architecture UML Description of Portable Server
o Model Components Usage Scenarios Getting the RootPOA
o POA Creation - Creating a POA
o Reference Creation o Explicit Activation
o Request Processing o Creating References before Activation
o Object Activation States o Servant Manager Definition and
o Implicit Activation Creation
o Dynamic Skeleton Interface o Object Activation on Demand
Interfaces And Descriptions
o The Servant IDL TypePOAManager
Interface
o Persistent Objects with POA assigned
Ids
o Multiple object Ids Mapping to a single
o AdapterActivator Interface
o ServantManager Interface
Servant
o One Servant for All Objects
o ServantActivator Interface
o ServantLocator Interface
o POA Policy Objects
o POA Interface
ORB Interface
-------------
Overview
ORB operations
Object References Operations
Determining the Object Interface
Duplicating and Releasing copies of Object References
ORB and OA initialization and Initial References
Management of Policy Domains
TypeCodes
Exceptions
Portable Interceptor
--------------------
Introduction Portable Interceptor Current
Interceptor Interface
Use of Portable Interceptor Current IOR Interceptor
Request Interceptors o Overview
Dynamic Initial References
Interface Repository
--------------------
Overview and Scope Interface Repository
Basics Interfaces Repository Ids
DII, DSI and DynAny
-------------------
Overview and Scope Interface Repository
Basics Interfaces Repository Ids
Training Program For CORBA based Enterprise Systems
---------------------------------------------------
Distributed Systems and CORBA Architecture
A remarkable number of real-world, mission-critical systems use CORBA. Including distributed
real-time and embedded systems, e.g., telecom/datacomm, aerospace, defense, control systems,
industrial automation, online financial services, gaming and multimedia, robotics, automotive
systems. Know who-who of the worlds largest enterprises are using CORBA. Learn about that
and CORBA Architecture in the first session of the programme.
Middleware as distributed OS
Design Issues for Distributed Systems
CORBA vs Web Services/.NET/J2EE
OMA Object Management Architecture
ORB Object Request Broker
CORBA Services and Facilities
OMG IDL Interface Definition Language
Mapping of IDL to specific language
Clients
Object Implementations
Object References
Communication Protocol GIOP/ IIOP
Dynamic Capabilities
o Any
o DynAny
o DII Dynamic Interface Invocation
o DSI Dynamic Skeleton Invocation
POA Portable Object Adapter
o POA Manager
o POA Policies
o Reference Creation
o Request Processing
o Object Activation
Servant Manager
o Default Servant Manager
o Servant Activator
o Servant Locator
Interface Repository
Implementation Repository
CORBA and Link to MDA
---------------------
Although MDA can target every middleware platform and will map to all that have significant
market presence, CORBA plays a key role as a target platform because of its programming
language-, operating system-, and vendor-independence.
CORBA provides powerful programming model that reduces writing infrastructure codes. The
object-activation model (Servant managers) and other idioms eases programmers from writing
low level codes and so enables rapid development and high productivity.
CORBA in Telecom
----------------
Long considered to be bread & butter for CORBA. Its commonly said that if you make a call,
CORBA has been used somewhere.
Recent adoption of CORBA as choice of technology by TEC (Telecom Engineering
Communications (India) makes it mandatory for Telecom Equipment manufacturers to be
TMF513 business interface compliant. Learn about that and also how to enable CORBA
applications interworking with TMN Systems Specification.
TMF JIDM
o Overview o Overview
o Architecture o Architecture
o Business problem o JIDM CORBA Facilities
o Business processes .
Overview
o Process definition .
JIDM Gateways (Manager
o Mapping of process to eTOM
o ETOM business process framework
Requirement
side and Agent side)
o SNMP CORBA Facilities
CORBA Component Model (CCM)
---------------------------
CCM is a specification to build server side robust, scalable application. It simplifies system
specification, programming model, assembly framework, packaging and deployment of software
systems. This makes it possible to design, develop and deploy complex softwares over
heterogeneous infrastructures.
Component Model Component categories
o Component definition, identity, o Service component
navigation. o Session component
o Component Levels (basic and
extended)
Facets
Receptacles
o Process component
o Entity component
Integrating with EJB
o Introduction
Event Publisher (Emitter and Publisher) o EJB view of CORBA component
Event Consumer (Event Sink) o Compare EJB with CCM
Component configuration Packaging of component
Component Implementation Framework o Package descriptor
o Component Implementation Definition o Component descriptor
o Component Executor o Deployment descriptor
o Composition structure Assembly
o State information o Component Assembly Packaging
o Component Home o Assembly Descriptor
Container Programming Model Application/Assembly deployment
Component containers o Assembly Deployment descriptor
o Component lifetime management o Collocation mechanism for deployment
o Transaction QoS
o Security o Stream ports
o Events
o Persistence
Distributed Event Notification Service
--------------------------------------
The main design goal is to allow asynchronous communication between clients and server.
Service Description Sharing subscriptions
Architecture Features Filtered Typed Events
Overview The Event Type Repository
Structured Events Interfaces Overview
Event Filtering with Filter Objects
Quality of Service Administration
o CosNotification Module
o CosNotifyFilter Module
o CosNotifyComm Module
o CosNotifyChannelComm Module
o CosTypedNotifyChannel Module
CORBA Fault Tolerance Service
-----------------------------
Many different kinds of applications, developed by the members of the OMG and the users of
CORBA, have a need for fault tolerance. These applications range from very large critical
systems (such as air traffic control and defense systems) to smaller critical systems (such as 911
and medical systems) to embedded applications (such as aircraft instrumentation and
manufacturing control applications) to communication systems (such as telephony and
networking systems) to enterprise applications (such as financial and supply chain applications).
A standard that attempts to meet all of the requirements of this wide spectrum of applications
Overview Replication Management
Architecture of basic FT o Object Group Manager
Use Cases Fault management
ORB specific
------------
The vendors provide their own propriety implementation of standard to satisfy specific needs,
driven by actual use cases and real life situations. The result is very pragmatic implementations
that solve very real problems.
Service Description Implementation Repository
CORBA QoS Policies
Building Multithreaded Application
Configuring Application
IDL
---
The OMG Interface Definition Language (IDL) is the language used to describe the interfaces that
client objects call and object implementations provide. An interface definition written in OMG IDL
completely defines the interface and fully specifies each operation s parameters.
An OMG IDL interface provides the information needed to develop clients that use the interface s
operations.
Overview
IDL Designing
Import Declaration
Module Declaration
Interface Declaration
Value Declaration
Constant Declaration
Type Declaration
o Designing IDL for Performance
Exception Declaration
Granularity
Operation Declaration
o Designing IDL for Batching
Attribute Declaration
IDL Patterns
Event Declaration
o IDL Operations
Component Declaration
o IDL Inheritance
Home DeclarationValuetypes
o IDL Exceptions
o Architecture
o IDL Callbacks
o Standard Value Box Definitions
o IDL Distributed Iterators
o Language Mappings
o Custom Marshalling
Any
Abstract Interface Semantics
o Overview
o Semantics of Abstract Interface
o Usage Guidelines
IDL to C
----------
The C mapping tries to avoid limiting the implementation freedoms of ORB developers. For
each OMG IDL and CORBA construct, the C mapping explains the syntax and semantics of
using the construct from C .
The design of the C mapping was driven by a number of considerations, including a design
that achieves reasonable performance, portability, efficiency, and usability for OMG IDL-to-C
implementations. Several other considerations are outlined in this section.
POA
---
The ORB is an abstraction visible to both the client and server. The POA is an object visible to
the server. User-supplied implementations are registered with the POA. Learn all about POA and
its capabilities
POA Architecture UML Description of Portable Server
o Model Components Usage Scenarios Getting the RootPOA
o POA Creation - Creating a POA
o Reference Creation o Explicit Activation
o Request Processing o Creating References before Activation
o Object Activation States o Servant Manager Definition and
o Implicit Activation Creation
o Dynamic Skeleton Interface o Object Activation on Demand
Interfaces And Descriptions
o The Servant IDL TypePOAManager
Interface
o Persistent Objects with POA assigned
Ids
o Multiple object Ids Mapping to a single
o AdapterActivator Interface
o ServantManager Interface
Servant
o One Servant for All Objects
o ServantActivator Interface
o ServantLocator Interface
o POA Policy Objects
o POA Interface
ORB Interface
-------------
Overview
ORB operations
Object References Operations
Determining the Object Interface
Duplicating and Releasing copies of Object References
ORB and OA initialization and Initial References
Management of Policy Domains
TypeCodes
Exceptions
Portable Interceptor
--------------------
Introduction Portable Interceptor Current
Interceptor Interface
Use of Portable Interceptor Current IOR Interceptor
Request Interceptors o Overview
Dynamic Initial References
Interface Repository
--------------------
Overview and Scope Interface Repository
Basics Interfaces Repository Ids
DII, DSI and DynAny
-------------------
Overview and Scope Interface Repository
Basics Interfaces Repository Ids
About The Training Provider: InvariantLogic
InvariantLogic - This company is into training in OMG technologies, including CORBA, UML, MDA and SOA etc.
We have two modes of training, we prefer and promote instructor based training anywhere in India. But also have web based online training courses as well.
Inspired by requirement in the industry because of lack of available experts esp in advance technology like CORBA and UML etc, we decided to launch...
