Getting Started with WebSphere Application Server

Appendix A – Solutions to review questions 215
information by the Java EE authentication mechanisms. Role-based security
allows the developer to secure access to Java EE resources based on roles. Often
the developer has no knowledge of the users and groups that will exist at runtime,
so how does the developer refer to the set of users and groups that should have
access to a specific artifact? The answer is through roles. Java EE allows the
developer to define an arbitrary set of roles and to restrict access to artifacts based
on these roles. Later, the developer (or an administrator) can map these roles to
actual users and groups.
3. Java EE has two forms of role-based security: Declarative security, where the
security constraints limiting access are defined in the deployment descriptors and
the Java EE runtime is the mechanism that manages access to the Java EE
artifact. Consider this as coarse-grained security, where the user will see all or
none of the resource. Programmatic security, where the user code queries if a
user is in a role, and then executes different statements depending on whether the
user is in the role or not. Consider this as fine-grained security, where the user
might only see a subset of the resource depending on his role.
4. In Community Edition’s web console, select Security -> Users and Groups.
5. A Java EE (three-tiered) application using Community Edition and DB2 will
improve its security and performance when using trusted contexts because the
user ID's are always preserved for security, and auditing, they are not "lost" behind
the database user ID used by Community Edition to connect to the database (as it
would without trusted contexts). In addition, performance is improved because by
using trusted contexts, each user ID does not need to create a new database
connection.
6. C
7. E
8. A, D
9. B
10. E
Chapter 9 – Administering
1. Use the following steps to start the Community Edition server on Linux platform:
- Change the current directory into /bin,
- Run startup.sh.
2. To override all the default port numbers, one can change the PortOffset
parameter in /var/config/configsubstitutions.properties.
3. Use following Steps to add a library to the server repository: