{section}
{column:width=25%}
{livesearch:spaceKey=xVM}
h6. Contents
{children:all=true}
h6. [Index]
{column}
{column:width=75%}
This page provides a high-level overview of the installation and configuration process.
h3. Getting the Installation Software Bundle
Contact your Sun sales support representative to get the Sun xVM Ops Center software bundle.
The installer is located in the /<version>/Product/installer directory.
The following installation options are available:
* install Installs all software (satellite, proxy, agent)
* install -p Installs the proxy only
* install -e Un-installs all software from the system
h3. Installing The Software
1. If Sun xVM software is installed on the system, run the uninstall script as the root user.
./install -e
2. As the root user, install the software bundle.
/.install
3. Use the sc-console command to register. Part of installer involves the following new install jobs:
* Proxy job - sc-console called to register local Proxy to this Satellite.
* Agent job - sc-console called to register local Agent to local Proxy.
4. Log into the Satellite Control Panel (SCP) BUI and create a connection from Satellite to Sun Inventory (Sun-hosted).
Note: this is performed in the BUI, not the CLI, however the BUI and sc-console use the same library.
h3. Configuring The Proxy
1 Run the interactive Framework Proxy Configuration script.
2. You will be asked to provide the following information:
* Satellite-Proxy firewall/HTTP proxy host/port
* Sun Online Account (SOA) user name and password
* Satellite host
3. The script invokes sc-console to register Proxy with Satellite. First it will setup proxy through firewall, then registers the connection:
* sc-console register \-u [https://sathost:11165] \-f cred \-i \-n scn-proxy [-h http-proxy-host -p http-proxy-port]
* sc-console will get the self-signed cert from Satellite's Jetty (via the SSL handshake) and present to user to confirm it can be accepted. If accepted then it is saved in /var/scn/security/jsse/scn-proxy/truststore (See discussion on truststores at the end)
4. The script will ping the Sun xVM Ops Center to get its self-signed certificate and present it for confirmation.
h3. Installing Additional Agents
The agent can be installed either automatically via ssh, or standalone. If standalone then the user must invoke sc-console manually. In both cases sc-console will be invoked:
h4. Automated
Before sc-console is invoked in the ssh script, the cert from Proxy's Jetty (/etc/cacao/instances/default/security/jsse/truststore) is passed over via scp to /var/scn/security/jsse/scn-agent/truststore on the Agent. This will allow the webservice call to proceed with the cert being automatically accepted.
* sc-console \-u [https://proxy:21165] \-f cred \-n scn-agent
h4. Standalone/Manual
In standalone mode, the cert from Proxy's Jetty is not yet present on the agent, so user must invoke sc-console with \-i flag, for interactive, to accept the cert, and have it stored in the truststore.
* sc-console \-u [https://proxy:21165] \-f cred \-n scn-agent \-i
*Note* the agent talks HTTPS to port 21165 (scn-proxy instance Jetty port) directly, not 443. There is no Apache between the Agent and the Proxy's CRS.
{column}
{section}
{column:width=25%}
{livesearch:spaceKey=xVM}
h6. Contents
{children:all=true}
h6. [Index]
{column}
{column:width=75%}
This page provides a high-level overview of the installation and configuration process.
h3. Getting the Installation Software Bundle
Contact your Sun sales support representative to get the Sun xVM Ops Center software bundle.
The installer is located in the /<version>/Product/installer directory.
The following installation options are available:
* install Installs all software (satellite, proxy, agent)
* install -p Installs the proxy only
* install -e Un-installs all software from the system
h3. Installing The Software
1. If Sun xVM software is installed on the system, run the uninstall script as the root user.
./install -e
2. As the root user, install the software bundle.
/.install
3. Use the sc-console command to register. Part of installer involves the following new install jobs:
* Proxy job - sc-console called to register local Proxy to this Satellite.
* Agent job - sc-console called to register local Agent to local Proxy.
4. Log into the Satellite Control Panel (SCP) BUI and create a connection from Satellite to Sun Inventory (Sun-hosted).
Note: this is performed in the BUI, not the CLI, however the BUI and sc-console use the same library.
h3. Configuring The Proxy
1 Run the interactive Framework Proxy Configuration script.
2. You will be asked to provide the following information:
* Satellite-Proxy firewall/HTTP proxy host/port
* Sun Online Account (SOA) user name and password
* Satellite host
3. The script invokes sc-console to register Proxy with Satellite. First it will setup proxy through firewall, then registers the connection:
* sc-console register \-u [https://sathost:11165] \-f cred \-i \-n scn-proxy [-h http-proxy-host -p http-proxy-port]
* sc-console will get the self-signed cert from Satellite's Jetty (via the SSL handshake) and present to user to confirm it can be accepted. If accepted then it is saved in /var/scn/security/jsse/scn-proxy/truststore (See discussion on truststores at the end)
4. The script will ping the Sun xVM Ops Center to get its self-signed certificate and present it for confirmation.
h3. Installing Additional Agents
The agent can be installed either automatically via ssh, or standalone. If standalone then the user must invoke sc-console manually. In both cases sc-console will be invoked:
h4. Automated
Before sc-console is invoked in the ssh script, the cert from Proxy's Jetty (/etc/cacao/instances/default/security/jsse/truststore) is passed over via scp to /var/scn/security/jsse/scn-agent/truststore on the Agent. This will allow the webservice call to proceed with the cert being automatically accepted.
* sc-console \-u [https://proxy:21165] \-f cred \-n scn-agent
h4. Standalone/Manual
In standalone mode, the cert from Proxy's Jetty is not yet present on the agent, so user must invoke sc-console with \-i flag, for interactive, to accept the cert, and have it stored in the truststore.
* sc-console \-u [https://proxy:21165] \-f cred \-n scn-agent \-i
*Note* the agent talks HTTPS to port 21165 (scn-proxy instance Jetty port) directly, not 443. There is no Apache between the Agent and the Proxy's CRS.
{column}
{section}