4.8.3 Settings for 10-20 concurrent users to work with operation windows

(1) Impact from changing the settings

The heap size of Java Virtual Machine for the Web application server is changed from 512 MB to 1 GB, which results in an increased memory consumption and heavier CPU load.

The size of a log file increases from 1,024 KB to 5,120 KB, which causes the installation folder to consume approximately 72 MB more disk capacity.

To Page Top

(2) Procedure for changing the built-in Web application server settings

To change the built-in Web application server settings:

1. Back up the following files from the installation folder of JP1/IT Desktop Management 2 to a different folder.

   • JP1/IT Desktop Management 2-installation-folder\mgr\uCPSB\httpsd\conf\httpsd.conf

   • JP1/IT Desktop Management 2-installation-folder\mgr\uCPSB\CC\server\usrconf\ejb\jp1dtnavi\usrconf.cfg

   • JP1/IT Desktop Management 2-installation-folder\mgr\conf\jdn_log.ini

2. Edit the JP1/IT Desktop Management 2-installation-folder\mgr\uCPSB\httpsd\conf\httpsd.conf file as follows:

   Change to: ThreadsPerChild 23 (By default, this is set to ThreadsPerChild 10.)

3. Edit the JP1/IT Desktop Management 2-installation-folder\mgr\uCPSB\CC\server\usrconf\ejb\jp1dtnavi\usrconf.cfg file as follows:

   Change to: add.jvm.arg=-Xms1024m (Also delete the hash mark (#) at the head of the line.)

   Change to: add.jvm.arg=-Xmx1024m (Also delete the hash mark (#) at the head of the line.)

   Change to: add.jvm.arg=-XX:NewRatio=4

   Change to: add.jvm.arg=-XX:SurvivorRatio=1

4. Edit the JP1/IT Desktop Management 2-installation-folder\mgr\conf\jdn_log.ini file to add the following statements:

   --- Statements to be added (Start) ---

   [JDNAPIM]

   SIZE=5120

   [JDNAPID]

   SIZE=5120

   --- Statements to be added (End) ---

5. Stop the JP1/IT Desktop Management 2 service.

6. Back up the mmap directory and log files (*.log files) from JP1/IT Desktop Management 2-installation-folder\mgr\uCPSB\CC\server\public\ejb\jp1dtnavi\logs\user\jp1dtnavi to a different location you want.

7. Start the JP1/IT Desktop Management 2 service.

To Page Top

(3) Procedure for restoring the built-in Web application server settings

After you change the built-in Web application server settings by following steps in (2) Procedure for changing the built-in Web application server settings, if you want to restore the original settings, use the following steps:

1. Copy the files that you backed up in step 1 in (2) Procedure for changing the built-in Web application server settings to overwrite the current files:

   • JP1/IT Desktop Management 2-installation-folder\mgr\uCPSB\httpsd\conf\httpsd.conf

   • JP1/IT Desktop Management 2-installation-folder\mgr\uCPSB\CC\server\usrconf\ejb\jp1dtnavi\usrconf.cfg

   • JP1/IT Desktop Management 2-installation-folder\mgr\conf\jdn_log.ini

2. Stop the JP1/IT Desktop Management 2 service.

3. Back up the mmap directory and log files (*.log files) from JP1/IT Desktop Management 2-installation-folder\mgr\uCPSB\CC\server\public\ejb\jp1dtnavi\logs\user\jp1dtnavi to a different location you want.

4. Start the JP1/IT Desktop Management 2 service.

To Page Top

(4) Notes on 10-20 concurrent users to work with operation windows

• Perform steps in (2) Procedure for changing the built-in Web application server settings again after an overwrite installation.

• Set the maximum number of displayed items per page on a list view to 100.

• After the system initiates operations, it might be found that there are peak times of operations or that windows are not responsive. In such a case, you should consider adjusting your business procedures to work around the problem. For example, it is a good way to allocate a time slot for each department to allow the administrators to use the media creation, import, or export function.

• When good performance is not provided, you should consider adding cores to the allocated CPUs.

• When multiple users perform actions concurrently, a heavy load is put on the server. This can cause the following symptoms:

  Action	Symptom	Workaround
  General	A message appears indicating that a heavy load is put on the database.	Wait for a while and then retry the action. (Allocate a different time slot for the action, if possible.)
  	A page is not rendered completely.	Reload the page. (Allocate a different time slot for the action, if possible.)
  	Response is slow.	None. (Allocate a different time slot for the action, if possible.)
  Media creation	The Web server restarts automatically.	Retry from the login step.
  Import or export	The process does not finish.	Retry the action. (Allocate a different time slot for the action, if possible.)
  Search result view (available only to system administrators)	The process does not finish.	Retry the action. (Allocate a different time slot for the action.)

To Page Top