This section introduces the main system level differences between BMC Discovery versions before 11.3 and version 11.3 running on CentOS 6, and how those changes affect BMC Discovery users. If you have upgraded to version 11.3, your appliance is running on CentOS 6.
To determine whether your appliance is running on CentOS 6 or CentOS 7, check the footer of any UI page. The BMC Discovery version number, build number, and OS version are provided on the bottom line.
Alternatively, from the command line, enter:
CentOS release 6.x
For CentOS 7 the output begins:
CentOS Linux release 7.x
All of the BMC Discovery application services in 11.3 on CentOS 6 are controlled using the
tw_service_control utility. For complete information on its usage, see the
tw_service_control documentation. The
tw_service_control utility enables you to start and stop individual application services, such as the Application Server service or the External API service, or all services as one, which is the equivalent of the
tideway service in versions before 11.3.
In CentOS 6, the only services that require you to use system level commands to control them are
omniNames, and occasionally,
appliance service still exists, but is only used by the system at boot.
In an 11.2 appliance you would restart the security service using:
On an 11.3 appliance running on CentOS 6, you should enter:
Or to restart all services (the equivalent of the tideway service in release before 11.3), you should enter:
tideway service still exists, though you should use the
If you have written scripts to interact with BMC Discovery services, you should modify those scripts to use the
BMC Discovery uses the Apache web server. In 11.3 appliances running on CentOS 6, the Apache version is still 2.2.
Integration with BMC Atrium Single Sign-On was deprecated in BMC Discovery 11.0 and has been removed. You should use the integration with Remedy Single Sign-On.