Many SAP Customers started using XS Advanced and there were several questions on how to deploy or where to deploy and what are the consideration for choosing any of those approached. Based on my experience with various customers I tried to address some key topics in this blog to consolidate information from various sources of documentations
There are various ways of deploying the XS Advanced runtime. Before deploying the XSA many scenarios need to considered that will have impact on your landscape maintenance activity. For example the system refresh scenarios where you will need to refresh only a certain tenants instead of complete system this deployment plays a key role. I will go through the limitations in detail in backup restore section. In general, The following additional services run where XSA is deployed:
One benefit of using the HANA Deployment Infrastructure (HDI) is that a clear interface exists that lists the dependencies to objects outside of the respective HDI container. With this it becomes pretty simple to adapt a project that should run in a different environment, such as when moving a project that has been developed in an on premise XSA environment with SAP Web IDE for SAP HANA to SAP HANA Cloud.
Below several concepts are illustrated that help to adapt existing projects that refer to objects that are not contained in the project.
The main challenge you will face when moving your project to a different environment is that you cannot rely on resources that are not included in your project. For example, resources might only exist under a different name or schema. The new development concepts of SAP HANA, in particular the deployment with the SAP HANA Deployment Infrastructure (HDI), prepares you for this task by abstracting away dependencies to resources outside of your project. Dependencies in HDI come into your project via mainly two routes:
When ever a developer is doing local build of a db module in WebIDE for HANA, it creates an HANA service instance that name looks like <USER><GUID><MODULE_NAME>.
You can see those HANA service instances via XSA Cockpit
The main tools for XS Advanced administration are the XS Command-Line Interface and the XS Advanced Cockpit.
For both of them, the prerequisites are to have an XS Advanced user with required role collections and also to be member of the organization/space you want to manage.
If you are using XSA only in the context of Data modeling (HDI Advanced Model) via WebIDE for HANA, you may face the situation that developers have XS Advanced users in development system but only basic database users in quality and production systems. For security reason, you may not want to provide them access to XSA Cockpit in Quality and Production systems.
There are various ways of deploying the XS Advanced runtime. Before deploying the XSA many scenarios need to considered that will have impact on your landscape maintenance activity .For example the system refresh scenarios where you will need to refresh only a certain tenants instead of complete system this deployment plays a key role . I will go through the limitations in detail in backup restore section. In general, The following additional services run where XSA is deployed:
◉ xscontroller: Central management component of XSA. It has a view on all deployed and/or running applications, and persists configuration and status information in the database
In this blog post I will try and show you the easiest way to import shapefiles data into HANA Cloud, via the wizard.
There are alternative ways of importing spatial data, that can be used.
◉ Import shapefile via wizard
◉ Import CSV via wizard and convert to spatial data types
◉ Import CSV from Cloud Object Store (S3, GCS, ADL) and convert.
The SAP Web IDE provides so-called replication tasks to set up real-time replication. It provides a graphical UI to browse tables in your connected source systems, create virtual tables, create subscriptions for real-time replication, create data load partitioning strategies, and more. The replication tasks in Web IDE are part of the SAP Smart Data Integration (SDI) toolset, which comes integrated with the SAP HANA platform, both on-premise and in the cloud.
SAP Analytics Cloud’s story mode supports various filter concepts such as story filters, page filters, widget filters, input controls and linked analysis. SAC’s Analytic Application uses a different approach to implement filter capabilities in dashboards. In fact, the Analytics Designer (where Analytic Applications are created) is all about customization and flexibility.
SAC’s Analytics Designer provides filtering capabilities through programming APIs. A full documentation of SAC Analytics Designer APIs can be found here. This enables developers to create the desired filtering logic within a dashboard. Furthermore, with Analytics Designer APIs you can create your own filtering concepts! This blog post will guide you along one specific scenario to create such a custom filter.
