Starting your first Application

Provisioning the sample application

1. Log in to the controller via the web shell (if not done already)
2. Execute app config SugarCRM --boundary to see the set of configuration parameters that are available.
3. Chose network configuration parameters that are correct for your grid -- the IP addresses must be from the set of IP addresses listed on your dashboard; the netmask, gateway and dns servers should match as well.
4. Provision the application using the app provision command. Upon completion of the app provision command, the application should be running. The following is an example:
   app provision SugarCRM? mysugar
   user_ip=209.100.100.11 admin_ip=209.100.100.12
   netmask=255.255.255.0 gateway=209.100.100.1
   dns1=209.101.1.2 dns=209.102.1.2
   mail_server=mail@mycompany.com
   config.size=256M logs.size=64M
   .description="My SugarCRM application"
   • You will see the application instance volumes being created. This process -- which runs only once -- may take a while. On subsequent starts, the volume creation phase will be skipped.
   • after a small delay, you should see "Starting application" and a progress indicator; as appliances complete their startup, they will be reported
   • at the end, you should see "Application started successfully."
5. Point your browser to the IP address of the user gateway (the value of the usr_ip property you recorded above.
6. You should see the SugarCRM home page. Feel free to work with the application.

To find out more about the sample application, see the SugarCRM application data sheet.

Modifying the application

• You can simplify the application by removing the load balancer and the second web server. To do this:
  • stop the application (app stop mysugar)
  • edit the application using the visual editor: delete the webs and srv2 components, connect the output of the usr gateway straight into the srv1 server
  • save the application
  • restart it (app start mysugar).

• You can make the application more scalable by adding one more web server.
  • drag a new WEB server from the catalog onto the canvas, under srv2
  • connect the 3rd output of webs to the input of the new server
  • connect all the outputs the same way as they are connected on srv1 and srv2
  • double-click on the new server and set all settings (attributes, resources, user volumes and property values) the same way as for srv1
    • you can see the settings of srv1 by double-clicking on it

-- BeckyH - 13 Jun 2006