This procedure is necessary for AIX
®, or Solaris operating systems only.
When adding or modifying client definitions, you need to be aware of potentially encountering a memory allocation error. If the ulimit
value is set too low, a memory allocation error can occur on AIX
, or Solaris and a too many files open
error is logged to the wp_profile_root/logs/WebSphere_Portal/SystemOut.log
file. This could cause WebSphere
® Portal to stop.
It is recommended setting the ulimit
value to at least 2000, or to unlimited
, even when the system is not under stress.
To change the ulimit
value, perform the following steps.
Parent topic: Configuring Mobile Portal Accelerator to support new mobile devices
- With a text editor, open the following file:
There is a space between the period (.
) and the rest of the command.
- Locate the command ulimit -n 1024.
- Change 1024 to a higher value (such as 2000) or to the word unlimited (for example, ulimit -n unlimited).
- Save your changes.
- Restart the portal server using the following commands:
[[Variable names used in the information center for user supplied informationmpa8|wp_profile_root]]/bin/stopServer.sh server_name -username WAS_admin -password WAS_admin_password_value
[[Variable names used in the information center for user supplied informationmpa8|wp_profile_root]]/bin/startServer.sh server_name
is the name of the WebSphere
Application Server instance (for example, WebSphere_Portal