The Integrated Solutions Console Toolkit installation program provides options to install plug-ins that assist in developing components for Integrated Solutions Console. To install the plug-ins, the system must have the following:

• Rational Application Developer, Version 6.0

The plug-in provides help documentation that describes how to use the wizard and  editor, as well as manually perform some tasks that the plug-in does not automate. To view the documentation, click Help > Help Contents on the toolbar for Rational Application Developer. You may install the plug-in at a later stage, if you choose not to install it when you install the Integrated Solutions Console Toolkit.

Preparing the LDAP Server

If you plan to install the console runtime and use WebSphere Application Server security with an LDAP server as the user registry, perform the following procedure:

1. Follow the installation instructions provided with the LDAP server to install and configure the server before you install the Toolkit. Create the users and user groups that you want to use in Integrated Solutions Console. You must create at least one group (iscadmins) and then create at least one user in that group, such as iscadmin.
2. If you need more information about settings, contact your LDAP administrator for assistance. The following table provides an example of the possible settings.

Panel	Field or Selection	Value
Member Manager properties Note: Member Manager handles user and group management tasks for the console runtime	User ID for the Member Manager	uid=iscadmin,cn=users,dc=yourco,dc=com
	Password for the Member Manager	iscpass
Specify a security option	Enable an LDAP user registry.	Select that option.
Specify LDAP values for the Integrated Solutions Console user and group	Console Administrator ID	uid=iscadmin,cn=users,dc=yourco,dc=com
	Console Administrator ID Short	iscadmin
	Console Administrator Password	iscpass
	Console Administrator Group ID	uid=iscadmins,cn=groups,dc=yourco,dc=com
	Console Administrator Group ID Short	iscadmins
Specify LTPA values	LTPA Password	The password for the Lightweight Third Party Authentication (LTPA) bind. LTPA is an IBM WebSphere protocol. The value can contain the characters a-z, A-Z, and 0-9.
	LTPA Timeout	120 The time out interval for the LTPA bind. The value is the number seconds to wait for the bind.
	SSO Domain Name	yourcompany.com A subset of the host name of the HTTP server that Integrated Solutions Console uses. The value of this parameter will be used as the domain name of the LTPAToken cookie. The value is not the same as the LDAP server host name. An example is: ibm.com
Specify LDAP values	Hostname	ldaphost.yourcompany.com The fully-qualified host name of the LDAP server that Integrated Solutions Console will use.
	Port	389 The port that the LDAP server will use. Specify 389. If the LDAP server will communicate with Integrated Solutions Console over an SSL connection, specify 636.
	LDAP Administrator ID	cn=root The user ID for the LDAP directory administrator in the distinguished name format.
	LDAP Administrator Password	The password for the LDAP directory administrator.
	Bind ID	uid=iscadmin,cn=users,dc=yourco,dc=com The user ID for the LDAP bind authentication.
	Bind Password	The password for the LDAP bind authentication.
	SSL Enabled	false
	Suffix	dc=yourco,dc=com The LDAP suffix.
	User Prefix	uid The distinguished name (DN) prefix attribute name for user entries.
	User Suffix	cn=users The DN suffix attribute name for user entries.
	Group Prefix	cn The DN prefix attribute name for group entries.
	Group Suffix	cn=groups The DN suffix attribute name for group entries.
	User Object Class	inetOrgPerson The User object class corresponding to your directory. Choose the value appropriate for your LDAP server.
	Group Object Class	groupOfUniqueNames The Group object class corresponding to your directory.
	Group Member	uniqueMember The property that specifies the attribute name of the membership attribute of your group attribute name.

Preparing an existing DB2 installation for the console database

Note: The information in this section does not apply to console runtime installations on i5/OS systems.

This section applies only to installations where the Integrated Solutions Console runtime will be installed. The console runtime has a data store, which can be in one of the following locations:

• In the IBM Cloudscape that is embedded in the console runtime
• In a local or remote DB2 installation.
• In the IBM Cloudscape Network server that is embedded in the console runtime

If you want to use a local or remote DB2 installation for the console data store, you must perform the following tasks before you run the Toolkit installation program:

• Create the database on the DB2 server. An installation of the Integrated Solutions Console runtime cannot share a DB2 database with another installation of the console runtime. However, console runtimes can use different databases on the same DB2 server.
• If the console runtime will be installed on a system that is separate from the DB2 server, configure a DB2 client on the system where the console runtime will be installed

To create the database, perform the following procedure on the system where the DB2 server is installed:

1. Go to the system where the DB2 server is installed.
2. If the system is a Linux, or Solaris installation, or an AIX installation that has a .profile file in the root directory (the directory / ), perform the following steps to export the db2instance environment to your profile:
   1. In the .bashrc, .dshrc, or .profile file, add the following code:

      if [ -f /home/db2inst/sqllib/db2profile ];
      then . /home/db2inst/sqllib/db2profile; fi

      The variable db2inst is your database instance.

   2. Reopen the shells.
   3. To verify that your environment has set the DB2 profile environment variables (such as DB2INSTANCE=db2inst), run the env command.
3. If the system is an AIX installation that does not have a .profile file in the root directory (the directory / ), perform the following steps to export the db2instance environment to your profile:
   1. Change to the following directory: /home/db2inst1
   2. Copy the .profile file in that directory to the root directory (the directory / ).
   3. Edit the .dtprofile in the root directory and uncomment the last line of the file.
   4. Verify that the Java Runtime Environment 1.4.2 is installed on the system and that the path is in the .profile file.
   5. Log off and then log on again.
   6. Reopen the shells.
   7. To verify that your environment has set the DB2 profile environment variables (such as DB2INSTANCE=db2inst), run the env command.
4. Log in to the DB2 server machine as a user with sufficient database privileges:
   • For Windows systems, log in as a user with administrative privileges.
   • For AIX, Linux, and Solaris systems, log in to DB2 using the name of the DB2 instance or your database user name. If you are logged in as root, enter the following command to change to the db2instuser, where db2instuser is the database user:

     su - db2instuser 

5. Create the databases:
   • If you want to create a single database for the console data and its Member Manager data, use the sample script create_local_databases as a guide. Change the string iscDB to the name you want to assign to the database.
   • If you want to create two separate databases for the console data and the Member Manager data, use the sample script create_local_databases as a guide. In the script, make the following changes:
     1. Change the string iscDB to the name you want to assign to the console database.
     2. Uncomment the command lines in the WMM Section.
     3. Change the string wmmDB to the name you want to assign to the Member Manager database.
   • If you use the create_local_databases.sh sample script, make the following changes in addition to the changes described earlier:
     1. Change the string iscA to the local alias you want to assign to the console database.
     2. Change the string wmmA to the local alias you want to assign to the Member Manager database.
     3. For AIX systems, change db2inst1 if your database instance has a different name.
   • To run the script, issue one of the following commands:
     • For AIX, Linux, and Solaris systems, run create_local_databases.sh
     • For Windows systems, run db2cmd create_local_databases.bat
6. If the DB2 server is on a separate system from the system where the console runtime will be installed, perform the following steps:
   1. Use a text editor to open the /etc/services file, which is in different locations depending on the operating system. For example, on Windows systems, the location might be C:\winnt\system32\drivers\etc.
   2. If the services file does not specify DB2 connection and interrupt service ports, add the following lines to specify those ports:

      db2c_db2inst 50000/tcp # connection service port for the DB2 instance db2inst
      db2i_db2inst 50001/tcp # interrupt service port for the DB2 instance db2inst

      The variable db2inst is the name of the DB2 instance ID on the system.

   3. Set DB2COMM to use TCP/IP as its communications protocol. Enter the following command:

      db2set DB2COMM=TCPIP

   4. Configure the DB2 server to use the correct TCP/IP port for communication with clients. Enter the following command:

      db2 UPDATE DBM CFG USING svcename svce_name

      The variable svce_name is the connection service name (db2c_db2inst) that you specified in the /etc/services file.

   5. Restart the database instance.
      
      Note: If you used the script create_local_databases.sh and the connection to iscA (the local alias for the console database) fails, restart the operating system.

If the Integrated Solutions Console runtime will be installed on a system that is separate from the DB2 server, perform the following procedure to configure a DB2 client on the system where the console runtime will be installed:

1. Go to the system where the Integrated Solutions Console runtime will be installed.
2. Install IBM DB2 Connect on the system.
3. Log in to the system as a user with sufficient database privileges:
   • For Windows systems, log in as a user with administrative privileges.
   • For AIX, Linux, and Solaris systems, log in to DB2 using the name of the DB2 instance or your database user name. If you are logged in as root, enter the following command to change to the db2instuser, where db2instuser is the database user:

     su - db2instuser 

4. Use a text editor to open the /etc/services file, which is in different locations depending on the operating system. For example, on Windows systems, the location might be C:\winnt\system32\drivers\etc.
5. Add the following line for the DB2 connection port:

   db2c_db2inst 50000/tcp # connection service port for the DB2 instance db2inst

   The variable db2inst is the name of the DB2 instance ID on this system.

6. Set DB2COMM to use TCP/IP as its communications protocol. Enter the following command:

   db2set DB2COMM=TCPIP

7. Catalog the TCP/IP node with the IP address of the remote DB2 server. Enter the following command:

   $ db2 catalog tcpip node db2_alias remote database_server server svce_name

   The variables have the following meanings:

   • db2_alias is the user-defined alias of the DB2 node on this system. Specify any valid name you want.
   • database_server is the fully-qualified host name or the static IP address of the remote DB2 server.
   • svce_name is the same connection service name (db2c_db2inst) that you specified in the /etc/services file on the DB2 server.
8. Catalog the remote console database. Enter the following command:

   $ db2 catalog db remote_console_database as local_alias at node db2_alias

   The variables have the following meanings:

   • remote_console_database is the name of the console database on the remote DB2 server. That name was specified in your modification of the create_local_database script that you used to create the database on the server.
   • local_alias is the alias by which the remote database will be known on this system.
   • db2_alias is the alias of the DB2 node on this system, as specified in the previous step.
9. To log off of DB2, enter the following command: $ exit
10. To test your remote connection, enter the following command:

    $ db2 connect to local_alias user user_ID using password

    The variables have the following meanings:

    • local_alias is the alias by which the remote database is known on this system and matches the alias you specified in the previous step to catalog the remote database.
    • user_ID is database user.
    • password is the password for the database user.

DB2 Script - create_local_databases

The scrips to be run on Linux, AIX and Solaris platforms. Copy the following lines into a .sh file
#!/bin/sh
# To use this script to create a local Integrated Solutions Console database,
# update the following values throughout:
# db2inst1 Replace with the db2 admin user (also replace in WMM Section)
# iscNode Replace with the desired node name (also replace in WMM Section)
# iscDB Replace with the desired database name
# iscA Replace with the desired alias name
# This will create a database that can be used for both the Portal and WebSphere Member Manager databases.
# If separate databases are desired for the Portal and WebSphere Member Manager databases,
# uncomment the WMM Section at the end of this script before running it.
# start db2 if necessary
su - db2inst1 -c 'db2start'
su - db2inst1 -c 'db2 -v UNCATALOG DATABASE iscA'
su - db2inst1 -c 'db2 -v UNCATALOG NODE iscNode'
su - db2inst1 -c 'db2 -v DROP DATABASE iscDB'
# handle remote db2 server
DB2_SERVER=`hostname`
SVCE=`su - db2inst1 -c "db2 get dbm cfg" | grep SVCENAME | awk '{print $NF}'`
su - db2inst1 -c "db2 -v -t CATALOG TCPIP NODE iscNode remote $DB2_SERVER server $SVCE"
su - db2inst1 -c 'db2 -v CREATE DATABASE iscDB USING CODESET UTF-8 TERRITORY us'
su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR iscDB USING APPLHEAPSZ 16384'
su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR iscDB USING STMTHEAP 60000'
su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR iscDB USING APP_CTL_HEAP_SZ 8192'
su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR iscDB USING LOCKLIST 400'
su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR iscDB USING INDEXREC RESTART'
su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR iscDB USING LOGFILSIZ 1000'
su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR iscDB USING LOGPRIMARY 12'
su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR iscDB USING LOGSECOND 10'
su - db2inst1 -c 'db2set DB2_RR_TO_RS=yes'

su - db2inst1 -c 'db2 -v CATALOG DATABASE iscDB AS iscA AT NODE iscNode'



# To use this section of the script to create a separate WebSphere Member Manager database,
# uncomment the WMM Section below and update the following values throughout:
# wmmDB Replace with the desired database name
# wmmA Replace with the desired alias name

##WMM Section
#su - db2inst1 -c 'db2 -v UNCATALOG DATABASE wmmA'
#su - db2inst1 -c 'db2 -v DROP DATABASE wmmDB'
#su - db2inst1 -c 'db2 -v CREATE DATABASE wmmDB USING CODESET UTF-8 TERRITORY us'
#su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR wmmDB USING APPLHEAPSZ 16384'
#su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR wmmDB USING STMTHEAP 60000'
#su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR wmmDB USING APP_CTL_HEAP_SZ 8192'
#su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR wmmDB USING LOCKLIST 400'
#su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR wmmDB USING INDEXREC RESTART'
#su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR wmmDB USING LOGFILSIZ 1000'
#su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR wmmDB USING LOGPRIMARY 12'
#su - db2inst1 -c 'db2 -v UPDATE DATABASE CONFIGURATION FOR wmmDB USING LOGSECOND 10'
#su - db2inst1 -c 'db2set DB2_RR_TO_RS=yes'
#su - db2inst1 -c 'db2 -v CATALOG DATABASE w


The scripts to be run on a Windows Platform

Copy the following script to a .bat file and run the same

REM To use this script to create a local Integrated Solutions Console database,
REM update the following values throughout:
REM iscDB Replace with the desired database name
REM This will create a database that can be used for both the Portal and WebSphere Member Manager databases.
REM If separate databases are desired for the Portal and WebSphere Member Manager databases,
REM uncomment the WMM Section at the end of this script before running it.
db2 -v "DROP DATABASE iscDB"
db2 -v "CREATE DATABASE iscDB USING CODESET UTF-8 TERRITORY us"
db2 -v "UPDATE DATABASE CONFIGURATION FOR iscDB USING APPLHEAPSZ 16384"
db2 -v "UPDATE DATABASE CONFIGURATION FOR iscDB USING STMTHEAP 60000"
db2 -v "UPDATE DATABASE CONFIGURATION FOR iscDB USING APP_CTL_HEAP_SZ 8192"
db2 -v "UPDATE DATABASE CONFIGURATION FOR iscDB USING LOCKLIST 400"
db2 -v "UPDATE DATABASE CONFIGURATION FOR iscDB USING INDEXREC RESTART"
db2 -v "UPDATE DATABASE CONFIGURATION FOR iscDB USING LOGFILSIZ 1000"
db2 -v "UPDATE DATABASE CONFIGURATION FOR iscDB USING LOGPRIMARY 12"
db2 -v "UPDATE DATABASE CONFIGURATION FOR iscDB USING LOGSECOND 10"
db2set DB2_RR_TO_RS=yes

REM To use this section of the script to create a separate WebSphere Member Manager database,
REM uncomment the WMM Section below and update the following values throughout:
REM wmmDB Replace with the desired database name
REM REM WMM Section
REM db2 -v "DROP DATABASE wmmDB"
REM db2 -v "CREATE DATABASE wmmDB USING CODESET UTF-8 TERRITORY us"
REM db2 -v "UPDATE DATABASE CONFIGURATION FOR wmmDB USING APPLHEAPSZ 16384"
REM db2 -v "UPDATE DATABASE CONFIGURATION FOR wmmDB USING STMTHEAP 60000"
REM db2 -v "UPDATE DATABASE CONFIGURATION FOR wmmDB USING APP_CTL_HEAP_SZ 8192"
REM db2 -v "UPDATE DATABASE CONFIGURATION FOR wmmDB USING LOCKLIST 400"
REM db2 -v "UPDATE DATABASE CONFIGURATION FOR wmmDB USING INDEXREC RESTART"
REM db2 -v "UPDATE DATABASE CONFIGURATION FOR wmmDB USING LOGFILSIZ 1000"
REM db2 -v "UPDATE DATABASE CONFIGURATION FOR wmmDB USING LOGPRIMARY 12"
REM db2 -v "UPDATE DATABASE CONFIGURATION FOR wmmDB USING LOGSECOND 10"
REM REM WMM Section

Verifying the installation

If you installed the console runtime, perform the following procedure to verify the installation:

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. For i5/OS installations that use SYSINT, find the port number by checking the iscports.tmp file in the /tmp/InstallShield/ directory (the default port number is 2001). For i5/OS installations that use WebSphere Application Server Express or WebSphere Application Server Base, the port number is the value specified by the -W generalConfig.port property of the install response file.
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, /tmp/InstallShield on i5/OS 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.

• The following table summarizes the restrictions for the database and security options:

  Table 1. Database and Security Options

  Console Database (dbChoice.dbChoice)	Security Choices (securityChoice.securityChoice)	Restrictions and Caveats
  Embedded Cloudscape ("cloudscape")	No security ("none") Security enabled with an LDAP user registry ("dbldap")	This configuration should not be used for production environments. The Cloudscape database is accessible only to the console. This configuration does not apply to installations on i5/OS systems.
  DB2 Universal Database ("db2")	No security ("none") Security enabled with a DB2 user registry ("dbonly") Security enabled with an LDAP user registry ("dbldap")	The DB2 Universal Database can be on a local or remote system.
  Embedded Cloudscape Network Server ("cloudscapens")	Security enabled with a Cloudscape Network Server user registry ("dbonly")	Use this configuration only for embedded production environments. Do not use this configuration in enterprise environments. To use this configuration, you must also use the application server that is embedded in the console runtime. The Cloudscape Network Server is accessible only to the console. This configuration does not apply to installations on i5/OS systems.
  Note: If the no security option is selected, the user registry is stored in the console database and users are not authenticated when they access the console. You can add, edit, or delete users through the Console Settings pages only. If the user registry is on an LDAP server, you can add, edit, or delete users through the LDAP interface or the Settings pages. If the user registry is in the embedded Cloudscape Network Server or on a DB2 server, you can add, edit, or delete users through the Console Settings pages only.

Known Issues:

• ISC uninstallation (with External WAS) does not cleanup properly. ISC_Portal is not removed on External WAS when ISC is uninstalled. Ports are not released after uninstallation. Please end server process and clean the files manually.
• Installation of ISC fails on Win2K. This happens only when both the runtime and toolkit options are selected. You can install both seperately, i.e first time install only ISC Runtime and then rerun the installer to install ISC Toolkit. But note that the ISC uninstallers created with seperate Installations of ISC runtime and ISC Toolkit remove both when either is run.
• Eclipse help system fails to start in Windows 2000 and 2003 platforms. You may get an eclipse error message while you start the ISC server.
• Installation fails if both Runtime and Toolkit options are selected on Windows 2000 Professional.
• ISC Eclipse Help startup fails on Windows 2000 Pro and Windows 2003 Standard Server.
• ISC fails to return proper error code when PD/SI deployment fails in AIX platform.
• 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.
• Installation on External WAS – Make sure that WSAnt.sh has the required execute permissions for the user on UNIX platforms.
• Installation using External WAS – Apply PTF ‘PK00274’ to your WAS 6.0.0.2 Base before installing ISC
• Installation fails if a combination of options – ‘External WebSphere Application Server’ and ‘Cloudscape Network Server as User Registry’ are used.
• Linux/AIX DB2 Config - In Linux and AIX, the default configuration for DB2 is to use shared memory segments for local db access. This causes ISC installation failure when all the shared memory gets used up. So in these platforms, an alias should be created for DB2 in such a way that it is accessed remotely and not thru shared memory. See the section on configuring remote DB2 for the steps to be followed.

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
OS/400 : the installer does not contain a bundled java. The machine should have Java 1.4.2 pre- installed. All OS/400 bundles require PTFs  SF99269 and MF34019 to be installed prior to installing any of the Toolkit bundles.

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

      • For i5/OS systems that use WebSphere Application Server Express or WebSphere Application Server Base, run the following command:

        i5os_appserver_profile_root/AppServer/bin/wasprofile -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. This step does not apply to i5/OS installations.
   • 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. This step does not apply to i5/OS installations.
   • 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: