| Oracle Collaboration Suite Installation Guide Release 1 Version 9.0.3.0.1 for HP 9000 Series HP-UX, Linux Intel, and Solaris Operating System (SPARC) Part Number B10044-02 |
|
This chapter guides you through the process of configuring Oracle Files.
This chapter contains these topics:
Oracle Files Configuration Assistant starts automatically at the end of the Oracle Universal Installer 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, you should:
prompt> lsnrctl START prompt> sqlplus /NOLOG SQL> CONNECT sys/password AS SYSDBA Connected. SQL> startup ORACLE instance started. Total System Global Area 185369592 bytes Fixed Size 279544 bytes Variable Size 117440512 bytes Database Buffers 67108864 bytes Redo Buffers 540672 bytes Database mounted. Database opened. SQL> exit
In order for users to access Oracle Files, they must first be created as users in Oracle Internet Directory. It is recommended that you perform this task prior to configuring Oracle Files. To create users in Oracle Internet Directory:
http://hostname:7777/oiddas
orcladmin).
The Create User page displays.
Once users are created in Oracle Internet Directory, they are automatically provisioned in Oracle Files every 24 hours, a default setting that can be changed to provision users more frequently.
|
See Also:
"Provisioning Users in Oracle Files" for additional information |
Oracle Workflow will not integrate successfully with Oracle Files if Oracle Workflow is not properly configured prior to configuring Oracle Files. For step-by-step information, please see Chapter 3 of the Oracle Collaboration Suite Release Notes.
| Topic | Location |
|---|---|
|
Configuring Oracle Workflow prior to configuring Oracle Files |
Chapter 3 of Oracle Collaboration Suite Release Notes |
|
Creating Oracle Files users in Oracle Internet Directory |
|
|
Provisioning users in Oracle Files |
|
|
Oracle Files configuration tasks involving Oracle Enterprise Manager |
Oracle Files Administration Guide |
|
Oracle Files Site Administrator and Subscriber Administrator information |
"Creating the Oracle Files Subscriber" and Oracle Files online help |
|
Configuring the NFS Server |
Oracle Files Release Notes |
|
Installing the Oracle FileSync client |
|
|
Other client access paths and software |
Chapter 2 of Oracle Files Administration Guide |
|
Troubleshooting Oracle Files installation and configuration |
Oracle Files Configuration Assistant is started automatically by Oracle Universal Installer, and guides you through the range of possible deployment scenarios listed in Table 6-2. Oracle Files Configuration Assistant always begins with the Oracle Files CA - Welcome screen.
Using 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 from the command line, located in the following directory:
$ORACLE_HOME/ifs/files/bin
Table 6-2 describes the type of configurations you can perform:
| Configuration Type | Description | See Also... |
|---|---|---|
|
Creates a new Oracle Files schema in the database. Optionally configures the software required to include the computer as a node in the domain. |
||
|
Configures Oracle Files software on the system for integration with 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.
The Database Selection screen appears.
SYS user account.
The Database Login Verifications message box appears while the CLASSPATH, database connection to the Oracle9i 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.
|
See Also:
"Deploying Oracle Files" for information about preliminary setup requirements |
If an "Invalid password for Oracle user SYS" error message is displayed, this is likely due to a missing password file on the database server. 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 additional errors occur, more information on why verification failed can be found in the FilesConfig.log file.
When the verification process completes, the Schema Name screen appears.
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 appears notifying you of this problem.
If the schema name does not exist, the Tablespaces screen appears.
A warning screen appears if you do not have an Oracle Workflow instance installed and configured in the database, and therefore Oracle Files cannot automatically integrated with Oracle Workflow. No warning box appears if an Oracle Workflow instance is installed and configured.
|
See Also:
"Oracle Files Dependencies on Oracle Workflow 2.6.2" for more information |
If you continue with the configuration, the Character Set and Language screen appears. Otherwise, the Oracle Files configuration process ends.
Oracle Corporation recommends setting the character set to Unicode (UTF8) to enable full multi-language functionality. Specifying non-UTF8 character sets may limit Oracle Files ability to access and display content in multiple languages.
If you need to support single-byte language functionality only, you can use UTF8 or any of the single-byte character sets supported by the database.
The Default Port Numbers screen appears.
The default port number settings are stored as an object for use by all middle tier computers that use the Oracle Files schema. To change the configuration on any single middle tier computer, you must use the Enterprise Manager Web Site.
The Web Site Information screen appears.
The SMTP Information screen appears.
The Administrator Information screen appears.
username@yourcompany.com.
The Users screen appears. 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.
The Oracle Internet Directory Login screen appears.
The default port number is 389 for LDAP. If this port is in use, port 4032 is used. You can usually leave this unchanged. If you have SSL enabled on Oracle Internet Directory, select Uses SSL and change the port number. The default port number for SSL-enabled mode is 636.
The default Oracle Internet Directory super user name is cn=orcladmin.
The password is whatever was entered when Oracle Internet Directory was installed.
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.
The Workflow Schema screen appears if an Oracle Workflow schema has been configured in the same database you specified Oracle Files should point to, during Oracle Files Configuration Assistant Step 2 of 16, Database Selection. If the Workflow Schema screen appears, continue to Step 26.
Otherwise, the Setup Local Machine screen appears. Continue to step 29.
The Setup Local Machine screen appears.
The Domain Components screen appears.
The Node Configuration screen appears. This screen lists all the protocol servers and agents that you can choose to run in the domain:
The HTTP Node Configuration screen appears, 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 36.
Otherwise, the Summary screen appears. Continue to step 38.
The Summary screen appears. 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.
A progress window appears. 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 Oracle Files Configuration Assistant was started by Oracle Universal Installer, then any remaining configuration tools are started.
These instructions guide you through the process of setting up a computer to use an existing domain. You must install and configure Oracle Files software into an Oracle home based on Oracle Collaboration Suite. For visual reference, see the screen shots included in the previous section.
The instructions begin from the Oracle Files Configuration Assistant Welcome screen.
The Domain Operation screen appears
The Database Selection screen appears.
SYS user account.
The Database Login Verifications message box appears as the CLASSPATH, database connection to the Oracle9i 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.
|
See Also:
Chapter 2, "Preparing for Installation" for more information about preliminary setup requirements |
If an "Invalid password for Oracle user SYS" error message is displayed, this is likely due to a missing password file on the database server. 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 additional errors occur, more information on why verification failed can be found in the FilesConfig.log file.
When the verification process completes, the Schema Name screen appears.
The Domain Components screen appears after the database connection and schema are verified.
The Node Configuration screen appears.
The Node Configuration screen lists all the protocol servers and agents that you can choose to run in the domain:
The HTTP Node Configuration screen appears 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 appears. Continue to step 14.
The Summary screen appears. 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.
A progress window appears. If an error occurs, check the following log file for more information:
$ORACLE_HOME/ifs/files/log/FilesConfig.log
If Oracle Files Configuration Assistant was started by Oracle Universal Installer, then the remaining configuration tools are started.
You can configure the Oracle Files domain non-interactively by passing a response file containing all the configuration settings to 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.
silentconfig.properties file in a text editor.
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
Perform the following tasks to complete the initial configuration and start the domain, and to ensure that your system is operational and secure:
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 Oracle9iAS Infrastructure to support the DAV Servlet, which is deployed to OC4J automatically during the configuration process.
targets.xml file, the Oracle Files domain does not appear in the Oracle Enterprise Manager Web Site until you restart Oracle Enterprise Manager.
$ORACLE_HOME/bin/emctl start
If your Oracle Files domain comprises multiple physical computers, you must run the emctl start command on each computer.
http://hostname:1810
Alternatively, you can go directly to the Oracle Enterprise Manager page by entering:
http://hostname:1810/emd/console/targets
If you enter this URL, the page listed in Step 4 appears.
A Username and Password Required or Enter Network Password prompt appears.
ias_admin as the user name with the appropriate password for the Oracle9iAS Infrastructure instance.
The Web page displays a list of all Oracle9iAS Infrastructure and Oracle Collaboration Suite components, or Targets, running on the specified host.
ias_admin and the appropriate password to continue.
A 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
root user name and password.
If your domain comprises multiple nodes across multiple computers, repeat this step for each computer. You must enter the operating system account name and password on each computer running a node that you want to start.
The Oracle Files top-level management page appears. The domain name displays in the upper-left area of the page. The domain name has the form:
myHostname.mycompany.com:1521:myDBServiceName:myFILESSchemaName
opmnctl startall
To stop the OC4J instance, enter:
opmnctl stopall
The Oracle Files domain starts.
$ORACLE_HOME/ifs/files/bin/ifsctl status -n
In the following steps, you will log in to Oracle Files as the Site Administrator and create the Subscriber.
http://httphost:port/files/app/AdminLogin
For example:
http://acme.us.oracle.com:7778/files/app/AdminLogin
The Administrator Login page appears.
site_admin and use the same site_admin password you used during configuration.
The Subscriber Name page appears. Note that the Subscriber Name is the default subscriber for the Oracle Internet Directory server. The Oracle Internet Directory server is the value entered during Oracle Files configuration (this subscriber is typically "US").
The Subscriber Information page appears.
The Create Subscriber Administrator Account page appears.
The New Subscriber Confirmation page appears.
The Browse Subscribers page appears. You can see that the Subscriber has been created and the Subscriber's password has been automatically e-mailed.
http://httphost:port/files/app/AdminLogin
The Administrator Login page appears.
"Provisioning Users in Oracle Files" for more information about creating users in Oracle Files
See Also:
In order for users to access Oracle Files, they must first be created as users in Oracle Internet Directory.
|
See Also:
"Preconfiguration Tasks for Oracle Files" in this chapter for information about how to create users in Oracle Internet Directory. |
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 24 hours (the default setting) by the FilesOidUserSynchronizationAgent.
To reset the activation period for FilesOidUserSynchronizationAgent from 24 hours to a shorter time period (so that you do not have to wait 24 hours for the agent to provision users in Oracle Files) follow these steps:
$ORACLE_HOME/bin/emctl start
If you have more than one Oracle9iAS Infrastructure or Oracle Collaboration Suite home on the same host, start EMD from the ACTIVE_EMD_HOME. You can check your ACTIVE_EMD_HOME by navigating to the location shown in the following table:
| Operating System | Location |
|---|---|
|
Solaris |
|
|
HP-UX and Linux |
|
http://hostname:1810/.
ias_admin using the same password you entered for the Oracle Collaboration Suite instance when you installed Oracle Collaboration Suite.
iFS_host:1521:ServiceName_SchemaName
The Files Domain page appears.
FilesOidUserSynchronizationAgentConfiguration by changing the value of IFS.SERVER.TIMER.ActivationPeriod from 24h to 3m (three minutes).
FilesOidUserSynchronizationAgentConfiguration.
The Load Server page appears.
FilesOidUserSynchronizationAgent.
After the FilesOidUserSynchronizationAgent has provisioned users, you can change the ActivationPeriod back to 24 hours (24h) or whatever is your preference.
As a result of the synchronization process, Oracle Files users receive an e-mail confirming that they have an account on Oracle Files, with a URL to the Oracle Files login page and instructions on how to enable protocol access to Oracle Files.
To access the protocol servers running on your Oracle Files Domain, each end user should perform the following steps:
http://hostname:7778/files/app/ProtocolAccess
The Single Sign On page (SSO) appears.
The Protocol Access page appears.
Now that you have configured the Oracle Internet Directory user using the Protocol Access page, you can access the protocol servers that may be running on your Oracle Files Domain.
To validate that the domain and node started and the core Oracle Files components are working, attempt to connect to the system from another computer on the network.
Note that if you attempt to connect to the HTTP Web server and receive a 503 Service Temporarily Unavailable message, the domain (in particular, the HTTP node) has not fully started. You must start the HTTP node.
|
|
![]() Copyright © 2002 Oracle Corporation. All Rights Reserved. |
|