Maintenance outage Saturday, September 18 at 9 PM CDT

This site, docs.bmc.com, will undergo a brief outage for maintenance on Saturday, September 18, at 9 PM.

Page tree

Maintenance outage Saturday, September 18 at 9 PM CDT

This site, docs.bmc.com, will undergo a brief outage for maintenance on Saturday, September 18, at 9 PM.

Unsupported content

   

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Skip to end of metadata
Go to start of metadata

The BMC TrueSight Capacity Optimization Datahub tab provides core services, APIs, supports data warehousing, and data exchange activities. You can access this tab by navigating to Administration > System > Global configuration > Datahub.

Some of the services are exposed as web services and allow Datahub communication with all ETL engine servers in a BMC TrueSight Capacity Optimization infrastructure.

The Datahub tab allows you to configure access point to BMC TrueSight Capacity Optimization Datahub web services. You can communicate remotely through RESTful over HTTP(s).

Option

Description

Datahub Webservice URL

You can specify the endpoint interface address, when the Datahub Web Services are exposed.
The default value is http://<bcohost>:<port>/dh-services where:
<bcohost>: It is the address of the Datahub on the existing BMC TrueSight Capacity Optimization server.
<port>: It is the port of the Datahub on the existing BMC TrueSight Capacity Optimization server.

Data API External Webservice URL

You can specify the access URL to the Datahub Web services from other components that resides in Remote ETL Engine servers and communicate through WAN links.
The URL format is http://<host>:port/dh-service.

Data API ParallelismSpecify the number of concurrent threads that must process data imported through the data API. Reducing this number will reduce the data API throughput but will also reduce the pressure on the database. On the other hand, increasing the number can improve data API performances but increase the load on the database.
Remote Repository HostGenerally, no configuration is required for this option. This option is useful in advanced and customized deployments to allow specific configuration from a support perspective.
Remote Repository UsernameGenerally, no configuration is required for this option. This option is useful in advanced and customized deployments to allow specific configuration from a support perspective.
Remote Repository PasswordGenerally, no configuration is required for this option. This option is useful in advanced and customized deployments to allow specific configuration from a support perspective.