CA TPX Session Management for z/OS

Repository Tip - Group Profile Administration in WSO 

05-04-2015 09:33 AM

When accessing CA Repository Webstation Option, if users are going to share user IDs or use the generic user ID defined in the WSO server configuration file, WSOServerProperties.xml, to automatically log in, all users using that User ID can access the same user profiles. This means that any of those users can edit and delete any of the user profiles. In this case, the Repository administrator should consider setting up group profiles to prevent all users from updating the same user profiles.

There are two tables that control the profile information. Both tables reside on the mainframe but are not maintained as CA Repository Webstation Option metadata tables:

  • The user profile table (DBX_USER_PREF) is updated automatically any time a user makes a change to a user profile using the My Profiles on Profile Administration panel in CA Repository Webstation Option. The user profile table is what actually defines which search objects and topics are made available to the end user.
  • The group profile table (DBX_USER_GROUP) can only be updated directly on the mainframe by the Repository administrator. The group profile table does not contain the search objects or topics for categories. Instead, it defines who can access information in an existing user profile, by connecting information in the group profile table with matching information in the user profile table.

Typically the Repository administrator maintains the profile tables. As more users create user profiles, the Repository administrator should periodically clean up the DBX_USER_PREF and DBX_USER_GROUP tables by deleting any obsolete information from these tables. This task can be done using standard DB2 tools.

Any user profile can be turned into a group profile by inserting rows into the DBX_USER_GROUP table. Each row in table DBX_USER_GROUP represents a user and the associated group profile they can access. The following attributes in the DBX_USER_GROUP table are what associate the group profile to the user profile:

  • The GROUPID must match a USERID found in the DBX_USER_PREF table.
  • The GROUP_PROF_NAME must match a PROFILE_NAME found in the DBX_USER_PREF table. The USERID is the DB2 User ID of the CA Repository Webstation Option user.

Creating a group profile is done using CA Repository Webstation Option to first create a user profile, and then using DB2 tools on the mainframe to edit the group profile table to create the group profile:

1. Create a user profile using the CA Repository Webstation Option interface to contain the objects that will be available to end users.
For example, the user ADMIN01 signs on to WSO and creates a profile called End_User For more information about creating a user profile, see Create a User Profile in the CA Repository Webstation Option online help.
2. Use DB2 tools on the mainframe to update the Profile table to set the User ID for the profile to a name that is not used by CA Repository Webstation Option users.
For example, the USERID is set to GROUP1. UPDATE DBX_USER_PREF Set USERID = 'GROUP01' Where USERID = 'ADMIN01' and profile_name = 'End_User'
The group profile is created and the user ADMIN01 is assigned to the group GROUP1.

Define the relationship between User Profile and Group Profile

1. Insert a row into the DBX_USER_GROUP table for each end user who can access the user profile. For a description of the table attributes, see Group Profile Table.
2. Add the new user to the DBX_USER_GROUP table using DB tools on the mainframe and associate it with the profile, using the following command:

INSERT INTO DBX_USER_GROUP Values ('GROUP01', 'USER01', 'End_User', CURRENT_TIMESTAMP)

The insert permitted the user ID USER01 to use profile End_User created by group GROUP01. User USER01 is now able to set the End_User profile as the current profile within CA Repository Webstation Option. However, USER01 cannot edit the group.

Statistics
0 Favorited
0 Views
0 Files
0 Shares
0 Downloads

Tags and Keywords

Related Entries and Links

No Related Resource entered.