SAP Web IDE for SAP HANA SPS 12

Known Issues
This list provides a set of current known issues of the SAP Web IDE for SAP HANA development tools (as
of May 2016, SPS12).

Contents
Development ................................................................................................................................................... 1
Building, Running, Packaging, Deploying MTAs ............................................................................................ 1
General............................................................................................................................................................. 2
Version Control (Git) ....................................................................................................................................... 3
SAP HANA Runtime Tools (HRTT) ................................................................................................................... 3
Security ............................................................................................................................................................ 4
Resolved Issues................................................................................................................................................ 5

Development
Topic

Issue

Impact/Workaround

Debugging

Changes in the source require a

restart of the Node.js debugger.

The Node.js debugger always needs to be restarted

upon any source changes, there is no hot deployment.

Node.js
development

Node.js modules with the XSJS

support, which had been created in
the SPS11 version of SAP Web IDE,
cannot be built and run. They
require a manual adjustment after
an upgrade to the SPS12 version.
No embedded support of SQL
Script debugging.

Workaround: To be able to build and run such

modules, you need to update their package.json file
with the dependencies for the following modules:

SQL Script
debugging

"sap-xsjs-test": 1.2.2
sap-xsjs: 1.6.4
sap-xsjs-test: 1.0.7

Workaround: SQL Script debugging can only be

triggered from SAP HANA Runtime Tools application.

Building, Running, Packaging, Deploying MTAs

Topic
Selective build

Issue
It is not possible to build individual
database artefacts in HDB modules.

Impact, Workaround
As the build of HDB modules is transactional, in case of
error during deployment of all the artefacts in a
module, the deployment process is completely rolled
back.

MTA

No support for module parameters

Deployment

It is not possible to deploy a

packaged application (mtar) into
SAP HANA XS, advanced model (XS
Advanced) directly from SAP Web
IDE.
The package.json that is generated
by SAP Web IDE for an HDB module
during packaging always contains
the autoUndeploy flag. With this
flag, the XS Advanced HDI deployer
automatically undeploys any
runtime object that is not
described in the design-time
artifacts. For example, if an existing
table was deleted from a CDS file,
this table will be automatically
deleted from the database once
the CDS is deployed again with the
autoUndeploy flag.
After upgrading from SPS11 to
SPS12, it is not possible to build an
existing project created in SPS11.
The builder component does not
start.

Packaging

Building

Workaround: To exclude from build the artefacts that

cause errors, temporarily change their file extensions
to ".txt".
When running a module, the default application
parameters such as host, port, memory etc., will be
used. There is no workaround.
Use the XSA command line tools (xs deploy).

Though this behavior is required in development

systems, it might be not required in QA or production
systems.
Workaround: If this behavior is not required in the
target system in which you deploy the MTA archive
produced by SAP Web IDE, you can manually delete
this flag from the package.json of each HDB module in
the archive.

The builder component is not automatically installed

into the development space.
Workaround: create a new dummy project. This will
trigger the builder installation.

General
Topic
Installation

Issue
Installation of the SAP Web IDE
components sometimes fails.

Resource
provisioning

Automatic provisioning of
resources, which are declared in
the MTA descriptor (mta.yaml), is
available only for the
com.sap.xs.hdi-container type.

Impact, Workaround
Workaround: Restart the XS Advanced Deploy Service
by running the command xs rs deploy-service
in the XS Advanced CLI, and then reinstall the
components.
Workaround: To develop an application that uses
resources of other types, such as UAA, manually
create the corresponding XS Advanced service using
the XS Advanced CLI, and add to the mta.yaml a
resource with the same name as the service. Define
the required dependencies on this resource. When the
module is run, the specified resource will be bound to
the module.

Service
binding

HDI services, which are bound to a

module, remain bound to the
module after the resource
dependency in mta.yaml is
changed or removed.

Resource
deallocation

When a user logs out, or when the

user session terminates after a
timeout, the allocated server-side
resources are not freed up.

Multitenant
database
containers
Search

No support for multitenant

database containers.

Unicode
support
Browser
support

Search by file name is casesensitive.

Various limitations (e.g. filenames
limited to ASCII letter subsets).
SAP Web IDE is not supported on
Internet Explorer

For example, a Node.js module has a dependency on

an HDI resource. When the module is run for the first
time, it binds to the corresponding HDI service. If the
resource name is changed or the resource dependency
is removed in mta.yaml while the module is running,
the previous service binding remains alongside the
new one. This might cause unexpected behavior.
Workaround: after changing a dependency, stop the
running module explicitly, and then run it again.
Server-side resources remain allocated, and may grow
over time.
Workaround: Use the XS Advanced command line
tools to manually review the status of running
processes and services, and/or kill unnecessary ones.

Workaround: use wild cards in the seach text: for

example, search for *ile instead of File or file.
In the user-defined names, use ASCII only.
Use other browsers.

Version Control (Git)

Topic
Creating a
repository
User name
and email
listed for
commits
Branch
management
Git settings
Integration
with Gerrit

Issue/Limitation
It is not possible to execute the
git init command from SAP
Web IDE.
The user name and email listed for
your commits are the user name
and email from your SAP HANA
system, not the user name and
email from your Git system.
Creation of multiple branches is not
possible.
Git settings are defaulted during
cloning, and cannot be changed by
the user.
It is not possible to work with
Gerrit as a code review system.

Impact, Workaround
The creation of a repository, a branch, and an initial
commit should be done outside of SAP Web IDE.
The user cannot change or override this for a specific
project or Git repository.

Use the master branch for all changes.

The default settings allow to work with Git in the SAP
Web IDE development scenarios.
When the developer pushes a commit/change, the
remote branch is updated without a code review
process forced by Gerrit. Change ID will not be
generated.
The developer must get a permission to push to the
remote branch (Git administration).

Git operations

No support for empty Git

repositories.

When you create a new repository, make sure that it

has at least one commit. On GitHub, you can achieve
this by selecting the "Initialize this repository with a
README" option in the repository creation page.

SAP HANA Runtime Tools (HRTT)

Topic

Issue

Impact/Workaround

SQL
debugging

Occurs after the user has chosen to ignore the

browser warning about using an invalid or untrusted
certificate, when running HRTT over HTTPS in Firefox
and Mac OS Safari, and sometimes in Google
Chrome. When the user applies SQL debugger
settings, a warning message is displayed indicating
that SQL debugging could not be connected to the
currently selected HDI service.

The SQL Debugger feature requires a

valid and trusted server certificate
for making its connections, therefore
running HRTT over HTTPS requires a
well-known certificate to be
configured in your XS Advanced
environment.

SQL queries

Occurs when executing a SELECT statement where

some column names or name aliases are not unique.
The result set will contain
wrong values in these columns.
For example, a query
SELECT T.column1 AS x, T.column2 AS x FROM T;
would return an incorrect result set.

Workaround: use unique column

aliases in a query to ensure that all
result set column names are unique.
For example:
SELECT T.column1 AS x1, T.column2
AS x2 FROM T;

Security
Topic

Issue / Impact

Workaround

Space isolation

SAP Web IDE supports full isolation between the SAP space
in XS Advanced, in which the SAP tools are installed and
run, and a development space in which applications
developed in SAP Web IDE are built and run.
However, isolation between different development spaces
is not supported. All applications developed in SAP Web IDE
are located in the same development space.
This means that any authenticated SAP HANA database
user assigned to the SpaceDeveloper role for the
development space has full access to all applications in this
space, and can potentially cause disruption or misuse of
these applications.
For more information about the XS Advanced security
concept, see SAP HANA Security Guide.

To create an isolated
environment, for example,
for different departments,
you can install SAP Web IDE
in a separate instance of XS
Advanced for each
department.

Administration

Authorization

Backup and
recovery
File upload

SAP Web IDE does not restrict access to administration

tasks by roles. Any authenticated SAP HANA database user
assigned to the SpaceDeveloper role for the SAP space can
manage SSL certificates for Git access, as well as perform
any administration tasks, such as deleting user workspaces,
updating npm registry content and so on.
SAP Web IDE does not define any specific roles. This means
that any authenticated SAP HANA database user can access
SAP Web IDE, and create and maintain projects in his own
workspace. However, the user requires
the SpaceDeveloper role for the development space to
build or run applications.
SAP Web IDE does not support backup and recovery for
workspace content (projects, folders, files).
No automatic virus scan and content validation of files
before upload to SAP Web IDE.
Malicious content can be uploaded to SAP Web IDE.

No workaround is available

No workaround is available

Use a Git repository as a

backup.
Developers should perform
a virus scan and content
validation of the files using
external tools before
uploading them.
Alternatively, customers
could use a file-based
antivirus to scan the files on
the disk.

Resolved Issues
The following issues have been resolved as of SPS12.
Topic

Issue / Impact

Workaround

Node.js
development

No support for npm repositories and dependencies in

locations, which issue SSL certificates that are not publicly
trusted.

Building an MTA

Building a multi-target application does not automatically

trigger a build of all its modules.

Workaround: Create a
node_modules subfolder in
the Node.js module folder,
and import there the
external packages including
their recursive
dependencies. Write the
code and run the modules
as usual.
Workaround: before
building the whole
application, build all the
modules in the order
according to the
dependencies defined in the
MTA descriptor (mta.yaml).

Workspace and
project access

SAP Web IDE does not limit access to workspaces.

No workaround

Any authenticated SAP HANA database user have full

access to the build and run logs, as well as database tables.
General

In the About box, SAP internal mode is displayed under the

version number.

Ignore

SAPUI5

No local installation of SAPUI5 is available. Developers

should refer to the online version of SAPUI5.

Solution in SPS 12:

Developers who for security
reasons dont connect their
client computers to the
Internet, can install a local
version of SAPUI5, and
configure their HTML5
modules to reference this
version, using cross-MTA
dependencies.