4
Post-Configuration

The instructions in this chapter assume that you have completed all of the pre-installation and configuration tasks described in previous chapters. Topics in this chapter include:

• Required Post-Configuration Task

• Optional Post-Configuration Tasks

Required Post-Configuration Task

The instructions presume that the Oracle CM SDK Configuration Assistant has successfully completed. You must perform the following task to complete the configuration and start the domain, and to ensure that your system is operational and secure:

• Starting All Necessary Processes

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. Restart the Application Server Control on the Oracle CM SDK middle-tier computer by stopping it and then starting it again. Use the following command to start the site:

   $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 specified during Oracle Application Server configuration. This value is typically 1810.

   • 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 username 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 system username 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 system username 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. On UNIX systems, this is typically the root user name and password.

   • 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. Use the opmnctl command, located in :

   $ORACLE_HOME/opmn/bin/
   
   

   Use the following command to start the OC4J instance:

   opmnctl startproc process-type=OC4J_iFS_cmsdk
   
   

   The Oracle CM SDK domain starts.

Starting the Oracle CM SDK Domain from the Command Line

Alternatively, you can use the ifsctl command-line tool to start the Oracle CM SDK domain. You must be logged in as the root user in order to use the ifsctl tool. The tool is located in:

$ORACLE_HOME/ifs/cmsdk/bin/

The syntax is:

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

This launches any local Oracle CM SDK nodes for the specified domain. ("Local nodes" are those configured to run on the computer where ifsctl is invoked.) If the domain controller for the specified domain runs locally, it is also launched. If you omit the domain, the tool launches all local Oracle CM SDK nodes and domain controllers for all domains for which the computer is registered. The command also starts the domain controller if it has been launched (either locally or remotely) but is not yet started.

Specify [domain] in the following format:

ifs://<hostname>:<port>:<service>:<schema>

The -v flag causes ifsctl to generate a log file with additional diagnostic information, located at:

$ORACLE_HOME/ifs/cmsdk/log/ifsctl.log

Starting an Oracle CM SDK domain requires a schema password. If you omit the -n flag, ifsctl prompts for the password. If you include the -n flag, ifsctl runs in non-interactive mode, and does not prompt for the schema password. In this case, ifsctl launches the Oracle CM SDK nodes and domain controllers, but does not start the domain controller.

See the Oracle Content Management SDK Administrator's Guide for more information about starting, stopping, and managing Oracle CM SDK.

Optional Post-Configuration Tasks

Depending on the details of your Oracle CM SDK deployment, you might need to perform the following post-installation tasks. These tasks are not required to configure and run Oracle CM SDK.

• Validating Basic Operations

• Running the Web Starter Application

• Configuring the NFS Server

• Using Oracle CM SDK with a RAC Database

See the Oracle Content Management SDK Administrator's Guide for more post-configuration options, including user and folder creation information.

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.

Table 4-1  Basic Functionality

Protocol or Server	Access Address or Method	Expected Result
HTTP	http://<hostname>:<port>/cmsdk/admin	Prompts for the administrative user account (system/<password>) and, upon authentication, displays the Oracle CM SDK Manager. The value for port is specified during Oracle Application Server configuration. This value is typically 1810.
SMB	\\<hostname>\root From Windows Explorer, select Tools > Map network drive.	Displays a Windows file share. Prompts for an Oracle CM SDK user name and password. Upon authentication, displays a folder listing.

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 gid=OC4J_iFS_webstarterapp
     
     

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

   http://<hostname>:<port>/webstarterapp
   
   

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

Note: For more information about the Web Starter Application, see the ReadMe file included with the Web Starter Application sample code.

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.

Mapping UNIX UIDs to Oracle CM SDK User Accounts

The Oracle CM SDK NFS Protocol Server uses the UNIX system authentication process to authenticate users. The UNIX UID (user identification) number is passed to the Oracle CM SDK NFS protocol server.

If their UNIX accounts are mapped to Oracle CM SDK accounts, users can log in to the UNIX operating system and access Oracle CM SDK without having to undergo an additional login process.

UNIX-UID to-Oracle CM SDK client mapping is configured in the IFS.DOMAIN.PROTOCOL.NFS.UidToUserMap domain property. You can map UIDs manually, through the Application Server Control, or you can upload UIDs using the Java Bulk NFS Tool.

Mapping UIDs Manually

To map UIDs manually:

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

   http://<hostname>:<port>
   
   

   The value for port is specified during Oracle Application Server configuration. This value is typically 1810.

2. Enter the Oracle Application Server login username and password to continue.
   • Enter ias_admin as the username with the appropriate password for the Oracle Application Server instance.

   The Oracle Application Server Home page appears, listing all of the components running on the application server instance, including the Oracle CM SDK domain.

3. Click the name of the Oracle CM SDK domain. The Oracle CM SDK home page appears, listing the domain controller and nodes that comprise the domain.

4. Click Domain Properties (under the Configuration heading). The Domain Properties page appears, listing 25 property bundles at a time. Scroll down until you find IFS.DOMAIN.PROTOCOL.NFS.UidToUserMap. The property might be located on a second or subsequent page.

5. Click IFS.DOMAIN.PROTOCOL.NFS.UidToUserMap. The Edit page appears.

   By default, the UID 60001 (the default UNIX guest account) is listed on the page.

6. Click Add to add a UNIX UID and create a mapping to an Oracle CM SDK user account:
   • Enter the UID in the Name field.

   • Enter the Oracle CM SDK user account name in the Value field.

   • Leave the Type setting as String.

7. Continue adding users in this manner until you have added all users with UNIX client accounts that will access Oracle CM SDK using NFS.

Unlike other domain properties, changes to this domain property are updated dynamically, so you need not restart the domain. In addition, these changes persist after the domain is restarted.

Mapping UIDs Using the Bulk NFS Tool

To map UIDs using the Bulk NFS Tool:

1. On any middle-tier host, ensure that the CLASSPATH includes cmsdk.jar.

   This file is located in the $ORACLE_HOME/ifs/cmsdk/lib directory.

2. Run the following single line with the required values:

   java oracle.ifs.protocols.nfs.tools.UidLoader SmallServiceConfiguration 
   system <cmsdk_system_user_password> 
   uidfile=$IFSROOT/test/common/sosd/UidToName
   
   

   Where UidToName is a flat file you have created with entries of type:

   <cmsdk_user>:x:<uid on client>
   
   

   For example:

   jsmith:x:44610
   
   

   Note: The file name must be UidToName, including the use of capitalization.

3. When prompted, enter the name of the Oracle CM SDK domain, in the format:

   ifs://<hostname>:<port>:<service>:<schema>
   
   

4. When prompted, enter the Oracle CM SDK schema password.

Setting Up a Trusted Client List

You can create a list of trusted clients for Oracle CM SDK to enhance security. Oracle recommends that you change these settings in the Configuration Object and then load the server on the service using the modified configuration object so that the client list is used after a restart. Optionally, you can modify these properties dynamically.

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

   http://<hostname>:<port>
   
   

   The value for port is the value specified during Oracle Application Server configuration.

2. Enter the Oracle Application Server login username and password to continue.
   • Enter ias_admin as the username with the appropriate password for the Oracle Application Server instance.

   The Oracle Application Server Home page appears, listing all of the components running on the application server instance, including the Oracle CM SDK domain.

3. Click the name of the Oracle CM SDK domain. The Oracle CM SDK top-level page appears, listing the domain controller and nodes that comprise the domain.

4. Click Server Configurations (under the Configuration heading). The Server Configurations page appears, listing 25 property bundles at a time. Scroll down until you find NfsServerConfiguration.

5. Click NfsServerConfiguration. The Edit page appears.

6. Scroll down to the Properties section of the page to the IFS.SERVER.PROTOCOL.NFS.TrustedClientList and the IFS.SERVER.PROTOCOL.NFS.TrustedClientsEnabled properties. The properties might be located on a second or subsequent page.

7. Select the IFS.SERVER.PROTOCOL.NFS.TrustedClientsEnabled property and click Edit. The Edit Property page appears.

8. Set the Value to True. Click OK to save the change and return to the Edit NFSServerConfiguration page.

9. Select the IFS.SERVER.PROTOCOL.NFS.TrustedClientList property and click Edit. Specify each entry in one of the following formats:
   • Client address: Specify a hostname or an IP address. For example, smith.oracle.com or 130.35.59.9.

   • Domain suffix: Specify the domain as a string starting with a period character. For example, .us.oracle.com.

   • Subnet: Specify the subnet as an at symbol (@) character followed by an IP address, with an optional subnet bit length (/n) specifying the number of significant bits in the subnet address. You can omit low order zero bytes of the subnet address. For example, @130.35.68.0, @130.35.68 or @130.35.68.0/24.

     If an entry is preceded by a hyphen, then that specific client will be denied access through the Oracle CM SDK NFS server.

10. Click OK to save the change and return to the Edit NFSServerConfiguration page.

11. Click OK to save and return to the Server Configuration page.

    After modifying the NfsServerConfiguration object, you must reload the modified configuration object and restart the service:

12. Return to the Oracle CM SDK home page.

13. Click the Node where the NFS protocol server (NfsServer) is running. The Node page appears.

14. Select the NFS protocol server and click Restart.

Enabling NIS Authentication

NIS (Network Information System) is a centralized management facility that consolidates UNIX password, group, and host file information. It is a distributed database of information that is easier to maintain than individual files (/etc/group, /etc/passwd, /etc/hosts) in large UNIX networks.

1. Using a Web browser, connect to the Application Server Control running on the computer where the Oracle CM SDK domain controller is configured:

   http://<hostname>:<port>
   
   

   The value for port is specified during Oracle Application Server configuration. This value is typically 1810.

2. Enter the Oracle Application Server login username and password to continue.
   • Enter ias_admin as the username with the appropriate password for the Oracle Application Server instance.

   The Oracle Application Server Home page appears, listing all of the components running on the application server instance, including the Oracle CM SDK domain.

3. Click the name of the Oracle CM SDK domain. The Oracle CM SDK home page appears, listing the Domain Controller and nodes that comprise the domain.

4. Click Server Configurations (under the Configuration heading). The Server Configurations page appears, listing 25 property bundles at a time. Scroll down until you find NfsServerConfiguration.

5. Click NfsServerConfiguration. The Edit page appears.

6. Scroll down to the Properties section of the page to the IFS.SERVER.PROTOCOL.NFS.NISEnabled and IFS.SERVER.PROTOCOL.NFS.NISServiceProvider properties.

7. Select the IFS.SERVER.PROTOCOL.NFS.NISEnabled property and click Edit. The Edit Property page appears.

8. Set the Value to True. Click OK to save the change and return to the Edit NFSServerConfiguration page.

9. Select the IFS.SERVER.PROTOCOL.NFS.NISServiceProvider property and click Edit.
   • Specify the name of the NIS server in your network that should be used to authenticate users. The format is:

     nis://<NIS_Server_Name>/<cmsdk_domain>
     
     

10. Click OK to save the change and return to the Edit NFSServerConfiguration page.

11. Click OK to save and return to the Server Configuration page.

    After modifying the NfsServerConfiguration object, you must restart the node.

12. Return to the Oracle CM SDK home page.

13. Select the Node where the NFS protocol server (NfsServer) is running.

14. Click Stop.

15. On the Warning page, click Yes to stop the node. The status of the node changes to "Down."

16. Select the Node.

17. Click Start.

    The Node status changes to a green checkmark icon, indicating that the node is up.

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>files</DomainType>

   <Registered>1018925008096</Registered>

   <LastModified>1028330926700</LastModified>

   <LastStarted>1028329087966</LastStarted>

   <Ports></Ports>

   </Instance>

2. Modify the IFS.SERVICE.JDBC.DatabaseUrl Service Configuration Property in the Service Configuration used for the system. This property should be set to the same value specified in the DatabaseUrl specified in step 1:

   jdbc:oracle:oci8:@<tnsentry>

   You can view Service Configuration Properties through Oracle Enterprise Manager by navigating to http://<hostname>:<port> (where hostname is the computer where the Oracle CM SDK domain controller is configured, and port is the value specified during Oracle Application Server configuration, typically 1810).

   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 CM SDK processes cannot connect to the Oracle CM SDK schema.