-
-
-
- Building blocks of the data model
- Basic concepts
- Classes
- Key fields
- Local lookup lists
- Fields and data types
- Defining the columns of a table
- Relations between classes
- Global lookup lists
- Filters
- Universal connected classes
- Deleting foreign records
- Class inheritance
- Storage of personal data on test and develop environment (scrambling)
-
- User interface versions
- Building blocks for user interface design
- Adding styles with a css
- Surrounding page
- Changing snippets
- Creating a custom login page (pre 3.4)
- Creating a custom login page
- Using velocity templates within the blueprint
- Create your own web pages
- HTML delivery requirements
- How to customize system mails
-
- Resource files
- Velocity - How does it work?
- Quick Velocity Tutorial
- Debugging velocity scripts
- Velocity Command Reference
- Script Editor Tutorial
- Using velocity for calculations
- Using predefined forms in a html design
- Velocity forms
- Data field identifiers
- Macros and methods
- Velocity library
- Velocity: using the #macro command
- velocity and xml
- Using AJAX in your velocity scripts
-
-
- Argon2 password conversion
- Introduction to security
- Secure development
- Security certification
- Security Exam
- Field properties concerning security
- Developing user groups securely
- Security considerations for user interface
- Secure file organization
- Securely using the request
- Cross Site Scripting (XSS)
- Other options concerning secure development
- Security analysis
- Secure deployment
- Secure application management
- Scrambling of testdata
- Anonymization of personal data
- Using robots.txt
- Permission settings
- Security measures
- Data encryption
-
- Search Engine Optimization
- OTP
- User Interface migration guide
- User account management
- Instructies voor implementatie van visueel editen van nieuwsbrieven
- Login as another user
- Support
- More information about moving to User Interface Version 4.0
- Standaard page layout
- Sections moved to layout
- Aanpassingen in release 2024-7
- Media library
- Aanpassingen in release 2024-10
- Analytics and Matomo
- Registration forms
- How to change names of classes and fields?
- Responsible Disclosure Policy
- How to upload a blob in Velocity?
- Aanpassingen in release 2024-2
- Instances
- Componenten in onze technologie
- Google Analytics
- Street and City helper (postcodecheck)
- Responsible disclosure-beleid
- Postcode check service (straat en huisnummer) kosten
- Expressions
- Regular Expression Reference
-
Connecting to database(s)
The CrossmarX Application Engine is able to connect to most common RDBMS products, like Oracle, SQLServer, MySQL, Postgress, etc. And other databases like SQLite and Derby
The name of the database(s) that is/are used by your application, are provided by CrossmarX. You are free to choose the location of the database(s), as long as the databases are accessible through the network.
If the RDBMS uses named users (almost all do), a database user should be created with sufficient rights:
- If the application only reads data from the database, read rights are sufficient (SELECT).
- If the application alters data, write rights are also needed (UPDATE, INSERT, DELETE).
- If you want the CrossmarX Application Engine to create and maintain the database structure automatically, additional rights concerning the Data Definition Language are necessary (CREATE, ALTER, DROP and INDEX).
Next open the file environment.properties in the directory etc and add the following entries:
- database.product: the database type (mysql, oracle, postgresql, ...)
- database.driver: the driver to be used
- database.urlprefix with value: the url to the RDBMS
- database.user with value: the login name of the database user
- database.password with value: the password of the database user
The content could look like this:
database.product=mysql
database.driver=com.mysql.jdbc.Driver
database.urlprefix=jdbc:mysql://localhost:3306/
database.user=scott
database.password=tiger
Testing
Open a browser and go to the engine panel:
http://YOUR_HOST:YOUR_PORT/engine?service=engine
Login with: login name engine and password crossmarx. Go to "Test database connection". Enter the name of the database and press "Go".
The engine should respond with "Connecting to database succeeded".
Now that the Application Engine runs and the database is connected, we can start your application. Open a new browser and go to:
YOUR_HOST:YOUR_PORT/engine
The CrossmarX Application Engine should now respond with the start screen of your application.