Deploying the ArcSight Capabilities

The registry credentials have an expiration deadline of 1 hour after creation. If more time than that has elapsed, make sure to refresh the credentials before running this procedure.

After you install the OMT Installer, complete the following steps to configure the cluster and then install the ArcSight capabilities.

  1. Use your remote desktop to access the jump host.
  2. Browse to the cluster using your private DNS address at port 3000.

    3. For example:

    https://installer.private.arcsight.com:3000
  3. Log in using admin (user ID) and the password you specified during the OMT installation.

    4. The system prompts you to upload the following ArcSight installer metadata.tar file:

    arcsight-suite-metadata-<version>.xx.tar
  4. On the Security Risk & Governance - Container Installer page:
    1. Select the OMT base product metadata version.
    2. Click Next.

  5. On the End User License Agreement page:
    1. Review the End User License Agreement.
    2. To accept the agreement, select the I agree… check box.
    3. (Optional) To have information passed to OpenText, select the I authorize... check box.
    4. Click Next.

  1. From the Suite Metadata Upload screen, select the metadata file versions for the release you will be installing. For more information about those files, please refer to the Release Notes for ArcSight Platform 23.3.
  2. On the Capabilities page:
    1. Select the checkboxes corresponding to the capabilities you wish to install. For example, to install ArcSight Recon, select the ArcSight Recon check box. The list of capabilities shown depends on products purchased by your organization, but can include Transformation Hub, Fusion, ArcSight Recon, ArcSight Intelligence, and ArcSight ESM Command Center.
      2. Other products might require Transformation Hub or other capabilities as prerequisites. You can view any such requirements in the pull-down text associated with the capability.
    2. To show additional information associated with the capabilities, click the > (greater than) arrow.
    3. Click Next.
  3. On the Database page:
    1. Ensure the PostgreSQL High Availability box is unselected. This database is not used by ArcSight capabilities.
    2. To continue, click Next.

      3.  

  4. On the Deployment Size page:
    1. Based on your planned implementation, select a size for your deployment. (You can configure additional nodes, each running on their own host systems, in subsequent steps.)

      2.  

    2. Click Next.
  5. On the Connection page:
    1. In External Hostname, the deployment populates an external hostname automatically from the value provided in the --external-access-host parameter, specified earlier during the installation of OMT.
    2. Confirm the port is correct.
    3. To continue, click Next.

      4.  

  6. On the File Storage page, for each NFS volume to configure:
    1. In the File System Type drop-down, ensure Managed NFS is selected.
    2. In File Server, specify the IP address or FQDN for the NFS server.
    3. From the Exported Path drop-down, select the appropriate volume. For example, when using NetApp, specify the path manually instead: /nfs/arcsight-volume, /nfs/db-backup-vol, /nfs/db-single-vol, /nfs/itom-logging-vol itom-vol. Filling out the volume path for arcsight-volume, and clicking the auto-fill slider (in the upper right corner) will fill out the remaining paths.
    4. Click Next. All volumes must validate successfully to continue with the installation. The following volumes must be available on your NFS server.

      5. OMT NFS Volume Claim

      Your NFS volume

      itom-vol

      		<NFS_ROOT_FOLDER>/itom_vol

      db-single-vol

      <NFS_ROOT_FOLDER>/db-single-vol

      itom-logging-vol

      <NFS_ROOT_FOLDER>/itom-logging-vol

      arcsight-volume

      <NFS_ROOT_FOLDER>/arcsight-volume

    5. Click Next.

      6. After you click Next, the infrastructure implementation is deployed. Please ensure that your infrastructure choices are adequate to your needs. An incorrect or insufficient configuration might require a reinstall of all capabilities.

  7. On the Confirm dialog, to start deploying the nodes, click Yes.

    8.  

    After all nodes have been configured, and all services have been started on all nodes, the Preparation Complete page displays. You are now ready to configure product-specific installation attributes.

    If the installation of the products seems to stall, check the logs for this message:
    mkdir: cannot create directory 'data/pg-data-backup/log': Permission denied

    If this message is found, you will need to manually reassign the NetApp volumes permissions by running these commands: 
    cd  <NFS_ROOT_FOLDER>
    chown -R 1999:1999 itom-vol

    After the permissions have been reassigned, the itom-pg-backup pod will start running and the suite deployment will finish successfully.