| Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1.1) for Windows Part Number B12239-01 |
|
|
View PDF |
| Oracle® Collaboration Suite Installation and Configuration Guide Release 2 (9.0.4.1.1) for Windows Part Number B12239-01 |
|
|
View PDF |
This chapter guides you through the process of configuring Oracle Files.
This chapter contains these topics:
The following steps are required to configure and run Oracle Files:
Run the Oracle Files configuration assistant.
Start the Oracle Files processes.
Create the Oracle Files subscriber.
Log in to Oracle Files as orclguest (or as an existing Oracle Internet Directory user).
See "Setting Up Oracle Files Runtime" for more information about post-configuration tasks. See "Additional Post-Configuration Tasks" for additional post-configuration tasks.
The following describes security considerations for the protocols used to access Oracle Files.
FTP and AFP protocols send unencrypted user passwords across the network.
This is the defined behavior of these industry-standard protocols. Oracle has no control over this behavior, and it does not represent a defect in Oracle software. Sites unwilling to accept this behavior should either a) disable these protocols; or b) configure Oracle Files to use Oracle Files-specific user passwords for these protocols, so that users' Oracle9iAS Single Sign-On passwords are not compromised if FTP or AFP passwords are compromised.
To set Oracle Files-specific passwords, use the Protocol Access page in Oracle Files. See the Oracle Files online help for details.
The HTTP/DAV protocol allows both "basic" (unencrypted) and "digest" (encrypted) authentication.
"Basic" authentication sends unencrypted user passwords across the network unless HTTP/DAV uses SSL (Secure Sockets Layer). Apache configuration (performed separately from Oracle Files configuration) determines whether or not HTTP/DAV uses SSL. Sites concerned about HTTP/DAV "basic" authentication should configure Apache to use SSL.
The HTTP/DAV, FTP, SMB, AFP, NTFS, and NFS protocols do not encrypt the network channel by default.
Files transferred using these protocols are susceptible to interception. This is the defined behavior of these protocols. Oracle has no control over this behavior and it does not represent a defect in Oracle software. Sites unwilling to accept this behavior should disable these protocols and configure Apache to use SSL (HTTP/DAV only).
If authentication is performed using the Oracle Files Web User Interface HTML form, instead of Oracle9iAS Single Sign-On, unencrypted passwords are transmitted over the network unless Apache is configured to use SSL.
To administer Oracle Files using Oracle Enterprise Manager, a user authenticates using an HTML form. Unless Oracle Enterprise Manager is configured for SSL, unencrypted passwords are transmitted over the network.
By default, JDBC does not encrypt network connections between Oracle Files processes and the Oracle9i database. This means that passwords and files being transferred are susceptible to interception. Either a) secure the network connection between the middle tier machines running Oracle Files (if any), or b) use Oracle Advanced Security to encrypt these connections.
When configuring Oracle Files to use Oracle Internet Directory for user authentication, the administrator must choose whether or not to use SSL for connections between Oracle Files and Oracle Internet Directory. If SSL is not used, unencrypted passwords can be sent over network connections between Oracle Files processes and Oracle Internet Directory. Either a) secure the network connection between Oracle Files and Oracle Internet Directory or b) use SSL.
The Oracle Files configuration assistant starts automatically if you chose to configure Oracle Files as part of the installation process and guides you through the process of identifying the Oracle database to use for the Oracle Files schema and various other configuration tasks.
Before you configure Oracle Files, there are a number of preconfiguration tasks you might want to complete, depending on your planned deployment. To perform any of these tasks, either deselect the Oracle Files check box in the Oracle Universal Installer, which stops the Oracle Files configuration assistant from starting, or cancel the Oracle Files configuration assistant when it starts.
After performing the desired preconfiguration task(s), you can then run the Oracle Files configuration assistant again and configure Oracle Files.
This section contains these topics:
Table 14-1 lists recommended and optional preconfiguration tasks and provides information to help you determine whether or not a task is necessary to your deployment of Oracle Files.
Table 14-1 Optional Preconfiguration Tasks for Oracle Files
| Optional Preconfiguration Task | Purpose |
|---|---|
| "Create Custom Tablespaces (Recommended)"
Steps for this task begin |
For a production environment, Oracle recommends creating custom tablespaces for the various tables and indexes that comprise the system.
If you choose to create custom tablespaces, you must do so before configuring Oracle Files. You cannot use custom tablespaces that you create after configuring Oracle Files. |
| "Set Up Oracle Files to Use Real Applications Clusters Database (Optional)"
Steps for this task begin |
If you know that you want to use a Real Application Clusters database with your initial deployment of Oracle Files, it is recommended that you perform this preconfiguration task prior to configuring Oracle Files. |
Table 14-2 lists additional configuration and usage information for Oracle Files.
Table 14-2 Important Information for Configuring and Running Oracle Files
| Topic | Location |
|---|---|
| Creating users in Oracle Internet Directory | "Creating Users in Oracle Internet Directory" |
| Provisioning users in Oracle Files | "Creating Users in Oracle Internet Directory", and Oracle Files Administrator's Guide |
| Integrating Oracle Workflow With Oracle Files | "Integrating Oracle Workflow with Oracle Files (Optional)" |
| Oracle Files configuration tasks involving Oracle Enterprise Manager | Oracle Files Administrator's Guide |
| Oracle Files Site Administrator and Subscriber Administrator information | "Creating the Oracle Files Subscriber"; Oracle Files Administrator's Guide and Oracle Files online help |
| Configuring the NFS Server | Oracle Files Administrator's Guide |
| Installing the Oracle FileSync client | Oracle Files Administrator's Guide |
| Other client access paths and software | Oracle Files Administrator's Guide |
| Creating a Return to Portal link | "Adding the Return to Portal Link in the Oracle Files Web UI (Required)" |
| Setting up the NTFS server | "Configuring the NTFS Protocol Server (Optional)" |
| Enabling Windows users to map Oracle Files as network drives | "Enabling Windows Users to Map Oracle Files as Network Drives (Optional)" |
During Oracle Files configuration, you must select whether to store all schema objects in the USERS tablespace, or in custom tablespaces. For a production environment, the USERS tablespace is not optimal. Oracle recommends creating custom tablespaces for the various tables and indexes that comprise the system (see Table 14-3) before attempting to configure Oracle Files.
To create custom tablespaces for Oracle Files, Oracle recommends that you create tablespaces as locally managed tablespaces.
Locally managed tablespaces track all extent information in the tablespace itself, using bitmaps, resulting in simplified space allocation, ease of management, and performance benefits.
Locally managed tablespaces have been available since Oracle8i, and beginning with the Oracle9i Database Server, locally managed is the default for all non-SYSTEM permanent tablespaces whenever the type of extent management is not explicitly specified.
An example of the SQL syntax is:
CREATE TABLESPACE "tbspname"
LOGGING
DATAFILE 'D:\oradata\sidname\tbspname_01.dbf' SIZE 50M EXTENT
MANAGEMENT LOCAL
In this example, the EXTENT MANAGEMENT LOCAL clause is extraneous, since this is the default, but the full syntax is shown to highlight the fact that you need not provide segment, extent, and other sizing parameters.
If you create locally managed custom tablespaces, the default options are recommended. Specifically, be aware that you should not specify automatic segment-space management for the tablespaces, because almost all Oracle Files data is stored as LOBs, and AUTO SEGMENT SPACE MANAGEMENT does not support LOBs. (The default segment-space management type is MANUAL. By default, locally managed tablespaces are created correctly for use with Oracle Files.)
Create custom tablespaces on disk storage appropriate for your implementation. See the Oracle9i Database Performance Tuning Guide and Reference for more information.
Table 14-3 contains additional information about custom tablespaces. This table can be used to note the names and specifics of any custom tablespaces you create.
For more information about creating tablespaces and about locally managed tablespaces, see the Oracle9i Database Administrator's Guide, Volume 1.
Table 14-3 Custom Tablespace Definitions for Oracle Files
You can choose to run Oracle Files against a Real Application Clusters database at any time, either preconfiguration or post-configuration.
However, if you know that you want to point to a Real Application Clusters database for your initial Oracle Files deployment, performing the following preconfiguration steps enables you to specify a Real Application Clusters database during the Oracle Files configuration process. Note that there are additional post-configuration tasks that must also be completed.
|
Important: In order to use Real Application Clusters, configuration of Oracle Files must be performed against a specific node in the target Real Application Clusters configuration, and this node must have load balancing disabled during the Oracle Files configuration process. |
Set the following system parameter in the Real Application Clusters database:
MAX_COMMIT_PROPAGATION_DELAY=1
Ensure that the JOB_QUEUE_PROCESSES parameter is set to a value of 10 or higher.
Make a TNS entry in the tnsnames.ora file for load balancing and connection failover options in each Oracle home used by Oracle Files. Please see Oracle9i Real Application Clusters Administration for more information on making a TNS entry for these options.
Configure Oracle Files, specifying the name of the Real Application Clusters database on the Database Selection screen of the Oracle Files configuration assistant.
Perform required post-configuration steps.
See "Post-Configuration Steps for Using Oracle Files with a Real Application Clusters Database (Optional)" for details.
The Oracle Files configuration assistant is started automatically by the Oracle Universal Installer, and guides you through the configuration options listed in Table 14-4. The Oracle Files configuration assistant always begins with the Oracle Files CA - Welcome screen.
Using the Oracle Files configuration assistant, make your choices on each screen and click Next to continue. You can click Cancel to stop the assistant and configure Oracle Files at a later time by executing ifsca.bat from the following location:
%ORACLE_HOME%\ifs\files\bin
Table 14-4 describes the types of configurations you can perform:
Table 14-4 Configuration Assistant Options
| Configuration Type | Description | See Also... |
|---|---|---|
| Creating a New Oracle Files Domain |
Creates a new Oracle Files schema in the database. Optionally configures the software required to include the computer as a middle tier in the domain. | "Creating a New Oracle Files Domain" |
| Setting Up a Computer to Use an Existing Domain |
Configures Oracle Files software on the system for integration with an existing domain. Select this option if you are adding additional middle tiers. | "Setting Up a Computer to Use an Existing Domain" |
To monitor the Oracle Files configuration assistant as it progresses, you can view the log as it is being written to the following file:
%ORACLE_HOME%\ifs\files\log\FilesConfig.log
These instructions guide you through the process of configuring the Oracle Files domain controller computer, which is typically the first computer in the domain that you are configuring.
The instructions begin from the Oracle Files configuration assistant Welcome screen.
Click Next.
The Domain Operation screen displays.
Select the Create a new Oracle Files domain option.
|
Important: If you upgraded your Oracle Files schema from Oracle Collaboration Suite Release 1 (9.0.3) to Oracle Collaboration Suite Release 2 (9.0.4.1.1), you must choose Set up this computer to use an existing Oracle Files domain on the Domain Operation screen, and reference the instructions for "Setting Up a Computer to Use an Existing Domain". |
Click Next.
The Database Selection screen displays.
Enter the name of the host on which the database is running, the listener port number, the database service name, and the password for the database SYS user account.
Click Next.
The Database Login Verifications message box displays while the CLASSPATH, database connection to the Oracle9i database, initialization parameters, Oracle JServer installation, and other important requirements are verified.
If an error occurs (for example, if JServer is not installed in the database, you see an error message related to the DBMS_JAVA package), you must cancel the Oracle Files configuration process, fix the error, then restart the Oracle Files configuration assistant by executing ifsca.bat from the following location:
%ORACLE_HOME%\ifs\files\bin
The Oracle Files configuration assistant attempts to make a connection as SYS AS SYSDBA using a database string, and therefore needs the database to be configured with a password file. If the following error message displays, then it is likely due to a missing password file on the database server:
Invalid password for Oracle user SYS
|
See Also: Oracle9i Database Administrator's Guide for more information about password file administration. |
If additional errors occur, more information on why verification failed can be found in the FilesConfig.log file at the following location:
%ORACLE_HOME%\ifs\files\log\FilesConfig.log
The Schema Name screen displays when the verification process completes.
Enter a name to use for the Oracle Files schema. You must also provide a password for the schema. Enter the password in both fields to confirm.
Click Next.
The Oracle Files configuration assistant checks to see if the schema name exists in the database. If it does exist, or if related schema names based on this schema name exist, a message box displays requesting further clarification.
In this message box:
Clicking No returns you to the Schema Name screen, where you can enter a new name for the schema.
Clicking Yes drops this schema and all related objects from the database, such as tables and views, and create a new schema.
|
Caution: Do not click Yes unless you are sure you want to drop this schema and all related objects from the database, and create a new schema. If you are upgrading Oracle Files, exit from the Configuration Assistant and runocsua.bat. Follow the instructions in "Setting Up a Computer to Use an Existing Domain". |
The Tablespaces screen displays after you close the message box.
Select one of the following options:
Select Use the USERS tablespace for all Oracle Files data if you have not created custom tablespaces for Oracle Files content.
|
Important: Oracle corporation recommends that you create custom tablespaces for Oracle Files if you are configuring a production system. Create custom tablespaces as a preconfiguration step. See "Create Custom Tablespaces (Recommended)" for more information. |
Select Specify a tablespace for each data type and choose the tablespaces you want to use for each type of content from the drop-down lists if you have created tablespaces specifically for Oracle Files content. The tablespaces must exist in order to select them for each data type; the Oracle Files configuration assistant does not create them.
Click Next. The Character Set and Language screen displays.
Select the default character set and indexing language to use when storing documents in Oracle Files. The document character set defaults are used by client applications that do not specify a language or character set for documents being transferred to Oracle Files. The default character set is also used by non-Unicode enabled protocols, such as FTP and WebDAV, to determine the character set for these protocol servers to use.
Oracle Corporation recommends setting the character set to the character set used by the majority of users in your Oracle Files domain.
|
See Also: "Multi_Lexer" in Oracle Text Reference for more information |
Click Next.
The Default Port Numbers screen displays. The default port number settings are stored as an object for use by all middle tier computers that use the Oracle Files schema. After configuration of Oracle Files is complete, to change the configuration on any single middle tier computer, you must use the Enterprise Manager Web Site.
Change any of the port numbers as needed.
If you change the main port for the NFS protocol server, you must also change the mount server port to a number other than 0. A value of 0 indicates that the mount server port number should be dynamically allocated by the port mapper, and should only be used when the NFS protocol server is on the standard NFS port number 2049.
|
See Also: Oracle Files Administrator's Guide for detailed information about setting up the NFS protocol server |
Click Next.
The Website Information screen displays.
Enter the following information:
HTTP Host Name: Enter the fully-qualified host name and port number of the computer through which you want the domain to provide HTTP listener services. This information should match the values you entered during Oracle Collaboration Suite middle-tier installation.
HTTP Port: Enter a value for the HTTP port. Port information can be found in the following file:
%ORACLE_HOME%\install\portlist.ini
For example:
4443: Enter this value if you have configured SSL and are not using Oracle9iAS Web Cache.
4444: Enter this value if you have configured SSL and are using Oracle9iAS Web Cache.
7777: Enter this value if you have not configured SSL and are not using Oracle9iAS Web Cache.
7778: Enter this value if you have not configured SSL and are using Oracle9iAS Web Cache.
Uses SSL: Select this only if you have configured SSL on that computer.
|
Note: If you have a load balancer in front of your middle-tiers, then the hostname and port number should match that of the load balancer. |
|
See Also: Oracle9i Application Server Security Guide for detailed information about using SSL. |
Click Next.
The SMTP Information screen displays.
Enter the e-mail server information. This can be any valid SMTP server name. Enter the full host name of the SMTP server, in the form hostname.domain. Alternatively, you can enter the IP address of the SMTP server.
This information is used to send e-mail to the Subscriber Administrator regarding their respective passwords and to users regarding Oracle Files account provisioning.
|
Important: This information must be correct in order for the Subscriber Administrator to receive a password and for users to be notified when their accounts are provisioned. If the information is not correct, the Subscriber Administrator cannot log in to Oracle Files and users will not know when their accounts are provisioned. |
|
Note: If you need to change this information after configuring Oracle Files, you must:
|
Click Next.
The Administrator Information screen displays.
Enter the fully-qualified e-mail address to use for sending notifications and other messages to the Oracle Files site_admin user.
Click Next.
The Users screen displays. The Oracle Files configuration assistant creates three new users: system, guest, and site_admin. The Site Administrator is used to create the Subscriber in Oracle Files.
Assign passwords to each of the default users.
The site_admin user is necessary for creating the Oracle Files subscriber post-configuration.
Click Next.
The Oracle Internet Directory Login screen displays.
Enter the login information for the Oracle Internet Directory instance that you want to use for credential management. Enter the following information:
Server: Enter the fully-qualified host name for the computer running Oracle Internet Directory.
Port: Enter the port number where the Oracle Internet Directory server is listening.
Typically, the port number is 389. If port 389 is unavailable during the installation, port 4032 is used.
If you have SSL-enabled Oracle Internet Directory, select Uses SSL and change the port number. Typically, the port number for SSL-enabled Oracle Internet Directory is 636 or 4031.
|
See Also: Oracle Internet Directory Administrator's Guide for detailed information about setting up Oracle Internet Directory for use with SSL |
Super User: Enter the Oracle Internet Directory super user name.
The default Oracle Internet Directory super user name is cn=orcladmin.
Super User Password: Enter the Oracle Internet Directory super user password.
The password is whatever was entered when Oracle Internet Directory was installed.
Root Oracle Context: Enter the root Oracle Context.
The default Oracle Internet Directory root Oracle Context is set to cn=OracleContext. Typically, you can leave this unchanged. If the Oracle Internet Directory administrator changed the root context, you must enter the correct value. The concept of a root context is specific to LDAP directory services.
Click Next.
The Set Up Local Machine screen displays.
Select one of the following options:
Select Yes to create the Oracle Files schema and configure this host to run a domain controller, node, or HTTP node.
Select No to create the new schema without configuring this host.
Click Next.
The Domain Components screen displays.
Enter the fully qualified host name that you want to use for Oracle Files. If the computer contains multiple network interface cards (NICs), enter the IP address of the host computer.
Select Run Domain Controller on this computer and all other processes that you want to configure for the domain. By default, the following processes are selected on this screen:
Run Domain Controller on this computer configures the Oracle Files Domain Controller process. Only one computer should run this process.
Run a Node on this computer configures an Oracle Files node to run on this computer. Protocol servers and agents run on this node.
Run an HTTP Node on this computer configures an HTTP node to run the Oracle Files DAV server for HTTP and WebDAV access on this computer.
Click Next.
The Node Configuration screen displays. This screen lists all the protocol servers and agents that you can choose to run in the domain:
Node Name is the name by which you want the node to be known. It can include the name of the computer (host name), but it need not. The name must be unique across all of the nodes on this domain.
Run Oracle Files Agents configures all the Oracle Files system agents to run on this computer. Note that agents run on only one node in the domain. If agents are already configured to run on another node, this box must be unchecked.
Run Protocol Servers configures the Oracle Files protocol servers to run on this computer. Protocol Servers include FTP, AFP, NFS, and NTFS.
|
See Also: Chapter 1, "Oracle Files Concepts" in Oracle Files Administrator's Guide |
Enter a node name and configure protocol servers and agents as needed.
Click Next.
The HTTP Node Configuration screen displays, if you selected Run an HTTP Node on this computer on the Domain Components screen. This screen enables you to provide a name for the HTTP Node. Continue to step 32.
Otherwise, the Summary screen displays. Continue to step 34.
Enter the name for the HTTP Node.
HTTP Node Name is the name by which you want the HTTP node to be known. It can include the name of the computer (host name), but this is not a requirement. The name must be unique across all of the nodes on this domain.
Click Next.
The Summary screen displays. The Oracle Files configuration assistant now has all the information needed to create a new Oracle Files schema and configure the node and other processes. Note the name and location of the log file and any other important information on this screen.
Click Configure to execute the configuration process.
A progress window displays. If an error occurs, check the following log file for more information:
%ORACLE_HOME%\ifs\files\log\FilesConfig.log
When the process is complete, a message informs you that the configuration was successful. Click OK to close the message. Oracle Files and the Oracle Enterprise Manager Web Site are integrated automatically.
If the Oracle Files configuration assistant was started by Oracle Universal Installer, then any remaining configuration tools are run.
These instructions guide you through the process of setting up a computer to use an existing domain. Perform these steps if you upgrade your Oracle Files schema from Oracle Collaboration Suite Release 1 (9.0.3) to Oracle Collaboration Suite Release 2 (9.0.4.1.1), or if you want to add additional Oracle Collaboration Suite middle tiers for your existing Oracle Files domain.
The instructions begin from the Oracle Files configuration assistant Welcome screen.
Click Next to begin the configuration process.
The Domain Operation screen displays
Select the Set up this computer to use an existing Oracle Files domain option and click Next.
The Database Selection screen displays.
Enter the name of the host on which the database is running (database host name), the listener port number, the database service name, and the password for the database SYS user account.
Click Next.
The Database Login Verifications message box displays as the CLASSPATH, database connection to the Oracle database, initialization parameters, Oracle JServer installation, and other important requirements are verified.
If an error occurs, you must correct the problem before configuration can continue. For example, if JServer is not installed in the database, you see an error message related to the DBMS_JAVA package.
If additional errors occur, more information on why verification failed can be found in the FilesConfig.log file at the following location:
%ORACLE_HOME%\ifs\files\log\FilesConfig.log
The Schema Name screen displays when the verification process completes.
Select the schema name of the existing Oracle Files domain from the list and enter the schema password.
|
Important: If you select the name of an existing Oracle Files schema from Oracle Collaboration Suite Release 1 (9.0.3), and you have not previously upgraded this schema to Oracle Collaboration Suite Release 2 (9.0.4.1.1), a dialog box displays with the following text:"You have selected an Oracle Collaboration Suite Release 1 (9.0.3) Files schema which must first be upgraded to Oracle Collaboration Suite Release 2 (9.0.4.1.1) Files schema before configuring Oracle Files against it. To perform this upgrade, cancel the configuration process and run the Oracle Collaboration Suite Upgrade Assistant. You can also choose another schema by entering new schema information in the Oracle Files Configuration Assistant." For step-by-step information about upgrading your Oracle Files schema from Oracle Collaboration Suite Release 1 (9.0.3) to Oracle Collaboration Suite Release 2 (9.0.4.1.1), see "Oracle Files Post-Upgrade Tasks". |
Click Next.
The Domain Components screen displays after the database connection and schema are verified.
Enter the host name that you want to use for Oracle Files. If the computer contains multiple network interface cards (NICs), enter the IP address of the host computer.
Select Run Domain Controller on this computer and all other processes that you want to configure to run on this computer. By default, the following processes are selected:
Run Domain Controller on this computer configures the Oracle Files Domain Controller process. Only one computer should run this process. To reuse an existing schema, uncheck this box. If a Domain Controller is already running on a different node, leave this box checked ONLY if you want to move the Domain Controller to this middle tier.
Run a Node on this computer configures an Oracle Files node to run on this computer. Select this option if you want to run protocol servers or agents on this middle tier.
Run an HTTP Node on this computer configures an HTTP node to run the Oracle Files DAV server for HTTP and WebDAV access on this computer.
Click Next.
The Node Configuration screen displays.
The Node Configuration screen lists all the protocol servers and agents that you can choose to run in the domain:
Node Name is the name by which you want the node to be known. It can include the name of the computer (host name), but it need not. Use any string that makes sense to you.
Run Oracle Files Agents configures all the Oracle Files system agents to run on this computer. Note that agents run on only one node in the domain. If agents are already configured to run on another node, this box must be unchecked. If this box is checked, it inactivates agents running on other nodes and enables them on this node. If you are upgrading an existing Oracle Files schema, this box must be unchecked.
Run Protocol Servers configures the Oracle Files protocol servers to run on this computer. Protocol Servers include FTP, AFP, NFS, and NTFS.
|
See Also: "Oracle Files Concepts" in Chapter 1 of Oracle Files Administrator's Guide |
Enter a node name and configure protocol servers and agents as needed.
Click Next.
The HTTP Node Configuration screen displays if you selected Run an HTTP Node on this computer on the Domain Components screen. This screen enables you to provide a name for the HTTP Node. Continue to step 12.
Otherwise, the Summary screen displays. Continue to step 14.
Enter the name for the HTTP Node.
HTTP Node Name is the name by which you want the HTTP node to be known. It can include the name of the computer (host name), but it need not. Use any string that makes sense to you.
Click Next.
The Summary screen displays. The Oracle Files configuration assistant now has all the information needed to configure the computer. Note the name and location of the log file and any other important information on this screen.
Click Configure to execute the configuration process.
A progress window displays. If an error occurs, check the following log file for more information:
%ORACLE_HOME%\ifs\files\log\FilesConfig.log
When the process completes, a message informs you that the initial configuration was successful. Click OK to close the message.
If the Oracle Files configuration assistant was started by the Oracle Universal Installer, then the remaining configuration tools are started.
|
Note: After configuring Oracle Files to reuse a previously created schema, you must edit the following Oracle Files Base Server Configuration properties so that they point to the appropriate computer:IFS.SERVER.APPLICATION.UIX.ApplicationHost IFS.SERVER.APPLICATION.UIX.ApplicationPort Alternatively, you can override these properties in the server-specific configurations. |
You can configure the Oracle Files domain non-interactively by passing a response file containing all the configuration settings to the Oracle Files configuration assistant as a parameter at the command line. The location of the response file is:
%ORACLE_HOME%\ifs\files\settings\silentconfig.properties
The file contains instructions about how to modify and use it. Modify the response file to meet your specific needs.
Open the silentconfig.properties file in a text editor.
Make any required changes to the settings in the file, and close the file when you are finished.
The file itself contains instructions about how to modify and use it. Modify the response file to meet your specific needs. For example, you can specify a name for the schema, or disable the Run Domain Controller, if you are installing and configuring an additional middle-tier machine to work with an existing instance.
Run the Oracle Files configuration assistant using your modified response file by entering the following two commands:
cd %ORACLE_HOME%\ifs\files\bin ifsca -file %ORACLE_HOME%\ifs\files\settings\silentconfig.properties -silent
Oracle Files is configured on the computer according to the specifications defined in the response file. If an error occurs, check the following log file for more information:
%ORACLE_HOME%\ifs\files\log\FilesConfig.log
|
Note: The response file contains sensitive information, such as passwords. After you have used the response file to configure Oracle Files, you should delete password information from file. |
You must perform the following tasks to set up Oracle Files for runtime, and to ensure that your system is operational and secure:
You must grant the Windows NT, 2000, and 2003 Administrator account (or other account that you are using to install and configure Oracle Collaboration Suite) the Logon as Batch Job privilege in order for the local user to be able to start the Domain Controller and Nodes from the Oracle Enterprise Manager Web Site:
These instructions assume that you are logged on to the Windows NT or Windows 2000 computer as the Administrator (or other user account with administration privileges).
Select Start > Programs > Administrative Tools (Common) > User Manager.
User Manager (or User Manager for Domains on Windows NT Server) appears.
Select Policies > User Rights.
The User Rights Policy screen appears.
Select Show Advanced User Rights, located in the lower-left corner of the display.
Select Logon as Batch Job from the drop-down menu of rights.
Click Add.
Add the user account that was used to install Oracle Collaboration Suite. This is typically the Administrator user or another user account from the Administrators group.
Click OK to close the dialog.
Click OK to save the change and exit the User Rights Policy dialog.
Select Start > Programs > Administrative Tools > Local Security Policy.
The Local Security Settings window appears.
From the tree on the left side pane, open Local Policies and select User Rights Assignment.
A list of policies appears in the right side panel.
Select Logon as Batch Job.
Click Add.
Add the user account that was used to install Oracle Collaboration Suite. This is typically the Administrator user or another user account from the Administrators group.
Click OK to close the dialog.
Click OK to save your changes and exit the Local Security Settings window.
These instructions assume that Oracle Files has been installed and configured, and that the database and listener are running.
Oracle Files uses the Oracle9iAS Containers for J2EE (OC4J) component of the Oracle Collaboration Suite Infrastructure to support the DAV Servlet, which is deployed to OC4J automatically during the configuration process.
Verify that Oracle Enterprise Manager Web Site is running by using the following command:
%ORACLE_HOME%\bin\emctl status
From a Web browser on the server computer or from another computer on the network, access the URL to connect to the Oracle Enterprise Manager Web Site on the computer where the Oracle Files domain controller is configured:
http://hostname:port
The hostname should be a fully qualified domain name. The port is typically 1810.
A User name and Password Required or Enter Network Password prompt displays.
Enter ias_admin as the user name with the appropriate password for the Oracle Collaboration Suite middle-tier.
The Web page displays a list of all Oracle Collaboration Suite Infrastructure components, or Targets, running on the specified host, as well as any Oracle Collaboration Suite-associated middle tiers.
Click the name of the Oracle Collaboration Suite instance that is hosting the Oracle Files software. If you are prompted for the Oracle Collaboration Suite instance user name and password again, enter ias_admin and the appropriate password to continue.
The Application Server page displays all of the system components running on the instance. The list should include the Oracle Files domain, which appears as a concatenation of iFS_ and the database instance's host name, port number, service name, and the name of the schema for Oracle Files. For example:
iFS_myMachineHostname.mycompany.com:1521:myDBServiceName:myFILESSchemaName
|
Note: Although you see Start and Stop buttons on this page, you cannot control Oracle Files from this page. The radio button is not active. |
Click the Oracle Files domain name link. On the subsequent page, click Start Local Components. A page prompting you for the host credential to start the Oracle Files node displays.
Enter the operating system account name and password for the computer. This is typically the Windows administrator user name and password, or the name and password of the user who installed Oracle Files.
Click OK.
If your Oracle Files domain comprises multiple nodes across multiple computers, repeat steps 1 through 7 of this section for each computer. You must enter the operating system account name and password on each computer running a node that you want to start.
Click the link that takes you back to the Application Server page.
Select OC4J_iFS_files and click Start or Restart.
Start the OC4J instance.
To start the OC4J service, select Start > Settings > Control Panel > Administrative Tools > Services. In the Services dialog, select the service Oracleinstance_nameProcessManager, and select Action > Start.
To start the OC4J instance from the command line, navigate to the %ORACLE_HOME%\opmn\bin directory and use the following command:
opmnctl startproc gid=OC4J_iFS_files
The Oracle Files domain starts. You must start the OC4J instance on every middle tier computer that is running the HTTP Node.
Check the status of the Oracle Files domain. To do this, run the ifsctl status -n command from the following location:
%ORACLE_HOME%\ifs\files\bin\
Check the log files to make sure the node and the HTTP node appear. The log files are located in the following directories:
%ORACLE_HOME%\ifs\files\log\ %ORACLE_HOME%\j2ee\OC4J_iFS_files\application-deployments\files \OC4J_iFS_files_default_island_1\
|
Note: Ensure that the SMTP server is running before creating a subscriber. The SMTP server must be running in order for the Subscriber administrator and users to receive e-mail regarding their respective passwords. |
In the following steps, you must log in to Oracle Files as the Site Administrator and create the Subscriber. You must create the Oracle Files subscriber in order for Oracle Internet Directory users to be able to log in to Oracle Files.
Go to:
http://http_host:port/files/app/AdminLogin
The http_host should be a fully qualified domain name. For example:
http://acme.us.oracle.com:7778/files/app/AdminLogin
The Administrator Login page displays.
Log in as site_admin and use the same site_admin password you used during configuration.
Click New Subscriber.
The Subscriber Name page displays. Note that the Subscriber Name is the default subscriber for the Oracle Internet Directory server. The Oracle Internet Directory server is the value entered in step 23 in the "Creating a New Oracle Files Domain" section during Oracle Files configuration.
Accept the defaults.
|
Important: Multiple subscribers are not currently supported due to Oracle9iAS Single Sign-On limitations. |
Click Next.
The Subscriber Information page displays.
Set the quota and maximum number of users. For example, 1 GB total quota, 10 MB quota for each user, and 10 MB quota for each Workspace.
Click Next.
The Create Subscriber Administrator Account page displays.
Enter the Subscriber Administrator user login ID. The e-mail address is where the subscriber's password is sent. Specify the Default User Account Settings and Default Workspace Settings.
Click Next.
The New Subscriber Confirmation page displays.
Review your information, then click Submit.
The Browse Subscribers page displays. You can see that the Subscriber has been created and the Subscriber's password has been automatically e-mailed.
To log in as the Subscriber Administrator, navigate to the following URL:
http://http_host:port/files/app/AdminLogin
The Administrator Login page displays.
Log in as subscriberadmin_user_login_ID/password using the subscriber user login ID that you entered when creating the subscriber in step 8 of this section, and the subscriber password that you received by e-mail.
Click the USERS tab to view the Users page. Refresh this page to see an updated list of Oracle Files users.
|
See Also: "Creating Users in Oracle Internet Directory" for more information about creating users in Oracle Files |
In order for users to access Oracle Files, they must first be created as users in Oracle Internet Directory, Oracle's LDAP server.
To create users in Oracle Internet Directory:
Make sure that the OC4J_DAS instance has been started on the Infrastructure host.
Connect to your infrastructure host, typically:
http://oidserver.us.oracle.com:7777/oiddas
The hostname should be a fully qualified domain name.
Log in as the Oracle Internet Directory Administrator (typically orcladmin).
Click the Directory tab.
Click Create.
The Create User page displays.
Fill in the fields. You must specify an e-mail address.
Select Oracle Collaboration Suite Users to add this user to the group.
Click Submit.
|
Caution: If you use spaces at the end of user names, or any of the following characters, the user is not provisioned from Oracle Internet Directory into Oracle Files: & ' % ? \ / + = ( ) * ^ , ; | ~ |
Once users are created in Oracle Internet Directory, and the Oracle Files Site Administrator has created the Oracle Files Subscriber Administrator, they are automatically provisioned in Oracle Files every 15 minutes (the default setting) by the FilesOidUserSynchronizationAgent.
Additionally, once a user has been created in Oracle Internet Directory, logging on to Oracle Files as that user immediately provisions the user in Oracle Files, irrespective of the time interval specified for the Agent (this feature is new in this release).
You can reset the default interval for auto-provisioning by the FilesOidUserSynchronizationAgent from 15 minutes to any interval of your choosing.
|
See Also: Oracle Files Administrator's Guide for information about how to change this default interval |
|
Note: Although Oracle Files supports multibyte character sets, some protocols, such as WebDAV, do not support multibyte user names. For this reason, when you create users for Oracle Files in Oracle Internet Directory, you should create the names using single-byte characters only. Users whose names are created with multibyte characters are unable to access content through Oracle Files protocol servers. Similarly, you should create user passwords in ASCII since the protocols only accept ASCII passwords.Users whose passwords are created with non-ASCII characters are unable to access content through the Oracle Files protocol servers. |
To access the protocol servers running on your Oracle Files Domain, each end user must perform the following steps:
Connect to the Protocol Access page:
http://ocs_midtier_hostmachine:port/files/app/ProtocolAccess
The value supplied for ocs_midtier_hostmachine should be a fully qualified domain name. The value supplied for port should be the port number of the middle tier computer.
The Single Sign-On page displays.
Log in using the Oracle Internet Directory user and password.
The Protocol Access page displays.
Enter the Oracle9iAS Single Sign-On password and the Oracle Files-specific password and password confirmation to create these passwords for the user.
Click Continue to save.
Now that you have configured the Oracle Internet Directory user using the Protocol Access page, you can access the protocol servers that are running on your Oracle Files Domain.
|
Note: To access FTP and AFP, use the Oracle Files-specific password. To access NTFS, Oracle FileSync, WebFolders, or the Oracle Files Web interface, use the Oracle Internet Directory password. |
|
See Also: Oracle Files Administrator's Guide for more information about creating users and accessing protocol servers running on your Oracle Files Domain |
To validate that the domain and node started and the core Oracle Files components are working, perform the following steps:
Check the status of the Oracle Files domain. Run the ifsctl status -n command from the following location:
%ORACLE_HOME%\ifs\files\bin\
Check the HTTP log at the following location:
%ORACLE_HOME%\j2ee\OC4J_iFS_files\application-deployments\files \OC4J_iFS_files_default_island_1\application.log
If the HTTP log contains a "503 Service Temporarily Unavailable" message, attempt to connect to the system from another computer on the network.
Table 14-5 Basic Functionality
| Protocol or Server | Access Address or Method | Expected Result |
|---|---|---|
| HTTP |
http://ocs_middle_tier_host_ name:port_number/files/app |
Log in as a user created in the Oracle Internet Directory server. |
| NTFS | Map a network drive from Windows Explorer.
\\middle_tier_host_name\myhome |
A Windows file share appears. |
If you attempt to connect to the HTTP Web server and receive a 503 Service Temporarily Unavailable message, the HTTP node has not fully started. You must start the HTTP node (the OC4J instance).
To start the OC4J service, select Start > Settings > Control Panel > Administrative Tools > Services. In the Services dialog, select the service Oracleinstance_nameProcessManager, and select Action > Start (or Restart).
To start the OC4J instance from the command line, navigate to the %ORACLE_HOME%\opmn\bin directory and use the following command:
opmnctl restartproc gid=OC4J_iFS_files
Depending on your planned deployment, some or all of the following tasks are required after configuring Oracle Files.
Post-Configuration Steps for Using Oracle Files with a Real Application Clusters Database (Optional)
Adding the Return to Portal Link in the Oracle Files Web UI (Required)
Editing the Oracle Internet Directory Return Query Limit (Optional)
Enabling Windows Users to Map Oracle Files as Network Drives (Optional)
If you want to integrate Oracle Workflow with Oracle Files, perform the following categories of tasks, in the order given:
Configure net service names using Oracle Net Configuration Assistant as follows:
Run the Oracle Net Configuration Assistant by executing the NetCA utility. Select Start > Programs > Oracle - ORACLE_HOME > Configuration and Migration Tool > Net Configuration Assistant.
Oracle_Home is the name of the Oracle home that you specified when installing Oracle Collaboration Suite.
The Welcome screen displays.
Select Net Service Name configuration, and click Next.
The Net Service Name Configuration screen displays.
Click Add, and then click Next.
The Net Service Name Configuration, Database Version screen displays.
Select Oracle8i or later database or service.
Click Next.
The Service Name screen displays. Enter a Service Name for the database instance, such as db1.us.acme.com.
Click Next.
The Select Protocols screen displays.
Select TCP (default).
Click Next.
The TCP/IP Protocol screen displays. Enter values for the DB Hostname and DB Port. The default value for the database port is 1521.
Click Next.
The Test screen displays.
Click Yes to perform a test.
The Connecting screen displays with the result of the test connection. The test attempts to connect using the default user scott. Because the user scott is locked during database creation, the test connection might fail. If the test connection fails, the Oracle Net configuration assistant returns to the Service Name screen. Change the user to system, enter the values for your database and perform the test connection again.
If the Connection screen returns the result OK, click Next.
The Net Service Name screen displays. Enter a service name for this database connection in the TNS Alias Name field, such as db1.
Click Next.
The Net Service Name screen displays. Accept the default value of No.
Click Next.
The NetCA Done screen displays.
Click Next.
The Summary screen displays.
Click Finish.
The steps detailed in this section must be performed to properly configure Oracle Workflow for use with Oracle Files.
Configuring Oracle Workflow primarily involves setting up the Oracle Workflow schema, and only needs to be done for the first middle tier, not for any additional middle tiers that are added.
|
Note: The Oracle Workflow scripts automatically set the Oracle Workflow administrator as theorcladmin user. |
Run Oracle Workflow Configuration Assistant in the first middle tier computer by executing the following script:
%ORACLE_HOME%\wf\install\wfinstall.bat
The Oracle Workflow Configuration Assistant displays.
Enter the user information listed in Table 14-6:
Table 14-6 Oracle Workflow Configuration Assistant Values
| Field | Value |
|---|---|
| Workflow Account | The user name of your Oracle Workflow database account. The default Workflow account is OWF_MGR. If you are creating more than one Oracle Workflow instance on the same information storage database, enter a descriptive name for this account. |
| Workflow Password | The password for your Oracle Workflow database account. |
SYS Password |
Enter the SYS password for the database in which you are creating the Oracle Workflow account. See your Oracle DBA if you need more information. |
SYSTEM Password |
Enter your SYSTEM password for the database in which you are creating the Oracle Workflow account. See your Oracle DBA if you need more information. |
| Install Option | Select Install to perform a fresh installation of Oracle Workflow. |
| Language Selection | If you selected the Add language install option, select the language abbreviation for the language you want to add. Otherwise, accept the default.
See Also: Table 14–8, " Language Codes" for a list of standard language abbreviations |
| Connect Method | Select Local to connect to a local database using the Oracle SID, or Remote to connect to a remote database through Oracle Net.
Select Remote if you performed the steps listed in "Configuring Net Service Names". |
| Connect String | If you select the Remote connect method, enter the service name that you specified in step 11 of "Configuring Net Service Names" for the remote database.
Important: To ensure that the Oracle Workflow schema is created on the same database where the Oracle Files schema is to be created, use the Oracle Collaboration Suite information store |
Click Submit to begin Oracle Workflow configuration.
When Oracle Workflow configuration is complete, a confirmation window displays.
Click OK.
Oracle Workflow configuration is now complete. You can check the status of the Oracle Workflow configuration by reviewing the workflow.log log file located in the following directory:
%ORACLE_HOME%\wf\install\
|
Important: Theworkflow.log file produced during installation and configuration of Oracle Workflow can contain sensitive information. To protect this sensitive information, delete this file after the installation is complete or change the permissions for the file so that only authorized administrators can access it. |
Before integrating Oracle Workflow with the Oracle Files schema, you must apply the following patches:
ARU 4920260 (for issue 2183448)
ARU 4909037 (for issue 3180908)
ARU 5126488 (for issue 3279810)
Download the patches from http://metalink.oracle.com.
To integrate Oracle Workflow with the Oracle Files schema, perform the following steps. These steps assume you have already configured Oracle Workflow per the instructions:
If you are integrating Oracle Files with Oracle Workflow in a locale other than English, you must change the NLS_LANG environment variable to the English locale before running the ifswfsetup script. Type the following at a command prompt:
|
Note: Before changing the value of NLS_LANG, use the commandset NLS_LANG at a command prompt and record the current value of the environment variable. |
SET NLS_LANG = american_america.we8iso8859p1
Once you have successfully configured Oracle Workflow, edit the ifswfsetup.properties file using the values provided in Table 14-7. This table describes the parameters that are used by the ifswfsetup script. Edit these parameters based on your requirements. These edits are mandatory if you want to integrate Oracle Workflow with Oracle Files. The ifswfsetup.properties file is located at:
%ORACLE_HOME%\ifs\files\settings
|
Important: Back up theifswfsetup.properties file before modifying it. Do not edit any parameters other than the ones listed in Table 14-7. |
Table 14-7 Values for ifswfsetup.properties File
| Field # and Name | Structure | ExampleFoot 1 |
|---|---|---|
| (1) Oracle home |
ORACLE_HOME=ORACLE_HOME |
ORACLE_HOME=D:\ocsmid |
| (2) Database Host |
DB_HOST_NAME=dbhost.us.oracle.com |
DB_HOST_NAME=acme.us.oracle.com |
| (3) Database Port |
DB_LISTENER_PORT=port_number |
DB_LISTENER_PORT=1521 |
| (4) Database Service Name |
DB_SERVICE_NAME=db_service_name |
DB_SERVICE_NAME=acme9i |
| (5) Database TNS Alias Name |
DB_TNS_ALIAS=db_tns_aliasname |
DB_TNS_ALIAS=my_files_instanceThis is the database service that you are using for Oracle Files, created with the Oracle Net Configuration Assistant. See "Configuring Net Service Names" for more information. |
| (6) Database SID |
DB_SID=db_sid |
DB_SID=my_files_sid |
| (7) Oracle Files Schema Name |
IFS_SCHEMA_NAME=ifssys |
IFS_SCHEMA_NAME=ifssys |
| (8) Oracle Workflow Schema Name |
IFS_WORKFLOW_SCHEMA_NAME=workflow _schema_name |
IFS_WORKFLOW_SCHEMA_NAME=owf_mgr |
| (9) Oracle Workflow URL |
WF_URL=http://midtier:port_number |
WF_URL=http:// midtier.us.oracle.com:7777 |
| (10) Oracle LDAP Host |
OID_HOST_NAME= ldaphost.us.oracle.com |
OID_HOST_NAME= oidserver.us.oracle.com |
| (11) Oracle LDAP Port |
OID_PORT=port_number |
OID_PORT=4032 |
| (12) Oracle LDAP Admin User Name |
OID_SUPER_USER_NAME=cn=orcladmin |
Enter the exact value specified in the Structure column. |
| (13) Oracle LDAP Changelog |
LDAP_CHANGELOG=cn=changelog |
Enter the exact value specified in the Structure column. |
| (14) Oracle LDAP Baselog |
LDAP_BASELOG= cn=Users,dc=us,dc=oracle,dc=com |
Values should match those specified for LDAP searchbase during Oracle Internet Directory configuration. |
| (15) Language Upload Script |
LANGONLY=false |
Enter either true or false. |
| (16) Language Files to Upload
See Table 14-8, "Language Codes" for a complete list of language codes. Multiple codes can be entered, separated by a comma. |
LANG=language_code |
LANG=When LANGONLY=false (see Field 15), this value should be left empty.
When |
| (17) OID Sync Interval |
INTERVAL=interval_duration |
INTERVAL=10Specifies, in minutes, how often an Oracle Internet Directory user is provisioned in Oracle Files. |
Save and exit from the ifswfsetup.properties file.
Execute the ifswfsetup script by entering the following two commands:
cd \ifs\files\bin ifswfsetup
This executes the script and creates the ifswfsetup.log log file in the following directory:
\ifs\files\log\
|
Important: Theifswsetup.properties file and the ifswfsetup.log file contain sensitive information. To protect this sensitive information, delete these files after the installation is complete or change the permissions for the files so that only authorized administrators can access them. |
|
Note: If you changed the value of NLS_LANG, you must use theset NLS_LANG command at a command prompt to set the value of the environment variable to its previous value. |
Enable additional languages in the Oracle Workflow schema, if necessary.
To enable additional languages in the Oracle Workflow schema, perform the following steps:
Edit the ifswfsetup.properties file (located at %ORACLE_HOME%\ifs\files\settings), as follows:
Field 15: Language Upload Script
LANGONLY=true
Field 16: Language Files to Upload
LANG=[Enter language codes from column 2 of Table 14-8 that match the languages that you want to upload to Oracle Workflow. Separate multiple language codes with a comma.]
If you want to enable all languages, use the following syntax:
LANG=all
When you have completed edits to the ifswfsetup.properties file, execute the ifswfsetup script by entering the following two commands:
cd \ifs\files\bin ifswfsetup.bat
This executes the script and creates the ifswfenablelang.log log file in the following directory:
\ifs\files\log\
|
Important: Theifswfenablelang.log file contains sensitive information. To protect this sensitive information, delete this file after the installation is complete or change the permissions for the file so that only authorized administrators can access it. |
Table 14-8 Language Codes
| Language | CodeFoot 1 |
|---|---|
| Danish | da |
| German | de |
| Greek | el |
| Spanish | es |
| Finnish | fi |
| French | fr |
| Italian | it |
| Japanese | ja |
| Korean | ko |
| Dutch | nl |
| Norwegian | no |
| Portuguese | pt |
| Brazilian Portuguese | pt_BR |
| Russian | ru |
| Swedish | sv |
| Turkish | tr |
| Simplified Chinese | zh_CN |
| Traditional Chinese | zh_TW |
ifswfsetup.properties file.The following tasks are required after configuring Oracle Files if you are using Oracle Files with a Real Application Clusters database.
In addition to the required preconfiguration tasks for setting up Oracle Files to use a Real Application Clusters database (see "Set Up Oracle Files to Use Real Applications Clusters Database (Optional)"), you must perform the following post-configuration steps:
On each middle tier, back up and then edit the registry.xml file (located in the \ifs\common\ directory) to add a DatabaseUrl entry.
You can add the DatabaseUrl entry anywhere under the <Instance> tag. In the following example, the entry is added directly under the tag. Note that the value for tnsentry should be the same as that specified in the Real Application Clusters pre-configuration steps.
For example:
<Instance> <DatabaseUrl>jdbc:oracle:oci8:@tnsentry</DatabaseUrl> <Domain>ifs://DBHOME:1521:dbservice:ifssys</Domain> <DomainType>files</DomainType> <Registered>1018925008096</Registered> <LastStarted>1028329087966</LastStarte>d <LastModified>1028330926700</LastModified> <Ports> </Instance>
Modify the IFS.SERVICE.JDBC.DatabaseUrl Service Configuration Property in the Service Configuration used for the system. Enter the same value specified in the DatabaseUrl specified in step 1 of this section:
jdbc:oracle:oci8:@tnsentry
You can view Service Configuration Properties through Oracle Enterprise Manager by navigating to http://hostname:1810 (where hostname is the computer where the Oracle Files domain controller is configured).
The property that shows your default service configuration is:
IFS.DOMAIN.LIBRARYOBJECT.SERVICECONFIGURATION.DefaultServiceConfiguration
Your default service configuration is one of the following:
SmallServiceConfiguration
MediumServiceConfiguration
LargeServiceConfiguration
|
Caution: Be sure to specify a correct value for the DatabaseUrl parameter. If you specify an incorrect value, Oracle Files processes cannot connect to the Oracle Files schema. |
If you have configured Oracle9iAS Portal, you can add a Return to Portal link that displays in the Oracle Files Web UI, so that you can navigate from Oracle Files to the Oracle Collaboration Suite Home page.
To add the Return to Portal link to the Oracle Files Web UI, perform the following steps:
Access the Oracle Enterprise Manager Web site by entering the following URL in a Web browser:
http://hostname:1810/
Log in as ias_admin, using the password you specified during installation, and click OK.
From the Oracle9iAS Home page, navigate to the Oracle Files top-level page by clicking on the Oracle Files domain link. For example:
iFS_dbhost.us.oracle.com:1521:ifsdbservice.us.oracle.com:FilesSchema
In the Configuration section, click Server Configurations
From the Server Configuration page, click FilesBaseServerConfiguration. The Edit page displays.
In the Properties section, select IFS.SERVER.APPLICATION.FILES.PortalUrl and click Edit.
Change the value to specify the Oracle Collaboration Suite Home page URL. For example:
http://hostname.us.foo.com:7777/pls/portal
Click OK on the Edit Properties page.
Click OK on the Edit Server page.
Return to the Oracle9iAS Home page.
Select OC4J_iFS_files and click Restart.
The Return to Portal link now displays in the Oracle Files Web UI. It also displays in the Federated Search pages.
If your Oracle Internet Directory server has more than 1000 Oracle Internet Directory user accounts, the following error message can occur in your node log when the Oracle Files OidUserSynchronizationAgent attempts to synchronize users from the Oracle Internet Directory server:
8/13/02 7:39 PM Files: [oidsync-2107123 OidUserSynchronizationAgent] Exception oracle.ifs.common.IfsException: IFS-12988: Count limit exceededUIDs
To avoid this error, complete the following steps before starting the Oracle Files OidUserSynchronizationAgent:
Run Oracle Directory Manager by selecting Start > Programs > Oracle9i Application Server - OCSMidtier_home > Integrated Management Tools > Oracle Directory Manager.
Log in to the infrastructure Oracle Internet Directory server using the Oracle Internet Directory administrator's user name and password.
Select the Oracle Internet Directory server into which you just logged in from the tree. The server is represented in the tree with the account name, Oracle Internet Directory host, and Oracle Internet Directory port. Oracle Directory Manager displays the properties of the Oracle Internet Directory server in the right part of the window.
Locate and change the value in the Query Entry Return Limit field so that it is greater than the number of Oracle Collaboration Suite users.
Click OK to save.
The NTFS protocol server creates a virtual disk drive on a Windows server which provides access to Oracle Files from the Window server's file system. This virtual disk drive can be shared using Windows network file sharing to provide Windows clients network access to files in Oracle Files (see "Enabling Windows Users to Map Oracle Files as Network Drives (Optional)" for more information).
The NTFS protocol server controls access from the Windows server by matching the Windows server user name to an Oracle Files user name. After Oracle Files is initially installed and started, a virtual disk is created and assigned the drive letter "O". Initially, no files are accessible on the "O" drive because all file access requires an authenticated user, and initially an Oracle Files installation does not have any users.
To access the "O" drive, you must provision an Oracle Files user with the same user name as the Windows server user (the "Windows server administrator") that is used to start Oracle Files. Once this Oracle Files user is provisioned, the Windows server administrator is able to access files on the "O" drive.
To provision an Oracle Files user, you must first create the user in Oracle Internet Directory. Once they are created in Oracle Internet Directory, they are automatically provisioned in Oracle Files by the FilesOidUserSynchronizationAgent. This agent runs by default every 15 minutes, but this default time period can be reset to run the agent more frequently. For more information about creating users in Oracle Internet Directory and automatically provisioning those users in Oracle Files, see "Creating Users in Oracle Internet Directory".
After the Oracle Files user has been created, verify that the Windows server administrator can access the "O" drive.
After running the Oracle Files Configuration Assistant, the Windows server administrator must perform the following steps in order to properly configure the NTFS protocol server:
Reboot to complete the installation of the Oracle Files NTFS driver.
Create an Oracle Files user in Oracle Internet Directory. This user must have the same name as a Windows user who is in the Windows Administrators group (the "Windows server administrator"), or this user cannot start the NTFS driver.
Start all Oracle Files servers by using ifsctl start in a command window. All the Oracle Files protocol servers and agents start up, although the NTFS server cannot yet be used to access Oracle Files.
Wait for the FilesOidUserSynchronizationAgent to provision the user created in Oracle Internet Directory as an Oracle Files user. By default, this process occurs every 15 minutes. For detailed information on how to change the default sync time to a shorter interval, see the Oracle Files Administrator's Guide.
Once the user has been provisioned, the "O" drive is accessible and the default mountpoints are created. If the mountpoints are not created, you can create them by restarting the NTFS server. Restart the Oracle Files NTFS server using the Oracle Enterprise Manager Web site. Alternatively, you can restart all Oracle Files servers using ifsctl stop and ifsctl start at a command line. The NTFS server can now be used to access Oracle Files.
By default, the NTFS protocol creates Windows network shares called MyHome and AllPublic for the root ("O:\") and AllPublic directories, respectively, on the "O" drive. These directories must be accessible to the local Windows server administrator in order for the network shares to be created. If these directories are not accessible to the Windows server administrator, the creation of these shares fails. After you have verified that you can access the "O" drive, restart the NTFS protocol server to create the default network shares. You can restart the server using Oracle Enterprise Manager Web site or you can stop and start all servers using ifsctl stop and ifsctl start.
By default, access to the "O" drive on the Windows server is based on the Windows user that was used to start the Oracle Files servers. The Windows user is mapped to an Oracle Files user of the same name. For example, if the Oracle Files servers are started by the Windows user Administrator, then access to the "O" drive is based on an Oracle Files user named Administrator.
You can change the default Oracle Files user that is used to access the "O" drive on the Windows server by setting a property in the NTFS server configuration. Edit the NTFS server configuration properties and add a string property with the name IFS.SERVER.PROTOCOL.NTFS.SystemUserName. Set the value of this property to the Oracle Files user name to be used to access the "O" drive on the Windows server. After changing the NTFS server configuration, you must stop and restart the node by using the ifsctl stop and ifsctl start commands at a command line.
The Oracle Files Web Interface enables Oracle Files users to logon using their Oracle Files accounts without requiring Windows user accounts. However, Windows NT/2000/2003 drive mapping is controlled independently from Oracle Files, by the native Windows security mechanisms. Before users can access an Oracle Files instance on a Windows NT/2000/2003 server as a Windows file share, Oracle Files users must be authenticated by the native Windows security mechanism. Perform the following steps to allow users to map Oracle Files NTFS protocol servers as Windows network drives:
Windows server administrators must create Windows user accounts for all authorized Oracle Files users.
If your organization is using the Microsoft Windows domain security model, the Windows server administrator should create the user accounts in the Windows domain (by using User Manager for Domains), not on the local machine. (Oracle Files ignores the domain prefix and looks at the user name only. For this reason, Windows server administrators should ensure that Windows user names that map to Oracle Files user names are unique across all Windows domains.)
If the Windows user accounts already exist, the Windows server administrator must provision corresponding Oracle Files accounts. For more information about creating users in Oracle Internet Directory and automatically provisioning those users in Oracle Files, see "Creating Users in Oracle Internet Directory".
Users in a Windows NT/2000/2003 domain must enter valid Windows NT/2000/2003 user names and passwords if prompted when they attempt to map a drive to an Oracle Files server.
Windows NT/2000/2003 domain users might be prompted to supply the Windows domain name as part of their user name in the logon prompt, as follows:
windows-nt/2000/2003_domainname\username
For example:
MyDomain\gking
Once users have authenticated using the native Windows security mechanism, they gain access to Oracle Files as the user of the same name as the Windows account.
Oracle Files administrators and Windows NT/2000/2003 administrators should ensure that appropriate user accounts have been created on Windows and in Oracle Internet Directory, and therefore provisioned in Oracle Files. To avoid inappropriate access to information, the individuals associated with Oracle Files user accounts should be the same individuals associated with Windows NT/2000/2003 accounts.
If users are unable to map a network drive to an Oracle Files instance, you (or the Windows NT/2000/2003 administrator) can create a separate Windows NT/2000/2003 file share (independent of Oracle Files), and have users attempt to map to this "test" drive to determine if the problem is with Windows NT/2000/2003. If users cannot map to the native Windows NT/2000/2003 file share, see the Windows documentation to resolve the problem.
After configuring Oracle Files and starting the domain, you must run the Web client installer in order to configure the Oracle Files and Search portlets. After registering the portlets, they become available from the Oracle Collaboration Suite Web client page.
|
See Also: Chapter 6, " Installing Oracle Collaboration Suite" for information about running the Web client installer |
