This chapter explains how to install and configure the BEA WebLogic plug-in. The chapter contains the following information:
Acquiring the BEA WebLogic plug-in is a two-step process. First, you must add the package file that contains the BEA WebLogic plug-in JAR file to your system. Then you must import the BEA WebLogic plug-in JAR file.
The BEA WebLogic 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 plug-in files for the BEA WebLogic Plug-In 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 BEA WebLogic plug-in is available for import from two different JAR files. Choose the correct file depending on your situation.
If you are importing the BEA WebLogic Plug-In for the first time, acquire the com.sun.weblogic_2.0.jar file.
If you have already imported the previous version of the BEA WebLogic Plug-In, acquire the com.sun.weblogic_1.1_2.0.jar file.
Add the package containing the JAR file.
Import the JAR file – Importing the BEA WebLogic Plug-In to the Sun N1 Service Provisioning System
The BEA WebLogic plug-in is contained in the SUNWspswlg 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 . SUNWspswlg
The standalone JAR file is in the /opt/SUNWn1sps/plugins/com.sun.weblogic/ directory. The upgrade JAR file is in the /opt/SUNWn1sps/plugins/com.sun.weblogic/Upgrade directory.
The BEA WebLogic plug-in is contained in the sun-spswlg-2.0-1.noarch.rpm file.
In a terminal window, become superuser.
Move to the directory containing the sun-spswlg-2.0-1.noarch.rpm file.
Type the following command and press Return.
# rpm –i sun-spswlg-2.0-1.noarch.rpm
The standalone JAR file is in the /opt/sun/N1_Service_Provisioning_System/plugins/com.sun.weblogic/ directory. The upgrade JAR file is in the /opt/sun/N1_Service_Provisioning_System/plugins/com.sun.weblogic/Upgrade directory.
The BEA WebLogic plug-in is contained in the sun-spswlg-2.0.msi file.
Move to the directory containing the sun-spswlg-2.0.msi file.
Double-click the sun-spswlg-2.0.msi file.
The Installer GUI start. The JAR file is copies to the C:\Program Files\N1 Service Provisioning System\plugins\com.sun.weblogic directory.
To make a given plug-in known to the Sun N1 Service Provisioning System, you need to import the plug-in to the Master Server. If you have already imported a previous version of the BEA WebLogic 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.
Navigaet to the location of the JAR file.
If you are importing the BEA WebLogic Plug-In for the first time, select the com.sun.weblogic_2.0.jar file.
If you have already imported a previous version of the BEA WebLogic Plug-In, select the com.sun.weblogic_1.1_2.0.jar file.
Click the Continue to Import button.
When the import complete 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 BEA WebLogic Plug-In for the first time, plugin-filename is com.sun.weblogic_2.0.jar.
If you have already imported the previous version of the BEA WebLogic Plug-In, plugin-filename is com.sun.weblogic_1.1_2.0.jar.
Information about customizing the BEA WebLogic plug-in for your environment is provided in the readme.txt file in the com.sun.weblogic_2.0.jar or com.sun.weblogic_1.1_2.0.jar files.
Check the SunSolve site for available patches for the BEA WebLogic plug-in. To apply the patch, follow the instructions in the patch README file.