Before scaling up your deployment you might need to perform some configuration changes. These configuration changes are required in any of the following scenarios:
- If you performed a typical installation of the product on a single-server before deciding to scale.
- If you upgraded to the new version of the product, on the server where you had initially performed a typical installation, before deciding to scale.
These changes are required because in a typical installation, the product stores the host name of the destination server as "localhost" and not the actual host name. In such a scenario, if you scale up, then the newly installed components cannot communicate with the initial product server.
Therefore, before scaling up you need to update certain configuration properties on the initial product server. This means you need to change the value of these properties from "localhost" to the fully qualified host name of the server. In the following table, the example of "Host1.bmc.com" indicates the fully qualified host name that you need to provide.
After updating the properties, restart the product services for all the components. For more information, see Starting or stopping product services.
The following table describes the file locations and property names (with corresponding examples) that need to be updated.
| Configuration property and location | Example |
|---|---|
| %BMC_ITDA_HOME%\conf\services\configdb.conf | |
wrapper.app.parameter.11 | wrapper.app.parameter.11=Host1.bmc.com |
| %BMC_ITDA_HOME%\conf\indexer\esmonitor.properties | |
indexing.host | indexing.host=Host1.bmc.com |
| %BMC_ITDA_HOME%\conf\indexer\indexer.yml | |
|
|
| %BMC_ITDA_HOME%\custom\conf\server\olaengineCustomConfig.properties | |
|
|
| %BMC_ITDA_HOME%\custom\conf\server\searchserviceCustomConfig.properties | |
|
|
| %BMC_ITDA_HOME%\station\collection\custom\conf\agent.properties | |
|
|
Overview
Content Tools
Apps
Reporter Replacement
com.bmc.atlassian.bmc-util-plugin-2.section.label
Tasks