NetIQ Cloud Manager Installation and Upgrade Guide
- NetIQ Cloud Manager Installation and Upgrade Guide
- Preparing for Cloud Manager Installation
- Installation Checklist
- Cloud Manager System Requirements
- Cloud Manager Licensing Requirements
- Cloud Manager Orchestration Server Requirements
- Cloud Manager Orchestration Agent Requirements
- Cloud Manager Orchestration Console Requirements
- Cloud Manager Application Server Requirements
- Cloud Manager Application Console Requirements
- Cloud Manager Monitoring Agent Requirements
- Requirements and Cloud Manager Support for the Virtual Environment
- Choosing the Installation Patterns and Where to Install Them
- Cloud Manager Orchestration Server Installation Pattern
- NetIQ Cloud Manager Installation Pattern
- Cloud Manager Monitoring Server Installation Pattern
- Cloud Manager Orchestration Agent Installation Pattern
- Cloud Manager Monitoring Agent Installation Pattern
- Cloud Manager Orchestration Console Installation Pattern
- Orchestration Components Preinstallation Tasks
- Gathering Certificate and License Information
- Preparing the Server When Multiple NICs and DNS Addresses Exist
- Component Installation
- Installing Cloud Manager Orchestration Components
- Installing Orchestration Components on SLES
- Alternative Installation Methods for the Orchestration Agent
- Alternative Installation Methods for the Orchestration Console and Clients
- Alternative Installation Methods for the Cloud Manager Monitoring Agent
- Installing Cloud Manager Application Server Components
- Installing Cloud Manager Pattern on Your SLES Server
- Standard Cloud Manager Component Configuration
- Configuring Cloud Manager Orchestration Components
- Configuring the Orchestration Server
- Configuring the Monitoring Server and Monitoring Agent
- Configuring the Orchestration Agent
- Validating and Optimizing the Orchestration Installation
- Configuring Connections to the Cloud Manager Application Server
- Enabling a Secure Connection
- Enabling a Non-Secure Connection
- Launching the Orchestration Console and Logging in to the Orchestration Server
- Launching the Orchestration Console
- Logging In Explicitly to a Named Server
- Creating a Resource Account
- Opening the Resources Monitor
- Automatically Registering a Resource
- Selecting a Resource for Manual Registration
- Manually Registering a Resource in the Orchestration Console
- Configuring Orchestration Provisioning Adapters
- Configuring the vSphere Provisioning Adapter
- Configuring Sysprep or Autoprep
- Understanding and Configuring Sysprep
- Understanding and Configuring Autoprep
- Using the Cloud Manager Application Server Configuration Tool
- Configuring the PostgreSQL Database Connection and Credentials
- Configuring Cloud Manager to Use Authentication Sources
- Installing and Configuring Other Cloud Manager Feature Settings
- Advanced Installation and Integration Topics
- Preparing the Cloud Manager Orchestration Server for SUSE High Availability Support
- Overview
- Orchestration Server Failover Behaviors
- Installing the Orchestration Server to a SLE High Availability Cluster Environment
- Configuring the Orchestration Server for High Availability
- Installing and Configuring Orchestration Server Packages for High Availability on Other Nodes in the Cluster
- Creating the Server Cluster Resource Group
- Testing the Failover of the Orchestration Server in a High Availability Grid
- Installing and Configuring other Orchestration Components to the High Availability Grid
- Configuring the Orchestration Server to Use an Audit Database
- Installing the PostgreSQL Package and Dependencies on an Independent Host
- Configuring PostgreSQL to Accept Remote Database Connections
- Logging in Locally to the PostgreSQL Database
- Creating an Orchestration Server User for the PostgreSQL Database
- Configuring the Orchestration Server Audit Database on a Separate Host
- Installing and Configuring the Orchestration Server for Use with a Local PostgreSQL Audit Database
- Configuring the Audit Database after the Cloud Manager Orchestration Server Is Configured
- Configuring the Remote Audit Database after the Cloud Manager Orchestration Server Is Configured
- Modifying Audit Database Tables to Accommodate Long Names
- Understanding Grid ID Usage in the Audit Database
- Integrating the Orchestration Server with a Sentinel Collector
- Integration Architecture
- System Requirements
- Importing and Deploying the Orchestration Server Sentinel Collector Plug-in
- Connecting the Orchestration Server to the Sentinel Collector Plug-In
- Verifying the Sentinel Configuration After Connecting to the Orchestration Server
- Event Classification and Taxonomy Keys
- Plain Text Visibility of Sensitive Information
- Configuring Secure Authentication Sources to Communicate with Cloud Manager
- Configuring NetIQ Access Manager to Work with Cloud Manager
- Upgrading
- Orchestration Components Upgrade Overview
- Basic Functions of the Orchestration Components Upgrade
- Cloud Manager Orchestration Components That Are Not Upgraded
- Upgrading Cloud Manager Orchestration Components
- Upgrading Orchestration Components
- Alternate Methods for Upgrading Older Agents and Clients
- Running the Upgrade Configuration on an Enterprise Scale
- Upgrading a Cloud Manager Orchestration High Availability Configuration
- Upgrading the Cloud Manager Application Server Components
- Backing Up the PostgreSQL Database
- Performing a Complete Cloud Manager System Backup
- Running the Cloud Manager Configuration Script
- Restoring Cloud Manager In the Event of a System Failure
- Compatibility Checking Behavior for Orchestration Components
- If the Orchestration Server Is Not Compatible with the Orchestration Console
- When an Agent Version Does Not Match the Server Version
- How to Recover from a Failed Orchestration Server Upgrade
- Upgrade Failure Scenarios
- Uninstalling
- Uninstalling Orchestration Component Patterns from a SLES Server
- What’s Next?
- Legal Notice