Special configurations

This section includes:

Establish Trust Between OMi and OM Deployments

For connection and communication between OMi and OM hosts or other OMi hosts, you must establish a trust relationship between the systems. In FIPS mode, the trusted certificates must be exchanged manually. To do so, follow these steps:

1. On the OMi data processing server, execute the following command:

   ovcert -exporttrusted -file <omi.cer>

2. On the external system (OM or other OMi deployment), execute the following command:

   ovcert -exporttrusted -file <other.cer>

3. Copy <other.cer> from the external system to the OMi data processing server.

4. Copy <omi.cer> from the OMi data processing server to the external system.

5. On the OMi data processing server, execute the following commands:

   ovcert -importtrusted -file <other.cer>

   ovcert -importtrusted -file <other.cer> -ovrg server

6. On the external system, execute the following commands:

   ovcert -importtrusted -file <omi.cer>

   ovcert -importtrusted -file <omi.cer> -ovrg server

Run REST-based command-line interfaces

To secure REST web service command-line tools, the following CLI must be called once after every certificate change. By running the script, the specified certificate will be imported into the OMi keystore.

<OMi_HOME>/opr/bin/opr-import-fips-cert.[bat|sh] <downloaded_browser_certificate>.cer

The following CLI tools are REST-based:

• ConfigExchange
• ConfigExchangeSIS
• ConfigWsTool
• ConnectedServer
• ContentManager
• opr-agt
• opr-ci-list
• opr-downtime
• opr-jobs
• opr-node
• opr-package-manager
• opr-template
• opr-tool
• opr-script
• opr-user
• RestWsUtil