2019 February Release

Setting up the development environmentPermanent link for this heading

Before you can get started with the implementation of your Cloud App, you need to set up your development environment.

More precisely, you have to install Eclipse as well as the Fabasoft app.ducx and Fabasoft app.test plug-ins on your computer so you can start coding and create automated tests for your Cloud App.

Installing the Eclipse IDEPermanent link for this heading

Eclipse is a software development environment featuring an integrated development environment (IDE) and an extensible plug-in system. We recommend using the 64-bit edition.

Eclipse can be downloaded free of charge from the Eclipse web site http://www.eclipse.org/downloads [Ecli18]. Any edition is fine, so you can pick either Eclipse Classic or the Eclipse IDE for Java, PHP or C++ developers.

Note: You can also download a preconfigured Eclipse version from the “Fabasoft Cloud” Teamroom (see chapter “Fabasoft Cloud update cycle”). For you convenience, the Fabasoft app.ducx plug-in is already pre-installed in this version.

Eclipse requires the Oracle Java SE Development Kit (JDK), which can be obtained from the Oracle web site (see [Orac18a]).

Eclipse uses so-called features to package plug-ins and allow for full integration with the Eclipse platform. Fabasoft app.ducx provides a feature group that must be installed before it can be used with Eclipse.

Installing the Fabasoft app.ducx plug-inPermanent link for this heading

Fabasoft app.ducx is packaged as a feature group consisting of multiple Eclipse features and plug-ins. For the sake of simplicity, this book sometimes refers to the entire collection of plug-ins making up Fabasoft app.ducx as “the Fabasoft app.ducx plug-in”.

You can install the Fabasoft app.ducx feature by opening the “Help” menu in Eclipse and clicking “Install New Software”. Click “Add”. In the following dialog, enter http://update.appducx.com in the Location field and click “OK”.

Select the “Fabasoft app.ducx” feature group and click “Next”. Then click “Finish” to install Fabasoft app.ducx.

Note: Make sure that your proxy server (if necessary) is configured correctly in Eclipse (“Window” > “Preferences” > “General” > “Network Connections”) and that you are connected to the Internet, when installing the app.ducx plug-in (if your Eclipse installation does not meet all prerequisites, missing features are downloaded from the Internet, too).

Figure 6: Specifying a new update site in Eclipse

Updating the Fabasoft app.ducx plug-inPermanent link for this heading

The Fabasoft app.ducx plug-in for Eclipse is continuously improved and periodically released by Fabasoft. After each release, the latest version is made available for download from http://update.appducx.com.

In order to benefit from all the improvements implemented by Fabasoft, you should always keep your Fabasoft app.ducx plug-in up to date and regularly check for updates.

To update the Fabasoft app.ducx plug-in installed on your local computer, simply select “Check for Updates” from the “Help” menu in Eclipse and follow the steps of the update wizard.

Improving the performance of EclipsePermanent link for this heading

To improve the performance of your Eclipse environment, edit the eclipse.ini file found in the Eclipse installation folder and assign sufficient memory to the Java virtual machine by setting the -Xms and -Xmx parameters to an adequate value of at least 2 GB or more (e.g. “2g”) as the rule thumb is “the bigger, the better” when it comes to memory allocation.

Example

-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
-vmargs
-Xms256m
-Xmx2g

Working with the Cloud App VDEPermanent link for this heading

After getting a Fabasoft Cloud App VDE subscription, you have to create a “Virtual Development Environment” object in Fabasoft Cloud. You can create the “Virtual Development Environment” object on your home screen or in a folder of your choice.

When creating the “Virtual Development Environment” object, you are prompted to enter a password, which you have to use for accessing your Cloud App VDE later on. Then click “Next” to save your changes.

In the next step, select “Request Virtual Development Environment” from the context menu of the “Virtual Development Environment” object to initialize your new Cloud App VDE.

Note: You may only have one Cloud App VDE. Attempting to request additional Cloud App VDEs will fail.

To obtain the URL for accessing the self-service portal of your Cloud App VDE, double-click the “Virtual Development Environment” object and click the URL displayed in the Self-Service Portal URL property.

The URL has the following format: https://vde.fabasoft.com/dev<X>/vm<Y>/

Note: The placeholders <X> and <Y> contain the actual IDs assigned to your personal Cloud App VDE.

When connecting to the Cloud App VDE self-service portal, you are prompted for your credentials. Enter the user name developer and the password you have provided when creating the “Virtual Development Environment” object.

The self-service portal allows you to carry out the following tasks:

  • Restart Services: This will restart the web services of the Cloud Sandbox. A restart of the web services should solve problem situations where the Fabasoft Cloud portal does not respond anymore, e.g. due to an infinite loop in your Cloud App.
  • Restart Virtual Machine: This will restart the entire virtual machine (VM). A restart of the VM should only be required in exceptional cases.
  • Fabasoft Cloud Sandbox: This link is a redirect to your Cloud Sandbox. You can directly access the Cloud Sandbox by clicking the URL displayed in the Cloud Sandbox URL property of your development project or using the URL https://vde.fabasoft.com/dev<X>/vm<Y>/folio (be sure to replace the placeholders <X> and <Y> with the actual IDs of your Cloud App VDE)
  • Fabasoft app.telemetry: This link starts the Fabasoft app.telemetry management interface, which allows you to monitor your VM and identify performance issues caused by your Cloud App. For further information refer to the chapter “Fabasoft app.telemetry”.

Figure 7: Fabasoft Cloud App VDE self-service portal

Note: Your Cloud App VDE is automatically wiped and updated before every update of the Fabasoft Cloud. This will allow you to adjust your Cloud App to the latest version of Fabasoft Cloud before the actual update. Refer to the calendar in the “Fabasoft Cloud” Teamroom to find out when the updates of your Cloud App VDE will take place (see chapter “Fabasoft Cloud update cycle”). You are also notified via e-mail about upcoming updates.

Fabasoft reserves the right to reset your Cloud App VDE at any time. You can also reset it manually. After an update or reset of your Cloud App VDE, all data is lost.

Therefore, we strongly recommend using Fabasoft app.test tests to create the test data structures you need for testing your Cloud App. Do not create test data structures manually as you will have to recreate all of your test data after every update or reset of your Cloud App VDE.

Also note that your Cloud App VDE will not be backed up, and Fabasoft does not guarantee any service levels for it. The maximum size of the Cloud App VDE, including operating system and services is limited to 15 GB. For further details refer to [Faba19d].

Requests and suggestions for additional features as well as reports of issues and problems with the Cloud App VDE should be deposited in the “Fabasoft Cloud – Developer Forum” Scrum project (https://cloud.fabasoft.com/folio/mx/COO.6505.100.2.1283934) in Fabasoft Cloud in form of stories and defects.

If you click the “Fabasoft Cloud Sandbox” link in the self-service portal, you are redirected to the Cloud Sandbox, which is a Fabasoft Cloud installation similar to the production environment, and logged in as a “developer” user.

Figure 8: Fabasoft Cloud Sandbox

To log in with a different user account, start a new browser session and use the URL referring directly to the Cloud Sandbox: https://vde.fabasoft.com/dev<X>/vm<Y>/folio

There are several preconfigured test users available for accessing the Cloud Sandbox. For the remainder of this book, we will use a user named Wanda Carney with the user account carney0001.

Refer to the table in [Faba19c] for a complete list of the available test user accounts. All test user accounts share the same password, which you can define in the self-service portal.

For each test user, there are ten distinct, sequentially numbered user accounts available (e.g. carney0001, carney0002 and so on). The main reason for this is to facilitate the execution of Fabasoft app.test tests in different scopes. For further information on recording and running Fabasoft app.test tests refer to the chapter “Testing your Cloud App”.

Different test users have subscriptions for different editions of Fabasoft Cloud. If your Cloud App requires a certain edition of Fabasoft Cloud as a prerequisite, pick a test user with the desired edition when conducting manual tests or when creating Fabasoft app.test tests.

Note: The test users do not have access to the Fabasoft Cloud App VDE self-service portal. With a test user account, you can only access the Cloud Sandbox.

Fabasoft app.telemetryPermanent link for this heading

Fabasoft app.telemetry helps you to identify performance bottlenecks in your Cloud App.

When you click on the “Fabasoft app.telemetry” link in the self-service portal of your Cloud App VDE, you are redirected to the Fabasoft app.telemetry portal.

Figure 9: Fabasoft app.telemetry

For a detailed walkthrough on how to analyze a Fabasoft app.telemetry session refer to http://www.apptelemetry.com.