Monitoring Running Tasks ‘You can use the Running Tasks feature to view and terminate running tasks, You can filter running tasks by application server, user, task performed, and task status, Note: Only the user who starts @ task or a user assigned to the Administrator role can terminate a task that is running ‘You can view and terminate the following tasks: © Consolidation © Data Load © Extended Analytics Export © Post All Transactions © Unpost All Transactions Delete All Transactions © UnMatch All Transactions © AutoMatch by ID © AutoMatch by Account @ IC Matching Report by ID © IC Matching Report by Acct IC Transaction Report, ‘You can filter the running tasks by the following task status types: «Initializing © Running © Paused © Uninitializing «Stopped © Aborted © Completed © Not Responding Scheduled Stop © Scheduled Start > To monitor and stop running tasks: 1. Select Administration > Running Tasks. 50 Managing ApplicationsYou must have an application open for the Running Tasks link to be available. Optional: in the Server Selection text box, enter the server name to filter by application server. If you leave the Server Selection text box blank, tasks running on all servers are listed. Optional «From the User Selection drop-down list, select the user to monitor, or running tasks for all users, I: Set filter options: elect All to view «From the Task Filter drop-down list, select the task to monitor, or select All to view all running tasks. © From the Status Filter drop-down list, select the status type to monitor, or select All to monitor all status types, Click View. The tasks that meet the filtering criteria are displayed. In the Stop Task column, click © next to the task to stop. Note: tice in the Log column ofthe lst o view the log file for a completed task. By default, running tasks remain in the database for 900 seconds (15 minutes). You can change the default by modifying the AutoClearDeadTasksafterSeconds registry key in the HKEY_TOCAL_¥2 ARE\Hyperion Solutiona\Hyperion Financial Management \Server\Running ‘Tasks registry location. The minimum value for the registry Key is 720 seconds (12 minutes); the maximum value is 864,000 seconds (10 days). INES Scanning For and Deleting Invalid Records opwone You can use the Delete Invalid Records feature to scan an application for invalid records and to remove them. Administrator access is required to use this feature Windows Procedure To scan for and delete invalid records: Open the application from which to delete invalid records. From the navigation frame, select Database Management. Click the Delete Invalid Records tab. Browse to or enter the name and path of the log file, Perform a task: © Click Sean, ‘Seanning For and Deleting Invalid Records 51.© Click Delete. 6 Optional To view the lg file, click View, Web Procedure To scan for and delete invalid records: In Browser View, expand Tasks, and select Data Tasks. Select Database Management. > 1. Open the application from which to delete invalid records. 2 3 4 Click Delete Invalld Records. Note: This tab is available only to users with Administrator access. 5 Perform a task: © Click Scan Only. © Click Delete Invalid Records. Changing Settings for Multiple Server Tasks There are several registry settings that control the amount of consolidations, data loads, and Extended Analytics exports that can run at any one time in a multi-server environment. Ifyou nced to run several concurrent consolidations for example, you can change the values in these registry settings. Registry Setting Description MaxNumConcurrentConsolidations Controls the numberof concurtent consolidations allowed per application server, Any consolidations executed above the value are queved as Scheduled Consolidations, Minimum value is 1; maximum value is 8 NumConsalidationThreads Contvols the mutt-threading of consolidations per application sewer. Lowering ‘the value limits the systems utilization of system resources, resukng in lower consolidation perfomance. Minimum value is 1; maximum value is 8. NumConsoldationsAllowed Conivols the numberof consolidations allowed per aplication across all he application serves, Default value is 8 and the range is 1-20, NumbataLoadsAllowed Contos the numberof data loads allowed per application across all the application serers. Default value is 8 and the range is 1-20. NumEAExporisAllowed Contos te number of Extended Analytic expots allowed per application across all te application servers, Default value is 8 and the range is 1-20, > To change a server registry setting: 1. Select Start > Run. Managing Applications2. Inthe Open box, type regedt32, and click OK. 3. Select =xEv_LOCAL_WACHTNE\SOFTHARF\Hyperion Solutions \#yperion Financial ment \Server\RunningTasks lick the registry setting that you want to change, change the value, and click OK. Maintaining Server Logon Information When you use application server clusters, by default, users are kept on the same application server for subsequent logons. For example, a user logged on to Financial Management who runs reports with Oracle's Hyperion® Financial Reporting — System 9 will always use the same application server, instead of potentially logging on to different application servers, You can create the UseStickyServer cluster level registry setting on the client to disable Sticky Server support. You must create the registry setting for each Web server and Win32 client. > To disable UseStickyServer support 1 Navigate to HKEY_LOCAT_MACH=NE\SOFTWARE\Hyperion Solutions\Hyperion Pinancial Management\Client \Clusters\machinenane, 2. Greate a REG_DWORD value named UseStickyServer. 3. Enter the value “0” To enable it, change the value to 1, or delete the key. By default, a“I” is assumed ifthe key is missing Maintaining Server Logon Information §354 Managing Applications3 Managing Application Security In This Chapter Application Security Considerations 56 Launching the User Management Console trom Financial Management. 88 Loading Application Secu. 83 Extracting Application SecUiy... sot snniesetneninntnnenenenneninentieninnennneenennesese 68 ‘There are two ways to set up security for Financial Management applications: © Load a security file into an application, See “Loading Application Security” on page 63 Use the User Management Console to set up security information. See “Launching the User Management Console from Financial Management” on page 56. Security and access rights enable you to control access to Financial Management applications and application elements. Setting up security enables you to protect data and prevent ‘unauthorized users from changing data. For example, you can restrict access to certain data elements or forms within an application. Security exists at two levels: «Authentication by an external provider Financial Management security, in which users and groups are assigned to applications and application elements are assigned to security classes. Note: For information on setting up users, see “Configuring External Authentication for Shared. Services” in the Hyperion Security Administration Guide. ‘The following security roles are required for application administration. For information on assigning roles, see the Hyperion Security Administration Guide. ‘Security Role Description Dimension Elitor Creates and manages impot profes for dimension creation, as well as creating and managing dimensions ‘manually within the Performance Management ‘rchitectuser interface or the Classic Anplication ‘Adminstration option,