Creating an Oracle server configuration

You can create a server installation configuration to use an Oracle database. You must install the database, either locally or remotely, and create a database instance before you install the Remote Control server.

About this task

To create an Oracle server configuration task, complete the following steps:

Procedure

  1. Select the relevant operating system.
  2. Enter the installation directory for the Remote Control server to be installed to or accept the default that is given.
  3. Select the relevant Oracle version and enter the relevant database parameters.
    Database server address
    The IP address or host name of your database server. 127.0.0.1 can be used when Oracle is installed locally. If you install Oracle on a remote system, type in the IP address of the remote system.
    Port on which to connect to the database
    Port on which Oracle is installed.
    Name of the Database to use
    Specify a name for the database. The name is the SID name on the server, not the one in tnsnames.ora. For example, TRCDB.
    Database Administrator Userid
    Specify the administrator user ID that is used for logging on to the database. The user ID must have admin access to the database.
    Note: For an Oracle installation, a user that is called asset must exist. This user ID can be used here or use an existing or new user.
    Database Administrator Password
    Specify the Administrator password for connecting to the database.
    Path to the JDBC drivers
    Specify the path to the oracle Java™ JDBC library. The location can be obtained from the Oracle server installation or downloaded from the Oracle website. For example, c:\oracle\ora92\jdbc\lib\ojdbc14.jar
  4. Enter the server installation parameter values.
    HTTPS as Default for Target URL
    Select this option for the target to use the HTTPS server URL to communicate with the server. The enforce.secure.endpoint.callhome and enforce.secure.endpoint.upload properties in the trc.properties file are also set to true. If not selected, the HTTP URL is used. Regardless of your selection, the enforce.secure.web.access, enforce.secure.weblogon, and enforce.secure.alllogon properties that enable HTTPS logon and access to the web portal, are all set to True by default. For more information about these properties, see Set a secure environment .The check box is selected by default on a new installation.
    Note: For HTTPS, you must use a fully qualified domain name in the Address of the Websphere server field.
    Use secure registration tokens to register targets
    Select this option to enable the secure target registration feature. This feature prevents unauthorized targets from registering with the Remote Control server. Ensure that the HTTPS as Default for Target URL option is also selected. For more information about secure registration, see Enable secure target registration..
    Address of the WebSphere® server
    The fully qualified name for the Remote Control server. For example, trcserver.example.com.
    Note: Enter the fully qualified name. This name is used to create the URL in the trc.properties file that is passed to the target when it contacts the server for the first time. If the fully qualified name is incorrect, the target might be unable to contact the server successfully when it is next due to contact it.
    Web path of URL
    Specify the web path for the server URL, http://trcserver.example.com/webpath. For example, trc. http://trcserver.example.com/trc
    HTTP port
    Specify a port for the server. Default is 80.
    HTTPS port
    Specify a port if you are using SSL. Default is 443.
    Administrator email
    Specify an administrator email address. For example, admin@company.com
    Note: To use the email function within the Remote Control server, a mail server must be installed. For more information about enabling email, see the BigFix® Remote Control Installation Guide.
    Enable FIPS
    Select to enable FIPS compliance on the server. For more information about enabling FIPS compliance, see the BigFix® Remote Control Installation Guide.
    Enable NIST SP800-131A compliance (Enables FIPS)
    Select this option to enforce NIST SP800-131A compliant algorithms and key strengths for all cryptographic functions. For more information about enabling NIST SP800-131A compliance, see the BigFix® Remote Control Installation Guide.
    Adjust some advanced web parameters
    Select this option to set extra port values.
  5. Save the configuration by completing the following steps:
    1. Click Create Server Installation Task
    2. Complete the relevant information for your task and click OK.