› KCM Installation Guide › Manual component installation › Adding Batch & Output Management

Adding Batch & Output Management

This section describes the Batch & Output Management (B&OM) installation that results in a B&OM installation to a single server in a dedicated folder.

Using a command-line tool AddOutputManagement.exe you can add a Batch & Output Management to an existing KCM installation.

Batch & Output Management can only be installed on server.

AddOutputManagement.exe doesn't install B&OM in a running state. You can find the instructions on running this component in the Starting B&OM section of this guide.

Since B&OM is an extension of KCM, it requires a KCM installation of the same version to be present in the organization. If B&OM is installed on the same server as a KCM instance, it will be configured automatically to connect to that instance (or the first instance if multiple ones are present).

If B&OM is installed remotely or if it needs to be connected to a specific instance, you should configure its connection as described in the Connecting B&OM to KCM Instance section of this guide.

Distributed B&OM installation

This section describes an option of distributing a single B&OM installation over multiple machines.

Such installation is created by extending a primary B&OM installation with one or more secondary B&OM installations. A distributed B&OM setup shares a single configuration amongst its installations, as well as the storage folder. In order to create such a setup, you need to set up a primary installation that enables you to share the configuration and storage folder, and then set up the secondary installations.

Additional requirements

This section lists the prerequisites and preparatory steps you have to take before you run AddOutputManagement.exe.

Before you start, make sure that your environment satisfies the general KCM installation requirements.

Batch & Output Management requires two databases:

  • A database for the B&OM Repository
  • A database for the runtime information
  1. Databases must be created manually, with case-insensitive collation.
  2. Databases must be empty.
  3. Two user accounts for database access. They must be specified with the OutputManagement!RepositoryDatabaseUser and OutputManagement!RuntimeDatabaseUser deployment parameters.
  4. In case of using SQL Server, both accounts must satisfy the following conditions:
    • database owner role
    • ALTER_TRACE privilege
  5. For Oracle databases, both accounts must have the following privileges:
    • CREATE SESSION
    • CREATE TABLE
    • ALTER SESSION
    • CREATE VIEW
    • CREATE PROCEDURE
    • CREATE SEQUENCE
  6. In addition, the user account for the B&OM Repository database (specified with the OutputManagement!RepositoryDatabaseUser parameter) must have the following privileges:
    • CREATE TYPE
    • CREATE TRIGGER
    • EXECUTE ON DBMS_LOCK
    • EXECUTE ON DBMS_LOB
    • EXECUTE ON DBMS_OUTPUT
    • EXECUTE ON CTX_DDL