Setup and Administration for ISVs

Transcription

1 17 Setup and Administration for ISVs ISV accounts for both hosted and private cloud support white labeling functionality and give you the ability to provision and manage customer tenants directly. A customer tenant is a virtual space that securely hosts applications and data and provides a working environment for a set of users. This allows you to run your own Software as a Service (SaaS) business and take advantage of the Rollbase platform for rapid development and secure deployment of applications that meet critical business needs. ISV Features For ISV pricing or to purchase, contact Progress. Progress Rollbase provides the following benefits to all ISV customers: ISV account: Hosted cloud standard customers receive a special account that provides the ability to create and manage customer tenants. This eliminates dependencies on Progress for deployment and maintenance. Rollbase Private Cloud customers can set up any number of ISV Accounts for their own customers. Fifty users included: Rollbase Hosted Cloud Standard and Rollbase Private Cloud Standard ISV licenses include 50 subscribers with the base monthly fee.you will be billed for subscribers 51 and beyond. Private Cloud Enterprise customers get their first 1000 users included with the base monthly fee. Custom login and password retrieval pages: ISVs with dedicated websites for their companies and products can host their own branded pages for log in and forgotten passwords, making the use of Rollbase transparent to end users. Any number of custom login pages can be created and hosted externally allowing you to have different login mechanisms for each application, dedicated login pages for key customers, or a central login for all of your customers. Custom Application Directory: You can set up a custom branded, private application directory allowing your customers and prospects to view and install applications directly from their website. 563

2 Chapter 17: Setup and Administration for ISVs Customizable platform name: It is simple to replace Rollbase with your own product, platform or company name. Customizable URLs: All default external links within the platform that point to company-hosted pages, such as terms of service, privacy statement, etc, can be redirected to your pages. Hosted cloud ISV customers will still see in the browser address bar. Private Cloud customers will see Automatically provisioned free trials: As an ISV, you can offer automatically-provisioned free 30 day trials of any application through dedicated pages on your website. This includes the ability to customize and brand automated s sent from the Rollbase system. The topics in this section describe how to work with Progress Rollbase Hosted Cloud or Private Cloud as an ISV. For details, see the following topics: Getting Started Creating a Custom Log In Page Creating a Page for Users to Retrieve Passwords Customizing Page Title Tags Using a Third-Party Cloud Service for Storage Getting Started Rollbase hosted standard cloud customers receive a special ISV account that allows tenant and published application management. When this account is created you will receive a welcome from Rollbase that allows you to log in and start creating customer tenants. When you log in, you will want to view and modify your ISV accounts settings. And, you can change these settings at any time. However, remember that once you have customer tenants that changes made to ISV account settings will not be applied immediately. Please contact Rollbase support if you need these to be activated within 24 hours. To view and modify your ISV settings: Note: 1. From the Applications drop-down list, select Setup. 2. Under the Personal Setup heading, click My Settings In addition to the usual Rollbase user settings, you will see the ISV-specific options described in the table below. All fields are optional. Field ISV System Name ISV Home Page Integration Name isvsysname isvhome Description Name of your company. This value will replace "Rollbase" throughout the platform. URL to your website to use instead of Rollbase.com 564

3 Getting Started Field ISV Login URL ISV Copyright ISV Support URL ISV Title Template Integration Name isvloginurl isvcopyright isvsupporturl isvtitletemplate Description URL to your custom login page Copyright string to use at the bottom of all pages URL to "Support Requests" link to use instead of Rollbase.com Template to use for the <title> tag in all pages Using the ISV Partner Application When logging into an ISV account, you will automatically be taken to the ISV Partner application that includes tabs for managing the following objects: Customers: Allows you to create and manage customer tenants. Published Applications: Allows you to manage applications published by customer tenants to your Application Directory. Here you can edit published application information such as name and description and choose whether or not they should appear by approving them for installation. Support: Allows you to manage and respond to support tickets submitted by your customers Sharing User Object Fields with Customer Tenants Several fields defined on the User object in the Master system are designed to share important information with ISV-managed Customers. See the table in Getting Started. Private Cloud customers can define any fields to be shared between an ISV user and related customers. In the User object in the Master system, check Make this field available for related ISV Customers checkbox on the field create or field edit page for each field you want to expose. Once this is enabled, in any template or formula within that customer tenant you can use a merge field to retrieve the value of that Master system user field. Warning: Due to the current User caching mechanism, updates to shared fields may not be available to customers until after the next Rollbase maintenance event (or Tomcat restart for Private Cloud customers). 565

4 Chapter 17: Setup and Administration for ISVs Using a Sandbox for Development We recommend that all ISV customers create at least one dedicated customer tenant for development purposes (i.e. a sandbox) that applications will be published from. Use sandbox customer tenants to develop and test your applications. Then use the XML publishing mechanism described in Chapter 16 to publish your application and deploy/update each application in your production Customers. Creating and Managing Customer Tenants The ISV Partner application contains Customer records to define customer tenants. To add a customer tenant, select the Customer tab, and click New Customer. Complete as much information as possible and provide data for the first administrative user. This will initiate the tenant creation process and the administrative user will receive a welcome with login information and a temporary password when the tenant creation process is completed. To prevent users from modifying applications, create an account for yourself in each of your customer tenants and assign the Administrator role (with all customization capabilities) to yourself rather than to your users. To manage customer tenants, from the Customers List, click the customer name. The available actions include the following: The Login button logs you in to a customer tenant as a super-admin, an invisible user with full access. From the More actions drop-down, the Login As option allows you to log in to a customer tenant as a particular user. The View Logs button allows you to view system logs that are useful for troubleshooting. From the More actions drop-down, the Reindex option allows you to re-create the full-text search index for that customer 566

5 Creating a Custom Log In Page Creating a Custom Log In Page A hosted or private cloud ISV account gives you the option to create and host a custom login page. This page can be hosted on another website and allow customer tenants to log in to Rollbase. Please contact Rollbase support or your account manager if you wish to see examples built by some existing Rollbase Hosted Standard or Private Cloud customers. Custoom HTML login pages must contain a FORM tag that includes the following: An action attribute pointing to A loginname parameter that will store the login name specified by a user. A password parameter that will store the password specified by a user. An act hidden parameter with a value of login. An rt hidden parameter points to the full URL of your custom login page (this parameter stands for "return to" and is stored as part of the user's session, so when they logout or their session expires the user is automatically taken back to your custom login page rather than Rollbase.com). An errmsg parameter is optional. If this HTTP parameter is set in the Login Page, URL errors, such as invalid user name, will be captured and displayed as error messages. If a login is unsuccessful for any reason, Rollbase will redirect the user back to your custom login page. The HTTP parameter errmsg will contain an error description. We strongly recommend that any custom login page capture and display this error message when it is non-empty. An o parametier is optonal. If this HTTP parameter is set in the Login Page URL, it iwll be captured and and stored in the o hidden parameter. For example, this parameter might contain the location of the first landing page. Once you have configured your custom login page you must update your ISV account settings to point to it. The following example shows a simple login page: <html> <head> <title>custom Login Page</title> </head> <body> <form action=" method="post" name="theform"> <input type="hidden" name="act" value="login"> <input type="hidden" name="rt" value=" <table cellpadding=0 cellspacing=0> <td><h2>secure Customer Login</h2><td> <tr height='10'><td></td> <td nowrap><b>user Name:</b> </td> <td><input type="text" maxlength="80" size="30" name="loginname"></td> <tr height='5'><td></td> 567

6 Chapter 17: Setup and Administration for ISVs <td nowrap><b>password:</b> </td> <td><input type="password" maxlength="80" size="30" name="password"></td> <tr height='5'><td></td> <td></td> <td alignment='left'><input type="submit" value=" Login " name="btns"></td> </table> </form> </body> </html> Creating a Page for Users to Retrieve Passwords A hosted or private cloud ISV account gives you the option to create a page for users to retrieve forgotten passwords. Such a page must contain HTML with a FORM tag satisfying the following conditions: An action attribute pointing to A loginname input parameter that stores the login name entered by a user. An input parameter that contains the address entered by a user (must match to login name). An act hidden parameter with a value of forgotpassword. An rt hidden parameter that points to the full URL of your custom login page. The following example shows a very simple password retrieval page: <html> <head> <title>custom Login Page</title> </head> <body> <form action=" method="post" name="theform"> <input name="act" value="forgotpassword" type="hidden"> <input type="hidden" name="rt" value=" <table cellpadding=0 cellspacing=0> <td><h2>forgot your password?</h2><td> <td colspan="2">in order for us to reset your password we need to confirm your identity. Please enter your user name. <br>you will receive an with a new temporary password.</td> <td nowrap><b>user Name:</b> </td> <td ><input name="loginname" size="30" type="text"></td> 568

7 Customizing Page Title Tags <td nowrap><b> Address:</b> </td> <td ><input name=" " size="30" type="text"></td> <tr height='5'><td></td> <td></td> <td alignment='left'><input type="submit" value=" Submit " name="btns"></td> </table> </form> </body> </html> Customizing Page Title Tags A hosted or private cloud ISV account gives you the option to customize the <title> tag used in application pages that will be accessed by your customer tenants. Valid templates may include any text and the following merge tokens that get replaced at runtime: {!A} - Current Application Name {!S} - ISV System Name (see above) {!P} - Customer's Subscription Plan Name (Solo, Professional, etc.) {!O} - Current Object name (if any) {!R} - Current Record name (if any) Using a Third-Party Cloud Service for Storage By default, Rollbase stores uploaded files and images on a local drive. The location of these files is specified in the System Console. Click the Storage server component to view the value. As an alternative to local storage, ISVs and Private Cloud customers can configure their customer tenants to use Amazon S3 or Microsoft Azure on a tenant by tenant basis. Use of third-party cloud storage is enabled on the customer tenant record. Using a third party cloud service for storage can impact performance because files and images are not served directly by Rollbase but from that third party. Progress recommends that you test the performance of your selected storage provider before deploying cloud storage in production scenarios. After you have enabled cloud storage, the files will be moved in asynchronous mode. The administrator will receive an message with summary of the moved files. After that, local files can be deleted to save disk space. All errors related to third-party cloud services are logged in the storage.log file. Please review this file if you're having problems with remote storage. See the following topics for more informatio: Using Amazon S3 569

8 Chapter 17: Setup and Administration for ISVs Using Microsoft Azure Using Amazon S3 To use the Amazon S3 service for file storage, you need to have an S3 subscription and you must have at least one bucket, your Access Key ID and Secret Access Key. You can retrieve the S3 ID and S3 Key values for your AWS account by logging in and navigating to the Security Credentials screen. 570

9 Using a Third-Party Cloud Service for Storage Enabling S3 Storage To enable Amazon S3 Storage per customer tenant, follow these steps: 1. From the Applications drop-down menu, select ISV Partner. 2. From the Customers List on the Customers tab, find the customer tenant for whom you want to enable S3 storage and click Edit. 3. Scroll down to the Cloud Storage section and from the Cloud Storage drop-down, select Amazon S3. 4. Enter the appropriate values in the following fields: S3 Bucket: the S3 bucket to use for this customer tenant. S3 ID: the Access Key ID assigned to your AWS account. S3 Key: the Secret Access Key associated with the Access Key ID. 5. If you want existing files to be moved from local storage to Amazon, check the box Move local files to Cloud storage. Otherwise, only files stored in the future will be stored in the cloud. If you do not see the following fields when you edit a customer tenant, use the Page Editor to add them from the Available Components section. Using Microsoft Azure To use the Microsoft Azure service you need to have an Azure account and you will need to specify the following information: Name of your Azure account. Optionally you can add "/" followed by customer-specific text prefix which will be added to container names used by customer. Prefixes allow storage for several customer tenants to use the same Azure account. The Account Key, which plays the role of a password. Click the Manage Keys link at the bottom of the Azure Management Portal page to obtain this key. Note: Azure account and prefix names can only contain lower-case letters, digits, and hyphens "-" (but not two hyphens in sequence). The length of the prefix cannot exceed 16 characters. The system will automatically format specified prefix to match these Azure limitations. The following examples illustrate how the Azure storage area relates to the specified Account Name: 571

10 Chapter 17: Setup and Administration for ISVs rollbase Account Name Rollbase Azure Name data template Azure Storage rollbase/test Rollbase testdata testtemplate rollbase/test_#1 Rollbase test-1data test-1template Enabling Azure Storage To enable Amazon S3 Storage per customer tenant, follow these steps: 1. From the Applications drop-down menu, select ISV Partner. 2. From the Customers List on the Customers tab, find the customer tenant for whom you want to enable S3 storage and click Edit. 3. Scroll down to the Cloud Storage section and from the Cloud Storage drop-down, select Microsoft Azure. 4. Enter the appropriate values in the following fields: S3 Bucket: leave this field empty, it does not apply. S3 ID/Account Name: the name of your Azure account. S3 Key/Account Key: the Account Key from your Azure account. 5. If you want existing files to be moved from local storage to Azure, check the box Move local files to Cloud storage. Otherwise, only files stored in the future will be stored in the cloud. 572