{section}
{column:width=25%}
{livesearch:spaceKey=xVM}
h6. Contents
{children:all=true}
h6. [Index]
{column}
{column:width=75%}
To install Sun xVM Ops Center
1. Install the software on a system that is designated as the satellite server.
2. Install the software on a system that is designated to be the proxy.
3. Install the agent software on the systems that you want to use to provision, manage, and update software.
4. Register the proxy to the satellite. This is part of the proxy installation job. The sc-console command called to register local proxy to the satellite.
5. Register the local agent to the local proxy. This is part of the agent installation job. The sc-console command called to register local agent to local proxy.
6. As the administrator, log into the Satellite Control Panel (SCP) BUI and create a connection from Satellite to Sun Inventory (Sun-hosted application).
Note: This is performed in the BUI, not the CLI, however the BUI and sc-console the same library.
7. As the administrator, run the interactive Framework Proxy Configuration script in the proxy.
8. When prompted, answer the following questions:
* Satellite-Proxy firewall/HTTP proxy host/port
* Sun Online Account (SOA) user name and password
* Satellite host name
9. 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)
10. If Sun xVM Ops Center is hosted outside of Jetty then the script will ping the Ops Center to get its self-signed cert and present for confirmation.
11. Ping OS provisioning on Apache to get Apache's self-signed cert and present for confirmation
{column}
{section}
{column:width=25%}
{livesearch:spaceKey=xVM}
h6. Contents
{children:all=true}
h6. [Index]
{column}
{column:width=75%}
To install Sun xVM Ops Center
1. Install the software on a system that is designated as the satellite server.
2. Install the software on a system that is designated to be the proxy.
3. Install the agent software on the systems that you want to use to provision, manage, and update software.
4. Register the proxy to the satellite. This is part of the proxy installation job. The sc-console command called to register local proxy to the satellite.
5. Register the local agent to the local proxy. This is part of the agent installation job. The sc-console command called to register local agent to local proxy.
6. As the administrator, log into the Satellite Control Panel (SCP) BUI and create a connection from Satellite to Sun Inventory (Sun-hosted application).
Note: This is performed in the BUI, not the CLI, however the BUI and sc-console the same library.
7. As the administrator, run the interactive Framework Proxy Configuration script in the proxy.
8. When prompted, answer the following questions:
* Satellite-Proxy firewall/HTTP proxy host/port
* Sun Online Account (SOA) user name and password
* Satellite host name
9. 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)
10. If Sun xVM Ops Center is hosted outside of Jetty then the script will ping the Ops Center to get its self-signed cert and present for confirmation.
11. Ping OS provisioning on Apache to get Apache's self-signed cert and present for confirmation
{column}
{section}