1. Introduction

uberAPPS is the integrated software and services store that allows you to add, run and maintain a growing range of tools from within uberSVN, turning it into your all singing, all dancing development hub.

This guide runs through the inner workings of uberAPPS, to give you an overview of how to buy and setup applications and services.

2. Store

uberAPPS store

The uberAPPS showroom.

The store page is where available apps and services are displayed. Click on the app's logo or its 'more info' link to get more details. Users who don't have any special permissions will only see a store tab, the table below shows which user permissions correspond with additional uberAPPS tabs.

On a fresh install of uberSVN 11.8, the system admin (the account created during the installation) is automatically given the new uberAPPS User permission, which is required for making purchases. However, when moving from an earlier version to 11.8 using the updater, the system admin account is not automatically given the uberAPPS User permission.

uberAPPS User permission is enabled from the Permissions tab of a user's profile.

2.1 Who can do what in uberAPPS

User Permission Viewable uberAPPS tabs
Regular User, Global Team Admin, Global Repository Admin Store
System Admin Store, Requested Apps, Installed Apps
uberAPPS user Store, Account, Requested Apps

3. Product Screen


uberAPPS store as viewed by a regular user.

Each product or service in the uberAPPS store has its own product screen. This features a product description, where applicable a link to the developer's own website and either a buy or request button, depending on whether the user who is viewing the store has uberAPPS purchasing permission.

When viewing uberAPPS as a regular user, you'll be unable to purchase apps yourself. Instead you can send a request to your uberAPPS users. To do this, click on the Request button.

4. Request Application


Requesting an application.

You can add details about who the request is for, with an option for providing some notes to help the uberAPPS purchaser decide if the purchase is appropriate. To log the request, press SEND REQUEST. Once submitted the request will appear on the Requested Apps tab.

5. Account

uberAPPS store

Account registration screen.

The account tab can only be viewed by users who have the uberAPPS User permission on their uberSVN account. On first visiting the tab you are presented with the account registration screen where you enter the following details that will be tied to your payment account.

First Name:
The account holder's first name.
Last Name:
The account holder's last name.
Email address for the account holder.
The Company name.
Building name or similar.
The company address, or the address that tallies with the payment method.
The city in which the company is based.
The region in which the city is based.
Zip/Post code:
The post code for the company's office.
The country in which the company is based.
A security question that will be asked in the event that you need to contact WANdisco regarding your uberAPPS purchasing account.
The answer to your security question.
uberAPPS store

Account tab as it appears after the account has been registered.

Once the account has been set up clicking on the Account tab will present the account details, as shown above. Click Edit Details if you need to make any changes to your account details.

Before an apps can be purchased, payment details need to be added by clicking the Manage Payment Methods button. uberAPPS store

Manage Payment Methods.

The payment details that you enter are never stored in the uberSVN product, they're transmitted using a secure connection to our e-commerce provider.

tip"Billing Security
Our Payment Gateway is provided by Zuora, a PCI and SAS70 Compliant e-commerce server which appears on VISA's list of approved providers. In addition, Zuora is certified as Safe Harbour Compliant, a data protection framework set up by the European Commission on how to provide protection for stored personal information.

6. Requested Apps

uberAPPS store

Who can do what in uberAPPS.

Each time a user makes a request for an app, the request is logged on the Requested Apps tab.

The type of request; an Install is requesting that an app be purchased, downloaded and installed on the uberSVN server. Access indicates that the app is already available and just requires the administrator to configure the product to allow.
The name of the application that has been requested.
Requested By:
The name of the user who has made the apps request.
Requested For:
Indicates the users for which the application or service has been requested.
Information provided in support of the application request. This allows users to explain why they need access to the application.
Any available actions associated with the requested app will appear in the 'Action' column.

   Buy will begin take begin the purchasing process.
   Configure will take you to the configure screen from where you can change any available application settings, or set which users can view or use the application.

7. Manage Apps

uberAPPS store

Who can do what in uberAPPS.

All applications and services that have been purchased, or that are available free appear on the Manage Apps tab.

Application Name:
The name of the available application.
The version of the application that is currently installed or ready to install.
The status of the application, indicating if whether the application is Active or still awaiting installation/activation.
The date and time at which point the current application or service will need to be renewed. The Expiry is only really relevent for products or services that have a time-limit or is available on a subscription basis. You can otherwise ignore the Expiry date
Lists the available actions for each application. These may include Install, Configure, Cancel Subscription

8. Configure

uberAPPS store

Configure the application.

Applications that require some setup will present configuration screens, allowing you to modify any customisable features. Each application will have its own set of configuration settings. For example, Jenkins lets you decide whether it is viewable by all userSVN users, or only by selected users.