In TrueSight Capacity Optimization(TSCO), what is the process to share the Share Content Repository Directory and when does it need to be done?

Version 5
    Share This:

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    TrueSight Capacity Optimization


    Capacity Optimization


    TrueSight Capacity Optimization 20.X, 11.0, 10.7, 10.5, 10.3, 10.0



    The TrueSight Capacity Optimization (TSCO) documentation describes that in an environment with multiple Application Servers (AS) the $CPITBASE/repository directory must be shared between all TSCO AS machines in the environment. 

    Is it necessary to share the directory between the AS and ETL Engine (EE) servers? 
    What is the best practice method to share the directory between the AS machines in the environment?





    Q: Does the TSCO $CPITBASE/repository directory need to be shared between the Application Server and ETL Engine Servers?


    No, the $CPITBASE/repository directory just needs to be shared between all TrueSight Capacity Optimization (TSCO) Application Servers deployed for the instance.


    Q: What is the best way to share the $CPITBASE/repository directory between Application Servers when TSCO is first deployed?

    When the TSCO installer is run as the root user it provides an option to mount the   $CPITBASE/repository from a central location or from the TSCO Primary Application Server.  The TSCO installer mounts the shared repository using NFS. 

    The TrueSight Capacity Optimization (TSCO) product documentation describes the process to share the   Content Repository  

    Q: What options are available for sharing the $CPITBASE/repository directory?


    What needs to be shared between all TSCO Application Servers (AS) in an environment is the /[TSCO Installation Directory]/repository directory (which I'll refer to as $CPITBASE/repository).

    There are three different ways that this directory can be shared:

    1. By NFS mounting the $CPITBASE/repository from the Primary AS onto the Secondary (Web) AS
    3. By creating the $CPITBASE/repository directory on a 3rd machine and mounting it via NFS as $CPITBASE/repository on both the Primary AS and Secondary (Web) AS.
    5. By defining the $CPITBASE/repository as a clustered file system which is then simultaneously mounted on multiple servers

    Verify also that both the server can access to this folder (and all subfolder) in rw mode

         Legacy ID:KA426133


      Article Number:


      Article Type:

      Solutions to a Product Problem

        Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles