Previous Topic: Run the H2 Database RestoreNext Topic: How to Change the Cost Analysis Configuration

Discipline-Specific Administration Tasks

Discipline-Specific Administration Tasks

How to Add or Remove Storage Engines

CA Chorus connects to each storage engine subsystem through TCP/IP to display object data in the interface. To add or remove storage engine subsystems to CA Chorus, follow these steps:

Note: The storage engine subsystem must be installed and configured before you add it. For more information, see the CA Chorus for Storage Management Site Preparation Guide.

  1. Stop the CA Chorus task (the JBoss server) by entering the following console command: 
    P CHORJBOS

    A message indicating that the JBoss server started task has ended is logged.

  2. Open the E4HI0010 job for editing. The E4HI0010 job is located in the chorusstor_runtime_hlq.CE4HJCL data set.
  3. Replicate the datasource_name line in the E4HI0010 job for each storage engine subsystem that you want to add, or remove datasource_name lines for the storage engine subsystems

    In a multiple storage engine subsystem environment, one storage engine is chosen as the Main (storage) Engine in the CA Chorus Investigator. The Main Engine provides CA Chorus with storage object attributes, which include storage object table header information, the available Administrative Actions for the object, relationships to other objects, and so on.

    CA Chorus determines the Main Engine during JBoss startup. This determination depends on the order of the storage engines that are defined in the E4HI0010 job and if CA Chorus can receive data from the storage engines. That is, the first storage engine that is listed in the E4HI0010 job defaults as the Main Engine during JBoss startup. If a connection to this storage engine is not available during JBoss startup, CA Chorus sets the next storage engine that is listed in the E4HI0010 job as the Main Engine and tries to connect to it. The Main Engine repeats this process until it finds a storage engine to which it can connect and receive data from.

    To use all storage engine features, the Main Engine must have the latest CA Vantage SRM maintenance applied.

    Verify the first storage engine listed in the E4HI0010 job contains all user-created Summary Objects, Joined Objects, and so on, and that CA Chorus can connect and receive data from the first storage engine listed in the E4HI0010 job during the JBoss server startup.

    Note: For more information about multiple storage engines, see the CA Chorus for Storage Management User Guide.

    Note: We recommend a maximum of eight storage engine subsystems. If you configure more than eight, you receive a warning message when running the E4HI0010 job. Despite this message, all of your servers will be configured as requested.

  4. Substitute the following variables in each replicated datasource_name line:
    datasource_name

    Any descriptive name for each storage engine subsystem (maximum 12 characters). Assign each storage engine subsystem with a unique datasource_name value. This value is case-sensitive. That is, if you enter it in upper-case, it must be specified as upper case in the Storage Management interface's My Profile Host definition. The value of the datasource_name variable is displayed in the HOST column of the Investigator in the object table when the object table is populated with data from multiple hosts.

    Note: Record the datasource_name values, exactly as you enter them in this job. You need them later when creating public host connection definitions in the Storage Management interface.

    The Storage Management interface accessed from the Quick Links module has only one authenticating host that is used as the single-sign on to this interface. The interface authenticating host name is specified in the vantage.web.client.host.name in the CETJOPTN (ENVE4H) member. The value of the datasource_name and vantage.web.client.host.name can be the same but it is not required.

    ip_address_or_host_name

    The network name or IP Address the storage engine subsystem is running.

    port

    The TCP/IP port number that the storage engine subsystem is listening on for connection requests. This value is set in parameter TCPPORT within each VKGPARMS member of each storage engine subsystem parameter library.

  5. Save and submit the E4HI0010 job.
  6. Submit either the $TJI0150 or ETJI0150 job in CETJJCL to update the data source XML files with the storage engines.
  7. Start the CA Chorus task (the JBoss server): 
    S CHORJBOS

    A message indicating that the JBoss server is initialized is logged.

The storage engine subsystems are defined for CA Chorus.