ORACLE COMPLEX MAINTENANCE, REPAIR & OVERHAUL R12.1

SOLUTION HIGHLIGHTS

Oracle Complex Maintenance, Repair, and Overhaul R12.1 provides the most robust, reliable and effective means through which service poviders

and operators manage the entire maintenance lifecycle for complex assets. Specifically, Oracle cMRO R12.1 now supports:

• Aircraft induction
• Line maintenance
• Heavy maintenance planning
• Heavy maintenance execution
• Engine and component overhaul
• Marshalling

Today’s MROs use a variety of individual applications for each of their critical business processes; none of which are integrated nor provide any insight into combat readiness, asset availability, labor utilization/productivity, and maintenance profitability. As a result, multiple sources of the “truth” exist in various siloes, undermining the integrity of supply chain planning and execution, inventory levels, customer service and satisfaction, aircraft records and billing capabilities.

Oracle R12 Cloning One Node to Multi Node

Introduction

This document describes a step-by-step approach to clone an Oracle Applications R12 (which is autoconfig enabled) using Rapid Clone from one to two nodes, it includes Port Selection, Forms Server, Reports Server, Apache Server and Concurrent Processing, also all the scripts or programs, which are used to startup up and shutdown all the services. The cloning word means to do a functional copy of an existing environment. Simply copying the application directories doesn’t mean that our new environment will work properly, we need to do some additional steps or tasks to have a functional environment.

Some of the reasons to do a cloning are:

• To create a test environment from an existing production environment to test some patches or to reproduce any production issues.

Oracle Applications 11i Context/ Environment Files

Oracle Applications Context Files

During the Oracle Applications eBusiness Suite installation Rapid Install save the configuration parameters in 2 files (context files) named
<CONTEXT_NAME>.xml. The <CONTEXT_NAME> by default is <SID>_<hostname>. For instance if $ORACLE_SID is VIS and
$HOSTNAME is apps_svr.localdomain the context file will be VIS_apps_svr.xml. These context files are not used directly to configure the
Oracle Applications; the context files are only repositories which store the the configuration parameters.
The 2 context files are:
<RDBMS ORACLE_HOME>/appsutil/VIS_apps_svr.xml (for the database tier)
and
<APPL_TOP>/admin/VIS_apps_svr. xml (for each node of the the application tier)
The context files could be modified in 3 situations:
1. Apply a patch from Oracle that adds or changes the variables in VIS_apps_svr.xml, AutoConfig template files or AutoConfig driver files;
2. Using Context Editor (editcontext ) ( which is provided by the patch number 2873456);
3. Using Oracle Applications Manager (OAM) H or higher. OAM automatically stores the new values in the database and update the context files.
Oracle recommends using OAM; however if the OAM is not accessible the Context Editor must be used. The Context Editor is located at:

Application tier: <COMMON_TOP>/util/editcontext/

Database tier: <RDBMS ORACLE_HOME>/appsutil/editcontext/
The Context Editor executable file is editcontext (for UNIX) and EditContext.cmd (for Windows). The Context Editor contains 3 screens: 1st locate the context file and load it in the editor, the 2nd screen allows to edit the values in the context file and the 3rd screen allows you to save the changes to the context file.

Using Project Builder to implement a management strategy

In any development project, management tasks can be split roughly into two categories:

n Project management, which includes allocating the necessary equipment, budget, and person-hours of work necessary to complete the development of the application.

n Software configuration management, which includes assigning modules to developers, determining dependencies among modules, maintaining the code under development, and version control.

Project Builder, a component of both Forms Developer and Reports Developer, enables you to simplify your software configuration management tasks so you and your team can focus on your primary objectives: designing, coding, and testing applications.

About Project Builder

To help simplify your software management tasks, Project Builder provides the means for you to:

n Associate modules with an application or component of an application.

n Automate actions based on file types.

n Create dependencies between modules and indicate how changes cascade; in other words, show which modules need to be recompiled based on changes to other modules.

n Assign default connection strings to modules.

n Designate which modules are to be included in the final install set.

n Share projects and subprojects among team members and port them to different environments.

n Invoke other tools from the Project Builder user interface.

These features are described in detail in Section 1.1.3, "Exploring Project Builder benefits". If you’re unfamiliar with Project Builder terminology, however, it’s a good idea to read through Section 1.1.2.1, "Understanding Project Builder terminology" before proceeding. This section defines some basic terms which provide the context for a discussion of Project Builder’s features.

Oracle Forms Developer : The Software Development Lifecycle: An Overview

Application development typically occurs in four phases:

n Design. The initial specification for the application is developed. This specification can be based on a variety of sources: customer feedback, input of project management or development team members, requests for enhancement, necessary bug fixes, or systems analysis.

n Develop. Individual modules are created or modified, possibly incorporating a wide variety of languages, tools, or platforms.

n Test. The modules are tested. This generally occurs in two stages: unit test and system test. Unit test is testing at a modular or functional level; for example, testing UI
elements such as menus or buttons. System test tests the integration of major portions of the code; the backend with the UI, for example.

n Deploy. The modules are packaged together in an installable form and delivered to customers.

Figure 1–1 The phases of the development lifecycle: input and deliverables

As the application grows in size and complexity, the four phases are repeated iteratively, and the amount of information produced (actual code, bug reports, enhancement requests, etc.) grows. Yet all input and deliverables for all phases must be tracked and maintained to ensure the integrity of the final deliverable: the application your customer installs.

Install and Configure the Web Tier

Follow these steps to install the Oracle Web Tier on to Webhost1 and Webhost2
Install and Configure the First Oracle Web Tier on Webhost1
Install Oracle HTTP Server on Webhost1
Start the Oracle Universal Installer as follows:

On UNIX, issue this command: runInstaller
On Windows, double-click setup.exe