Cheat Sheet
- Docker Build & Push
- Clean Up Kronos Database
- Chrome Extensions
- Integration Tests
- Create Delivery Units
-
Local:
cd releng/server docker build -t ghcr.io/codbex/kronos . docker push ghcr.io/codbex/kronos -
Cloud Foundry:
cd releng/sap-cf docker build -t ghcr.io/codbex/kronos-cf . docker push ghcr.io/codbex/kronos-cf -
Kyma:
cd releng/sap-kyma docker build -t ghcr.io/codbex/kronos-kyma . docker push ghcr.io/codbex/kronos-kyma
If you want to use a HotSwap enabled JDK:
docker build -t ghcr.io/codbex/kronos --build-arg JDK_TYPE=hotswap-jdk --build-arg USE_HOTSWAP_JDK .
Using a HotSwap enabled JVM like TravaOpenJDK enables you to patch Java code while still debugging. Additional info if using IntelliJ could be found here. Have in mind the HotSwap limitations described there should not exist in the Kronos as the hotswap-jdk configuration in Docker uses a Dynamic Code Evolution VM by default.
DROP VIEW DIRIGIBLE_DISCUSSIONS_BOARD_RATING;
DROP VIEW DIRIGIBLE_DISCUSSIONS_BOARD_STATS;
DROP VIEW DIRIGIBLE_DISCUSSIONS_STATS;
DROP TABLE DIRIGIBLE_BPM;
DROP TABLE DIRIGIBLE_DATA_STRUCTURES;
DROP TABLE DIRIGIBLE_DISCUSSIONS_BOARD;
DROP TABLE DIRIGIBLE_DISCUSSIONS_BOARD_TAG;
DROP TABLE DIRIGIBLE_DISCUSSIONS_BOARD_VOTE;
DROP TABLE DIRIGIBLE_DISCUSSIONS_TAGS;
DROP TABLE DIRIGIBLE_DISCUSSIONS_USERS;
DROP TABLE DIRIGIBLE_DISCUSSIONS_COMMENT;
DROP TABLE DIRIGIBLE_EXTENSIONS;
DROP TABLE DIRIGIBLE_EXTENSION_POINTS;
DROP TABLE DIRIGIBLE_IDENTITY;
DROP TABLE DIRIGIBLE_JOBS;
DROP TABLE DIRIGIBLE_LISTENERS;
DROP TABLE DIRIGIBLE_MIGRATIONS;
DROP TABLE DIRIGIBLE_ODATA;
DROP TABLE DIRIGIBLE_ODATA_CONTAINER;
DROP TABLE DIRIGIBLE_ODATA_MAPPING;
DROP TABLE DIRIGIBLE_ODATA_SCHEMA;
DROP TABLE DIRIGIBLE_PUBLISH_LOGS;
DROP TABLE DIRIGIBLE_PUBLISH_REQUESTS;
DROP TABLE DIRIGIBLE_SECURITY_ACCESS;
DROP TABLE DIRIGIBLE_SECURITY_ROLES;
DROP TABLE DIRIGIBLE_SYNCHRONIZER_STATE;
DROP TABLE DIRIGIBLE_SYNCHRONIZER_STATE_LOG;
DROP TABLE DIRIGIBLE_WEBSOCKETS;
DROP TABLE QUARTZ_BLOB_TRIGGERS;
DROP TABLE QUARTZ_CALENDARS;
DROP TABLE QUARTZ_CRON_TRIGGERS;
DROP TABLE QUARTZ_FIRED_TRIGGERS;
DROP TABLE QUARTZ_LOCKS;
DROP TABLE QUARTZ_PAUSED_TRIGGER_GRPS;
DROP TABLE QUARTZ_SCHEDULER_STATE;
DROP TABLE QUARTZ_SIMPLE_TRIGGERS;
DROP TABLE QUARTZ_SIMPROP_TRIGGERS;
DROP TABLE QUARTZ_TRIGGERS;
DROP TABLE QUARTZ_JOB_DETAILS;
DROP TABLE KRONOS_DATA_STRUCTURES;
DROP TABLE KRONOS_IMPORTED_CSV_RECORDS;
DROP TABLE KRONOS_JOBS;
DROP TABLE KRONOS_ODATA;
DROP TABLE KRONOS_PRIVILEGES;
DROP TABLE KRONOS_SECURE_STORE_LIST;
DROP TABLE KRONOS_SECURITY_ACCESS;
DROP TABLE KRONOS_TABLE_IMPORT_TO_CSV;To Visualize XML install chrome extension xml-tree
It will be used when showing xml related data, for example as *.xsodata.
The main focus is to test HDB and XS related artifacts with different end-to-end scenarios against PostgreSQL, MySQL and SAP HANA Cloud.
Allow testing HDB related artefacts to the specified database by synchronizing and asserting if they are created, updated or deleted.
Allow testing custom defined and sample applications which include both HDB and XS related artifacts by making http calls to the services the applications provide and asserting the returned data.
Allow testing ui invoked operations.
The itests profile is to be run as follows:
mvn verify -P itests -Dhana.url="jdbcUrl" -Dhana.username="jdbcUsername" -Dhana.password="jdbcPassword"
Note that you have to provide the credentials of your own HANA Cloud instance and more importantly to wrap them in quotes! Otherwise you might not be able to connect to the db instance due some special characters in respective db properties.
To find more details about an Insufficient Privileges Error execute the following stored procedure:
call SYS.GET_INSUFFICIENT_PRIVILEGE_ERROR_DETAILS ('<ERROR-GUID>', ?) Note: Before executing the command, replace the
<ERROR-GUID>placeholder.
A delivery unit (DU) is a group of transportable packages that contain objects used for content delivery. You can use the SAP HANA Application Lifecycle Management to create a DU for your application content or your software component.
To create a delivery unit with the SAP HANA Application Lifecycle Management, you must ensure the following prerequisites are met: You have access to an SAP HANA system. You have the privileges granted by a role based on the SAP HANA sap.hana.xs.lm.roles::Administrator user role template. The vendor ID is defined for the DU. The vendor ID defines the repository namespace in which the new DU resides.
You use a DU to transport the design-time objects that are stored in the SAP HANA repository between two systems, for example, from a development system to a consolidation system. To create a new delivery unit using the SAP HANA application lifecycle management, perform the following steps.
1. Open SAP HANA Application Lifecycle Management.
SAP HANA Application Lifecycle Management is available on the SAP HANA XS Web server at the following URL: http://:80/sap/hana/XS/lm
2. Choose the PRODUCTS tab.
3. Choose the Delivery Units tab.
4. Choose Create.
The New Delivery Unit dialog box appears.
Enter details for the new DU.
When entering details, note the following points:
- Name
The field is mandatory and you must follow strict naming conventions, for example, use capital letters.
- Vendor
This field is mandatory. However, you cannot enter a vendor here; the box is populated by the value you enter when defining the vendor in the SETTINGS tab.
- Version
Version numbers must take the form “#.#.#”, for example, 1.0.5, where:
- 1 = the DU version number
- 0 = the support package version (if required)
- 5 = the patch version (if required)
The numbers you enter here refer to the application component that you are developing; the numbers do not refer to the patch or service-pack level deployed on the SAP HANA server. Choose Create. The new delivery unit is added to the SAP HANA repository in the namespace specified by the vendor ID and the application path. Check the status bar at the bottom of the browser window for error messages. Choose the message link to display the message text.