Configurations Overview

This document provides information on how to set up the HPE Codar Console and HPE Codar in order to enable users to log in and use the Codar Console . Some tasks must be completed before you can start using Codar.

The user who sets up  Codar should have knowledge of or work with someone who has knowledge of LDAP, TLS, HPE Operations Orchestration, and the resource providers that will be integrated with  Codar.

Note If you have added the HPECloud Service Automation license, you have access to all of the Cloud Service Automation functionality, such as global search and reporting database user. For details see the Cloud Service Automation Configuration Guide.

The following information is provided in this document:

Getting Started. Before setting up the Codar Console, you may need to complete some initial configuration such as preparing LDAP, configuring Codar truststore properties, and requesting a software license.

Secure Connections. Many of the components that interact with Codar may require communication over a secure connection. You may want to replace the Codar self-signed certificate or configure a secure connection for LDAP, SMTP, the Oracle Database, the Microsoft SQL Server, or the Operations Orchestration Load Balancer.

Operations Orchestration. A process engine whose flows are executed by Codar, Operations Orchestration must be integrated with Codar and sample flows must be imported before the flows can be executed.

The Codar Console. To set up the Codar Console so that users can log in, you must configure the provider organization. In order to start using the Codar Console, you must add a software license. You may wish to import the sample service designs provided with Codar, configure a proxy, or enable or customize sidebar menu items in the Codar Console.

Common Codar Tasks. Common tasks include launching the Codar Console, starting, stopping, or restarting Codar, encrypting an Codar password, and uninstalling Codar.

User Administration. User administration includes tasks such as changing the out-of-the-box users. On Windows, also allows non-administrator users to start and stop Codar services.

IPv6 Configuration. Configure Codar to support IPv6 (both dual-stack and IPv6-only).

Common Access Card. Common access cards are used for user authentication and allow users to log in to Codar using a Personal Identity Verification card.

Single Sign-On. Enable or disable Single Sign-On that is included with Codar. Single sign-on can also be configured for the Codar Console with almost any single sign-on solution and a specific solution for CA SiteMinder is provided.

FIPS 140-2 Compliance. FIPS 140-2 is a standard for security requirements for cryptographic modules defined by the National Institute of Standards and Technology (NIST). Codar can be configured for FIPS 140-2 compliance.

Database Administration. Database administration includes any task that might involve the database, such as configuring the Codar reporting database user if you did not configure it during installation, updating Codar database system or users and passwords, importing large archives, purging service subscriptions, installing the Codar database schema, and configuring Codar to mitigate frequently dropped database connections.

Codar Console Properties. This is a reference to the Codar Console configurable properties.

Operations Orchestration Settings. This is a reference to the Operations Orchestration configurable settings applicable to Codar.

Identity Management Configuration. This is a reference to the Identity Management component configurable settings applicable to Codar.

See the following guides for more information:

  • Codar: Codar Concepts Guide
  • Supported components and versions: Codar System and Software Support Matrix
  • Installation: Codar Installation and Configuration Guide
  • Upgrade: Codar Upgrade Guide
  • Configuration: Codar Configuration Guide
  • Codar Console: : Codar Console Help