General Information for a UNIX Installation

In this section:

This section covers general information for a UNIX Installation.


Top of page

x
Java Listener JVM Defaults

How to:

The Java Listener on AIX has a pre-set value for Maximum Java Heap Size (JVM_MAX_HEAP) because the internal default for Java for this heap size is insufficient, which causes server features to fail. The pre-set value does not reflect any specific tuning, but is simply a known working value. Specific tuning should be done based on application need.

Other UNIX/Linux operating systems have not shown issues with internal defaults, and are not pre-set. However, applications may benefit from tuning, and it should be done based on application need.



x
Procedure: How to Tune the Java Listener from the Web Console

To tune the Java Listener from the Web Console:

  1. Select Workspace from the menu bar.
  2. Open the Java Services folder.
  3. Right-click DEFAULT and select Properties.

    The Java Services Configuration pane opens.

  4. Expand the JVM Settings section.
  5. Under Non-standard JVM options, enter values in the Initial Java Heap Size and Maximum Java Heap Size fields.
  6. Click Save and Restart Java Services.

Top of page

x
Limiting CPU Use on Machines With Multiple CPUs

How to:

When the effective number of CPUs (cores) on a computer exceeds the number allowed by the server license, depending upon the license, either the server will not start or users are given warnings in edaprint.log and at Web Console or Data Management Console login.

To remediate the situation, the installation site has two choices:

Note that running multiple instances of the server (each under a limited virtual processor set) or adding processors to the virtual set after the server is running constitutes a license violation.

The virtual environment methods, specific commands, and options that should be used depend on the operating system vendor and what the site wants to accomplish with the operating system supplied tools. Basic syntax examples are supplied below as an assistance. Consult your operating system documentation for further specific information on the use of the respective commands as the commands are not a server feature, but an operating system provided environment in which the server runs.



x
Syntax: How to Start the Server With Limited Effective CPUs for Solaris

The psrset operating system command is used to create virtual processor sets and run processes under them, but it also requires ID authorization. Authorization must be done by the root by adding a line to the /etc/user_attr file. For example:

iadmin::::type=normal;defaultpriv=basic,sys_res_config

The server admin decides on and forms a set, and then uses the resulting set number in the psrset -e command to start the server. For example:

$ psrset -c 2 3
processor 2: was not assigned, now 1
processor 3: was not assigned, now 1
$ cd ibi/srv77/wfs
$ psrset -e 1 bin/edstart -start


x
Syntax: How to Start the Server With Limited Effective CPUs for HP-UX

The psrset operating system command is used to create virtual processor sets and run processes under them.

The server admin decides on and forms a set, and then uses the resulting set number in the psrset -e command to start the server. For example:

$ psrset -c 2 3
processor 2: was not assigned, now 1
processor 3: was not assigned, now 1
$ cd ibi/srv77/wfs
$ psrset -e 1 bin/edstart -start


x
Syntax: How to Start the Server With Limited Effective CPUs for AIX

The mkrset and execrset operating system commands are used to create processor/memory region sets and run processes under them, but they also require ID authorization. Authorization must be done by the root by issuing:

chuser capabilities=CAP_NUMA_ATTACH,CAP_PROPAGATE iadmin

The server admin decides on and forms a set, and then uses the assigned name in the execrset command to start the server. For example:

$ mkrset -c 2-3 mycorp/mycpus
$ cd ibi/srv77/wfs
$ execrset mycorp/mycpus bin/edstart -start


x
Syntax: How to Start the Server With Limited Effective CPUs for Linux (all vendors)

The taskset operating system command is used to bond a process to particular processors, in effect creating a virtual environment.

The server admin decides on the processors to use and uses them in the taskset command to start the server. For example:

$ cd ibi/srv77/wfs
$ taskset -c 3,4 bin/edstart -start

iWay Software