3
Installation and Configuration

• Oracle CM SDK must be installed in the Oracle9i Application Server, Release 2 home. Make sure to select the file location carefully; once installed, the Oracle CM SDK software cannot be moved without deinstalling and reinstalling.

The Summary screen appears a list of the selected components. Oracle CM SDK should display among the listed items.

A progress indicator appears to monitor the installation as the files that comprise the software are copied to the appropriate directories on the server.

When the copying process completes, the Oracle Universal Installer launches the Oracle CM SDK Configuration Assistant automatically.

Oracle Content Management SDK Server Configurations

The Configuration Assistant is launched automatically by the Oracle Universal Installer, and guides you through the range of possible deployment scenarios listed in Table 3-1. The Configuration Assistant always begins with the Welcome screen shown in Figure 3-1.

Figure 3-1 Configuration Assistant Welcome Screen

Text description of the illustration ifsca_wl.gif

Make your choices on each screen and click the Next button to continue. You can click the Cancel button to stop the wizard, then configure at a later time by executing ifsca.bat from the command line, located in the following directory:

ORACLE_HOME\ifs\cmsdk\bin

Table 3-1 summarizes the types of configurations you can perform:

Table 3-1 Configuration Assistant Options

To monitor the Oracle CM SDK Configuration Assistant as it progresses, you can view the log as it's being written to the following file:

ORACLE_HOME\ifs\cmsdk\log\CmsdkConfig.log

Creating a New Oracle Content Management SDK Domain

These instructions guide you through the process of configuring the Oracle CM SDK domain controller machine, which is typically the first machine in the domain that you're configuring. You must install and configure Oracle CM SDK into an Oracle home based on Oracle9i Application Server, release 9.0.2.

The instructions begin from the Oracle CM SDK Configuration Assistant Welcome screen.

1. Click Next.

   The Domain Operation screen appears.

Figure 3-2 Domain Operation Screen

Text description of the illustration ifsca_01.gif

This option will create a new schema and configure Oracle CM SDK on the machine.

The Database Selection screen appears.

Figure 3-3 Database Selection Screen

Text description of the illustration ifsca_02.gif

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 Chapter 2, "Requirements" for information about preliminary setup requirements.)

The Oracle CM SDK 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 appears, it is likely due to a missing password file on the database server:

Invalid password for Oracle user SYS

Please refer to the Oracle 9i Database Administrator's Guide, Chapter 1, "Password File Administration", for more information.

If additional errors occur, more information on why verification failed can be found in the CmsdkConfig.log file.

When the verification process completes, the Schema Name screen appears (CMSDK CA-Step 3 of 14: Schema Name).

Figure 3-4 Schema Name Screen

Text description of the illustration ifsca_03.gif

Oracle CM SDK 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.

• Click No to return to the Schema Name screen and enter a new name for the schema.

• Click Yes if you're certain that you want to delete this schema and all related objects from the database, such as tables and views, and create a new schema.

  The Tablespaces screen appears (CMSDK CA - Step 4 of 14) after you close the message box.

Figure 3-5 Tablespaces Screen

Text description of the illustration ifsca_04.gif

• Select Use the USERS tablespace for all Oracle Content Management SDK data if you have not created custom tablespaces for Oracle CM SDK content.

• Select Specify a tablespace for each data type if you have created tablespaces specifically for Oracle CM SDK content, and choose the tablespaces you want to use for each type of content from the drop-down lists.

  Important: The tablespaces must already exist in order to select them for each data type -- the Configuration Assistant does not create them. See the Oracle Content Management SDK Administration Guide and Chapter 2, "Requirements" in this guide for additional information on custom tablespaces.

10. Click Next.

    The Character Set and Language screen appears (CMSDK CA - Step 5 of 14: Character Set and Language).

Figure 3-6 Character Set and Language Screen

Text description of the illustration ifsca_05.gif

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 CM SDK. The default character set is also used by non-Unicode enabled protocols, such as FTP and WebDAV, to determine the character set that these protocol servers should use.

Oracle Corporation recommends setting the character set to Unicode (UTF8) to enable full multi-language functionality. Specifying non-UTF8 character sets may limit Oracle CM SDK functionality, with respect to accessing and displaying content in multiple languages.

Table 3-3 lists some multi-byte character sets if you only need to support a single-language:

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. For more information, see the section on "Multi_Lexer" in the Oracle Text Reference Guide.

• Click Next.

  The Default Port Numbers screen appears (CMSDK CA-Step 6 of 14: Default Port Numbers).

Figure 3-7 Default Port Numbers Screen

Text description of the illustration ifsca_06.gif

The default port number settings are stored as an object for use by all middle-tier machines that use the Oracle CM SDK schema. To change the configuration on any single middle-tier computer, you must use the Enterprise Manager Web Site.

13. Change any of the port numbers as needed.
    • To run both third-party Windows and Oracle CM SDK versions of specific protocol servers on this computer, you must change the port numbers to avoid conflicts. If you change port numbers, the new port numbers will be used for all nodes in the domain.

    • 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.

    • If you do not want to run any Windows implementations of the services, you can accept the default port numbers.

14. Click Next.

    The Website Information screen appears.

Figure 3-8 Website Information Screen

Text description of the illustration ifsca_07.gif

15. Enter the fully qualified hostname and port number that correspond to the Oracle9iAS WebCache HTTP Listen (SSL) port and check the Uses SSL checkbox (to do this, you must have SSL configured on that computer).

    The hostname and port number can be obtained by accessing the following URL:

    http://hostname:portID/portlist

    where hostname is the hostname of the middle-tier on which Oracle CM SDK is installed, and port number corresponds to the Oracle HTTP Server Port (typically 7777).

16. Click Next.

    The Admin Information screen appears (CMSDK CA- Step 8 of 14: Admin Information).

Figure 3-9 Admin Information Screen

Text description of the illustration ifsca_08.gif

The Directory Service screen appears (CMSDK CA-Step 9 of 14: Directory Service).

Figure 3-10 Directory Service Screen

Text description of the illustration ifsca_09.gif

19. Select either CMSDK Directory Service or Oracle Internet Directory Service for user authentication.
    • If you select CMSDK Directory Service, the Users screen appears (CMSDK CA- Step 10 of 14: Users).

    • On the Users screen, enter passwords for system, guest, and scott user accounts. Enter the passwords twice, in the fields on the screen, and click Next to continue. The Set up Local Machine screen appears -- skip to Step 24.

    • If you select Oracle Internet Directory, you must already have an Oracle Internet Directory instance configured and running. Click Next to continue; the OiD Login screen appears.

Figure 3-11 OiD Login Screen

Text description of the illustration ifsca_10.gif

20. Enter the login information for the Oracle Internet Directory instance that you want to use for credential management.
    1. In the Server field, enter the fully-qualified hostname for the machine running Oracle Internet Directory.

    2. The Port field should be the port number on which the Oracle Internet Directory server is listening. You can accept the default port number or assign a new number (the default is typically 389 or 4032.)

       If you have SSL-enabled Oracle Internet Directory, select Uses SSL and change the port number. The default port number for SSL-enabled mode is 636.

    3. Enter the Oracle Internet Directory super user name and password.

       The default Oracle Internet Directory super user name/password is cn=orcladmin/welcome1.

    4. Enter the 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 has changed the root context, you must enter the correct value. The concept of a "root context" is specific to LDAP directory services.

21. Click Next.

    The Users screen appears (CMSDK CA - Step 11 of 15: Users).

    Figure 3-12 Users Screen

    

    Text description of the illustration ifsca_11.gif

    22. Create the two default Oracle Content Management SDK users. These are system and guest. Optionally, you can also create an Oracle Content Management SDK user account, scott, for demo purposes.
        • If you have an existing account in Oracle Internet Directory that you want to use for the Oracle CM SDK system user, select Map to user from the drop-down list and enter the account name and password.

        • If you don't have an account in Oracle Internet Directory to map to, select Create as New from the drop-down list. When you do this, the corresponding field under "OiD User" is grayed out, and the name "system" is displayed.

        If you attempt to create a new account but one already exists in Oracle Internet Directory, an error message displays.

    23. Click Next.

        The OidCredentialManager is now configured. The Set up Local Machine screen appears.

    Figure 3-13 Set Up Local Machine Screen

    

    Text description of the illustration ifsca_12.gif

    24. Select Yes to configure this domain as a target that can be managed using the Oracle Enterprise Manager Web site. Select No to create the new domain without configuring this domain with the software necessary to manage it as a target from the Oracle Enterprise Manager Web site.

    25. Click Next.

        The Domain Components screen appears (CMSDK CA - Step 13 of 15: Domain Components).

    Figure 3-14 Domain Components Screen

    

    Text description of the illustration ifsca_13.gif

    26. Select Run Domain Controller and all other processes that you want to configure for the domain. By default, all processes are selected on this screen.
        • If the machine contains multiple network interface cards (NICs), enter the hostname (in the Local Host Name field) that you want to use for Oracle CM SDK.

        • Run Domain Controller configures the Oracle 9iFS Domain Controller process. Only one machine in a domain should run this process.

        • Run a Node on this computer configures an Oracle 9iFS node to run on this machine.

        • Run an HTTP Node on this computer configures an HTTP node to run the Oracle 9iFS DAV server for HTTP and WebDAV access on this machine.

    27. Click Next.

        The Node Configuration screen appears (CMSDK CA -Step 14 of 15: Node Configuration).

    Figure 3-15 Node Configuration Screen

    

    Text description of the illustration ifsca_14.gif

    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 machine (host name), but it need not. Use any string that makes sense to you.

    • Run Oracle 9iFS System Agents configures all the Oracle 9iFS system agents to run on this machine. 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 Oracle 9iFS Protocol Servers configures the Oracle 9iFS protocol servers to run on this machine. Protocol Servers include FTP, AFP, NFS, and NTFS.

    See Chapter 1, Concepts, in the Oracle Content Management SDK Administration Guide for more information about protocol servers and agents.

    • Click Next.

      If you selected the Run an HTTP Node on this computer on the Domain Components screen, the HTTP Node Configuration screen appears. (Otherwise, the Summary screen appears.)

    Figure 3-16 HTTP Node Configuration Screen

    

    Text description of the illustration ifsca_15.gif

    29. Enter the name for the HTTP Node.

    30. Click Next.

        The Summary screen appears (CMSDK CA - Summary). The Oracle CMSDK Configuration Assistant now has all the information it needs to create a new Oracle CM SDK 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.

    Figure 3-17 Summary Screen

    

    Text description of the illustration ifsca_su.gif

    31. Click Configure to execute the configuration process.

        A progress window appears. If an error occurs, check the following log file for more information:

        ORACLE_HOME\ifs\cmsdk\log\CmsdkConfig.log
        
        

        When the process is complete, a message appears notifying you that the configuration was successful. Click OK to close the message. Oracle CM SDK and the Oracle Enterprise Manager Web site are integrated automatically.

        If the Oracle CMSDK Configuration Assistant was launched by the Oracle Universal Installer, the OUI End Installation screen appears.

    32. Click Exit and then Yes to quit the Oracle Universal Installer.

    See Chapter 4, "Post-configuration" for instructions about how to make Oracle Content Management SDK operational.

    Upgrading an Oracle Internet File System Domain

    These instructions presume you have completed all necessary tasks detailed in Chapter 2. Before running the Oracle CM SDK Configuration Assistant, be sure to copy over any custom classes from your old Oracle Internet File System installation to the 9.0.3 installation (directory is ORACLE_HOME\ifs\cmsdk\custom_classes). If the Configuration Assistant cannot find the custom classes, upgrading the schema may fail.

    The instructions begin from the Oracle CMSDK Configuration Assistant Welcome screen. Screens for the Oracle CM SDK Configuration Assistant are pictured in the previous section, Creating a New Oracle Content Management SDK Domain.

    Note: The upgrade process requires the default LOB chunk size of 32K. If you changed the default chunk size when you initially installed and configured Oracle Internet File System, you must change the chunk size in the upgrade actions file before upgrading. Contact your Oracle Support representative for details.

    1. Read the Welcome screen, then click the Next button to begin the configuration process.

       The Domain Operation screen appears.

    2. Select the Upgrade an existing Oracle Internet File System domain option.

       This option will upgrade an existing Oracle Internet File System instance to the Oracle CM SDK release.

    3. Click Next.

       The Database Selection screen appears.

    4. Enter the name of the host on which the database containing the existing Oracle Internet File System domain is running (database host name), the listener port number, the database service name, and the password for the database SYS user account.

    5. Click Next.

       The Database Login Verifications message box appears while the CLASSPATH, database connection to the Oracle9i database, 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 Chapter 2, "Requirements" for information about preliminary setup requirements.)

       The Oracle CM SDK 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 appears, it is likely due to a missing password file on the database server:

       Invalid password for Oracle user SYS
       
       

       Please refer to the Oracle 9i Database Administrator's Guide, Chapter 1, "Password File Administration", for more information.

       When the verification process completes, the Schema Name screen appears (CMSDK CA-Step 3 of 14: Schema Name).

    6. Enter the name of the Oracle Internet File System schema that you want to upgrade. You must also enter the schema password.

    7. Click Next.

       If you are upgrading from Oracle Internet File System release 9.0.1 or higher, the Website Information screen appears. Proceed to step 12.

       If you are upgrading from an Oracle Internet File System release prior to 9.0.1, the Tablespaces screen appears.

    8. Choose one of the following options:
       • Select Use the USERS tablespace for all Oracle Content Management SDK data if you have not created custom tablespaces for Oracle CM SDK content.

       • Select Specify a tablespace for each data type if you have created tablespaces specifically for Oracle CM SDK content, and choose the tablespaces you want to use for each type of content from the drop-down lists.

         Important: The tablespaces must already exist in order to select them for each data type -- the Configuration Assistant does not create them. See the Oracle Content Management SDK Administration Guide and Chapter 2, "Requirements" in this guide for additional information on custom tablespaces.

    9. Click Next.

       The Default Port Numbers screen appears (CMSDK CA-Step 6 of 14: Default Port Numbers).

       The default port number settings are stored as an object for use by all middle-tier machines that use the Oracle CM SDK schema. To change the configuration on any single middle-tier computer, you must use the Enterprise Manager Web Site.

    10. Change any of the port numbers as needed.
        • To run both third-party Windows and Oracle CM SDK versions of specific protocol servers on this computer, you must change the port numbers to avoid conflicts. If you change port numbers, the new port numbers will be used for all nodes in the domain.

        • 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.

        • If you do not want to run any Windows implementations of the services, you can accept the default port numbers.

    11. Click Next.

        The Website Information screen appears.

    12. Enter the fully qualified hostname and port number of the computer through which you want the domain to provide HTTP listener services. Select Uses SSL only if you've configured SSL on that computer.

    13. Click Next.

        The Admin Information screen appears (CMSDK CA- Step 8 of 14: Admin Information).

    14. Enter the fully qualified email address to use for sending notifications and other messages to the Oracle CM SDK administrator. For example, username@yourcompany.com.

    15. Click Next.

        The Set up Local Machine screen appears.

    16. Select Yes to configure this domain as a target that can be managed using the Oracle Enterprise Manager Web site. Select No to create the new domain without configuring this domain with the software necessary to manage it as a target from the Oracle Enterprise Manager Web site.

    17. Click Next.

        The Domain Components screen appears (CMSDK CA - Step 13 of 15: Domain Components).

    18. Select Run Domain Controller and all other processes that you want to configure for the domain. By default, all processes are selected on this screen.
        • If the machine contains multiple network interface cards (NICs), enter the hostname (in the Local Host Name field) that you want to use for Oracle CM SDK.

        • Run Domain Controller configures the Oracle 9iFS Domain Controller process. Only one machine in a domain should run this process.

        • Run a Node on this computer configures an Oracle 9iFS node to run on this machine.

        • Run an HTTP Node on this computer configures an HTTP node to run the Oracle 9iFS DAV server for HTTP and WebDAV access on this machine.

    19. Click Next.

        The Node Configuration screen appears (CMSDK CA -Step 14 of 15: Node Configuration).

        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 machine (host name), but it need not. Use any string that makes sense to you.

        • Run Oracle 9iFS System Agents configures all the Oracle 9iFS system agents to run on this machine. 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 Oracle 9iFS Protocol Servers configures the Oracle 9iFS protocol servers to run on this machine. Protocol Servers include FTP, AFP, NFS, and NTFS.

        See Chapter 1, Concepts, in the Oracle Content Management SDK Administration Guide for more information about protocol servers and agents.

    20. Click Next.

        If you selected the Run an HTTP Node on this computer on the Domain Components screen, the HTTP Node Configuration screen appears. Otherwise, the Summary screen appears.

    21. Enter the name for the HTTP Node.

    22. Click Next.

        The Summary screen appears (CMSDK CA - Summary). The Oracle CMSDK Configuration Assistant now has all the information it needs to create a new Oracle CM SDK 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.

    23. Click Configure to execute the configuration process.

        A progress window appears. If an error occurs, check the following log file for more information:

        ORACLE_HOME\ifs\cmsdk\log\CmsdkConfig.log
        
        

        When the process is complete, a message appears notifying you that the configuration was successful. Click OK to close the message. Oracle CM SDK and the Oracle Enterprise Manager Web site are integrated automatically.

        If the Oracle CMSDK Configuration Assistant was launched by the Oracle Universal Installer, the OUI End Installation screen appears.

    24. Click Exit and then Yes to quit the Oracle Universal Installer.

    See Chapter 4, "Post-configuration" for instructions about how to make Oracle Content Management SDK operational. Be sure to also perform the "Additional Post-configuration Tasks for Upgrades from 1.1.x Only".

    Setting Up a Computer to Use an Existing Domain

    These instructions guide you through the process of setting up a computer to use an existing domain. You must install and configure Oracle CM SDK software into an Oracle home based on Oracle9i Application Server, release 9.0.2.

    The instructions begin from the Oracle CM SDK Configuration Assistant Welcome screen.

    1. Click Next to begin the configuration process.

    2. Select the Set up this computer to use and existing Oracle CM SDK domain option and click Next.

       The Database Selection screen appears.

    3. 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.

    4. Click Next.

       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 will see an error message related to the DBMS_JAVA package. (See Chapter 2, "Requirements" for information about preliminary setup requirements.)

       The 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. The following error message is likely due to a missing password file on the database server.

       Invalid password for Oracle user SYS 
       
       

       Please refer to the Oracle 9i Database Administrator's Guide, Chapter 1, Password File Administration, for more information.

       If additional errors occur, more information on why verification failed can be found in the CmsdkConfig.log file.

       When the verification process completes, the Domain Components screen appears.

    5. Select Run Domain Controller and all other processes that you want to configure for the domain. By default, all processes are selected on this screen.
       • If the machine contains multiple network interface cards (NICs), enter the hostname (in the Local Host Name field) that you want to use for Oracle CM SDK.

       • Run Domain Controller configures the Oracle 9iFS Domain Controller process. Only one machine in a domain should run this process.

       • Run a Node on this computer configures an Oracle 9iFS node to run on this machine.

       • Run an HTTP Node on this computer configures an HTTP node to run the Oracle 9iFS DAV server for HTTP and WebDAV access on this machine.

    6. Click Next.

       The Node Configuration screen appears.

       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 machine (host name), but it need not. Use any string that makes sense to you.

       • Run Oracle 9iFS System Agents configures all the Oracle 9iFS system agents to run on this machine. 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 Oracle 9iFS Protocol Servers configures the Oracle 9iFS protocol servers to run on this machine. Protocol Servers include FTP, AFP, NFS, and NTFS.

       See Chapter 1, Concepts, in the Oracle Content Management SDK Administration Guide for more information about protocol servers and agents.

    7. Click Next.

       If you selected the Run an HTTP Node on this computer option on the Domain Components screen, the HTTP Node Configuration screen appears. Otherwise, the Summary screen appears.

    8. Enter the name for the HTTP Node.

    9. Click Next.

       The Summary screen appears (CMSDK CA - Summary). The Oracle CMSDK Configuration Assistant now has all the information it needs to create a new Oracle CM SDK 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.

    10. Click Configure to execute the configuration process.

        A progress window appears. If an error occurs, check the following log file for more information:

        ORACLE_HOME\ifs\cmsdk\log\CmsdkConfig.log
        
        

        When the process is complete, a message appears notifying you that the configuration was successful. Click OK to close the message. Oracle CM SDK and the Oracle Enterprise Manager Web site are integrated automatically.

        If the Oracle CMSDK Configuration Assistant was launched by the Oracle Universal Installer, the OUI End Installation screen appears.

    11. Click Exit and then Yes to quit the Oracle Universal Installer.

    See Chapter 4, "Post-configuration" for instructions about how to make Oracle Content Management SDK operational.

    Non-interactive Installation and Configuration

    As an alternative to using the graphical tools described in Oracle Content Management SDK Server Configurations, you can pass the name of a response file (.rsp) to the setup.exe executable as a parameter. If your response file contains responses for all of the installer prompts, you can use the -silent parameter to avoid seeing any dialogs or windows at all. Do this only if you have verified that the response file meets your specific deployment needs or if you have modified it to do so.

    Table 3-3 Response File Parameters

    Parameter	Description	Example
    ORACLE_HOME=	Enter the correct Oracle home name for your machine.	ORACLE_HOME=D:\IAS902
    s_IfsConfigRspFile=	Enter the IfsConfig Response filename.	s_IfsConfigRspFile= ORACLE_HOME\ifs\cmsdk\settings\ silentconfig.properties
    b_configureIFS=	Set to FALSE to install only (not configure). If you set b_configureIFS=TRUE, be sure you've already modified the IFS response file as required for your particular configuration.	b_configureIFS=FALSE

    The Oracle Universal Installer response file, which copies the base software, libraries, and various scripts to the machine for further configuration, is located on the CD in the stage\Response\ directory.

    After making any necessary changes to the file, you can install the software by using these two commands:

    cd %STAGE_LOCATION%\install\win32
    
    setup.exe -responseFile %STAGE_
    LOCATION%\stage\Response\oracle.ifs.Complete.rsp -silent
    

    You can configure the Oracle CM SDK domain using this same approach, by passing a response file (containing all the configuration settings) to the Configuration Assistant as a parameter at the command line. The response file is located in the ORACLE_HOME\ifs\cmsdk\settings directory after installing using the OUI, or the script:

    ORACLE_HOME\ifs\cmsdk\settings\silentconfig.properties
    
    

    The file itself contains instruction about how to modify and use it. Modify the response file to meet your specific needs.

    1. Open the silentconfig.properties file in a text editor.

    2. Make any other changes to the settings in the file you need, and close the file when you're finished.

    3. Run the Configuration Assistant using your modified response file using these two commands:

       cd ORACLE_HOME\cmsdk\bin
       ifsca.bat -file ORACLE_HOME\ifs\cmsdk\settings\silentconfig.properties -silent
       
       

    Oracle CM SDK will be configured on the machine according to the specifications defined in the response file. If errors occur during the silent install, check the CmsdkConfig.log file for more information.

    Continue with the required post-installation tasks for your configuration as detailed in Chapter 4, "Post-configuration".

    Oracle Internet Directory and Credential Management

    For detailed information on Oracle Internet Directory and Credential Management (including Credential Manager Configuration and Oracle Internet Directory User Migration), see Oracle Content Management SDK Administration Guide, Chapter 6, "Oracle Internet Directory and Credential Management."