Oracle® Application Server Portal Configuration Guide 10g (9.0.4) Part Number B10356-01 |
|
This chapter assumes that OracleAS Portal has been installed as part of the Oracle Application Server and addresses the basic tasks that the portal administrator can perform after installation is complete.
This chapter contains the following sections:
Basic OracleAS Portal configuration can be performed on the Administer tab available from OracleAS Portal. Additionally, there are other administrative tools available to configure OracleAS Portal, and its related components.
This section will introduce you to the various different administrative tools:
The OracleAS Portal framework provides administrative services, such as access to monitoring and configuration tools, single sign-on, directory integration, caching, and security. A lot of the features needed to manage users and groups, to set up security and search features, and to administer the portal and database are incorporated into a series of dialog boxes accessed through portlets on a Portal page.
After you have installed OracleAS Portal, you need to log in as an administrator, to perform various administrative functions.
After you have logged in to OracleAS Portal, the Portal Builder page is displayed to you, as shown in Figure 4-1:
Click the Administer tab to view all the sub-tabs and portlets that help you administer the Portal. The Administer tab is shown in Figure 4-2.
Text description of the illustration cg_sshot_administer_tab.gif
You will see the following sub-tabs in the Administer tab screen:
This sub-tab under the Administer tab in the Builder page contains the portlets shown in Table 4-1. This sub-tab is displayed by default when you click the Administer tab.
Portlet Name | Enables You to |
---|---|
Services |
See Chapter 7, "Monitoring and Administering OracleAS Portal" for more information on administering the log registry and monitoring Portal performance. |
SSO Server Administration |
See Chapter 6, "Securing OracleAS Portal" for more information. |
Export/Import Transport Set |
See Chapter 10, "Exporting and Importing Content" for more information. |
User |
|
Portal User Profile |
|
Group |
|
Portal Group Profile |
This sub-tab under the Administer tab in the Builder page contains the portlets shown in Table 4-2.
Portlet Name | Enables You To |
---|---|
Portlet Repository |
|
Remote Providers |
|
Remote Provider Group |
This sub-tab under the Administer tab in the Builder page contains the portlets shown in Table 4-3.
Portlet Name | Enables You To |
---|---|
Schemas |
|
Roles |
|
Database Information |
|
Database Memory Consumption, Transactions and Locks |
|
Database Storage |
For some administrative tasks that cannot be performed through the OracleAS Portal Administer tab, you may need to use one of the following tools:
The Oracle Enterprise Manager Application Server Control 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 enables you to perform the following administration and configuration operations:
These functions of the Application Server Control are described in more detail in Chapter 7, "Monitoring and Administering OracleAS Portal".
OracleAS Portal is dependent on the components: Oracle Application Server Web Cache and Oracle Internet Directory. It may be necessary to fine tune, or configure these components after Oracle Application Server is installed.
To simplify configuration changes, OracleAS Portal introduces the Portal Dependency Settings File. This file stores configuration data from all the dependent components in a central place and the content of the file is updated when there are configuration changes.
You can use the Portal Dependency Settings file to:
The Portal Dependency Settings file is described in more detail in Appendix A, "Using the Portal Dependency Settings File".
The OracleAS Portal Configuration Assistant (OPCA) is a Java-based configuration tool for installing and configuring the OracleAS Portal schema in the OracleAS Metadata Repository. OPCA is described in more detail in Appendix B, "Using the OracleAS Portal Configuration Assistant Command Line Utility".
There are also various scripts, copied to your ORACLE_HOME
during the installation of OracleAS Portal, These scripts may be needed to perform administrative actions, and are described in more detail in Appendix C, "Using OracleAS Portal Installation and Configuration Scripts".
This section covers the following topics:
After OracleAS Portal is installed, access it by entering the following URL in your browser:
http://<hostname>:<portnumber>/pls/<dad>
For an explanation of the URL components, see Table 3-1, " Portal URL Descriptions".
To find your Portal version number:
The version number for your OracleAS Portal is shown at the bottom of the page.
This section covers the following topics:
The home page is the first page that is displayed to a user after logging in to Oracle Portal. Here's how the logic works:
If mobile support is enabled, you can specify a default mobile home page to display when a user accesses the portal from a mobile device.
If there is no default home page for the user's default group, the system default home page is displayed.
To set the system default home page:
By default, the Services portlet is on the Portal sub-tab of the Administer tab on the Portal Builder page.
If the user has not selected a personal home page, but belongs to a default group, the default home page specified for that group is displayed.
To set a group's default home page:
By default, the Portal Group Profile portlet is on the Administer tab of the Builder page.
If the user has not selected a personal home page, but you have set one for him or her, the default home page specified for that user is displayed.
To set a user's default home page:
By default, the Portal User Profile portlet is on the Administer tab of the Builder page.
If you are the portal administrator, you are responsible for selecting a style to serve as the system default.
When a style is deleted, all pages and item regions that used the style revert to the page group default style. If the page group default style is <None>, all pages and regions revert to the system default style.
To set the system default style:
By default, the Services portlet is on the Portal sub-tab of the Administer tab on the Portal Builder page.
A personal page provides an area within OracleAS Portal where authorized users can store and share their own content. Personal pages are located under the Shared Objects page group, and are organized alphabetically by user name.
This section covers the following topics:
To configure OracleAS Portal to automatically create a personal page for new users:
By default, the Services portlet is on the Portal sub-tab of the Administer tab on the Portal Builder page.
Whenever a new user logs on for the first time, a personal page is automatically created for that user.
To configure OracleAS Portal to create a personal page for an existing user:
By default, the Portal User Profile portlet is on the Administer tab of the Builder page.
You can limit the amount of space provided in your database to store documents uploaded to page groups. If you want to limit the amount of space provided for a single page group, see Section 4.3.6, "Changing the Page Group Quota".
You can also limit the size of individual files that content contributors can upload to page groups. See Section 4.3.5, "Setting the Maximum File Size for Uploaded Files" for more information.
When a user uploads a file to the portal, the upload is monitored in the middle-tier to detect if the total space or maximum file size are exceeded. If either of these limits is exceeded, the upload is terminated and an error message is displayed.
To set the total space allocated for uploaded files:
By default, the Services portlet is on the Portal sub-tab of the Administer tab on the Portal Builder page.
You can limit the size of individual files that users can upload to the page groups in your portal.
You can also limit the total amount of space provided in your database to store documents uploaded to page groups. See Section 4.3.4, "Setting the Total Space Allocated for Uploaded Files" for more information.
When a user uploads a file to the portal, the upload is monitored in the middle-tier to detect if the maximum file size or portal file quota is exceeded. If either of these limits is exceeded, the upload is terminated and an error message is displayed.
To set the maximum file size for uploaded files:
By default, the Services portlet is on the Portal sub-tab of the Administer tab on the Portal Builder page.
You can limit the amount of space provided in your page group to store uploaded documents.
To change the page group quota:
OracleAS Portal enables you to choose the error message page that you want to display to users. You can choose the default system error page, or you can specify your own customized error page.
OracleAS Portal includes an error message page (called Sample Error Page) that you can edit to match the look and feel of the other pages in your portal. The Sample Error Page is available under the Portal Design-Time page group and includes a portlet that displays all the diagnostic information. Alternatively, you can create your own error message page in any of your page groups. To do this, you must include the Error Message Portlet on the page and turn caching off.
To specify an error message page:
By default, the Services portlet is on the Portal sub-tab of the Administer tab on the Portal Builder page.
You can specify the page that is displayed to users after they have logged out by setting the default home page for the PUBLIC (that is, non-authenticated) user.
To set the page users see when they log out:
By default, the Portal User Profile portlet is on the Administer tab of the Builder page.
If you have access to SQL*PLUS, you can suppress the Context-sensitive Help link that appears in the banner in OracleAS Portal wizards, dialog boxes, alerts, and so on. Note that you cannot suppress the "?" icon that appears in the blue bar of wizards, dialog boxes, and alerts.
You cannot perform this task through the UI; it must be done programmatically through SQL*PLUS.
To remove the context-sensitive help icon:
To re-instate the context-sensitive help icon:
exec wwui_api_body.set_display_help (wwui_api_body.DISPLAY_HELP_ON); commit;
To enable users to create their own portal user accounts, you must configure the self-registration feature. After completing this process the self-registration link is exposed in the Login portlet.
You can set up an approval process for self-registered users so that they cannot log in until their accounts have been approved. When the account has been approved or rejected, the user is notified by e-mail.
If you do not require approval for self-registered users, the user will be able to log in to the portal immediately after registering.
To set up self-registration:
By default, the Services portlet is on the Portal sub-tab of the Administer tab on the Portal Builder page.
By default, the Login portlet can be found in the SSO/OID page under the Administration page in the Portlet Repository.
If you have created your own self-registration screen, enter the URL in this field.
This section covers the following topics:
You can simplify the full URL created by the OracleAS Portal installation to a more memorable or meaningful URL using the Redirect directive. In this way, end users can access OracleAS Portal by entering a simple URL.
By default, the URL for a new OracleAS Portal installation requires you to enter:
http://hostname:portnumber/pls/dad
You can simplify this URL to:
http://hostname/redirectpath
httpd.conf
. This file is located in the following directory:
ORACLE_HOME/Apache/Apache/conf/
Redirect /DADnamepath http://hostname:portnumber/pls/dad
For example:
Redirect /portalhome http://mysite.oracle.com/pls/portal
In this example, end users can enter:
http://mysite.oracle.com/portalhome
to access the full URL, which is:
http://mysite.oracle.com/pls/portal
To set the OracleAS Portal homepage as the Oracle HTTP Server's default homepage:
ORACLE_HOME
/Apache/Apache/htdocs/
, make a backup copy of the files index.html.html
and index.html.<lang>
, where <lang>
is the language code. For example, index.html.en
is the index HTML file for English.
index.html.<lang>
by replacing the entire contents of the file with the following HTML redirection code:
<HTML> <SCRIPT LANGUAGE=JavaScript> document.location="http://host.domain:port/pls/portal" </SCRIPT> </HTML>
mod_plsql provides support for building and deploying PL/SQL-based applications on the Web. PL/SQL stored procedures can retrieve data from database tables and generate HTTP responses containing formatted data and HTML code to display in a Web browser.
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. The information in the DAD includes the user name (which also specifies the schema and the privileges), password, connect-string and Globalization Support language of the database.
There are two types of DADs: general DADs and Portal DADs. An OracleAS Portal middle-tier uses a Portal DAD to access the OracleAS Metadata Repository, which is discussed in this section. For information on general DADs, refer to the Oracle HTTP Server Administrator's Guide.
You configure DAD information from the mod_plsql Services page in the Oracle Enterprise Manager Application Server Control. See Figure 4-3.
Text description of the illustration cg_basic_sshot_createdad.gif
You can access the mod_plsql Services page from:
To configure a Portal DAD from the Application Server Control:
Typically, http://<host>.<domain.com>:1812
. For more information, see Section 7.1, "Using the Application Server Control".
From the DADs section you can also maintain existing DADs. To edit an existing DAD, click the DAD Name. To delete a DAD, select the DAD Name and click Delete.
If you leave the Oracle User Name and Oracle Password fields blank, the user is prompted to enter a username and password when first logging in.
Leave this field blank if the database is local.
If the Connection String Format is not specified, mod_plsql assumes the connect string format is either SIDFormat (host:port:sid
) or, resolvable as NetServiceNameFormat. The differentiation between the two is made by the presence of colon characters (:) in the connect string.
For database installations like Real Application Clusters (RAC), it is recommended that users configure the connect string using the NetServiceNameFormat such that the lookup is through LDAP. This allows database nodes to be for added/removed without having to reconfigure each Oracle Application Server middle-tier separately to recognize added/removed nodes.
<NLS_LANGUAGE>_<NLS_TERRITORY>.<NLS_CHARACTERSET>
, for example, American_America.UTF8.
To obtain these values, query the nls_database_parameters
table as follows:
select value, parameter from nls_database_parameters where parameter in ('NLS_LANGUAGE','NLS_TERRITORY','NLS_CHARACTERSET');
Once restarted, the new DAD is accessible from the Oracle HTTP Server.
Sometimes you must clear the portal cache (the OracleAS Portal File System Cache). For example, if you change the character set of the OracleAS Metadata Repository. In such cases, the existing content in the Portal cache will be invalid, as it will continue to have content configured to use the older character set.
To clear the Portal cache:
ORACLE_HOME
/Apache/modplsql/cache
.
rm -rf *
To avoid losing custom images stored in the OracleAS Portal images directory (which is ORACLE_HOME
/portal/images
by default), it is recommended that you create your own images directory and set up an appropriate Oracle HTTP Server alias for this directory.
For example, add an entry, similar to the one shown next, to the file ORACLE_HOME
/portal/conf/portal.conf
. It is recommended that you use the local Oracle Enterprise Manager Application Server Control instance to make this change. For more information, refer to the Oracle HTTP Server Administrator's Guide or the Oracle Application Server Web Cache Administrator's Guide.
Alias /mycompany/images/ "/opt/app/myportal/images/" <Directory "/opt/app/myportal/images/"> AllowOverride None Order allow,deny Allow from all ExpiresActive on ExpiresDefault A2592000 <Files *> Header set Surrogate-Control 'max-age=2592000' </Files> </Directory>
You do not need to perform any specific OracleAS Web Cache configuration as OracleAS Web Cache is already configured to globally cache .bmp, .gif, .png, .jpg, and .jpeg files.
This section discusses how OracleAS Portal and Oracle Application Server Wireless are configured to operate together. OracleAS Portal pages can be viewed from a wide variety of devices including desktop browsers, mobile phones, and PDAs. OracleAS Portal uses OracleAS Wireless to provide wireless functionality to receive requests from wireless devices, and transform content provided by the portal into an appropriate format.
This chapter contains the following sections:
Performing a standard Oracle Application Server installation of OracleAS Portal and Oracle Application Server Wireless configures mobile support in Portal as follows:
You can change most of these mobile settings using a standard desktop browser.
To modify mobile settings:
By default, the Services portlet is on the Portal sub-tab of the Administer tab on the Portal Builder page.
All the options for setting mobile options for OracleAS Portal are found here.
In the Mobile Settings page, you can perform the following actions:
This setting controls the response of OracleAS Portal to mobile clients that request portal pages by connecting through OracleAS Wireless.
If you want OracleAS Portal to be able to return pages and portlets in response to mobile requests, you must select the Enable Mobile Access option in the Mobile tab. If you do not select this option, OracleAS Portal responds to mobile requests with a message stating that it is not mobile enabled.
To enable mobile access:
By default, the Services portlet is on the Portal sub-tab of the Administer tab on the Portal Builder page.
Text description of the illustration cg_iasw_enablemobile.gif
You'll find additional information about how OracleAS Portal responds to mobile requests, in the article "Life Cycle of a Mobile Request," on Portal Center, http://portalcenter.oracle.com.
When mobile friendly Portal pages are created, an option to preview the page as it would display in a mobile device, is available in the page editor. Selecting the Enable Mobile Access option in the Mobile tab enables the display of the Mobile: Preview option in the page editor.
Text description of the illustration cg_iasw_mobilepreview.gif
This option enables page designers to create and edit pages using the mobile page editor, and also to specify mobile home pages. Pages of type Mobile are typically referred to as mobile pages.
To enable mobile page design:
By default, the Services portlet is on the Portal sub-tab of the Administer tab on the Portal Builder page.
Text description of the illustration cg_iasw_enablemobilepage.gif
You'll find additional information about the dedicated mobile page editor, in the article "Using the Mobile Page Editor," on Portal Center, http://portalcenter.oracle.com.
In addition, if you select this option, the following screens display an extra field that allows the selection of a home page specific to mobile access of the OracleAS Portal:
This setting controls the logging of OracleAS Portal mobile portlet responses.
To enable logging of mobile responses:
By default, the Services portlet is on the Portal sub-tab of the Administer tab on the Portal Builder page.
Text description of the illustration cg_iasw_logresponses.gif
Portlet responses are logged if all the following conditions are met:
You'll find additional information in the article "Provider Debugging Techniques: Using the Mobile Log Viewers," on Portal Center, http://portalcenter.oracle.com.
An Oracle Application Server reconfiguration that has resulted in a change to the Oracle Application Server Wireless service URL or OracleAS Portal home page URL, requires the changes to be reflected in the stored information in OracleAS Portal, and the OracleAS Wireless service definition that refers to OracleAS Portal. You should reconfigure OracleAS Wireless and OracleAS Portal to ensure that the communication between them is not affected.
You have to manually reconfigure OracleAS Wireless and OracleAS Portal to update the values of the following referenced URLs, as required:
The OracleAS Portal home page URL is the address that OracleAS Wireless service definition refers to. If the home page URL has changed, you need to update the following references to it:
Use the OracleAS Wireless Webtool to update the Portal service definition. Edit the URL value displayed in the Basic Info section of the OracleAS Wireless service definition that references OracleAS Portal. This section is accessible from the Services tab of the OracleAS Wireless Webtool. You access the Wireless Tools at:
http://server:port/mobile/
To change OracleAS Portal's own reference to its home page URL, use the script cfgiasw.csh
(UNIX) or cfgiasw.cmd
(Windows) to manually update the value. The script files are located here:
ORACLE_HOME/assistants/opca/cfgiasw.csh
To run the script, use the following command:
cfgiasw.csh -s portal -sp portal -c portal_db -h 'http://my_portal_server.com/pls/portal/portal.home'
The preceding example is specific to a UNIX machine. For more information on the cfgiasw
script, see Section C.8, "Using the cfgiasw Script to Configure Mobile Settings".
Oracle Application Server Wireless is used by OracleAS Portal as an intermediary in providing access to mobile devices. To provide this access, OracleAS Portal must know the URL to the OracleAS Wireless service on which the Portal is registered. If the OracleAS Wireless service URL has changed, its reference within OracleAS Portal needs to be updated. This reference can be updated in either of the following ways:
To update the value of the OracleAS Wireless Portal Service URL:
By default, the Services portlet is on the Portal sub-tab of the Administer tab on the Portal Builder page.
Text description of the illustration cg_iasw_wirelessurl.gif
You can change the OracleAS 10g Wireless Portal Service URL setting only when OracleAS Portal is not operating with multiple subscribers.
The Portal home page URL and Portal character set fields are for information only. If OracleAS Portal is operating with multiple subscribers, only the hosting administrator should change the value of OracleAS 10g Wireless Portal Service URL.
If you need to change OracleAS Portal's reference to the URL of Oracle Application Server Wireless Portal service, you can use the script cfgiasw.csh
(UNIX) or cfgiasw.cmd
(Windows) to manually set the value. The script files are located here:
ORACLE_HOME/assistants/opca/cfgiasw.csh
To run the script, use the following command:
cfgiasw.csh -s portal -sp portal -c portal_db -w 'http://my_iasw_server.com/ptg/rm?PAoid=12345'
The preceding example is specific to a UNIX machine. For more information on the cfgiasw
script, see Section C.8, "Using the cfgiasw Script to Configure Mobile Settings".
For more information on managing users, groups and passwords, refer to Chapter 6, "Securing OracleAS Portal".
See Also:
The Browser Recommendations section in the Preface of the Oracle Application Server Portal User's Guide. |
OracleAS Portal is designed to allow application development and deployment in different languages. OracleAS Portal is configured with the languages that are selected in the Oracle Universal Installer (OUI) during the Oracle Application Server middle-tier installation. Languages that are configured show up in the Set Language portlet. You can use OracleAS Portal in the language that corresponds to the language setting in the browser, or to the language you have selected in the Set Language portlet. To configure additional languages after installation, the OracleAS Portal Configuration Assistant (OPCA) must be used in LANGUAGE mode.
To install languages, run OPCA in the LANGUAGE mode. Note that you must run OPCA for each language that you want OracleAS Portal to support. See Section B.2.3, "LANGUAGE" for more information.
The following example loads the Dutch language strings into the OracleAS Metadata Repository.
ptlasst.csh -mode LANGUAGE -lang nl -available
See "Usage" in Section B.2.3, "LANGUAGE" for more information on the usage of the LANGUAGE OPCA mode.
Once a language is installed into OracleAS Portal, the end user can select the language to be used from the languages displayed in the Set Language portlet.
OracleAS Portal's globalization support enables you to define the preferred Locale and Territory to be used for a given language. For example, Australian English, or Canadian French.
The Set Language portlet is not available by default, and has to be added to the Portal Builder page.
To add the Set Language portlet to the Portal Builder page:
The Set Language portlet is now available in the Administer tab screen of the Portal Builder page.
To enable the use of territories and locales:
Text description of the illustration cg_basic_sshot_setlanguage.gif
By selecting the Enable Territory Selection option, the appropriate locales for each registered language are displayed. The locales are listed after the languages in the Set Language portlet, as shown in Figure 4-11.
Text description of the illustration cg_basic_sshot_setlang.gif
WebDAV is a protocol extension to HTTP 1.1 that supports distributed authoring and versioning. With WebDAV, the Internet becomes a transparent read and write medium, where content can be checked out, edited, and checked in to a URL address. mod_dav is an implementation of the WebDAV specification. The standard mod_dav implementation supports read and write access to files.
The term OraDAV refers to the capabilities available through the mod_oradav module. mod_oradav is the Oracle module that is an extended implementation of mod_dav, and is integrated with the Oracle HTTP Server. mod_oradav can read and write to local files, but also to an Oracle database. The Oracle database must have an OraDAV driver installed. The OraDAV driver is installed by default on installation of OracleAS Portal. mod_oradav calls this driver to map WebDAV activity to database activity. mod_oradav enables WebDAV clients to connect to an Oracle database, read and write content, and query and lock documents in various schemas.
When Oracle Application Server is installed, all required OraDAV parameters are set with values that enable access to Oracle database content through a Web browser or a WebDAV client. If necessary, you can modify parameter values if the default values do not meet your needs.
Similar to the Portal DAD configuration file, WebDAV has it own configuration file (ORACLE_HOME
/Apache/oradav/conf/oradav.conf
) that contains the OraDAV parameters, and start with DAV and DAVParam. These parameters are specified within a <Location> directive. The oradav.conf
file is included in the httpd.conf
file in an include statement.
After OracleAS Portal has been installed as part of the Oracle Application Server installation, the oradav.conf
file should be populated with a <Location> directive that points to the portal schema. In the following example, the location /dav_portal/portal
will be OraDAV-enabled and will (once populated with the correct values) connect to the portal schema so that users can use WebDAV clients to access portal data.
<Location /dav_portal/portal> DAV Oracle DAVParam ORACONNECT dbhost:dbport:dbsid DAVParam ORAUSER portal_schema DAVParam ORAPASSWORD portal_schema_password DAVParam ORAPACKAGENAME portal_schema.wwdav_api_driver </Location>
By default, the OracleAS Portal DAV URL is:
http://hostname:port/dav_portal/portal/
For example:
http://mysite.oracle.com:7777/dav_portal/portal
The dav_portal
part of the URL is the default name of a virtual directory used to differentiate between portal access through a WebDAV client and portal access that uses the pls
virtual directory. portal
is the DAD of the portal installation. You can also configure virtual hosts to provide a different, simpler, or easier to remember URL for WebDAV access, if need be.
Users connect to a portal in WebDAV clients using the same user name and password that they use to log in to the portal itself. If the portal is in a hosted environment, users also need to add their company information to their user name, as follows:
<username>@<company>
If you are using the SQL*Net Advanced Security Option (ASO), the ORACONNECT
parameter in the oradav.conf
file must be replaced with ORASERVICE dbhost
as shown next:
<Location /dav_portal/portal> DAV Oracle DAVParam ORASERVICE dbhost DAVParam ORAUSER portal_schema DAVParam ORAPASSWORD portal_schema_password DAVParam ORAPACKAGENAME portal_schema.wwdav_api_driver Options Indexes </Location>
This allows the database alias to be resolved by the tnsnames.ora
file.
The steps required to set up a WebDAV client to connect to OracleAS Portal varies depending on the client. All clients will eventually request a URL. The Portal DAV URL is very similar to the URL you use to access the portal itself in your Web browser, and uses the following format:
http://<hostname>:<port>/<dav_location>
If you experience problems while connecting to OracleAS Portal from a WebDAV client, refer to the WebDAV troubleshooting section in the Oracle Application Server Portal Error Messages Guide.
You can check the version of the OraDAV drivers from any Web browser, as shown in the following example:
http://<machine>:<port>/<dav location>/~OraDAV-Version
The output will be like the following example:
Version 1.0.3.2.3-0030 Using Container Version 1.5
You can check the version of mod_oradav.so
by running the oversioncheck
binary and specifying mod_oradav.so
as its argument, as shown subsequently:
ORACLE_HOME/Apache/Apache/bin/oversioncheck ORACLE_HOME
/Apache/oradav/lib/mod_oradav.so
|
![]() Copyright © 2002, 2003 Oracle Corporation. All Rights Reserved. |
|