Avaya Event Processor Release 2.2 Operations, Administration, and Maintenance Interface

Transcription

1 Avaya Event Processor Release 2.2 Operations, Administration, and Maintenance Interface Document ID: Release 2.2 July 2008 Issue No.1

2 2008 Avaya Inc. All Rights Reserved. Notice While reasonable efforts were made to ensure that the information in this document was complete and accurate at the time of printing, Avaya Inc. can assume no liability for any errors. Changes and corrections to the information in this document might be incorporated in future releases. Documentation disclaimer Avaya Inc. is not responsible for any modifications, additions, or deletions to the original published version of this documentation unless such modifications, additions, or deletions were performed by Avaya. Link disclaimer Avaya Inc. is not responsible for the contents or reliability of any linked Web sites referenced elsewhere within this documentation, and Avaya does not necessarily endorse the products, services, or information described or offered within them. We cannot guarantee that these links will work all the time and we have no control over the availability of the linked pages. License USE OR INSTALLATION OF THE PRODUCT INDICATES THE END USER'S ACCEPTANCE OF THE TERMS SET FORTH HEREIN AND THE GENERAL LICENSE TERMS AVAILABLE ON THE AVAYA WEB SITE ("GENERAL LICENSE TERMS"). DO NOT USE THE PRODUCT IF YOU DO NOT WISH TO BE BOUND BY THE GENERAL LICENSE TERMS. IN ADDITION TO THE GENERAL LICENSE TERMS, THE FOLLOWING LICENSE TERMS AND RESTRICTIONS WILL APPLY TO THE PRODUCT: Avaya grants End User a license within the scope of the license types described below. The applicable number of licenses and units of capacity for which the license is granted will be one (1), unless a different number of licenses or units of capacity is specified in the Documentation or other materials available to End User. "Designated Processor" means a single stand-alone computing device. "Server" means a Designated Processor that hosts a software application to be accessed by multiple users. "Software" means the computer programs in object code, originally licensed by Avaya and ultimately utilized by End User, whether as stand-alone Products or pre-installed on Hardware. "Hardware" means the standard hardware Products, originally sold by Avaya and ultimately utilized by End User. License type(s): Concurrent User License (CU. End user may install and use the Software on multiple Designated Processors or one or more servers, so long as only the licensed number of Units are accessing and using the Software at any given time. A "Unit" means the unit on which Avaya, at its sole discretion, bases the pricing of its licenses, and can be, without limitation, an agent, port, or user, an or voice mail account in the name of a person or corporate function (e.g., webmaster or helpdesk), or a directory entry in the administrative database utilized by the product that permits one user to interface with the Software. Units may be linked to a specific, identified Server. Database License (DL). Customer may install and use each copy of the Software on one Server or on multiple Servers provided that each of the Servers on which the Software is installed communicate with no more than a single instance of the same database. Copyright Except where expressly stated otherwise, the Product is protected by copyright and other laws respecting proprietary rights. Unauthorized reproduction, transfer, and or use can be a criminal, as well as a civil, offense under the applicable law. Third-party components Certain software programs or portions thereof included in the Product may contain software distributed under third party agreements ("Third Party Components"), which may contain terms that expand or limit rights to use certain portions of the Product ("Third Party Terms"). Information identifying Third Party Components and the Third Party Terms that apply to them is available on the Avaya Support Web site: Avaya fraud intervention If you suspect that you are being victimized by toll fraud and you need technical assistance or support, call the Technical Service Center Toll Fraud Intervention Hotline at for the United States and Canada. Suspected security vulnerabliities with Avaya products shoud be reported to Avaya by sending to securityalerts@avaya.com. For additional support telephone numbers, see the Avaya Support Web site: Trademarks Avaya is a trademark of Avaya Inc. All non-avaya trademarks are the property of their respective owners. Downloading documents For the most current versions of documentation, see the Avaya Support Web site: Avaya support Avaya provides a telephone number for you to use to report problems or to ask questions about your product. The support telephone number is in the United States. For additional support telephone numbers, see the Avaya Support Web site:

3 Contents Contents About the Event Processor OAM interface Administrative road map Security best practices for administration Chapter 1: The Event Processor OAM Interface Logging in to the OAM interface Interface layout Logging off Changing administrator passwords Assistance for users with disabilities Global login properties Configuring global login properties Login Session field descriptions Chapter 2: Administering resources Working with views, categories and groups Required permissions Creating categories Creating groups Copying groups to a different category Moving groups to a different category Copying categories to a different view Moving categories to a different view Removing groups Removing categories Adding resources to groups Removing resources from groups User administration View a list of users Add a user to the Event Processor system User configuration fields Search for a user Unlock a user Delete a user Roles overview Role definition Operations Access permissions Avaya Event Processor 2.2: OAM Interface July

4 Contents Default roles Administering roles Adding a new role Editing general role options Editing a role to add operations Editing a role to add users Editing a role to assign data access permissions Displaying group membership for a role Displaying user role assignments Administering permissions for a user Chapter 3: System maintenance tasks User Management System Maintenance Run Log Viewer Run Alarm Manager System Configuration Manage Administrative Data Administer Log and Alarm Options Utility Run Ping Test Administer Scheduled Jobs System Properties Connection Management Security Administer Server Certificates Trusted Certificates Synchronized JKS (Java Key Store) Event Processor Index Avaya Event Processor 2.2: OAM Interface July

5 About the Event Processor OAM interface The Event Processor Operations Administration and Maintenance (OAM) interface provides a centralized, web location for roles-based administration of the Event Processor application. Administrative functions other than roles-based administration (and some basic utilities) are provided through the EP Console, a separate web-based application included with Event Processor. The Event Processor OAM Interface provides a link to the EP Console, which is discussed in more detail in Chapter 7 of the Avaya Event Processor 2.2: User s Guide. The Event Processor OAM interface is available only to those users who have installed the Production Edition of Event Processor (as opposed to the Developer Edition). For details on the two installations, refer to the Avaya Event Processor 2.2: User s Guide. It includes the following capabilities: Web browser interface that eliminates the need for client software installation and maintenance. Grouping of resources to reflect business structure, from broad to fine levels of granularity. Creation of user roles and permissions to provide access control. Administrative road map Avaya recommends administering the system as follows: User administration: Create roles, operations, and permissions for managers and system administrators, as described in the following sections: User administration on page 16 Roles overview on page 19 Access permissions on page 21 Roles and permissions: Administer roles and permissions for users. This information is described in the following sections: Roles overview on page 19 Administering roles on page 23 Avaya Event Processor 2.2: OAM Interface July

6 About the Event Processor OAM interface Access permissions on page 21 Administering permissions for a user on page 28 Routine maintenance procedures: Global login properties on page 10 Unlock a user on page 18 Security best practices for administration Use the following best practices to help maintain a secure environment: Use role assignments to appropriately restrict access to operations. For more information, see Roles overview on page 19. Use data access permissions to appropriately restrict access to resource data. For more information, see Editing a role to assign data access permissions on page 25. Use the Login Session Properties to help prevent unauthorized access. For more information, see Global login properties on page 10. Do not create shared logins or allow use of shared logins. For accountability, each user must have a unique login ID. Instruct users to not share their login ID and password. For more information, see User administration on page 16. Instruct users to check the displayed time and date of their last successful login. If the user reports unknown activity on their account, either change the password on that account, or delete the account and give the user a new account. Deleting an account does not impact the namespace associated with the user. Periodically review and update the list of administered users, their roles, and their permissions. Review administration audit logs on a regular basis to check the validity of administration changes. Review audit logs on a regular basis to ensure that the system is operating properly. Review security logs and alarms on a frequent basis to monitor possible security events. 6 Avaya Event Processor 2.2: OAM Interface July 2008

7 Chapter 1: The Event Processor OAM Interface Logging in to the OAM interface 1. Open your browser, and enter the following URL: or ip-address>:8080/cs-oam where EP-hostname is the host name of the Event Processor server or ip-address is the IP address of the Event Processor server. 2. In the Logon Id field, enter your user name. 3. In the Password field, enter your password, and then click Logon. The OAM interface appears. Interface layout The Event Processor OAM interface consists of a navigation pane on the left and a work pane on the right. In the navigation pane, there are two tabs, Tasks and Enterprise. Tasks: The Tasks tab provides access to the following operations: User Management. Refer to User administration on page 16 and Unlock a user on page 18 for more details. System Maintenance, which includes the Log Viewer and Alarm Manager. Refer to Run Log Viewer on page 32 and Run Alarm Manager on page 32 for more details. System Configuration, which includes the Manage Administrative Data and Administer Log and Alarm Options. Refer to Manage Administrative Data on page 33 and Administer Log and Alarm Options on page 34 for more details. Utility, which includes ping and job scheduling options. Refer to Utility on page 34 for more details. System Properties, which provides login session property administration. Refer to Global login properties on page 10 for more details. Avaya Event Processor 2.2: OAM Interface July

8 Chapter 1: The Event Processor OAM Interface Connection Management, which provides for the administration of connection properties. The Connection Management options are not supported for use with Event Processor 2.2. Security, which provides for the management of server certificates. Refer to Security on page 35 for more details. Event Processor, which provides a link to the EP Console, a web-based application for the administration of a running Event Processor server instance. Enterprise: The Enterprise tab gives you access to the following operations: Sites, which provides for host administration. The Site options, which provide options for the maintenance of hosts, are not supported for use with Event Processor 2.2. Resources, which provides options for managing resources including users, roles, and operations. For more details, refer to Chapter 2: Administering resources. The tool bar provides access to the following features: Home: The Home link displays the Welcome to OAM dialog. Help: The Help link for the current release is a placeholder for future on-line help.. Log Off: The Log Off link logs you out of the administration interface. Logging off When finished with a session, make sure to log out. Logging out prevents unauthorized users from accessing administrative features. To log out, click on the Log Off option on the tool bar. If you do not log out manually, your session times out based on the session timeout values defined in the Login Session Properties view. Changing administrator passwords 1. Navigate to System Configuration > Manage Administrative Data. 2. Click on the Change Password link. The Change Administrator Password window appears. 8 Avaya Event Processor 2.2: OAM Interface July 2008

9 Assistance for users with disabilities 3. Enter the User Id. 4. Enter the current Admin Password. 5. Enter the New Password. 6. Re-enter the new password in the Confirm New Password field. Although the Event Processor 2.2 OAM interface does not enforce password rules, the following guidelines should be used when creating or modifying passwords: Passwords should be 8 to 14 characters long. Passwords should include a mix of the following character types: - Lower case letters - Upper case letters - Numerals - Other keyboard symbol punctuation marks and non-alpha characters Note also that: Passwords are case sensitive. A password should not be identical to the previous 10 passwords for the User Id. Your last name, first name, or any other personal information should never be used. Passwords should be changed every 90 days. After submitting the change, a success or failure message displays. If the change was not accepted, try again, making sure to enter the user ID and passwords correctly. Verify that the Caps Lock key is not on. Assistance for users with disabilities This section contains tips for users with disabilities. These tips may be used during administration sessions to help users better navigate the interface. The Firefox browser tends to render the administration interface better than the Internet Explorer browser. Tab can be used to move through dialogs, though some tab operations may be less than optimal. In some cases, you might have to tab through fields that are not part of the dialog to get to all of the option fields. Icons in the interface have tool tips that are recognized by screen readers. Avaya Event Processor 2.2: OAM Interface July

10 Chapter 1: The Event Processor OAM Interface Global login properties Configuring global login properties 1. Log in to the OAM interface. In the navigation pane, click System Properties > Administer Login Session. The Login Session Properties page is displayed. 2. View or change the settings as appropriate. For information on each field, see Login Session field descriptions. 3. Click Submit to save changes. Login Session field descriptions Table 1: Login Session field descriptions Field Maximum Failed Login Attempts Description Number of failed login attempts that a user can make before he or she is locked out of the system. The user cannot log in again until the Lockout Duration time expires. The valid range is 1 to 999. The default value is 3. Lockout Duration Number of minutes that a user must wait after being locked out of the system before he or she can attempt to log in again. The valid range is 1 to 99 minutes. The default value is 10. Maximum Failed Authentication Attempts Session Timeout Duration Number of failed authentication attempts that a user can make before the system logs an alarm. For example, if this value is set to 5, five login attempts would be the equivalent to a single authentication attempt. The valid range is 1 to 999. The default value is 3. Number of minutes that an OAM login session can be inactive before the user is logged out. The valid range is 5 to 1440 minutes (24 hours). The default value is 90. Initial Password Change Select either Enable or Disable to determine whether a user is prompted to change their password at the initial login. 10 Avaya Event Processor 2.2: OAM Interface July 2008

11 Chapter 2: Administering resources There are three types of resources in the Event Processor OAM Interface: Operation Role User The Event Processor OAM interface enables you to organize resources according to views, categories, and groups. The Resources folder, under the Enterprise tab, contains the following default hierarchy of views, categories, and groups: All Resources (view) - Application Operations (category) Operations (group) - Roles (category) Enterprise Roles (group) Services Roles (group) - User Management (category) Enterprise Users (group) Functional (view) Location (view) Organizational (view) User Defined (view) The All Resources view, with its pre-defined categories and groups, enables you to initially create resources according to their type (Operation, Role, or User), as well as to add resources to groups. The other four views - Functional, Location, Organizational, and User Defined - are empty (without categories and groups.) Initially, when defining groups, resources can be selected only from the All Resources view. Once categories and groups have been added to the other four views, resources can be added from those groups. Tip: Tip: Avaya recommends creating all categories and groups before adding any resources to the groups. For details on creating categories and groups, refer to the next section, Working with views, categories and groups. Avaya Event Processor 2.2: OAM Interface July

12 Chapter 2: Administering resources Working with views, categories and groups Required permissions To administer resource groups, the administrator must have the following permissions: To create a category, the administrator must have read, add, and change permissions on the parent view. To create a group, the administrator must have read, add, and change permissions on the parent category. To add resources to a group, the administrator must have read and change permissions on the group. To copy a category, the administrator must have change permission on the originating category, and add and change permission on the destination category. To copy a group, the administrator must have change permission on the originating group, and add and change permission on the destination group. To move a category, the administrator must have delete permission on the originating category and change permission on the destination category. To move a group, the administrator must have delete permission on the originating group and change permission on the destination group. Creating categories 1. Under the Enterprise tab, expand the Resources folder. 2. Select one of the views. 3. Click New. The Create New Category dialog displays. 4. Enter a name and description for the category. 5. Select OK. Creating groups 1. Under the Enterprise tab, expand the Resources folder. 2. Expand one of the views. 3. Select a category under the expanded view. 12 Avaya Event Processor 2.2: OAM Interface July 2008

13 Working with views, categories and groups 4. Click New. The Create New Group dialog is displayed. 5. Enter a name and description for the group. Under the Type field, select the resource type that matches the group you are creating: Operations Roles Users 6. Select OK. Copying groups to a different category 1. Under the Enterprise tab, select Expand All. 2. Select the category that contains the group to be copied. 3. In the Resource View, highlight the group you want to copy. Do not double-click the group. 4. Select Copy. The Select Destination for Copy dialog displays. 5. Modify the name and description, if needed. 6. In the Select Destination For Copy pane, expand the resource tree until the desired category is displayed. 7. Select the category where you want to copy the group. 8. Select Allow Duplicates if you want to add resources that have already been added to other groups under the same view. 9. Select OK. The group is copied to the category. Moving groups to a different category 1. Under the Enterprise tab, select Expand All. 2. Select the category that contains the group to be moved. 3. In the Resource View, highlight the group you want to move. Do not double-click the group. 4. Select Move. The Move to New Location dialog displays. 5. Under the Select Destination For Move pane, expand the resource tree until the desired category is displayed. 6. Select the category where you want to move the group. 7. Select Allow Duplicates if you want to add resources that have already been added to other groups under the same view. 8. Select OK. The group is moved to the category. Avaya Event Processor 2.2: OAM Interface July

14 Chapter 2: Administering resources Copying categories to a different view 1. Under the Enterprise tab, select Expand All. 2. Select the view that contains the category to be copied. 3. In the Resource View, highlight the category you want to copy. Do not double-click the category. 4. Select Copy. The Select Destination for Copy dialog displays. 5. Modify the name and description, if needed. 6. Under the Select Destination For Copy pane, expand the resource tree until the desired view is displayed. 7. Select the view where you want to copy the category. 8. Select Allow Duplicates if you want to add resources that have already been added to other groups under the same view. 9. Select OK. The category is copied to the view. Moving categories to a different view 1. Under the Enterprise tab, select Expand All. 2. Select the view that contains the category you want to move. 3. In the Resource View, highlight the category you want to move. Do not double-click the category. 4. Select Move. The Move to New Location dialog displays. 5. Under the Select Destination For Move pane, expand the resource tree until the desired view is displayed. 6. Select the view where you want to move the category. 7. Select Allow Duplicates if you want to add resources that have already been added to other groups under the same view. 8. Select OK. Removing groups 1. Under the Enterprise tab, select Expand All. 2. Select the category that contains the group you want to remove. 14 Avaya Event Processor 2.2: OAM Interface July 2008

15 Working with views, categories and groups 3. In the Resource View, highlight the group you want to remove. Do not double-click the group. 4. Select Delete. A confirmation message displays. 5. Select OK. The group is removed from the category. Removing categories CAUTION:! CAUTION: Removing a category removes all groups under the category. If any of the groups are still valid for another category, move those groups before you remove the category. 1. Under the Enterprise tab, select Expand All. 2. Select the view that contains the category you want to remove. 3. In the Resource View, highlight the category you want to remove. Do not double-click the category. 4. Select Delete. A confirmation message displays. 5. Select OK. The category is removed from the view. Adding resources to groups 1. Under the Enterprise tab, select Expand All. 2. Select a group under the expanded view. 3. Select Add. The Add Resources dialog displays. 4. Under the Resource Selector pane, expand the resource tree until the desired group of available resources is displayed. 5. Select the resources you want to add to the group. If there is more than one page of resources, step through each page to select the resources you want to add to the group. Use the search function to find a particular resource. 6. Select Allow Duplicates if you want to add resources that have already been added to other groups under the same view. 7. Select OK. The resources added to the group are displayed. Avaya Event Processor 2.2: OAM Interface July

16 Chapter 2: Administering resources Removing resources from groups 1. Under the Enterprise tab, select Expand All. 2. Select a group under the expanded view. 3. Select the resources you want to remove from the group. 4. Select Remove. A confirmation message displays. 5. Select OK. User administration View a list of users 1. From the Tasks view, expand the User Management folder. 2. Click on the Administer Users option. 3. Click on the List All Users link. The OAM interface displays a list of all the users that have access to the Event Processor server. From the buttons below the list, it is possible to, depending on your role: - Edit user information - Delete a user - View Details about a user - List All the users in the system. Use the scrollbar to view all users. Select the user, and click on the appropriate button. You can also use the search feature when there are too many users for the initial view. Refer to Search for a user on page 18 for details. Add a user to the Event Processor system 1. From the Tasks view, expand the User Management folder. 2. Click on the Administer Users option. 3. Click on the Create User link. A list of the required and optional data fields appears. 16 Avaya Event Processor 2.2: OAM Interface July 2008

17 User administration 4. Enter the information for the fields. For detailed field information, refer to the next section, User configuration fields. User configuration fields Field User ID Common Name Surname User Password Confirm Password Avaya Role Description Required - The user s login ID Required - The user s first name Required - The user s last name Required - User password Required - Re-enter the password Required - The user role for interactive OAM purposes and must be the string userservice.useradmin. For details on defining roles refer to the Administering roles section in this chapter. The table above lists only the minimum required fields and entry requirements. Additional user information can be entered in the other fields, according to the needs of your organization, including: Department Number Cell phone (mobile) Home postal address Employee Type Css home Given Name CM home Display Name MM Home Enterprise Handle Initials Admin Note Room Number Avaya Event Processor 2.2: OAM Interface July

18 Chapter 2: Administering resources Home Phone Pager Organization Employee Number Telephone Number Car License Business Category Preferred Language Mail Labeled URI There is no particular entry format for the optional user fields. The Event Processor application does not use the information from these fields. Search for a user 1. From the Tasks view, expand the User Management folder. 2. Click on the Administer Users option. 3. Click on the Search users link. 4. Select an option from the Search Attribute drop-down list: - User Id - Common Name - Surname 5. Enter a value in the Search Value box. 6. Click on Search. The search results view displays a list of matching items, which can then be viewed or edited as necessary. Unlock a user To unlock a user locked out for exceeding the maximum number of login attempts, follow these steps: 1. From the Tasks view, expand the User Management folder. 2. Click on the Unlock User Accounts option. 18 Avaya Event Processor 2.2: OAM Interface July 2008

19 Roles overview 3. Select the Locked User, or the Select All link. 4. Click on the Unlock Account button. Delete a user To delete a user: 1. Under the Tasks tab, select User Management > Administer Users > List All Users. 2. Select one of the users. 3. Select Delete. 4. After the Confirm Action screen is displayed, select Delete User to delete the user or Cancel to cancel your action. Roles overview User roles provide the following capabilities: Control access to administration operations Ability to assign the same set of permissions to one or more users that perform similar tasks Role definition Roles definition consists of specifying the operations assigned to a role, the users assigned to a role, and the access permissions defined for the user/role: Operations are the tasks that users are allowed to perform and are the basis for the roles created. To simplify user administration, similar operations can be grouped into appropriate roles according to business structure. Users can be assigned to a single role or to multiple roles. When you assign two or more roles to a user, the user gains the cumulative permissions of all of the assigned roles. If a role is deleted, its permissions are removed from any users assigned to that role. Refer to Administering roles on page 23 and Adding a new role on page 24 for more details. Access permissions define what users can view, add, edit, or delete. Operations, and permissions are discussed in more detail in the sections that follow. Avaya Event Processor 2.2: OAM Interface July

20 Chapter 2: Administering resources Operations Application operations control access to administration tasks, and are assigned to roles. An operation can consist of a single task, or multiple tasks. The following sections list all the operations included in the Event Processor OAM Interface, grouped by category: Administrative operations Maintenance operations Administrative operations Administer Certificate Defaults: Set up defaults for trusted certificates. Administer Connections: Configure connections to external data sources and databases. Administer Login Session Properties: Set login session properties. Administer Roles: Define roles. Administer Sites and Hosts: Administer sites and hosts. Administer Users: Manage enterprise users. EP Console: Access the web-based Event Processor administrative console. Manage Administrative Data: Perform administrative tasks associated with the user service. Synchronize JKS: Synchronize the Java Key Store (JKS). Unlock User Accounts: Unlock user accounts that have been disabled due to failed login attempts. View Pending Certificate Requests: View pending certificate requests. Maintenance operations Administer Log and Alarm Options: Set alarm and log retention periods. Run Alarm Manager: Access the alarm manager and run alarm reports. Run Log Viewer: Access the log viewer and run log reports. Run Ping Test: Send a ping test message to another host to confirm network connectivity. 20 Avaya Event Processor 2.2: OAM Interface July 2008

21 Roles overview Access permissions View: View permissions allow users to view data for existing resources. Edit: Edit permissions allow users to edit parameters of existing resources, categories, or groups. Add: Add permissions allow users to add new resources, categories, or groups. Delete: Delete permissions allow users to delete existing resources. For user permissions, there are two additional options: User Override: When administering permissions for a user, this option overrides any role permissions that are assigned to the user. With User Override, you can override the role permission assignment and also grant edit permissions to the user. The override option is valuable when you have a large group of users where the majority of the group only needs limited permissions, but one or two of the users in the group require additional permissions. No Permissions: This option allows you to quickly remove all permissions for a user. This can be useful if there is a behavior issue with a user and you want to remove all of their access without removing their user ID. Operations permission changes made to a user do not take effect until after the user logs out of the system and then back into the reporting or administration application. Data access permissions only require a refresh of the browser cache. Default roles The Event Processor OAM Interface includes default roles to help begin administration. The Avaya provisioning team or your Business Partner initially assigns your system administrators to a role that can administer all system features. These system administrators can then assign the default roles or define new roles for other users. Default user roles are grouped into two main categories: Enterprise: This category includes roles for all enterprise users on your system. These roles are also used by Business Partners during implementation. The enterprise users category has two default roles: System Administrator Installer Services: This category includes roles for login IDs used by Avaya services personnel who work on the initial implementation and provide ongoing support of your system. These roles are not displayed to enterprise users and cannot be edited by enterprise users. Avaya Event Processor 2.2: OAM Interface July

22 Chapter 2: Administering resources The services users category has two default roles: Services Admin (sroot login ID) Services Tech (craft login ID) The default roles have access to the following operations. Operation Enterprise (Customer) Services (Avaya) System Administrator Installer Services Admin (sroot) Services Tech (craft) Administer Server Certificates Administer Certificate Defaults X X View Pending Certificate Requests X X Connection Management Administer Connections X X Event Processor Event Processor Console X X RBAC Administer Roles X X Security Administer Server Certificates X X Synchronize JKS X X Subsystem Administer Sites and Hosts X X System Configuration Administer Log and Alarm Options X X X X Manage Administrative Data X X System Maintenance Run Alarm Manager X X X X 22 Avaya Event Processor 2.2: OAM Interface July 2008

23 Administering roles Operation Enterprise (Customer) Services (Avaya) System Administrator Installer Services Admin (sroot) Services Tech (craft) Run Log Viewer X X X System Properties Administer Login Session Properties X X X User Management Administer Users X X Unlock Administration User Accounts X X Utility Administer Scheduled Jobs X X Run Ping Test X X Administering roles Once you have determined the necessary user roles, they can be added to the Enterprise Roles group. The Services Roles group is designated for Avaya services personnel, and roles cannot be added to the Services Roles group. Creating a role includes the following procedures: Adding a new role on page 24 Editing general role options on page 24 Editing a role to add operations on page 24 Editing a role to add users on page 25 Editing a role to assign data access permissions on page 25 In addition to these tasks, you can also do the following procedures: Displaying group membership for a role on page 27 Displaying user role assignments on page 27 Avaya Event Processor 2.2: OAM Interface July

24 Chapter 2: Administering resources Adding a new role 1. Under the Enterprise tab, select Resources > All Resources > Roles > Enterprise Roles. The Resource Management-Enterprise Roles dialog displays. 2. Click New. The Create New Role dialog displays. 3. Enter a name and description for the role. The Managed Resource Group option defaults to Roles. 4. Select OK. Editing general role options 1. Under the Enterprise tab, select Resources > All Resources > Roles > Enterprise Roles. The Resource Management dialog displays the existing roles. 2. Select the role you want to edit. 3. Select Edit. The Resource Editor dialog is displayed for the selected role. 4. Select the General tab. 5. Change the name or description for the role. 6. Select Apply. The General tab refreshes showing the new information. 7. Click on Close to leave role administration. Editing a role to add operations 1. Under the Enterprise tab, select Resources > All Resources > Roles > Enterprise Roles. The Resource Management dialog displays the existing roles. 2. Select the role you want to edit. 3. Select Edit. The Resource Editor dialog displays for the selected role. 4. Select the Operations tab. A list of operations is displayed, including those that are already assigned to the role and those available for assignment. 24 Avaya Event Processor 2.2: OAM Interface July 2008

25 Administering roles 5. Do one of the following steps: Select one or more operations in the Available Operations area.continue with Step 6. Select Assign All Operations. A confirmation message is displayed. Continue with Step Select the shuttle up arrow. The selected operations are moved to the Assigned Operations area. 7. Click on Close to exit role administration. Editing a role to add users To add one or more users to a role: 1. Under the Enterprise tab, select Resources > All Resources > Roles > Enterprise Roles. The Resource Management dialog displays the existing roles. 2. Select the role you want to edit. 3. Select Edit. The Resource Editor dialog displays for the selected role. 4. Select the Users tab. 5. Select Add. The Resource Selector dialog displays. 6. Browse through the available resources to view the list of available enterprise users. 7. Select one or more users to add to the role. 8. Select OK. The users assigned to the role are displayed in the Users tab. 9. Click on Close to exit role administration. Editing a role to assign data access permissions To set permissions for a role: 1. Under the Enterprise tab, select Resources > All Resources > Roles > Enterprise Roles. The Resource Management dialog displays the existing roles. 2. Select the role you want to edit. 3. Select Edit. The Resource Editor dialog displays for the selected role. 4. Select the Permissions tab. The Access Permissions Assigned To Role dialog displays. 5. Select Add. The Folder selection dialog displays. 6. Select the view(s) to which you want to apply data permissions access. 7. Select Add. The Folder selection dialog refreshes, displaying the unselected views. Avaya Event Processor 2.2: OAM Interface July

26 Chapter 2: Administering resources 8. Select Close. The Access Permissions Assigned To Role dialog refreshes showing the views that you selected. 9. From the displayed list, select the view to which you want to assign data access permissions. The dialog refreshes showing the permissions you can assign to the view. 10. Select the permissions you want to assign to the view. 11. Set the Populate Children option: If Populate Children is selected, the same permissions are assigned to the view and all its children. Resource permissions are always set to the group level permissions, so the Populate Children option is not relevant for groups. Avaya recommends using the Populate Children option. If Populate Children is not selected, only those children whose permissions match those of the view receive the updated permissions. For example, a role has view only permissions for the Location view and for its Munich category, and view and edit permissions for the Bangalore category. When applying view, edit and add permissions to the Location view, the role will have view, edit and add permissions for the Location view and the Munich category, but will maintain the view and edit permissions for Bangalore. 12. Select Apply. The dialog refreshes showing the categories assigned to the view. 13. Depending on the option you selected, continue with one of the following: If you selected the Populate Children option, you are finished administering data access permissions to this view. Return to Step 9 and continue with the next view. If you did not select the Populate Children option, continue with Step Double-click the view to which you applied the data access permissions. The dialog refreshes showing the categories assigned that you have permission to view. 15. Select the category to which you want to assign data access permissions. Add like categories if none are listed. The dialog refreshes showing the permissions that can be assigned to the category. 16. Select the permissions you want to assign to the category. When you remove all permissions for a view, the view disappears from the list of available views. This is true even if not using the remove button. To see the missing view, it must be added back to the list using the Add operation. The children of the added view are also restored. 17. Set the Populate Children option: If Populate Children is selected, the same permissions are assigned to the category and all its children. Resource permissions are always set to the group level permissions, so the Populate Children option is not relevant for groups. Avaya recommends using the Populate Children option. 26 Avaya Event Processor 2.2: OAM Interface July 2008

27 Administering roles If Populate Children is not selected, only those children that have matching permissions as the category receive the updated permissions for the selected view. 18. Select Apply. The dialog refreshes, showing the groups assigned to the category. 19. Depending on the option you selected, continue with one of the following: If you selected the Populate Children option, you are finished administering data access permissions to this category. Return to Step 15 and continue with the next category. If you did not select the Populate Children option, continue with Step Double-click the category to which you applied data access permissions. The dialog refreshes, showing the groups assigned to the category that you have permission to view. 21. Select the group to be assigned data access permissions. Add like views if none are listed. The dialog refreshes, showing the permissions that can be assigned to the group. 22. Select the permissions to assign to the group. 23. Repeat Steps 21 and 22 for each group. 24. Select Back within the dialog twice to return to the view level. Repeat Steps 9 through 23 for the next view. 25. When finished adding permissions to a role, select Close to exit role administration. Displaying group membership for a role 1. Under the Enterprise tab, select Resources > All Resources > Roles > Enterprise Roles. The Resource Management dialog displays the existing roles. 2. Select the role to edit. 3. Select Edit. The Resource Editor dialog displays for the selected role. 4. Select the Member of tab. The display shows the groups that the role belongs to. 5. Click on Close to exit role administration. Displaying user role assignments This operation displays the following information about users assigned to a role: Users assigned to a role Users that have User Override permission for any role To display role assignments: 1. Under the Enterprise tab, select Resources > All Resources > Roles > Enterprise Roles. The Resource Management dialog displays the existing roles. Avaya Event Processor 2.2: OAM Interface July

28 Chapter 2: Administering resources 2. Select the role you want to edit. 3. Select Edit. The Resource Editor dialog displays for the selected role. 4. Select the Access tab.the display refreshes, showing all of the roles that have been assigned data access permissions to the role being edited. The permissions assignment is displayed with the role. 5. Select a role from the Roles Assigned Access table. 6. Select one of the options from the Users Assigned Access table: - Display all users assigned to the selected role option is the default selection. All of the enterprise users assigned to the role are displayed, along with the data access permissions relevant to the role being edited. - Display all users directly assigned access to the resource. Any users with User Override permissions for any role are displayed. 7. Click on Close to exit role administration. Administering permissions for a user To assign permissions to a user: 1. Under the Enterprise tab, select Resources > All Resources > User Management > Enterprise Users. The Resource Management dialog displays the existing users. 2. Select the user you want to edit. 3. Select Edit. The Resource Editor dialog displays for the selected user. 4. Select the Permissions tab. The Access Permissions Assigned To User dialog displays. 5. Select Add in the Resources pane. The Folder selection dialog displays. 6. Select the views to which you want to apply data access permissions. More than one view can be selected. 7. Select Add. The Folder selection dialog refreshes, showing the unselected views. 8. Select Close. The Access Permissions Assigned To User dialog refreshes showing the selected views. 9. From the displayed list, select the view to which you want to assign data access permissions. The dialog refreshes showing the permissions that can be assigned to the view. 10. Select the permissions to assign to the view. 28 Avaya Event Processor 2.2: OAM Interface July 2008

29 Administering permissions for a user When you remove all permissions for a view, the view disappears from the list of available views. This is true even if not using the remove button. To see the missing view, it must be added back to the list using the Add operation. The children of the added view are also restored. 11. Set the Populate Children option: If Populate Children is selected, the same permissions are assigned to the view and all its children. Resource permissions are always set to the group level permissions, so the Populate Children option is not relevant for groups. Avaya recommends using the Populate Children option. If Populate Children is not selected, only those children whose permissions match those of the view receive the updated permissions. 12. Select Apply. The dialog refreshes, showing the categories assigned to the view. 13. Depending on the option you selected, continue with one of the following: If you selected the Populate Children option, you are finished administering data access permissions to this view. Return to Step 9 and continue with the next view. If you did not select the Populate Children option, continue with Step Double-click the view for which you just applied data access permissions. The dialog refreshes, showing the categories assigned to the view. 15. Select the category to which you want to assign data access permissions. Add like views if none are listed. The dialog refreshes showing the permissions you can assign to the category. 16. Select the permissions you want to assign to the category. When you remove all permissions for a view, the view disappears from the list of available views. This is true even if not using the remove button. To see the missing view, it must be added back to the list using the Add operation. The children of the added view are also restored. Avaya Event Processor 2.2: OAM Interface July

30 Chapter 2: Administering resources 17. Set the Populate Children option: If Populate Children is selected, the same permissions are assigned to the view and all its children. Resource permissions are always set to the group level permissions, so the Populate Children option is not relevant for groups. Avaya recommends using the Populate Children option. If Populate Children is not selected, only those children whose permissions match those of the view receive the updated permissions. 18. Select Apply. The dialog refreshes, showing the groups assigned to the category. 19. Depending on the option you selected, continue with one of the following: If you selected the Populate Children option, you are finished administering data access permissions to this category. Return to Step 15 and continue with the next category. If you did not select the Populate Children option, continue with Step Double-click the category to which you applied data access permissions. The dialog refreshes, showing the groups assigned to the category. 21. Select the group to be assigned data access permissions. Add like views if none are listed. The dialog refreshes showing the permissions you can assign to the group. 22. Select the permissions you want to assign to the group. 23. Repeat Steps 21 and 22 for each group. 24. Select Back within the window twice to return to the view level. Repeat Steps 9 through 23 for the next view. 25. Click on Close to exit user administration. 30 Avaya Event Processor 2.2: OAM Interface July 2008