Sun Java logo     Previous      Contents      Index      Next     

Sun logo
Sun Java(TM) Systems Identity Manager 7.1 Installation Guide 

Chapter 4
Installing Identity Manager for WebSphere

Use the following information and procedures to install Identity Manager for use with the IBM WebSphere Application Server, Versions 5.1 express and 6.0. This chapter includes:

Before You Begin

During installation, you will need to know:

Installation Steps

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

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 Manager Software

To install and configure the software:

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

    2. jar -xvf idm.war

    Note

    The idm.war file is located in the base directory of the Installation CD.

  2. If you plan to use an index database, you may need to copy one or more files to the idm\WEB-INF\lib directory. To determine the steps you may need to perform before you go on, see Index Database Reference. When finished, launch setup to continue with installation.

    3. Caution

    If you launch setup before copying your index database files, setup will not proceed correctly. Copy the files, and then use the lh setup command to restart the setup portion of the installation process.

  3. Set the environment variables JAVA_HOME and WSHOME:

    4. set JAVA_HOME=c:\Program Files\WebSphere\AppServer\java
    set WSHOME=Path To IDMStaging Directory

    Note

    Make sure the value of the WSHOME environment variable does NOT contain the following:

    • Quotation marks (“ “)
    • A slash or backslash at the end of the path (/ or \)

    Do not use quotation marks, even if the path to the application deployment directory contains spaces.

    Note

    The following step is not necessary when installing version 6.0 or later.

  4. Change to the staging directory, and delete the following files, if they exist:

    5. WEB-INF\lib\cryptix-jce-provider.jar
    WEB-INF\lib\cryptix-jce-api.jar

    Note

    The Cryptix jars are no longer included and no longer supported. You need to remove them if you haven't already. If you've customized your Waveset.properties file, please make sure that security.jce.workaround property is set to false or removed. An exception will be thrown if this property is set to true because the intention of this property will not be fulfilled.

    Removing the jars from WEB-INF/lib for WebSphere disables the BPE. Move those jars to a different location and create a CLASSPATH variable that points to those jars to re-enable the BPE.

  5. Run the following command.

    6. bin\lh setup

    The installer displays the Locate Repository panel.

  6. 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.

      Note

      • See Index Database Reference, for selections and setup instructions. 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).
      • If you are planning to use a WebSphere or WebLogic Data Source as your repository location, see the special instructions in Configuring Data Sources for Identity Manager.

  7. Click Next.
  8. The Continue Identity Manager Demo Setup? panel appears.
  9. If this is a non-demo installation click No, I will configure Identity Manager myself. Go to Step 18.
  10. If appropriate, click Yes, I would like to continue setting up a demonstration environment.

    11. This allows you to quickly configure users and enter environment and server information.

  11. Enter the following personal information:
    • First name
    • Last name
    • Email address

      • Note

      This personal information is used to create the Approver user (with configurator privileges.)

  12. Enter the following Approver information:
    • Approver name
    • Approver password
  13. Click Next.
  14. Select the Server Type from the list.

    15. Select None if your environment has no server to manage. If there is a server you wish to manage, select the appropriate server type. You will be prompted for further server information as appropriate.

  15. If you have an email SMTP server, click SMTP Host and enter the server address. If desired, click Test Server to verify communication to the SMTP server.
  16. If you would like email notifications to be written to a file, click Notification File. Click Browse to select another notification file.
  17. Click Next.
  18. The installer displays the Import Save Configuration panel.
  19. Click Execute to perform all the listed functions. If desired click Hide Details.
  20. When all functions complete, click Done in the setup panel.
  21. Delete these files, if they exist:
    • WEB-INF/lib/log.jar
    • WEB-INF/lib/j2ee.jar
    • WEB-INF/lib/ldap.jar

      • Note

      Removing the jars from WEB-INF/lib for WebSphere disables the Business Process Editor. Move those jars to a different location and create a CLASSPATH variable that points to those jars to re-enable the BPE.

  22. Download the latest jlog package from WebSphere at:

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

    Note

    The jlog package is now incorporated in WebSphere’6.0. Download this only for earlier versions.

  23. Copy the com\ibm\logging\log.jar file to idm/WEB-INF/lib/log.jar.
  24. Create a .war file from WSHOME:

    25. jar -cvf idm.war *

  25. Start the application server. You must use WebSphere’s script to do this. For example, if WebSphere’s binary files are installed in c:\Program Files\WebSphere\AppServer\bin, and that the application server is named server1:

    26. cd c:\Program Files\WebSphere\AppServer\bin

    startServer.bat server1

  26. Start the WebSphere administration console, and then select
    Applications—>Install New Application.
  27. Add the full path to the idm.war file in the Path:ServerPath field.
  28. Add the path to the Context Root for the Identity Manager installation (for example, /idm), and then click Next.
  29. Select the Generate Default Bindings option. (Use the default selections for Override and Virtual Host.)
  30. Click Next.
  31. Accept the was.policy file that is displayed under the heading Application Security Warnings. Scroll down to the bottom of this file and click the Continue button.
  32. Configure the Step 1: provide options to perform the installation page as needed.
    • If you want to install the application to a different location than WebSphere’s default location, enter the path to install the application in the Directory to Install Application field; for example:

      c:\Program Files\WebSphere\AppServer\installedApps\Hostname

    • Make sure the Distribute Application and Use Binary Configuration options are selected.
    • Make sure that the Create Mbeans for Resources and Deploy EJBs options are not selected.
    • Enter the name of the application in the Application Name field (the default is idm).
    • If desired, select the Enable class reloading option.

      • Click Next after configuring this dialog.

  33. Make sure the Step 2: Map virtual hosts for web modules panel displays a line for the current release of Identity Manager and that it maps to the appropriate virtual host, and then click Next.
  34. Make sure the Step 3: Map modules to application servers panel displays a line for the current release of Identity Manager and that it maps to the appropriate server, and then click Next.
  35. Review the summary of options, then click Finish.
  36. After Identity Manager has been installed, click Save to Master Configuration to save the configuration.
  37. Click Save, and then wait for the page to clear.

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 Install the Sun Identity Manager Gateway.



Previous      Contents      Index      Next     

Part No: 820-0817-10.   Copyright 2007 Sun Microsystems, Inc. All rights reserved.