Home > Articles > Operating Systems, Server > Solaris

Like this article? We recommend

Minimizing and Automating Installations

The primary goal of this article is to create a simple, reproducible, and secure application installation methodology. A secondary goal is to automate the OS and software installation process.

The following sections provide procedures for each of the tasks:

  • "Verifying OS Software"
  • "Installing Solaris OE Core Cluster"
  • "Installing Patches"
  • "Removing Unnecessary Packages"
  • "Using JumpStart Software to Configure the OS"
  • "Installing and Configuring Software Packages"
  • "Checking For Errors"
  • "Testing Software Installation"

Verifying OS Software

Verify that the Solaris OE versions installed on the JumpStart boot server are the versions that you require. For the purposes of the testing performed for this article, we use the following Solaris OE versions:

  • Solaris 2.6 OE (5/98)
  • Solaris 7 OE (11/99)
  • Solaris 8 OE (2/02)
  • Solaris 9 OE (5/02)

Installing and Configuring a JumpStart Server

The installation and configuration of a JumpStart server is beyond the scope of this article. For information, please refer to the following:

Kernel Patching the Boot Image

Depending on the Solaris OE version used on the JumpStart server and the hardware platform being installed, some kernel patching of the boot image may be required. If you encounter unexpected results during the installation, refer to SunSolve OnLine (http://sunsolve.sun.com) to determine if any patches are required.

For information on how to kernel patch the boot image, refer to the Sun BluePrints JumpStart™ Technology: Effective Use In the Solaris™ Operating Environment.

Using Solaris Security Toolkit Scripts

The JumpStart framework and automation capabilities of the Solaris Security Toolkit software simplify Step 2 through Step 6 of the methodology as described in "Methodology Summary" on page 6. You can download the scripts used to validate and test this methodology from http://www.sun.com/blueprints/tools/. The following list describes the scripts specific to the Sun ONE Web Server installation supported by Solaris OE versions 2.6 through 9.

  • install-iPlanetWS.driver – Provides a framework, based on the Solaris Security Toolkit software, in which all other scripts are run.

  • install-iPlanetWS.fin – Extracts and installs the Sun ONE Web Server software onto the server.

  • minimize-iPlanetWS.fin – Removes unnecessary Solaris OE packages according to the Solaris OE being installed.

  • minimal-iPlanetWS-Solaris9-64bit.profile – Defines which cluster and packages should be installed for a 64-bit Solaris 9 OE installation.

  • minimal-iPlanetWS-Solaris8-32bit.profile – Defines which cluster and packages should be installed for a 32-bit Solaris 8 OE installation.

  • minimal-iPlanetWS-Solaris8-64bit.profile – Defines which cluster and packages should be installed for a 64-bit Solaris 8 OE installation.

  • minimal-iPlanetWS-Solaris7-32bit.profile – Defines which cluster and packages should be installed for a 32-bit Solaris 7 OE installation.

  • minimal-iPlanetWS-Solaris7-64bit.profile – Defines which cluster and packages should be installed for a 64-bit Solaris 7 OE installation.

  • minimal-iPlanetWS-Solaris26.profile – Defines which cluster and packages should be installed for a Solaris 2.6 OE installation.

Installing Solaris OE Core Cluster

The initial installation should include only the Solaris OE Core cluster and a few other packages that contain critical functionality. In JumpStart server terminology, the Core cluster is referred to as the SUNWCreq cluster. For your initial Core cluster, be advised that each OS version requires additional packages. Refer to "Minimizing the Sun ONE Web Server" for version details.

The profile, which is used by JumpStart to define which OS cluster and packages are installed, must specify both the Solaris OE install cluster and any additional packages required. Sample profiles are available in the Solaris Security Toolkit software.

Installing Patches

Before making any other changes to the system, it is critical to install on your server all recommended, security, and software vendor patches. This step is especially important when the goal is to minimize the number of installed packages, because some patches may install unwanted packages.

Sun recommends installing the Recommended and Security Patch Cluster for the Solaris OE version being installed. It contains all recommended and security patches. Access to these patch clusters does not require a service contract.

You can find the Recommended and Security Patch Cluster, the Patches Containing Security Fixes, and the Kernel Update Patches on the SunSolve OnLine Web site at: http://sunsolve.sun.com.

The kernel update patch 106541 for Solaris 7 OE is an example of why patches must be installed before you perform any minimization or security hardening. The README and pkgmap of this patch shows that the following files are updated when the patch is installed:

  • /etc/rc2.d/S71rpc
  • /etc/syslog.conf
  • /etc/init.d/rpc

The presence of any of these files may either enable a service that has previously been disabled (rpc, automounter, or volume manager) or overwrite a file with specific configuration information in it (syslog.conf).


Once package removal and system configuration has begun, patch installation should be done only after the README and pkgmap of a package is reviewed for possible conflicts.

Removing Unnecessary Packages

After you install and patch the Solaris OE, remove unnecessary packages. The package removal process deletes all packages not explicitly required by either the OS or the software package being installed.

In the test environment, we use headless Sun4U systems based on SPARC technology and using PCI- based I/O cards. We remove more than half of the 62 packages included in the Solaris 9 OE Core cluster. The number of packages to remove depends upon the system being used. This package removal is automated with the minimize-iPlanetWS.fin script. This script is both application and OS-specific, because each software package and OS has slightly different requirements.

For package listings of all Solaris OE versions, refer to ";Minimizing the Sun ONE Web Server". Different hardware architectures, environments, and software packages may require other packages for your installations.

Additional configuration and hardening of the OS is not covered in this article. Refer to "References and Related Resources" for Sun BluePrints OnLine articles that cover these topics.

Using JumpStart Software to Configure the OS

Due to the repetitive nature of installations in this methodology, the basic network configuration steps for a server are automated. These include both required network and operating systems configurations. We use the Solaris Security Toolkit software to automate the creation of files such as /etc/defaultrouter and to configure services, thereby simplifying system configuration.

Installing and Configuring Software Packages

The final step in the methodology is to install and configure as much of the software package as possible. The level of automation implemented depends on how the software package is installed and the time available to automate the process. In the case of the Sun ONE Web Server software, which uses a curses-based installation process, the only automated task is to extract the source packages into an appropriate directory. Once extracted, the installation routines must be run manually to configure the server. The Solaris Security Toolkit install-iPlanetWS.fin script copies and extracts the software package into the /opt directory of the client.

Checking For Errors

Before installing software applications, it is important that you examine the installation logs on the server for any errors or configuration problems.

The JumpStart logs are located in the /var/sadm/system/logs directory. The begin.log contains all pre-OS installation operations and the finish.log contains all post-OS installation steps. Usually the finish.log contains the most pertinent messages. If you find errors, correct them and repeat the installation. Repeat this process until you resolve all errors.

Testing Software Installation

The software installation is tested manually by running the setup routine and selecting a default configuration for both the administrative and production web server ports. After a default configuration is defined, the startconsole command is used to start up the administration server. For additional information on how to automate the configuration process, refer to the product documentation.

In our test environment, this command, while successfully starting the Sun ONE Web Server software, also attempted to launch a local Netscape™ Communicator session. It failed because Netscape Communicator was not installed locally on the system. Rather than managing the installation locally, we used a remote Netscape Communicator session to configure the web server through the administration port.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information

To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.


Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.


If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information

Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.


This site is not directed to children under the age of 13.


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information

If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information

Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents

California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure

Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact

Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice

We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020