3
Installation and Configuration

Figure 3-2 Oracle Universal Installer: File Locations Screen

Text description of the illustration instfile.gif

• Path: Accept or select the location of the products.jar file from the product CD or CD image in the Path field of the Source section.

• Name: Accept the default or enter a new name for the Oracle Home in the Name field of the Destination section.

• Path: Enter the full path of the directory in which to install the Oracle CM SDK software in the Path field of the Destination section.

You must install Oracle CM SDK in the Oracle Application Server, 10g (9.0.4) middle-tier home. Select the file location carefully. After installation, you cannot move the Oracle CM SDK software without deinstalling and reinstalling.

Figure 3-3 Oracle Universal Installer: Select a Product to Install Screen

Text description of the illustration instprod.gif

Select Oracle Content Management SDK to install Oracle CM SDK. For information about installing Oracle Workflow, see the Oracle Workflow Installation Notes for Oracle Content Management SDK.

Figure 3-4 Oracle Universal Installer: Summary Screen

Text description of the illustration instsum.gif

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

Oracle CM SDK Server Configuration Types

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

Figure 3-5 Oracle CM SDK Configuration Assistant: Welcome Screen

Text description of the illustration ifsca_01.gif

Make your choices on each screen and click Next to continue. You can click Cancel to stop the Oracle CM SDK Configuration Assistant and configure at a later time by executing ifsca from the command line, located in the following directory:

$ORACLE_HOME/ifs/cmsdk/bin

The Oracle CM SDK Configuration Assistant provides two main configuration options: Simple and Advanced.

• Simple Configuration asks a minimum of required questions and uses the defaults for most values. Simple configuration is recommended for users configuring Oracle CM SDK for testing or evaluation purposes.

• Advanced Configuration asks all advanced-level configuration questions, and enables you to create a new domain, upgrade a domain, or use an existing domain. Advanced configuration is recommended for a production environment.

Table 3-4 summarizes the types configurations you can perform:

Table 3-4  Oracle CM SDK Configuration Assistant Options

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

$ORACLE_HOME/ifs/cmsdk/log/CmsdkConfig.log

Simple Configuration

These instructions guide you through the process of configuring the Oracle CM SDK domain using the simple configuration option. You must install and configure Oracle CM SDK into an Oracle home based on Oracle Application Server, 10g (9.0.4).

The simple configuration process creates a new Oracle CM SDK schema. If you want to upgrade an existing schema, you must use one of the advanced configuration options.

• Simple Configuration Default Values

• Simple Configuration Installation

Simple Configuration Default Values

Table 3-5 summarizes the default values used in the simple configuration option.

Table 3-5  Simple Configuration Default Values

Simple Configuration Installation

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

1. Click Next on the Welcome to Oracle CM SDK Configuration Assistant screen to begin the configuration process. The Configuration Type screen appears.

Figure 3-6 Configuration Type Screen

Text description of the illustration simple01.gif

Select Simple Configuration and click Next.

Figure 3-7 Database Selection Screen

Text description of the illustration simple02.gif

• Database Host Name: Enter the fully-qualfied name of the host on which the database is running.

• Listener Port Number: Enter the listener port number. The default value is 1521.

• Database Service Name: Enter the name of the database service.

• Password of Database User SYS: Enter the password for the Oracle database SYS user account.

Click Next to continue.

If an error occurs, you must correct the problem before configuration can continue. See Chapter 6, "Troubleshooting" and view the CmsdkConfig.log file for more information.

Figure 3-8 Schema Name Screen

Text description of the illustration simple03.gif

If the name exists, or if related schema names based on the schema name exist, a message box appears notifying you of this conflict.

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

• Click Yes if you want to drop this schema and all related objects from the database (tables, views, and so forth), and create a new schema.

  Caution: Selecting Yes deletes the existing schema.

The URL Information screen appears.

Figure 3-9 URL Information Screen

Text description of the illustration simple04.gif

• HTTP Host Name: Enter the hostname of the computer through which you want the domain to provide HTTP listener services. Typically, this is the Oracle Application Server, Infrastructure middle-tier Web server computer. Enter the fully-qualified hostname in the following format:

  <computer_name>.<domain>

• HTTP Port: Enter the port number of the computer through which you want the domain to provide HTTP listener services. This port number was specified during the installation of Oracle Application Server, Infrastructure.

• Uses SSL: Click the Uses SSL box to select SSL only if you have configured SSL on the HTTP host computer. By default, the Web server computer listens at port 7777.

Figure 3-10 Summary Screen

Text description of the illustration ifscasum.gif

$ORACLE_HOME/ifs/cmsdk/log/CmsdkConfig.log

When the process completes, a message appears notifying you that the configuration was successful.

At the end of the configuration process, several scripts execute automatically in order to integrate Oracle CM SDK and the Oracle Enterprise Manager Application Server Control. See Chapter 4, "Post-Configuration" for instructions about how to make Oracle CM SDK operational.

Advanced Configuration: Creating a New Oracle CM SDK Domain

These instructions guide you through the process of configuring the Oracle CM SDK domain controller computer, which is typically the first computer in the domain that you are configuring. This option creates a new Oracle CM SDK schema. To upgrade an existing schema, see "Advanced Configuration: Upgrading an Existing Domain".

You must install and configure Oracle CM SDK into an Oracle home based on Oracle Application Server 10g (9.0.4).

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

1. Click Next on the Welcome to Oracle CM SDK Configuration Assistant screen to begin the configuration process. The Configuration Type screen appears.

Figure 3-11 Configuration Type Screen

Text description of the illustration ifsca_02.gif

Select Advanced Configuration and click Next.

Figure 3-12 Domain Operation Screen

Text description of the illustration ifsca_03.gif

Figure 3-13 Database Selection Screen

Text description of the illustration ifsca_04.gif

• Database Host Name: Enter the name of the host on which the database is running. Oracle Corporation recommends that you use a fully-qualified host name, but this is not required.

• Listener Port Number: Enter the listener port number. The default value is 1521.

• Database Service Name: Enter the name of the database service.

• Password of Database User SYS: Enter the password for the Oracle database SYS user account.

If an error occurs, you must correct the problem before configuration can continue. See Chapter 6, "Troubleshooting" and view the CmsdkConfig.log file for more information.

Figure 3-14 Schema Name Screen

Text description of the illustration ifsca_05.gif

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

• Click Yes if you want to drop this schema and all related objects from the database (tables, views, and so forth), and create a new schema.

  Caution: Selecting Yes deletes the existing schema.

The Tablespaces screen appears.

Figure 3-15 Tablespaces Screen

Text description of the illustration ifsca_06.gif

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

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

Figure 3-16 Character Set and Language Screen

Text description of the illustration ifsca_07.gif

Oracle Corporation recommends setting the character set to the character set used by the majority of users in your Oracle Files domain.

Table 3-7 lists some of the multibyte character sets available for use if you only need to support a single language:

Table 3-6  Multibyte Language Character Sets

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.

Figure 3-17 Default Port Numbers Screen

Text description of the illustration ifsca_08.gif

• To run both the native UNIX and the Oracle CM SDK versions of a specific protocol server listed on this computer, you must change the port numbers to avoid conflicts.

  Note: To provide Oracle CM SDK NFS support to NFS clients running on AIX, HP-UX, or Compaq Tru64, you must use port 2049 (the default) for Oracle CM SDK and disable the native UNIX NFS protocol server. Linux and Solaris NFS clients do not have this limitation, so you can use both UNIX NFS and Oracle CM SDK NFS protocol servers on the same computer for these clients.

• If you change the main port for the NFS protocol server, you must also change the NFS 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 run the native UNIX implementations of the services, you can accept the default port numbers. The default port number settings are stored as an object for use by all middle-tier computers that use the Oracle CM SDK schema. Use the Application Server Control to change the configuration on any single middle-tier computer.

Figure 3-18 URL Information Screen

Text description of the illustration ifsca_09.gif

• HTTP Host Name: Enter the hostname of the computer through which you want the domain to provide HTTP listener services. Typically, this is the Oracle Application Server, Infrastructure middle-tier Web server computer. Enter the fully-qualified hostname in the following format:

  <computer_name>.<domain>

• HTTP Port: Enter the port number of the computer through which you want the domain to provide HTTP listener services. This port number was specified during the installation of Oracle Application Server, Infrastructure.

• Uses SSL: Click the Uses SSL box to select SSL only if you have configured SSL on the HTTP host computer. By default, the Web server computer listens at port 7777.

Figure 3-19 Admin Information Screen

Text description of the illustration ifsca_10.gif

Figure 3-20 Directory Service Screen

Text description of the illustration ifsca_11.gif

• If you select Oracle CM SDK Directory Service, the Users screen appears.

Figure 3-21 Users Screen

Text description of the illustration ifsca_12.gif

Enter passwords for the system, guest, and scott user accounts. The password for the system account must be at least five characters long, must include at least one numeric character, and must use ASCII characters only. Click Next to continue. The Set up Local Computer screen appears. Continue the instructions at step 25.

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

Figure 3-22 OiD Login Screen

• In the Server field, enter the fully-qualified hostname of the computer running Oracle Internet Directory.

• In the Port field, enter the port number at which Oracle Internet Directory server listens.
  • The default port number is 3060.

  • If you have SSL-enabled Oracle Internet Directory, select Uses SSL and change the port number. Typically, the default port number for SSL-enabled Oracle Internet Directory is 3130.

  • The default port number for LDAP is 389. The default port number for LDAP with SSL-enabled Oracle Internet Directory is 636.

• The default Oracle Internet Directory super user name is cn=orcladmin. The password is the password supplied for the ias_admin Infrastructure user.

• The default OID root Oracle context is cn=OracleContext. Typically, you can leave this unchanged. If the Oracle Internet Directory administrator has changed the root context, enter the correct value. (The concept of a "root context" is specific to LDAP directory services.)

Figure 3-23 OiD Users Screen

Text description of the illustration oiduser.gif

• To use an existing Oracle Internet Directory user account for an Oracle CM SDK system, guest, or scott account, select Map to user and enter the account name and password.

• To create a new system, guest, or scott account, select Create as new and enter the password for the account.

  The password for the system and guest accounts must be at least five characters long and must include at least one numeric character. The scott account is optional, and typically used for demonstration purposes.

Figure 3-24 Set up Local Computer Screen

Text description of the illustration ifsca_13.gif

• Select Yes to configure this domain as a target that can be managed using the Application Server Control. Select this if you want to configure the local computer to run the Domain, Node, or HTTP Node. This creates the Oracle CM SDK schema and configures the computer as an Oracle CM SDK middle-tier.

• Select No to create the new domain without the software necessary to manage it as a target from the Application Server Control. This creates the Oracle CM SDK schema, but does not configure the computer as an Oracle CM SDK middle-tier. Continue the instructions at step 34.

Figure 3-25 Domain Components Screen

Text description of the illustration ifsca_14.gif

• If the computer contains multiple network interface cards (NICs), enter the hostname that you want to use for Oracle CM SDK in the Local Host Name field. You can specify a hostname or an IP address.

  See the Oracle Content Management SDK Administrator's Guide for information about changing a hostname after configuration.

• Select Run Domain Controller on this computer to configure the Oracle CM SDK Domain Controller process. Only one computer in the Oracle CM SDK domain should run this process.

• Select Run a Node on this computer to configure a regular node to run on this computer.

• Select Run an HTTP Node on this computer to configure an HTTP node to run the Oracle CM SDK DAV server for HTTP and WebDAV access on this computer. The HTTP node is also required to run the Oracle CM SDK Enterprise Manager.

  See the Oracle Content Management SDK Administrator's Guide for more information about domain controllers and nodes.

• Click Yes to replace the existing instance with a new OC4J instance.

• Click No to leave the existing OC4J instance. The Oracle CM SDK Configuration Assistant does not create an OC4J instance for the new HTTP node.

Otherwise, the Summary screen appears.

Figure 3-26 Node Configuration Screen

Text description of the illustration ifsca_15.gif

• Enter the name by which you want the node to be known in the Node Name field. It can include the name of the computer (hostname). The name must be unique across all of the nodes on this domain.

• Select Run Oracle CM SDK Agents to configure all of the Oracle CM SDK system agents to run on this computer. Only one computer in the Oracle CM SDK domain should run the system agents.

• Select Run Protocol Servers to configure protocol servers to run on this computer. Supported protocol servers include FTP, AFP, CUP, SMTP, NFS, SMB, and IMAP.

Otherwise, the Summary screen appears.

Figure 3-27 HTTP Node Configuration Screen

Text description of the illustration ifsca_16.gif

The Oracle CM SDK Configuration Assistant now has all the information it needs to create a new Oracle CM SDK schema and to configure the node and other processes.

Figure 3-28 Summary Screen

Text description of the illustration ifscasum.gif

$ORACLE_HOME/ifs/cmsdk/log/CmsdkConfig.log

When the process completes, a message appears notifying you that the configuration was successful.

At the end of the configuration process, several scripts execute automatically in order to integrate Oracle CM SDK and the Application Server Control. See Chapter 4, "Post-Configuration" for instructions about how to make Oracle CM SDK operational.

Advanced Configuration: Upgrading an Existing Domain

These instructions guide you through the process of upgrading an existing Oracle Internet File System or Oracle CM SDK domain. These instructions assume that you have completed all of the required tasks described in Chapter 2, and that you have stopped the existing Oracle Internet File System or Oracle CM SDK domain, as described in "Required Pre-Installation Tasks". In order to install Oracle CM SDK 10g (9.0.4), you must first upgrade to Oracle Internet File System release 9.0.2 or Oracle CM SDK release 9.0.3.

Before running the Oracle CM SDK Configuration Assistant, copy all custom classes from your old Oracle Internet File System or Oracle CM SDK installation to the 10g (9.0.4) installation. The custom classes are located in $ORACLE_HOME/ifs/cmsdk/custom_classes. If the Oracle CM SDK Configuration Assistant cannot find the custom classes, it might not be able to upgrade the schema.

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

1. Read the Welcome screen, then click Next to begin the configuration process. The Configuration Type screen appears.

2. Select Advanced Configuration and click Next. The Domain Operation screen appears.

3. On the Domain Operation screen, select Upgrade an existing Oracle Internet File System domain and click Next to continue.

4. A message appears warning you to copy your custom classes before upgrading. Click OK to continue.

5. The Database Selection screen appears.

6. On the Database Selection screen, specify the following information:
   • Database Host Name: Enter the name of the host on which the database containing the existing Oracle Internet File System or Oracle CM SDK domain is running.

   • Listener Port Number: Enter the listener port number. The default value is 1521.

   • Database Service Name: Enter the name of the database service.

   • Password of Database User SYS: Enter the password for the Oracle database SYS user account.

7. Click Next to continue. The Database Login Verifications message box appears while the Oracle CM SDK Configuration Assistant verifies the CLASSPATH, database connection to the Oracle9i Database Server, and other requirements. If an error occurs, you must correct the problem before configuration can continue.

   If an error occurs, you must correct the problem before configuration can continue. See Chapter 6, "Troubleshooting" and view the CmsdkConfig.log file for more information.

   When the verification process completes, the Schema Name screen appears.

8. Select the Oracle Internet File System or Oracle CM SDK schema that you want to upgrade and enter the password for the schema.

9. Click Next to continue. The URL Information screen appears.
   • Enter the fully-qualified hostname and port number of the computer through which you want the domain to provide HTTP (Web) services.

   • Select Uses SSL only if you have configured SSL on that computer.

10. Click Next to continue. The Admin Information screen appears. Enter the fully-qualified e-mail address to use to send notifications and other messages to the Oracle CM SDK administrator. For example, username@yourcompany.com.

11. Click Next to continue. The Set up Local Computer screen appears.

12. On the Set up Local Computer screen:
    • Select Yes to configure this computer as a target that can be managed using the Application Server Control.

    • Select No to upgrade the domain to Oracle CM SDK 10g (9.0.4) without the software necessary to manage it as a target from the Application Server Control. Continue the instructions with step 18.

13. Click Next to continue. The Domain Components screen appears. Select the processes that you want to configure for the domain. By default, all processes are selected on this screen.
    • If the computer contains multiple network interface cards (NICs), enter the hostname that you want to use for Oracle CM SDK in the Local Host Name field.

    • Select Run Domain Controller on this computer to configure the Oracle CM SDK Domain Controller process. Only one computer should run this process.

    • Select Run a Node on this computer to configure a regular node to run on this computer.

    • Select Run an HTTP Node on this computer to configure an HTTP node to run the Oracle CM SDK DAV server for HTTP and WebDAV access on this computer.

14. Click Next to continue. The Domain Component Verifications message box appears while the Oracle CM SDK Configuration Assistant verifies the local host name. If the local host name is not valid, you must retype the name in the Domain Components screen.

15. If you selected Run a Node on this computer in the Domain Components screen in step 13, the Node Configuration screen appears when the verification process completes successfully.

    Otherwise, the Summary screen appears. Continue the instructions with step 18.

16. The Node Configuration screen lists all Oracle CM SDK processes (protocol servers and agents discussed in Chapter 1, Concepts, in the Oracle Content Management SDK Administrator's Guide) that you can choose to run in the domain:
    • Enter the name by which you want the node to be known in the Node Name field. This can optionally include the name of the computer (hostname).

    • Select Run Oracle CM SDK Agents to configure all of the Oracle CM SDK system agents to run on this computer. Agents can run on only one node in the domain. If agents are configured to run on another node, you must deselect this option.

    • Select Run Protocol Servers to configure protocol servers to run on this computer. Supported protocol servers include FTP, AFP, CUP, SMTP, NFS, SMB, and IMAP.

17. Click Next to continue. If you selected Run an HTTP Node on this computer on the Domain Components screen in step 13, the HTTP Node Configuration screen appears. Enter the name for the HTTP Node and click Next to continue.

    The Oracle CM SDK Configuration Assistant now has all the information it needs to create a new Oracle CM SDK schema and to configure the node and other processes.

18. Click Next to continue. The Summary screen appears. Note the name and location of the log file.

19. Click Configure to execute the configuration process using all the information entered via the Oracle CM SDK Configuration Assistant. Once you have started 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 completes, a message appears notifying you that the configuration was successful.

20. Click OK to close the message. If the Oracle Universal Installer launched the Oracle CM SDK Configuration Assistant, the Oracle Universal Installer End Installation screen appears.

21. On the Oracle Universal Installer End Installation screen, click Exit to exit from the Oracle Universal Installer. Click Yes to confirm that you want to exit the Oracle Universal Installer.

At the end of the configuration process, several scripts execute automatically in order to integrate Oracle CM SDK and the Application Server Control. See Chapter 4, "Post-Configuration" for instructions about how to make Oracle CM SDK operational.

Advanced Configuration: Use an Existing Oracle CM SDK Domain

These instructions guide you through the process of setting up a computer to use an existing domain. Use this configuration type to add more middle-tier computers to the Oracle CM SDK domain.

You must install and configure Oracle CM SDK software into an Oracle home based on Oracle Application Server 10g (9.0.4).

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

1. Click Next on the Welcome to Oracle CM SDK Configuration Assistant screen to begin the configuration process. The Configuration Type screen appears.

2. Select Advanced Configuration and click Next. The Domain Operation screen appears.

3. On the Domain Operation screen, select Set up this computer to use an existing Oracle CM SDK domain and click Next to continue. The Database Selection screen appears.

4. On the Database Selection screen, specify the following information:
   • Database Host Name: Enter the name of the host on which the database is running.

   • Listener Port Number: Enter the listener port number. The default value is 1521.

   • Database Service Name: Enter the name of the database service.

   • Password of Database User SYS: Enter the password for the Oracle database SYS user account.

5. Click Next to continue. The Database Login Verifications message box appears as the Oracle CM SDK Configuration Assistant verifies the CLASSPATH, database connection to the Oracle9i Database Server, initialization parameters, Oracle JServer installation and other requirements.

   If an error occurs, you must correct the problem before configuration can continue. See Chapter 6, "Troubleshooting" and view the CmsdkConfig.log file for more information.

   When the verification process completes, the Schema Name screen appears.

6. Select the Oracle CM SDK schema that you want to reuse and enter the password for the schema.

7. Click Next to continue. The Domain Components screen appears.

8. On the Domain Components screen, select the processes that you want to configure to run on this computer. By default, all processes are selected.
   • If the computer contains multiple network interface cards (NICs), enter the hostname that you want to use for Oracle CM SDK in the Local Host Name field.

   • Select Run Domain Controller on this computer to configure the Oracle CM SDK Domain Controller process. Only one computer should run this process.

   • Select Run a Node on this computer to configure a regular node to run on this computer.

   • Select Run an HTTP Node on this computer to configure an HTTP node to run the Oracle CM SDK DAV server for HTTP and WebDAV access on this computer.

9. Click Next to continue. The Domain Component Verifications message box appears while the Oracle CM SDK Configuration Assistant verifies the local host name. If the local host name is not valid, you must retype the name in the Domain Components screen.

10. If you selected Run a Node on this computer in the Domain Components screen in step 13, the Node Configuration screen appears when the verification process completes successfully.

    Otherwise, the Summary screen appears. Continue the instructions with step 13.

11. The Node Configuration screen lists all Oracle CM SDK processes (protocol servers and agents discussed in Chapter 1, Concepts, in the Oracle Content Management SDK Administrator's Guide) that you can choose to run in the domain:
    • Enter the name by which you want the node to be known in the Node Name field. It can include the name of the computer (hostname), but it need not: the value is any string that makes sense to you.

    • Select Run Oracle CM SDK System Agents to configure all of the Oracle CM SDK system agents to run on this computer. Agents can run on only one node in the domain. If agents are configured to run on another node, you must deselect this option.

    • Select Run Protocol Servers to configure protocol servers to run on this computer. Supported protocol servers include FTP, AFP, CUP, SMTP, NFS, SMB, and IMAP.

12. Click Next to continue. If you selected the Run an HTTP Node on this computer on the Domain Components screen in step 8, the HTTP Node Configuration screen appears. Enter the name for the HTTP Node and click Next to continue.

    The Oracle CM SDK Configuration Assistant now has all the information it needs to configure the computer.

13. The Summary screen appears. Note the name and location of the log file.

14. Click Configure to execute the configuration process using all the information entered via the Oracle CM SDK Configuration Assistant. Once you have started 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 completes, a message appears, telling you that the configuration was successful.

15. Click OK to close the message. If the Oracle Universal Installer launched the Oracle CM SDK Configuration Assistant, the Oracle Universal Installer End Installation screen appears.

16. On the Oracle Universal Installer End Installation screen, click Exit to exit from the Oracle Universal Installer. Click Yes to confirm that you want to exit the Oracle Universal Installer.

See Chapter 4, "Post-Configuration" for instructions about how to make Oracle CM SDK operational.

Non-Interactive Installation and Configuration

As an alternative to using the graphical tools described in Oracle CM SDK Server Configuration Types, you can use text files to pass values to the installation and configuration scripts. This section contains the following topics:

• Non-Interactive Installation

• Non-Interactive Configuration

Non-Interactive Installation

To perform a non-interactive installation, pass the name of a response file (.rsp) to the runInstaller script 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-7  Response File Parameters

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

After making any necessary changes to the response file, use the following two commands to install the software:

cd $<STAGE_LOCATION>/install/<OS>

./runInstaller -responseFile $<STAGE_LOCATION>/stage/Response/oracle.ifs.Complete.rsp 
-silent

where <OS> is one of the following:

Table 3-8  Oracle Universal Installer: Operating System Directories

Non-Interactive Configuration

You can configure the Oracle CM SDK domain using this same approach, by passing a text file (containing all the configuration settings) to the Oracle CM SDK Configuration Assistant as a parameter at the command line. The text file (silentconfig.properties) is located in the
$ORACLE_HOME/ifs/cmsdk/settings directory after installing using the Oracle Universal Installer or the installation script.

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

To edit the response file and run the Oracle CM SDK Configuration Assistant:

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

2. Edit the settings in the file. When you are finished modifying the parameters, save and close the file.

3. Use the following two commands to run the Oracle CM SDK Configuration Assistant using the modified response file:

   cd $ORACLE_HOME/cmsdk/bin
   
   ./ifsca -file $ORACLE_HOME/ifs/cmsdk/settings/silentconfig.properties 
   -silent
   
   

The Oracle CM SDK Configuration Assistant script configures Oracle CM SDK on the computer according to the parameters defined in the file. If errors occur during the silent install, check the CmsdkConfig.log file, located in $ORACLE_HOME/ifs/cmsdk/log/, for more information.

Continue with the required post-installation tasks as described in Chapter 4, "Post-Configuration".