The Integrated Solutions Console bundle contains the following:

Installation options

The ISC installation program provides a graphical user interface. This installer comes with the following predefined set of configurations.

• You can use the installation program to install the runtime and/or toolkit which includes, Developer Information Center, samples, plug-in for Rational Application Developer etc or any combination of those features, depending on your operating system.
  
• If you select the option to install the Integrated Solutions Console runtime, the following configuration will be used:
  • Application Server - Embedded version of WebSphere Application Server bundled with ISC installer
  • User Registry - Embedded Cloudscape packaged with ISC installer
  • Security - Database only Security

ISC Custom installer can be used for selecting different options during ISC Runtime installation

Software Prerequisites
Before you install Integrated Solutions Console components, ensure that your system meets the prerequisites for the type of installation you will perform.

The following components can be installed by the installer for Integrated Solutions Console.

• Developer Information Center
• Sample Console Applications
• Integrated Solutions Console Runtime
• Integrated Solutions Console plug-in for Rational Application Developer
• SVG Chart Generator Plug-in for Rational Application Developer

The toolkit plug-ins for Rational Application Developer are available only on Windows and Linux platforms. The software requirements for all components are described in the following sections:

Toolkit software requirements
This describes requirements for all components except for the console runtime.

The plug-in for Rational Application Developer requires that JVM 1.4.2 and Rational Application Developer 6.0.0.2 are already installed.

Application development tools

Rational Application Developer Version 6.0

Java

Toolkit components require JVM 1.4.2

Globalization Support

Translated into all group 1 languages.

Note: Integrated Solutions Console is enabled to support bidrectional text. However, the console is not translated into any bidirectional languages at this time.

Runtime software requirements

This section lists the software requirements for installing and running the console runtime.

• Embedded components
• Supported Web servers
• Eclipse Help System
• Java
• Globalization Support
• Tested Software

Embedded components

Platform	Requirement
Solaris, AIX, Linux, and Windows	Cloudscape Network Server 5.1.60.24 IBM Eclipse System 3.0.1 Embedded Version of IBM WebSphere Application Server - Express 6.0.2 WebSphere Portal Technology 5.1.0.1 Presentation Services Web Component Library (WCL) 5.0

Supported Web servers

Platform	Requirement
Solaris, AIX, Linux, and Windows	The WebSphere Application Server internal HTTP server will always be used.

Eclipse Help System

To serve the console help, Integrated Solutions Console uses Eclipse Help System. This is setup during installation.

Platform	Requirement
Solaris, AIX, Linux, and Windows	Eclipse Help System V3.0.1

Java

JVM version 1.4.2 is required

Globalization support

Integrated Solutions Console is developed in English and translated to the following languages:

Group 1	Group 2 (partial)
Simplified Chinese Traditional Chinese Japanese Korean French German Italian Spanish Brazilian Portuguese	Czech Hungarian Polish Russian

Note: Integrated Solutions Console is enabled to support Unicode and bidrectional text. However, the console is not translated into any bidirectional languages at this time.

Tested Software

Note 1: Please reference the Abstract User Interface Markup Language (AUIML), Presentation Services Web Component Library (PS WCL), Scalable Vector Graphics (SVG), Java Server Faces (JSF), Java Widget Library (JWL), or other technology support statements for their support of IBM Integrated Solutions Console V6.0.

Note 2: IBM Integrated Solutions Console V6.0 does not support VMWare.

Getting Started

The Integrated Solutions Console can be accessed by invoking a standard web browser:

1. The Integrated Solutions Console requires the ISC_Portal server to be running. See section "Stopping and starting the server" below.
   
2. Use your browser to open the Integrated Solutions Console URL: http://your.server.name:isc_port/ibm/console
   where your.server.name is the host name for the Integrated Solutions Console installation and isc_port is the port that you specified during the installation. This port number can be found in the C:\Program Files\IBM\ISC\Toolkit\Runtime\isc.properties file having one property called PortalServer.Port=port value The default port is 8421. E.g.: http://localhost:8421/ibm/console.

Stopping and starting the server

The Integrated Solutions Console installation program automatically starts Integrated Solutions Console server and its help system after a successful installation. If the machine is rebooted, the ISC_Portal server will no longer be running. The Integrated Solutions Console can not function if ISC_Portal server is not running.

• AIX, Linux, and Solaris systems
• Windows systems

The following table lists the commands for starting and stopping the servers on AIX, Linux, and Solaris systems. See "Alternate command syntax" in the Console Developer Information Center for a description of alternate syntax for the stopISC command on systems where WebSphere Application Server security with an LDAP server is enabled.

The following table lists the commands for starting and stopping the servers on Windows systems. See "Alternate command syntax" in the Console Developer Information Center for a description of alternate syntax for the stopISC command on systems where WebSphere Application Server security with an LDAP server is enabled.

1. Use a Web browser to open the Integrated Solutions Console URL one of the following URLs:
   • http://host_name:isc_port/ibm/console
   • http://localhost:isc_port/ibm/console
   • http://127.0.0.1:isc_port/ibm/console
   • The variables have the following meanings:
   • host_name is the host name for the Integrated Solutions Console installation.
   • isc_port is the port for Integrated Solutions Console. You must specify the protocol name (http or https) in the URL, because the URL contains a port number. For AIX, Linux, Solaris and Windows installations, the default port is 8421.
2. Log in as the Integrated Solutions Console administrator. Specify the user ID that was configured during the Toolkit installation. The default user ID is iscadmin.
3. Click Console Settings on the navigation tree.
4. Click User and Group Management. The page is displayed in the work area.
5. To view help for the portlet on the page, click the portlet help icon (the ? symbol). The help topic Manage users and groups is displayed in a separate browser window. Close the help window.
6. On the Integrated Solutions Console toolbar, click Help. A separate window is launched and displays a navigation frame for accessing the Console Basics help set.
7. To log out of the console, click Log off on the toolbar. The Login page is displayed.
8. If the verification procedure was not successful, see Solving installation problems.

If you selected the option to install the Developer Information Center or the plug-ins for Rational Application Developer, see Accessing the developer documentation to verify those installations.

If you installed the Developer Information Center, perform the following procedure to view that documentation:

1. Use your Web browser to open http://your.server.name:infocenter_port/help, where your.server.name is the fully-qualified host name for the Integrated Solutions Console installation and infocenter_port is the port for the Eclipse-based help system that hosts the Developer Information Center. The default port is 8430.
2. In the navigation tree, click Console Developer Information Center.
3. To view a topic, click the topic in the navigation tree or use the Search function to find a topic.

The Integrated Solutions Console plug-in for Rational Application Developer provides documentation on using the plug-in wizard and the component.xml editor. If you installed the plug-in, perform the following procedure to view that documentation:

1. Open Rational Application Developer.
2. Click Help > Help Contents on the toolbar. The help displays in a separate window.
3. In the navigation tree, click Integrated Solutions Console documentation.
4. Click the topic Getting started.

The SVG Chart Generator plug-in for Rational Application Developer provides documentation on using the widgets to add charts to your Web application. If you installed the plug-in, you can find the documentation in the /wstools subdirectory of Rational Application Developer. Look for the Eclipse plug-in, com.ibm.etools.svgwidgets.doc_1.2.0.


Deploying the samples

The sample console modules illustrate how to use the Integrated Solutions Console APIs, create multi-language console modules, create different page layouts, secure access to pages, and perform other console module development tasks. You can select the option to install the sample console modules during the Toolkit installation. If you select that option, the program copies the samples to a subdirectory named samples on your system.

To view and use the a sample, you must deploy the sample to a system where the Integrated Solutions Console runtime is installed. For instructions on deploying the samples, see the topic "Sample console modules" in the Developer Information Center.

Solving installation problems

If you have a problem with installing Integrated Solutions Console:

1. Verify that you have followed all of the installation instructions.
2. Ensure that the correct prerequisites are installed.
3. Ensure that all of the settings (such as user IDs and passwords) that you specified are correct.
4. Check the installation log files for error messages.Check the log files related to ISCRuntime and ISCToolkit in your %temp% folder.
5. If you can't solve the problem, try to uninstall Integrated Solutions Console and then install it again. Please note that if the installation has failed, un-installation could also fail. Please refer to Solving Uninstallation problems to manually remove ISC. (The ISC uninstaller should still be invoked, before manual delete, to clean up the Solution Install Repository)

Installation log files

The table describes the log files created during installations and uninstalls and recommends when to check the file for information that might assist in troubleshooting problems. The location of the log files varies according to the operating system:

• For AIX, Linux, Solaris, and Windows systems, the log files are written to the operating system temporary directory, which is the value of the system variable %TEMP% on Windows systems, and /tmp on the other systems. Depending on the operating system, these files might not be saved after the system is shutdown.

File name	Description	Problem symptoms
ISCToolkitInstall.log	Contains messages for the part of the Toolkit installation that involves installing the samples and Developer Information Center.	Check this log if the installation failed. Start at the end of the log and read backwards until you find the command that failed (as opposed to the that reports the failure or lines that report cleanup). If the failing command sent output to another log file, open that file, go to the end of the file, and repeat the same procedure that you used with the first log file.
ISCToolkit.rsp	Contains settings that you specified when you ran the Toolkit installation program.	If the installation was not successful, check this log to verify that the settings are correct.
ISCToolkitUninstall.log	Contains trace output for the runtime uninstall program.	Check this log if the Toolkit uninstall failed. Start at the end of the log and read backwards until you find the command that failed (as opposed to the lines that reports the failure or lines that report cleanup). If the failing command sent output to another log file, open that file, go to the end of the file, and repeat the same procedure that you used with the first log file.
ISCRuntimeInstall.log	Contains messages for the runtime installation, which is part of the Toolkit installation if you select that option.	Check this log if the installation failed. Look for messages that indicate that a command failed.
ISCRuntime.rsp	Contains settings that you specified for the runtime installation.	If the installation was not successful, check this log to verify that the settings are correct.
ISCRuntimeUninstall.log	Contains trace output for the runtime uninstall program.	Check this log if the runtime uninstall failed. Look for messages that indicate that a command failed.
ISCPreInstallConfigTask.log	Contains messages that were recorded during preliminary configuration steps before Integrated Solutions Console is installed..
ISCPostInstallConfigTask.log	Contains messages that were recorded during system configuration after Integrated Solutions Console is installed.
PortalBasicConfig.log
ISCSetupISCXml.log
ISCUpdatePorts.log
wpsinstalllog.txt
ISCDeploy_ManagePrincipals.log
ISCEnableSecurityLDAPNew.log
ISCDeploy_ResourceView.log
PortalDeployConfig.log
ISCDeploy_Tracing.log

Installation return codes

The Toolkit installation program invokes other processes. Two of those processes issue return codes: ISCRuntime and ISCAction. The return codes appear in the log files along with messages from the processes.

ISCRuntime returns 0 for a successful completion. Any other return code indicates that the process failed.

ISCAction returns a two-digit return code. The following table lists the meaning of each digit in the code. The following scenarios are examples of scenarios for ISCAction:

• If you select the option to use an existing WebSphere Application Server installation, the return code will be 55 if Integrated Solutions Console is not already installed on that WebSphere Application Server and security is not enabled on the server.
• The return code 78 indicates that the current version of Integrated Solutions Console is already installed on the specified WebSphere Application Server and LDAP security is enabled for that server.
• Return 9x and x9 indicate an error that should be debugged.

1. Stop Integrated Solutions Console and the help system as mentioned above.
2. Clean the system temporary directory:
   1. Change to the system temporary directory. The temporary directory is the value of the operating system variable $TEMP or %TEMP%.
   2. Save a copy of the following files in the temporary directory:
          - ISCRuntimeInstall.log
          - ISCRuntime.rsp
          - ISCRuntimeUninstall.log
          - All of the Portal*.log files
   3. In the temporary directory, delete all of the files and the directories that begin with the string ISC, such as ISCRuntime.rsp, ISC_TEMP, ISCToolkitInstall.log,PortalInit.log, and PortalSetupWAS.log.
3. Clean the registry that Installer creates :
   1. Locate the file vpd.properties.
            - On Windows systems, search the system directory (such as C:\WINNT\vpd.properties).
            - On AIX, Linux search for the file. There might be multiple vpd.properties files on an AIX system. If there are multiple copies, be sure to edit all  copies of the file when you perform the edit step.
   2. Save a copy of the vpd.properties file.
   3. Use a text editor to open the vpd.properties file. Use an editor that does not wrap lines so that you can easily isolate single lines for removal. Setting the editor to use a monospace font will make it easier to see the file structure.
   4. Delete each line that contains the string your_isc_root, where your_isc_root is the root directory of your Toolkit installation. If there are no remaining lines in vpd.properties, leave the file empty or delete it.
   5. Delete the directory your_isc_root.
           - If you delete the directory successfully, the Toolkit has been uninstalled.  You are finished.
           - If the operating system is unable to do delete the directory, continue with the next step.
   6. To stop all Java processes for Integrated Solutions Console:
      1. For AIX, Linux, and Solaris systems:
             - Issue the following command to find the processes that are using    
               your_isc_root/AppServer/java/bin/java.exe:
                 ps -ef | grep java
             - Kill all of those processes.
      2. For Windows systems:
             - Open Windows Task Manager.
             - Locate the Java processes and end those processes. 
   7.  Delete the directory your_isc_root.

Documentation

The documentation for the Integratd Solutions Console Builder is provided by the Eclipse online help system. Online help is accessed from the main toolbar menu: Help -> Help Contents

Limitations and Restrictions

Please check the list of supported platforms in the download site before attempting install.
Changing the hostname after installation sometimes creates problems.

Systems with multiple network adapters
In certain configurations on Windows machines with multiple network interface cards, the Integrated Solutions Console Toolkit installation program can fail due to the system returning a different hostname than is expected. If you plan to install the Toolkit on a machine that has multiple network adapters, perform the following procedure to avoid this problem:

a. In Windows, click Settings > Control Panel. The Control Panel window is displayed.
b. Click Network and Dial-up Connections. The window is displayed.
c. On the main menu, click Advanced > Advanced Settings. The Advanced Settings window is displayed.
d. In the list of Connections, verify that the network adapter that you want to use is first in the list. If adapter is not first, select the adapter and then use the up arrow key to move it to the top of the list.

Also note the following restrictions:

• The toolkit plug-ins for Rational Application Developer are available only on Windows and Linux(Intel) platforms.
• You cannot use the Toolkit installation program to upgrade an existing console runtime installation to Version 6.0.
• You cannot install the console runtime on a WebSphere Application Server where WebSphere Portal is already installed.

Known Issues:

• Un-installation on AIX does not clean up the system (Refer the section on steps to clean up the system manually)
• Gnu Tar 1.13 needs to be installed on AIX and Solaris machines.

User Permissions:
The user invoking the installer should have Administrator (on windows system)/root (on Unix Systems) permissions.

Firewall Settings:
If you have a firewall enabled, you must configure the firewall to accept connections to the ports that are established during the installation wizard to prevent installation failure.

Java
The installer needs SUN/IBM Java 1.4.2 to successfully install the package. The installer has a bundled IBM JRE 1.4.2. If Java 1.4.2 is not present on  the system, the installer will put the bundled java on the machine and this will be used during installation.

IBM JRE 1.4.2 will be installed at the following location :

Windows : C:/Program Files/IBM/Java142/jre
Solaris : /usr/jre142
Linux : /usr/jre142
AIX : /usr/java142

NOTE: The installed bundles use Java 1.4.2. Please do not delete the java after the package is installed.

Disk Space Requirements

AIX systems

To install the console on a system for the first time and use the WebSphere Application Server that is embedded in the console runtime, you need:

• 1521 MB to satisfy the installation program disk space check
• An additional 727 MB in the /tmp directory (which is also checked during the installation including 48 MB for JRE
• 780 MB for the completed installation

To install the console on a separate WebSphere Application Server installation, you need:

• 1521 MB (which consists of 40 MB in the WebSphere Application Server directory and 796 MB in the root directory where Integrated Solutions Console will be installed and distributables a well as uninstaller) to satisfy the installation program disk space check
• An additional 649 MB in the /tmp directory (which is also checked during the installation including 48 MB for JRE
• 780 MB for the completed installation

Linux Intel systems

To install the console on a system for the first time and use the WebSphere Application Server that is embedded in the console runtime, you need:

• 1521 MB to satisfy the installation program disk space check
• An additional 727 MB in the /tmp directory (which is also checked during the installation including 48 MB for JRE
• 780 MB for the completed installation

To install the console on a separate WebSphere Application Server installation, you need:

• 1521 MB (which consists of 40 MB in the WebSphere Application Server directory and 796 MB in the root directory where Integrated Solutions Console will be installed) to satisfy the installation program disk space check
• An additional 649 MB in the /tmp directory (which is also checked during the installation including 48 MB for JRE
• 780 MB for the completed installation

Solaris systems

To install the console on a system for the first time and use the WebSphere Application Server that is embedded in the console runtime, you need:

• 1521 MB to satisfy the installation program disk space check
• An additional 727 MB in the /tmp directory (which is also checked during the installation including 48 MB for JRE
• 780 MB for the completed installation

To install the console on a separate WebSphere Application Server installation, you need:

• 1521 MB (which consists of 40 MB in the WebSphere Application Server directory and 796 MB in the root directory where Integrated Solutions Console will be installed) to satisfy the installation program disk space check
• An additional 649 MB in the /tmp directory (which is also checked during the installation including 48 MB for JRE
• 780 MB for the completed installation

Windows systems

To install the console on a system for the first time and use the WebSphere Application Server that is embedded in the console runtime, you need:

• 1521 MB to satisfy the installation program disk space check
• An additional 727 MB in the temporary directory (the value of the system variable %TEMP%), which is also checked during the installation including 48 MB for JRE
• 780 MB for the completed installation

To install the console on a separate WebSphere Application Server installation, you need:

• 1521 MB (which consists of 40 MB in the WebSphere Application Server directory and 796 MB in the root directory where Integrated Solutions Console will be installed) to satisfy the installation program disk space check
• An additional 649 MB in the temporary directory (the value of the system variable %TEMP%), which is also checked during the installation including 48 MB for JRE
• 780 MB for the completed installation

OS/400 systems

The console runtime installation program does not check for available disk space during the installations on OS/400 systems.

To install the console on an existing WebSphere Application Server - Express, you need:

• 800 MB for the installed Integrated Solutions Console runtime. This value does not include the disk space required to install the prerequisite OS/400 software.
• An additional 28 MB of temporary space is needed during the installation.

To install the console on an existing WebSphere Application Server Base, you need:

• 835 MB for the installed Integrated Solutions Console runtime. This value does not include the disk space required to install the prerequisite OS/400 software.
• An additional 28 MB of temporary space is needed during the installation.

Temporary disk space: An additional 952 MB during the installation.

Related Packages

Problem Determination Scenario bundle - An Integrated Solutions Console component provided in the Autonomic Computing Toolkit to support the Problem Determination scenario (a self-healing scenario).
Solution Installation and Deployment Samples Scenario bundle - An Integrated Solutions Console component demonstrating various features of the Solution Installation architecture (a self-configuring scenario).

Instructions for a manual uninstall

If you need to clean up your system from an unsuccessful installation or if the Toolkit uninstall program was not successful, follow the instructions in this section.

To perform a manual uninstall of the Toolkit:

1. To uninstall the console runtime, perform one of the following procedures:
   1. Stop the console server only. If the command is not successful, try ending the Java processes that correspond to the console server.
   2. Stop the console help server only. If the command is not successful, try ending the Java processes that correspond to the console help server.
   3. If the console runtime uses a separate WebSphere Application Server instead of the embedded application server, delete the WebSphere Application Server profile that contains Integrated Solutions Console. To delete the profile, issue one of the following commands:
      • For AIX, Linux, and Solaris systems, run the following command:

        your_isc_runtime_root/AppServer/bin/wasprofile.sh -delete -profileName profile_name

      • For Windows systems, run the following command:

        your_isc_runtime_root\AppServer\bin\wasprofile.bat -delete -profileName profile_name

   4. Delete the root directory for the Integrated Solutions Console runtime. If you cannot delete the directory, verify that all of the Java processes for the console server and the console help server have been ended.
   5. Edit the vpd.properties file:
      1. Locate the file vpd.properties.
         • On AIX, Linux, and Solaris systems, search for the file. There might be multiple vpd.properties files on an AIX system. If there are multiple copies, be sure to edit all copies of the file when you perform the edit step.
         • On Windows systems, search the system directory (such as C:\WINNT\vpd.properties).
      2. Save a copy of the vpd.properties file.
      3. Use a text editor to open the vpd.properties file. Use an editor that does not wrap lines so that you can easily isolate single lines for removal. Setting the editor to use a monospace font will make it easier to see the file structure.
      4. Delete each line that refers to the path your_isc_runtime_root, where your_isc_runtime_root is the root directory for the Integrated Solutions Console runtime. If there are no remaining lines in vpd.properties, leave the file empty or delete it.
2. For AIX, Linux, and Solaris systems: If the console runtime was installed and the system was configured to automatically start the console and console server when the system restarted, edit the operating system file /etc/inittab to remove the following line:

   service_ID:23:boot:your_isc_root/PortalServer/bin/startISC.sh ISC_Portal 

   where service_ID is the name of the service for the console server. That name was specified when the console was installed.

3. For Windows systems: If the console runtime was installed and the system was configured to automatically start the console and console server when the system restarted, run the following commands to manually disable that service. Each command must be entered on a single line.

   1. application_server_root\bin\wasservice.exe -remove console_service_name

   2. your_isc_root\PortalServer\ISCEclipse\EclipseSvc.exe -delete
         help_service_name your_isc_root\PortalServer\ISCEclipse

   The variables have the following meanings:

   • application_server_root is the root directory of the WebSphere Application Server. If the console uses the embedded application server, the application server root directory is your_isc_root\AppServer.
   • console_service_name is the name of the service for the console server. That name was specified when the console was installed.
   • help_service_name is the name of the service for the console help server. That name was specified when the console was installed.
4. To uninstall the plug-ins for Rational Application Developer, use Update Manager in Rational Application Developer.
5. To uninstall the Developer Information Center, perform the following steps:
   1. Stop the server for the Developer Information Center.
   2. To clean the registry that InstallShield for Multiplatforms uses:
      1. Locate the file vpd.properties.
         • On AIX, Linux, and Solaris systems, search for the file. There might be multiple vpd.properties files on an AIX system. If there are multiple copies, be sure to edit all copies of the file when you perform the edit step.
         • On Windows systems, search the system directory (such as C:\WINNT\vpd.properties).
      2. Save a copy of the vpd.properties file.
      3. Use a text editor to open the vpd.properties file. Use an editor that does not wrap lines so that you can easily isolate single lines for removal. Setting the editor to use a monospace font will make it easier to see the file structure.
      4. Delete each line that refers to the path your_isc_toolkit_root/Eclipse. If there are no remaining lines in vpd.properties, leave the file empty or delete it.
   3. Delete the directory Eclipse subdirectory under the Toolkit root directory.
6. To remove the files for the undeployed samples, perform the following steps:
   1. To clean the registry that InstallShield for Multiplatforms uses:
      1. Locate the file vpd.properties.
         • On AIX, Linux, and Solaris systems, search for the file. There might be multiple vpd.properties files on an AIX system. If there are multiple copies, be sure to edit all copies of the file when you perform the edit step.
         • On Windows systems, search the system directory (such as C:\WINNT\vpd.properties).
      2. Save a copy of the vpd.properties file.
      3. Use a text editor to open the vpd.properties file. Use an editor that does not wrap lines so that you can easily isolate single lines for removal. Setting the editor to use a monospace font will make it easier to see the file structure.
      4. Delete each line that refers to the path your_isc_toolkit_root/samples. If there are no remaining lines in vpd.properties, leave the file empty or delete it.
   2. Delete the samples subdirectory under the Toolkit root directory.

Manually uninstalling the runtime from the embedded application server

If the install program fails and the console installation uses the application server that is embedded in the console runtime, you can try to manually remove the Integrated Solutions Console runtime and then install again. To manually remove the console runtime, perform the following steps:

1. Open a command window or go to a command prompt.
2. Stop the console server (which is the application server named ISC_Portal).
3. Stop the application server named server1 by issuing one of the following commands:
   • For installations on AIX, Linux, and Solaris systems, issue the following command (on a single line):

     your_isc_root/AppServer/bin/stopServer.sh server1 -username application_server_administrator
       -password application_server_password

   • For installations on Windows systems, issue the following command (on a single line):

     your_isc_root\AppServer\bin\stopServer.bat server1 -username application_server_administrator
       -password application_server_password

4. Stop the console help server.
5. To clean the registry that InstallShield for Multiplatforms uses:
   1. Locate the file vpd.properties.
      • On AIX, Linux, and Solaris systems, search for the file. There might be multiple vpd.properties files on an AIX system. If there are multiple copies, be sure to edit all copies of the file when you perform the edit step.
      • On Windows systems, search the system directory (such as C:\WINNT\vpd.properties).
   2. Save a copy of the vpd.properties file.
   3. Use a text editor to open the vpd.properties file. Use an editor that does not wrap lines so that you can easily isolate single lines for removal. Setting the editor to use a monospace font will make it easier to see the file structure.
   4. Delete each line that refers to the path for the root directory of the console runtime. If there are no remaining lines in vpd.properties, leave the file empty or delete it.
6. If the system was configured to automatically start the console and console server when the system restarted, perform one of the following steps to manually disable that function.
   • For AIX, Linux, and Solaris systems: If the console runtime was installed and the system was configured to automatically start the console and console server when the system restarted, edit the operating system file /etc/inittab to remove the following line:

     service_ID:23:boot:your_isc_root/PortalServer/bin/startISC.sh ISC_Portal

     The variables have the following meanings:

     • service_ID is the name of the service for the console server. That name was specified when the console was installed.
     • your_isc_runtime_root is the root directory of the Integrated Solutions Console runtime.
   • For Windows systems, issue the following commands, each on a single line:

     1. application_server_root\bin\wasservice.exe -remove console_service_name

     2. your_isc_runtime_root\PortalServer\ISCEclipse\EclipseSvc.exe -delete
           help_service_name your_isc_runtime_root\PortalServer\ISCEclipse

     The variables have the following meanings:

     • application_server_root is the root directory of the separate WebSphere Application Server installation that the console uses.
     • your_isc_runtime_root is the root directory of the Integrated Solutions Console runtime.
     • console_service_name is the name of the service for the console server. That name was specified when the console was installed.
     • help_service_name is the name of the service for the console help server. That name was specified when the console was installed.
7. If the system was configured to use Cloudscape Network Server, perform one of the following steps to manually remove the Cloudscape Network Server service.
   • For AIX, Linux, and Solaris systems, run the following command (all on one line);

     java -cp your_isc_root/CloudscapeNS/isc.install.util.jar
                            com.ibm.isc.install.util.CSNSUtilities deleteCSNSUnixService csns_servername

     where csns_servername is the name of the Cloudscape Network Server, for example, DS01.

   • For Windows systems, issue the following commands:

     1. your_isc_root\CloudscapeNS\CloudscapeNetworkSvc.exe -stop csns_service_ID

     2. your_isc_root\CloudscapeNS\CloudscapeNetworkSvc.exe -delete csns_service_ID

     where csns_service_ID is the name of the service for the Cloudscape Network Server database. That name was specified when the console was installed.

8. Delete the root directory for the console runtime.
   • If you delete the directory successfully, the runtime has been uninstalled. You are finished.
   • If the operating system is unable to delete the directory, continue with the next steps.
9. Note: Complete this step if you were not able to complete the previous step successfully.
   Stop all Java processes for Integrated Solutions Console by performing the following steps.
   1. For AIX, Linux, and Solaris systems:
      1. Issue the following command to find the processes that are using your_isc_runtime_root/AppServer/java/bin/java.exe:

         ps -ef | grep java

      2. Kill all of those processes.
   2. For Windows systems:
      1. Open Windows Task Manager.
      2. Locate the Java processes and end those processes.
10. Delete the root directory for the console runtime.
11. If this procedure was not successful and no other applications are installed on the application server profile, consider deleting the WebSphere Application Server profile and creating a new one.

Manually uninstalling the console runtime from a separate WebSphere Application Server

If the install program fails and the console installation uses a separate WebSphere Application Server, you can try to manually remove the Integrated Solutions Console runtime and then install again. To manually remove the console runtime, perform the following steps: