Installing Identity Install Pack for WebSphere 4.x

Use the following information and procedures to install Identity Install Pack for use with the IBM WebSphere Application Server, Version 4.x.

Before You Begin

Location where WebSphere is installed

Your license key

The password you selected when you set up the index database

Installation Steps

Follow these installation and configuration steps, located in this chapter and following chapters:

Step 1: Install and configure the Identity Install Pack software

Step 2: Install the Sun Identity Manager Gateway (optional)

Step 3: Additional WebSphere configuration

These procedures assume that you have set up an application server and servlet engine in WebSphere. For detailed information about installing and using WebSphere, refer to the Web page or reference information provided by the application server software provider.

Step 1: Install and Configure the Identity Install Pack Software

Unjar the idm.war file into an lh_staging folder on a file system:

jar -xvf idm.war

idm.war

Delete these files, if they exist:

WEB-INF/lib/log.jar

WEB-INF/lib/j2ee.jar

WEB-INF/lib/ldap.jar

WEB-INF/lib/cryptix-jce-provider.jar

WEB-INF/lib/cryptix-jce-api.jar

security.jce.workaround

WEB-INF/lib

Install the Java Secure Socket Extension (JSEE) 1.0.3 .jar files, located at http://java.sun.com/products/jsse/index-103.html:

WEB-INF/lib/jnet.jar

WEB-INF/lib/jcert.jar

WEB-INF/lib/jsse.jar

Download the latest jlog package from WebSphere at:

http://www.alphaworks.ibm.com/tech/loggingtoolkit4j

Replace the idm/WEB-INF/lib/log.jar file with the com\ibm\logging\log.jar file.

Edit the idm\WEB-INF\bin\lh.bat file and add the following line at the top of the file (after the @echo off line):

set CLASSPATH=%CLASSPATH%;WebSphere/AppServer/lib/j2ee.jar

where WebSphere is the location where WebSphere is installed.

If you plan to use an index database, you may need to copy one or more files to the idm\WEB-INF\lib directory. For example, you may need to place into idm/WEB-INF/lib a JAR file containing a JDBC driver (for a DriverManager connection) or a JAR file containing a JNDI InitialContextFactory (for a DataSource connection). To determine the steps you may need to perform before you go on, see Appendix A, Index Database Reference. When finished, launch setup to continue with installation.

lh setup

Set $WSHOME to the location of the staging directory where you unjarred the idm.war file.

Set JAVA_HOME in the environment to the Java directory under the WebSphere installation; for example:

set JAVA_HOME=c:\ProgramFiles\WebSphere\AppServer\java

Change to $WSHOME, and then enter the command:

lh setup

The installer displays the Locate the Repository panel.

Select an index database:

Oracle (JDBC Driver)

Oracle (Data Source)

MySQL (JDBC Driver)

MySQL (Data Source)

DB2 (JDBC Driver)

DB2 (Data Source)

SQL Server (JDBC Driver)

SQL Server (Data Source)

LocalFiles

Depending on your selection, setup prompts for additional setup information.

Appendix A

Index Database Reference

Appendix C

Configuring Data Sources for Identity Manager

Click Next.

Identity Manager displays the License Key panel.

Click Import from File to import your license key data from an XML file.

Click Next.

Identity Manager displays the Import XML Files panel.

Accept the default XML file (idm\sample\init.xml), or enter or browse to the path to the XML file you will use to set initial database values. When finished, click Import File.

When import completes, click Done in the setup panel.

Create a .war file from the staging folder with these commands:

cd lh_staging
jar -cvf c:\temp\idm.war *

Install the idm.war file by using the WebSphere Web Admin interface:

Highlight Enterprise Applications, and then right-click and select Install Enterprise Application.

For application display name, specify idm.

For context root, specify /idm.

Edit the IBMHTTPServerLocation\conf\httpd.conf file to set up an alias in the IBM http server.

Add the following lines at the bottom of the file:

Alias /idm
WebSphereIDManagerApplicationDirectory/idm.ear/
idm.war

Restart the HTTP server.

Ensure that the application server is started to generate the plugin configuration during application startup. To do this:

From the Admin console, go to WebSphere Administrative Domain—>
Nodes—>YourNodeName—>ApplicationServers—>
YourApplicationServerName.

Go to the Custom tab, and set the value of Automatic Generation of Plugin to true.

Restart the application server.

.war

$WAS_HOME/bin/SEAppInstall.bat -install c:\temp\idm.war -nodeName HostName

You are prompted with the following questions; provide answers as follows:

(Please Specify an application display name) idm

(Please Specify a context root) /idm

(Do you wish to precompile all JSPs in this application?) n

(Do you wish to precompile individual Web Applications?) n

(Please specify a Virtual Host for the following Web Applications
1) Sun Identity Manager) [] default_host

Step 2. Install the Sun Identity Manager Gateway

If you plan to set up Windows Active Directory, Novell NetWare, Novell GroupWise, Exchange 5.5, Remedy, or RSA ACE/Server resources, you should install the Sun Identity Manager Gateway. Follow the procedures in Chapter 11, Install the Sun Identity Manager Gateway.

Step 3. Configure the Application Server for https

If you plan to use the application server for https, you must register the correct protocol handler.

5