Discovery Cloud connector
Use the BMC Discovery connector to fetch the relationships between business services, applications, and the supporting IT infrastructure in your cloud environment. The connector fetches this mapping information from BMC Discovery. With this integration you can view the discovered business services as imported resource pools in BMC Helix Cloud Cost. You can also cross-launch from BMC Helix Cloud Cost to BMC Helix Discovery to view the network topology or the graph details of individual resources.
All communication between BMC Helix Cloud Cost and BMC Helix Discovery is secure over HTTPS.
Supported BMC Discovery versions:
- BMC Discovery (on-premises): 20.08, 20.02, 12.1, 11.3
- BMC Helix Discovery
Step I. Complete the preconfiguration tasks
- Create a user in the BMC Helix Discovery and assign the API access rights. The connector uses the credentials of this user to connect to BMC Helix Discovery for data collection.
- Log in to the BMC Helix Discovery as an administrator.
- Click settings
.
- Under Security, click Users > Add.
On the Add User page, do the following:
- From the Template list, select User.
- Specify the user name and password details.
- Under Groups, select these check boxes to assign rights and add the user to these Public groups: api-access and never-deactivate
- Click Apply.
The settings are saved, and a confirmation message is displayed.
- Add manual groups for creating business services.
- Log in to BMC Helix Discovery as an administrator.
Under Quick View, click any of the following options:
- Application Instances - To add groups to application instances
- Hosts - To add groups to systems under hosts
- Virtual Machines - To add groups to virtual machines
- Select the check boxes corresponding to the application instances, systems, or virtual machines for which you want to add manual groups.
- Click Actions > Manual Groups, create the required manual groups and subgroups, and select them. The selected groups and subgroups are displayed under Manual Groups.
- To create a business service hierarchy for the virtual machines below the application instance (BAI), the manual group name (default name: Service) must be associated with the parent application instance. If the manual group name is associated with the child application instance, the manual group is not created.
- To create business services for virtual machines of unassociated hosts, you must add the manual group called Service on the virtual machine itself, with its value as subgroup.
- By default, manual group AppTier is used for creating service pools below the business services.
- Click Actions > Manual Groups, create the required manual groups and subgroups, and select them. The selected groups and subgroups are displayed under Manual Groups.
Create an API token for the user account. For information about how to generate a token, see the Managing system users in the BMC Helix Discovery documentation.
- Ensure that integration with Remedy Single Sign-On in enabled in BMC Helix Cloud Cost and BMC Helix Discovery. Both these products use Remedy SSO for authentication of users. This step is required so that you can cross-launch to BMC Helix Discovery from BMC Helix Cloud Cost to view the Application Model details in BMC Helix Discovery.
- Ensure that the manual groups, business services, and application instances are created in BMC Helix Discovery.
Ensure that BMC Helix Cloud Cost has scanned the resource utilization data from the same cloud environment as that of BMC Helix Discovery. For information about which cloud providers are supported by BMC Helix Discovery, see Supported Cloud Providers.
Step II. Configure the connector
You must configure the connector to connect to BMC Discovery for data collection.
To configure the connector:
- In the BMC Helix Cloud Cost dashboard, navigate to Connectors > Add a Connector > and select Discovery Cloud Connector.
On the Configure Connector page, configure the following properties:
Property
Description
Connector name
A unique name for the connector.
Select Resource Types
Specify the type of resources for which you want to discover data center inventory, configuration, and relationship data.
- Cloud resources - Discover the resources from your multi-cloud environments
- On-premise asset - Discover the resources from your hybrid application environments
Discovery configuration
- Specify the endpoint URL to connect to your Discovery environment
- Select the authentication type:
- Token Based: The token of the user that you have created during the preconfiguration steps.
- User Credential Based: The name and the password of the user that you created during the preconfiguration steps.
Business Service Configuration
- Business Service Creation Criteria:
- Create Business Services for all Business Application Instances containing cloud resources: Scans data for all the manual groups
- Create Business Service based on Subgroup name where manual Group name is: Scans data for a specific manual group.
Specify the manual group name for which you want to scan the data.
- Create Business Service based on Subgroup name where manual Group name is: Scans data for a specific manual group.
- Collection mode: By default, the data collection cycle is set to On Demand collection. You can select an appropriate unit of time (days, minutes, hours) to schedule the data collection frequency.
- Click Continue.
- A confirmation message about the request for data collection processing is displayed.
The Manage Connectors page shows the details of the newly configured Discovery Cloud Connector. - (For on-premises Discovery connector only) BMC Helix Cloud Cost starts downloading the connector setup zip file automatically to your local disk. The downloaded zip file name is same as the connector name that you have specified in the connector configuration. After the download is complete, the state of the connector is displayed as Downloaded on the Manage Connectors page.
- Copy the downloaded zip file to a folder of your choice on the target computer. Extract the package.
- Run the connector package.
- (Windows) Double-click run.bat
- A confirmation message about the request for data collection processing is displayed.
- (UNIX) At the shell prompt, type chmod +x run.sh to grant execute permissions to the run.sh file. Type run.sh and press Enter.
- While the package execution is in progress, switch to the BMC Helix Cloud Cost UI, and from the Download page, click Continue.
- After the execution is complete, the Manage Connectors page shows the details of the newly configured Discovery connector and the state of the connector is updated to Running.
Step III. Verify data collection
Verify that the connector executed successfully and check whether business services from BMC Discovery are imported into BMC Helix Cloud Cost as Resource Pools.
- Business services imported as resource pools are marked with Business Service and Imported labels in the resource pools list. You cannot edit the details of these imported resource pools.
- Cross-launch links are available from the Resource Pool details page that can be used to launch BMC Helix Discovery to see the Application model details.
Application model details for WordPress_App displayed in BMC Helix Discovery when you cross-launch from BMC Helix Cloud Cost.
Supported Amazon Web Services, Microsoft Azure, and Google Cloud Platform resources
The Discovery Cloud connector currently supports the following resources:
Cloud services | Resource type | Discovery Kind | Licensed in Discovery? | Available in BMC Helix Cloud Cost |
---|---|---|---|---|
Amazon Web Services | ||||
Compute | Amazon EC2 | VirtualMachine | Yes | Yes |
Amazon EC2 - Auto scaling group | VirtualMachine | Yes | Yes | |
Amazon EC2 - Storage | StorageVolume | Yes | Yes | |
Database | Amazon Aurora | SoftwareInstance | Yes | Yes |
Amazon RDS | SoftwareInstance | Yes | Yes | |
Amazon DynamoDB | Database | Yes | Yes | |
Amazon Neptune | SoftwareInstance | Yes | Yes | |
Containers | Amazon EC2 Container Service | VirtualMachine | Yes | Yes |
Amazon EKS | Cluster | Yes | Yes | |
AWS Fargate | Deployment | Yes | no | |
Analytics | Amazon Athena | CloudResource | Yes | no |
Amazon EMR | CloudResource | Yes | Yes | |
Amazon Kinesis | CloudResource | Yes | Yes | |
Amazon Redshift | CloudResource | Yes | Yes | |
Application Hosting/Serverless | AWS Elastic Beanstalk | Cloud Resource | Yes | no |
AWS API Gateway | SoftwareInstance | Yes | Yes | |
AWS Step Functions | CloudResource | Yes | Yes | |
Caching | Amazon ElastiCache | SoftwareInstance | Yes | Yes |
Storage | Amazon S3 | CloudResource | Yes | Yes |
AWS Glacier | CloudResource | Yes | Yes | |
Messaging Services | Amazon MQ | CloudResource | Yes | Yes |
Microsoft Azure | ||||
Compute | Virtual Machine | VirtualMachine | Yes | Yes |
Database | SQL | SoftwareInstance | Yes | Yes |
Azure DB for MySQL | SoftwareInstance | Yes | Yes | |
Azure for PostgreSQL | SoftwareInstance | Yes | Yes | |
Analytics | HDInsight | CloudResource | Yes | Yes |
Azure Databricks | CloudResource | Yes | Yes | |
Data Lake | CloudResource | Yes | Yes | |
Azure Stream Analytics | CloudResource | Yes | Yes | |
Storage | Azure Backup | CloudResource | Yes | Yes |
Auto Scaling | Virtual Scale Sets | VirtualMachine | Yes | Yes |
Google Cloud Platform | ||||
Compute | Compute Engine | Yes | ||
Database | Cloud SQL | Yes |