Configuring the WebSphere JVM

You must configure the JVM configuration and command line parameters for your installation.

  1. Under Servers/Server Types on the left side of the console, click WebSphere application servers.
  2. On the right side of the console, click server1.
  3. In the Server Infrastructure area on the right side of the console, expand Java and Process Management.
  4. Click Process definition.
  5. In the Additional Properties area on the right side of the console, click Logging and tracing.
  6. Click JVM Logs.
  7. In the System.out/Log File Rotation area, verify that the File Size check box is selected.
  8. In the Maximum Size text box, type 10.
  9. In the Maximum Number of Historical Log Files text box, type 10.
  10. In the System.err/Log File Rotation area, verify that the File Size check box is selected.
  11. In the Maximum Number of Historical Log Files text box, type 10.
  12. Click OK.
  13. Near the top of the right side of the console, click Process definition.
  14. In the Additional Properties area of the right side of the console, click Java Virtual Machine.
  15. Type the following information in the corresponding text boxes:

    Initial Heap Size: 256

    (64-bit) Maximum Heap Size: 2800

  16. Click Apply.
  17. In the Additional Properties area on the right side of the console, click Custom properties.
  18. Click New.
  19. In the Name text box, type the following entry:

    client.encoding.override

  20. In the Value text box, type the following entry, then click OK:

    UTF-8

  21. Click New.
  22. In the Name text box, type the following entry:

    fiper.system.parmfile

  23. In the Value text box, enter the following path and filename, then click OK:

    Windows: <see_install_dir>\config\acs.properties

    ( or ${fiperhome}\..\config\acs.properties)

    Linux: <see_install_dir>/config/acs.properties

    (or ${fiperhome}/../config/acs.properties)

  24. Click New.
  25. In the Name text box, type the following entry:

    fiper.system.configpath

  26. In the Value text box, enter the following path, then click OK:

    <see_install_dir>/config

    (or ${fiperhome}/../config)

    On Windows, use a back slash “\” in the entry (instead of a forward slash “/”).

  27. Click New.
  28. In the Name text box, type the following entry:

    fiper.system.installpath

  29. In the Value text box, enter the following path, then click OK:

    ${fiperhome}

  30. Click New.
  31. In the Name text box, type the following entry:

    IBM_HEAPDUMP_OUTOFMEMORY

  32. In the Value text box, type the following entry, then click OK:

    false

  33. Click New.
  34. In the Name text box, type the following entry:

    IBM_JAVADUMP_OUTOFMEMORY

  35. In the Value text box, type the following entry, then click OK:

    false

  36. Click New.
  37. In the Name text box, type the following entry:

    oracle.jdbc.autoCommitSpecCompliant

  38. In the Value text box, type the following entry, then click OK:

    false

  39. For Linux only, complete the following substeps, then continue. For Windows, skip to the next step.
    1. Near the top of the right side of the console, click Process definition.
    2. In the Additional Properties area on the right side of the console, click Environment Entries.
    3. Click New.
    4. In the Name text box, enter the following for Linux:

      • LD_LIBRARY_PATH

    5. In the Value text box, enter:

      ${fiperhome}/code/bin

    6. Click OK.
  40. Near the top of the console in the center, click server1.
  41. In the Additional Properties area on the right side of the console (near the bottom), click Thread pools.
  42. In the Name column, click Default.
  43. Type the following information in the corresponding text boxes:

    Minimum Size: 25

    Maximum Size: 50

    Thread inactivity timeout: 30000

  44. Click Allow thread allocation beyond maximum thread size.
  45. Click OK.
  46. Near the top of the right side of the console, click server1.
  47. On the right side of the console, expand Container Services.

    Additional options appear.

  48. Click ORB service.
  49. Click Pass by reference.
  50. Click OK.
  51. On the right side of the console, expand Container Services.

    Additional options appear.

  52. Click Transaction Service.
  53. In the Total transaction lifetime timeout text box, type 300.
  54. Click OK.
  55. Save the configuration.