Getting Started with WebSphere Application Server
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
216 <strong>Getting</strong> <strong>Started</strong> <strong>with</strong> <strong>WebSphere</strong> <strong>Application</strong> <strong>Server</strong> Community Edition<br />
- Log on to the administrative console<br />
- In the left hand navigation pane, select Services → Repository.<br />
- Click Browse at the right side of File, and select the directory of the JAR library.<br />
- Specify other fields for the library following the guide in Section 3.4.<br />
- Click Install.<br />
4. The file /var/security/groups.properties.<br />
5. The var and deploy directories.<br />
6. C<br />
7. D<br />
8. B<br />
9. C<br />
10. A<br />
Chapter 10 –Tuning<br />
1. Following is the typical steps to tune a system.<br />
a) Measure the performance before you apply any changes to the system by<br />
using the appropriate monitoring tools.<br />
b) Identify possible performance bottlenecks in the whole system.<br />
c) Make changes to remove the bottlenecks.<br />
d) Return to step 1 to measure the performance.<br />
e) The cycle ends when the system reaches an acceptable performance.<br />
2. The default size of DefaultThreadPool is 500; the default size of<br />
ConnectorThreadPool is 30.<br />
3. Update values in wasceHome/var/config/config.xml according to the steps<br />
described in section 10.2.3<br />
4. Following is the steps to monitor the memory usage of Community Edition server.<br />
a) Start up Community Edition, launch console.<br />
b) In the left hand navigation pane, select <strong>Server</strong> → Information to open portlet<br />
to monitor the memory usage.<br />
5. Add JAVA_OPTS environment variable, set the value to be<br />
- Default heap size: -Xmsm<br />
- Maximum heap size: -Xmxm
Change language