Skip to content
Examples and code samples for using the Skyve framework
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.

Skyve Cookbook

Examples and code samples for using the Skyve framework.


Skyve Script

Skyve Script is a new abbreviated way to declare a no-code application - using the markdown standard to allow developers to specify domain models.

Quick Overview

In Skyve Script, a document declaration looks like this:

## Address `MDL_Address`
- *addressLine1* text 100
- addressLine2 text 100
- addressLine3 text 100
- *suburb* text 50
- state enum (QLD,NSW,WA,NT,ACT,SA,VIC,TAS)
- *country* Country
- verified boolean

Skyve Script supports complex applications, with relationships between documents, for example:

## Organisation `MDL_Organisation`
- *name* text 100
- businessAddress Address
- postalAddress Address
- deliveryAddress Address

The script for a complete 'Organisation Address Book' application module would then be:

# "Organisation Address Book"

## Address `MDL_Address`
- *addressLine1* text 100
- addressLine2 text 100
- addressLine3 text 100
- *suburb* text 50
- state enum (QLD,NSW,WA,NT,ACT,SA,VIC,TAS)
- *country* Country
- verified boolean

## Country `MDL_Country`
- *name* text 100

## Organisation `MDL_Organisation`
- *name* text 100
- businessAddress Address
- postalAddress Address
- deliveryAddress Address

Using Skyve Script

You can use Skyve Script with the Skyve online project creator for a new project, or within an existing Skyve application to create additional documents.

Within an existing Skyve application, the Skyve admin module provides the Document Creator - a user interface for editing Skyve Script. By placing your markdown in the Input tab, the system will preview the markdown and generated document declaration when you change tab. Any errors will be highlighted in red in the Document Preview tab.

The power of Skyve Script is that you can create it anywhere anytime, on your phone, in notepad or on paper. You don't need a UML modelling application or diagramming tool, but it is sufficient to create a functioning no-code application in Skyve.

While Skyve Script is sophisticated enough to build real no-code applications, it is intended as a rapid development technique and not a replacement for a complete Skyve declaration. While the full Skyve declaration standard supports rich domain models sufficient for enterprise scale, sophisticated mission critical systems, Skyve Script will get you to a functioning no-code application in minutes.


Skyve Script has a few specific syntax requirements it is looking for when generating domain models:

  • New modules should be specified with a level 1 heading (#), followed by a space, then the module name in title case
    • e.g. # Admin
    • If a specific module title is required, it can be encapsulated in single or double quotes, e.g. # 'My Module'
  • New domain models (documents), should be specified with a level 2 heading (##), followed by a space, then the document name in title case
    • e.g. ## User
    • If a specific document title is required, it can be encapsulated in single or double quotes, e.g. ## 'My Document'
    • If the document is to be persisted, the persistent name should follow the document name surrounded by backticks (`), e.g. ## User `ADM_User`
  • Domain attributes (fields) should be specified as a list below the domain heading, by using a dash (-), followed by a space, then the attribute definition
    • Attribute definitions should start with the attribute name in camel case (no spaces, first letter lowercase, uppercase for new words), e.g. firstName
    • Required attributes should have their name surrounded by asterisks, e.g. - *firstName*
    • The type should follow the attribute name
    • If the type is text, the length should follow the type, e.g. - *firstName* text 150
    • If the type is enum, the values should follow the type in brackets, e.g. - state enum ("Not Started", 'In Progress', Complete)
    • If a specific display name is required, it can be encapsulated in single or double quotes, e.g. - 'Yes/No'
  • Associations should be specified as a list item by using a dash (-), followed by a space, then the association name in camel case, then the association document in title case
    • e.g. - country Country
    • Required associations should have their name surrounded by asterisks, e.g. - *country* Country
    • Association type can be specified surrounded by backticks after the document name, e.g. - country Country `composition`
  • Collections should be specified as a list item by using a plus (+), followed by a space, then the collection name in camel case, then the collection document in title case
    • e.g. + roles Role
    • Required collections should have their name surrounded by asterisks, e.g. + *roles* Role
    • Collection type can be specified surrounded by backticks after the document name, e.g. + roles Role `child`

⬆ back to top


When to use:

  • performing an instanceof fails when operating over subclasses of a document with a persistence strategy of single
  • Skyve logs an error performing a BindUtil.get():
14:09:22,785 SEVERE [SKYVE] (default task-14) Could not BindUtil.get(, allocations[0].relatedTransaction.source.selectedDebitAllocation)!
14:09:22,785 SEVERE [SKYVE] (default task-14) The subsequent stack trace relates to obtaining bean property selectedDebitAllocation from

The Util.deproxy() utility method lets you resolve this by loading the correct subclass.

Occurrence occ = edc.getToBeOccurrence();
occ = Util.deproxy(occ);
if (occ instanceof DeviceOccurrence) {

⬆ back to top

Ordering a collection in a data table

Collections can be ordered or unordered, where an ordered collection allows the user to define the sort of items in the list via drag and drop. Ordering on a collection can be enabled by adding the ordered="true" attribute to the collection declaration.

Collections can also have a default sorting by specifying the sort columns in the collection declaration in the document:

  <order by="binding1" sort="ascending" />
  <order by="binding2" sort="ascending" />

⬆ back to top


Heap space errors

During startup of the server, if you encounter a java.lang.OutOfMemoryError: Java heap space, a possible cause could be an error in your json file which can't be parse correctly. A sample stacktrace of this is below:

14:12:51,910 ERROR [] (ServerService Thread Pool -- 64) MSC000001: Failed to start service jboss.undertow.deployment.default-server.default-host./skyve: org.jboss.msc.service.StartException in service jboss.undertow.deployment.default-server.default-host./skyve: java.lang.OutOfMemoryError: Java heap space
    at org.wildfly.extension.undertow.deployment.UndertowDeploymentService$
    at java.util.concurrent.Executors$
    at java.util.concurrent.ThreadPoolExecutor.runWorker(
    at java.util.concurrent.ThreadPoolExecutor$
Caused by: java.lang.OutOfMemoryError: Java heap space
    at java.util.Arrays.copyOf(
    at java.lang.AbstractStringBuilder.expandCapacity(
    at java.lang.AbstractStringBuilder.ensureCapacityInternal(
    at java.lang.AbstractStringBuilder.append(
    at java.lang.StringBuffer.append(
    at org.skyve.impl.util.json.JSONReader.add(
    at org.skyve.impl.util.json.JSONReader.add(
    at org.skyve.impl.util.json.JSONReader.string(
    at org.skyve.impl.util.json.JSONReader.object(
    at org.skyve.util.JSON.unmarshall(
    at org.skyve.impl.util.UtilImpl.readJSONConfig(
    at org.skyve.impl.web.SkyveContextListener.contextInitialized(

⬆ back to top

Creating REST Services

The BasicAuthFilter provided in Skyve can be used to allow authentication using a HTTP basic auth header. So a user can make REST requests using their existing credentials, or create a specific API user in Skyve which has permission to the API.

The web.xml in the project will need to be updated to configure the filter, similar to the SkyveFacesFilter. Specify the init params for realm (optional and defaulted) and unsecured (optional).

You can either configure the filter in web.xml (see SkyveFacesFilter for something simliar) or by using a @WebFilter annotation on the class.

For example:

@WebFilter(filterName = "BasicAuthFilter", urlPatterns = {"/api/*"})

The filter has to init parameters:

private String realm = "Protected";
private String[] unsecuredURLPrefixes;

The realm is used when an unauthorised response is sent, it is an arbitrary value. The unsecured URL prefixes allows you to create exceptions that will not be secured by the filter. Its similar in use to SkyveFacesFilter in web.xml (the URL prefixes are separated by a newline).

Understanding Skyve Rest

Skyve provides a number of Rest endpoints to support whatever application you build.

However to use these you will require a knowledge of Rest and web filters. An integration test is available at

You can trial the endpoints in your browser to gain an understanding of how they work, before you begin coding interactions. To trial the endpoints, you'll need to edit the web.xml which is located in your project at: /src/main/webapp/WEB-INF/web.xml

Configuring The Session Filter

Insert this filter and mapping after the other filters:


Then redploy your app (or restart your app server).

Testing end points

The SessionFilter will allow you to interact with the end points while you have a valid Session, and you'll be redirected to a login page at the first interaction to authenticate. Once you've logged in, you can then exercise the endpoints using your browser. The SessionFilter allows you to make REST calls after initial login that will propagate the remote user onto the REST call's execution context (the logged in user).

For example:


This end point will return an array of json strings for all user contacts. Note that the address includes

  • rest - the filtered service
  • json - the specific implemented result type
  • admin - the Skyve module
  • Contact - the Skyve document

Your result will be similar to the following:

    "name":"Aaliyah Bowling",
    "mobile":"0474 618 810",

In the example above, there is only one Contact in the database, called admin. The fields returned are the fields which would be returned if you used the menu item Contacts in admin module, that is, the default Skyve query for Contacts.

To retrieve a specific instance, use the bizId of the instance in the address, for example:


Note that the id matches the bizId in the prior example, and that the entire Contact object is now retrieved - not only the fields in the default query. This includes the result of conditions declared in the Contact document.

  "name":"Aaliyah Bowling",
  "mobile":"0474 618 810",

Note the attributes, bizCustomer, bizModule and bizDocument define the specific entity. When using insert and update endpoints, these attributes specify the entity to be manipulated.

To retrieve data from a specific query, provide the query name, for example:


To retrieve a paged result set, provide the start and end rows and the specific Skyve query name, for example to retrieve results 0 to 9:


There are also endpoints provide for insert, update and delete.


These require a complete json representation of the object to be manipulated. These endpoints utilise the bizCustomer, bizModule and bizDocument within the json representation.

For example, the update the email address of the contact admin in the prior example from to, supply the modified json as follows:

curl -X POST -H "Content-Type: application/json" -d '{"bizModule":"admin","bizDocument":"Contact","name":"Aaliyah Bowling","contactType":"Person","email1":"","mobile":"0474 618 810","image":"","bizId":"58619c0d-496b-49e6-9fcb-ff43281ae740","bizCustomer":"demo","bizDataGroupId":null,"bizUserId":"bf8cb7c4-5d8a-477b-8b96-15a2bc72364a","bizVersion":5,"bizLock":"20170410143341392demo"}' http://localhost:8080/<projectName>/rest/json/update/

Note: on Windows, you will need to use double quotes instead of single quotes around the JSON, and escape the double quotes with a backslash, e.g. "{"created":true. This can also be performed as a GET request if the JSON is properly escaped.

Using the BasicAuthFilter

When you're ready to start coding comment out the following in your web.xml:

<!-- Secure rest services -->

This will stop these url patterns redirecting to the login page, and change the filter to the as follows:




The BasicAuthFilter allows authentication using a HTTP basic auth header. You can use the class by just changing the package to your package - there are no extra dependencies introduced by its use.

You can either configure the filter in web.xml (see SkyveFacesFilter for something similar) or by using a @WebFilter annotation on the class.

For example:

@WebFilter(filterName = "BasicAuthFilter", urlPatterns = {"/api/*"})

The filter has two init parameters:

private String realm = "Protected";
private String[] unsecuredURLPrefixes;

The realm is used when an unauthorised response is sent (it is an arbitrary value). The unsecured URL prefixes allows you to create exceptions that will not be secured by the filter. For comparison, review the SkyveFacesFilter in web.xml (the URL prefixes are separated by a newline).

Example (CURL)

curl --user name:password<projectName>/rest/json/query/admin/qContacts

Example (React)

const base64 = require('base-64');
var headers = new Headers();
headers.append("Authorization", "Basic " + base64.encode("admin:password01"));
fetch('<projectName>/rest/json/query/admin/qContacts', {
  headers: headers
.then((response) => {
.catch((error) => {
  console.error("err" + error);

Using the RestUserPersistenceFilter

If your REST API:

  • does not use basic authentication
  • requires some other form of authentication not able to be performed in a filter
  • is not being performed on behalf of a system user (e.g. a request from a 3rd party service)

You will still need a user set on the Skyve Persistence in order to query or update the database. The BasicAuthFilter attempst to use the Basic credentials supplied to authenticate and perform database requests. Another option is to create a specific API user which has the roles and permissions the API can access. The RestUserPersistenceFilter allows a named user to be specified for all requests which match a URL pattern.

If this sounds like the scenario you require, to begin using the filter addo the following in your web.xml (near the other filters):


You will need to change {restUsername} to the username of the API user you create in the admin module.

Modify {restUrlPattern} to be the url endpoint your API controller is listening at.

You will also need to update src/main/webapp/WEB-INF/spring/security.xml to allow unauthenticated requests:

<intercept-url pattern="{restUrlPattern}" access="permitAll" method="POST" />

Other Resources

⬆ back to top

Injecting Custom JavaScript into SmartClient

It is possible to use third party JavaScript within a Skyve application in certain scenarios, for example to use a custom mapping or charting library. An <inject> tag is available for this purpose when creating a view for a Document within the power user interface (SmartClient),

The following example creates a hard-coded chart using chartjs. Javascript can be used to retrieve data through Skyve using the built in REST API, or a custom REST endpoint within the application.

Below is a complete edit.xml for rendering a chart:

<?xml version="1.0" encoding="UTF-8"?>
<view xmlns="" xmlns:xsi="" name="edit" title="Chart Example" xsi:schemaLocation=" ../../../../schemas/view.xsd">
  <hbox minPixelHeight="600">
        <h3>My Custom Chart Example</h3>
        <canvas id="myChart"></canvas>
        // make sure SC has finished rendering the view
        view.opened = function(data) {
          // make sure the 3rd party script has fully loaded before trying to interact with the dom
          isc.BizUtil.loadJS('', function() {
            // hard-coded chart example from 
            var ctx = document.getElementById("myChart").getContext('2d');
            var myChart = new Chart(ctx, {
              type: 'bar',
              data: {
                labels: ["Red", "Blue", "Yellow", "Green", "Purple", "Orange"],
                datasets: [{
                  label: '# of Votes',
                  data: [12, 19, 3, 5, 2, 3],
                  backgroundColor: [
                    'rgba(255, 99, 132, 0.2)',
                    'rgba(54, 162, 235, 0.2)',
                    'rgba(255, 206, 86, 0.2)',
                    'rgba(75, 192, 192, 0.2)',
                    'rgba(153, 102, 255, 0.2)',
                    'rgba(255, 159, 64, 0.2)'
                  borderColor: [
                    'rgba(54, 162, 235, 1)',
                    'rgba(255, 206, 86, 1)',
                    'rgba(75, 192, 192, 1)',
                    'rgba(153, 102, 255, 1)',
                    'rgba(255, 159, 64, 1)'
                  borderWidth: 1
            // uncomment to only call this once, will be called each time if commented out
            // view.opened = function() {};
      <!-- disable actions unless required -->
      <!-- <defaults/> -->

In the above example, we use a blurb tag to output some custom HTML onto the page, which gives us our Canvas chartjs requires. There are other methods to obtain a reference to the hbox and then programatically add the canvas, but this is the simplest example.

The inject tag then adds our custom javascript to the page. To make sure that the page has loaded and been fully drawn by the browser, we use two callbacks in the javascript:

view.opened = function(data) {

This is called back when SmartClient has finished parsing the JSON from the server and rendering the components of the view.

isc.BizUtil.loadJS('', function() {

This is called after the chartjs library has been downloaded. Multiple loadJS callbacks can be nested inside each other if multiple scripts are required for the page.

Another example of injecting custom javascript can be found in the Office edit view in the whosinintegrate module of Skyve-ee. This manupulates the existing view to create a new button which opens an iframe in a Skyve popup window.

⬆ back to top

Adding Swagger Documentation to your REST API

Swagger is a documentation framework for REST APIs which allows external developers to explore your API and interact with your application. Swagger API definitions can be created manually, but it also provides libraries to automatically generate an API definition from annotations on your REST controllers.

If you are defining your own API endpoints for your Skyve application, the following setup can be used to integrate Swagger to parse your API and be available in your Skyve project (requires Skyve version > 20190201).

Define the API Path

Create a class (can be called anything, e.g. MyApplication). Swagger requires a configuration file for basic API information, which packages to scan for endpoints, etc. This can either be supplied in an external file, or created programatically. The JaxRsActivator below will load a defined openapi.yaml file in the root of your content specified in your JSON (so it can be different per server environment), or it will build it programatically if it is not found in the content directory.

After you create the file, the following needs to be customised:

  • your path to your API in the @ApplicationPath annotation
  • your class names of your REST API controllers in getClasses()
  • if using the programmatic Swagger configuration in buildProgrammaticContext(), provide the API information and the package to your REST controller classes
public class JaxRsActivator extends Application {

    public JaxRsActivator(@Context ServletConfig servletConfig) {
        SwaggerConfiguration oasConfig = buildProgrammaticContext();

        try {
            // check to see if there is a config defined in the content directory
            Path contextPath = Paths.get(Util.getContentDirectory(), "openapi.yaml");
            if (contextPath.toFile().exists()) {
                new JaxrsOpenApiContextBuilder()
            } else {
                new JaxrsOpenApiContextBuilder()
        } catch (OpenApiConfigurationException e) {
            throw new RuntimeException(e.getMessage(), e);

     * This tells Java to scan and load these classes against the application path
     * defined on the path. This is required for all controllers even without Swagger.
    public Set<Class<?>> getClasses() {
        return Stream
                .of(MyRestController1.class, // add each of your controller classes here
                        OpenApiResource.class, // required for swagger
                        AcceptHeaderOpenApiResource.class) // required for swagger

    private SwaggerConfiguration buildProgrammaticContext() {		
        OpenAPI oas = new OpenAPI();
        Info info = new Info()
                .title("API title")
                .description("API description.\n\nThis can contain markdown.")
                // .termsOfService("")
                .contact(new Contact()
                /*.license(new License()
                        .name("Apache 2.0")

        Server server = new Server();

        SwaggerConfiguration oasConfig = new SwaggerConfiguration()
        return oasConfig;

Update Spring security

Open the WEB-INF/spring/security.xml file for your project.

Add this above the <!-- Secure everything else --> block to allow Spring to not intercept basic authentication request to your API endpoint. Change the pattern if you modified it in your JaxRxActivator class.

    <!-- do not secure the API, as this is secured by the BasicAuth servlet -->
    <http auto-config="true" use-expressions="true" security="none" pattern="/api/**" />

Update web.xml

Open the WEB-INF/web.xml file for your project.

Enable the Documentation Servlet

Skyve provides an xhtml page which creates loads the Swagger UI client application. To make this more convenient to customers (e.g. instead of typing {applicationUrl}/swagger/swagger.xhtml into their browser), Skyve provides a documentation servlet.

Open your project's web.xml and uncomment the DocsServlet definition. The docsPath <init-param> tells the servlet where to forward to, and the <url-pattern> defines the URL for the servlet. So by default, accessing /docs will forward to /swagger/swagger.xhtml and load Swagger UI.

<!-- API documentation servlet -->

Turn on the BasicAuthFilter for your API URL

Add the following below the DocsServlet definition and customise it with the path to your API.

<!-- API filter -->

Update the pom

Open the pom.xml for your project.

In the <properties> section, include the version properties for the Swagger dependencies.


In the <dependencies> section, make sure you have the three dependencies for jackson-jaxrs, swagger-jaxrs2 and swagger-ui.


In your maven-war-plugin <plugin> configuration, add the following webResource. This ensures the Swagger.xhtml copies in the swagger UI version from the pom when the project is built.


⬆ back to top

Other Resources

⬆ back to top

Customer Scoped Roles

While Groups and Roles allow user permissions to be managed at the module level, some applications have permissions which span multiple modules and the permissions need a way to be linked to function correctly (e.g. a user may have incomplete access to application features if module permissions were not correctly applied to their account). To address this, a customer scoped role can be defined in the customer.xml which allows roles to be aggregated together into something coherent and cross module.

<roles allowModuleRoles="true">
    <!-- External Access Roles -->
    <role name="External Basic">
        <description>Basic role for all external users</description>
            <role module="admin" name="BasicUser"/>
            <role module="admin" name="AppUser"/>
            <role module="module1" name="ExternalBasic"/>
            <role module="module2" name="ExternalBasic"/>

The allowModuleRoles property controls whether the module roles show up in the admin User Interface or not.

Customer roles aggregate only module roles, they cannot reference other customer roles. Groups can be used to aggregate either module rules or customer roles (if enabled by allowModuleRoles).

SAIL Automated UI Tests

  • download the latest chromdriver.exe from
  • update src/test/java/sail/admin/ with the location of the downloaded chromedriver (line 12) and the baseUrl (line 17)
  • ensure you have the following dependencies in the project pom.xml
  • generate domain to make sure dependencies have been downloaded
  • check src/test/java/sail/admin/ and update the login instructions with correct login credentials for your project (login doesn't appear to support a default customer - so remove that from .json if you have it)
  • start wildfly server and deploy project
  • right-click AdminFunctionSail and run as JUnit- browser should fire up and tests should begin

Setting up a Skyve instance

Recommended requirements

We recommend the following:

  • 4GB RAM for Linux and 8GB RAM for Windows
  • Java JDK 8u191 (this is the JDK for Java 8)
  • Wildfly Wildfly 10.1.0.Final
  • Disk space requirements depend on the nature of the application especially if the database and content repository are located on the same drive, however, for most common applications, 50GB drive space will probably be sufficient.

Installation of prerequisites

To run a Skyve application, the server requires:

Java 8 (also called 1.8) - while the JRE is sufficient, the JDK is recommended.

Wildfly 10.1.0.Final

Installing database driver

For database access, load the appropriate driver and declare this driver in the Wildfly standalone.xml configuration file.

For example, for SQL Server:

  • load the sqljdbc42.jar into wildfy.../modules/system/layers/base/com/microsoft/sqlserver/main/
  • copy the following definition into a new file wildfy.../modules/system/layers/base/com/microsoft/sqlserver/main/module.xml
<?xml version="1.0" encoding="utf-8"?> 
  <module xmlns="urn:jboss:module:1.3" name=""> 
      <resource-root path="sqljdbc42.jar"/> 
      <module name="javax.api"/> 
      <module name="javax.transaction.api"/>
      <module name="javax.xml.bind.api"/>
  • declare the driver in the wildfly configuration file wildfly/standalone/configuration/standalone.xml stanza as follows:
  <driver name="sqlserver" module="">

Configuring ports

To configure which ports will be used for accessing the application, modify the section in the wildfly configuration file wildfly/standalone/configuration/standalone.xml for http and https:

  <socket-binding name="http" port="${jboss.http.port:8080}"/>
  <socket-binding name="https" port="${jboss.https.port:8443}"/>

For example, for external access, typically you would assign as follows:

  <socket-binding name="http" port="${jboss.http.port:80}"/>
  <socket-binding name="https" port="${jboss.https.port:443}"/>

Create a folder for content

Skyve includes the elastic content repository - the repository requires a dedicated folder to persist files. The user credential running wildfly (for example) will need read-write permissions to this folder.

Install the wildfly service

So that the Skyve application will be always available, install the wildfly service, ensuring that the service will have read/write access to the content folder. The following may be useful for linux installations -

Skyve application configuration

To deploy a Skyve application, there are typically three artefacts:

  • the application '.war' folder
  • the datasource 'ds.xml' file
  • the properties '.json' file

For example, if your Skyve application is called 'helloworld', these will be:

  • 'helloworld.war'
  • 'helloworld-ds.xml'
  • 'helloworld.json'

The 'ds.xml' and '.json' remain on the server you are deploying to, and are customised for that specific instance, so that when you are deploying a new version of your Skyve application, the instance settings do not need to be adjusted.

When deploying the Skyve application web archive 'war', ensure that matching configuration settings are updated in the associated 'ds.xml' and '.json' configuration files.

Ensure the 'ds.xml' file uses a connection string and credentials corresponding to the setting for the database driver above

Ensure the '.json' properties file has been updated for the specific instance including:

  • content directory
  • smtp settings
  • context url
  • maps and other api keys
  • environment identifier

Finally, ensure that the user credential that will run the wildfly service has read/write permissions to the wildfly folder and the content folder created above.

Deploying a new version of your Skyve application

Once a Skyve application has been successfully deployed, to update your application with a new version:

  • undeploy the previous version or stop the wildfly service
  • replace the application '.war' folder with the new version (remove the old version, copy in the new)
  • deploy the new version or start the wildfly service

If the server has multiple Skyve application deployments, you can replace one of these without impacting on other deployments by signalling an undeployment and deployment as follows:

To undeploy, create an '.undeploy' file in the wildfly/standalone/deployment/ folder corresponding to the name of your application (an empty text file with that name is all that is required), for example 'helloworld.undeploy'. After approximately 30s, wildlfly will replace this file with a file named 'helloworld.undeployed'.

To redeploy, create a '.dodeploy' file in the wildfly/standalone/deployment/ folder corresponding to the name of your application, for example 'helloworld.dodeploy' (an empty text file with that name is all that is required). After approximately 30s, wildfly will replace this file with 'helloworld.isdeploying' and once deployment is successful, wildfly will replace this with 'helloworld.deployed' (if successful) or 'helloworld.failed' (if unsuccesful).

Manually seeding new customer users

Creating the customer scope

Here's how to create another customer to the Skyve download example, for example a customer called acme:

  1. Copy the demo customer folder from \demo\skyve\src\skyve\customers\demo to \demo\skyve\src\skyve\customers\acme
  2. Rename the file \demo\skyve\src\skyve\customers\acme\demo.xml to \demo\skyve\src\skyve\customers\acme\acme.xml
  3. Edit the new file \demo\skyve\src\skyve\customers\acme\acme.xml and change the customer name value to match - i.e. on line 2 <customer name="acme" ...

All customisations specific to this customer will live within this customer folder.

Deploying the customer

If you're not using a development tool (an IDE like eclipse) and you just want another customer in the demo, then you'll need to copy the customer folder manually to the deployment area, i.e. copy \demo\skyve\src\skyve\customers\acme to \demo\skyve\javaee\skyve.ear\apps.jar\skyve\customers\acme

If you're using an IDE like eclipse then this copy will happen automatically.

Adding a setup user

However to start creating data within that customer context, you'll need a user credential in the database so that you can log in the first time. There's several ways to do this but the simplest at the moment would be to open up the database and run a script - this will inject a user credential. This is just to get you started. Once you've logged in as this user, you can begin adding more users and data via the user interface.

Now start up the application server, by running \demo\run.bat (or \demo\ if you're not using Windows)

Using the h2 database manager

If you're using the demo h2 database, to access the h2 database manager embedded in the demo, browse to http://localhost:8080/skyve/h2

Signing in

Check that the JDBC URL matches the name of the h2 file in the \demo\content\ folder - for the demo, this will be demo - and so the JDBC URL should have the full path, for example jdbc:h2:C:/demo/skyve/content/demo (where C:/demo/skyve/content/demo is the full path to the file demo.h2.db - without the ".h2.db")

Inserting the user record

NOTE: You will only ever need this script once - to get started - from that point on you won't need to use SQL again to build, test or maintain your application.

Paste in the following lines into your database manager (modify by replacing acme with your customer name):

INSERT INTO adm_contact (bizId,bizVersion,bizLock,bizCustomer,bizUserId,bizKey,name,mobile,email1,contactType) VALUES 
('setupContact',72,'20080114123937714setup','acme','setup','Setup User','Setup User',NULL,'','Person');

INSERT INTO adm_securitygroup (bizId,bizVersion,bizLock,bizCustomer,bizUserId,bizKey, name,description) VALUES 
('setupGroup',200,'20080114123937714setup','acme','setup','Setup','Setup','Setup user');

INSERT INTO adm_securitygrouprole (bizId,bizVersion,bizLock,bizCustomer,bizUserId,bizKey, roleName,parent_id) VALUES 

INSERT INTO adm_securityuser (bizId,bizVersion,bizLock,bizCustomer,bizUserId,bizKey, userName,password,contact_id) VALUES 

INSERT INTO adm_securityuser_groups (owner_id,element_id) VALUES  ('setup','setupGroup');

Using h2

NOTE: This script assumes the SHA1 password hashing algorithm. If you're using something else, you'll need to swap the value '0RGzjA5zvIZ8S61AI2BqDg32TC8=' for the encrypted value using that algorithm.

The above script can be trivially modified if you're using an RDBMS other than h2.

Run the script, then browse to the application at localhost:8080\skyve

Now you can log in as the setup user in the new customer acme - with the following credentials:

  • Customer acme
  • Username setup
  • Password password01

Customer sign in

⬆ back to top

You can’t perform that action at this time.