Integrating BMC Cloud Lifecycle Management with BMC ProactiveNet at a later stage
This section describes how to configure BMC ProactiveNet to connect to BMC Cloud Lifecycle Management using the pw cloudTopologyIntegration conf -a <adaptertype> command.
To configure BMC ProactiveNet:
Run the command pw cloudTopologyIntegration conf help -a <adaptertype> to get help on the required arguments for the command.
The following prompt appears:
*********************************************************************************
Please enter the required command line arguments as below
pw cloudTopologyIntegration conf –a CLM [-pms <CLM Platform Manager Protocol>]
-pmh <CLM Platform Manager host> [-pmt <CLM Platform Manager Port>]
-pmu <CLM Platform Manager User Name> -pmp <CLM Platform Manager Password>
[-bcs <BPPM Central Protocol>] [-bch <BPPM Central Host>] [-bct <BPPM Central Port>]
where
<CLM Platform Manager Protocol> is the CLM Platform Manager protocol (default http, if not specified)
<CLM Platform Manager host> is the CLM Platform Manager host
<CLM Platform Manager Port> is the CLM Platform Manager Port (default 80, if not specified)
<CLM Platform Manager User Name> is the CLM Platform Manager User Name
<CLM Platform Manager Password> is the CLM Platform Manager Password
<BPPM Central Protocol> is the BPPM Central Protocol (default http, if not specified)
<BPPM Central Host> is the BPPM Central Host (default localhost, if not specified)
<BPPM Central Port> is the BPPM Central Port (default 80, if not specified)
If the Password is empty enter ""
*********************************************************************************Enter the required arguments to configure cloud publishing:
Argument
Description
CLM Platform Manager Protocol
CLM Platform Manager Host
CLM Porthttp or https
Host Name where platform manager is configured
Port number configured for Platform manager protocolCLM Platform Manager User Name
BMC Cloud Lifecycle Management user name having cloud administration rights.
CLM Platform Manager Password
BMC Cloud Lifecycle Management user having cloud administration rights.
BPPM Central Protocol
HTTP or HTTPS
Default value is configured by the BMC ProactiveNet Server installer. The default value is HTTP.BPPM Central Host
Name of the host where BMC ProactiveNet Central Server is configured.
Default value is configured by BMC ProactiveNet Server installer. The default value is localhost.BPPM Central Port
Port number configured for BMC ProactiveNet Central Server.
Default value is configured by BMC ProactiveNet Server installer. The default port is 80.You can also configure additional properties directly in the following configuration files located at the installationDirectory/pronto/conf folder:
CLMAdapter.xmlParameter Name
Default Value
Description
Comments
clm-timeout
10000
Timeout to connect to BMC Cloud Lifecycle Management server
The default value is in millisecond.
clm-no-of-retry
3
Retry for the specific number of times before throwing an ERROR
clm-retry-interval-seconds
300
Wait for the specific number of seconds before attempting to connect to BMC Cloud Lifecycle Management server.
The default value is in second.
differentialCalculationEnabled
true
true–checks if the data is already available on BMC ProactiveNet server (sends only delta to BMC ProactiveNet server)
false–does not check if data is already available on BMC ProactiveNet server.This is used in conjunction with fetchCLMDataOnStartEnabled.
If the fetchCLMDataOnStartEnabled = true then find the delta and add it to BMC ProactiveNet.fetchCLMDataOnStartEnabled
true
true-fetches the data from BMC Cloud Lifecycle Management on BMC ProactiveNet startup.
false-does not fetch data from BMC Cloud Lifecycle Management at startup.missed-callout-config
schedularInterval
schedularIntervalUnit
2
HOURSRuns the missed callout manager every two hours. This is used to sync the data between BMC ProactiveNet and BMC Cloud Lifecycle Management.
Interval can be SECOND, MINUTE or HOUR.
CleanUpDetails interval
86400000
Runs the cleanup manager every 24 hours. The cleanup manager will run on each classes mentioned in the Cleanup classes section.
The default value is in millisecond.
CloudAdapter.xml
Parameter Name
Default Value
Description
staging-enabled
true
true–when the adapter fails to create a cloud object on BMC ProactiveNet server due to a specified error (configured in the CloudAdapter.xml error-config parameter), the failed object is cached and the adapter retries to create it.
false–an error is thrown when the adapter fails to create a cloud object.staging-cleaner-interval
300
Runs the staging cleaner manager every 5 minutes.
This parameter is used in conjunction with staging-enabled