2.0 How to Provision an Application
2.2 Request for an Application Instance
2.3 Collect Resource Requirements and Boundary Parameters
2.4 Partially Configure a Copy of the Template Application
2.5 Provision the Application
Product: CA AppLogic
Release: 3.0 and later
This scenario describes how operators provision a templateapplication to create an instance of the application. Thisscenario uses the provisioning wizard and the SugarCRMpreconfigured template application. The provisioningprocess can be repeated, providing multiple customers witha unique instance each.
This scenario applies to all operating systems that CAAppLogic supports, in both mainframe and distributedenvironments. This scenario also applies to all applicationoperating systems.
This Knowledge Base Article constitutes a portion of theofficial CA product documentation forthis CA product. This Knowledge Base Article is subject tothe following notices, terms, and conditions.
As a CA AppLogic operator, you provide applications on thegrid to your customers. Often, you provide the sameapplication to multiple users. The number of users andtheir requirements can change frequently. Therefore, yourapplication must be deployable on demand as multipleinstances.
For on-demand deployment in the CA AppLogic environment,you prepare a template application. Template applicationsare not fully configured and cannot be run. When you createan instance of the template application, you providenecessary configuration details, such as IP addresses andbilling codes. These details are unique to each instance.Provisioning is the process of creating those uniqueinstances on demand.
CA AppLogic includes many preconfigured templateapplications. One of these template applications isSugarCRM. This scenario uses SugarCRM as an example of atemplate application to provision. SugarCRM is an opensource customer relationship management software package.CA AppLogic enables service providers to offer SugarCRM ondemand, as software-as-a-service (SaaS) hosted on the Cloud.
<Please see attached file for image>
To provision an application, follow these procedures:
When the wizard is finished, you have a fully configuredSugarCRM application instance.
Before you provision an application, verify that thefollowing requirements are met:
This scenario supposes that you work for a SaaS provider.Your workflow involves receiving requests to provideapplication instances to customers. In this scenario, youfill the following sample request:
|Customer resource requirements||None specified (use default resource allocation)|
Other SugarCRM parameters are not mentioned in the customerrequest. In this example, either the customer sets theseparameters through the SugarCRM administration interface orthe default values are accepted. For example, the customeris given the administration IP and default password for theSugarCRM administration interface. After the application isprovisioned, the customer logs in to this interface andchanges the password.
This scenario walks you through configuring the mandatoryparameters for provisioning SugarCRM. When you provision anapplication for your organization, before you begin, checkthe parameters that you configure. Discover whetherparameters are mandatory or optional. Discover thepermitted range of values. This information is availablefrom the following sources:
app config application_name --boundary
Applications have the following types of parameter:
Some parameters have the same value for all instances of anapplication. For efficiency, set those values in thetemplate application itself. All instances of thatapplication inherit these values. You set the values onlyonce instead of setting them every time you provision theapplication.
To follow best practice, copy the template application andset parameter values in that copy. By doing so, you alwayshave an unaltered version of the template application.
Note: In this scenario, you set the template applicationgateway, netmask, and DNS properties. Use the values fromyour grid. These properties are the same for allapplications on your grid.
Follow these steps:
Each time you provision a template application, you createa unique instance for an end user. This procedure explainshow to use the provisioning wizard in the UI. Here youprovision the template application copy that you createdand configured.
Follow these steps:
This Documentation, which includes embedded help systemsand electronically distributed materials, (hereinafterreferred to as the "Documentation") is for yourinformational purposes only and is subject to change orwithdrawal by CA at any time.
This Documentation may not be copied, transferred,reproduced, disclosed, modified or duplicated, in whole orin part, without the prior written consent of CA. ThisDocumentation is confidential and proprietary informationof CA and may not be disclosed by you or used for anypurpose other than as may be permitted in (i) a separateagreement between you and CA governing your use of the CAsoftware to which the Documentation relates; or (ii) aseparate confidentiality agreement between you and CA.
Notwithstanding the foregoing, if you are a licensed userof the software product(s) addressed in the Documentation,you may print or otherwise make available a reasonablenumber of copies of the Documentation for internal use byyou and your employees in connection with that software,provided that all CA copyright notices and legends areaffixed to each reproduced copy.
The right to print or otherwise make available copies ofthe Documentation is limited to the period during which theapplicable license for such software remains in full forceand effect. Should the license terminate for any reason, itis your responsibility to certify in writing to CA that allcopies and partial copies of the Documentation have beenreturned to CA or destroyed.
TO THE EXTENT PERMITTED BY APPLICABLE LAW, CA PROVIDES THISDOCUMENTATION "AS IS" WITHOUT WARRANTY OF ANY KIND,INCLUDING WITHOUT LIMITATION, ANY IMPLIED WARRANTIES OFMERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, ORNONINFRINGEMENT. IN NO EVENT WILL CA BE LIABLE TO YOU ORANY THIRD PARTY FOR ANY LOSS OR DAMAGE, DIRECT OR INDIRECT,FROM THE USE OF THIS DOCUMENTATION, INCLUDING WITHOUTLIMITATION, LOST PROFITS, LOST INVESTMENT, BUSINESSINTERRUPTION, GOODWILL, OR LOST DATA, EVEN IF CA ISEXPRESSLY ADVISED IN ADVANCE OF THE POSSIBILITY OF SUCHLOSS OR DAMAGE.
The use of any software product referenced in theDocumentation is governed by the applicable licenseagreement and such license agreement is not modified in anyway by the terms of this notice.
The manufacturer of this Documentation is CA.
Provided with "Restricted Rights." Use, duplication ordisclosure by the United States Government is subject tothe restrictions set forth in FAR Sections 12.212,52.227-14, and 52.227-19(c)(1) - (2) and DFARS Section252.227-7014(b)(3), as applicable, or their successors.
Copyright © 2013 CA. All rights reserved. All trademarks,trade names, service marks, and logos referenced hereinbelong to their respective companies.