How to Provision an Application

Products

APPLOGIC APPLOGIC FOR SYSTEM Z

Issue/Introduction

2.0 How to Provision an Application
2.1 Prerequisites
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

3.0 Copyright

1.0 Introduction

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.

2.0 How to Provision an Application

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 AppLogicenvironment,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:

Receive a customer request for an application instance.
Collect resource requirements and parameters that arenecessary to complete the application configuration.
(Optional) Copy the SugarCRM template application.Partially configure the copy of the template application,specifying any permanent parameter values that allinstances inherit.

Note: You configure a copy of the template application sothat the original template application is unaltered.
Run the provisioning wizard on the template application.

When the wizard is finished, you have a fully configuredSugarCRM application instance.

2.1 Prerequisites

Before you provision an application, verify that thefollowing requirements are met:

You are authorized to log on to a CA AppLogic^® grid.
You are familiar with the CA AppLogic^® system dashboard.
Your grid includes the SugarCRM template application, whichis included with CA AppLogic^®.
You are familiar with the process that your organizationuses to request instances of template applications.

2.2 Request for an Application Instance

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:

Parameter	Value
Software	Sugar CRM
CustomerID	SuperCo
Billing Code	205832
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.

2.3 Collect Resource Requirements and Boundary Parameters

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:

For the preconfigured template applications that areincluded with this project, data sheets are available inthe Application Catalog Reference Guide. The guide includesa data sheet for the SugarCRM application that thisscenario uses. Ideally, you also have data sheets for anyapplications that you create in-house or obtain from athird party.
Log in to the grid. Run the following command:
```
app config application_name --boundary
```
The output from this command is similar to the contents ofthe data sheet but without as much explanatory text.

Applications have the following types of parameter:

General

Application instance name, description, and customerbilling information.

Values: Arbitrary, depending on the procedures in your company.

In this scenario: You set application instance name and customer billing information.
Resources

System resources, such as CPUs and memory, that areallocated to your application instance.

Values: Default values are set in the template application. Change the default values only if your customer has requirements that exceed them.

In this scenario: Use the default values.
Properties

Application-specific settings that specialize theapplication instance for its role. Some properties are setfor the template application. All instances inherit theseproperty values. Other properties are set for each instanceduring provisioning.

Values: IP and IP-owned property values match grid values. Other property values depend on customer requirements.

In this scenario: You set only the IP and IP-owned properties, which are mandatory.

2.4 Partially Configure a Copy of the Template Application

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:

Log in to the grid. In a browser, open the system dashboard.
Open the Applications tab, right-click the SugarCRMtemplate application, and select Copy. Accept the defaultname for the copy.
After copying is completed, right-click the copy in theApplications tab and select Configure.
In the Application Configuration dialog, select theProperties tab, then locate the netmask, gateway, and dns1fields.

Note: The properties with red fields are mandatory. Howeveryou give values to some of these fields later, when youprovision the application. A template application does nothave all parameters configured.
Go back to the Dashboard tab in the system dashboard andlocate the netmask, gateway, and name servers fields.

These values apply to all applications on this grid.
Copy and paste the following values and click OK:
- Copy the values of the netmask and gateway fields from thedashboard and paste them into the same fields in theApplication Configuration dialog.
- Copy one of the name server IP addresses and paste it intothe dns1 field in the Application Configuration dialog.
You have a copy of the SugarCRM template application. Thatcopy is now configured and ready for provisioning.

2.5 Provision the Application

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:

Log in to the grid. In a browser, open the system dashboard.
Open the Applications tab, right-click the copy of theSugarCRM template application that you configured, andselect Provision.
Name the instance SugarCRM_r18_SuperCo_instance1.

A best practice is to include the customer name (in thiscase, SuperCo) in the instance name.
Type in the following information:
- Type the customer name, SuperCo, in the user1 field.
- Type the billing code, 205832, in the user2 field.
- Optionally, type a description of this application instance.
Click Next.

The Configure Resources page opens.
Click Next to accept default resource settings.

Note: In the Configure Resources page, the CPU, Memory, andBandwidth sliders all have default values. Disk volumesalso have default sizes.

Note: CA AppLogic^® assigns volumes and default sizes thatare based on the template application configuration. Youcannot add or delete a volume but you can change the volumesize.
(Version 3.5) Click Next to skip the Configure Interfacespage.

This page refers to raw interfaces, and this applicationhas no raw interfaces.
Fill in all empty, mandatory IP fields. Click Next.

The IP field values are under Application IP Range in theDashboard tab.

Note: The instance inherits the values for the gateway, netmask, and dns1 from the template application.

Note: If a selected IP address is in use, you receive anerror message.
Click Next to accept the default setting.

The application launches when provisioning is complete.

CA AppLogic provisions the SugarCRM application. When the provisioning is complete, you have a running instance of SugarCRM accessible at the IP addresses you specified in the provisioning wizard. Point a browser window to the user IP address and the Sugar CRM console appears.

3.0 Copyright

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.

Environment

Release:
Component: APPLGC

Attachments

1558717639120000020934_sktwi1f5rjvs16ukx.gif get_app