Writer instructions | |
|---|---|
Page title | For most spaces, this page must be titled Space announcements. For spaces with localized content, this page must be titled Space announcements l10n. |
Purpose | Provide an announcement banner on every page of your space. |
Location | Move this page outside of your home branch. |
Guidelines | |
Configuring the HTTPS Certificate for auto-deployment
By default the MVMM Configuration Agent uses an HTTPS connection to retrieve deployment information. A certificate for that HTTPS server is included in a java key store if using an agent distribution of the MVMM Configuration Agent. It is stored in the file configuration/services/httpsTrustStore.jks, unless configured otherwise.
The key store should be updated if ...
- The agent connects to a different host
- The certificate is updated
- The agent was not retrieved using agent distribution
To update the key store with a new HTTPS certificate, first make any other configuration changes (e.g. change the services host, or update the certificate on the service tier).
- Stop the MVMM Configuration Agent.
- Start the MVMM Configuration Agent in console mode.
- Issue the storeHTTPSCertificate command
- Respond to the prompts as appropriate
- Exit the console mode, and restart the MVMM Configuration Agent.
See the following example session.
Alternatively the key store can be manipulated directly with the java keytool command (For example, to import certificates from other sources).