| Oracle® Content Services Administrator's Guide 10g Release 1 (10.1.2) Part Number B25275-04 |
|
|
View PDF |
| Oracle® Content Services Administrator's Guide 10g Release 1 (10.1.2) Part Number B25275-04 |
|
|
View PDF |
After you install and configure Oracle Content Services, you may want to customize your setup for a particular deployment scenario. For example, you may want to integrate Oracle Content Services with an antivirus solution, or run the Oracle Content Services application on a different port number.
Additional deployment options are covered elsewhere in this book. See the following references for more information:
This chapter provides information about the following topics:
Records management is the systematic and comprehensive control of the creation, capture, maintenance, filing, use, and disposition of records. Its goal is to ensure that records:
Are authentic and reliable
Can be retrieved when needed as quickly and efficiently as possible
Are not destroyed prematurely or kept longer than required
Oracle Records Management is a records management application that ships with Oracle Content Services. It must be licensed separately; see Oracle Collaboration Suite Licensing Information for more information.
When you install Oracle Content Services, Oracle Records Management is installed automatically, but the application is disabled by default. You can use the Oracle Collaboration Suite Control to enable Oracle Records Management. You can also choose to configure records management-related metrics.
User permissions related to Oracle Records Management are managed from the Oracle Content Services Web client. See Oracle Content Services Application Administrator's Guide for more information.
For information about how to use Oracle Records Management, see Oracle Records Management Administrator's Guide.
Although the Oracle Records Management application is disabled, by default, after you install and configure Oracle Content Services, you can use the Oracle Collaboration Suite Control to enable Oracle Records Management.
To enable Oracle Records Management, you must first enable the Oracle Records Management OC4J instance (OC4J_RM), then activate the node configuration for the Oracle Records Management HTTP node. Finally, you must activate the Records Management Lifecycle Agent.
|
Note: You must activate the node configuration for the Oracle Records Management HTTP node to use Oracle Records Management. It is not enough to enable only the Oracle Records Management OC4J instance. |
If you have multiple Oracle Content Services Applications tiers on which you want to enable Oracle Records Management, you must connect to the Oracle Collaboration Suite Control on each Applications tier to enable multiple Oracle Records Management OC4J instances.
To enable Oracle Records Management OC4J instances:
Connect to the Oracle Collaboration Suite Control and go to the Collaboration Suite Home page.
From the Collaboration Suite Home page, click Enable/Disable Components.
From the Disabled Components list, select OC4J_RM and click Remove. The selected component appears in the Enabled Components list.
Click OK.
Restart Oracle HTTP Server (HTTP_Server) from the Collaboration Suite Home page.
Repeat these steps for each Oracle Content Services Applications tier on which you want to run Oracle Records Management.
You can activate all Oracle Records Management HTTP node configurations from one Applications tier.
To activate Oracle Records Management HTTP node configurations:
Connect to the Oracle Collaboration Suite Control and go to the Content Services Home page.
In the Administration section, click Node Configurations.
Click the name of the Oracle Records Management HTTP node for this Applications tier. The name of the Oracle Records Management HTTP node appears in the following format: Applications_tier_name_RM_HTTP_Node.
Select Active in the General section, then click OK.
If you have multiple Applications tiers on which you want to enable Oracle Records Management, click the names of the Oracle Records Management HTTP nodes for the other Applications tiers. On the Edit Node Configuration page for these nodes, select Active, then click OK.
Return to the Content Services Home page and start each Oracle Records Management HTTP node. To do this, select each OC4J_RM instance in the Processes list and click Start.
Each Oracle Records Management HTTP node has the same display name (OC4J_RM). Use the Middle Tier column of the Processes table to distinguish between different Oracle Records Management HTTP nodes. (In the Oracle Collaboration Suite Control, Middle Tier is used interchangeably with Applications tier.)
After you have at least one Oracle Records Management HTTP node running, you can access the Oracle Records Management application from any Web browser. The default URL is:
http://hostname:port/rm
Use the same host name and port as for the Oracle Content Services application. Use https:// if you are using SSL.
The Records Management Lifecycle Agent runs on only one Applications tier. You must activate this agent for Oracle Records Management to work properly.
See "Records Management Lifecycle Agent" for more information about this agent.
To activate the Records Management Lifecycle Agent:
Connect to the Oracle Collaboration Suite Control and go to the Content Services Home page.
In the Administration section, click Node Configurations.
On the Node Configurations page, click the name of the regular node that runs the Records Management Lifecycle Agent.
In the Servers section, select RmLifeCycleAgent and click Edit.
Select Active, then click OK.
On the Edit Node page, click OK.
Return to the Content Services Home page and restart the node that corresponds to the node configuration you edited.
You can optionally choose to collect metrics related to Oracle Records Management Web application response time by configuring particular performance metrics on each Applications tier. For more information about how to do this, see "Configuring Performance Metrics".
Oracle Content Services integrates with a partner solution, the Symantec AntiVirus Scan Engine (SAVSE), to provide options to verify that content is virus free and to clean files that are infected.
After antivirus integration has been set up, files will be scanned for viruses whenever they are opened for read access, using the latest available virus definitions. The following files will be excluded from the scanning process:
Files that are quarantined
File formats (such as .doc) that are excluded by the administrator
Files that have already been scanned using the current virus definitions
If a file is infected with a virus, it will be marked as quarantined, and users will not be able to open the file until it is repaired. Contents of the file will remain unreadable even if virus checking is disabled by the administrator.
The Virus Repair Agent is responsible for repair attempts and retrieving the latest virus definitions. Whenever the agent becomes active, it polls the SAVSE server for updated virus definitions, and then attempts to repair the quarantined files. The agent will not attempt to repair the following files:
Files that have exceeded the maximum number of repair attempts
Files that have already experienced repair attempts using the current virus definitions
The following sections describe how to set up virus checking in Oracle Content Services:
SAVSE must be installed and configured properly to function with Oracle Content Services. The following options must be set:
You must select ICAP as the communication protocol. No other protocols are supported.
You must set the scan policy to Scan and Repair or Scan Only. If you choose Scan Only, no repair attempts will be made. The Scan and Delete and Scan, Repair or Delete options are not supported.
You must enable the ICAP 403 response. This parameter cannot be set using the SAVSE administration tool; instead, it must be manually set in the SAVSE configuration file.
After the SAVSE server has been installed and configured, you can enable antivirus functionality in Oracle Content Services. You can also change the maximum number of repair attempts for quarantined documents, and configure how often the Virus Repair Agent is activated. Use the Oracle Collaboration Suite Control to perform these tasks.
To enable antivirus functionality and set the maximum number of repair attempts:
Connect to the Oracle Collaboration Suite Control and go to the Content Services Home page.
In the Administration section, click Domain Properties.
Click the IFS.DOMAIN.ANTIVIRUS.Enabled property, set the value to true, and click OK.
Click the IFS.DOMAIN.ANTIVIRUS.Host property, enter the host name or IP address of the computer where the SAVSE server is running, and click OK.
Click the IFS.DOMAIN.ANTIVIRUS.MaxRepairAttempts property, enter the number of times you want the Virus Scan Agent to attempt to repair a file, and click OK.
Click the IFS.DOMAIN.ANTIVIRUS.Port property, enter the value for the SAVSE listener port, and click OK.
Return to the Content Services Home page and click Restart Domain.
To configure how often the Virus Repair Agent becomes active:
Connect to the Oracle Collaboration Suite Control and go to the Content Services Home page.
In the Administration section, click Server Configurations.
Click VirusRepairAgentConfiguration.
In the Properties section, click IFS.SERVER.TIMER.ActivationPeriod.
Change the Value as necessary.
On the Edit Property page, click OK.
On the Edit Server Configuration page, click OK.
Return to the Content Services Home page and restart the node that runs this agent.
You can exclude formats from being scanned for viruses to improve system performance. For example, you may choose to only scan formats with a higher probability of being infected, such as .zip files. Use the Oracle Collaboration Suite Control to exclude formats from virus checking.
To exclude formats from being scanned:
Connect to the Oracle Collaboration Suite Control and go to the Content Services Home page.
In the Administration section, click Formats.
Click the name of the format you want to exclude from virus scanning.
Select Omitted From Anti-Virus Scan.
Click OK.
The performance of Oracle Content Services may be affected by enabling the virus checking option. The performance impact depends on the following factors:
The frequency of virus definition updates made to the SAVSE service. Each time virus definitions are updated, all files that are opened (except for quarantined or excluded files) are scanned - none are excluded based on having already been scanned with these definitions, because the definitions are new.
After a virus definition update, overall system performance will degrade initially, but will gradually return to normal as more files are scanned with the current virus definitions and are therefore excluded from subsequent scans.
The size and frequency of use of the Oracle Content Services repository.
The type and size of the data in the repository.
The probability of the number of attempted reads on unique files. Since files will only be scanned the first time they are opened against the current definitions, the frequency of unique files will affect performance.
The performance of the SAVSE service. This is the most significant performance factor.
The number of files whose format has been excluded from scanning by the administrator. Excluding certain formats will reduce the number of scans and improve system performance.
The Oracle Content Services storage management options provide support for both offline and near-line storage. In offline and near-line storage, content that is infrequently accessed is moved from expensive online media, such as a disk array, to a cheaper offline medium, such as tape. The metadata and search indexes are kept online and are readily available.
Oracle Content Services uses BFILEs to support offline and near-line storage. A BFILE is a read-only Oracle data type consisting of a directory object and a file name. Updating a document whose content is stored as a BFILE results in the content being reloaded from the external storage as a new binary large object (BLOB), where the modifications are made. The new content will be indexed, depending on its format. End users will be unaware of where their content is stored.
This section provides information about the following topics:
Oracle Content Services provides both data aging and data archiving through BFILEs. Through data aging, content that has not been accessed for a specified interval can be automatically moved from a BLOB to a BFILE. Through data archiving, content in the Archive is automatically moved from a BLOB to a BFILE.
Content that has been moved to a BFILE is still accessible, and is visible as any content would be when users are browsing or searching.
BFILE aging and archiving are not enabled by default. Follow the instructions in the subsequent sections to set up BFILE aging and archiving:
Oracle Content Services is not set up for BFILE aging by default. To configure BFILE aging, you must first set domain properties that enable BFILE aging, then you must configure and activate the Content Agent. You can also specify storage management options.
To set domain properties that enable BFILE aging:
Connect to the Oracle Collaboration Suite Control and go to the Content Services Home page.
In the Administration section, click Domain Properties.
Click IFS.DOMAIN.BFILE.Enabled, set the value to true, and click OK.
Click IFS.DOMAIN.BFILE.AgingEnabled, set the value to true, and click OK.
Return to the Content Services Home page and click Restart Domain.
To configure and activate the Content Agent:
Connect to the Oracle Collaboration Suite Control and go to the Content Services Home page.
In the Administration section, click Server Configurations.
Click ContentAgentConfiguration.
Edit the server configuration properties as desired; see the Content Agent properties in Appendix E, "Server Configuration Properties" for more information about specific properties. In particular, you may want to edit IFS.SERVER.AGENT.CONTENTAGENT.RetentionPeriod; this property specifies the inactivity interval for files before they are moved to a BFILE.
Click OK.
Return to the Content Services Home page, and in the Administration section, click Node Configurations.
Click the name of the node configuration that corresponds to the node where you want to run the Content Agent.
On the Edit Node Configuration page, in the Servers section, click ContentAgent.
Select Initially Started and click OK.
On the Edit Node Configuration page, click OK.
Return to the Content Services Home page, select the node that corresponds to the node configuration you edited, and click Restart.
After you have set the domain properties for BFILE aging and configured the Content Agent, you can set storage management options as described in "Specifying Storage Management Options".
Oracle Content Services is not set up for BFILE archiving by default. To configure BFILE archiving, you must set domain properties that enable BFILE archiving. You can also specify storage management options.
To set domain properties that enable BFILE archiving:
Connect to the Oracle Collaboration Suite Control and go to the Content Services Home page.
In the Administration section, click Domain Properties.
Click IFS.DOMAIN.BFILE.Enabled, set the value to true, and click OK.
Click IFS.DOMAIN.BFILE.ArchivingEnabled, set the value to true, and click OK.
Return to the Content Services Home page and click Restart Domain.
After you have set the domain properties for BFILE archiving, you can set storage management options as described in "Specifying Storage Management Options".
If you are using Oracle Records Management, you have the option of storing certain types of records using BFILEs. Near-line storage for records is not enabled by default; to enable this option, you must set a BFILE-related domain property and specify storage management options.
To set the domain property that enables near-line records storage:
Connect to the Oracle Collaboration Suite Control and go to the Content Services Home page.
In the Administration section, click Domain Properties.
Click IFS.DOMAIN.BFILE.Enabled, set the value to true, and click OK.
Return to the Content Services Home page and click Restart Domain.
After you have set the domain property to enable near-line storage for records, you can set storage management options as described in the following section.
You can change the default base path and policy for BFILE storage using the Oracle Collaboration Suite Control. These settings apply to all types of BFILE storage, including BFILE aging, BFILE archiving, and near-line storage for records.
To specify storage management options:
Connect to the Oracle Collaboration Suite Control and go to the Content Services Home page.
In the Administration section, click Storage Management.
You will not be able to access the Storage Management page unless you have already set the IFS.DOMAIN.BFILE.Enabled property to true.
Figure 2-1 shows the Storage Management page.
Change the BFILE Base Path. The default base path is:
ORACLE_HOME/ifsbfiles/content_services_schema
ORACLE_HOME refers to the database Oracle home on the database computer.
Each BFILE has a relative path in addition to the base path. The relative path is:
/yyyy/dd/mm/hh/mm/ss/ifsbfile_id
In the relative path, ifsbfile_id is the file naming pattern that associates a unique ID to each piece of content.
Change the BFILE Policy. This policy determines whether the operating system files should be deleted when the BFILE references are deleted from the database. If you are storing BFILEs on an optical device that does not permit deletion, you should specify that the operating system files should be retained.
Click OK.
Oracle Content Services supports integration with two records management retention solutions: Network Appliance SnapLock and EMC Centera. These retention storage solutions provide write once, read many (WORM) data permanence capabilities for records management and regulatory compliance requirements. The critical data becomes immutable, nonrewritable, and unremovable for a specified retention period.
You must license Oracle Records Management in order to use a retention storage solution with Oracle Content Services. See Oracle Collaboration Suite Licensing Information for more information.
To integrate Oracle Content Services with a records management retention device, you must install and configure the hardware, either Network Appliance SnapLock or EMC Centera. Then, refer to the following sections for additional information about configuring Oracle Content Services for the appropriate retention device:
|
Note: The features described in this section were added to Oracle Collaboration Suite in the Oracle Collaboration Suite Cumulative Patchsets 10.1.2.1 and 10.1.2.2. Support for Network Appliance SnapLock was added in the Oracle Collaboration Suite Cumulative Patchset 10.1.2.1, and support for EMC Centera was added in the Oracle Collaboration Suite Cumulative Patchset 10.1.2.2.If you are using a previous version or patchset of Oracle Collaboration Suite, the features described are not available. |
Follow the instructions in this section to configure Oracle Content Services for Network Appliance SnapLock integration. Before you begin, make sure that Oracle Records Management has been configured and that the Records Management Lifecycle Agent has been activated. See "Setting Up Oracle Records Management" for more information.
This section contains the following topics:
Configuring the Database Computer for Network Appliance SnapLock
Configuring the Applications Tier Computer for Network Appliance SnapLock
Network Appliance SnapLock uses NFS to move data from the Oracle Collaboration Suite database to the retention storage device.
To configure the database computer on UNIX systems:
As the root user, perform an NFS mount to the SnapLock volume. Refer to the documentation for your operating system for optimum NFS mount point options.
In the mounted directory, create another directory. This new directory will be considered as the relative path to the SnapLock volume. The owner and group permissions on this new directory must be the same as that of the operating system user running the database.
To configure the database computer on Microsoft Windows systems:
On the database computer, install and configure an NFS client for Windows systems.
Ensure that the pcnfsd daemon process is running on the Network Appliance device. To start the pcnfsd process:
Access the Web-based Network Appliance administration tool, na_admin, using the following URL:
http://hostname/na_admin
Click the FilerView icon.
When prompted, provide the na_admin user name and password.
Click NFS > Configure in the left navigation pane.
Set PCNFS Enabled to Yes.
Click Apply.
Alternatively, you can telnet to the Network Appliance device and type the following command:
options pcnfsd.enable on
Use the NFS client to map a drive to the SnapLock volume. This will cause the SnapLock volume to appear as a drive letter.
Refer to the documentation for your NFS client for optimum NFS mount point options.
Perform the following steps on the Applications tier that is running the Records Management Lifecycle Agent. To determine which Applications tier is running this agent, use the Oracle Collaboration Suite Control to view each node to see where the agent is running.
Follow the steps in these sections to configure the Applications tier:
Installing the Network Appliance SnapLock Software
You must install the Network Appliance SnapLock software on the Applications tier that is running the Records Management Lifecycle Agent. To do this, follow these steps:
Obtain the Network Appliance SnapLock software (version 1.5 or later), located in the Network Appliance manageontap.jar file. You can obtain this file from the Network Appliance NOW (NetApp on the Web) site at http://now.netapp.com.
You must become a member of the NOW site by clicking the New User Sign Up link. There is no cost to join. Once you are a member, go to the following URL to download the software:
http://now.netapp.com/NOW/download/tools/oracleocs_manageontap/
Be sure to refer to the Network Appliance certification information to ensure that Network Appliance supports your operating system.
Copy the manageontap.jar file to the ORACLE_HOME/content/lib directory.
Modify the classpath in the following XML files to include the manageontap.jar file:
ORACLE_HOME/opmn/conf/opmn.xml
ORACLE_HOME/j2ee/OC4J_Content/application-deployments/content/content/orion-web.xml
ORACLE_HOME/j2ee/OC4J_RM/application-deployments/rm/rm/orion-web.xml
|
Note: For more information about the Network Appliance software, refer to Data ONTAP System Administration Guide at the Network Appliance NOW site athttp://now.netapp.com. |
Setting Domain Properties for Network Appliance SnapLock
Use the Oracle Collaboration Suite Control to set domain properties related to Network Appliance SnapLock. To do this, follow these steps:
On the Content Services Home page, click Domain Properties.
Click IFS.DOMAIN.RETENTION.StorageDevice. You may need to move to the next page to find this property, or you can use the Search field.
In the Value field, select SNAPLOCK and click OK.
Click IFS.DOMAIN.RETENTION.SNAPLOCK.Configuration.
Click HOST.
In the Value field, specify the host name or IP address of the Network Appliance device and click OK.
Click MOUNTPOINT.
In the Value field, enter the absolute path where the Network Appliance is NFS-mounted on the database and click OK.
If the database computer is running on Windows, you must enter a universal naming convention (UNC) path. For example, for a Filer called snapserver and a volume called wormdrive, you would enter the following path:
\\\\snapserver\\wormdrive
Because the backslash (\) is a common escape character, you must add an additional backslash to each backslash in the path. This means that you must enter four backslashes at the beginning of the path.
Click PORT.
In the Value field, enter the port used to communicate with the Network Appliance device through HTTP and click OK. The default port is 80.
Click RELATIVEPATH.
In the Value field, specify the relative path to the NFS mount point where content should be stored and click OK.
If the database computer is running on Windows, you must enter a universal naming convention (UNC) path. Because the backslash (\) is a common escape character, you must add an additional backslash to each backslash in the path.
Click SNAPLOCKEXPORTPATH.
In the Value field, specify the absolute path of the NFS-exported volume and click OK.
On the Edit Domain Property page, click OK.
Specifying Credential Information for Network Appliance SnapLock
Use the Oracle Collaboration Suite Control to specify credential information for Network Appliance SnapLock. To do this, follow these steps:
From the Content Services Home page, click Retention Hardware.
Figure 2-2 shows the Retention Hardware page.
In the Retention Device Type field, select Network Appliance SnapLock.
Enter a Username for Network Appliance SnapLock. You must provide a user name created in Network Appliance SnapLock; do not provide an Oracle Content Services user name.
Enter a corresponding Password for Network Appliance SnapLock, and confirm it in the Confirm Password field.
Click OK.
Return to the Content Services Home page and click Restart Domain.
Follow the instructions in this section to configure Oracle Content Services for EMC Centera integration. Before you begin, make sure that Oracle Records Management has been configured and that the Records Management Lifecycle Agent has been activated. See "Setting Up Oracle Records Management" for more information.
You should perform the steps in the following sections on the Applications tier that is running the Records Management Lifecycle Agent. To determine which Applications tier is running this agent, use the Oracle Collaboration Suite Control to view each node to see where the agent is running
This section contains the following topics:
You must install the EMC Centera software on the Applications tier that is running the Records Management Lifecycle Agent. To do this, follow these steps:
Download EMC Centera 3.1 Patch 1 SDK or later from OracleMetaLink at http://metalink.oracle.com. To find the SDK on OracleMetaLink, search for patch number 5072277.
This SDK contains the necessary .jar and library files. Follow the instructions in the readme to install the software.
Modify the classpath in the following XML files to include the FPLibrary.jar file:
ORACLE_HOME/opmn/conf/opmn.xml
ORACLE_HOME/j2ee/OC4J_Content/application-deployments/content/content/orion-web.xml
ORACLE_HOME/j2ee/OC4J_RM/application-deployments/rm/rm/orion-web.xml
In ORACLE_HOME/opmn/conf/opmn.xml, include the directory that contains the libraries in the appropriate path variable for the node, OC4J_Content, and OC4J_RM. This variable is called LD_LIBRARY_PATH on Linux and Solaris, PATH on Windows, SHLIB_PATH on HPUX, and LIBPATH on AIX. For example, on Linux, include the following entry:
<environment>
<variable id="$LD_LIBRARY_PATH" value "$LD_LIBRARY_PATH:absolute_path_to_Centera_lib_directory"/>
</environment>
An example path on Linux could be:
/usr/local/centera31/lib
|
Note: Ifopmn.xml does not include an <environment> entry for the variable for your platform, you must create one. |
Use the Oracle Collaboration Suite Control to set domain properties related to EMC Centera. To do this, follow these steps:
On the Content Services Home page, click Domain Properties.
Click IFS.DOMAIN.RETENTION.StorageDevice. You may need to move to the next page to find this property, or you can use the Search field.
In the Value field, select CENTERA and click OK.
Click IFS.DOMAIN.RETENTION.CENTERA.Configuration.
Click ADDRESSLIST.
In the Value field, enter the comma-separated IP addresses of the EMC retention clusters and click OK.
On the Edit Domain Property page, click OK.
Use the Oracle Collaboration Suite Control to specify credential information for EMC Centera. To do this, follow these steps:
From the Content Services Home page, click Retention Hardware.
Figure 2-3 shows the Retention Hardware page.
In the Retention Device Type field, select EMC Centera.
Enter a Username for EMC Centera. You must provide a user name created in EMC Centera; do not provide an Oracle Content Services user name.
Enter a corresponding Password for EMC Centera, and confirm it in the Confirm Password field.
Click OK.
Return to the Content Services Home page and click Restart Domain.
If you want to change the Oracle Content Services application port to a different port number, perform the tasks listed in the following sections:
For additional information about changing port numbers, see Chapter 14, "Changing Oracle Collaboration Suite Network Configurations" in Oracle Collaboration Suite Administrator's Guide.
Use the Oracle Collaboration Suite Control to change the port number in Oracle HTTP Server.
From the Collaboration Suite Home page, click HTTP_Server.
Click Administration.
Click Server Properties.
In the Listening Addresses and Ports section, change the Default Port to the desired port number.
Click Apply.
On the Confirmation page, click Yes to restart Oracle HTTP Server.
If OracleAS Web Cache is enabled, you must change the port number in OracleAS Web Cache using the Oracle Collaboration Suite Control. To do this, follow these steps:
From the Collaboration Suite Home page, choose Web Cache.
Click the Administration tab, then click Ports in the Properties - Web Cache section.
Change the appropriate port number in the Listen Ports section, then click OK.
Return to the Web Cache Home page and click Restart.
After you change the port number in Oracle HTTP Server, you must register the new port with OracleAS Single Sign-On. To do this, run the single sign-on registration tool, then restart Oracle HTTP Server. See "Registering mod_osso" in Oracle Application Server Single Sign-On Administrator's Guide for more information.
Universal Resource Identifiers (URIs) for Oracle Content Services that are registered in the Oracle Internet Directory Service Registry may need to be updated with the new port number. See "Managing the Oracle Internet Directory Service Registry" in Chapter 7 of Oracle Collaboration Suite Administrator's Guide for more information.
Use the Oracle Collaboration Suite Control to update the Oracle Content Services Application Port domain property and restart the Oracle Content Services OC4J instance:
From the Content Services Home page, in the Administration section, click Domain Properties.
On the Domain Properties page, click IFS.DOMAIN.APPLICATION. ApplicationPort. You may need to move to the second or third page to find this domain property, or you can use the Search field.
On the Edit page, enter the new port number in the Value field and click OK. If you are using a load balancer with multiple Oracle Content Services Applications tiers, enter the load balancer port.
Return to the Content Services Home page.
Select OC4J_Content and click Restart. If you are using Oracle Records Management, you also need to restart OC4J_RM.
You also need to update the port number for any affected Web application response time metrics. To do this, update the affected URLs on the Metric Configuration page in the Oracle Collaboration Suite Control. See "Configuring Performance Metrics" for more information.
You can set up Oracle Content Services so that users outside the firewall can have access. To do this, follow these steps:
Open ports. Disable the firewall for the following ports:
Oracle Content Services domain ports (node manager, node controller)
Database listener port (typically 1521)
Apache port (Oracle HTTP Server port)
Oracle Internet Directory ports (if Oracle Internet Directory is running inside the firewall)
Load balancer port (if you use a load balancer)
Set firewall timeout periods. You must set the operating system parameter TCP_keepalive to 120 minutes.
Figure 2-4 shows a possible firewall scenario with the database and Applications tiers inside the firewall, and with OracleAS Infrastructure outside the firewall.
Oracle Content Services provides support for and integration with the OmniPortlet, a feature of Oracle Application Server Portal (OracleAS Portal). You can set up a preconfigured instance of the OmniPortlet, called the Content Services portlet, in your OracleAS Portal page. The Content Services portlet uses the Content Services searchlet, a user-definable query tool, and a tabular layout to display user-specific Oracle Content Services data. Users can search for and display content from Oracle Content Services in the Content Services portlet.
The following sections provide instructions about how to set up the OmniPortlet for Oracle Content Services:
All steps are performed on the Applications tier running OracleAS Portal.
To deploy the Content Services Searchlet, you must provide the content_searchlet.rar file and add connection information to the oc4J-connectors.xml file.
To deploy the Content Services Searchlet:
Create a directory called ContentSearchlet under the following directory:
ORACLE_HOME/j2ee/OC4J_Portal/connectors
Copy the content_searchlet.rar file and paste it into the ContentSearchlet directory you just created. The content_searchlet.rar file is located on the Oracle Content Services Applications tier computer in the following directory:
ORACLE_HOME/content/lib
Go to the ORACLE_HOME/j2ee/OC4J_Portal/config directory and open the oc4j-connectors.xml file for editing.
Add a <connector> tag for the Content Services Searchlet by adding the following lines to the <OC4J-connectors> section:
<connector name="ContentSearchlet" path="content_searchlet.rar"> </connector>
The relevant portion of the edited file should look similar to the following:
<oc4j-connectors> <connector name="ContentSearchlet" path="content_searchlet.rar"> </connector> </oc4j-connectors>
Save the file.
Restart the OC4J instance for OracleAS Portal (OC4J_Portal) using the Oracle Collaboration Suite Control, or you can use the following opmnctl command:
opmnctl restartproc process-type=OC4J_Portal
The content_searchlet.rar file is expanded under the ORACLE_HOME/j2ee/OC4J_Portal/connectors/ContentSearchlet directory.
After you have deployed the Content Services Searchlet, you must register the OmniPortlet with Oracle Internet Directory by adding a <grant> entry to the jazn-data.xml file, and by running the ops2scfg script.
To register the OmniPortlet with Oracle Internet Directory:
Go to the ORACLE_HOME/config directory and open the jazn-data.xml file for editing.
Add the following <grant> entry before the closing tags </jazn-policy></jazn-data> to set access permissions on the OmniPortlet repository API:
<grant>
<grantee>
<codesource>
<url>file:Oracle_home_path/portal/jlib/portaltools.jar</url>
</codesource>
</grantee>
<permissions>
<permission>
<class>oracle.ias.repository.schemaimpl.CheckRepositoryPermission</class>
<name>makeNewOIDEntry</name>
</permission>
<permission>
<class>oracle.ias.repository.schemaimpl.CheckRepositoryPermission</class>
<name>connectAs</name>
</permission>
</permissions>
</grant>
Make sure to replace Oracle_home_path with the actual path of the Oracle home.
Save the file.
Run the ops2scfg script, located in the ORACLE_HOME/portal/conf directory, and provide the following values when prompted:
Create a name and password for the OmniPortlet application entry in Oracle Internet Directory (for example, orclApplicationCommonName=OmniPortlet)
Enter the user name and password of an Oracle Internet Directory administrator
When the script completes, copy and save the output. For example:
orclApplicationCommonName=OmniPortlet,cn=Portal,cn=Products,cn=OracleContext
You will need to provide this information when you add a Content Services data source to the OmniPortlet framework.
|
Note: Be careful when you supply values for theops2scfg script, because you can only run the script one time. If you need to update these values later, you must do so in Oracle Internet Directory. |
After you have registered the OmniPortlet with Oracle Internet Directory, you must configure the Content Services Searchlet by providing connection information in the oc4j-ra.xml file.
To configure the Content Services Searchlet:
Go to the ORACLE_HOME/j2ee/OC4J_Portal/application- deployments/default/ContentSearchlet directory.
Open the oc4j-ra.xml file for editing.
Specify the JNDI name for the Content Services Searchlet and set the value for Search Web Service URL by updating the <connector-factory> tag, as follows:
<connector-factory location="eis/ContentSearchlet" connector-name="Content
Services Search Adapter">
<config-property name="webServiceURL" value="http://content_services_host_
name:port/content/ws"/>
</connector-factory>
Save the file.
Restart the OC4J instance for OracleAS Portal (OC4J_Portal) using the Oracle Collaboration Suite Control, or you can use the following opmnctl command:
opmnctl restartproc process-type=OC4J_Portal
After you have configured the Content Services Searchlet, you must add a data source for Oracle Content Services to the OmniPortlet framework by creating a data source descriptor file.
To add a data source for Oracle Content Services to the OmniPortlet framework:
Create a directory called Content under the following directory:
ORACLE_HOME/j2ee/OC4J_Portal/applications/portalTools/omniPortlet/WEB-INF/ plugins/datasources
Go to the new folder.
Create a datasource descriptor file (datasource.xml) with the content that appears in the following sample. For <OCSClientDN>, provide the script output you saved from Step 4 of the procedure in "Registering the OmniPortlet with Oracle Internet Directory".
|
Note: If you cut and paste the text directly from this document, remove the extra carriage return and any extra spaces betweenoracle.webdb.reformlet.data.search and .SearchDataSourceDefinition. Otherwise, the data source descriptor file will not work. |
<datasources>
<datasource class="oracle.webdb.reformlet.api.plugin.DefaultDataSource">
<name>Content</name>
<displayName>Content</displayName>
<icon>Content.gif</icon>
<includeParamSection>true</includeParamSection>
<editDefaultsHelp>rfdvdtwp.htm</editDefaultsHelp>
<!-- Default values of datasource's metadata -->
<metadata class="oracle.webdb.reformlet.data.search .SearchDataSourceDefinition">
<name>Content</name>
<displayName>Content</displayName>
<contentDataSourceJndiName>eis/ContentSearchlet</contentDataSourceJndiName>
<requiresS2SAuthentication>true</requiresS2SAuthentication>
<useSSL>true</useSSL>
<OCSClientDN>orclApplicationCommonName=OmniPortlet,cn=Portal,cn=Products,cn=OracleContext</OCSClientDN>
</metadata>
</datasource>
</datasources>
Restart the OC4J instance for OracleAS Portal (OC4J_Portal) using the Oracle Collaboration Suite Control, or you can use the following opmnctl command:
opmnctl restartproc process-type=OC4J_Portal
After you have added the data source to the OmniPortlet framework, you can define the OmniPortlet in OracleAS Portal by choosing search criteria and deciding which fields to display.
To define the OmniPortlet in OracleAS Portal:
Create a page in OracleAS Portal. To do this, on the OracleAS Portal home page, click Create Page and follow the Wizard instructions.
From your new page, click the Add Portlet icon and go to the OmniPortlet you registered. Then, select the portlet and click OK.
Click Define. The Type page appears.
Select Content and click Next.
On the Source page, click Next.
On the Filter page, enter search criteria for the OmniPortlet.
On the View page, click Next.
On the Layout page, enter the fields you want the OmniPortlet to return.
Click Finish.
|
Note: When you click a link to a folder within the OmniPortlet, you may be asked to re-authenticate. This behavior does not occur if you click a document link. |
