Running ODEE Installer

In this stage, you run the setup application to install ODEE. You will be prompted to enter the information listed on the previous topic.

During the initial installation, the system creates a registry setting that identifies the Oracle Home directory. This directory is the location of where ODEE will be installed.

Note:

During the installation process:
  • You are prompted to enter various required values. If you need help completing these values, contact the appropriate system administrator.
  • A set of sample resources are provided. These resources let you deploy the example or Reference Implementation MRL (RI-MRL Correspondence) which the configuration is already setup to function.
Follow these steps to run the Installation:
  1. From the installation package, on the Application Tier run.
    Windows: setup.exe
    Linux/Solaris: ./runInstaller

    Note:

    See Oracle Universal Installer (OUI) User’s Guide for Command-Line options
  2. On the Welcome installer screen click Next

    Note:

    The first time you run an Oracle Installation it will request the location of the Oracle Inventory via the Specify Inventory Details Window screen. Review the information and modify if necessary and click Next.
  3. On the Specify Installation Location installation screen, enter the Installation Path and click Next.

    The defaults:

    For Windows: c:\oracle\odee_1

    For Linux/Solaris: /u01/data/domains/odee_1

    Note:

    The name of the installation directory cannot exceed 44 characters. The Oracle limit is 64 characters, but Documaker appends 20 characters to the path.
  4. On the Specify Administrator Group and User installation screen, enter the data and click Next:
    Field Description
    Group Enter the group name. This provides the installation user with control over initial Administration group and Administration user
    User Enter the user name for the Administrator Group.
    Password Enter the password for the Administrator Group.
    Confirm Password Re-enter password to confirm.

    Note:

    With default WebLogic install and steps, we populate the WebLogic internal LDAP repository with these values and deploy the example/sample to web app users, so that users can get into Dashboard and Administrator, or optional DI if installation was done without any example users.
  5. On the Database Server Details installation screen, indicate the database you will use and click Next:
    • Oracle
    • SQL Server
  6. On the Database Server Details window, enter data and click Next:
    Field For an Oracle database For a DB2 database For SQL Server
    Host The host name or static IP address of the database server. The default is the computer where the installation is running from. The host name or static IP address of the database server. The default is the computer where the installation is running from. The host name or static IP address of the database server. The default is the computer where the installation is running from.
    Port The port number of the database; the default is 1521. The port number of the database; the default is 50000 The port number of database; the default port is 1433.
    Database Oracle Database Name of the database to which ODEE will be connected; the default is IDMAKER Name of the database to which ODEE will be connected; the default is IDMAKER
    Advanced Compression True* n/a n/a

    Note:

    * The scripts enable advanced compression on certain database columns. If you do not have an Advanced Compression Options license for Oracle 11g, please remove the COMPRESS DEDUPLICATE and COMPRESS HIGH DEDUPLICATE attributes from the scripts in dmkr_asline.sql.
  7. The Administration Schema Details installation screen contains settings for configuring the Administration Schema where the configuration date is stored. On this screen enter the data and click Next:
    Field Description
    DB Index Folder The database folder where the physical database index files will be created.

    Note:

    This is applicable only for SQL server DB.
    DB Folder The database folder location where the physical database files will be created. If blank, the database folder (directory) is created in the working directory of the database installation. For an Oracle database, this is honored. For a DB2 LUW database, this is only honored if you uncomment the dmkr_admin schema portion and create database section to reference another DB Folder location or enable this setting when the DBA creates the database in DB2.
    User Enter the user name/schema name. The application will use to connect to the database for the Administration System DB schema. The default is dmkr_admin. In the case of DB2 database, the user name must be less than 8 characters, is case sensitive and must preexist where DB2 server expects it for authentication (e.g. OS user by default).
    Password The password for the user name the application will use to connect to the database. The default is Admin12.
    Confirm Password Re-enter the password to confirm.
    System ID A unique system ID for this Document Factory instance. If other Document Factory instances (not Assembly Lines) are installed, they also require a unique system ID. For initial installations, accept the default of one (1).
    System Name This is the display name for the Document Factory instance within the Documaker Administrator. The default is System 1. Change this name to reflect the Document Factory system in your organization.
  8. The Assembly Line Schema Details installation screen contains settings for configuring the Assembly Line schema where the Assembly Line processing (live) tables and historical tables are stored. On this screen enter the required data and click Next:
    Field Description
    DB Index Folder The database folder where the physical database index files will be created.

    Note:

    This is applicable only for SQL server DB.
    DB Folder The location where the physical database files will be created. If you leave this field blank, the database folder is created in the working directory of the database installation.
    User Enter the user name and schema name. The application will use to connect to the database for the Assembly Line schema. The default is dmkr_admin. In the case of DB2 database, the user name must be less than 8 characters, is case sensitive and must preexist where DB2 server expects it for authentication (e.g. OS user by default).
    This user name is also used for the:
    • Database schema/owner
    • JDBC data source name
    • ODBC data source name
    • Name applied to the Docupresentment service (docupresentment dmkr_asline)
    Password This is the password for this assembly line database. The default for Oracle DB and SQL Server is Asline12. This password is also the Documaker Studio password for the Docucorp user.
    Confirm Password Re-enter the password to confirm.
    Assembly Line ID This is the ID for this Assembly Line. If other assembly lines are installed, they require a unique Assembly Line ID. For initial installations, accept the default of one (1).
    Assembly Line Name The display name for the Assembly Line instance within the Documaker Administrator. The default is Assembly Line 1. Change this name to reflect the name of the assembly line in your organization.
  9. The Application Server Details installation screen contains settings for connecting and deploying ODEE web application server resources and applications to WebLogic.

    The installer provides a weblogic_installation.properties file with this information, for use by the two (convenience) methods pre-configured and provided to deploy to WebLogic Server.

    Method 1: wls_extend_clustered_server,

    Method 2: wls_create_domain script.

    Select WebLogic Server and enter the required data and click Next.

    Field Description
    User Web Application Server admin user.
    Password Web Application Server admin user password.
    Confirm Password Re-enter the password to confirm.
    Host Web Application Server Host.
    Oracle Home Path to the WebLogic Server’s Oracle Home (Example: C:\oracle\middleware\wls_home)
    Project Path Path to where the domains are created (Example: c:\oracle\middleware\wls_home\user_projects\domains)
    Admin Server/Port WebLogic Admin Server Name and Port. (typically the Admin SSL port).
    Default Server Name Main Managed Server name to target for the resources and web applications. Will configure in the weblogic_installation.properties file (Defaults to hostname_app_server_1)
    Cluster Name Cluster Name for domain if configured. Required if using wls_extend_clustered_server deployment method. Will configure in the weblogic_installation.properties file. (Defaults to hostname_app_cluster_1)
    Machine Name Machine Name for instance if configured in the domain. Required if using wls_extend_clustered_server deployment method. Will configure in the weblogic_installation.properties file. (Defaults to hostname_node_1)
    Coherence Cluster Coherence Cluster if configured in the domain. Required if using wls_extend_clustered_server deployment method. (Defaults to DataGridConfig)
  10. The JMS Details installation screen contains the JMS values. If you need help with these values, contact your web application server administrator.

    In this installer screen enter the required data and click Next:

    Field Description
    Connection Class The name of the Java class used to connect to the JMS queues. Normally the default value is correct:
    oracle.documaker.bus.messaging.jms.JMSJNDIMessageQueueFactory
    InitialContextFactory A Java class used when connecting to the JMS queues. Normally the default value is correct:
    weblogic.jndi.WLInitialContextFactory
    Provider URL The protocol used to connect to the JMS queues. Normally the default value is correct and should start with protocol t3 or t3s (requiring certificate in Factory JRE from WebLogic), then the host name or IP of the JMS Server and port.
    Example:
    t3s://yourhostname:9002
    Principal If JMS is secured then enter the required ID to connect to JMS. Example: weblogic
    Credentials If JMS is secured then enter the password required to connect to JMS. For WebLogic usually the WebLogic Server Admin account.
    Confirm Credentials Re-enter credentials to confirm.
  11. On the Hot Directory installation screen enter the HotFolder path and click Next. This path can include more than one directory, each separated by a comma.

    This Hot Folder path applies to the Assembly Line in the previous window. The default is:

    Window: ODEE_HOME\documaker\hotdirectory

    Linux/Solaris: ODEE_HOME/documaker/hotdirectory

    Note:

    This directory is monitored for jobs that are waiting to be processed.
  12. (Optional) On the SMTP Email Server Details installation screen enter the data and click Next:
    Field Description
    Host Enter the IP address or server name of the SMTP server.
    Port Enter the port number of the SMTP server.
    User Enter the user name for the SMTP server.
    Password Enter the password for the SMTP server.
    Confirm Password Re-enter password to confirm.
    Sender Enter the email address the SMTP server uses as the sender for any email publication from the Documaker Document Factory.

    The default is: admin@hostname

  13. (Optional) On the WebCenter Information installation screen enter the WebCenter Content settings and click Next:
    Field Description
    Enable Select True to enable documents to be archived to WebCenter. The default is False.
    User Enter the WebCenter user name.
    Password Enter the WebCenter password.
    Confirm Password Re-enter password to confirm.
    Connection String Enter the connection string. Here is an example:

    idc://hostname:4444

    Document URL Enter the document URL. Here is the default:

    http://hostname:16200/cs/groups/secure/documents/document

  14. (Optional) On the UMS Details installation screen enter the User Messaging Services settings and click Next:
    Field Description
    Enable Select True to enable user messaging services. The default is False.
    User Enter the UMS server user name.
    Password Enter the UMS server user password.
    Confirm Password Re-enter password to confirm.
    Endpoint Enter the URL of the UMS server used for notifications.
  15. On the Installation Summary installation screen review your installation settings, space requirements, and availability. To make any changes, click Back. Click on Save to save your changes.

    Note:

    You can save a OUI response file that contains the data entered (except passwords) to be used as input to run installer silently or with GUI with data pre-filled. Useful for standing up additional ODEE Factory instances on other nodes. You can manually add passwords in response file if desired to be used in subsequent installs silently.
  16. Click Install to begin the installation process.
  17. The Install Status installation screen indicates the progress of the installation. To stop the installation process, click Cancel.
  18. If errors occur during the installation, review the installActions[date_and_ time].log file. These are mentioned on the installation screen.

    This file is usually located in this directory:

    Windows: [drive_letter:]\Program Files\Oracle\Inventory\logs\ or in %TEMP%

    Linux/Solaris: /tmp/

    Note:

    These standard out files and error logs are also created during the installation process:
    • oraInstall[date_time].out
    • oraInstall[date_time].err
  19. When the installation process has completed, the Installation complete installation screen appears. Click Finish to close the installation program.