test

Sun Open Telecommunications Platform 2.0 Developer's Guide

Chapter 4 Sun OTP Components

This chapter describes Sun OTP components, plans, and plug-in. It also describes the Sun OTP deployment options and how you can customize the Sun OTP deployment.

N1 SPS Components

The components installed by the N1 SPS (N1 Service Provisioning System) plans are as follows:

Table 4–1 N1 SPS Components

Components 

Folder 

Description 

N1SPS 

/com/sun/OTP/management/n1sps

Component to install Sun OTP application provisioning service (Sun N1 Service Provisioning System) 

N1SM 

/com/sun/OTP/management/n1sm

Component to install Sun OTP system management service (Sun N1 System Manager) 

SunCluster 

/com/sun/OTP/availability/sc

Component to install Sun OTP availability service (Sun Cluster) 

AccessManager 

/com/sun/OTP/security/jes_am

Component to install Access Manager. This component is part of Sun OTP security service. 

DirectoryServer 

/com/sun/OTP/security/jes_ds

Component to install Directory Server. This component is part of Sun OTP security service. 

WebServer 

/com/sun/OTP/security/jes_ws

Component to install Web Server. This component is part of Sun OTP security service. 

Zone, ZoneRASSH, ZoneRARAW 

/com/sun/OTP/virtualization/zones

Components to install zones 

sunotp-secure.driver.tar 

/com/sun/OTP/security/jass

Component to administer Sun OTP JumpStart Architecture and Security Scripts (JASS) 

PatchOS 

/com/sun/OTP/Utilities

Component to install patches on the OS 

SharedDisk 

/com/sun/OTP/Utilities

Component to set up shared storage 

WebSSO 

/com/sun/OTP/security/WebSSO

Component to administer Sun OTP Web SSO 

SharedComponents (internal to Sun OTP) 

/com/sun/OTP/shared_components

Component to install Sun OTP shared services 

JESHA (internal to Sun OTP) 

/com/sun/OTP/security/jes_ha

Component to administer high availability services for Sun OTP security service 

Init (internal to Sun OTP) 

/com/sun/OTP/Utilities

Container Component that has constants and some common code. This common code is used by other components. 

OTPConfig (internal to Sun OTP) 

/com/sun/OTP/Utilities

Component to store and validate the Sun OTP configuration variables 

SysMng (internal to Sun OTP) 

/com/sun/OTP/N1SM

Component to administer N1SM 

The following figure shows the N1 SPS folder structure of Sun OTP plug-in.

Figure 4–1 N1 SPS Folder Structure of Sun OTP Plug-in

Figure showing the N1 SPS folder structure of Sun OTP plug-in

N1 SPS Plans

This section describes the order of installing N1 SPS plans,plan re-runs, plan configuration files, and utility plans.

The following topics are discussed in this section:

Order of Installing N1 SPS Plans

A plan orchestrates deployment of multiple components.

To install Sun OTP, N1 SPS plans must be installed in the following order:

  1. Setup Configuration

  2. Patch

  3. Install Availability Service

  4. Configure Availability Service

  5. Configure Solaris Containers (optional)

  6. Setup Shared Storage (optional)

  7. Install System Management Service

  8. Install Provisioning Service

  9. Install Security Service

  10. Configure Components

  11. Install Web SSO

Plan Re-runs

Plan re-runs provides an option to re-run specific plans instead of reinstalling Sun OTP from the beginning. Plans can be re-run multiple times irrespective of the previous state of the plan.

The following plans can be re-run:

When you re-run a plan, plan re-runs read the registry and determines the state of the plan. Based on the state of the plan, plan re-runs perform the following actions.

The following are the possible actions of plan re-runs:

Plan Configuration Files

Plan configuration files are the variable sets provided by N1 SPS. You can create component variables for your plans using the variable sets. The Setup Configuration plan provided by Sun OTP accepts all the component variables and validates the variables provided in the variable set.

The following table lists the component variables used by Sun OTP plans. See Sun OTP Plan Settings Description for descriptions of each component variable.

Table 4–2 Component Variables Used by Sun OTP Plans

Plan 

Component Variables 

Patch 

  • mediaDirectory

  • applyAllPatches

  • hostType

Install Availability Service 

  • mediaDirectory

  • hostType

  • clusterName

  • sponsorNode

  • autoConfigureIPMP

  • secondaryInterface

  • secondaryIP

  • testIPAddress

  • privateInterface1

  • privateInterface2

  • nodeAuthentication

  • transportTypeInterface1

  • transportTypeInterface2

  • applyAllPatches

  • quorumAutoConfiguration

Configure Availability Service 

  • mediaDirectory

  • hostType

  • clusterName

  • sponsorNode

  • autoConfigureIPMP

  • secondaryInterface

  • secondaryIP

  • testIPAddress

  • privateInterface1

  • privateInterface2

  • nodeAuthentication

  • transportTypeInterface1

  • transportTypeInterface2

  • applyAllPatches

  • quorumAutoConfiguration

Configure Solaris Containers 

  • mediaDirectory

  • hostType

  • zoneName

  • zoneInterface

  • zoneIPAddress

  • zonePath

  • zoneHostname

  • zoneMask

  • zoneDefaultRoute

  • zoneSPSHost

Setup Shared Storage 

  • rootDisk

  • diskSlice

  • hostType

Install System Management Service 

  • mediaDirectory

  • hostType

  • mgmtHost

  • mgmtIP

  • managementInterface

  • provisioningInterface

  • applyAllPatches

Install Provisioning Service 

  • mediaDirectory

  • mgmtHost

  • mgmtIP

  • applyAllPatches

  • spsRAConnectionType

  • hostType

Install Security Service 

  • mediaDirectory

  • hostType

  • hostName

  • zoneHostname

  • zoneIPAddress

  • jesHAHost

  • domainName

  • applyAllPatches

  • mmrHostList

Configure Components 

  • mediaDirectory

  • mgmtHost

  • mgmtIP

  • applyAllPatches

  • spsRAConnectionType

  • hostType

  • hostName

  • zoneHostname

  • zoneIPAddress

  • jesHAHost

  • jesHANodeList

  • domainName

  • mmrHostList

Install Web SSO 

  • hostName

  • hostType

  • mgmtHost

  • jesHAHost

  • ssoCookieDomain

  • zoneIPAddress

  • zoneHostname

  • domainName

Utility Plans

Sun OTP provides the following utility plans:

Table 4–3 Sun OTP Utility Plans

Plan 

Description 

Patch 

Installs the OS patches on the Sun OTP host. 

Convert 

Converts the stand-alone Sun OTP host to the clustered Sun OTP host. 

Enable & Disable 

Enables and disables Sun OTP system management service and Sun OTP application provisioning service. 

Add User 

Adds Web SSO user. 

Change User Password 

Changes the password of existing Web SSO user. 

Remove User 

Removes Web SSO user. 

Install Driver 

Installs the Sun OTP SST package. 

UnInstall Driver 

Uninstalls the Sun OTP SST package. 

Harden 

Improves the security of the system by hardening the Sun OTP host. You can close the ports and disable the services that might present a security risk to the system. 

UnHarden & Keep 

Reopens the ports and enables the services that were closed by the hardening process. This plan rolls back only the unchanged configuration files to its default state. 

UnHarden & Revert 

Reopens the ports and enables the services that were closed by the hardening process. This plan rolls back all the configuration files, including the changed files, to its default state. 

Sun OTP AHE Plug-in

A plug-in is a collection of plans and components. Sun OTP AHE plug-in is a collection of Sun OTP plans and components.

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