+

Search Tips   |   Advanced Search

(zos)

Controlling application environments with RACF server class profiles

The Resource Access Control Facility (RACF ) server class profiles are used to control dynamic application environments. Dynamic application environments are displayed and controlled separately from static application environments.

To set up both the three-part or four-part RACF server class profiles for the application server or cluster for the dynamic application environment, the user ID for the servant must be given read access to both of the profiles.

The Resource Access Control Facility (RACF) server class profiles are used to:

  1. Permit the unauthorized WebSphere Application Server servant access to controller services

  2. Control dynamic application environments, which are displayed and controlled differently from static application environments

Choose between two SERVER class profiles. You need one of these profiles, and which profile we need correlates to dynamic application environment (DAE) support.


Three-part profile

The existing three-part profile has the form:

subsystem_type.subsystem_name.application_environment_name

where:

The four-part profile adds the cell name to avoid ambiguities with existing profile names. The four-part profile has the form:

subystem_type.subsystem_name.application_environment_name.cell_name

where:

Three-part profile names:

Four-part profile names:

If we do not want to discriminate between any of the application servers, we can eliminate all the specified profiles and use a generic form to cover the three and four-part names for all the servers in the sysplex:


Related tasks

  • Secure specific application servers