|
Oracle® Application Server Portal Configuration Guide
10g (9.0.4) Part No. B13675-01 |
|
|
|
|
Oracle® Application Server Portal Configuration Guide
10g (9.0.4) Part No. B13675-01 |
|
|
|
|
This chapter provides information about the monitoring and administration tools that are available, and how to use them to successfully monitor and administer OracleAS Portal.
You can monitor and administer OracleAS Portal through the Oracle Enterprise Manager 10g Grid Control Console, or the Oracle Enterprise Manager 10g Application Server Control Console. Additionally, you can view OracleAS Portal Analytics to monitor OracleAS Portal performance and analyze OracleAS Portal access characteristics.
|
See Also: For additional OracleAS Portal monitoring and administration information, see the Portal Administrator Zone on Portal Center, athttp://portalcenter.oracle.com.
|
This chapter contains the following sections:
Using the Oracle Enterprise Manager 10g Grid Control Console
Using Application Server Control Console to Monitor and Administer Portal
The Oracle Enterprise Manager 10g Grid Control Console is a full enterprise management framework consisting of the Oracle Management Service, Oracle Management Agent, and Oracle Management Repository. In the Grid Control Console, you can:
Manage targets in your environment
Monitor historical trends
Configure alerts
View diagnostics
Monitor application performance
Manage enterprise configuration
|
Note: For more information, see Oracle Enterprise Manager Grid Control Installation and Basic Configuration. |
Oracle Enterprise Manager 10g uses a Web-based architecture that is robust, reliable, globally scalable, and easy to deploy and operate within today’s Internet-enabled environments. This architecture (shown in Figure 7-1) uses four integrated software components, three of which (Oracle Management Service, Oracle Management Repository, and Oracle Management Agent) run behind the scenes, gathering, organizing, and routing management data. The Browser-based console provides a Web-based user interface so you can manage the information from a standard Web browser.
Figure 7-1 Overview of Oracle Enterprise Manager 10g Grid Control Console Components
The Oracle Enterprise Manager 10g Grid Control Console ships with Oracle Application Server, but must be installed separately. In the case of OracleAS Portal, the Grid Control Console can be used for monitoring, and tracking historical trends, but not for configuration.
Typically you can access the Grid Control Console by navigating to the following URL: http://<hostname>:7777/em/. You must then log in using a valid Grid Control Console username/password combination with privileges to access the OracleAS Portal targets you intend to monitor.
After logging on successfully, the Oracle Enterprise Manager 10g Grid Control Console home page is displayed.
To drill down to the application server level, click the Targets tab, and then the Application Servers sub-tab. Select the application server that you want to monitor from the list of available application servers. The home page for the selected application server is then displayed.
From the application server home page, you can click any of the components listed to get detailed information. For example, if you click the Portal component, if listed, the OracleAS Portal target page is displayed as shown in Figure 7-2.
Figure 7-2 Grid Control Console - Portal Target Page
On the Portal target page, in addition to availability information, you can monitor the average home page download time on a chart.
The Grid Control Console helps you in:
In the Grid Control Console, you can look at various OracleAS Portal metrics collected over a specific time period. The range of metrics which are collected are configured (by default) when the Management Agent is installed.
Figure 7-3 shows a list of the kinds of OracleAS Portal metrics you can monitor.
Figure 7-3 Grid Control Console - OracleAS Portal Metrics
You can use the OracleAS Portal metrics to monitor historical trends. For example, if you want to see how your site has performed over the previous 31 days, follow these steps:
Navigate to the Grid Control Console home page.
Click the Targets tab, and then the Application Servers tab.
Choose the application server of interest.
From the Components table, select the Portal target.
Click the All Metrics link.
Expand the Portal Homepage Metric node.
Click the Homepage Download (msec) metric.
A table lists all the collected data for this metric over the last 24 hours, by default. Figure 7-4 shows an example of the information displayed.
Figure 7-4 Grid Control Console - OracleAS Portal Metric Information
To change the duration to 31 days, select Last 31 days from the View Data drop-down list (top right hand corner).
|
Note: For more information, see Oracle Enterprise Manager Concepts manual. |
You can compare the details of an OracleAS Portal metric (the currently selected metric), with the details of the same metric on a different OracleAS Portal target.
For example, you can compare the Homepage Download (ms) metric on portal1 with the Homepage Download (ms) metric on portal2 and portal3. The comparisons are plotted on a Metric Value History chart.
To compare metrics:
Navigate to the OracleAS Portal metrics page, as shown in Figure 7-3.
Expand the metric node of interest and click the relevant metric link.
From the View Data drop-down list (top right hand corner), choose a suitable time period for analyzing this metric.
Click the Compare Targets link in the Related Links section.
Choose the OracleAS Portal targets that you want to compare, move them to the Selected Targets list box and then click OK.
The comparisons are plotted on the Metric Value History chart.
In the Grid Control Console, you can set up notification alerts to report that certain metrics exceed pre-set thresholds.
Check that the Oracle Enterprise Manager 10g administrator has setup at least one Notification Method for an Outgoing Mail Server, a Script (Operating System Command or PL/SQL) or an SNMP Trap:
Click the Setup link (top right hand corner).
Click Notification Methods.
Once a notification method exists, setup a Notification Rule:
Click the Preferences link (top right hand corner).
Click the Notification Rules link.
From this page you can create a notification rule and choose targets and conditions for which you want to receive notifications in Oracle Enterprise Manager 10g.
|
Note: For more information, see Oracle Enterprise Manager Concepts manual. |
In the Grid Control Console, you can define and adjust the thresholds for OracleAS Portal metrics. Thresholds are boundary values against which monitored metric values are compared. You can specify a warning threshold so that when a monitored metric value crosses that threshold, a warning alert is generated. Alerts can notify you of impending problems which you can address in a timely manner.
Editing metric thresholds is useful because you can add or change the thresholds to fit the monitoring needs of your organization. When defining a threshold, choose a value that won't generate too many unnecessary alerts.
To edit OracleAS Portal related metrics, click the Manage Metrics link at the bottom of any OracleAS Portal target page, as shown in Figure 7-2. The metrics listed on the Manage Metrics page are either default metrics provided by Oracle, or metrics with thresholds you can change. For an example, see Figure 7-5.
|
Note: For more information, see the Oracle Enterprise Manager Concepts manual. |
Figure 7-5 Grid Control Console - OracleAS Portal Edit Metric Thresholds
A list of the most recent alerts are displayed on the OracleAS Portal target page, in the section called Alerts and Host Alerts (see Figure 7-2).
When an alert is generated to notify you of availability or performance problems, you can check the Grid Control Console for more information about the metric that triggered the alert. This includes information on the metric’s historical values that might show trends over the past week or month.
In the Grid Control Console, you can use the Web Applications feature for Application Performance Monitoring of OracleAS Portal sites. You can monitor the end-user response time, or the performance of representative transactions. You can group multiple targets into a single Web Application group, which corresponds to the topography of an OracleAS Portal application. For example, you could add the Database and OracleAS Single Sign-On targets used by your OracleAS Portal to the same Web Application group.
End-User Response Time monitoring - All URLs based on the application homepage (specified in the Web Application properties) are monitored. URLs of particular importance can be identified in a URL Watchlist.
Representative Transaction monitoring - Recorded application activity (transactions) is played back at regular intervals through client robots (Beacons). The availability of the application is defined as the availability of a selected subset of representative transactions, replayed through selected Beacons.
|
Note: For more information, see the Oracle Enterprise Manager Concepts manual. |
The Application Server Control Console is included when you install Oracle Application Server. From OracleAS Portal’s perspective, consider this to be the administration console for the Oracle Application Server. The Application Server Control Console enables you to perform the following administration and configuration operations:
Enable and disable components
Administer clusters
Start and stop services
View logs and ports
Perform real-time monitoring
Modify the Infrastructure services used by an Oracle Application Server middle-tier.
This section contains information about:
You can access the Application Server Control Console by entering the following URL in your Web browser:
http://<hostname>:<port>
For example, http://mgmthost.company.com:1810. The port is typically on 1810, however the possible port range for the Application Server Control Console varies upwards in increments of 1.
If there is more than one standalone application server instance, your start page for the Application Server Control Console is the Oracle Application Server Farm home page. Clicking an instance, takes you to the Oracle Application Server instance home page. This page contains a table of System Components. From this table you can display the home page for each component of the application server for monitoring and administrative purposes.
If OracleAS Portal is configured, Portal:<portal schema name> appears in this table. The default portal schema name is portal.
If Portal:portal is not listed in the System Components table, it means it is not yet configured. The Configure Component button appears above the System Components table if you have installed, but not configured, some Oracle Application Server components.
|
Note: Only components that have the check box selected can be started or stopped. |
To configure OracleAS Portal perform these steps:
On the Oracle Application Server home page, click the Configure Component button.
Enter the administration password for the Oracle Application Server instance in the Password field.
Click Finish.
|
Note: By default, an OracleAS Portal middle-tier is made up of one portal instance. Both the DAD name and the OracleAS Metadata Repository schema name for this instance are portal. You cannot use the Configure Component button to configure additional OracleAS Portal instances for a given middle-tier if Portal:portal is already listed in the System Components table. |
To monitor and administer OracleAS Portal, click Portal:<portal schema name> in the list of system components on the Oracle Application Server instance home page. The default portal schema name is portal. Note that OC4J:Portal is the container for portal servlets, and not an actual portal servlet to monitor.
The main page for monitoring OracleAS Portal that is displayed, is shown in Figure 7-6.
You can also access this page directly from OracleAS Portal. Click the Administer tab on the Portal Builder page and then click Portal Service Monitoring (located on the Portal sub-tab).
|
Note: If any Oracle Enterprise Manager 10g Application Server Control Console details change, for example, the port or protocol, you must update the link provided by OracleAS Portal otherwise it will not work. For instructions, see Section 7.3.8, "Updating OracleAS Portal Link to Oracle Enterprise Manager 10g". |
Figure 7-6 Application Server Control Console - Main OracleAS Portal Monitoring Page
The main OracleAS Portal monitoring page, shown in Figure 7-6, contains various sections and links:
Use this section to establish the general status of an OracleAS Portal instance, that is, whether it is currently 'up' or 'down'.
You can also see the average number of page requests for each hour, as well as the current home page download speed. Furthermore, you can check if the monitoring services are up and running.
Use this section to view metrics relating to the OracleAS Metadata Repository. This is the repository containing the OracleAS Portal schema.
You can see if the database that contains the OracleAS Metadata Repository is up and running, the version number, name of the database, and the version number of the OracleAS Metadata Repository.
From the Application Server Control Console, you can specify the OracleAS Web Cache settings that OracleAS Portal should use. Setting the OracleAS Web Cache properties on this page will automatically result in the Portal Dependency Settings file located on this middle-tier being updated, and the ptlconfig script being executed. See Appendix A, " Using the Portal Dependency Settings File" for more details.
When you click the Portal Web Cache Settings link, under Administration, the Portal Web Cache Settings page shown in Figure 7-7 is displayed.
|
Note: Changing OracleAS Web Cache settings (for example, Listening Port) can change the OracleAS Portal URL. If you do this, mobile settings need to be updated. For more information, see Appendix C, "Using the cfgiasw Script to Configure Mobile Settings". |
Figure 7-7 Application Server Control Console - Oracle Application Server Web Cache Settings
In the Portal Web Cache Settings page, you can modify the settings detailed in Table 7-1:
Table 7-1 Portal Web Cache Settings
| Setting | Description |
|---|---|
| Host | The hostname that OracleAS Web Cache should use. For example, abc.company.com.
|
| Listening Port | The port on which OracleAS Web Cache listens. For example, 7778.
|
| Listening Port SSL Enabled | Indicates whether OracleAS Web Cache is SSL enabled. Valid values are 'Yes' and 'No'. |
| Administration Port | The OracleAS Web Cache administration port. For example, 4000.
|
| Invalidation Port | The OracleAS Web Cache invalidation port, to which invalidation messages are sent. For example, 4001.
|
| Invalidation Username | The username used for sending the invalidation messages. Either invalidator or administrator.
|
| Invalidation User Password | The invalidation password. The default is invalidator.
|
| Confirm Password | Repeat the password specified earlier. |
|
Note: When you set OracleAS Web Cache properties, Portal's perspective of these properties changes but the actual OracleAS Web Cache configuration properties do not change. You must make corresponding changes to the appropriate OracleAS Web Cache configuration pages. Refer to the Oracle Application Server Web Cache Administrator's Guide for more information about OracleAS Web Cache.Typically, the hostname and port number, by which OracleAS Portal is addressed, uses the OracleAS Web Cache hostname and port number. This is because, in a simple configuration, browser requests go directly to OracleAS Web Cache. However, in a configuration that has a load balancing router (LBR), or reverse proxy server front-ending OracleAS Web Cache, the hostname and port number defined on this page may need to reflect that of the LBR, or reverse proxy server. In this configuration, you want OracleAS Web Cache invalidation messages to be sent directly to the OracleAS Web Cache host, as opposed to the LBR, or reverse proxy server. In the scenario where your published hostname is different from the hostname used for OracleAS Web Cache invalidation, you cannot use the Portal Web Cache Settings page in the Oracle Enterprise Manager 10g Application Server Control Console, to establish these settings. Instead, you must use the OracleAS Portal Configuration Assistant (OPCA) in the MIDTIER mode with -type OHS, using the |
In the following example, the Portal Web Cache Settings page is used to configure OracleAS Portal to use OracleAS Web Cache on a different host:
Example 7-1 Example: Configuring OracleAS Portal to use OracleAS Web Cache on a Different Host
To configure OracleAS Portal to use OracleAS Web Cache on a different host from the one the OracleAS Portal middle-tier is installed on, you must follow these steps:
Access the Application Server Control Console on the middle-tier where OracleAS Portal is installed.
Select the portal instance you want to configure. Typically this is Portal:portal.
Select Portal Web Cache Settings.
Update the Host property with the new host name, along with any other property changes you want to add.
Click OK.
Lists the Oracle Application Server components used by OracleAS Portal and indicates their status. You can also drill down to find more information about individual Oracle Application Server components. These components are:
For performance reasons, less critical metric data, that is, non-response metric, are collected by the Application Server Control Console metric cache and may be slightly out of date. To display the most up to date metric data, click the Refresh link in the top left corner of a page.
Clicking the HTTP Server link takes you to the Oracle HTTP Server home page. This is the starting point for managing a single instance of Oracle HTTP Server. For example, you can restart the Oracle HTTP Server from here.
Clicking the mod_plsql Services link takes you to the mod_plsql Services home page shown in Figure 7-8. From here you can configure, as well as monitor, mod_plsql related settings and metrics.
In the Grid Control Console you can only monitor mod_plsql services, whereas the Application Server Control Console allows for actual configuration as well.
Figure 7-8 Application Server Control Console - mod_plsql Services Monitoring Page
The following sub-sections in this page help you monitor and configure mod_plsql services:
General
Indicates whether the mod_plsql module loaded into memory successfully. It also shows the number of requests for every hour, received by mod_plsql since the server was started.
HTTP Response Codes
Displays the HTTP response and error codes. For each response code, the number of requests and the percentage this number represents overall is shown.
Cache
Displays the Cache Settings, as shown in Figure 7-9. Here you can see the number of requests for cached content, including the percentage of cache hits and misses. In the case of a cache miss you can see if the miss was due to stale content, or new content being added. If you see a high percentage of misses, you can tune the cache.
To update the cache configuration settings on this page, click Configure.
Figure 7-9 Application Server Control Console - Cache Settings
DADs
Displays the status of existing DADs. A Database Access Descriptor (DAD) is a set of values that specify how an application connects to an Oracle database to fulfill an HTTP request. You can also create, edit, and delete DADs here. See also Section 4.5.3, "Configuring a Portal DAD".
Errors and Response Codes
Provides links to the HTTP error and SQL error pages. You can get the following details:
Breakdown of HTTP response codes that mod_plsql has returned.
Last ten SQL errors mod_plsql has encountered.
SQL errors that mod_plsql has encountered, grouped by type of error.
Clicking the Web Cache link takes you to the OracleAS Web Cache home page. Use this page to gather overall performance statistics for OracleAS Web Cache, including status, resource utilization, and cache efficiency. The following sections in this page enable you to monitor and configure Oracle Application Server Web Cache settings:
General - Displays the current status of OracleAS Web Cache.
Activity - Displays cache resource and performance information.
Performance - Enables you to monitor overall cache performance, monitor the status and performance of the origin servers, and view the most popular requests since the cache was started.
Administration - Provides access to the OracleAS Web Cache Manager URL (http://web_cache_hostname:admin_port/webcacheadmin).
Clicking the Parallel Page Engine Services link takes you to the Parallel Page Engine (PPE) monitoring page shown in Figure 7-10. From here you can get detailed PPE statistics, such as:
Portlet response codes
Page level caching
Status of the OC4J Portal container
PPE request queue statistics
|
See Also: For more information about the PPE, refer to Appendix D, " Configuring the Parallel Page Engine". |
Figure 7-10 Application Server Control Console - Parallel Page Engine Services Monitoring Page
Clicking the Providers link takes you to the Providers monitoring page shown in Figure 7-11. From here you can get an overview of the performance, status, and HTTP response codes (portlets only) of providers and portlets that are requested by the Parallel Page Engine (PPE) in the Application Server Control Console.
|
Note: For performance reasons, the Provider’s Up/Down value in the Component Status table (see Figure 7-6) is always set to 'Unknown'. |
Figure 7-11 Application Server Control Console - Providers Monitoring Page
On the Providers page, Web Providers are distinguished from Database Providers. You can click a provider to get details about individual portlets, owned by a provider.
Metrics you can monitor include:
Avg Time (seconds) - The average response time to request a portlet.
Max Time (seconds) - The maximum response time to request a portlet.
Requests - The number of requests serviced by this provider.
Cache Hits - The number of times the cache has been accessed.
Online - Indicates if a provider is currently online.
Performance - Indicates whether the providers are performing as expected.
Status - Indicates whether a specific provider is up or down.
Clicking the Syndication Services link takes you to the Oracle Application Server Syndication Services monitoring page. From this page you can manage Oracle Application Server Syndication Services, which automates the establishment of syndication relationships (offers and subscriptions), content transfers based on delivery rules (contracts), and results analysis (access logs).
The following administration options are available from this page:
Offer Management - View, select, create, and manage offers and associated offer contracts from content providers.
Content Providers - Register and manage content providers and view content provider connectors that provide the interface to external content repositories belonging to content providers.
Subscriptions - View and manage accepted offer agreements, subscription state, and purge expired and terminated subscriptions.
System Properties - Enable access logging, edit domain information, edit scheduler properties, and edit HTTP/S and SMTP transport properties.
Access Logs - View and manage user access records for all access to Oracle Application Server Syndication Services.
For more information, see Chapter 11, " Syndicating Content Into OracleAS Portal".
Clicking the Ultra Search link takes you to Oracle Ultra Search administration pages. From here you can configure Oracle Ultra Search. For more information, see Chapter 8, " Configuring the Search Features in OracleAS Portal ".
Lists the Oracle Application Server components used by OracleAS Portal that indicate severity status. Table 7-2 describes the severity status levels that are reported.
|
Note: Severity level threshold are set intargets.xml.
|
Contains the link Portal End User Default Homepage, which takes you to the home page of the OracleAS Portal being monitored.
To perform detailed diagnostics, using log files, click the Log link. In the Application Server Control Console, this link is located at the top and bottom of every Oracle Application Server component home page.
OracleAS Portal provides a link to the Oracle Enterprise Manager 10g Application Server Control Console that is monitoring and managing the portal. To access the Portal Service Monitoring link, click the Administer tab in OracleAS Portal and locate the Services portlet.
If any Oracle Enterprise Manager 10g Application Server Control Console details change, for example, the port or protocol, you must update the link provided by OracleAS Portal otherwise it will not work.
To do this, follow these steps:
Edit the file iasconfig.xml on the Portal middle-tier.
This is usually located in ORACLE_HOME/portal/conf. For details, see Appendix A, " Using the Portal Dependency Settings File".
Update the EMComponent element for your Portal instance, as required.
Run the following script to update the Oracle Application Server Metadata Repository with the new settings:
ORACLE_HOME/portal/conf/ptlconfig -dad <dad -em
Clear the OracleAS Web Cache cache to view the updated link in OracleAS Portal, that is, the Services portlet.
In the Services portlet, click Global Settings, the Cache tab and then select Clear The Entire Web Cache.
An Oracle Application Server 10g (9.0.4) middle-tier can use an Oracle9iAS Portal repository version 9.0.2. You must complete some additional steps after installation to enable Oracle Enterprise Manager 10g Application Server Control Console to monitor this version of Oracle9iAS Portal.
If you do not do this, Oracle9iAS Portal version information and Oracle9iAS Portal Metadata Repository information (database version and start time) is not accessible in Oracle Enterprise Manager 10g Application Server Control Console. Also, missing package errors (WWC_MONITORING) are displayed in the Oracle HTTP Server logs.
In SQL*Plus, connect as SYS.
Run the script cfgvr902.sql, located in the middle-tier Oracle home, under <upgrade_directory>/wwc/.
Use the <portal schema name> as an argument.
Note that this script only exists in the Oracle Application Server (9.0.4) middle-tier with which the Oracle9iAS Portal repository (9.0.2) is connected. The script will not exist in the Oracle home running the infrastructure.
For example, if the Oracle9iAS Portal repository (9.0.2) schema name is portal and the middle-tier is running from /homes/portalMid904/, enter:
/homes/portalMid904/portal/admin/plsql/wwc/cfgvr902.sql portal
If there are no errors, run the following grant when connected to the portal schema:
In SQL*Plus, connect as PORTAL.
Make the new WWC_MONITORING package accessible to the monitoring component, enter:
grant execute on WWC_MONITORING to PUBLIC;
OracleAS Portal analytics includes:
Performance reports
Activity reports
A set of OracleAS Portal Activity reports are available that execute against data collected by the performance logging service of mod_plsql. For a full description of how to implement this logging service, refer to Section 9.5, "Generating Performance Reports". These reports return information such as:
Peak login time each day
Number of logins the portal receives each day
Portlet execution time
Slowest portlet
Total hits received by the portal each day
Most/least popular portlets
Frequency of pages or portlets viewed by users
Number of unique users login each day
Portlets that were accessed
Number of hits received by every page each day
Number of hits received by every portlet each day
Breakdown of information by IP address or host name
You can find additional information in the technical note Object Access Reporting from the Performance Logs in OracleAS Portal, on Portal Center, http://portalcenter.oracle.com. Click the Search icon in the upper right corner of any Portal Center page.
You can log objects and actions in OracleAS Portal and generate reports for analyzing the data. For example, you can add an entry into the Activity Log tables every time OracleAS Portal users create, edit or delete a particular page.
Any authorized user can view the OracleAS Portal Log Registry records. However, only the portal administrator can set up what information is to be logged. See Section 7.4.2.2, "Choosing Which Events are Logged" for more information.
|
Note: With the introduction of OracleAS Web Cache into the OracleAS Portal architecture, some of the actions logged in OracleAS Portal Activity Log tables have become inaccurate. These actions include View, Execute (for Reports, Charts, and Hierarchies), and Show. The Activity Log tables and views still remain in the OracleAS Metadata Repository, as all other actions logged are still accurate |
Table 7-3 lists the events that can be logged for different portal objects.
Table 7-3 Logged Events for OracleAS Portal Objects
| Portal Object | Event |
|---|---|
| Pages | Create, Edit, Delete, Customize |
| Items | Create, Edit, Delete, Move, Check Out, Check In |
| Application Components | Create, Edit, Delete, Execute (except for Reports, Charts, and Hierarchies), Copy, Export, Rename, Generate, Access Control, Manage, Insert, Update, Save |
| Portlets | Add to Page, Delete from Page |
| Portlet Instances | Hide, Customize |
| Searches | Search |
|
Note: User and Group actions such as Create, Edit, and Delete are logged by Oracle Internet Directory and may be viewed from Oracle Directory Manager, if logging is enabled. For more information, refer to the Oracle Internet Directory Administrator's Guide. |
You can choose which events are logged in the Log Registry records.
In the Services portlet, click Log Registry Administration.
|
Note: By default, the Services portlet is on the Portal sub-tab of the Administer tab on the Portal Builder page. |
The Administer Log Registry page is displayed as shown in Figure 7-12.
Figure 7-12 Administer Log Registry Page
Figure 7-12 shows two logging requests. The first creates an entry in the Activity Log every time a portlet is customized. The second creates an entry every time a page is created. If you want to log all possible requests, choose % for each field.
Do one of the following:
Click Add New Log Registry Record to create a new Log Registry record and specify logging criteria.
Or,
Edit logging criteria for an existing Log Registry record. To do this, perform the following steps:
Click the Edit icon to edit logging criteria for an existing Log Registry record (under Edit/Delete Log Registry Record).
The Edit Log Registry Record page is displayed as shown in Figure 7-13.
Figure 7-13 Edit Log Registry Record page
Choose the objects that you wish to log, from the Sub Domain list. Valid objects are listed in Table 7-3.
Choose which actions (or events) you want to log, from the Action list. Valid actions are listed in Table 7-3.
Specify other logging criteria as required.
Click OK.
Several Activity Log views are available (named wwlog_*). These views exist in the schema in which OracleAS Portal is installed. These views are granted to public; however, the logs are secure according to the object's security. For example, information about pages is available only on pages for which the user has access privileges.
Table 7-4 lists all the Activity Log views and their descriptions. You can create simple OracleAS Portal DB Provider reports and charts based on these views if required.
Table 7-4 Activity Log Views
| Log View | Description |
|---|---|
| wwlog_portal_admin_logs | All logs (only has records if the user is the portal administrator). |
| wwlog_user_logs | All logs created by current user. |
| wwlog_all_portlet_logs | Portlet instances on pages that the current user can view. |
| wwlog_all_document_logs | Documents that the current user can view. |
| wwlog_all_search_logs | Searches that the current user can view. |
| wwlog_all_item_logs | Items that the current user can view. |
| wwlog_all_component_logs | Components that the current user can view. |
| wwlog_all_object_logs | Summary view, which encompasses all the preceding views. |
You can also access information in the Activity Log views from outside of the OracleAS Portal browser-based interface, that is, using SQL*Plus, OracleAS Reports Services, and so on. To do this, you must first set the portal security context for your database session using the wwctx_api.set_context API:
wwctx_api.set_context ( p_user_name => 'portal_username', p_password => 'portal_pw' );
In Application Server Control Console, the Application Server Ports page shows a list of all the ports currently in use by the components of a particular Oracle Application Server instance. This page is important when you are troubleshooting port conflicts among the various application server components.
Whenever possible, Application Server Control Console provides a link to the appropriate Oracle Enterprise Manager 10g configuration page where you can modify the port settings for the component.
To access the Application Server Ports page:
Access the Application Server Control Console. See Section 7.2.1, "Accessing the Application Server Control Console" for details.
If there is more than one standalone application server instance, your start page for the Application Server Control Console is the Oracle Application Server Farm home page.
Click an instance to take you to the Oracle Application Server instance home page.
Click the Ports link below the application server name to view the Application Server Ports page, as shown in Figure 7-14.
Figure 7-14 Oracle Application Server Ports Page
For information on managing ports, see the chapter "Managing Ports" in the Oracle Application Server 10g Administrator's Guide.
