Sun Identity Manager 8.1 Installation

Step 3: Deploy the Application

Note –

The following procedure uses the Integrated Solutions Console, Version 6.1. The configuration procedure may vary for other versions of the Integrated Solutions Console.

ProcedureTo deploy Identity Manager on WebSphere

  1. Delete the following files, if they exist:

    • WEB-INF/lib/log.jar

    • WEB-INF/lib/j2ee.jar

    • WEB-INF/lib/ldap.jar

  2. Create a .war file from WSHOME:

    jar -cvf idm.war *

  3. 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 the application server is named server1:

    cd c:\Program Files\WebSphere\AppServer\bin
    startServer.bat server1
  4. Start the WebSphere Integrated Solutions Console, and then select Applications—>Install New Application.

    The Preparing for the application installation panel displays.

    1. Add the full path to the idm.war file in the Local or Remote file system field.

    2. Add the path to the Context Root for the Identity Manager installation (for example, /idm).

    3. Select the Show me all installation options and parameters option, then click Next. A new panel is displayed.

  5. Select the Generate Default Bindings option. (Use the default selections for Override and Virtual Host.) Click Next.

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

  7. Configure the Step 1: Select installation options 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 Enterprise Beans 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.

  8. Make sure the Step 2: Map modules to servers panel displays a line for the current release of Identity Manager and that it maps to the appropriate server. Click Step 6: Map virtual hosts for Web modules.

  9. Make sure the Step 6: 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 Step 8: Summary.

  10. Review the summary of options, then click Finish.

  11. After Identity Manager has been installed, click Save to Master Configuration to save the configuration.

  12. Click Save, and then wait for the page to clear.

  13. Stop the Identity Manager application.

  14. Add the following line to your WAS_ROOT/profiles/ProfileName/installedApps/nodename/EnterpriseAppName/idm.war/WEB-INF/ibm-web-ext.xmi file

    <jspAttributes xmi:id="JSPAttribute_1" name="jdkSourceLevel" value="15"/>

    This line causes the application server to compile JSPTM files in Java 5.

  15. Restart Identity Manager.