Full Installation of Policy Orchestrator > Step 3 - Connecting the Data Sources and Configuring the EventBases > Configuring the Source Connection (UC4 System)

Configuring the Source Connection (UC4 System)

This step is only relevant if you want to use an Applications Manager (AM) as source.

The source system database can be a Applications Manager (AM) database.

Relationship of source system database and Eventbase databases

Typically, you define one EventBase for each source system database. You could also define more than one EventBase for a single source system database. In this case, all EventBases are loaded with the relevant data from the source database. What you should NOT do is to have more than one source database write to the same EventBase, because then the data will be mixed and provide irrelevant results.

Prerequisite considerations

Your source database could use an Oracle DB for AM. Depending on the configuration the following cases may be considered to be able to establish a connection:

Consideration/Situation Additional Requirement
To establish a connection to the source system via OLE DB An appropriate OLE DB Provider is required for the database (Oracle Provider for OLE DB)
To use ODBC for the connection to the source system, An appropriate ODBC Driver for the relevant database is required (Oracle ODBC Driver).

Steps:

You configure the connections to source databases in the section "UC4 System".

  1. In the "EventBases" section, click the "UC4 System" tabTabs allow you to structure the Main Pane in several overlapping sections that are all open at the same time but are viewed one at time..

  2. Click the Add button to attach a new UC4 System (AM database).

    A dialog appears for entering a name for the EventBase that the source system data will be sent to. Enter a Name for the EventBase system and select the source system application Type.

    Configuration: Connection to the Source Database

  3. Select the database type and connection type

    For access to the source system database, the specified data base userA user is an instance of a User object in the Automation Engine, and generally the user is a specific person who works with Automic products. The user object is assigned a user ID and then a set of access rights to various parts of the system and product suite. These access rights come in the form of Automation Engine authorizations and privileges, Decision user roles and EventBase rights and Release Manager object rights. You can manage all these centrally in the AWI user management functions. See also, Unified user management. needs at least the following permissions:

  4. Enter the connection parameters (Server Name, User, Password, etc.).

    For Oracle RAC installations: Automic does not recommend installing PCO on a RAC cluster, but if you do (at your own risk), then enter the SCAN name (Single Client Access Name) instead of a host name in the Host field.

    Configuration of the Source Database Connection

  5. To test the connection settings now, click the Test Connection button.

 


Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support

Copyright © 2019 Automic Software GmbH