Table of Contents

Search

  1. Preface
  2. Installation Overview
  3. Pre-Installation Tasks
  4. Hub Store Installation
  5. Hub Store Post-Installation Tasks
  6. Hub Server Installation
  7. Hub Server Post-Installation Tasks
  8. Process Server Installation
  9. Process Server Post-Installation Tasks
  10. ActiveVOS Post-Installation Tasks for the Application Server
  11. ActiveVOS Post-Installation Tasks for the Business Entity Adapter
  12. Resource Kit Installation
  13. Troubleshooting the MDM Hub
  14. Uninstallation

Installation Guide for Oracle Database with Red Hat JBoss

Installation Guide for Oracle Database with Red Hat JBoss

Step 4. Create the ActiveVOS Schema

Step 4. Create the ActiveVOS Schema

To install ActiveVOS, you need to create the ActiveVOS schema. To create the schema, run the
create_bpm
script.
If you want to create multiple MDM Hub Master Databases, create an ActiveVOS schema for each MDM Hub Master Database.
If you want to use the Oracle multitenant feature, create the ActiveVOS schema in a pluggable database (PDB).
  1. Open a command prompt and change to the following directory:
    <
    MDM Hub distribution directory
    >/database/bin
  2. Run the following command:
    On UNIX.
    ./sip_ant.sh create_bpm
    On Windows.
    sip_ant.bat create_bpm
  3. Answer the prompts that appear.
    The prompt displays default text in brackets. Press
    Enter
    to use the default value and go to the next prompt.
    Property
    Description
    Database Type
    The type of database. For an Oracle database, specify
    Oracle
    . The database type must be the same as the database type selected for the MDM Hub Master Database and the Operational Reference Stores.
    Oracle Connection Type
    Connection type. Use one of the following values:
    • SERVICE. Uses the service name to connect to Oracle.
    • SID. Uses the Oracle System ID to connect to Oracle.
    ActiveVOS Database Host Name
    Name of the machine that hosts the database.
    ActiveVOS Database Port
    Port number that the database listener uses.
    Database Service Name
    Name of the Oracle service. This property is required when the selected Oracle connection type is SERVICE.
    Oracle Net Connect Identifier (TNS Name)
    Oracle TNS name.
    Database SID
    Name of the Oracle System ID. This property is required when the selected Oracle connection type is SID.
    DBA User Name
    User name of the database administrative user.
    DBA Password
    Password of the administrative user.
    ActiveVOS User Name
    User name of the ActiveVOS Server administrative user.
    ActiveVOS User Password
    Password of the administrative user.
    ActiveVOS User Tablespace
    The name of the tablespace that contains the records that are involved in MDM workflows.
    ActiveVOS User Temp Tablespace
    The name of the temporary tablespace.
  4. After you create the schema, review the
    sip_ant.log
    file in the following directory:
    <
    MDM Hub distribution directory
    >/database/bin
    The
    sip_ant.log
    file logs any errors that might occur when you run the
    sip_ant
    script to create the ActiveVOS database schema.

0 COMMENTS

We’d like to hear from you!