WorkShop Installation and Licensing Guide: 6 - Managing the Software

# Managing the Software | # 6 |

## 6.1 Product Software Functions and Commands

For product software, bug, or documentation information, review the README files located in the directory where you install the software.

### 6.1.1 Removing a Software Product

If you do not want to keep a software product that was already installed, use the following procedures to deinstall it:

  1. Become root by typing:

    `%` su

    `Password:` <root_password>``

  2. Determine the install location of the products you wish to deinstall, for example, /opt.

  3. Find all of the instances of the products that you wish to deinstall installed in that location by typing:

    `%` pkginfo -l | grep SPRO

    Most WorkShop package names start with `SPRO`, except NEOworks which begins with `SUNWO`. Be sure to get the correct version number, since there may be multiple instances of a package name. If there are two or more packages with the same name installed, the first instance will be called <package> and the second instance will be called <package>`.2`. Table C-3 on page C-87 lists all of the package configurations.

    If patches to a package have been installed, those will be named <package>.<number>. If you've installed several patches for a product, you may find that your list contains several similar package names, for example, `SPROlang`, `SPROlang.2`, and `SPROlang.3`.

    The product CD lists the packages comprising the products on the top-level file, `prod_config_file`. You can also refer to Appendix C, "WorkShop Products and Packages."

  4. Remove the package you do not want on the system by typing:

    `#` pkgrm`` <package_name>

  Remember that some software has interpackage dependencies.

  Package information displays; then, the script asks if you want to remove the package listed.

  5. Type y to remove the package listed.

    Otherwise, type `n` to keep the package.

  6. Remove each package using Step 4 and Step 5.

The `pkgrm` man page provides additional information about this function.

You must remove products using the `pkgrm` command. The `rm` command does not remove Developer Products packages; if the `rm` command is used, package information remains in the `pkginfo` database. Once all of the software packages are removed, you can reinstall software.

> Note - The pkgrm command does not work with the `SUNWOdbxD` package in Internet WorkShop.

### 6.1.2 Listing Installed Software

To list all of the packages, for products other than NEOworks, do the following:

| At a command prompt, type:

  `%` pkginfo | grep SPRO

  The `-l` option provides detailed package information, for example:
  `%` pkginfo -l SPROcc

| For NEOworks, type:

  `%` pkginfo | grep SUNWO

### 6.1.3 Elementary License Files on Product Servers

A product server may be served by one or more independent license servers. The product server will have one elementary license file corresponding to each license server. Each elementary license file contains the license server information and the product licenses.

## 6.2 Developing Distributed Objects

To develop distributed objects using NEOworks, you must first install Solaris NEO 2.0 to run the distributed object applications, including the object request broker (`ORB`). To install Solaris NEO, refer to the Solaris NEO Installation Guide.

Installing Solaris NEO starts the object request broker daemon (`ORBd`), invokes the NEO servers, and creates the initial web of objects needed by NEOworks. An active `ORBd`, invocable servers, and initial NEO objects are required by the WorkShop NEO installation.

If you need to NFS system-mount the NEO software, refer to the Solaris NEO Installation Guide for instructions.

To install JoeTM, you must also install JavaTM Development Kit 1.0, Solaris NEO 2.0, WorkShop NEO, and an HTTP server. Refer to your installation directory in `/usr/tmp/unbundled` for Joe installation steps in the `.log` file.

## 6.3 Software Installation Troubleshooting

### 6.3.1 Confirming `SUNWdthep` and `SPROesrt` Package Installation

If you customize your software installation and don't install all of the packages included with your WorkShop product, you may have difficulties running it. Check to make sure that both the `SUNWdthep` and `SPROesrt` packages are installed.

Confirm that `SUNWdthep` is installed, by typing:

`%` pkginfo -l SUNWdthep

Confirm that `SPROesrt` is installed, by typing:

`%` pkginfo -l SPROesrt

If either file is not installed, install it using Chapter 3, "Installing Product Software."

### 6.3.2 Using the SUNWlibC Package

The `SUNWlibC` package should be installed on each license and product server. This package consists of the shared libraries `libCso.5` that are installed in `/usr/lib`. You must install `SUNWlibC` to allow dynamic linking with `libC`. If this package is not installed, user applications link statically with `libC`.