Customizing Sun OTP Deployment
Sun OTP plans are modularized in a way that NEP developers can insert their own customization. NEP developers can insert their customization before or after the Sun OTP plans. NEP developers can copy the Sun OTP AHE plug-in and customize the OTP deployment with native command execution or with new plans. They can also write their own variable set as part of the new plans.
Sun OTP components are meant to be called only from Sun OTP plans. Sun OTP plans can be called from custom plans only if the order of installation of Sun OTP plans described in Order of Installing N1 SPS Plans is satisfied.
Note –
Do not customize the Sun OTP plans and Sun OTP variable set.
Examples of Solution Specific Steps
The following table lists some of the examples of solution specific steps and where it can be inserted in Sun OTP deployment.
Table 4–4 Examples of Solution Specific Steps|
Examples of Solution Specific Steps |
Insertion Point in Sun OTP Deployment |
|---|---|
|
User Administration |
After Sun OTP is installed |
|
Quorum Configuration |
After Sun OTP availability service is installed and configured |
|
Naming Services |
After OS is installed |
|
Shared Storage Configuration |
After Sun OTP availability service is installed and configured |
- © 2010, Oracle Corporation and/or its affiliates