Access Manager Server
This chapter describes how to monitor an ApplicationXtender File Access Manager Server using ApplicationXtender Administrator.
Appendix A, Using Audit Trails
This appendix describes how to configure the Audit Trail feature, which allows you to track user activities.
Accessing Utilities for AppXtender Server Monitors
This chapter describes how to access ApplicationXtender Administrator and ApplicationXtender Web Access .NET Administrator:
• Introduction to Utilities for Monitoring Servers, page 11
• Starting ApplicationXtender Administrator, page 11
• Accessing the ApplicationXtender Web Access .NET Administrator, page 13
Introduction to Utilities for Monitoring Servers
A variety of utilities, such as ApplicationXtender Administrator (AppXtender Admin) and Windows® Management Instrumentation (WMI), can be used to monitor AppXtender Servers.
(WMI is a component of the Microsoft® Windows® operating system.) If you are using AppXtender Web.NET, you can also use the AppXtender Web Administrator to monitor AppXtender servers.
Additional utilities are available for monitoring the AppXtender Web Server and AppXtender Index Server. Refer toChapter 2, Monitoring the ApplicationXtender Web Access ServerandChapter 4, Monitoring the ApplicationXtender Index Server, respectively.
Starting ApplicationXtender Administrator
The first time you start ApplicationXtender Administrator (AppXtender Admin), some configuration is required. For details, refer to the “Starting AppXtender Admin the First Time” section of the ApplicationXtender Core Components Administrator’s Guide. Subsequently, starting AppXtender Admin requires fewer steps.
To start AppXtender Admin:
1. From the Windows Start menu, select Programs> ApplicationXtender Desktop > AppXtender Admin. A login dialog box appears.
2. In the User Name text box, type an administrative user name. For details, seeInformation about Logging into AppXtender Admin, page 12.
3. In the Password text box, type the password for the user name you entered.
4. Click Login. AppXtender Admin appears. For instructions on viewing or unregistering components within AppXtender Admin, seeMonitoring Components, page 12.
Information about Logging into AppXtender Admin
When you log into AppXtender Admin, you are logging into all of the data sources in AppXtender Admin simultaneously. If all of the data sources in AppXtender Admin are using either the CM security provider or the Windows security provider, the user account that you use to log into AppXtender Admin must meet the following criteria:
• It must exist on all data sources.
• It must have the same password on all data sources.
• It must have the AppXtender Admin user privilege on each data source. (This criterion does not apply to SYSOP.)
However, if more than one security provider is being used in AppXtender Admin (for example, if one data source is using a directory service security provider and the rest are using the CM security provider), only SYSOP may log in to AppXtender Admin. In this case, SYSOP must have the same password on all data sources.
For more details, refer to the Information about Logging into AppXtender section of the ApplicationXtender Core Components Administrator’s Guide.
Monitoring Components
You can use AppXtender Admin to verify that ApplicationXtender content management components have been correctly registered for the data group being managed through that AppXtender Admin installation. You can also monitor performance on the servers through AppXtender Admin. For more information, see the following sections:
• Viewing Registered Components, page 12
• Unregistering a Registered Component, page 13
• Monitoring AppXtender Web Server Using AppXtender Admin, page 17
• Monitoring AppXtender Rendering Server Using AppXtender Admin, page 25
• Monitoring AppXtender Index Server Using AppXtender Admin, page 43
• Monitoring AppXtender Reports Mgmt Server Using AppXtender Admin, page 47
• Monitoring AppXtender File Access Manager Server Using AppXtender Admin, page 51
Viewing Registered Components
You can view a list of registered components and view activity for each component.
1. In the AppXtender Admin tree, expand the Monitor node and then select Registered Components.
2. A list of components currently registered with this data source group appears in the right pane.
3. To refresh the list of components to reflect newly registered components, select Refresh (at the bottom of the right pane).
4. To view current activity on a component, select the component in the list. Any activity detail appears in the lower half of the right pane.
Unregistering a Registered Component
If you unregister a registered component, that component is no longer used by the data source group, even if it is still installed and running. To re-register components that have been unregistered, you need to run the Component Setup Wizard for that component again on the computer where the component is installed.
Note: For more information on running Component Setup Wizard for a component, refer to the installation information for that component in the appropriate guide, such as the ApplicationXtender Web Access Administrator’s Guide.
To unregister a registered component:
1. In the AppXtender Admin tree, expand the Monitor node and then select Registered Components.
2. Select the component in the list and select the Unregister button at the bottom of the pane. A message appears asking you to confirm that you want to unregister the component.
3. Select Yes to remove the component from the data source group by unregistering it; select No to cancel the request without unregistering the component.
Accessing the ApplicationXtender Web Access .NET Administrator
You can access administrative functions through the AppXtender Web.NET client browser interface if you have administrative permissions.
To access the AppXtender Web.NET Administrator through a browser:
1. Enter the website address for AppXtender Web.NET in your browser Address text box. The format for the website URL is as follows:
http://<Server>/<alias>/login.aspx
• The placeholder <Server> represents the IP address or domain of the IIS server.
• The placeholder <alias> represents the AppXtender Web.NET server alias you specified when installing AppXtender Web.NET. By default the alias is AppXtender.
Note: If you do not know the name of the AppXtender Web.NET server, contact your AppXtender Web.NET administrator for assistance.
The Login page appears.
Figure 1. AppXtender Web.NET Login Page
2. To use a data source other than the default data source, on the AppXtender Web.NET Login dialog box, select the desired data source from the Data Source drop-down list. The selected data source is considered the active data source for the session.
All of the data sources available to you appear in the Data Source drop-down list. If you choose Default, you are logged into either the data source that your AppXtender Web.NET administrator set as default or the data source that you set as default in a previous session.
3. Type your ApplicationXtender login user name and password in the corresponding text boxes.
4. If the Request Full Text Search Support check box is not checked, select the box by clicking it.
A check mark appears in the box.
If you do not have full text privileges, a message indicating this will appear as you log in.
Also, if the maximum number of full-text licenses has been exceeded, a warning message will appear during login. In both cases, the Full-Text Query Criteria section will not appear on the search criteria page.
5. Click Login. The ApplicationXtender Web Access Applications window opens.
6. Select Edit> Administration. The ApplicationXtender Web Access .NET Administrator window opens.
AppXtender servers, see the following sections:
• Monitoring AppXtender Web.NET Server Using AppXtender Web.NET Administrator, page 20
• Monitoring AppXtender Rendering Server Using AppXtender Web.NET Administrator, page 27
• Monitoring AppXtender Index Server Using AppXtender Web.NET Administrator, page 44
Monitoring the ApplicationXtender Web Access Server
This chapter describes how to monitor ApplicationXtender Web Access (AppXtender Web) using various utilities:
• Monitoring AppXtender Web Server Using AppXtender Admin, page 17
• Monitoring AppXtender Web.NET Server Using AppXtender Web.NET Administrator, page 20
• Monitoring AppXtender Web Server Using Audit Trail, page 23
Monitoring AppXtender Web Server Using AppXtender Admin
You can use AppXtender Admin to view information related to the operation of an AppXtender Web server that is stored in the WMI repository on the AppXtender Web server.
To monitor current activity on the AppXtender Web Server:
1. Start AppXtender Admin. For instructions, seeStarting ApplicationXtender Administrator, page 11.
2. In the AppXtender Admin tree, expand the Monitor node and then select AppXtender Web.
3. To select the AppXtender Web Server to monitor, choose the name of the server from the Select component list. (To refresh the list of components to reflect newly registered components, select Refresh.)
Status entries appear for the items listed in the following table.
Table 1. ApplicationXtender Web Access Server Status Entries
Entry Description
Anonymous Requests Number of requests utilizing anonymous authentication
Anonymous Requests/Sec Number of requests per second utilizing anonymous authentication
Entry Description
Cache API Entries Total number of entries within the cache added by the user
Cache API Hit Ratio Ratio of hits called from user code Cache API Hit Ratio Base Cache API Hit Ratio Base
Cache API Hits Number of hits from user code
Cache API Misses Number of cache misses called from user code Cache API Turnover Rate Number of additions and removals to the API
cache per second
Cache Total Entries Total number of entries within the cache (both internal and user added)
Cache Total Hit Ratio Ratio of hits from all cache calls Cache Total Hit Ratio Base Cache Total Hit Ratio Base
Cache Total Hits Total number of hits from the cache Cache Total Misses Total number of cache misses
Cache Total Turnover Rate Number of additions to and removals from the total cache per second
Compilations Total Number of .asax, .ascx, .ashx, .asmx, or .aspx source files dynamically compiled
Debugging Requests Number of debugging requests processed Errors During
Compilation
Number of errors that have occurred during compilation
Errors During Execution Number of errors that have occurred during the processing of a request
Errors During Preprocessing
Number of errors that have occurred during parsing and configuration
Errors Total Total number of errors that occurred Errors Total/Sec Rate of error occurrence
Errors Unhandled During Execution
Number of errors not handled by user code, but by the default error handler
Errors Unhandled During Execution/Sec
Rate of unhandled errors
Output Cache Entries Current number of entries in the output cache Output Cache Hit Ratio Ratio of hits to requests for output cacheable
requests Output Cache Hit Ratio
Base
Output Cache Hit Ratio Base
Output Cache Hits Total number of output cacheable requests served from the output cache
Output Cache Misses Total number of output cacheable requests not served from the output cache
Output Cache Turnover Rate
Number of additions to and removals from the output cache per second
Pipeline Instance Count Number of active pipeline instances Request Bytes In Total The total size, in bytes, of all requests
Request Bytes Out Total The total size, in bytes, of responses sent to a client.
This does not include standard HTTP response headers.
Requests Executing The number of requests currently executing Requests Failed Total number of failed requests
Requests In Application Queue
The number of request in the application request queue
Requests Not Authorized The number of requests failed due to unauthorized access
Requests Not Found The number of requests for resources that were not found
Requests Succeeded The number of requests that executed successfully Requests Timed Out The number of requests that timed out
Requests Total The total number of requests since the application was started
Requests/Sec The number of requests executed per second Session SQL Server
connections total
The total number of connections to the SQL Server used by session state
Session State Server connections total
The total number of connections to the State Server used by session state
Sessions Abandoned The number of sessions that have been explicitly abandoned
Sessions Active The number of sessions currently active Sessions Timed Out The number of sessions timed out
Sessions Total Total number of sessions since the application was started
Transactions Aborted The number of transactions aborted Transactions Committed The number of transactions committed Transactions Pending The number of transactions in progress Transactions Total The total number of transactions since the
application was started
Transactions/Sec Transactions started per second
Monitoring AppXtender Web.NET Server Using AppXtender Web.NET Administrator
You can track the current AppXtender Web.NET Server status using the AppXtender Web.NET Administrator.
To monitor current activity on the AppXtender Web.NET Server:
1. Access the AppXtender Web.NET Administrator. For instructions, seeAccessing the ApplicationXtender Web Access .NET Administrator, page 13.
2. In the Admin window, select View> Monitor ApplicationXtender Web Access .NET. The ApplicationXtender Web Access .NET Monitor appears.
Figure 2. ApplicationXtender Web Access .NET Monitor
3. To select the AppXtender Web.NET Server to monitor, enter the name of the server in the Server Name text box.
4. To refresh the status entries to reflect new activity, select Refresh.
Status entries appear for the items listed in the following table.
Table 2. ApplicationXtender Web Access .NET Server Status Entries
Entry Description
Anonymous Requests Number of requests using anonymous authentication Anonymous Requests/Sec Number of requests per second using anonymous
authentication
Cache Total Entries Total number of entries within the cache (both internal and user added)
Cache Total Entries Cache Total Entries
Cache Total Hits Total number of hits from the cache Cache Total Misses Total number of cache misses Cache Total Hit Ratio Ratio of hits from all cache calls Cache Total Hit Ratio Base Cache Total Hit Ratio Base
Cache API Entries Total number of entries within the cache added by the user
Cache API Turnover Rate Number of additions and removals to the API cache per second
Cache API Hits Number of hits from user code
Cache API Misses Number of cache misses called from user code Cache API Hit Ratio Ratio of hits called from user code
Cache API Hit Ratio Base Cache API Hit Ratio Base
Output Cache Entries Current number of entries in the output cache Output Cache Turnover
Rate
Number of additions to and removals from the output cache per second
Output Cache Hits Total number of output cacheable requests served from the output cache
Output Cache Misses Total number of output cacheable requests not served from the output cache
Output Cache Hit Ratio Ratio of hits to requests for output cacheable requests Output Cache Hit Ratio
Base
The base used to determine the output cache hit ratio
Compilations Total Number of .asax, .ascx, .ashx, .asmx, or .aspx source files dynamically compiled
Debugging Requests Number of debugging requests processed Errors During
Preprocessing
Number of errors that have occurred during parsing and configuration
Errors During Compilation
Number of errors that have occurred during compilation
Errors During Execution Number of errors that have occurred during the processing of a request
Errors Unhandled During Execution
Number of errors not handled by user code, but by the default error handler
Errors Unhandled During Execution/Sec
Rate of unhandled errors
Errors Total Total number of errors that occurred
Entry Description
Errors Total/Sec Rate of error occurrence
Pipeline Instance Count Number of active pipeline instances Request Bytes In Total The total size, in bytes, of all requests
Request Bytes Out Total The total size, in bytes, of responses sent to a client.
This does not include standard HTTP response headers.
Requests Executing The number of requests currently executing Requests Failed Total number of failed requests
Requests In Application Queue
The number of requests in the application request queue
Requests Not Authorized The number of requests failed due to unauthorized access
Requests Not Found The number of requests for resources that were not found
Requests Succeeded The number of requests that executed successfully Requests Timed Out The number of requests that timed out
Requests Total The total number of requests since the application was started
Requests/Sec The number of requests executed per second
Cache Total Turnover Rate Number of additions to and removals from the total cache per second
Output Cache Entries Current number of entries in the output cache Output Cache Hit Ratio Ratio of hits to requests for output cacheable requests Output Cache Hit Ratio
Base
Output Cache Hit Ratio Base
Output Cache Hits Total number of output cacheable requests served from the output cache
Output Cache Misses Total number of output cacheable requests not served from the output cache
Output Cache Turnover Rate
Number of additions to and removals from the output cache per second
Session SQL Server connections total
The total number of connections to the SQL Server used by session state
Session State Server connections total
The total number of connections to the State Server used by session state
Sessions Abandoned The number of sessions that have been explicitly abandoned
Sessions Active The number of sessions currently active Sessions Timed Out The number of sessions timed out
Sessions Total Total number of sessions since the application was started
Transactions Aborted The number of transactions aborted Transactions Committed The number of transactions committed Transactions Pending The number of transactions in progress
Transactions Total The total number of transactions since the application was started
Transactions/Sec Transactions started per second
Monitoring AppXtender Web Server Using Audit Trail
You can track AppXtender Web events using AppXtender Audit Trail. AppXtender Audit Trail allows you to track user activities such as user login/logout, viewing and deletion of documents and pages, addition and deletion of annotations, batch indexing, printing, and queries.
The events to be audited are configured through AppXtender Application Generator (AppXtender AppGen), and can be enabled or disabled for an application, user, or group. When user activity triggers an audit event, details of the event are recorded in the audit trail. Each line in the audit trail represents a single audit event. Depending on the configuration, the audit trail can contain status information for each application and global audit events.
Note: AppXtender Desktop and Web audit trail logs cannot be separated. If Audit Trail is enabled and AppXtender Web is installed, both AppXtender Web and AppXtender Desktop events will be tracked.
Caution: When using AppXtender Audit Trail for AppXtender Web tracking purposes, you should never select the Log to File check box in AppXtender AppGen. Instead, you should only enable the Log to Database option to log AppXtender Web activity.
After audit settings are configured, you can choose to store audit trail events in the AppXtender audit trail database table (AE_AUDIT) or in a log file (AxAudit.log), or both. ApplicationXtender Audit Trail encodes the time column tsstamp in the AE_AUDIT table in Greenwich Mean Time (GMT) format. This allows the audit table entries to maintain consistency when workstations are located in multiple time zones. You can calculate your local time by applying your time zone offset. For example, Eastern Standard Time (EST) is -5 hours.
Note: If you have configured Audit Trail to log tracking information to the database table, be aware
Note: If you have configured Audit Trail to log tracking information to the database table, be aware