4 Post-Configuration

Granting Privileges to the Administrator Account

You must grant the Windows NT, 2000, 2003, and XP Administrator account (or other account that you are using to install and configure Oracle CM SDK) the Logon as Batch Job privilege in order for the local user to be able to start the Domain Controller and Nodes from the Application Server Control 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).

Starting All Necessary Processes

These instructions assume that Oracle Application Server and Oracle CM SDK have been installed and configured properly, and that the database and listener are running.

Oracle CM SDK uses the Oracle Application Server Containers for J2EE (OC4J) component of Oracle Application Server to support the DAV Servlet, which is deployed to OC4J automatically at the end of the configuration process.

1. Stop and restart the Application Server Control on the Oracle CM SDK middle-tier computer. Use the following two commands to stop and start the site:

   %ORACLE_HOME%\bin\emctl stop iasconsole
   %ORACLE_HOME%\bin\emctl start iasconsole
   
   

   If your Oracle CM SDK domain comprises multiple physical computers, you must run this emctl start iasconsole command on each computer.

2. From a Web browser, access the URL to connect to the Application Server Control on the computer where the Oracle CM SDK domain controller is configured:

   http://hostname:port
   
   

   The value for port is set automatically during Oracle Application Server configuration. This value is typically 1810. The port number is listed in the portlist.ini file, located in %ORACLE_HOME%\install\.

   • Alternatively, you can access the Oracle Application Server page directly by entering the following URL:

     http://hostname:port/emd/console/targets
     
     

     If you use this URL, the screen described in step 4 appears.

3. A Username and Password Required or Enter Network Password prompt appears. Enter the Oracle9iAS user name and password to proceed.

   Enter ias_admin as the user name with the appropriate password for the Oracle Application Server instance. If no Infrastructure has been configured, the Oracle Application Server Home page appears (otherwise, the farm page appears). The name displays as Enterprise Manager. A Targets tab appears in the upper-right area of the screen.

   The web page lists the Oracle Application Server components (the Targets) running on the specified host. By default, Oracle Business Components for Java (BC4J), OC4J Demos, Clickstream Collector, and other components are installed on every Oracle Application Server instance, regardless of the installation type and selections you make.

4. Click on the name of the Oracle Application Server instance that is hosting the Oracle CM SDK software. If prompted, enter the Oracle Application Server instance user name and password (ias_admin/password) to continue.

   
   

   Note: You are prompted to enter the Oracle CM SDK system administrator user name and password if you are logging in for the first time after: Upgrading the Oracle CM SDK schema Running ifsca to add a second middle tier for an additional HTTP node, regular node, or to migrate the domain controller, and you reused the existing Oracle CM SDK schema. If you do not provide the Oracle CM SDK system administrator user name and password, the Oracle CM SDK home page in Application Server Control does not display any elements of the Oracle CM SDK domain.

   
   

5. A page appears that lists the Oracle Application Server system components running on the instance. This list should include the Oracle CM SDK domain, which appears as a concatenation of Content Management SDK and the schema for Oracle CM SDK. For example:

   Content Management SDK(CMSDKSchemaName)
   
   

   Note that although you see Start and Stop buttons on this page, you cannot manage Oracle CM SDK from this page. You must perform the following steps to manage Oracle CM SDK.

6. Click the domain name. On the subsequent page, click Start Local Components. A page prompting you for the host credential to launch the Oracle CM SDK node appears.

   • Enter the OS (operating system) account name and password for the computer, typically Administrator or the Oracle user who has been granted the Logon as Batch Job privilege.

   • Click OK to continue.

   If your domain comprises multiple nodes across multiple computers, repeat this step for each computer. You must enter the OS account name and password on each computer running a node that you want to start.

7. Make sure that the OC4J instance is running.

   • 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 process-type=OC4J_iFS_cmsdk
     
     

   The Oracle CM SDK domain starts. You must start the OC4J service or instance on every middle tier computer that is running the HTTP Node.

8. Check the status of the Oracle CM SDK domain. Either view the Domain page of Oracle Enterprise Manager, or run the ifsctl status -n command from the following directory:

%ORACLE_HOME%\ifs\cmsdk\bin\

ifsctl.bat command start [-v] [-n] [domain]

ifs://hostname:port:service:schema

%ORACLE_HOME%\ifs\cmsdk\log\ifsctl.log

Validating Basic Operations

To validate that the domain and nodes have started and that the core Oracle CM SDK components are working, connect to the system from another computer on the network.

If a "503 Service Temporarily Unavailable" message appears when you connect to the Web server (HTTP), the HTTP node of the domain has not been started. Start the HTTP node to continue. See Chapter 6, "Troubleshooting" for more information.

Running the Web Starter Application

Oracle CM SDK is shipped with a sample Web application that developers can use as a starting point for creating their own custom Web applications. The Web Starter Application runs in its own OC4J instance, called OC4J_iFS_webstarterapp. This OC4J instance is automatically deployed during Oracle CM SDK configuration.

To start and run the Web Starter Application:

1. After the Oracle CM SDK domain has started, use opmnctl (located in %ORACLE_HOME%\opmn\bin\) to run the following commands:

   • Start OPMN:

     opmnctl start
     
     

   • Start the HTTP server:

     opmnctl startproc type=ohs
     
     

   • Start the Web Starter Application:

     opmnctl startproc process-type=OC4J_iFS_webstarterapp
     
     

2. Using a Web browser, access the Web Starter Application by entering:

   http://hostname:port/webstarterapp
   
   

Where port is usually 80. The Web Starter Application generates a log file, located at:

%ORACLE_HOME%\j2ee\OC4J_iFS_webstarterapp\application-deployments\webstarterapp\ OC4J_iFS_webstarterapp_default_island_1\application.log

Configuring the NFS Server

You can make the following three configuration changes to the Oracle CM SDK NFS Protocol Server:

• Mapping UNIX UIDs to Oracle CM SDK User Accounts. Creates a mapping between UNIX UIDs and Oracle CM SDK user accounts so that users can access Oracle CM SDK after logging on to their UNIX user accounts.

• Setting Up a Trusted Client List. Explicitly grants or revokes access privileges to a specific IP address, host computer, or domain. The Trusted Client list is an Oracle-specific capability to enhance NFS protocol security.

• Enabling NIS Authentication. If your environment uses NIS for user, group, and password information, you can configure the Oracle CM SDK NFS protocol server to use NIS to authenticate users.

In most environments, you should map the UNIX and Oracle CM SDK accounts. The user account map is a domain property, and it can be updated dynamically. You do not need to restart the server to have the mappings take effect. In addition, the changes are persistent, even after the server is restarted.

The Trusted Client List and NIS authentication are NFS server configuration properties.

See Chapter 5, "Client Access Paths and Software" for more information about configuring the NFS protocol.

Using Oracle CM SDK with a RAC Database

The following tasks are required after configuring Oracle CM SDK if you are using Oracle CM SDK with an Oracle RAC database.

In addition to the required preconfiguration tasks for setting up Oracle CM SDK to use a RAC database (see "Set Up Oracle CM SDK to Use Real Applications Clusters Database (Optional)"), you must perform the following post-configuration steps:

1. On each middle tier, back up and then edit the registry.xml file (located in the %ORACLE_HOME%\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 RAC pre-configuration steps.

   For example:

   <Instance>
     <DatabaseUrl>jdbc:oracle:oci8:@my_tnsentry</DatabaseUrl>
     <Domain>ifs://DBHOME:1521:dbservice:ifssys</Domain>
     <DomainType>cmsdk</DomainType>
     <Registered>1018925008096</Registered>
     <LastModified>1028330926700</LastModified>
     <LastStarted>1028329087966</LastStarted>
     <Ports></Ports>
   </Instance>
   
   

2. On each middle tier, back up and then edit the targets.xml file (located in the %ORACLE_HOME%\sysman\emd\ directory) to add a value for the DBConnectDescriptor parameter.

   Use the value specified as a TNS entry in the tnsnames.ora file. See "Set Up Oracle CM SDK to Use Real Applications Clusters Database (Optional)" for more information.

   For example, if the database specified in tnsnames.ora is ifsrac.company.com, specify the value of DBConnectDescriptor parameter as the following:

   <Property NAME="DBConnectDescriptor" VALUE="ifsrac.company.com"/>
   

Configuring the NTFS Protocol Server

The NTFS protocol server creates a virtual disk drive on a Windows server which provides access to Oracle CM SDK 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 CM SDK (see "Enabling Windows Users to Map Oracle CM SDK 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 CM SDK user name. After Oracle CM SDK 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 CM SDK installation does not have any users.

To access the "O" drive, you must create an Oracle CM SDK user with the same user name as the Windows server user (the Windows server administrator) that is used to start Oracle CM SDK. Once this Oracle CM SDK user is provisioned, the Windows server administrator is able to access files on the "O" drive. See the Oracle Content Management SDK Administrator's Guide for more information about creating users.

After creating the Oracle CM SDK user, verify that the Windows server administrator can access the "O" drive.

Enabling Windows Users to Map Oracle CM SDK as Network Drives (Optional)

The Oracle CM SDK Web Interface enables Oracle CM SDK users to logon using their Oracle CM SDK accounts without requiring Windows user accounts. However, Windows NT/2000/2003/XP drive mapping is controlled independently from Oracle CM SDK, by the native Windows security mechanisms. Before users can access an Oracle CM SDK instance on a Windows NT/2000/2003/XP server as a Windows file share, Oracle CM SDK users must be authenticated by the native Windows security mechanism. Perform the following steps to allow users to map Oracle CM SDK NTFS protocol servers as Windows network drives:

1. Windows server administrators must create Windows user accounts for all authorized Oracle CM SDK 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 CM SDK 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 CM SDK user names are unique across all Windows domains.)

   • If the Windows user accounts already exist, the Windows server administrator must provision corresponding Oracle CM SDK accounts.

2. Users in a Windows NT/2000/2003/XP domain must enter valid Windows NT/2000/2003/XP user names and passwords if prompted when they attempt to map a drive to an Oracle CM SDK server.

   • Windows NT/2000/2003/XP domain users might be prompted to supply the Windows domain name as part of their user name in the logon prompt, as follows:

     windows_domainname\username

     For example:

     MyDomain\gking

Once users have authenticated using the native Windows security mechanism, they gain access to Oracle CM SDK as the user of the same name as the Windows account.

Oracle CM SDK administrators and Windows NT/2000/2003/XP administrators should ensure that appropriate user accounts have been created on Windows and in Oracle Internet Directory or Oracle CM SDK, and therefore provisioned in Oracle CM SDK. To avoid inappropriate access to information, the individuals associated with Oracle CM SDK user accounts should be the same individuals associated with Windows NT/2000/2003/XP accounts.