Implementing private certificates in the TrueSight Infrastructure Management
The following section guides you to create a signed certificate for the Infrastructure Management server and cell.
Best practice
Before you begin
Before creating a private certificate for the Infrastructure Management server and securing the communication, ensure the following:
- Create a private certificate for the Remedy Single Sign-On Server and secure it.
- Create a private certificate for the TrueSight Presentation Server and secure it.
To apply the Infrastructure Management server certificate to the TrueSight Operations Management components
Once the Infrastructure Management Server and the cell certificate is generated and secured, you need to apply this certificate to various TrueSight Operations Management components that you have integrated in your environment. The following section guides you how to apply the Infrastructure Management server certificates to TrueSight Operations Management components.
Where to go from here
Once you secure the TrueSight Infrastructure Mnagement, you can apply this certificate to other TrueSight Operations Management components such as:
- Applying Infrastructure Management server and the cell certificate to the TrueSight Presentation Server.
- Applying Infrastructure Management server and the cell certificate to the TrueSight Integration Service.
- Applying Infrastructure Management server and the cell certificate to the Impact Integration Web Services.
- Applying Infrastructure Management server cell certificate to IT Data Analytics.
- Applying Infrastructure Management server cell certificate to the Publishing Server.
You can also explore how to implement private certificates in other TrueSight Operations Management components.
Comments
Within this page are tsim.cer and mcell.crt the same and tsimSrv.key and mcell.key the same?
Also is it correct/accurate to interchangeably use the phrases "private key" and "private cert"? It causes the novice great confusion. My, possibly incorrect, understanding is that the key is the private bit that a server uses to encrypt and the the certificate is a "fingerprint" used by a client to confirm that the server it's communicating with is what it expects. Getting the certificate signed gives an additional level of trust to the client that the server is saef to communicate with. This unclear terminology is present in almost every BMC page discussing this.
Hi,
I will discuss this with the SME and update you.
Thanks,
Rashmi
Hi,
I checked with the SME and confirmed that tsim.cer and mcell.crt are the same, similarly tsimSrv.key and mcell.key are the same. The mcell.crt and mcell.key are created for the cell components.
Thanks,
Rashmi
Log in or register to comment.