C++ CORBA Migration
Week 1
Day One: Introduction and discovery phase. The client shares with the OCI migration team the “as is” design and implementation. Factors that should be borne in mind are raised. These can be new design options, areas of dead code that can now be retired, new platform targets, upgrades to compilers, new coding standards, undesirable behavior that requires improvement (scalability, security, GUI’s).
This first day enables critical issues to be identified, and is used by OCI to refine the topic list for Days 2 and 3.
Days Two and Three: 12 hours of instruction on targeted functionality and features consistent with the Day 1 analysis. The 12 hours, in depth instruction, is selected from the following:
- CORBA 2.5 Overview – an update on the latest capabilities of CORBA - 1 hour
- Learning and using the Portable Object Adapter (POA) including the various strategy options. – 6 hours.
- An Overview of the ACE ORB (TAO).
- Building Applications with TAO – 1 hour.
- Using TAO’s IDL compiler
- Compiling and Linking applications with TAO
- Memory Management – 3 hours
- Operation Parameters
- Object References
- Implementation objects (servants).
- Request Processing – 3 hours
- Policies
- Multithreading
- Accessing CORBA Objects – 3 hours
- Using the naming service.
- Directly binding to CORBA Objects
- Indirectly binding to CORBA Objects
- Portable Interceptors – 3 hours.
- Miscellaneous issues – 1 to 3 hours depending on which features are likely to be required.
Note: This subject material is selected from existing OCI CORBA courseware but is presented in the context of migration plan and does not include exercises to ensure optimal use of the time.
At the conclusion of this instruction the participants will be able to more fully participate in the migration planning.
Days 4 and 5: These two days are utilized to create new design approaches where appropriate, identify recurring coding techniques and provide sample best practices for the new implementation. The OCI consultant meets with small groups of the team to mentor them in the new approaches. The consultant helps with installation, set up and code development.
Week 2
This optional week may follow on directly to continue the momentum of the first week. Or it may occur a few weeks later, as an “audit,” or design review, of progress achieved. It is scheduled to ensure continuity of the consulting team.