test

Sun N1 Service Provisioning System User's Guide for OS Provisioning Plug-In 3.0

Installing the OS Provisioning Plug-In

Acquiring the OS Provisioning Plug-In

Acquiring the OS Provisioning Plug-In is a two-step process. First, you must add the package file that contains the OS Provisioning Plug-In JAR file to your system. Then you must import the OS Provisioning Plug-In JAR file. Perform the following steps to add the plug-in to your Master Server.

  1. Add the file containing the JAR file:

    The OS Provisioning Plug-In is packaged as a plug-in to the N1 Service Provisioning System software. The plug-in files for the OS Provisioning Plug-In are available from the N1 SPS 5.2 DVD or from the Sun Download Center.

    For instructions about how to add the plug-in package to your system, see the following procedures.

  2. Import the JAR file.

    Once the package file is added to your system, the OS Provisioning Plug-In is available for import from two different JAR files. Choose the correct file depending on your situation.

    • If you are importing the OS Provisioning Plug-In for the first time, acquire the n1-basedir/com.sun.n1osp/com.sun.n1osp_3.0.jar file.

    • If you have already imported the previous version of the OS Provisioning Plug-In, acquire the n1-basedir/com.sun.n1osp/Upgrade/com.sun.n1osp_2.0_3.0.jar file.

    For instructions about how to import the plug-in JAR file, see Adding the OS Provisioning Plug-In to N1 SPS.

Adding the OS Provisioning Plug-In for Solaris

The plug-in product name plug-in is contained in the SUNWspsosp package.

ProcedureTo Add the OS Provisioning Plug-In Package for Solaris

Steps

  1. In a terminal window, become superuser.

  2. Move to the directory containing the plug-in package.

  3. Type the following command and press Return.

    # pkgadd -d package_directory SUNWspsosp

    The standalone JAR file is in the /opt/SUNWn1sps/plugins/com.sun.n1osp/ directory. The upgrade JAR file is in the /opt/SUNWn1sps/plugins/com.sun.n1osp/Upgrade directory.

Adding the OS Provisioning Plug-In for Linux

The plug-in product name plug-in is contained in the sun-spsosp-3.0-1.noarch.rpm file.

ProcedureTo Add the OS Provisioning Plug-In Package for Linux

Steps

  1. In a terminal window, become superuser.

  2. Move to the directory containing the sun-spsosp-3.0-1.noarch.rpm file.

  3. Type the following command and press Return.

    # rpm -i package_directory sun-spsosp-3.0-1.noarch.rpm

    The standalone JAR file is in the /opt/sun/N1_Service_Provisioning_System/plugins/com.sun.n1osp/ directory. The upgrade JAR file is in the /opt/sun/N1_Service_Provisioning_System/plugins/com.sun.n1osp/Upgrade directory.

Adding the OS Provisioning Plug-In for Windows

The plug-in product name plug-in is contained in the sun-spsosp-3.0.msi Microsoft Installer (MSI) package file.

ProcedureTo Add the OS Provisioning Plug-In MSI File for Windows

Steps

  1. Move to the directory containing the sun-spsosp-3.0.msi file.

  2. Double-click the sun-spsosp-3.0.msi file.

    The Installer GUI starts. The JAR file is copied to the c:\Program Files\N1 Service Provisioning System\plugins\com.sun.n1osp directory.

Adding the OS Provisioning Plug-In to N1 SPS

To make a given plug-in known to the N1 SPS product, you need to import the plug-in. To import a plug-in, follow these steps as explained in detail in Chapter 5, Plug-In Administration, in Sun N1 Service Provisioning System 5.2 System Administration Guide.

  1. In the Administrative section of the N1 SPS browser interface main window, click Plug-ins.

  2. In the Action column of the Plug-ins page, click Import.

  3. Browse to the location of the JAR file.

  4. Click the Continue to Import button.

When the import completes successfully, a plug-in details page appears that shows you the objects that the plug-in provides.

You can also import a plug-in archive file from the command line.

ProcedureHow to Upgrade the OS Provisioning Plug-In

To upgrade the OS provisioning plug-in from version 2.0 to version 3.0, follow these steps:

Steps

  1. Upgrade the N1 SPS software to version 5.2, as explained in Chapter 10, Upgrading to the Sun N1 Service Provisioning System 5.2, in Sun N1 Service Provisioning System 5.2 Installation Guide.

  2. Acquire and import the com.sun.n1osp_2.0_3.0.jar file.

    For instructions about how to install the OS Provisioning Plug-In, see Installing the OS Provisioning Plug-In.

  3. Upgrade the OS provisioning (control) server.

    You must use the OS provisioning plug-in 3.0 software to recreate any existing OS provisioning servers. See Creating the OS Provisioning Server

  4. Upgrade the OS image servers in your environment.

    You must use the OS provisioning plug-in 3.0 software to recreate any existing OS image servers.

    Note –

    When you recreate the boot and install servers, you must use the value that you used previously for the installPath variable. If the previous installPath variable value is no longer valid, you must create a new boot and install server with the valid installPath variable value.

  5. Change the variable for the remote agent in any existing OS profiles.

    The product_version_spsra variable in the profile must reflect the current N1 SPS RA software version. Edit any existing profiles and change the value of the product_version_spsra variable to 5.2. For more information about this variable, see Component Variables for Solaris Remote Agents.

Troubleshooting

Using the OS Provisioning Plug-In 3.0 With the N1 SPS 5.1 Release

Starting with the release N1 SPS 5.2 release, the OS Provisioning Plug-In 3.0 uses default values for N1 SPS 5.2 paths. If you are using the N1 SPS 5.1 release, the OS Provisioning Plug-In, you must edit the sps_cli variable value in your plans to enable the OS Provisioning Plug-In 3.0. Edit this value in the following procedures.

ProcedureHow to Access Previous Versions of a Component

When you upgrade to a new version of a plug-in, the Common Tasks page for the plug-in is updated to provide links to components that are installed with the new plug-in version. This feature enables you to easily view components that contain the most current features and improvements. Components that rely on old functionality are not linked to from the Common Tasks page.

If you have trouble finding a component that you previously installed, the component was likely created from the previous version of the plug-in. Follow these steps to view or work with a previous version of the component:

Steps

  1. Click the appropriate component procedure on the Common Tasks page.

    The Component Detail page appears.

  2. On the Component Details page, click Version History.

    A list of components and versions appears.

  3. Click the appropriate link.

    • To perform a task with a component, click the version number or the Details link that applies to the component that you want to use.

    • To view where a component is installed, click Where Installed.