Before you begin the full PCO installation, you need to define several Oracle 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. schemas to
You need several Oracle user schemas to access the various databases that are required to work with PCO. Specifically, you need all the following:
If you plan to set up additional EventBases that connect to an additional source systems (AE or AM databases), you need additional users for each combination of EventBase and source system.
SQL Scripts for creating users
SQL scripts for creating the necessary Oracle users are included in the PCO/PDA package, which you extracted in the steps "Download the PCO Package." To find the scripts:
Go to the folder where you extracted the Policy Orchestrator files.
Open the folder Tools\Oracle.
Instructions for creating each user using the related scripts are described below.
Prerequisite privilege
To run the scripts, you must have a user with the SYSDBA privilege on the various Oracle systems.
Use these steps when your the system with the source data is in an Applications Manager database and the database is an Oracle database. If your source data is an Oracle database for Automation EngineA separate product that can be used to control, administer and operate an Automic system. You can define and schedule objects that run processes and activities on different hosts., see the steps "Create Oracle Users."
Go to the folder where you extracted the Policy Orchestrator files.
Open the folder Tools\Oracle.
Run the script CreateUserAndSynonymsForAM.sql with the following parameters:
This will create a user with read-only access to the Applications Manager database.
Example:To create a user called AMREADER
with the password mypassword
that can read data from the schema AM_SCHEMA
on the host PCOINSTANCE
, you would run sqlplus with this statement:
sqlplus sys@PCOINSTANCE as sysdba CreateUserAndSynonymsForAM.sql AMREADER mypassword AM_SCHEMA
In Oracle, assign the user the CONNECT role.
To create the user to access the Admin database, use the following steps.
Go to the folder where you extracted the Policy Orchestrator files.
Open the folder Tools\Oracle.
Run the script CreateOracleUser.sql with the following parameters:
This will create a user with read and write access for the Admin database.
Example:To create a user called PCOADMIN
with the password mypassword
on the host PCOINSTANCE
, you would run sqlplus to connect the user to the database instance for PCO/PDA with the following statement:
sqlplus sys@PCOINSTANCE as sysdba CreateOracle.sql PCOADMIN mypassword
Note: You use the same script if you want to create a user for the EventBase database, who might need an additional role and privilege if you want to enable full text search. If you want to create the schema with different settings (for example a different tablespace), you can modify the script as you need.
In Oracle, assign the user the rightsRights in the user management functions in the AWI refer to user access rights to main object types and custom types in the Release Manager. These rights can be granted to either only read or also create these types.:
Roles:
Privileges
Object privilege
Object Privilege | Schema | Object |
---|---|---|
EXECUTE | CTXSYS | CTX_CLS |
You need one EventBase for each source system database (AE and/or AM database).
When you install PCO/PDA, you define one EventBase for each source system database (AE and/or AM database). You need an Oracle user to access the EventBase databases. You can use the same user for more than one EventBase or have individual users for each EventBase. Nevertheless, if you have multiple EventBases, then you have to run the script once for each EventBase.
Note for a standalone installation: If your are installing the Admin database and the EventBase(s) on the same Oracle database, then you need only one user. So, after running the script for the Admin database in "Create a User/Schema for the Admin Database," you can skip the steps below.
Use the following steps to create the access user for each EventBase.
Go to the folder where you extracted the Policy Orchestrator files.
Open the folder Tools\Oracle.
Run the script CreateOracleUser.sql with the following parameters:
This will create a user with read and write access to the related EventBase database.
Example:To create a user called PCOEVENTBASE
with the password mypassword
on the host PCOINSTANCE
, you would run sqlplus to connect the user to the database instance for PCO/PDA with the following statement:
sqlplus sys@PCOINSTANCE as sysdba CreateOracle.sql PCOEVENTBASE mypassword
Note: If you want to create the schema with different settings (for example a different tablespace), you can modify the script as you need.
In Oracle, assign the user the rights:
Roles:
Privileges
Object privilege (needed for fulltext indexing in PDA)
Object Privilege | Schema | Object |
---|---|---|
EXECUTE | CTXSYS | CTX_CLS |
Next steps: You are now ready to install the full PCO and PDA package. Start with Step 1 - Starting the Installation.
Automic Documentation - Tutorials - Automic Blog - Resources - Training & Services - Automic YouTube Channel - Download Center - Support |
Copyright © 2019 Automic Software GmbH |