How to: |
This section describes how to install the Omni-Gen Server and the Omni Governance Console (OGC).
This procedure assumes that a database server (for example, Microsoft SQL Server) and a repository server (for example, SVN) are already installed.
Note: Omni-Gen Version 3.16 is packaged with iWay Data Quality Server (DQS) Version 12. When you download Omni-Gen from the edelivery.tibco.com site, you will receive a temporary key for the DQS software. If you need a permanent key, contact Customer Support.
The InstallAnywhere startup window appears.
When the installation is ready to begin, the Introduction pane opens, as shown in the following image.
The Accept License Agreement pane opens, as shown in the following image.
The Choose Installation Folder pane opens, as shown in the following image.
The installer will create a directory named OmniGen in the location you specified.
Note: For Omni-Insurance, it is recommended to use the following location:
C:\omni_insurance\omnigen
The Choose Java Virtual Machine pane opens, as shown in the following image.
The Specify Base Port Number pane opens, as shown in the following image.
The Specify Hostname and Domain pane opens, as shown in the following image.
The default host name is the machine on which you are currently installing.
The Configure Omni-Gen Repository Tomcat Ports pane opens, as shown in the following image.
The Specify Location of Omni-Gen Designer pane opens, which prompts for the parameters that define the location of Omni Designer, as shown in the following image.
The Specify Location of Source Control .jar Files pane opens, which prompts you to select a folder containing the Source Code Control System (SCCS) .jar files, as shown in the following image.
Note: For Omni-Insurance, it is recommended to place these under the omni_insurance directory specified in step 6.
C:\omni_insurance\sccsjars
If you have not created a folder for the SCCS .jar files, then the following message displays:
If you receive this message, click Cancel and then create a new folder. Place the SCCS .jar files in that folder and click Choose in the Specify Location of Source Control .jar Files pane to navigate and select that new folder.
The Select Source Code Control System and Location pane opens, as shown in the following image.
The Specify Location of JDBC .jar Files pane opens, as shown in the following image.
The Configure Omni-Gen Server Databases pane opens, which provides an overview regarding Omni-Gen databases and configuration parameters, as shown in the following image.
The Select the DBMS type of the Remediation Database pane opens, as shown in the following image.
The Enter OGS Database Parameters: Oracle, Postgres, Teradata pane opens, as shown in the following image.
The Verify the Omni-Gen Master Database URL pane opens, as shown in the following image.
Note: For Omni-Insurance, it is recommended to use omni_insurance as the name for the combined OGS and Remediation database.
If you receive a message indicating that your connection test failed, verify that your database name exists in SQL (or the DBMS you are using).
When your database exists and the user name, password, and host are correct, the following message appears, indicating that your connection test passed for the specified database.
The Select the Data Quality DB's DBMS type pane opens, as shown in the following image.
The Enter DQ Database Parameters: Oracle, Postgres, Teradata pane opens, as shown in the following image.
The Verify the Data Quality Database URL pane opens, as shown in the following image.
If the test is successful, then the Data Quality Database Connection Test Passed pane opens, as shown in the following image.
If the test is not successful, click Previous twice, correct the connection parameters, and retest the URL.
The Select the Omni-Gen Server Runtime Protocol pane opens, as shown in the following image.
The Verify the Omni-Gen Server Port Numbers pane opens for your selected runtime protocol, as shown in the following image.
The Install the Controller as a Windows Service pane opens, as shown in the following image.
Note: It is strongly encouraged that you select Yes for ease of administration. If you select Yes, you will be prompted for the service name. You may type the service name in the Controller Service name field, or accept the default value, OmniGen_omniController.
The Verify the Omni-Gen Governance Console's Tomcat Parameters pane opens, as shown in the following image.
The Hostname parameter defaults to the machine on which you are currently installing Omni-Gen.
The Configure OGC Email Server pane opens, as shown in the following image.
In addition, each user who will receive email notifications must have a valid email address in their WSO2 user profile.
Following the Configure OGC Email Server pane, the Preserve or Create New WSO2 Repository pane opens, as shown in the following image.
The Verify the WSO2 parameters pane opens, as shown in the following image.
The Enter WSO2 Certificate Parameters pane opens, as shown in the following image.
The parameters are used to build a unique certificate to secure the Omni Governance Console to the WSO2 communication.
The Verify or change JVM Memory Settings - MD pane opens, as shown in the following image.
The Pre-Installation Summary pane opens.
The Ready To Install pane opens, indicating that the configuration for installation is complete.
The Installing Omni-Gen pane opens, which displays the progress of the installation.
The Executing Installation Script popup displays towards the end of the installation process, as shown in the following image.
The Omni-Gen installation is complete when the Install Complete pane displays, as shown in the following image.
cd \omnigen\omniserver
omni start-controller
Note: When the installation completes, a BUILD Successful message appears, but the startup processing continues for a few minutes. You must wait for the processing to complete before proceeding to the next step.
https://yourhost.yourdomain.com:9500
For example:
https://tcmappsa.ibi.com:9500
Note: You cannot use localhost in the URL.
You are now ready to apply your Omni-Insurance Business Content. For more information, see the Omni-Insurance Business Content Upgrade Guide.
As a prerequisite, the Omni-Gen installer must be run at least once prior to installing Omni-Gen using silent mode. The Omni-Gen installer creates the OmniGenInstall.properties file, which is used by the silent mode installer. The Omni-Gen installer can then be run again in silent mode and it will use the existing properties file as input.
The silent mode installer requires the installation folder as input to locate the properties file. The installation folder is the same folder as specified in the Choose Installation Folder pane of the Omni-Gen installer. However, the folder must already exist and contain the OmniGenInstall.properties file. The folder structure can exist from a previous installation, or it may be newly created. No other folders are required.
Use the following command to run in silent mode:
TIB_oin_3.16.0_win_x86_64.exe -i silent -DUSER_INSTALL_DIR=<installation_folder>
For example, if the OmniGenInstall.properties file is located in the c:\omnigen\install folder, then you would execute the following command:
TIB_oin_3.16.0_win_x86_64.exe -i silent -DUSER_INSTALL_DIR=c:\
To install Omni-Gen using silent mode:
c:\omnigen
c:\omnigen\install
TIB_oin_3.16.0_win_x86_64.exe -i silent -DUSER_INSTALL_DIR=c:\