This chapter provides information about installing and configuring the Windows 2000 plug-in. The chapter contains the following information:
Acquiring the Windows 2000 plug-in is a two-step process. First, you must add the package file that contains the Windows 2000 plug-in JAR file to your system. Then you must import the Windows 2000 plug-in JAR file.
The Windows 2000 plug-in is packaged as a plug-in to the Sun N1 Service Provisioning System software. Plug-ins are packaged in JavaTM Archive (JAR) files. The Windows 2000 plug-in files are available from the Sun N1 Service Provisioning System Supplement CD or from the Sun Download Center:
Once the package file is added to your system, the Windows 2000 Plug-In is available for import from two different JAR files. Choose the correct file depending on your situation.
If you are importing the Windows 2000 Plug-In for the first time, acquire the com.sun.windows_3.0.jar file.
If you have already imported the previous version of the Windows 2000 Plug-In, acquire the com.sun.windows_2.0_3.0.jar file.
Add the file containing the JAR file.
Import the JAR file – Importing the Windows 2000 Plug-In to the Sun N1 Service Provisioning System
The Windows 2000 plug-in is contained in the SUNWspswin package.
In a terminal window, become superuser.
Move to the directory containing the plug–in package.
Type the following command and press Return.
# pkgadd -d . SUNWspswin
The standalone JAR file is in the /opt/SUNWn1sps/plugins/com.sun.windows/ directory. The upgrade JAR file is in the /opt/SUNWn1sps/plugins/com.sun.windows/Upgrade directory.
The Windows 2000 plug-in is contained in the SUNWspswin.rpm file.
In a terminal window, become superuser.
Move to the directory containing the sun-spswin-3.0-1.noarch.rpm file.
Type the following command and press Return.
# rpm –i sun-spswin-3.0-1.noarch.rpm
The standalone JAR file is in the /opt/sun/N1_Service_Provisioning_System/plugins/com.sun.windows/ directory. The upgrade JAR file is in the /opt/sun/N1_Service_Provisioning_System/plugins/com.sun.windows/Upgrade directory.
The Windows 2000 plug-in is contained in the SUNWspswin.msi file.
Move to the directory containing the SUNWspswin.msi file.
Double-click the SUNWspswin.msi file.
The Installer GUI start. The JAR file is copied to the C:\Program Files\N1 Service Provisioning System\plugins\com.sun.windows directory.
To make a given plug-in known to the Sun N1 Service Provisioning System product, you need to import the plug-in to the Master Server. If you have already imported a previous version of the Windows 2000 Plug-In, you need to upgrade to the new plug-in.
To import or upgrade 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
In the Administrative section of the browser interface main window, click Plug-ins.
In the Action column of the Plug-ins page, click Import.
Navigate to the location of the JAR file.
If you are importing the Windows 2000 Plug-In for the first time, select the com.sun.windows_3.0.jar file.
If you have already imported a previous version of the Windows 2000 Plug-In, select the com.sun.windows_2.0_3.0.jar file.
Click the Continue to Import button.
When the import completes successfully, a plug-in details page appears and shows you the objects that the plug-in provides.
You can also import a plug-in by using the command line.
To import a plug-in file from the CLI, type:
% cr_cli -cmd plg.p.add -path plugin-filename -u username -p password |
If you are importing the Windows 2000 Plug-In for the first time, plugin-filename is com.sun.windows_3.0.jar.
If you have already imported the previous version of the Windows 2000 Plug-In, plugin-filename is com.sun.windows_2.0_3.0.jar.
You should grant the following permissions to the specified folders from the provisioning software interface:
/com/sun/windows folder
Grant allow on host set permission to all users who will perform deployments that use the Windows 2000 Plug-In components on hosts that the users are expected to deploy to. Also grant this permission to all users who are expected to prepare Windows hosts on the hosts they are expected to prepare.
Grant run component procedures permission only as needed. This permission is recommended only in non-production systems, or for trusted admin users. This permission allows services of the com.sun.windows#services system service to be directly executed. These services include controls to start and stop services, execute batch and cscript files, and manage MSIs.
/com/sun/windows/jacozoom folder
Grant allow on host set permission to all users who will be expected to prepare windows hosts on the hosts they are expected to prepare.
The following information is related to viewing previous versions of components after upgrading.
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:
Click the appropriate component procedure on the Common Tasks page.
The Component Detail page appears.
On the Component Details page, click Version History.
A list of components and versions appears.
Click the appropriate link.
Check the SunSolve site for available patches for the Windows 2000 plug-in. To apply the patch, follow the instructions in the patch README file.