Topics: |
This section describes how to configure Omni-Gen™ for Customer to quickly get started with using the product. For more information on detailed use of the related product areas, see the corresponding documentation for Omni-Gen™ Master Data Management (MDM) and Data Quality (DQ) Editions.
Note: Omni-Gen services can be managed from a command line prompt that has been launched using the Run as Administrator option or from the Omni Console. Using the Omni Console to manage Omni-Gen services is highly recommended. However, during certain points of the configuration process, Omni-Gen services must be managed (for example, started or stopped) from a command line prompt. In addition, during the configuration process, specific Omni-Gen services must be running (started) while other services are stopped. Please follow the management of Omni-Gen services (for example, starting and stopping) as described in this documentation.
The omni start-xx and omni stop-xx commands are accessible from the following folder:
<omni_install>\omnigen\OmniServer
cd <omni_install>\omnigen\OmniServer
omni start-controller
Note: The controller will take a minute or two to start as it has to initialize the underlying components. It is recommended to start the controller only for the development environment, instead of all of the services using the omni start-all command.
https://host.domain:9500/
Where the host is the host of your machine and the domain is the domain for your machine. The default user ID and password is ibi / ibi.
Note: Since there is no bundle currently deployed, you are not able to start the service for Omni Server (under Data Processing) and the five services listed under Data Quality. These services will be started after a deployed bundle is available.
Simply provide a repository name and keep default values for the remaining parameters.
Right-click in the Project Explorer area, select Import Project, and then click from Release Bundle, as shown in the following image.
C:\omnigen\OmniGenData\OmniCustomer\OmniGenForCustomer.zip
Please wait a minute until the system loads all of the artifacts.
After the project is imported, you will see the model load and can review it, as shown in the following image.
If any changes are made to this project, right-click the Customer project and select Commit, as shown in the following image.
Note: The Commit option is available only if the project has been updated.
This will commit changes to the source management system.
You can now generate a project bundle for deployment.
Please wait a minute for the project bundle to generate.
This process gathers all of the artifacts for DQ, Remediation, Model, OGC, and others, and packages them for deployment into runtime. A deployable project bundle is written to disk as a .zip file.
C:\omnigen\deploymentbundle
Please wait a minute to install as the system must load all of the artifacts and establish all of the repositories.
You will see the deployment steps as they are being executed, as shown in the following image.
Now it is time to start the services.
After all of the services up and running, the system is ready for data load, processing, and data access.
http://localhost:9090/ogc/
Login with your credentials based on your policy access. The default credentials are:
Note: You can customize this view and you can also export or import the definition for sharing. The Mdata file is located in the following directory:
C:\omnigen\OmniGenData\mdata