Search for	Example	Results
A single word	`cat`	Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".
A phrase. You can specify that the search results contain a specific phrase.	`"cat food"` (quotation marks)	Topics that contain the literal phrase "cat food" and all its grammatical variations. Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.

Search for	Operator	Example
Two or more words in the same topic	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Cloud Service Automation4.80

Administer > Configuration > Integrate CSA with HPE UCMDB

Integrate CSA with HPE UCMDB

This chapter describes how to use the HPE CSA (CI based) palette and to configure and integrate CSA with a HPE UCMDB provider.

Using HPE CSA (CI Type based) Palette

HPE CSA (CI Type based) palette is available for Sequenced Designs and the components in this palette are similar to the components available in the HPE CSA palette. However, the component types in the HPE CSA (CI Types based) palette is aligned with HPE UCMDB's CI Type system, so that each new CSA component type is mapped to its corresponding CI Type in HPE UCMDB, and the attributes of the corresponding CI Types are mapped to the attributes of the CSA component type.

An HPE UCMDB provider should be configured if the new component types based on HPE UCMDB's CI Type system needs to be created, or if the service topology provisioned by CSA should be created in HPE UCMDB. If the HPE UCMDB provider is configured and a service offering is subscribed or a service design is deployed in CSA, then the equivalent topology will be created in HPE UCMDB.

Note: For the Cloud Subscription Service CI to be visible in HPE UCMDB tool, the HPE UCMDB Content Pack should be imported to UCMDB from HPLN.

To download the new package, go to HPLN > Cloud Service Automation > Resource tab > Tools tile and download the CloudSubscriptionService UCMDB Package. Deploy the package using the UCMDB Package Manager from the Administration tab.

This chapter describes the following:

Configuring CSA for HPE UCMDB Integration
CSA Component Types aligned with HPE UCMDB’s CI Types
CI Type Component Types Hierarchy
Creating a Custom CSA Component Type

Configure CSA for HPE UCMDB Integration

Complete the following steps to configure CSA for HPE UCMDB integration:

Login to the server where HPE UCMDB is installed and extract the UCMDB server certificate using the following command:

Note: The UCMDB certificate must be imported into CSA's keystore if the UCMDB provider is configured to use secure HTTP for communication.

For Windows:
```
%UCMDB_JRE_HOME%\bin\jre\bin\keytool.exe -exportcert -keystore %UCMDB_JRE_HOME%\conf\security\server.keystore -alias hpcert -storepass hppass -file remoteServer.cert
```
Where, %UCMDB_JRE_HOME% is the directory where the Java Runtime Environment used by HPE UCMDB is installed.

For Linux:
```
$UCMDB_JRE_HOME/bin/jre/bin/keytool -exportcert -keystore $UCMDB_JRE_HOME/conf/security/server.keystore -alias hpcert -storepass hppass -file remoteServer.cert
```
Where, $UCMDB_JRE_HOME is the directory where the Java Runtime Environment used by HPE UCMDB is installed.
Copy the file "remoteServer.cert" to the server where CSA is installed, to a temporary location.
Change to the following directory in the server where CSA is installed:

For Windows:

%CSA_HOME%\openjre\bin

For Linux:
```
$CSA_HOME/openjre/bin
```
Open a Command Shell at this location, and execute the following command:

For Windows:
```
keytool.exe -importcert -alias hpcert –file <FILE PATH>/remoteServer.cert –keystore "%CSA_HOME%\openjre\lib\security\cacerts"
```
For Linux:
```
keytool -importcert -alias hpcert –file <FILE PATH>/remoteServer.cert –keystore "$CSA_HOME/openjre/lib/security/cacerts"
```
Where, <FILE PATH> is the path where the "remoteServer.cert" file is copied to as in step 2.

Note: If you are using an external JRE, then import the HPE UCMDB certificate into the keystore of the external JRE.
Restart CSA services after importing the certificate.

Once these steps are executed, create a new HPE UCMDB provider in CSA. If a HPE UCMDB provider is already configured, ensure the certificate is exported from the configured HPE UCMDB instance and imported into CSA.

Note: When designs having CI Type components are subscribed; during service provisioning if UCMDB is not reachable, the subscriptions will not fail. Subscriptions will be active however, the topology in UCMDB will not be created.

CSA Component Types aligned with HPE UCMDB’s CI Types

The new component types are included in a palette called HPE CSA (CI Types based). The component types in this palette are equivalent to similarly-named CI Types in the HPE UCMDB type system. The new component types cover most commonly used types in Compute, Network, Storage, Software and Load Balancer.

The table below describes the new CSA component types and how they are mapped to the equivalent CI Types in HPE UCMDB:

CI Types
Component Type	Description	Component Constraints	Resource Category Constraints
Configuration Item	Root Component for all components derived from CI Type or equivalent.	None	None
Infrastructure Element	Contains infrastructure service components such as, individual servers or server groups that are required in a service design.	None	None
Node	Represents a general purpose machine and is a base component type from which other component types representing devices such as, Virtual Machines will be derived.	None	None
Server	Represents a general purpose machine which has an IP Address such as, Windows or Unix Servers.	Node Element Running Software	Application Compliance Compute Configuration Management IT Service Management Monitoring Service Usage Storage
CI Collection	Generic logical collection of components that are of type - Infrastructure Element or Running Software.	None	None
Infrastructure Service	It contains a collection of infrastructure service components, such as Server Groups, that are needed in a service design.	Server Server Group	Compute Configuration Management Infrastructure Monitoring Network Storage
Server Group	Represents a server group which contains one or more servers.	Server Running Software	Compute Configuration Management Infrastructure Monitoring Network Storage
Running Software	Represents the runtime aspects of a software that is running or is intended to be running on a server and is a base component type from which other component types representing various software will be derived.	None	Application Monitoring
Database	Represents a database management system.	None	None
Oracle	Represents an Oracle database server.	None	None
MS SQL Server	Represents an MS SQL Server database server.	None	None
PostgreSQL	Represents a PostgreSQL database server.	None	None
Vertica	Represents a Verica Instance.	None	None
MySQL	Represents a MySQL database server.	None	None
Application Server	Represents a server that hosts an API to expose business logic and business processes for use by third-party applications.	None	None
J2EE Server	Represents a J2EE application server.	None	None
JBoss AS	Represents a JBoss application server.	None	None
Weblogic AS	Represents a Weblogic application server.	None	None
Load Balancer Software	Represents a component type for all Load Balancer software.	None	None
F5 BIG-IP LTM	Represents a F5 BIG-IP Local Traffic Manager software.	None	None
Web Server	Represents a software that accepts http requests and delivers web pages as a response.	None	None
Apache Web Server		None	None
Apache Tomcat	Represents an instance of Apache Tomcat web server.	None	None
IIS Web Server	Represents an instance of IIS Web Server.	None	None
Application Resource	A base component type that is used to derive component types representing application resources.	None	None
WebService Resource	A base component type used to derive component types that represent web service resources.	None	None
Web Service		None	None
Interface	A component type that describes a logical interface.	None	None

This indicates that the component type is not selected to be Designer Visible and therefore, the user cannot view these components in Service Designer while creating service designs. All the component types are system critical. The constraints defined for the new component types are same as the ones defined for older component types. Additional constraints can be defined as needed.

Designer Visible

When the Designer Visible check box for a component type is selected, then that component type is concrete and can be used in service designs. Such component types are visible in the Service Designer during design creation. Component types that are not Designer Visible can be used as base component types and new component types that are concrete in nature can be created and used.

For example, the Server Group and Server component types are marked as Designer Visible. This means a designer will be able to see the components of this type in the service designer, and can use them as components in a sequence design.

Component types such as, Node, Node Element and Running Software are not visible in the service designer. Instead it is recommended to use more concrete sub-types of these component types such as, Server, Network Connection or Application Server. However, you can create custom component types using such component types as base component types only, and use the custom component types while creating sequence designs.

Note: Components created using abstract components as base components cannot be set as designer visible. By default, the Designer Visible check box will be disabled on selecting an abstract component as the base component.

CI Type Component Relationship

Creating a Custom CSA Component Type

This section describes the steps and prerequisites for creating a custom CSA component type.

Prerequisites:

The following are the prerequisites for defining the CI Type for a new component type:

An HPE UCMDB provider must be configured. See, Configure CSA for HPE UCMDB Integration section for details.
The CI Type must exist in the configured HPE UCMDB server.
The CI Type of the base component type must be the parent of the CI Type set for the new component type, or it must be the same as the CI Type set for the new component type.

Note: The input for CI Type is not mandatory and can be left blank. When left blank, the CI Type of the base component type is used for the new component type.
The UCMDB certificate must be imported into CSA's keystore if the UCMDB provider is configured to use secure HTTP for communication as given in (step 1).

Follow the below steps to create a custom CSA component type:

From the Cloud Service Automation Dashboard, select Designs > Sequenced > Components.

The Sequenced Components page is displayed.
Select HPE CSA (CI Type) based palette from the left panel > click the gear icon and select Create Component Type.

The Create Component Type dialog box is displayed.
Select a CSA component type as the Base Component Type.

Base Components that are mapped to CI Types in HPE UCMDB is indicated by the CI Type label displayed beside component type, as shown in the image below.

Component Types indicated with the Label CI Type

Points to Note:

In HPE CSA (CI Type based) Palette
- You can only create CI Type based components from HPE CSA (CI Type based) palette. Though you can select other palettes from the Select Component Type dialog box, components for those palettes will not be displayed unless the component type is derived from a CI Type in HPE UCMDB.
- The CI Type field is visible in the Create Component Type dialog box by default.
- Selecting a Base Component Type is mandatory.
- When a Base Component Type is selected, the internal name of the selected Base Component Type is displayed in the CI Type field by default. However, you can change the CI Type to any other related CI Type component. But if the CI Type is not related, then the custom component type creation will fail. For example, if a custom component type for Windows-based Server is created, the CI Type should either be "host_node" or "nt". Instead if the CI Type is "disk _device" which is not related to "host_node" or "nt" the custom component type creation will fail.
- When the CI Type field is left blank, the selected Base Component is considered as the CI Type.
In palette other than HPE CSA (CI Type based)
- You can create components of all types including CI Type by selecting a CI Type component as the Base Component Type.
- The CI Type field in the Create Component Type dialog box is not visible by default. Only on selecting a CI Type component as the Base Component, the CI Type field is visible.
- Selecting Base Component Type is not mandatory for components other than CI Type.
Enter a name for the CI Type the new component type should be mapped to in HPE UCMDB. This CI Type must exist in HPE UCMDB else, the component type creation will fail.
Enter a name and display name for the new component type.

Note: You must also have a valid HPE UCMDB provider defined in CSA as described in the section Configure CSA for HPE UCMDB Integration.
Select the Designer Visible check box to set the component type to be visible and available for use in service designs.
Select the Consumer Visible check box to set the component type to be visible in the Marketplace Portal in Marketplace Portal.
Select the Pattern check box to set the component of this type to be accompanied by a Clone Pattern action in the parent service component.

The image below shows how a new CI Type component can be defined in CSA.

Create Component Type Dialog Box

Send Help Center feedback