COGNOS Business Intelligence Series 7
pes.pdf pes.pdf
Chapter 3: Control Processes PowerPlay Enterprise - Server Administration Use PowerPlay Enterprise - Server Administration to check the properties and monitor the status of each cube and report. PowerPlay client applications can only explore a cube or run a report when all of the following conditions are met: • The cube or report has been added to a PowerPlay server, or is a mirror reference on a PowerPlay server. • The cube, report, and its parent objects are enabled ( icon). • The PowerPlay server from which the cube is available is started and enabled. • Web ( icon) or Windows ( icon) access privileges have been correctly assigned. • Your preferred Web publishing method has been enabled and configured, to let users know that the data is available. You can also send users a direct URL to cubes and reports. • Any required network access rights and other forms of security access, such as Access Manager user classes, have been assigned. Use the Monitor tab to monitor the number of open processes for a cube or report (or all the cubes and reports in a folder), and the maximum number of processes available, as specified in the Cube or Report Properties dialog box. For example 2/5 means that there are currently two processes open out of five available processes. Other events you can monitor depend on whether the connection is for Web or Windows (or both). Monitor Web Connections For a connection from the Web to a query or report processor, you can monitor the following from PowerPlay Enterprise - Server Administration. Column Queue sec/Hit Hits/min Description The number of requests in the queue that are waiting to be processed The average time to process requests received in the last minute The number of PowerPlay Web requests (hits) received in the last minute For a Web connection, the server engine generates pages in HTML format. It generates a new page whenever data is requested by the user from the Web browser, for example, when a user opens a cube, drills down on a category, or changes the measure. Only the most recently generated information appears in the browser. During a session with PowerPlay Web Explorer, generated pages are treated as individual requests. The processing of each request is randomly routed to an available query processor. When the maximum number of open processes reaches its limit, requests will start to queue up.This is an indication that requests are taking longer to complete and you may have to consider adding available processes, possibly with mirror references. The requests sent to your servers probably differ substantially in complexity. The cube dimension structure, the report format, ranking, and the limit on the number of rows and columns returned are just some of the factors that affect processing time. You may want to determine the average time it takes to handle each request. The sec/Hit column gives you an average reading for the last minute. If you want to determine the average processing time for your site, you can enable auditing (p. 72) and compute the average from the records in the ppes_audit.log file. 32 Cognos PowerPlay (R)
Monitor Windows Connections Chapter 3: Control Processes For a connection from a Windows client application to a query processor, you can monitor the following from PowerPlay Enterprise - Server Administration. Column Delay (s) Connections Description The number of seconds that requests for the cube must wait for processing The number of Windows connections For a Windows request, the server engine generates cube results for the PowerPlay for Windows or PowerPlay for Excel clients. During a session with a Windows client, sockets communication is established and maintained with a single query process, resulting in minimal network transactions. As soon as a Windows connection is established with the client application, PowerPlay Enterprise Server assigns a query processor. That means that all requests from the same IP address are handled by a single process that you can monitor in PowerPlay Enterprise - Server Administration. For example, if the delay becomes too long, you can respond by • increasing the number of processes for the cube, thereby sharing the load. • adding another cube (pointing to the same .mdc file) so that Web and Windows requests are each allocated a dedicated process. • adding mirror references Define the Maximum Number of Processes When a cube or report is busy processing requests, it starts more processes for new requests, up to the number defined as the maximum. When the maximum is reached, the server does one of the following: • queues new requests until a processor becomes available • queues new requests up to the limit specified by the Local Process Threshold setting, and forwards requests to a mirror reference if the number in the queue exceeds this threshold. If Local Process Threshold is set to 0, requests are never queued. The maximum number of processes to define for a cube or report is a function of your peak time requirements, the size of the server, and the number of users, cubes, reports, and other applications running on the server. Also, because each process uses memory for its cache, you conserve memory if the maximum number of processes you define doesn't exceed the number of processes required to meet your peak requirements. If several agents run automatically when a cube is updated, the server can be overloaded with report requests, and you may need to re-tune the server. You may want to add more processes for a cube that is experiencing less than optimal throughput by increasing the Maximum Processes setting. If a server has available resources, adding processes provides better throughput. If it is running at or near 100% capacity, however, adding processes just makes all the requests take longer. Therefore, you should only add more processes under either of the following conditions: • the server has available resources • the server has no available resources, but the average request time is sufficiently fast that an increase in processing time would still meet your users’ expectations Steps 1. In PowerPlay Enterprise - Server Administration, select a cube or report. Enterprise Server Guide 33
- Page 1 and 2: COGNOS (R) Business Intelligence Se
- Page 3 and 4: Table of Contents Introduction 7 Ch
- Page 5 and 6: Chapter 6: Audit Server Activity 71
- Page 7 and 8: Introduction What Is in This Docume
- Page 9 and 10: Chapter 1: Enterprise Reporting Pow
- Page 11 and 12: Chapter 1: Enterprise Reporting •
- Page 13 and 14: Chapter 1: Enterprise Reporting Ser
- Page 15 and 16: Chapter 2: Configure Servers This c
- Page 17 and 18: Chapter 2: Configure Servers Daemon
- Page 19 and 20: Chapter 2: Configure Servers 2. Fro
- Page 21 and 22: Chapter 2: Configure Servers Securi
- Page 23 and 24: Chapter 2: Configure Servers Perfor
- Page 25 and 26: Disable Saving of Cognos Sub-Cubes
- Page 27 and 28: Chapter 3: Control Processes This c
- Page 29 and 30: Chapter 3: Control Processes In a m
- Page 31: Chapter 3: Control Processes Exampl
- Page 35 and 36: Chapter 3: Control Processes When y
- Page 37 and 38: Chapter 4: Deploy Cubes and Reports
- Page 39 and 40: Chapter 4: Deploy Cubes and Reports
- Page 41 and 42: Add a Cube or Report Chapter 4: Dep
- Page 43 and 44: Chapter 4: Deploy Cubes and Reports
- Page 45 and 46: Add Dimension Line Information to a
- Page 47 and 48: Chapter 4: Deploy Cubes and Reports
- Page 49 and 50: Chapter 4: Deploy Cubes and Reports
- Page 51 and 52: Chapter 4: Deploy Cubes and Reports
- Page 53 and 54: Chapter 4: Deploy Cubes and Reports
- Page 55 and 56: Chapter 4: Deploy Cubes and Reports
- Page 57 and 58: Chapter 4: Deploy Cubes and Reports
- Page 59 and 60: Chapter 4: Deploy Cubes and Reports
- Page 61 and 62: Chapter 5: Provide Drill-through Ac
- Page 63 and 64: Chapter 5: Provide Drill-through Ac
- Page 65 and 66: Chapter 5: Provide Drill-through Ac
- Page 67 and 68: Chapter 5: Provide Drill-through Ac
- Page 69 and 70: Chapter 5: Provide Drill-through Ac
- Page 71 and 72: Chapter 6: Audit Server Activity Us
- Page 73 and 74: Chapter 6: Audit Server Activity 2.
- Page 75 and 76: Chapter 6: Audit Server Activity Th
- Page 77 and 78: Chapter 6: Audit Server Activity Co
- Page 79 and 80: Level Usage Table Chapter 6: Audit
- Page 81 and 82: Appendix A: Context Help This secti
Chapter 3: Control Processes<br />
PowerPlay Enterprise - Server Administration<br />
Use PowerPlay Enterprise - Server Administration to check the properties and monitor the status<br />
of each cube and report. PowerPlay client applications can only explore a cube or run a report<br />
when all of the following conditions are met:<br />
• The cube or report has been added to a PowerPlay server, or is a mirror reference on a<br />
PowerPlay server.<br />
• The cube, report, and its parent objects are enabled ( icon).<br />
• The PowerPlay server from which the cube is available is started and enabled.<br />
• Web ( icon) or Windows ( icon) access privileges have been correctly assigned.<br />
• Your preferred Web publishing method has been enabled and configured, to let users know<br />
that the data is available. You can also send users a direct URL to cubes and reports.<br />
• Any required network access rights and other forms of security access, such as Access<br />
Manager user classes, have been assigned.<br />
Use the Monitor tab to monitor the number of open processes for a cube or report (or all the<br />
cubes and reports in a folder), and the maximum number of processes available, as specified in the<br />
Cube or Report Properties dialog box. For example 2/5 means that there are currently two<br />
processes open out of five available processes.<br />
Other events you can monitor depend on whether the connection is for Web or Windows (or<br />
both).<br />
Monitor Web Connections<br />
For a connection from the Web to a query or report processor, you can monitor the following<br />
from PowerPlay Enterprise - Server Administration.<br />
Column<br />
Queue<br />
sec/Hit<br />
Hits/min<br />
Description<br />
The number of requests in the queue that are waiting to be processed<br />
The average time to process requests received in the last minute<br />
The number of PowerPlay Web requests (hits) received in the last minute<br />
For a Web connection, the server engine generates pages in HTML format. It generates a new page<br />
whenever data is requested by the user from the Web browser, for example, when a user opens a<br />
cube, drills down on a category, or changes the measure. Only the most recently generated<br />
information appears in the browser.<br />
During a session with PowerPlay Web Explorer, generated pages are treated as individual requests.<br />
The processing of each request is randomly routed to an available query processor. When the<br />
maximum number of open processes reaches its limit, requests will start to queue up.This is an<br />
indication that requests are taking longer to complete and you may have to consider adding<br />
available processes, possibly with mirror references.<br />
The requests sent to your servers probably differ substantially in complexity. The cube dimension<br />
structure, the report format, ranking, and the limit on the number of rows and columns returned<br />
are just some of the factors that affect processing time. You may want to determine the average<br />
time it takes to handle each request. The sec/Hit column gives you an average reading for the last<br />
minute. If you want to determine the average processing time for your site, you can enable<br />
auditing (p. 72) and compute the average from the records in the ppes_audit.log file.<br />
32 Cognos PowerPlay (R)
Change language